linux-kernel - Re: [PATCH bpf-next v7 15/24] HID: bpf: allocate data memory for device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 28 Jul 2022 17:10:06 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Benjamin Tissoires <benjamin.tissoires@...hat.com>
Cc:     Jiri Kosina <jikos@...nel.org>,
        Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii@...nel.org>,
        Martin KaFai Lau <kafai@...com>,
        Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
        Kumar Kartikeya Dwivedi <memxor@...il.com>,
        John Fastabend <john.fastabend@...il.com>,
        KP Singh <kpsingh@...nel.org>, Shuah Khan <shuah@...nel.org>,
        Dave Marchevsky <davemarchevsky@...com>,
        Joe Stringer <joe@...ium.io>, Jonathan Corbet <corbet@....net>,
        Tero Kristo <tero.kristo@...ux.intel.com>,
        linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
        netdev@...r.kernel.org, bpf@...r.kernel.org,
        linux-kselftest@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH bpf-next v7 15/24] HID: bpf: allocate data memory for
 device_event BPF programs

On Thu, Jul 21, 2022 at 05:36:16PM +0200, Benjamin Tissoires wrote:
> We need to also be able to change the size of the report.
> Reducing it is easy, because we already have the incoming buffer that is
> big enough, but extending it is harder.
> 
> Pre-allocate a buffer that is big enough to handle all reports of the
> device, and use that as the primary buffer for BPF programs.
> To be able to change the size of the buffer, we change the device_event
> API and request it to return the size of the buffer.
> 
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@...hat.com>

Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>