From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 82201] ext4 crash in ext4_superblock_csum
Date: Wed, 13 Aug 2014 02:34:37 +0000 [thread overview]
Message-ID: <bug-82201-13602-fGaCCbqK4I@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82201-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82201
kun.chen <kun.chen@mediatek.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from kun.chen <kun.chen@mediatek.com> ---
I already checked that this is because ext4 super block memory was corrupted,
because we didn't set EXT4_FEATURE_RO_COMPAT_METADATA_CSUM, but it skip the
checking and enter ext4_superblock_csum.
ext4_super_block was stored in r1:c406d400, from stack the s_feature_ro_compat
value is c53e05e6, so it can skip the checking in ext4_superblock_csum_set.
And refer to r1 stack data, we already find it related to selinux.
"And did this happen after an unclean shutdown (so the journal had to be
replayed)"
Yes, it happened after a software watchdog reset. I'm not sure whether the
journal data corrupt related to memory corrupt, because next reboot it can
mount successful.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-13 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 5:19 [Bug 82201] New: ext4 crash in ext4_superblock_csum bugzilla-daemon
2014-08-12 15:25 ` [Bug 82201] " bugzilla-daemon
2014-08-13 2:34 ` bugzilla-daemon [this message]
2014-10-12 11:27 ` bugzilla-daemon
2014-10-12 12:03 ` bugzilla-daemon
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=bug-82201-13602-fGaCCbqK4I@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).