From: Lee Jones <lee.jones@linaro.org>
To: gregkh@linuxfoundation.org
Cc: daniel@iogearbox.net, andrii@kernel.org, ast@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] bpf: Fix toctou on read-only map's constant scalar tracking" failed to apply to 5.4-stable tree
Date: Thu, 17 Feb 2022 15:57:23 +0000 [thread overview]
Message-ID: <Yg5wY5FKj0ikiq+A@google.com> (raw)
In-Reply-To: <163757721744154@kroah.com>
Good afternoon Daniel,
On Mon, 22 Nov 2021, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 5.4-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
We are in receipt of a bug report which cites this patch as the fix.
The kernel in question is v5.4 and as you can see by the statement
above, it was not possible to back-port the fix into this Stable
release.
I did attempt to also back-port the commits mentioned in the commit
message of the patch you authored, in order to elevate the large merge
conflict that followed:
fc9702273e2e ("bpf: Add mmap() support for BPF_MAP_TYPE_ARRAY")
1f6cb19be2e2 ("bpf: Prevent re-mmap()'ing BPF map as writable for initially r/o mapping")
... but this just led me down a seemingly never ending rabbit hole.
Does v5.4 suffer with the problem you reported? The Fixes tag would
suggest that it does. If so, how would we go about patching it? As
you can image that kernel is still in support and running freely on an
innumerable amount of consumer devices.
Would you mind advising us how we might proceed please?
Kind regards,
Lee
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2022-02-17 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 10:33 FAILED: patch "[PATCH] bpf: Fix toctou on read-only map's constant scalar tracking" failed to apply to 5.4-stable tree gregkh
2022-02-17 15:57 ` Lee Jones [this message]
2022-02-17 16:17 ` Greg KH
2022-02-17 17:05 ` Lee Jones
2022-02-21 9:52 ` Lee Jones
2022-02-21 10:24 ` Greg KH
2022-02-21 10:44 ` Lee Jones
2022-03-01 21:23 ` Daniel Borkmann
2022-03-01 22:04 ` Rafael David Tinoco
2022-03-05 13:50 ` Greg KH
2022-03-07 8:38 ` Lee Jones
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=Yg5wY5FKj0ikiq+A@google.com \
--to=lee.jones@linaro.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=gregkh@linuxfoundation.org \
--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).