From: patchwork-bot+netdevbpf@kernel.org
To: Sean Young <sean@mess.org>
Cc: linux-media@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH] media: bpf: do not copy more entries than user space requested
Date: Thu, 24 Jun 2021 13:40:03 +0000 [thread overview]
Message-ID: <162454200366.13710.10179869349829486025.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210623213754.632-1-sean@mess.org>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 23 Jun 2021 22:37:54 +0100 you wrote:
> The syscall bpf(BPF_PROG_QUERY, &attr) should the prog_cnt field to see
> how many entries user space provided and return ENOSPC if there are
> more programs than that. Before this patch, this is not checked and
> ENOSPC is never returned.
>
> Note that one lirc device is limited to 64 bpf programs, and user space
> I'm aware of -- ir-keytable -- always gives enough space for 64 entries
> already. However, we should not copy program ids than are requested.
>
> [...]
Here is the summary with links:
- media: bpf: do not copy more entries than user space requested
https://git.kernel.org/bpf/bpf-next/c/647d446d66e4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-06-24 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 21:37 [PATCH] media: bpf: do not copy more entries than user space requested Sean Young
2021-06-24 9:21 ` Sean Young
2021-06-24 13:40 ` patchwork-bot+netdevbpf [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=162454200366.13710.10179869349829486025.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.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).