linux-kernel - Re: [char-misc-next v2] mei: use kvmalloc for read buffer

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] [day] [month] [year] [list]

Message-ID: <2024101519-malt-used-4986@gregkh>
Date: Tue, 15 Oct 2024 13:24:28 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Alexander Usyskin <alexander.usyskin@...el.com>
Cc: Oren Weil <oren.jer.weil@...el.com>, Tomas Winkler <tomasw@...il.com>,
	linux-kernel@...r.kernel.org, Rohit Agarwal <rohiagar@...omium.org>,
	Brian Geffon <bgeffon@...gle.com>
Subject: Re: [char-misc-next v2] mei: use kvmalloc for read buffer

On Tue, Oct 15, 2024 at 01:47:45PM +0300, Alexander Usyskin wrote:
> Read buffer is allocated according to max message size, reported by
> the firmware and may reach 64K in systems with pxp client.
> Contiguous 64k allocation may fail under memory pressure.
> Read buffer is used as in-driver message storage and not required
> to be contiguous.
> Use kvmalloc to allow kernel to allocate non-contiguous memory.
> 
> Reported-by: Rohit Agarwal <rohiagar@...omium.org>
> Closes: https://lore.kernel.org/all/20240813084542.2921300-1-rohiagar@chromium.org/
> Tested-by: Brian Geffon <bgeffon@...gle.com>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@...el.com>
> ---

No Fixes: tag?