linux-kernel - Re: Rust kernel policy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fd053f18e3856d070d695ea969b3fd635272e8e0.camel@tugraz.at>
Date: Sat, 22 Feb 2025 00:37:01 +0100
From: Martin Uecker <uecker@...raz.at>
To: Steven Rostedt <rostedt@...dmis.org>, Linus Torvalds
	 <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, ksummit@...ts.linux.dev
Subject: Re: Rust kernel policy

Am Freitag, dem 21.02.2025 um 17:24 -0500 schrieb Steven Rostedt:
> On Fri, 21 Feb 2025 11:30:41 -0800
> Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 
> > And yes, it's wrong in general. The problems with "x < 0" warning for
> > an unsigned 'x' are deep and fundamental, and macros that take various
> > types is only one (perhaps more obvious) example of how brokent that
> > garbage is.
> 
> The bug I recently fixed, and I still constantly make, where this does
> help, is the difference between size_t vs ssize_t. I keep forgetting that
> size_t is unsigned, and I'll check a return of a function that returns
> negative on error with it.
> 
> If I could just get a warning for this stupid mistake:
> 
> 	size_t ret;
> 
> 	ret = func();
> 	if (ret < 0)
> 		error();
> 
> 
> I'd be very happy.
> 

GCC has this warning, it is called -Wtype-limits

https://godbolt.org/z/M787vjhfo

It is activated by -Wextra.

(anyway, not at all related to my proposal)

Martin