public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: fstests@vger.kernel.org
Cc: david@fromorbit.com, djwong@kernel.org
Subject: [PATCH v2 0/2] xfstests: hexdump and CVE-2022-0847
Date: Wed, 23 Mar 2022 02:29:24 +0800	[thread overview]
Message-ID: <20220322182926.1829846-1-zlang@redhat.com> (raw)

Thanks review points from Dave and Darrick. This patchset contains 2 patches:
[PATCH v2 1/2] xfstests: replace hexdump with od command
[PATCH v2 2/2] fstests: test dirty pipe vulnerability issue of CVE-2022-0847

[v2 1/2] did below changes:
1) Change g/404, remove od/hexdump command, generate md5 directly
2) Change g/042, remove -v option of od/hexdump
3) As Dave has given this V1 patch a "reviewed-by", so add it

[v2 2/2] did below changes:
1) remove _cleanup(), turn to use default _cleanup function
2) add "rm -f $localfile" before testing start

Thanks,
Zorro


== Messages from original V1 patch ==
I've sent the V2 [2/2] last week[1], but due to the [2/2] hasn't been merged
and the [1/2] will affect [2/2]. So I send these two patches in one patchset
this time. Just please note, the [2/2] is the last version.

[1]
https://lore.kernel.org/fstests/20220320123932.1000005-1-zlang@redhat.com/


             reply	other threads:[~2022-03-22 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 18:29 Zorro Lang [this message]
2022-03-22 18:29 ` [PATCH v2 1/2] xfstests: replace hexdump with od command Zorro Lang
2022-04-10 15:13   ` Eryu Guan
2022-04-10 17:19     ` Zorro Lang
2022-03-22 18:29 ` [PATCH v2 2/2] fstests: test dirty pipe vulnerability issue of CVE-2022-0847 Zorro Lang
2022-03-22 21:27   ` Darrick J. Wong
2022-03-22 23:18   ` Dave Chinner

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=20220322182926.1829846-1-zlang@redhat.com \
    --to=zlang@redhat.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --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