linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bug 193661] New: xattr  ext4_xattr_block_find, bad block on cleanly formatted ext4 partition
@ 2017-01-30 16:06 bugzilla-daemon
  2017-01-30 16:08 ` [Bug 193661] " bugzilla-daemon
                   ` (9 more replies)
  0 siblings, 10 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-01-30 16:06 UTC (permalink / raw)
  To: linux-ext4

https://bugzilla.kernel.org/show_bug.cgi?id=193661

            Bug ID: 193661
           Summary: xattr  ext4_xattr_block_find, bad block on cleanly
                    formatted ext4 partition
           Product: File System
           Version: 2.5
    Kernel Version: all versions tested, from 3.19 through to 4.10-rc6
          Hardware: i386
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: colin.king@canonical.com
        Regression: No

Reproducer:

Ran inside a 8 proc VM instance, i386 kernel, 4MB of memory with the stress-ng
xattr stress test on a cleanly formated ext4 partition (e.g. mkfs.ext4
/dev/vdb1):

using stress-ng - to build from source on ubuntu systems:
   git clone git://kernel.ubuntu.com/cking/stress-ng
   sudo apt-get build-dep stress-ng
   cd stress-ng
   make

test script to invoke the stressor, needs to be run as root:

#!/bin/bash -x
for i in $(seq 30)
do
        ./stress-ng/stress-ng --xattr 8 -t 10
        rc=$?
        if [ $rc -ne 0 ]; then
                exit 1
        fi
done

This will trigger errors such as:

EXT4-fs error (device vdb1): ext4_xattr_block_find:802: inode #131074: comm
stress-ng-xattr: bad block 532519

and more often than not one needs to fsck the partition.

I've tested this on mainline kernels from 3.19 through to 4.10-rc6 and I can
trigger this on these kernels only on i386 systems. I've tested other 32 bit
platforms (32 bit arm, raspberry pi 2) but can't trigger it.  I cannot trigger
this issue on amd64 builds of the same kernels in a VM.

I put some debug into ext4_xattr_block_set() at the /* update the inode. *
comment and the bug does not trip, so it seems that this reduces the risk of
teh race condition occurring.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread
end of thread, other threads:[~2017-02-28 14:01 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-01-30 16:06 [Bug 193661] New: xattr ext4_xattr_block_find, bad block on cleanly formatted ext4 partition bugzilla-daemon
2017-01-30 16:08 ` [Bug 193661] " bugzilla-daemon
2017-01-30 16:10 ` bugzilla-daemon
2017-01-30 16:24 ` bugzilla-daemon
2017-01-30 16:48 ` bugzilla-daemon
2017-01-30 16:50 ` bugzilla-daemon
2017-01-30 16:53 ` bugzilla-daemon
2017-01-30 16:55 ` bugzilla-daemon
2017-02-21 14:52 ` bugzilla-daemon
2017-02-22  0:24 ` bugzilla-daemon
2017-02-28 14:01 ` bugzilla-daemon

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).