linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Eryu Guan <eguan@redhat.com>
Cc: Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
	fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH] generic/285: Add more SEEK_HOLE tests
Date: Mon, 15 May 2017 14:31:26 +0200	[thread overview]
Message-ID: <20170515123126.GG16182@quack2.suse.cz> (raw)
In-Reply-To: <20170513172620.GR7250@eguan.usersys.redhat.com>

On Sun 14-05-17 01:26:21, Eryu Guan wrote:
> On Sat, May 13, 2017 at 09:06:57AM +1000, Dave Chinner wrote:
> > On Fri, May 12, 2017 at 04:04:43PM +0800, Eryu Guan wrote:
> > > On Thu, May 11, 2017 at 06:48:09PM +0200, Jan Kara wrote:
> > > > Add tests for bugs found in ext4 & xfs SEEK_HOLE implementations
> > > > fixed by following patches:
> > > > 
> > > > xfs: Fix missed holes in SEEK_HOLE implementation
> > > > ext4: Fix SEEK_HOLE
> > > > 
> > > > Signed-off-by: Jan Kara <jack@suse.cz>
> > > 
> > > This will cause ext4 and xfs start to fail with current linus tree and
> > > appear as a new regression. So we usually don't add new tests to
> > > existing cases.
> > > 
> > > But seek_sanity_test.c deals with different SEEK_DATA/HOLE implentations
> > > nicely, which would be a bit tricky to do in a new test by shell, and it
> > > has all the infrastructures for new tests like this. So I think I'd
> > > prefer merging this patch as is, and document the false regression alert
> > > in release announce email.
> > 
> > Make the new tests optional (i.e. on a cli switch) and add a new
> > xfstest that runs them? Old test remains unchanged, doesn't fail,
> > new test covers the new tests, will fail on old kernels (which is ok
> > for new tests).
> 
> Yeah, this should work and looks a better solution to me. This avoids
> regressing generic/285 again when adding another new test in future,
> future tests could just follow this path too. Thanks for the suggestion!
> 
> Jan, could you please update the patch and, as suggested by Dave, make
> it a new test? I can do it too if you like.

Yeah, Dave's idea looks good. I'll work on it and send an updated version.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2017-05-15 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 16:48 [PATCH] generic/285: Add more SEEK_HOLE tests Jan Kara
2017-05-12  8:04 ` Eryu Guan
2017-05-12  8:12   ` Jan Kara
2017-05-12 23:06   ` Dave Chinner
2017-05-13 17:26     ` Eryu Guan
2017-05-15 12:31       ` Jan Kara [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=20170515123126.GG16182@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=david@fromorbit.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@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 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).