linux-kernel - Re: [PATCH] fs: remove accidental overflow during wraparound check

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: <20240508001035.GK2118490@ZenIV>
Date: Wed, 8 May 2024 01:10:35 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Justin Stitt <justinstitt@...gle.com>
Cc: Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
	Nathan Chancellor <nathan@...nel.org>,
	Bill Wendling <morbo@...gle.com>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
	linux-hardening@...r.kernel.org
Subject: Re: [PATCH] fs: remove accidental overflow during wraparound check

On Tue, May 07, 2024 at 11:17:57PM +0000, Justin Stitt wrote:

> I wonder, though, why isn't loff_t an unsigned type?

Consider
	lseek(fd, -10, SEEK_CUR)

PS: the above is *not* an endorsement of the proposed patch or
KASAN overflow nonsense in general.