From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Roberto Oppedisano <roberto.oppedisano@infracom.it>
Cc: LKML <linux-kernel@vger.kernel.org>,
tytso@mit.edu, adilger@sun.com, linux-ext4@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: kernel BUG at fs/ext4/inode.c:1184!
Date: Sat, 3 Oct 2009 13:15:15 +0200 [thread overview]
Message-ID: <20091003111515.GA2032@phenom2.trippelsdorf.de> (raw)
In-Reply-To: <4AC71ECC.2020104@infracom.it>
On Sat, Oct 03, 2009 at 11:52:12AM +0200, Roberto Oppedisano wrote:
> This is 100% reproducible on current git kernel.
> After hitting the BUG the machine is still alive, but some processes
> refuse to start and /bin/sync stalls forever.
> Last known good kernel is 2.6.32-rc2-00087-g9c1fe83.
>
> [ 74.971246] ------------[ cut here ]------------
> [ 74.971303] kernel BUG at fs/ext4/inode.c:1184!
This is already fixed, see:
http://marc.info/?l=linux-ext4&m=125437926005433&w=4
Unfortunately Linus has not pulled the fix yet.
--
Markus
next prev parent reply other threads:[~2009-10-03 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 9:52 kernel BUG at fs/ext4/inode.c:1184! Roberto Oppedisano
2009-10-03 11:15 ` Markus Trippelsdorf [this message]
2009-10-03 17:06 ` Roberto Oppedisano
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=20091003111515.GA2032@phenom2.trippelsdorf.de \
--to=markus@trippelsdorf.de \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roberto.oppedisano@infracom.it \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox