From: Eric Biggers <ebiggers@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: lkp@intel.com, Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, Jaegeuk Kim <jaegeuk@kernel.org>,
ltp@lists.linux.it
Subject: Re: [LTP] [f2fs] a1e09b03e6: ltp.ADSP024.fail
Date: Fri, 7 Jan 2022 14:49:02 -0800 [thread overview]
Message-ID: <YdjDXiXYjQMJnr/c@sol.localdomain> (raw)
In-Reply-To: <20211226132851.GC34518@xsang-OptiPlex-9020>
On Sun, Dec 26, 2021 at 09:28:52PM +0800, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: a1e09b03e6f5c1d713c88259909137c0fd264ede ("f2fs: use iomap for direct I/O")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> in testcase: ltp
> version: ltp-x86_64-14c1f76-1_20211221
> with following parameters:
>
> disk: 1HDD
> fs: f2fs
> test: ltp-aiodio.part2
> ucode: 0x21
>
This is caused by an f2fs bug where it exposes DIO-allocated blocks to users
before they have been initialized. This test actually fails both before and
after my commit "f2fs: use iomap for direct I/O". It is nondeterministic, which
is why it may have appeared to be a regression.
I'll start a separate discussion on linux-f2fs-devel about this, since this
thread has too many irrelevant mailing lists and this has been discussed before.
- Eric
prev parent reply other threads:[~2022-01-07 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 13:28 kernel test robot
2022-01-07 22:49 ` Eric Biggers [this message]
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=YdjDXiXYjQMJnr/c@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=ltp@lists.linux.it \
--cc=oliver.sang@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox