Luis Henriques <lhenriques@xxxxxxx> writes: > Dominique Martinet <asmadeus@xxxxxxxxxxxxx> writes: > >> Hi, >> >> Luis Henriques wrote on Thu, May 06, 2021 at 11:03:31AM +0100: >>> I've been seeing fscache complaining about duplicate cookies in 9p: >>> >>> FS-Cache: Duplicate cookie detected >>> FS-Cache: O-cookie c=00000000ba929e80 [p=000000002e706df1 fl=226 nc=0 na=1] >>> FS-Cache: O-cookie d=0000000000000000 n=0000000000000000 >>> FS-Cache: O-key=[8] '0312710100000000' >>> FS-Cache: N-cookie c=00000000274050fe [p=000000002e706df1 fl=2 nc=0 na=1] >>> FS-Cache: N-cookie d=0000000037368b65 n=000000004047ed1f >>> FS-Cache: N-key=[8] '0312710100000000' >> >>> It's quite easy to reproduce in my environment by running xfstests using >>> the virtme scripts to boot a test kernel. A quick look seems to indicate >>> the warning comes from the v9fs_vfs_atomic_open_dotl() path: >>> >>> [...] >>> >>> Is this a know issue? >> >> I normally don't use fscache so never really looked into it, I saw it >> again recently when looking at David's fscache/netfs work and it didn't >> seem to cause real trouble without a server but I bet it would if there >> were to be one, I just never had the time to look further. >> >> From a quick look v9fs uses the 'qid path' of the inode that is >> supposed to be a unique identifier; in practice there are various >> heuristics to it depending on the server but qemu takes the st_dev of >> the underlying filesystem and chops the higher bits of the inode number >> to make it up -- see qid_path_suffixmap() in hw/9pfs/9p.c in qemu >> sources. >> >> (protocol description can be found here: >> https://github.com/chaos/diod/blob/master/protocol.md >> ) >> >> >> In this case if there is a cookie collision there are two possibilities >> I can see: either a previously hashed inode somehow got cleaned up >> without the associated fscache cleanup or qemu dished out the same qid >> path for two different files -- old filesystems used to have predictable >> inode numbers but that is far from true anymore so it's quite possible >> some files would have the same lower bits for their inode number on the >> host... >> If you have the time to investigate further that would be appreciated, I >> have confirmed the fscache rework David suggested did not fix it so the >> work will not be lost. >> >> >> That's going to be very verbose but if you're not scared of digging at >> logs a possible way to confirm qid identity would be to mount with -o >> debug=5 (P9_DEBUG_9P + ERROR), all qid paths are logged to dmesg, but >> that might not be viable if there is a real lot -- it depends on how >> fast and reliable your quite easy to reproduce is... > > Thanks a lot for the quick reply, Dominique. I'll definitely allocate > some time to try to find a bit more about this issue (although I may end > up just hacking the code to print out the qids instead of turning on all > the debug). I just wanted to make sure I wasn't hitting some known > fundamental problem that simply couldn't be fixed without major changes. Ok, I spent some more time on this issue today. I've hacked a bit of code to keep track of new inodes' qids and I'm convinced there are no duplicates when this issue happens. OTOH, I've done another quick test: in v9fs_cache_inode_get_cookie(), I do an fscache_acquire_cookie() retry when it fails (due to the dup error), and this retry *does* succeed. Which means, I guess, there's a race going on. I didn't managed to look too deep yet, but my current theory is that the inode is being evicted while an open is triggered. A new inode is allocated but the old inode fscache cookie hasn't yet been relinquished. Does this make any sense? If this theory is correct, I'm not sure what's the best way to close this race because the v9inode->fscache_lock can't really be used. But I still need to proof this is really what's happening. Cheers, -- Luis
