potential race in FUSE's readdir() + releasedir()?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I am seeing something that to me looks like a race between FUSE's
readdir() and releasedir() handlers. On kernel 5.18, the FUSE daemon
seems to (ocasionally) receive a releasedir() request while a readdir()
request with the same `struct fuse_file_info *fi->fh` is still active
(i.e., the FUSE daemon hasn't sent a reply to the kernel for this yet).

Could this be a bug in the kernel? Or is there something else that could
explain this?

Best,
-Nikolaus

-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux