[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <169116865197.3054577.11464864173886707392.b4-ty@chromium.org>
Date: Fri, 4 Aug 2023 10:04:14 -0700
From: Kees Cook <keescook@...omium.org>
To: tony.luck@...el.com, gpiccoli@...lia.com, joel@...lfernandes.org,
enlin.mu@...soc.com, Yunlong Xing <yunlong.xing@...soc.com>
Cc: Kees Cook <keescook@...omium.org>, linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org, enlinmu@...il.com,
yunlong.xing23@...il.com
Subject: Re: [PATCH 1/1] pstore/ram: Check member of buffers during the initialization phase of the pstore
On Tue, 01 Aug 2023 14:04:32 +0800, Yunlong Xing wrote:
> The commit 30696378f68a("pstore/ram: Do not treat empty buffers as valid")
> would introduce the following issue:
>
> When finding the buffer_size is zero, it would return directly.However, at
> the same time, if the buffer's start is a illegal value, the others would
> panic if access the buffer.
>
> [...]
Applied to for-next/pstore, thanks!
[1/1] pstore/ram: Check member of buffers during the initialization phase of the pstore
https://git.kernel.org/kees/c/fe8c3623ab06
Take care,
--
Kees Cook
Powered by blists - more mailing lists