linux-ext4 - [Bug 14094] New: Ext4 NULL pointer reference in mb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <bug-14094-13602@http.bugzilla.kernel.org/>
Date:	Mon, 31 Aug 2009 09:24:39 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 14094] New: Ext4 NULL pointer reference in mb_cache function

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@...nel-bugs.osdl.org
        ReportedBy: suokkos@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html