diff options
author | Miklos Szeredi <mszeredi@redhat.com> | 2020-05-14 16:07:36 +0200 |
---|---|---|
committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | 2020-06-01 18:44:27 +0100 |
commit | 93bb3d8d4cdadf90f714b8ab71b4caa16092f38c (patch) | |
tree | a08cf112174941e4cc8f9868135e3bb3cfc45fdb /qemu-keymap.c | |
parent | 7d2ef6dcc1cf87e7506487051eda010b479f5d0e (diff) | |
download | qemu-93bb3d8d4cdadf90f714b8ab71b4caa16092f38c.zip qemu-93bb3d8d4cdadf90f714b8ab71b4caa16092f38c.tar.gz qemu-93bb3d8d4cdadf90f714b8ab71b4caa16092f38c.tar.bz2 |
virtiofsd: remove symlink fallbacks
Path lookup in the kernel has special rules for looking up magic symlinks
under /proc. If a filesystem operation is instructed to follow symlinks
(e.g. via AT_SYMLINK_FOLLOW or lack of AT_SYMLINK_NOFOLLOW), and the final
component is such a proc symlink, then the target of the magic symlink is
used for the operation, even if the target itself is a symlink. I.e. path
lookup is always terminated after following a final magic symlink.
I was erronously assuming that in the above case the target symlink would
also be followed, and so workarounds were added for a couple of operations
to handle the symlink case. Since the symlink can be handled simply by
following the proc symlink, these workardouds are not needed.
Also remove the "norace" option, which disabled the workarounds.
Commit bdfd66788349 ("virtiofsd: Fix xattr operations") already dealt with
the same issue for xattr operations.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Message-Id: <20200514140736.20561-1-mszeredi@redhat.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'qemu-keymap.c')
0 files changed, 0 insertions, 0 deletions