From: Greg KH <gregkh@linuxfoundation.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Vincent Mailhol <mailhol@kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH net 03/19] can: raw: add locking for raw flags bitfield
Date: Mon, 27 Jul 2026 05:59:07 +0200 [thread overview]
Message-ID: <2026072716-blurt-trickle-b2ef@gregkh> (raw)
In-Reply-To: <918a5842-9649-4c13-9291-f06fb3fa2910@hartkopp.net>
On Sun, Jul 26, 2026 at 09:45:09PM +0200, Oliver Hartkopp wrote:
>
>
> On 26.07.26 13:17, Greg KH wrote:
> > On Sun, Jul 26, 2026 at 10:08:52AM +0200, Oliver Hartkopp wrote:
> > > Upstream commit 1e5185c090589f4146d728ab36417d8a5419f127
> > >
> > > is missing in stable.
> >
> > Which stable? And why wasn't this tagged for stable inclusion to start
> > with?
>
> This patch fixes commit 890e5198a6e5b238627c245fafea1a92670a86cd ("can: raw:
> use bitfields to store flags in struct raw_sock") introduced in 6.18:
>
> $ git tag --contains 890e5198a6e5b238627c245fafea1a92670a86cd | head -1
> v6.18
>
> So it would be needed for 6.18 and never.
>
> I thought the tag
>
> Fixes: 890e5198a6e5 ("can: raw: use bitfields to store flags in struct
> raw_sock")
>
> would automatically tag this patch for stable with AUTOSEL.
Never rely on AUTOSEL if you know you want a patch merged, please just
follow the documentation for how to get a stable patch merged:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
thanks,
greg k-h
prev parent reply other threads:[~2026-07-27 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260716155528.809908-1-mkl@pengutronix.de>
2026-07-16 15:47 ` [PATCH net 02/19] can: esd_usb: kill anchored URBs before freeing netdevs Marc Kleine-Budde
[not found] ` <20260716155528.809908-4-mkl@pengutronix.de>
2026-07-26 8:08 ` [PATCH net 03/19] can: raw: add locking for raw flags bitfield Oliver Hartkopp
2026-07-26 11:17 ` Greg KH
2026-07-26 19:45 ` Oliver Hartkopp
2026-07-27 3:59 ` Greg KH [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=2026072716-blurt-trickle-b2ef@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).