From: Song Liu <song@kernel.org>
To: <bpf@vger.kernel.org>, <netdev@vger.kernel.org>
Cc: <ast@kernel.org>, <daniel@iogearbox.net>, <andrii@kernel.org>,
<kernel-team@fb.com>, Song Liu <song@kernel.org>
Subject: [PATCH bpf-next 0/2] fixes for bpf_prog_pack
Date: Mon, 21 Mar 2022 11:00:07 -0700 [thread overview]
Message-ID: <20220321180009.1944482-1-song@kernel.org> (raw)
Two fixes for issues reported by syzbot and kernel test robot.
Song Liu (2):
bpf: fix bpf_prog_pack for multi-node setup
bpf: fix bpf_prog_pack when PMU_SIZE is not defined
kernel/bpf/core.c | 22 +++++++++++++++++++---
1 file changed, 19 insertions(+), 3 deletions(-)
--
2.30.2
next reply other threads:[~2022-03-21 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 18:00 Song Liu [this message]
2022-03-21 18:00 ` [PATCH bpf-next 1/2] bpf: fix bpf_prog_pack for multi-node setup Song Liu
2022-03-21 18:00 ` [PATCH bpf-next 2/2] bpf: fix bpf_prog_pack when PMU_SIZE is not defined Song Liu
2022-03-21 21:00 ` [PATCH bpf-next 0/2] fixes for bpf_prog_pack patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2022-03-02 0:43 Song Liu
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=20220321180009.1944482-1-song@kernel.org \
--to=song@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@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).