From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14094] New: Ext4 NULL pointer reference in mb_cache function
Date: Mon, 31 Aug 2009 09:24:39 GMT [thread overview]
Message-ID: <bug-14094-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=14094
Summary: Ext4 NULL pointer reference in mb_cache function
Product: File System
Version: 2.5
Kernel Version: 2.6.31-rc8
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: suokkos@gmail.com
Regression: No
Created an attachment (id=22922)
--> (http://bugzilla.kernel.org/attachment.cgi?id=22922)
lspci for hardware details.
How bug was caused?
I did run apt-get upgrade in background while starting up firefox and pidgin.
Now there went something wrong in ext4. So I don't know exactly how to
reproduce this.
Reproducing?
Only once just a few minutes ago.
Version where this was seen?
Vanilla kernel v2.6.31-rc7 just a commit before tagging rc8 with a via agp
driver bug patch.
User land is Ubuntu Karmic.
Disk file system was upgraded from ext3 partition.
Debug info?
Sorry. all was lost because file system crashed so I could write it locally or
upload anywhere. I did try to upload it using ssh but that killed my last
working console so I have to do forced shutdown.
So all you have now left is my bad memory that remembers back trace in ext4
mb_*cache*. Which then caused a lot of warnings about scheduling while atomic.
If I can reproduce this I will next time take a photo before trying anything
else.
I'm just about to upgrade to the latest code even tough list of changes don't
look like affecting this.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
reply other threads:[~2009-08-31 9:24 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-14094-13602@http.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.