All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>, Cyril Hrubis <chrubis@suse.cz>,
	Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] mount08.c: Add min_kver for test case
Date: Wed, 1 Oct 2025 12:47:11 +0200	[thread overview]
Message-ID: <20251001104711.GA265041@pevik> (raw)
In-Reply-To: <20250930085858.GA224315@pevik>

Hi all,

...
> ...
> > For a record, d80b065bb172 is a merge commit, the fix contains actually 7
> > commits. IMHO none of them has been backported to any stable / LTS kernel.  I'll
> > ask Christian and Greg if it makes sense to backport it.

> asked [1]. (unfortunately I forgot to delete message-id and From: from the
> original message).

FYI answer from Aleksa [2] suggests it will not be backported, but let's wait
if somebody else give his opinion. Anyway, I'm not advocating for this patch
(to add .min_kver = "6.12"), although it wouldn't harm to document it in the
test that unlike kernel folks which consider it as a "new feature" we consider
it as a "security fix".

Kind regards,
Petr

> Kind regards,
> Petr

> [1] https://lore.kernel.org/all/20240806-work-procfs-v1-0-fb04e1d09f0c@kernel.org/
[2] https://lore.kernel.org/linux-fsdevel/2025-09-30-emerald-unsure-pillow-prism-nKVGLB@cyphar.com/

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

      reply	other threads:[~2025-10-01 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 11:29 [LTP] [PATCH v1] mount08.c: Add min_kver for test case Wei Gao via ltp
2025-09-29 12:05 ` Cyril Hrubis
2025-09-29 12:09   ` Martin Doucha
2025-09-29 18:11     ` Petr Vorel
2025-09-30  8:58       ` Petr Vorel
2025-10-01 10:47         ` Petr Vorel [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=20251001104711.GA265041@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    --cc=wegao@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.