From: Mariusz Bialonczyk <manio@skyboo.net>
To: Ted Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Strange bug
Date: Sat, 13 Nov 2010 23:58:57 +0100 [thread overview]
Message-ID: <4CDF1831.6070506@skyboo.net> (raw)
In-Reply-To: <20101113224236.GA18658@thunk.org>
On 11/13/2010 11:42 PM, Ted Ts'o wrote:
> On Sat, Nov 13, 2010 at 09:18:39AM +0000, Mariusz Bialonczyk wrote:
>> Hello
>> I'd like to share the bug report which i had on yesterday's git kernel.
>
> I'm pretty sure it's not "yesterday's" git kernel. At least, not as
> far as Linus's git tree is concerned. The "57" in your version number
> in your dmesg:
>
> 2.6.37-rc1-00057-gc3e1500-dirty
>
> ... is too small for Linus's git tree as of Friday, November 12th.
>
> I wasn't able to track down the git commit ID: c3e1500 so I'm guessing
> there are some commits from some other git tree involved.
Sorry - you're right about that, because i did:
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git v4l-dvb
cd v4l-dvb
git remote add linuxtv git://linuxtv.org/media_tree.git
git remote update
git checkout -b media-master remotes/linuxtv/staging/for_v2.6.38
... so it is not "pure" Linus's git tree
I'm sorry about misleading.
> However, looking at the BUG_ON which you reported:
>
>> Nov 12 23:19:34 draco kernel: [ 997.220452] kernel BUG at fs/ext4/page-io.c:146!
>
> I'm pretty sure it's a bug which is fixed as of v2.6.37-rc1-git6,
> specifically by commit id: f7ad6d2e9 (ext4: handle writeback of inodes
> which are being freed).
>
> Best regards,
>
> - Ted
good to know, that it is fixed now :)
Thank you
regards,
--
Mariusz Bialonczyk
jabber/e-mail: manio@skyboo.net
http://manio.skyboo.net
prev parent reply other threads:[~2010-11-13 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 9:18 Strange bug Mariusz Bialonczyk
2010-11-13 21:18 ` Eric Sandeen
2010-11-13 22:42 ` Ted Ts'o
2010-11-13 22:58 ` Mariusz Bialonczyk [this message]
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=4CDF1831.6070506@skyboo.net \
--to=manio@skyboo.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.