[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250613202027.1364272-1-ojeda@kernel.org>
Date: Fri, 13 Jun 2025 22:20:27 +0200
From: Miguel Ojeda <ojeda@...nel.org>
To: marc.herbert@...ux.intel.com
Cc: Benjamin.Cheatham@....com,
Jonathan.Cameron@...wei.com,
dakr@...nel.org,
dan.j.williams@...el.com,
gregkh@...uxfoundation.org,
linux-acpi@...r.kernel.org,
linux-cxl@...r.kernel.org,
linux-kernel@...r.kernel.org,
rafael.j.wysocki@...el.com,
rafael@...nel.org,
sudeep.holla@....com,
Kees Cook <kees@...nel.org>
Subject: Re: [PATCH] driver core: faux: fix Undefined Behavior in faux_device_destroy()
On Fri, 13 Jun 2025 19:15:56 +0000 marc.herbert@...ux.intel.com wrote:
>
> doubts, I include a very short and simple demo below. I imagine kernel
> compilation flags and various other conditions may not make the
> consequences as bad as this example, however those conditions could change
Yeah, the kernel uses `-fno-delete-null-pointer-checks`, so e.g. for your
example:
https://godbolt.org/z/hs49jb98o
Cheers,
Miguel
Powered by blists - more mailing lists