public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Zorro Lang <zlang@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] generic/095: update warning whitelist
Date: Wed, 3 Aug 2016 15:55:32 +0800	[thread overview]
Message-ID: <20160803075531.GI27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160803073918.GE16413@zlang.usersys.redhat.com>

On Wed, Aug 03, 2016 at 03:39:18PM +0800, Zorro Lang wrote:
> On Wed, Aug 03, 2016 at 09:23:05AM +1000, Dave Chinner wrote:
> > On Mon, Aug 01, 2016 at 11:02:56AM +0200, Christoph Hellwig wrote:
> > > The recent direct I/O path refactor changed the function name in the
> > > racing read case.  Update the test case to handle the new name in
> > > addition to the old one.
> > > 
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > > ---
> > >  tests/generic/095 | 6 ++++--
> > >  1 file changed, 4 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/tests/generic/095 b/tests/generic/095
> > > index c656ef1..4754992 100755
> > > --- a/tests/generic/095
> > > +++ b/tests/generic/095
> > > @@ -125,9 +125,11 @@ $FIO_PROG $fio_config >>$seqres.full 2>&1
> > >  filter_xfs_dmesg()
> > >  {
> > >  	local warn1="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_dio_aio_write.*"
> > > -	local warn2="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_read_iter.*"
> > > +	local warn2="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_dio_aio_read.*"
> > > +	local warn3="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_read_iter.*"
> > >  	sed -e "s#$warn1#Intentional warnings in xfs_file_dio_aio_write#" \
> > > -	    -e "s#$warn2#Intentional warnings in xfs_file_read_iter#"
> > > +	    -e "s#$warn2#Intentional warnings in xfs_file_dio_aio_read#" \
> > > +	    -e "s#$warn3#Intentional warnings in xfs_file_read_iter#"
> 
> Hi,
> 
> 1) xfs_file_dio_aio_read() was splited from xfs_file_read_iter() by
> below commit:
> 
>   bbc5a74 xfs: split xfs_file_read_iter into buffered and direct I/O helpers
> 
> 2) xfs_file_read_iter() came from xfs_file_aio_read() as below commit:
> 
>   b4f5d2c xfs: switch to ->read_iter()
> 
> Some Linux distro (e.g: RHEL-7) still use the old kernel with old function
> xfs_file_aio_read(), generic/095 always fails on it. So how about filter
> xfs_file_aio_read too?

I think you can just send another (follow-up) patch for review.

Eryu

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2016-08-03  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01  9:02 [PATCH] generic/095: update warning whitelist Christoph Hellwig
2016-08-02 23:23 ` Dave Chinner
2016-08-03  7:39   ` Zorro Lang
2016-08-03  7:55     ` 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=20160803075531.GI27776@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=xfs@oss.sgi.com \
    --cc=zlang@redhat.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