| 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: <20130321204704.GZ21522@ZenIV.linux.org.uk> Date: Thu, 21 Mar 2013 20:47:04 +0000 From: Al Viro <viro@...IV.linux.org.uk> To: Dave Jones <davej@...hat.com>, Linus Torvalds <torvalds@...ux-foundation.org>, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: VFS deadlock ? On Thu, Mar 21, 2013 at 04:36:39PM -0400, Dave Jones wrote: > at some point during the fuzz run, this happened.. > > Mar 20 15:20:41 kernel: [ 7578.784674] fuse init (API version 7.21) > Mar 20 15:20:41 systemd[1]: Mounting FUSE Control File System... > Mar 20 15:20:41 systemd[1]: Mounted FUSE Control File System. > > I guess something wandered into /dev/fuse and did something. Not sure why > systemd reacted though... AFAICS, fuse uses d_materialise_unique() and d_splice_alias(), though, so it's not too likely source of that crap; there's no d_instantiate() calls at all and the sole d_add() is using an inode that has just been allocated, so it won't be creating aliases either... -- 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