From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: "rpalethorpe@suse.de" <rpalethorpe@suse.de>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] syscalls/finit_module02: Add ETXTBSY error for read-write fd
Date: Fri, 19 Nov 2021 02:53:09 +0000 [thread overview]
Message-ID: <619711C7.90700@fujitsu.com> (raw)
In-Reply-To: <87ee7dagfp.fsf@suse.de>
H Richard
> Hello Yang,
>
> Yang Xu<xuyang2018.jy@fujitsu.com> writes:
>
>> Signed-off-by: Yang Xu<xuyang2018.jy@fujitsu.com>
>
> Reviewed-by: Richard Palethorpe<rpalethorpe@suse.com>
>
Thanks for your review, merged.
ps: I also record this error by sending a patch to man-pages community.
Best Regards
Yang Xu
>> ---
>> testcases/kernel/syscalls/finit_module/finit_module02.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/testcases/kernel/syscalls/finit_module/finit_module02.c b/testcases/kernel/syscalls/finit_module/finit_module02.c
>> index 47b5edbfb..b3437b5d0 100644
>> --- a/testcases/kernel/syscalls/finit_module/finit_module02.c
>> +++ b/testcases/kernel/syscalls/finit_module/finit_module02.c
>> @@ -72,6 +72,8 @@ static struct tcase tcases[] = {
>> NULL},
>> {"file-not-readable",&fd, "", O_WRONLY | O_CLOEXEC, 0, 0, EBADF, 0,
>> NULL},
>> + {"file-readwrite",&fd, "", O_RDWR | O_CLOEXEC, 0, 0, ETXTBSY, 0,
>> + NULL},
>> {"directory",&fd_dir, "", O_RDONLY | O_CLOEXEC, 0, 0, 0, 0, dir_setup},
>> };
>>
>> @@ -134,6 +136,7 @@ static void run(unsigned int n)
>> static struct tst_test test = {
>> .tags = (const struct tst_tag[]) {
>> {"linux-git", "032146cda855"},
>> + {"linux-git", "39d637af5aa7"},
>> {}
>> },
>> .test = run,
>> --
>> 2.23.0
>
>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2021-11-19 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 8:24 [LTP] [PATCH] syscalls/finit_module02: Add ETXTBSY error for read-write fd Yang Xu
2021-11-18 10:25 ` Richard Palethorpe
2021-11-19 2:53 ` xuyang2018.jy [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=619711C7.90700@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
/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