From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 20992] New: Data corruption triggers ext4 oops
Date: Sat, 23 Oct 2010 14:39:02 GMT [thread overview]
Message-ID: <bug-20992-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=20992
Summary: Data corruption triggers ext4 oops
Product: File System
Version: 2.5
Kernel Version: 2.6.35.7
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: bart.vanassche@gmail.com
Regression: No
While running I/O performance tests I accidentally overwrote an ext4
filesystem. The next access of that filesystem triggered a kernel oops. I don't
think that should happen ?
--
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 reply other threads:[~2010-10-23 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 14:39 bugzilla-daemon [this message]
2010-10-23 14:56 ` [Bug 20992] Data corruption triggers ext4 oops bugzilla-daemon
2010-10-23 14:58 ` bugzilla-daemon
2010-10-23 15:20 ` bugzilla-daemon
2010-10-23 15:27 ` bugzilla-daemon
2013-12-10 22:22 ` 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-20992-13602@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).