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 09:07:02 +0000 [thread overview]
Message-ID: <20110115090702.GK19804@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20110115075723.GJ19804@ZenIV.linux.org.uk>
On Sat, Jan 15, 2011 at 07:57:23AM +0000, Al Viro wrote:
> On Sat, Jan 15, 2011 at 08:46:20AM +0100, Sedat Dilek wrote:
>
> > Will try the patch from [1] as there was no feedback yet.
> >
> > - Sedat -
> >
> > [1] https://lkml.org/lkml/2011/1/12/394
>
> There's also vfsmount refcounting breakage somewhere in automount series,
> unfortunately caught only when redoing said refcounting on top of it [1] ;-/
> I'm bisecting it right now, will post when it's done.
>
> [1] with mnt{get,put}_long() variant the breakage is present, but not
> immediately noticable. With (local) rewrite to saner rules it became
> visible, but I spent quite a while trying to find the bug in the most
> obvious place - i.e. that rewrite.
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.
next prev parent reply other threads:[~2011-01-15 9:07 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 [this message]
2011-01-15 11:00 ` Sedat Dilek
2011-01-15 11:08 ` Al Viro
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=20110115090702.GK19804@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