Good afternoon Daniel,
On Mon, 22 Nov 2021, gregkh@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx>.
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
