All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Eryu Guan <eguan@redhat.com>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
Date: Tue, 31 May 2016 11:40:17 -0400	[thread overview]
Message-ID: <20160531154017.GC5357@thunk.org> (raw)
In-Reply-To: <20160531140922.GM5140@eguan.usersys.redhat.com>

On Tue, May 31, 2016 at 10:09:22PM +0800, Eryu Guan wrote:
> 
> I noticed that generic/130 hangs starting from 4.7-rc1 kernel, on non-4k
> block size ext4 (x86_64 host). And I bisected to commit 06bd3c36a733
> ("ext4: fix data exposure after a crash").
> 
> It's the sub-test "Small Vector Sync" in generic/130 hangs the kernel,
> and I can reproduce it on different hosts, both bare metal and kvm
> guest.

Hmm, it's not reproducing for me, either using your simplified repro
or generic/130.  Is there something specific with your kernel config,
which is needed for the reproduction, perhaps?

						- Ted

FSTESTVER: e2fsprogs	v1.43-25-ge2406b9 (Wed, 25 May 2016 00:30:42 -0400)
FSTESTVER: fio		fio-2.6-8-ge6989e1 (Thu, 4 Feb 2016 12:09:48 -0700)
FSTESTVER: quota		67fd9cc (Mon, 4 Apr 2016 00:32:39 -0400)
FSTESTVER: xfsprogs	v4.3.0 (Mon, 23 Nov 2015 15:24:24 +1100)
FSTESTVER: xfstests-bld	ccae8d1 (Tue, 26 Apr 2016 00:42:18 -0400)
FSTESTVER: xfstests	linux-v3.8-1036-gd22e675 (Wed, 25 May 2016 00:58:35 -0400)
FSTESTVER: kernel	4.7.0-rc1-ext4 #293 SMP Tue May 31 11:31:24 EDT 2016 x86_64
FSTESTCFG: "1k"
FSTESTSET: "generic/130"
FSTESTEXC: ""
FSTESTOPT: "aex"
MNTOPTS: ""
CPUS: "2"
MEM: "2007.43"
             total       used       free     shared    buffers     cached
Mem:          2007         93       1913          9          3         29
-/+ buffers/cache:         60       1946
Swap:            0          0          0
BEGIN TEST 1k: Ext4 1k block Tue May 31 11:33:55 EDT 2016
DEVICE: /dev/vdd
MK2FS OPTIONS: -q -b 1024
MOUNT OPTIONS: -o block_validity
FSTYP         -- ext4
PLATFORM      -- Linux/x86_64 kvm-xfstests 4.7.0-rc1-ext4
MKFS_OPTIONS  -- -q -b 1024 /dev/vdc
MOUNT_OPTIONS -- -o acl,user_xattr -o block_validity /dev/vdc /vdc

generic/130		[11:33:55]run fstests generic/130 at 2016-05-31 11:33:55
 [11:33:59] 4s
Ran: generic/130
Passed all 1 tests

             total       used       free     shared    buffers     cached
Mem:          2007         71       1936          9          0         16
-/+ buffers/cache:         53       1953
Swap:            0          0          0
END TEST: Ext4 1k block Tue May 31 11:33:59 EDT 2016
reboot: Power down

  reply	other threads:[~2016-05-31 15:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 14:09 xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel Eryu Guan
2016-05-31 15:40 ` Theodore Ts'o [this message]
2016-06-01  6:38   ` Eryu Guan
2016-06-01 13:53     ` Theodore Ts'o
2016-06-01 16:58     ` Eryu Guan
2016-06-02  8:58       ` Jan Kara
2016-06-02 12:17         ` Jan Kara
2016-06-02 12:30           ` Nikola Pajkovsky
2016-06-03 10:16           ` Eryu Guan
2016-06-03 11:58             ` Jan Kara
2016-06-08 12:56               ` Jan Kara
2016-06-08 14:23                 ` Holger Hoffstätte
2016-06-09  7:23                   ` Nikola Pajkovsky
2016-06-09 15:04                     ` Jan Kara
2016-06-10  5:52                       ` Nikola Pajkovsky
2016-06-16 13:26                         ` Jan Kara
2016-06-16 14:42                           ` Nikola Pajkovsky
2016-06-20 11:39                             ` Jan Kara
2016-06-20 12:59                               ` Nikola Pajkovsky
2016-06-21 10:11                                 ` Jan Kara
2016-06-22  8:55                                   ` Nikola Pajkovsky
2016-06-09 14:59                   ` Jan Kara
2016-06-10  8:37                 ` Eryu Guan
2016-06-12  3:28                   ` Eryu Guan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160531154017.GC5357@thunk.org \
    --to=tytso@mit.edu \
    --cc=eguan@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.