summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-06-22 16:09:49 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2022-06-22 16:09:49 +0300
commit3abc3ae553c7ed73365b385b9a4cffc5176aae45 (patch)
tree4cccb5183e9949f4b7e76d5d27af51806af76b2b /tools
parentca1fdab7fd27eb069df1384b2850dcd0c2bebe8d (diff)
parentb0017602fdf6bd3f344dd49eaee8b6ffeed6dbac (diff)
downloadlinux-3abc3ae553c7ed73365b385b9a4cffc5176aae45.tar.xz
Merge tag '9p-for-5.19-rc4' of https://github.com/martinetd/linux
Pull 9pfs fixes from Dominique Martinet: "A couple of fid refcount and fscache fixes: - fid refcounting was incorrect in some corner cases and would leak resources, only freed at umount time. The first three commits fix three such cases - 'cache=loose' or fscache was broken when trying to write a partial page to a file with no read permission since the rework a few releases ago. The fix taken here is just to restore old behavior of using the special 'writeback_fid' for such reads, which is open as root/RDWR and such not get complains that we try to read on a WRONLY fid. Long-term it'd be nice to get rid of this and not issue the read at all (skip cache?) in such cases, but that direction hasn't progressed" * tag '9p-for-5.19-rc4' of https://github.com/martinetd/linux: 9p: fix EBADF errors in cached mode 9p: Fix refcounting during full path walks for fid lookups 9p: fix fid refcount leak in v9fs_vfs_get_link 9p: fix fid refcount leak in v9fs_vfs_atomic_open_dotl
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions