[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191029233401.GB8537@mit.edu>
Date: Tue, 29 Oct 2019 19:34:01 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: Matthew Bobrowski <mbobrowski@...browski.org>
Cc: jack@...e.cz, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org,
linux-fsdevel@...r.kernel.org, hch@...radead.org,
david@...morbit.com, darrick.wong@...cle.com
Subject: Re: [PATCH v6 00/11] ext4: port direct I/O to iomap infrastructure
On Tue, Oct 29, 2019 at 07:31:59PM -0400, Theodore Y. Ts'o wrote:
> Hi Matthew, it looks like there are a number of problems with this
> patch series when using the ext3 backwards compatibility mode (e.g.,
> no extents enabled).
>
> So the following configurations are failing:
>
> kvm-xfstests -c ext3 generic/091 generic/240 generic/263
Here are the details of the generic/240 failure:
root@...-xfstests:~# diff -u /root/xfstests/tests/generic/240.out /results/ext4/results-ext3/generic/240.out.bad
--- /root/xfstests/tests/generic/240.out 2019-10-21 15:29:56.000000000 -0400
+++ /results/ext4/results-ext3/generic/240.out.bad 2019-10-29 19:32:29.166850310 -0400
@@ -1,2 +1,7 @@
QA output created by 240
Silence is golden.
+AIO write offset 4608 expected 4096 got 512
+AIO write offset 8704 expected 4096 got 512
+non one buffer at buf[0] => 0x00,00,00,00
+non-one read at offset 12800
+*** WARNING *** /vdd/aiodio_sparse has not been unlinked; if you don't rm it manually first, it may influence the next run
- Ted
Powered by blists - more mailing lists