From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>,
linux-ext4@vger.kernel.org
Subject: Re: OOPs in ext4
Date: Wed, 21 May 2014 10:53:15 -0400 [thread overview]
Message-ID: <20140521145315.GA8868@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1405211506190.2114@localhost.localdomain>
On Wed, May 21, 2014 at 03:20:20PM +0200, Lukáš Czerner wrote:
>
> yes there is definitely a bug in the error handling code because we
> really should not hit that BUG_ON() later.
The bug in the error handling code is fixed in commit 66a4cb187, which
will be in 3.15. I should have split apart the bug fix from the
general cleanup, to make it easier to backport to older kernels. At
the time, I didn't realize that the bug was getting hit so often.
> However I am curious how we got this state in the first place. Can
> you provide the logs before the first oops ? Are there any more
> warnings ?
Also, after the system rebooted, what messages if any did e2fsck
report?
Thanks,
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-21 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 10:29 OOPs in ext4 Arturo Borrero Gonzalez
2014-05-21 13:20 ` Lukáš Czerner
2014-05-21 14:33 ` Arturo Borrero Gonzalez
2014-05-21 14:53 ` Theodore Ts'o [this message]
2014-05-21 15:06 ` Arturo Borrero Gonzalez
2014-05-21 15:12 ` Lukáš Czerner
2014-05-21 15:14 ` Arturo Borrero Gonzalez
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=20140521145315.GA8868@thunk.org \
--to=tytso@mit.edu \
--cc=arturo.borrero.glez@gmail.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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