linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Török Edwin" <edwintorok@gmail.com>
To: Norbert Preining <preining@logic.at>
Cc: Dave Jones <davej@redhat.com>, Eric Sandeen <sandeen@redhat.com>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: another ext3 kernel BUG
Date: Thu, 16 Jun 2011 10:02:57 +0300	[thread overview]
Message-ID: <4DF9AAA1.5030002@gmail.com> (raw)
In-Reply-To: <20110616055125.GB23083@gamma.logic.tuwien.ac.at>

On 06/16/2011 08:51 AM, Norbert Preining wrote:
> On Mi, 15 Jun 2011, Norbert Preining wrote:
>> CONFIG_LIST_DEBUG is compiled in.
>> vbox modules are *not* loaded
> 
> new instance, this time again in fs/inode.c, but coming from fsnotify,
> and one from ntfs3g.
> 
> When I go to 3.0-rc1 all is fine.
> 
> I will try to get a git bisect running, but that is a pain because
> it is not easy to trigger.
> 
> Any suggestion what could be the culprit? 3cebde241 ?

e6bc45d65df8599fdbae73be9cec4ceed274db53

See here for a patch:
https://lkml.org/lkml/2011/6/15/341

Does that help?

Best regards,
--Edwin

  reply	other threads:[~2011-06-16  7:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11  2:17 ext3 and btrfs various Oops and kernel BUGs Norbert Preining
2011-06-14  1:19 ` another ext3 kernel BUG Norbert Preining
2011-06-14  2:19   ` Eric Sandeen
2011-06-14  2:43     ` Norbert Preining
2011-06-14  3:21       ` Dave Jones
2011-06-14  3:32         ` Eric Sandeen
2011-06-14  4:03 ` Norbert Preining
2011-06-15  1:23   ` Norbert Preining
2011-06-15  8:09     ` Török Edwin
2011-06-15 21:06       ` [PATCH] fix wrong iput on d_inode introduced by e6bc45d65d Török Edwin
2011-06-16  5:51     ` another ext3 kernel BUG Norbert Preining
2011-06-16  7:02       ` Török Edwin [this message]
2011-06-16  8:28         ` Norbert Preining

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=4DF9AAA1.5030002@gmail.com \
    --to=edwintorok@gmail.com \
    --cc=davej@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preining@logic.at \
    --cc=sandeen@redhat.com \
    /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).