Alan Somers 1f44d1861a fusefs: handle evil servers that return illegal inode numbers ... * If during FUSE_CREATE, FUSE_MKDIR, etc the server returns the same inode number for the new file as for its parent directory, reject it. Previously this would triggers a recurse-on-non-recursive lock panic. * If during FUSE_LINK the server returns a different inode number for the new name as for the old one, reject it. Obviously, that can't be a hard link. * If during FUSE_LOOKUP the server returns the same inode number for the new file as for its parent directory, reject it. Nothing good can come of this. PR: 263662 Reported by: Robert Morris <rtm@lcs.mit.edu> Reviewed by: pfg Differential Revision: https://reviews.freebsd.org/D35128 (cherry picked from commit 0bef4927ea)		2022-06-18 08:16:20 -06:00
..
fusefs	fusefs: handle evil servers that return illegal inode numbers	2022-06-18 08:16:20 -06:00
tmpfs	Fix sys.fs.tmpfs.mknod_test.{char, block} by reverting r321967	2018-07-21 20:14:01 +00:00
Makefile	Refine fusefs test workaround for mips+llvm	2020-01-06 18:25:58 +00:00
Makefile.depend
Makefile.inc