From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Joel Becker <jlbec@evilplan.org>,
linux-kernel@vger.kernel.org,
Bodo Stroesser <bostroesser@gmail.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Brendan Higgins <brendanhiggins@google.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v3 0/3] Restore the kernel v5.13 text attribute write behavior
Date: Thu, 29 Jul 2021 20:35:01 -0700 [thread overview]
Message-ID: <20210730033504.8228-1-bvanassche@acm.org> (raw)
Hi Christoph,
This patch series restores the v5.13 text attribute write behavior and also
adds unit tests for configfs. Please consider these patches for inclusion in
the Linux kernel.
Thanks,
Bart.
Changes compared to v2:
- Modified description of patch 2/3.
Changes compared to v1:
- Instead of making the text attribute write behavior POSIX compliant, restore
the v5.13 behavior.
- Added more unit tests.
Bart Van Assche (3):
configfs: Restore the kernel v5.13 text attribute write behavior
kunit: Add support for suite initialization and cleanup
configfs: Add unit tests
fs/configfs/Kconfig | 8 +
fs/configfs/Makefile | 2 +
fs/configfs/configfs-test.c | 427 ++++++++++++++++++++++++++++++++++++
fs/configfs/file.c | 18 +-
include/kunit/test.h | 4 +
lib/kunit/test.c | 14 ++
6 files changed, 461 insertions(+), 12 deletions(-)
create mode 100644 fs/configfs/configfs-test.c
next reply other threads:[~2021-07-30 3:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 3:35 Bart Van Assche [this message]
2021-07-30 3:35 ` [PATCH v3 1/3] configfs: Restore the kernel v5.13 text attribute write behavior Bart Van Assche
2021-07-30 3:35 ` [PATCH v3 2/3] kunit: Add support for suite initialization and cleanup Bart Van Assche
2021-07-30 3:35 ` [PATCH v3 3/3] configfs: Add unit tests Bart Van Assche
2021-07-30 16:09 ` [PATCH v3 0/3] Restore the kernel v5.13 text attribute write behavior Bart Van Assche
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=20210730033504.8228-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=bostroesser@gmail.com \
--cc=brendanhiggins@google.com \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.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 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).