From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 43023] Bad page map in process plugin-containe
Date: Mon, 2 Apr 2012 18:54:29 GMT [thread overview]
Message-ID: <201204021854.q32IsTms027453@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-43023-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=43023
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
Component|ext4 |Other
AssignedTo|fs_ext4@kernel-bugs.osdl.or |akpm@linux-foundation.org
|g |
Product|File System |Memory Management
--- Comment #1 from Theodore Tso <tytso@mit.edu> 2012-04-02 18:54:27 ---
This looks like a VM problem (a corrupted page table entry), not an ext4 file
system issue.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
prev parent reply other threads:[~2012-04-02 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 19:06 [Bug 43023] New: Bad page map in process plugin-containe bugzilla-daemon
2012-04-02 18:54 ` bugzilla-daemon [this message]
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=201204021854.q32IsTms027453@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).