On Sat, Jan 15, 2011 at 12:08 PM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
> On Sat, Jan 15, 2011 at 12:00:54PM +0100, Sedat Dilek wrote:
>
>> > Argh... ??In __do_follow_link() replace
>> >
>> > ?? ?? ?? ??if (link->mnt != nd->path.mnt)
>> > with
>> > ?? ?? ?? ??if (link->mnt == nd->path.mnt)
>> >
>> > Mismerge yesterday ;-/ ??I've pushed fix for that in for-next, will fold
>> > shortly. ??As for autofs4 breakage, I've a preliminary fix, testing it
>> > now.
>> >
>>
>> Hey, cool and thanks.
>>
>> Not sure if you catched them all, I have noticed on my latest
>> ("buggy") linux-next kernel these Call Traces when doing an
>> update-grub.
>
> That might be vfsmount being dropped when it shouldn't or dentry leaked.
> And seeing that it's umount(8), I would suspect the latter...
>
> Anyway, with the latest from dhowells we probably should have
> d_set_d_op() mess on autofs4 under control (in #for-next). ÂWhether
> it's enough to actually fix the sucker is a separate question, of
> course - there might very well be more crap.
>
> I've instrumented mntput() et.al. here; hopefully that'll make catching
> the remaining turds easier. ÂAs for dcache leaks... ouch. ÂCould you
> try to reproduce that one on the mainline kernel? ÂAt least that'd
> isolate things a bit.
>
Which version do you mean by "mainline"? 2.6.37-git12?
And with "[mismerge][foldme] breakage in __do_follow_link()" patch [1]?
I have to look by pulling-in(to) Linus-tree (linux-next) which patches
are not merged already.
- Sedat -
[1] http://git.kernel.org/?p=linux/kernel/git/viro/vfs-2.6.git;a=commit;h=2f3740b3a80bc19498b3ec9b86a25d5941545436
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
