On Fri, Feb 12, 2016 at 01:25:06PM -0500, Eric Whitney wrote:
> Commit 2bcba4781fa3 ("ext4: get rid of EXT4_GET_BLOCKS_NO_LOCK flag")
> can cause a kernel panic when xfstest generic/300 is run on a file
> system mounted with dioread_nolock. The panic is typically triggered
> from check_irqs_on() (fs/buffer.c: 1272), and happens because
> ext4_end_io_dio() is being called in an interrupt context rather than
> from a workqueue for AIO. This suggests that buffer_defer_completion
> may not be set properly when creating an unwritten extent for async
> direct I/O.
>
> Revert the locking changes until this problem can be resolved. Patch
> applied to 4.5-rc3 and tested with a full xfstest-bld auto group run.
>
> Signed-off-by: Eric Whitney <enwlinux@xxxxxxxxx>
Applied, thanks.
I was able to reliably reproduce the problem without this revert patch
using a 32-bit x86 kvm-xfstests test appliance:
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests/testing/root_fs.img.i386
Using the command: "kvm-xfstests -c dioread_nolock generic/300"
With this patch, the problem goes away, so reverting the patch is
clearly the right thing for now. There is something screwy going on,
since the original commit shouldn't have made a difference, but let's
revert it first, and figure it out when we have time to investigate
more deeply.
- Ted
--
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
