linux-ext4 - [Bug 12272] New: at random rmmod/insmod corrupts filesystem

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 22 Dec 2008 06:01:40 -0800 (PST)
From:	bugme-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 12272] New: at random rmmod/insmod corrupts filesystem

http://bugzilla.kernel.org/show_bug.cgi?id=12272

           Summary: at random rmmod/insmod corrupts filesystem
           Product: File System
           Version: 2.5
     KernelVersion: 2.6.26 and 2.6.27
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
        AssignedTo: fs_ext3@...nel-bugs.osdl.org
        ReportedBy: folkert@...heusden.com


Latest working kernel version: 2.6.18
Earliest failing kernel version: 2.6.26
Distribution: Debian
Hardware Environment: P4 (with HT), IDE disk (PATA), 512MB ram
Software Environment: http://vanheusden.com/pyk/
Problem Description: filesystem corrupted:
[85202.195563] rtc0: alarms up to one month, y3k, hpet irqs
[85204.035802] journal_bmap: journal block not found at offset 2060 on dm-0
[85204.035818] Aborting journal on device dm-0.
[85311.242093] ext3_abort called.
[85311.242120] EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected
aborted journal
[85311.242154] Remounting filesystem read-only
[86331.285847] EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry
in directory #24568: rec_len % 4 != 0 - offset=0, inode=4098364138,
rec_len=59542, name_len=76
[89931.353863] EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry
in directory #24568: rec_len % 4 != 0 - offset=0, inode=4098364138,
rec_len=59542, name_len=76

[92499.263276] attempt to access beyond end of device
[92499.263296] dm-2: rw=17, want=4177066240, limit=6004736
[92499.263311] Buffer I/O error on device dm-2, logical block 522133279
[92499.263333] lost page write due to I/O error on dm-2
[92499.263341] Aborting journal on device dm-2.
[92499.263504] ext3_abort called.
[92499.263515] EXT3-fs error (device dm-2): ext3_journal_start_sb: Detected
aborted journal
[92499.263543] Remounting filesystem read-only

[93531.419902] EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry
in directory #24568: rec_len % 4 != 0 - offset=0, inode=4098364138,
rec_len=59542, name_len=76

Steps to reproduce: run pyk script and run something like a git clone of the
mainline kernel git tree, rm -rf the tree, touch /forcefsk, reboot


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
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