linux-kernel - Re: [PATCH] ASoC: topology: fix stack corruption by code unification for creating standalone and widget controls

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] [day] [month] [year] [list]

Message-ID: <ZvFm0Oa6g_pTjK8t@finisterre.sirena.org.uk>
Date: Mon, 23 Sep 2024 15:02:08 +0200
From: Mark Brown <broonie@...nel.org>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Amadeusz Sławiński <amadeuszx.slawinski@...ux.intel.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
	linux-sound@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Discussions about the Letux Kernel <letux-kernel@...nphoenux.org>,
	kernel@...a-handheld.com, risca@...akolonin.se
Subject: Re: [PATCH] ASoC: topology: fix stack corruption by code unification
 for creating standalone and widget controls

On Mon, Sep 23, 2024 at 10:07:48AM +0200, H. Nikolaus Schaller wrote:

> You can't store a 64 bit pointer in an 32 bit unsigned int without getting into trouble
> on conversion back :) That is what uintptr_t is intended for, but it is also just an
> unsigned long in linux/types.h. AFAIK it is defined by C99 as "unsigned integer type
> capable of holding a pointer".

Practically speaking the kernel C code assumes that uintptr_t is the
same size as unsigned long and there's a whole bunch of porting would be
needed if you want to change that.  unintptr_t is a relatively new thing
compared to the C that the kernel originally targeted.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)