Skip to content
Snippets Groups Projects
Select Git revision
  • feature/libtcg-rebase default protected
1 result
Search by author
  • Any Author
  • Anton Anton anjo
1 author
  1. Mar 07, 2022
  3. Oct 27, 2021
  5. Dec 13, 2020
  7. Sep 15, 2020
    • Christian Schoenebeck's avatar
      9pfs: disable msize warning for synth driver · c418f935
      Christian Schoenebeck authored 
      
Previous patch introduced a performance warning being logged on host
side if client connected with an 'msize' <= 8192. Disable this
performance warning for the synth driver to prevent that warning from
being printed whenever the 9pfs (qtest) test cases are running.

Introduce a new export flag V9FS_NO_PERF_WARN for that purpose, which
might also be used to disable such warnings from the CLI in future.

We could have also prevented the warning by simply raising P9_MAX_SIZE
in virtio-9p-test.c to any value larger than 8192, however in the
context of test cases it makes sense running for edge cases, which
includes the lowest 'msize' value supported by the server which is
4096, hence we want to preserve an msize of 4096 for the test client.

Signed-off-by: default avatarChristian Schoenebeck <qemu_oss@crudebyte.com>
Reviewed-by: default avatarGreg Kurz <groug@kaod.org>
Message-Id: <E1kEyDy-0006nN-5A@lizzy.crudebyte.com>
Signed-off-by: default avatarChristian Schoenebeck <qemu_oss@crudebyte.com>
      c418f935
  9. Oct 10, 2019
    • Antonios Motakis's avatar
      9p: Added virtfs option 'multidevs=remap|forbid|warn' · 1a6ed33c
      Antonios Motakis authored 
      
'warn' (default): Only log an error message (once) on host if more than one
device is shared by same export, except of that just ignore this config
error though. This is the default behaviour for not breaking existing
installations implying that they really know what they are doing.

'forbid': Like 'warn', but except of just logging an error this
also denies access of guest to additional devices.

'remap': Allows to share more than one device per export by remapping
inodes from host to guest appropriately. To support multiple devices on the
9p share, and avoid qid path collisions we take the device id as input to
generate a unique QID path. The lowest 48 bits of the path will be set
equal to the file inode, and the top bits will be uniquely assigned based
on the top 16 bits of the inode and the device id.

Signed-off-by: default avatarAntonios Motakis <antonios.motakis@huawei.com>
[CS: - Rebased to https://github.com/gkurz/qemu/commits/9p-next


       (SHA1 7fc4c49e91).
     - Added virtfs option 'multidevs', original patch simply did the inode
       remapping without being asked.
     - Updated hash calls to new xxhash API.
     - Updated docs for new option 'multidevs'.
     - Fixed v9fs_do_readdir() not having remapped inodes.
     - Log error message when running out of prefixes in
       qid_path_prefixmap().
     - Fixed definition of QPATH_INO_MASK.
     - Wrapped qpp_table initialization to dedicated qpp_table_init()
       function.
     - Dropped unnecessary parantheses in qpp_lookup_func().
     - Dropped unnecessary g_malloc0() result checks. ]
Signed-off-by: default avatarChristian Schoenebeck <qemu_oss@crudebyte.com>
[groug: - Moved "multidevs" parsing to the local backend.
        - Added hint to invalid multidevs option error.
	- Turn "remap" into "x-remap". ]
Signed-off-by: default avatarGreg Kurz <groug@kaod.org>
      1a6ed33c
  11. May 17, 2019
  13. Jan 08, 2018
  15. Jun 29, 2017
    • Tobias Schramm's avatar
      9pfs: local: Add support for custom fmode/dmode in 9ps mapped security modes · b96feb2c
      Tobias Schramm authored 
      
In mapped security modes, files are created with very restrictive
permissions (600 for files and 700 for directories). This makes
file sharing between virtual machines and users on the host rather
complicated. Imagine eg. a group of users that need to access data
produced by processes on a virtual machine. Giving those users access
to the data will be difficult since the group access mode is always 0.

This patch makes the default mode for both files and directories
configurable. Existing setups that don't know about the new parameters
keep using the current secure behavior.

Signed-off-by: default avatarTobias Schramm <tobleminer@gmail.com>
Signed-off-by: default avatarGreg Kurz <groug@kaod.org>
      b96feb2c
  17. Feb 28, 2017
  19. Nov 23, 2016
  21. Jul 12, 2016
  23. Jul 01, 2016
  25. Jun 06, 2016
  27. Feb 23, 2016
  29. Jan 19, 2012
    • Aneesh Kumar K.V's avatar
      hw/9pfs: Add new security model mapped-file. · 2c30dd74
      Aneesh Kumar K.V authored 
      
This enable us to do passthrough equivalent security model on NFS directory.
NFS server mostly do root squashing and don't support xattr. Hence we cannot
use 'passthrough' or 'mapped' security model

Also added "mapped-xattr" security to indicate earlier "mapped" security model
Older name is still supported.

POSIX rules regarding ctime update on chmod are not followed by this security model.

Signed-off-by: default avatarAneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
      2c30dd74
  31. Jan 04, 2012
  33. Dec 21, 2011
  35. Dec 04, 2011
  37. Oct 31, 2011
  39. Oct 15, 2011
  41. Oct 12, 2011
  43. Sep 22, 2011
  45. Aug 22, 2011
  47. Jun 01, 2011
  49. Apr 27, 2011
  51. Jan 23, 2011
  53. Dec 03, 2010
  55. Oct 20, 2010
  57. Sep 08, 2010