From: Greg KH <greg@kroah.com>
To: Ignat Korchagin <ignat@cloudflare.com>
Cc: stable@vger.kernel.org, bpf@vger.kernel.org,
kernel-team@cloudflare.com, Pengfei Xu <pengfei.xu@intel.com>,
Jiri Olsa <jolsa@kernel.org>, Andrii Nakryiko <andrii@kernel.org>,
Hou Tao <houtao1@huawei.com>
Subject: Re: [PATCH 6.6.y] bpf: Add missing BPF_LINK_TYPE invocations
Date: Thu, 23 May 2024 13:57:43 +0200 [thread overview]
Message-ID: <2024052328-squatting-umpire-a826@gregkh> (raw)
In-Reply-To: <20240521101826.95373-1-ignat@cloudflare.com>
On Tue, May 21, 2024 at 11:18:26AM +0100, Ignat Korchagin wrote:
> From: Jiri Olsa <jolsa@kernel.org>
>
> commit 117211aa739a926e6555cfea883be84bee6f1695 upstream.
>
> Pengfei Xu reported [1] Syzkaller/KASAN issue found in bpf_link_show_fdinfo.
>
> The reason is missing BPF_LINK_TYPE invocation for uprobe multi
> link and for several other links, adding that.
>
> [1] https://lore.kernel.org/bpf/ZXptoKRSLspnk2ie@xpf.sh.intel.com/
>
> Fixes: 89ae89f53d20 ("bpf: Add multi uprobe link")
> Fixes: e420bed02507 ("bpf: Add fd-based tcx multi-prog infra with link support")
> Fixes: 84601d6ee68a ("bpf: add bpf_link support for BPF_NETFILTER programs")
> Fixes: 35dfaad7188c ("netkit, bpf: Add bpf programmable net device")
> Reported-by: Pengfei Xu <pengfei.xu@intel.com>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> Tested-by: Pengfei Xu <pengfei.xu@intel.com>
> Acked-by: Hou Tao <houtao1@huawei.com>
> Link: https://lore.kernel.org/bpf/20231215230502.2769743-1-jolsa@kernel.org
> Cc: stable@vger.kernel.org # 6.6
> Signed-off-by: Ignat Korchagin <ignat@cloudflare.com>
> ---
> Hi,
>
> We have experienced a KASAN warning in production on a 6.6 kernel, similar to
> [1]. This backported patch was adjusted to apply onto 6.6 stable branch: the
> only change is dropping the BPF_LINK_TYPE(BPF_LINK_TYPE_NETKIT, netkit)
> definition from the header as netkit was only introduced in 6.7 and 6.7 has the
> backport already.
>
> I was not able to run the syzkaller reproducer from [1], but we have not seen
> the KASAN warning in production since applying this patch internally.
Looks good, thanks for the backport, now queued up.
greg k-h
prev parent reply other threads:[~2024-05-23 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 10:18 [PATCH 6.6.y] bpf: Add missing BPF_LINK_TYPE invocations Ignat Korchagin
2024-05-23 11:57 ` 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=2024052328-squatting-umpire-a826@gregkh \
--to=greg@kroah.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=houtao1@huawei.com \
--cc=ignat@cloudflare.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@cloudflare.com \
--cc=pengfei.xu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox