From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 114301] jbd2_journal_write_revoke_records
Date: Sun, 13 Mar 2016 23:52:21 +0000 [thread overview]
Message-ID: <bug-114301-13602-tKGyUgEPiw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-114301-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=114301
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tytso@mit.edu
Resolution|--- |UNREPRODUCIBLE
--- Comment #2 from Theodore Tso <tytso@mit.edu> ---
This is a Red Hat Enterprise Linux kernel. As such, bugs should be reported
to Red Hat and Red Hat has the responsibility for fixing them.
If you have a reliable repro on a modern kernel (as opposed to a distribution
kernel customized to within an inch of its life and released six years ago),
please feel free to open a bug with the information on how to reproduce this on
a modern kernel.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-03-13 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 13:44 [Bug 114301] New: "Oops: Kernel access of bad area, sig: 11 [#1]" (check log for details) bugzilla-daemon
2016-03-10 13:47 ` [Bug 114301] jbd2_journal_write_revoke_records Oops: Kernel access of bad area bugzilla-daemon
2016-03-10 13:47 ` [Bug 114301] jbd2_journal_write_revoke_records bugzilla-daemon
2016-03-13 12:37 ` bugzilla-daemon
2016-03-13 19:35 ` bugzilla-daemon
2016-03-13 23:52 ` bugzilla-daemon [this message]
2016-03-14 3:24 ` bugzilla-daemon
2016-03-14 3:30 ` bugzilla-daemon
2016-03-30 9:19 ` 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-114301-13602-tKGyUgEPiw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.