Bug 14094 - Ext4 NULL pointer reference in mb_cache function
Summary: Ext4 NULL pointer reference in mb_cache function
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: File System
Classification: Unclassified
Component: ext4 (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: fs_ext4@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-31 09:24 UTC by Pauli
Modified: 2012-06-13 16:12 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.31-rc8
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lspci for hardware details. (11.59 KB, text/plain)
2009-08-31 09:24 UTC, Pauli
Details

Description Pauli 2009-08-31 09:24:38 UTC
Created attachment 22922 [details]
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.

Note You need to log in before you can comment on or make changes to this bug.