From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: WARNING: CPU: 2 PID: 20539 at fs/iomap.c:954 iomap_dio_rw+0x39a/0x3b0
Date: Tue, 7 Mar 2017 14:09:11 -0800 [thread overview]
Message-ID: <20170307220911.GA25288@infradead.org> (raw)
In-Reply-To: <1488922559.3877.6.camel@redhat.com>
On Tue, Mar 07, 2017 at 04:35:59PM -0500, Jeff Layton wrote:
> I was doing an xfstests run on xfs with v4.11.0-rc1, and these two
> warnings popped.�Looks like invalidate_inode_pages2_range failed? A
> small patch to print the error there showed that it was returning
> -EBUSY.
>
> Pretty easy to reproduce by running xfstests generic/095 on a KVM guest
> running v4.11.0-rc1.
Can you try:
"[PATCH v2] iomap: invalidate page caches should be after iomap_dio_complete() in direct write"
which was sent to the XFS list last week and check if it fixes things
for you?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: WARNING: CPU: 2 PID: 20539 at fs/iomap.c:954 iomap_dio_rw+0x39a/0x3b0
Date: Tue, 7 Mar 2017 14:09:11 -0800 [thread overview]
Message-ID: <20170307220911.GA25288@infradead.org> (raw)
In-Reply-To: <1488922559.3877.6.camel@redhat.com>
On Tue, Mar 07, 2017 at 04:35:59PM -0500, Jeff Layton wrote:
> I was doing an xfstests run on xfs with v4.11.0-rc1, and these two
> warnings popped. Looks like invalidate_inode_pages2_range failed? A
> small patch to print the error there showed that it was returning
> -EBUSY.
>
> Pretty easy to reproduce by running xfstests generic/095 on a KVM guest
> running v4.11.0-rc1.
Can you try:
"[PATCH v2] iomap: invalidate page caches should be after iomap_dio_complete() in direct write"
which was sent to the XFS list last week and check if it fixes things
for you?
next prev parent reply other threads:[~2017-03-07 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 21:35 WARNING: CPU: 2 PID: 20539 at fs/iomap.c:954 iomap_dio_rw+0x39a/0x3b0 Jeff Layton
2017-03-07 22:09 ` Christoph Hellwig [this message]
2017-03-07 22:09 ` Christoph Hellwig
2017-03-08 12:35 ` Jeff Layton
2017-03-08 3:29 ` 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=20170307220911.GA25288@infradead.org \
--to=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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.