Re: next-20250915: error[E0425]: cannot find function `atomic_read_acquire` in crate `bindings`

[Thorsten Leemhuis]

On 17.09.25 09:42, Dan Carpenter wrote:
> On Tue, Sep 16, 2025 at 06:46:06PM +0200, Christian Heusel wrote:
>> On 25/09/16 09:56PM, Naresh Kamboju wrote:
>>> On Tue, 16 Sept 2025 at 11:17, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote:
>>>>
>>>> The following build warnings / errors noticed on the arm arm64 and x86_64
>>>> with rust config build on the Linux next-20250915 tag.
>>>>
>>>> First seen on next-20250915
>>>> Good: next-20250912
>>>> Bad: next-20250915
> [...]
>>>> Build regression: next-20250915: error[E0425]: cannot find function
>>>> `atomic_read_acquire` in crate `bindings`
>>>
>>> Anders bisected this build regressions and found,
>>>
>>> # first bad commit:
>>>  [eb57133305f61b612252382d0c1478bba7f57b67]
>>>  rust: sync: Add basic atomic operation mapping framework
>>
>> Is this still an issue on next-20250916?

FWIW, I ran into this on next-20250915 and it afaics was fixed for
next-20250916.

>> As far as I can tell this has
>> been fixed, but now there is another rust build issue, see
>> https://lore.kernel.org/regressions/0fee48bb-7411-4414-b4e7-395a8c3d0f6c@xxxxxxxxx/
>> for more information.
> 
> next-20250916 still fails but with a different Rust issue.

Ran into that that merge mistake, too, but that can be fixed by the
patch Christian linked to above  -- and I expect Mark (now CCed) has
seen it and will resolve this with today's -next.

> [...]

Ciao, Thorsten