[Bugme-new] [Bug 11252] New: Kernel BUG on unmounting an intentionally corrupted filesystem

[bugme-daemon at bugzilla.kernel.org]

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

           Summary: Kernel BUG on unmounting an intentionally corrupted
                    filesystem
           Product: File System
           Version: 2.5
     KernelVersion: 2.6.27-rc1 (+ patch to fix #10976, now in -mm)
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4 at kernel-bugs.osdl.org
        ReportedBy: sliedes at cc.hut.fi


Latest working kernel version:
Earliest failing kernel version:
Distribution: Minimal Debian sid (unstable)
Hardware Environment: qemu x86
Software Environment:
Problem Description:

When unmounting the attached filesystem image after some use (it's actually a
corrupted ext3 image, but it's detected and mounted as ext4), a kernel bug
happens.

This seems somewhat similar to #11250, but the backtrace is entirely different
and it requires some different use before umount to break, so I'm filing a
separate bug.

Steps to reproduce:

1. bunzip2 the attached filesystem image
2. mount hdb.4000377 /mnt
[the image is mounted as ext4]
3. cd /mnt
4. cp -R doc doc2 >&/dev/null
5. press ctrl-C to kill the cp process once you no longer get kernel output
(which is almost immediately)
6. find -xdev >&/dev/null
7. find -xdev -print0 2>/dev/null |xargs -0 touch -- 2>/dev/null
8. mkdir tmp >&/dev/null
9. echo whoah >tmp/filu 2>/dev/null
10. rm -rf /mnt/* >&/dev/null
11. cd /
12. umount mnt
13. (boom)


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.