[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <171476494554.2457276.4385338995352491886.b4-ty@chromium.org>
Date: Fri, 3 May 2024 12:35:48 -0700
From: Kees Cook <keescook@...omium.org>
To: Alexander Popov <alex.popov@...ux.com>,
Thomas Weißschuh <linux@...ssschuh.net>
Cc: Kees Cook <keescook@...omium.org>,
linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org,
stable@...r.kernel.org,
Luis Chamberlain <mcgrof@...nel.org>,
Joel Granados <j.granados@...sung.com>
Subject: Re: [PATCH] stackleak: don't modify ctl_table argument
On Fri, 03 May 2024 15:44:09 +0200, Thomas Weißschuh wrote:
> Sysctl handlers are not supposed to modify the ctl_table passed to them.
> Adapt the logic to work with a temporary
> variable, similar to how it is done in other parts of the kernel.
>
> This is also a prerequisite to enforce the immutability of the argument
> through the callbacks prototy.
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] stackleak: don't modify ctl_table argument
https://git.kernel.org/kees/c/0e148d3cca0d
Take care,
--
Kees Cook
Powered by blists - more mailing lists