All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Pu Lehui <pulehui@huaweicloud.com>,
	stable@vger.kernel.org, Eduard Zingerman <eddyz87@gmail.com>,
	Luiz Capitulino <luizcap@amazon.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Pu Lehui <pulehui@huawei.com>
Subject: Re: [PATCH 5.10 1/6] bpf: allow precision tracking for programs with subprogs
Date: Sat, 5 Aug 2023 07:47:10 +0200	[thread overview]
Message-ID: <2023080542-theme-sleet-808c@gregkh> (raw)
In-Reply-To: <96bcca9a-48a2-a2db-bd12-f7b69df90ad8@leemhuis.info>

On Fri, Aug 04, 2023 at 08:56:09PM +0200, Thorsten Leemhuis wrote:
> On 04.08.23 12:33, Greg KH wrote:
> > On Tue, Aug 01, 2023 at 10:36:55PM +0800, Pu Lehui wrote:
> >> From: Andrii Nakryiko <andrii@kernel.org>
> >>
> >> [ Upstream commit be2ef8161572ec1973124ebc50f56dafc2925e07 ]
> > 
> > For obvious reasons, I can't take this series only for 5.10 and not for
> > 5.15, otherwise you would update your kernel and have a regression.
> > 
> > So please, create a 5.15.y series also, and resend both of these, and
> > then we will be glad to apply them.  For this series, I've dropped them
> > from my review queue now.
> 
> I see you explaining this occasionally, makes me wonder if we should add
> something like the following to
> Documentation/process/stable-kernel-rules.rst (sorry, no diff/context,
> but I guess you'll understand things nevertheless):
> 
> """
> When using option 2 or 3 you can target a specific stable series. When
> doing so, you have to ensure that the fix or and equivalent is present
> or submitted to all newer stable trees, as users updating to them
> otherwise might encounter regressions. Hence, if you want a patch that
> was merged for 5.19-rc1 included in the 5.10 stable series, you must
> submit it for any stable series still maintained in the v5.11..v5.18
> range.
> """

Sure, hopefully people read the documentation, at the very least, I can
just point the at it and stop saying this over and over :)

thanks,

greg k-h

  reply	other threads:[~2023-08-05  5:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 14:36 [PATCH 5.10 0/6] Backporting for test_verifier failed Pu Lehui
2023-08-01 14:36 ` [PATCH 5.10 1/6] bpf: allow precision tracking for programs with subprogs Pu Lehui
2023-08-04 10:33   ` Greg KH
2023-08-04 12:15     ` Pu Lehui
2023-08-04 12:18       ` Eduard Zingerman
2023-08-04 12:34         ` Pu Lehui
2023-08-04 18:56     ` Thorsten Leemhuis
2023-08-05  5:47       ` Greg KH [this message]
2023-08-01 14:36 ` [PATCH 5.10 2/6] bpf: stop setting precise in current state Pu Lehui
2023-08-01 14:36 ` [PATCH 5.10 3/6] bpf: aggressively forget precise markings during state checkpointing Pu Lehui
2023-08-01 14:36 ` [PATCH 5.10 4/6] selftests/bpf: make test_align selftest more robust Pu Lehui
2023-08-01 14:36 ` [PATCH 5.10 5/6] selftests/bpf: Workaround verification failure for fexit_bpf2bpf/func_replace_return_code Pu Lehui
2023-08-01 14:37 ` [PATCH 5.10 6/6] selftests/bpf: Fix sk_assign on s390x Pu Lehui
2023-08-02  7:23 ` [PATCH 5.10 0/6] Backporting for test_verifier failed Pu Lehui
2023-08-02  7:28   ` Greg KH
2023-08-02 19:28 ` Luiz Capitulino

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=2023080542-theme-sleet-808c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=linux@leemhuis.info \
    --cc=luizcap@amazon.com \
    --cc=pulehui@huawei.com \
    --cc=pulehui@huaweicloud.com \
    --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 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.