From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 45621] Kernel ooops: BUG: unable to handle kernel paging request at 000000080000001c
Date: Sun, 5 Aug 2012 22:36:15 +0000 (UTC) [thread overview]
Message-ID: <20120805223615.2F02611FC6B@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-45621-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=45621
--- Comment #4 from Theodore Tso <tytso@mit.edu> 2012-08-05 22:36:14 ---
Hi, I'm hoping this rings a bell with an mm developer:
https://bugzilla.kernel.org/show_bug.cgi?id=45621
It looks like the user is reporting a OOPS which was caused by the
inode's mapping->page_tree having gotten corrupted. The call stack
was from a write system call while the system was undergoing heavy
I/O, on a v3.4.7 kernel.
If someone could take a quick look at this, I'd really appreciate it.
Thanks!!
- Ted
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-08-05 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 23:33 [Bug 45621] New: Kernel ooops: BUG: unable to handle kernel paging request at 000000080000001c bugzilla-daemon
2012-08-04 23:45 ` [Bug 45621] " bugzilla-daemon
2012-08-05 22:12 ` bugzilla-daemon
2012-08-05 22:24 ` bugzilla-daemon
2012-08-05 22:36 ` bugzilla-daemon [this message]
2012-08-06 15:15 ` bugzilla-daemon
2012-08-06 22:14 ` bugzilla-daemon
2012-08-06 22:21 ` Gordan Bobic
2012-11-07 9:58 ` bugzilla-daemon
2012-11-07 12:42 ` bugzilla-daemon
2012-11-07 14:18 ` bugzilla-daemon
2013-11-19 23:43 ` 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=20120805223615.2F02611FC6B@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).