Re: VFS deadlock ?
From: Linus Torvalds
Date: Thu Mar 21 2013 - 16:32:50 EST
On Thu, Mar 21, 2013 at 1:26 PM, Dave Jones <davej@xxxxxxxxxx> wrote:
> those are qstr's, so I used d_name.name, right ?
Yup. And if you want to, you could do p1->d_parent->d_name.name too,
just to make things obvious. It's technically racy, but by the time
the bug happens, who cares?
> I'd be surprised actually, I've got sysfs excluded from its list of victim files,
> due to unrelated issues still unresolved. So unless it followed a symlink into
> sys from somewhere in /proc or /dev...
> It took a few hours to reproduce last time, I'll increase the number of child
> processes to see if I can trigger it faster now that I have the debug stuff in there.
Hmm, ok. Do you have any network mounts or fuse or other "odd"
filesystems etc? The whole "aliased inodes" thing might come from
something like that.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/