linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
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 12:23:57 +0100	[thread overview]
Message-ID: <AANLkTikkEFf4Ubp=joAHfbOF-OVbK3_npgnks494EfRh@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinXPgfkcLq6LsQ=dsFZgQK5JG4f4GQW92r95J5C@mail.gmail.com>

On Sat, Jan 15, 2011 at 12:16 PM, Sedat Dilek
<sedat.dilek@googlemail.com> wrote:
> On Sat, Jan 15, 2011 at 12:08 PM, Al Viro <viro@zeniv.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
>

OK, I will try with these two patches and report later.

- Sedat -

P.S.:

sd@tbox:~/src/linux-2.6/linux-2.6.37/debian/patches$ ls -l vfs-2.6-for-next/
insgesamt 28
-rw-r--r-- 1 sd sd  737 15. Jan 12:21
0001-mismerge-foldme-breakage-in-__do_follow_link.patch
-rw-r--r-- 1 sd sd 4446 15. Jan 12:21
0002-autofs4-Merge-the-remaining-dentry-ops-tables.patch
-rw-r--r-- 1 sd sd  201 15. Jan 12:21 diffstat
-rw-r--r-- 1 sd sd  232 15. Jan 12:21 Shortlog
-rw-r--r-- 1 sd sd 4417 15. Jan 12:21 vfs-2.6-for-next.patch

  reply	other threads:[~2011-01-15 11:23 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
2011-01-15 11:16           ` Sedat Dilek
2011-01-15 11:23             ` Sedat Dilek [this message]
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='AANLkTikkEFf4Ubp=joAHfbOF-OVbK3_npgnks494EfRh@mail.gmail.com' \
    --to=sedat.dilek@googlemail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).