From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 14916] New: jnode_page(node) != NULL
Date: Mon, 28 Dec 2009 14:37:15 GMT [thread overview]
Message-ID: <bug-14916-695@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=14916
Summary: jnode_page(node) != NULL
Product: File System
Version: 2.5
Kernel Version: 2009-12-10-17-19
Platform: All
OS/Version: Linux
Tree: -mm
Status: NEW
Severity: normal
Priority: P1
Component: Reiser4
AssignedTo: reiserfs-devel@vger.kernel.org
ReportedBy: buchner.johannes@gmx.at
Regression: No
Using several hard resets, I ran into "jnode_page(node) != NULL" asserts
(causing kernel panics). These panics happen when some file is read (often a
GNOME file needed for startup).
"fsck.reiser4 --fix" was always able to fix it, but the fs shouldn't get into
such a state in the first place.
I'm afraid I don't have a way to reproduce.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
reply other threads:[~2009-12-28 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-14916-695@http.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=reiserfs-devel@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).