fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hou Tao <houtao1@huawei.com>
To: <guaneryu@gmail.com>, Richard Weinberger <richard@nod.at>
Cc: <fstests@vger.kernel.org>, <houtao1@huawei.com>
Subject: [PATCH 0/2] add tests for race between xattr read and write
Date: Fri, 17 Jul 2020 16:44:45 +0800	[thread overview]
Message-ID: <20200717084447.66402-1-houtao1@huawei.com> (raw)

Hi,

These two test cases are reproducers for xattr bugs [1] on ubifs.
Although these bugs are ubifs specific, I still place these test cases
under generic directory, because we can ensure other filesystems implement
concurrent xattr read and write op correctly.

Comments are welcome.

Regards,
Tao

[1]: https://lore.kernel.org/linux-mtd/20200630130438.141649-1-houtao1@huawei.com/

Hou Tao (2):
  generic: add test for race between listxattr and setxatr
  generic: add test for race between getxattr and setxattr

 tests/generic/998     | 64 ++++++++++++++++++++++++++++++++++++++++
 tests/generic/998.out |  2 ++
 tests/generic/999     | 68 +++++++++++++++++++++++++++++++++++++++++++
 tests/generic/999.out |  2 ++
 tests/generic/group   |  2 ++
 5 files changed, 138 insertions(+)
 create mode 100644 tests/generic/998
 create mode 100644 tests/generic/998.out
 create mode 100644 tests/generic/999
 create mode 100644 tests/generic/999.out

-- 
2.25.0.4.g0ad7144999


             reply	other threads:[~2020-07-17  8:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  8:44 Hou Tao [this message]
2020-07-17  8:44 ` [PATCH 1/2] generic: add test for race between listxattr and setxatr Hou Tao
2020-07-20  3:40   ` Chao Yu
2020-08-22 11:41     ` [PATCH v2 " Hou Tao
2020-08-30 16:23       ` Eryu Guan
2020-08-31  1:19         ` Chao Yu
2020-08-31  3:01         ` Hou Tao
2020-09-02 15:48           ` Eryu Guan
2020-09-02 16:43       ` Darrick J. Wong
2020-07-17  8:44 ` [PATCH 2/2] generic: add test for race between getxattr and setxattr Hou Tao

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=20200717084447.66402-1-houtao1@huawei.com \
    --to=houtao1@huawei.com \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.com \
    --cc=richard@nod.at \
    /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).