Received-SPF: pass (google.com: domain of linux-kernel+bounces-34651-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Mon, 22 Jan 2024 18:51:29 -0800
From: Kees Cook <kees@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>,
 Kees Cook <keescook@chromium.org>
CC: linux-hardening@vger.kernel.org,
 "Gustavo A. R. Silva" <gustavoars@kernel.org>,
 Bill Wendling <morbo@google.com>, Justin Stitt <justinstitt@google.com>,
 linux-kernel@vger.kernel.org
Subject: =?US-ASCII?Q?Re=3A_=5BPATCH_00/82=5D_overflow=3A_Refacto?= =?US-ASCII?Q?r_open-coded_arithmetic_wrap-around?=
User-Agent: K-9 Mail for Android
In-Reply-To: <337u2jcp3s2vrvotj4jppgpr7zas5fod6k3mhe263ghpux7s5x@knz6eibm2jis>
References: <20240122235208.work.748-kees@kernel.org> <337u2jcp3s2vrvotj4jppgpr7zas5fod6k3mhe263ghpux7s5x@knz6eibm2jis>
Message-ID: <4DE92BD2-50FE-4634-ACF3-E0CC735EDAEB@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable


On January 22, 2024 6:22:13 PM PST, Kent Overstreet <kent=2Eoverstreet@lin=
ux=2Edev> wrote:
>On Mon, Jan 22, 2024 at 04:26:35PM -0800, Kees Cook wrote:
>> In our continuing effort to eliminate root causes of flaws in the kerne=
l,
>> this series is the start to providing a way to have sensible coverage
>> for catching unexpected arithmetic wrap-around=2E
>>=20
>This all seems fine, but=2E=2E=2E Rust already has this at the type syste=
m
>level=2E=2E=2E=2E
>
>I know you're not one of the people bringing bickering into the Rust
>threads, so I'm wondering if perhaps your secret plan is to annoy the
>die hard "I want everything to be fast with razor blades everywhere" C
>programmers enough to finally get onboard the "let's just switch to a
>language with less razor wire" train=2E

I don't want to annoy anyone, but yeah, in the process of getting rid of d=
angerous stuff we do end up asking people to make changes they're not used =
to=2E I hope to make it as easy as possible, though=2E

I'm a big fan of Rust, but I know it's not going to happen over night; the=
re is a LOT of C code in Linux=2E :) I look at making the kernel safer by r=
emoving as many C foot-guns as possible=2E As we remove the ambiguities in =
C that lead to vulnerabilities, we'll eventually meet halfway with the new =
Rust code=2E

-Kees

--=20
Kees Cook