linux-kernel - Re: linux-next: Tree for January 15 (Call Trace in fs/dcache.c + autofs4)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 15 Jan 2011 12:16:29 +0100
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	Al Viro <viro@...iv.linux.org.uk>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: linux-next: Tree for January 15 (Call Trace in fs/dcache.c + autofs4)

On Sat, Jan 15, 2011 at 12:08 PM, Al Viro <viro@...iv.linux.org.uk> 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-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/