linux-kernel - Re: [PATCH v3 0/4] kstrtox: introduce memparse

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: <ZZllAi_GbsoDF5Eg@smile.fi.intel.com>
Date: Sat, 6 Jan 2024 16:34:42 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Qu Wenruo <wqu@...e.com>
Cc: linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, christophe.jaillet@...adoo.fr,
	David.Laight@...lab.com, ddiss@...e.de, geert@...ux-m68k.org
Subject: Re: [PATCH v3 0/4] kstrtox: introduce memparse_safe()

On Thu, Jan 04, 2024 at 09:57:47AM +1030, Qu Wenruo wrote:
> [CHANGELOG]
> v3:
> - Fix the 32bit pointer pattern in the test case
>   The old pointer pattern for 32 bit systems is in fact 40 bits,
>   which would still lead to sparse warning.
>   The newer pattern is using UINTPTR_MAX to trim the pattern, then
>   converted to a pointer, which should not cause any trimmed bits and
>   make sparse happy.

Having test cases is quite good, thanks!
But as I understood what Alexey wanted, is not using the kstrtox files for this.
You can introduce it in the cmdline.c, correct? Just include local "kstrtox.h".

I'm on leave till end of the month, I'll look at this later.

-- 
With Best Regards,
Andy Shevchenko