All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2 1/2] fsstress: add splice support
Date: Fri, 11 Jan 2019 13:40:23 +0800	[thread overview]
Message-ID: <20190111054023.GD2713@desktop> (raw)
In-Reply-To: <20190111033117.GV30999@dhcp-12-149.nay.redhat.com>

On Fri, Jan 11, 2019 at 11:31:17AM +0800, Zorro Lang wrote:
> On Thu, Jan 10, 2019 at 10:01:13PM +0800, Eryu Guan wrote:
> > On Thu, Jan 10, 2019 at 04:25:15PM +0800, Zorro Lang wrote:
> > > Support the splice syscall in fsstress.
> > > 
> > > Signed-off-by: Zorro Lang <zlang@redhat.com>
> > > ---
> > > 

<snap>

> > > +	if (ret1 < 0 || ret2 < 0)
> > > +		e = errno;
> > > +	else
> > > +		e = 0;
> > > +	if (v1 || v2) {
> > > +		printf("%d/%d: splice %s%s [%lld,%lld] -> %s%s [%lld,%lld]",
> > 
> > Better to print out error number on success (0) too, to be consistent
> > with other operations.
> 
> Hmm... it's not consistent for all, likes clonerange_f, copyrange_f and
> deduperange_f don't print out error number on success (0), do you need I change
> them to keep consistent too, as you're asking for that now?

That'd be great (but we can do that in a separate patch)! I think it's
easier to parse fsstress log when tracing down bugs if the log follows
similar formats.

Thanks,
Eryu

      reply	other threads:[~2019-01-11  5:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10  8:25 [PATCH v2 1/2] fsstress: add splice support Zorro Lang
2019-01-10  8:25 ` [PATCH v2 2/2] xfs/068: new fsstress operation breaks xfsrestore output Zorro Lang
2019-01-10 14:01 ` [PATCH v2 1/2] fsstress: add splice support Eryu Guan
2019-01-11  3:31   ` Zorro Lang
2019-01-11  5:40     ` 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=20190111054023.GD2713@desktop \
    --to=guaneryu@gmail.com \
    --cc=fstests@vger.kernel.org \
    --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 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.