mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org, users@kernel.org
Subject: Re: [PATCH] get_maintainer: only use THE REST as a fallback
Date: Thu, 8 Oct 2026 18:04:50 +0200	[thread overview]
Message-ID: <d9e61e64-e300-415d-9b3f-0030425ce24b@kernel.org> (raw)
In-Reply-To: <20261008-quantum-polar-kraken-890dac@lemur>

On 08/10/2026 16:05, Konstantin Ryabitsev wrote:
> On Thu, Oct 08, 2026 at 03:22:56PM +0200, Matthieu Baerts wrote:
>> Is this list actively being used? The risk I see with this list is
>> having someone sending a new version of an existing patch only to this
>> list: this version will then be picked by tools like b4. If the
>> maintainer doesn't pay attention to the info messages, a wrong version
>> might be applied instead. Maybe b4 should catch such patches?
> 
> I'm trying to think of how this would happen. If the submitter users
> get-maintainer.pl, then they should always get the correct set of lists. If
> they aren't using get-maintainer.pl, then they aren't really likely to use
> just the patches archive list.
> 
> If they use b4 to send the patches, then even if they do manage to mess up the
> recipients, somehow, the maintainer should still be able to find it via the
> change-id search.

Sorry, I meant to say: when someone is trying to discretely get a bad
version applied on purpose. For example: user A sends a v1 using
get_maintainer.pl, then user B (or A) could send a v2 (or a v1 with
other content) only to patches@lists.linux.dev. In this case, a
maintainer who wants to apply the original v1, might end-up applying the
"bad" and "hidden" patch.

Or maybe "b4" already prevents that or is clear enough when picking a
newer/different version than the given one?

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2026-10-08 16:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 12:51 Konstantin Ryabitsev
2026-10-08 13:03 ` Jason A. Donenfeld
2026-10-08 13:10   ` Konstantin Ryabitsev
2026-10-08 13:22     ` Matthieu Baerts
2026-10-08 14:05       ` Konstantin Ryabitsev
2026-10-08 16:04         ` Matthieu Baerts [this message]
2026-10-09 16:41     ` Jason A. Donenfeld
2026-10-08 13:15 ` Jürgen Groß
2026-10-08 14:02   ` Konstantin Ryabitsev
2026-10-09 12:24   ` Jason Gunthorpe
2026-10-09 18:37   ` Willy Tarreau
2026-10-08 13:15 ` Michael S. Tsirkin
2026-10-08 13:39 ` Petr Pavlu
2026-10-08 14:06   ` Konstantin Ryabitsev
2026-10-09 16:25 ` Joe Perches

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=d9e61e64-e300-415d-9b3f-0030425ce24b@kernel.org \
    --to=matttbe@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=joe@perches.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=users@kernel.org \
    /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

all inboxes | Powered by JetHome®