| 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: <20130321221256.GA30620@redhat.com> Date: Thu, 21 Mar 2013 18:12:56 -0400 From: Dave Jones <davej@...hat.com> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Al Viro <viro@...iv.linux.org.uk>, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: VFS deadlock ? On Thu, Mar 21, 2013 at 02:18:15PM -0700, Linus Torvalds wrote: > On Thu, Mar 21, 2013 at 2:02 PM, Dave Jones <davej@...hat.com> wrote: > > > > here we go... > > > > WARNING: at fs/namei.c:2335 lock_rename+0x156/0x160() > > p1=irda p2=irda > > Ok, good. I ssupect it's /proc or /sys, we do have that entry there. > > But in fact I suspect we do want the parent name after all, because I > think we have multiple "irda" directories. There's the one in > /proc/net/ (added by net/irda/irproc.c), and there's a sysctl CTL_DIR > "irda" directory (kernel/sysctl_binary.c). And there might even be a > few other ones in /sys too, thanks to the ldisc called "irda" etc. > > I don't see where the shared inode comes from, but I suspect that > would be easier to guess if we actually see which particular case it > ends up being.. it's not just irda fwiw.. p1=rpc p2=rpc p1parent=net p2parent=net not sure why the printk with Al's last debugging info didn't print out.. Investigating.. Dave -- 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