[Bug 220272] Latent race condition in USB code unveiled with optimized memset_64.S

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220272

--- Comment #4 from Marcus Seyfarth (m.seyfarth@gmail.com) ---
(In reply to Greg Kroah-Hartman from comment #1)
> On Thu, Jun 26, 2025 at 11:39:35AM +0000, bugzilla-daemon@kernel.org wrote:
> > Experimenting with AI to tune memset_64.S (see the attached file) for my
> > Intel
> > 14700KF-system unveiled a race condition in the USB code.
> 
> Odds are this is because your memset code is buggy :)
> 
> As this isn't an existing kernel issue, there's not much we can do about
> this at the moment, sorry.

@Greg and Alan
Understood, I thought so, too. But maybe there is some truth to the AI
analysis. I cannot tell anything myself as I do not bring any programming
expertise to the table and am fully dependant on AI (which is far from perfect
at this point in time, I know). However, AI analysis by O3 and Gemini 2.5 Pro
both claim that my custom memset is fine and pointed me towards multiple
problems in the xhci_setup_device function of xhci.c.

All attempts to fix the problem failed so far. Hence this could be a red
herring, I cannot tell.

If people are willing to spend some time on this, I have attached the
customized memset_64.S as full file and as a patch. If people do not consider
this actionable, that is totally fine with me, too.

Kernel: 6.15.3
Distro: CachyOS

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.