[Bug 13676] unmount after fsstress on a ramdisk causes orphan inode list corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |akpm@xxxxxxxxxxxxxxxxxxxx
          Component|ext3                        |Block Layer
         AssignedTo|fs_ext3@xxxxxxxxxxxxxxxxxxx |axboe@xxxxxxxxx
                   |g                           |
            Product|File System                 |IO/Storage
         Regression|No                          |Yes




--- Comment #1 from Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>  2009-06-29 18:47:49 ---
More likely to be a ramdisk bug.

<checks>

yup, according to Adrian's report, it happened after the introduction of brd.

<marks as regression, assigns to Nick>

hm, we don't have a category for ramdisk.  I'll make it IO/Storage, Block
layer.

-- 
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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux