[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202406171100.B0A8095@keescook>
Date: Mon, 17 Jun 2024 11:00:41 -0700
From: Kees Cook <kees@...nel.org>
To: Adrian Ratiu <adrian.ratiu@...labora.com>
Cc: linux-fsdevel@...r.kernel.org, linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org,
linux-doc@...r.kernel.org, kernel@...labora.com, gbiv@...gle.com,
ryanbeltran@...gle.com, inglorion@...gle.com, ajordanr@...gle.com,
jorgelo@...omium.org, Guenter Roeck <groeck@...omium.org>,
Doug Anderson <dianders@...omium.org>, Jann Horn <jannh@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Randy Dunlap <rdunlap@...radead.org>,
Christian Brauner <brauner@...nel.org>, Jeff Xu <jeffxu@...gle.com>,
Mike Frysinger <vapier@...omium.org>
Subject: Re: [PATCH v6 2/2] proc: restrict /proc/pid/mem
On Thu, Jun 13, 2024 at 04:39:37PM +0300, Adrian Ratiu wrote:
> Prior to v2.6.39 write access to /proc/<pid>/mem was restricted,
> after which it got allowed in commit 198214a7ee50 ("proc: enable
> writing to /proc/pid/mem"). Famous last words from that patch:
> "no longer a security hazard". :)
This version looks great! Thanks for all the changes. :)
Reviewed-by: Kees Cook <kees@...nel.org>
--
Kees Cook
Powered by blists - more mailing lists