All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
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: Wed, 8 Mar 2017 11:29:56 +0800	[thread overview]
Message-ID: <20170308032956.GX14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1488922559.3877.6.camel@redhat.com>

Hi Jeff,

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.
> 
> [  591.302422] run fstests generic/095 at 2017-03-07 15:38:32
> [  591.452226] XFS (vda6): Unmounting Filesystem
> [  591.825895] XFS (vda6): Mounting V5 Filesystem
> [  591.841560] XFS (vda6): Ending clean mount
> [  592.127155] ------------[ cut here ]------------
> [  592.133775] WARNING: CPU: 2 PID: 20539 at fs/iomap.c:954 iomap_dio_rw+0x39a/0x3b0

and

> [  592.202828] WARNING: CPU: 0 PID: 20540 at fs/iomap.c:896 iomap_dio_rw+0x1b1/0x3b0

IIRC, these warnings are kind of "known issue", they're filtered out by
generic/095 and should not cause the test to fail. You can check the
comments before filter_xfs_dmesg() function in generic/095 test.

Did generic/095 fail for you due to dmesg check? If so I think there
might be an fstests bug. My generic/095 run on 4.11-rc1 kernel triggered
these warnings too, but test itself didn't report failure.

Thanks,
Eryu

      parent reply	other threads:[~2017-03-08  5:57 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
2017-03-07 22:09   ` Christoph Hellwig
2017-03-08 12:35   ` Jeff Layton
2017-03-08  3:29 ` Eryu Guan [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=20170308032956.GX14226@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --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.