[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-82201-13602-fGaCCbqK4I@https.bugzilla.kernel.org/>
Date: Wed, 13 Aug 2014 02:34:37 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 82201] ext4 crash in ext4_superblock_csum
https://bugzilla.kernel.org/show_bug.cgi?id=82201
kun.chen <kun.chen@...iatek.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from kun.chen <kun.chen@...iatek.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists