From: Gao Xiang <hsiangkao@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH v3] xfs: add test for CVE-2020-12655
Date: Thu, 25 Jun 2020 11:15:17 +0800 [thread overview]
Message-ID: <20200625031517.GB6242@xiangao.remote.csb> (raw)
In-Reply-To: <20200624151851.GI7625@magnolia>
On Wed, Jun 24, 2020 at 08:18:54AM -0700, Darrick J. Wong wrote:
...
> > + $seqres.full 2>&1
>
> Just FYI we conventionally use:
>
> $XFS_IO_PROG -f -c 'pwrite 0 64k' $SCRATCH_MNT/test >> $seqres.full
>
> to create files in fstests with less typing, but no need to reroll this
> whole thing just for that.
Okay, hope Eryu could update this when applying.
(anyway I could resend quickly if needed...)
Thanks,
Gao Xiang
prev parent reply other threads:[~2020-06-25 3:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 13:44 [PATCH] xfs: add test for CVE-2020-12655 Gao Xiang
2020-06-23 2:04 ` [PATCH v2] " Gao Xiang
2020-06-23 15:23 ` Darrick J. Wong
2020-06-23 15:30 ` Gao Xiang
2020-06-24 1:06 ` [PATCH v3] " Gao Xiang
2020-06-24 15:18 ` Darrick J. Wong
2020-06-25 3:15 ` Gao Xiang [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=20200625031517.GB6242@xiangao.remote.csb \
--to=hsiangkao@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@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).