| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <87zk78mvfe.fsf@devron.myhome.or.jp> Date: Tue, 10 Jul 2012 07:17:09 +0900 From: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> To: "Steven J. Magnani" <steve@...idescorp.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] fat (exportfs): reconnect file handles to evicted inodes/dentries "Steven J. Magnani" <steve@...idescorp.com> writes: >> Hm, not really, if the file handle is including parent ino. ext2 will >> get the latest parent ino, because it checks parent of inode of file >> handle. > > Can you point me to the code for this? The code I see looks pretty > congruent to what I think the FAT code would be. > >> But if the file handle is including parent ino and we believe it is >> parent, I think NFS server can be return the old parent. The difference >> is the result of ->get_parent(). > > I'm a little confused about which function we're discussing here. > fat_get_parent() isn't called with a file handle. fat_fh_to_parent() is, > but it is only called by exportfs_decode_fh() and I am reasonably sure > that that function is handling the case you're concerned about. Oh, you are right. I should discuss about it based on the new patch, and only if there is new usage of file handle (e.g. parent->i_no). -- OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists