From: "Sang, Oliver" <oliver.sang@intel.com>
To: "dsterba@suse.cz" <dsterba@suse.cz>
Cc: Goldwyn Rodrigues <rgoldwyn@suse.com>,
David Sterba <dsterba@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
"lkp@lists.01.org" <lkp@lists.01.org>, lkp <lkp@intel.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: RE: [btrfs] c0aaf9b7a1: ltp: stuck at diotest4
Date: Thu, 3 Sep 2020 13:29:57 +0000 [thread overview]
Message-ID: <06668b52b9ac4d4e81f945e06223d9b7@intel.com> (raw)
In-Reply-To: <20200903091123.GO28318@suse.cz>
> -----Original Message-----
> From: David Sterba <dsterba@suse.cz>
> Sent: Thursday, September 3, 2020 5:11 PM
> To: Sang, Oliver <oliver.sang@intel.com>
> Cc: Goldwyn Rodrigues <rgoldwyn@suse.com>; David Sterba
> <dsterba@suse.com>; LKML <linux-kernel@vger.kernel.org>; lkp@lists.01.org;
> lkp <lkp@intel.com>; ltp@lists.linux.it; linux-btrfs@vger.kernel.org
> Subject: Re: [btrfs] c0aaf9b7a1: ltp: stuck at diotest4
>
> On Thu, Sep 03, 2020 at 02:28:37PM +0800, kernel test robot wrote:
> > Greeting,
> >
> > FYI, we noticed the following commit (built with gcc-9):
> >
> > commit: c0aaf9b7a114f6b75e0da97be7d99c102347a751 ("btrfs: switch to
> > iomap_dio_rw() for dio")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git
> > master
>
> That's probably the O_DIRECT + O_(D)SYNC deadlock that was found recently.
> One of the cases in diotest4 does
>
> open(filename, O_DIRECT | O_RDWR | O_SYNC)
>
> Fix is work in progress, thanks for the report.
Thanks a lot for information!
prev parent reply other threads:[~2020-09-03 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200903062837.GA3654@xsang-OptiPlex-9020>
2020-09-03 9:11 ` [btrfs] c0aaf9b7a1: ltp: stuck at diotest4 David Sterba
2020-09-03 13:29 ` Sang, Oliver [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=06668b52b9ac4d4e81f945e06223d9b7@intel.com \
--to=oliver.sang@intel.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=ltp@lists.linux.it \
--cc=rgoldwyn@suse.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;
as well as URLs for NNTP newsgroup(s).