Linux Test Project
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it, linuxtestproject.agent@gmail.com
Subject: Re: [LTP] lib: Rename function check_kver() => check_min_kver()
Date: Mon, 3 Aug 2026 15:13:31 +0200	[thread overview]
Message-ID: <anCT-2ttAe0Qz0M3@yuki.lan> (raw)
In-Reply-To: <6a6c9716.b7086f8d.c2a23.334f@mx.google.com>

Hi!
> > @Cyril @Andrea could you also please double check?
> 
> It's correct.
> 
> The legacy ETXTBSY behavior was fully restored in commit
> 3b832035387f (Revert "fs: don't block i_writecount during exec").

Isn't this a case where we should just fail if the revert wasn't
backported?

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2026-08-03 13:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 10:51 [LTP] [PATCH v3 0/5] Add support for .max_kver Petr Vorel
2026-07-31 10:51 ` [LTP] [PATCH v3 1/5] lib: Rename function check_kver() => check_min_kver() Petr Vorel
2026-07-31 11:52   ` [LTP] " linuxtestproject.agent
2026-07-31 12:20     ` Petr Vorel
2026-07-31 12:37       ` Andrea Cervesato via ltp
2026-07-31 12:42         ` Petr Vorel
2026-07-31 12:44           ` Andrea Cervesato via ltp
2026-08-03 13:06             ` [LTP] [RFC] " Petr Vorel
2026-08-03 13:13         ` Cyril Hrubis [this message]
2026-08-03 13:42           ` [LTP] " Petr Vorel
2026-07-31 10:51 ` [LTP] [PATCH v3 2/5] lib: Add support for max_kver to struct tst_test and tst_fs Petr Vorel
2026-07-31 11:48   ` Avinesh Kumar via ltp
2026-07-31 10:51 ` [LTP] [PATCH v3 3/5] execve04: Use .max_kver Petr Vorel
2026-07-31 10:51 ` [LTP] [PATCH v3 4/5] creat07: " Petr Vorel
2026-07-31 10:51 ` [LTP] [PATCH v3 5/5] fanotify20: Skip on v7.2 Petr Vorel

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=anCT-2ttAe0Qz0M3@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --cc=linuxtestproject.agent@gmail.com \
    --cc=ltp@lists.linux.it \
    /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