Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38;
Date:   Thu, 7 Dec 2023 12:05:21 +0100
From:   Joel Granados <j.granados@samsung.com>
To:     Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <linux@weissschuh.net>
CC:     Luis Chamberlain <mcgrof@kernel.org>,
        Kees Cook <keescook@chromium.org>,
        "Gustavo A. R. Silva" <gustavoars@kernel.org>,
        Iurii Zaikin <yzaikin@google.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        <linux-hardening@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2 00/18] sysctl: constify sysctl ctl_tables
Message-ID: <20231207110521.jeudk6y5ejh6ngf6@localhost>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512";
        protocol="application/pgp-signature"; boundary="a7f76owrdx7oxple"
Content-Disposition: inline
In-Reply-To: <b4b0b7ea-d8b3-4538-a5b9-87a23bbdac5f@t-8ch.de>
CMS-TYPE: 201P
References: <20231204-const-sysctl-v2-0-7a5060b11447@weissschuh.net>
        <ZW66FhWx7W67Y9rP@bombadil.infradead.org>
        <CGME20231205080416eucas1p241d86dda65c0009ca352673e1ca5b26d@eucas1p2.samsung.com>
        <b4b0b7ea-d8b3-4538-a5b9-87a23bbdac5f@t-8ch.de>
Precedence: bulk

--a7f76owrdx7oxple
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 05, 2023 at 09:04:08AM +0100, Thomas Wei=DFschuh wrote:
> On 2023-12-04 21:50:14-0800, Luis Chamberlain wrote:
> > On Mon, Dec 04, 2023 at 08:52:13AM +0100, Thomas Wei=DFschuh wrote:
> > > Tested by booting and with the sysctl selftests on x86.
> >=20
> > Can I trouble you to rebase on sysctl-next?
> >=20
> > https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/log/?h=
=3Dsysctl-next
>=20
> Will do.
>=20
> Note:
>=20
> I noticed that patch "sysctl: move sysctl type to ctl_table_header" from
> this series seems to be the better alternative to
> commit fd696ee2395755a ("sysctl: Fix out of bounds access for empty sysct=
l registers")
> which is currently on sysctl-next.
Indeed. By taking this out of the ctl_table, we would not need to make
sure that we don't touch that (potentially non-existing) first element.

This is what I think should be done (@Luis @Kees chime in if you have any
thoughts):
1. Leave the current fix for 6.7. AFAIK, it is already queued for that
   release and it is a bit late in the cycle to put anything new in.
2. I think this patch has value on its own as a better solution to the
   "access invalid memory" issue. @thomas: remove this patch from your
   const set and send it in a different patch series.
3. const patchset would need to go on top of the new set.

Having it on its own will allow it to go in faster and make it easier to
review without having to thinkg about the const stuff as well.

Best
>=20
> The patch from the series should only depend on
> "sysctl: drop sysctl_is_perm_empty_ctl_table" from my series.
>=20
> Thomas

--=20

Joel Granados

--a7f76owrdx7oxple
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEErkcJVyXmMSXOyyeQupfNUreWQU8FAmVxpu8ACgkQupfNUreW
QU/DNAv/TDQMJUs4oKgPcr+aoFQ/sng5W4yFQY5GA7FAsG3lAFqEcPFG6YB8XWO6
pUmcI9ZvnpNMaQdN4PBYCo25B165jbGnm4qlyOQ/vCTECPzIESXwC42lNOCblQUQ
mM0LarwaqRHcUzh0/9EyTdh/8M3n0O3foisGm/3JmKBkMoFrt81ucKW01fyasptR
GIhFpi4WdbMsb/uRjImsMmJza8oPSa7uTU4Vhs9fMmhRIKwp4/fAW38z+LPZkf60
/nspxC6IRu1xA9fByp25sv+P/uAu5dx+VVrDFGfAyIyxAJLU1IIgeTLAzWmNKp0M
/BLnEEJ/8FD59zHUWRYE//yUKO/tfMfenQ9U69x13CeT2aeFEMT+jB3z1XcmaAG6
l5nycPXZZQsx8Nb0ayfWLaWSmeA5/Vh8Jc8QXCZmO7xLGftipyLWpZcGhjcOwaUi
upyI4hAm+GL2Gm7BbWUpjgeB34pbhTSCQPDNyGJeWT2x9l6qKKmlUG36eKx6q2NO
AXRuEQwr
=YKxV
-----END PGP SIGNATURE-----

--a7f76owrdx7oxple--