From: Al Viro <viro@ZenIV•linux.org.uk>
To: sedat.dilek@gmail•com
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
linux-fsdevel <linux-fsdevel@vger•kernel.org>
Subject: Re: linux-next: Tree for January 15 (Call Trace in fs/dcache.c + autofs4)
Date: Sat, 15 Jan 2011 11:08:48 +0000 [thread overview]
Message-ID: <20110115110848.GL19804@ZenIV.linux.org.uk> (raw)
In-Reply-To: <AANLkTinPs5toSudLXuu3=a0RoGHUqYvF8YyhdrXgckXY@mail.gmail.com>
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.
next prev parent reply other threads:[~2011-01-15 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 7:39 linux-next: Tree for January 15 (Call Trace in fs/dcache.c + autofs4) Sedat Dilek
2011-01-15 7:46 ` Sedat Dilek
2011-01-15 7:57 ` Al Viro
2011-01-15 8:10 ` Sedat Dilek
2011-01-15 9:07 ` Al Viro
2011-01-15 11:00 ` Sedat Dilek
2011-01-15 11:08 ` Al Viro [this message]
2011-01-15 11:16 ` Sedat Dilek
2011-01-15 11:23 ` Sedat Dilek
2011-01-15 11:34 ` Al Viro
2011-01-15 11:44 ` Sedat Dilek
2011-01-15 13:50 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110115110848.GL19804@ZenIV.linux.org.uk \
--to=viro@zeniv$(echo .)linux.org.uk \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sedat.dilek@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox