From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: lepillai@linux.ibm.com
Cc: lekshmi-cpillai <lekshmi@ktes.isst.tadn.ibm.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] Added new_behavior flag to detect kernel version Kernel >= 6.11: Tests that creat() succeeds (write to executed file allowed)
Date: Tue, 28 Apr 2026 08:46:09 +0000 [thread overview]
Message-ID: <69f073d5.050a0220.2ecf74.a4c0@mx.google.com> (raw)
In-Reply-To: <20260421050251.3662828-1-lepillai@linux.ibm.com>
Hi,
> From: lekshmi-cpillai <lekshmi@ktes.isst.tadn.ibm.com>
>
> ---
> testcases/kernel/syscalls/creat/creat07.c | 38 ++++++++++++++++-------
> 1 file changed, 27 insertions(+), 11 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/creat/creat07.c b/testcases/kernel/syscalls/creat/creat07.c
> index c7b85ee69..762022301 100644
> --- a/testcases/kernel/syscalls/creat/creat07.c
> +++ b/testcases/kernel/syscalls/creat/creat07.c
> @@ -19,6 +19,8 @@
>
> #define TEST_APP "creat07_child"
>
> +static int new_behavior;
> +
> static void verify_creat(void)
> {
> pid_t pid;
> @@ -33,16 +35,26 @@ static void verify_creat(void)
>
> TEST(creat(TEST_APP, O_WRONLY));
>
> - if (TST_RET != -1) {
> - tst_res(TFAIL, "creat() succeeded unexpectedly");
> - return;
> + if (new_behavior) {
> + /* Kernel >= 6.11: write to executed file is allowed */
> + if (TST_RET != -1) {
> + SAFE_CLOSE(TST_RET);
> + tst_res(TPASS, "creat() succeeded as expected (new behavior)");
> + } else {
> + tst_res(TFAIL | TTERRNO, "creat() failed unexpectedly");
> + }
> + } else {
> + /* Kernel < 6.11: write to executed file returns ETXTBSY */
> + if (TST_RET != -1) {
> + tst_res(TFAIL, "creat() succeeded unexpectedly");
> + SAFE_CLOSE(TST_RET);
> + } else if (TST_ERR == ETXTBSY) {
> + tst_res(TPASS, "creat() received ETXTBSY");
> + } else {
> + tst_res(TFAIL | TTERRNO, "creat() failed unexpectedly");
> + }
> }
>
> - if (TST_ERR == ETXTBSY)
> - tst_res(TPASS, "creat() received EXTBSY");
> - else
> - tst_res(TFAIL | TTERRNO, "creat() failed unexpectedly");
> -
> SAFE_KILL(pid, SIGKILL);
> SAFE_WAITPID(pid, NULL, 0);
> }
> @@ -50,9 +62,13 @@ static void verify_creat(void)
> static void setup(void)
> {
> if ((tst_kvercmp(6, 11, 0)) >= 0) {
> - tst_brk(TCONF, "Skipping test, write to executed file is "
> - "allowed since 6.11-rc1.\n"
> - "2a010c412853 (\"fs: don't block i_writecount during exec\")");
> + new_behavior = 1;
> + tst_res(TINFO, "Testing new behavior: write to executed file is "
> + "allowed since 6.11-rc1 (2a010c412853)");
> + } else {
> + new_behavior = 0;
> + tst_res(TINFO, "Testing old behavior: write to executed file "
> + "returns ETXTBSY");
> }
> }
>
> --
> 2.39.1
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
There's too much going on in these nested statements. The `new_behavior`
is not needed, we only need to save the error code (-1 or ETXTBSY) inside
a static variable.
If it's not -1, TST_EXP_ERR() can be used. Otherwise we print a TPASS.
The kernel version is printed before every test execution, so there's no
need to show any information about it.
Also test it with `-i` parameter. The test is likely broken with this patch.
Kind Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-28 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 5:36 [LTP] [PATCH] Added new_behavior flag to detect kernel version Kernel >= 6.11: Tests that creat() succeeds (write to executed file allowed) lepillai
2026-04-08 10:10 ` Cyril Hrubis
2026-04-21 5:02 ` lepillai
2026-04-21 5:35 ` [LTP] " linuxtestproject.agent
2026-04-28 8:46 ` Andrea Cervesato via ltp [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-08 5:33 [LTP] [PATCH] " lepillai
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=69f073d5.050a0220.2ecf74.a4c0@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=lekshmi@ktes.isst.tadn.ibm.com \
--cc=lepillai@linux.ibm.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