public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>,
	Christoph Hellwig <hch@lst.de>,
	"Darrick J . Wong" <darrick.wong@oracle.com>,
	fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] fstests: run xfs_io as multi threaded for 'quick' tests
Date: Fri, 21 Oct 2016 23:24:08 +0800	[thread overview]
Message-ID: <20161021152408.GO27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAOQ4uxhXEkaQLfzNV-oTaOa-p-w6UQgbNXuNGcq1LGkVq48vdQ@mail.gmail.com>

On Thu, Oct 20, 2016 at 09:27:03PM +0300, Amir Goldstein wrote:
> On Thu, Oct 20, 2016 at 5:25 PM, Eryu Guan <eguan@redhat.com> wrote:
> > On Mon, Oct 17, 2016 at 10:01:19AM +0300, Amir Goldstein wrote:
> 
> ...
> 
> >
> > I'm still having concerns about losing test coverage by enabling "-i" by
> > default. How about adding an command line option to disable it?
> 
> I could take the easy way and add a command line option to satisfy
> concerns, but we all know that 99% of the time, nobody is going to use it,
> so we will be just silencing out concerns instead of addressing them.
> 
> > So at
> > least we could have a way to turn it off. Or is it completely impossible
> > to lose any test coverage?
> 
> I would not argue that it is completely impossible to loose test coverage
> but I would argue that there is low probability of loosing *interesting* test
> coverage.
> 
> Here is the argument I am making:
> A file reference leak can be anywhere, (e.g in EXDEV error path of clone
> file range ioctl) so we SHOULD have -i test coverage for as many APIs
> as possible with as many arguments as possible.
> OTOH, the difference between slowpath and fastpath of fdget()/fdput()
> for single/multi threaded process is quite invariant to the specific API,
> so I do not see the value in test coverage of fastpath to all APIs.

Then I'll take it as it is, and we can always add a new option to turn
it off when we find it necessary :) Thanks!

Eryu

      reply	other threads:[~2016-10-21 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16 10:53 [PATCH v2 1/3] fstests: fix call sites that used xfs_io directly Amir Goldstein
2016-10-16 10:53 ` [PATCH v2 2/3] fstests: strip quotes from "$XFS_IO_PROG" call sites Amir Goldstein
2016-10-16 10:53 ` [PATCH v2 3/3] fstests: run xfs_io as multi threaded for 'quick' tests Amir Goldstein
2016-10-16 21:46   ` Dave Chinner
2016-10-17  7:01     ` Amir Goldstein
2016-10-17 21:49       ` Amir Goldstein
2016-10-20 14:25       ` Eryu Guan
2016-10-20 18:27         ` Amir Goldstein
2016-10-21 15:24           ` 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=20161021152408.GO27776@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    /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