On 5/9/25 18:19, Linus Torvalds wrote: > On Fri, 9 May 2025 at 08:09, Petr Pavlu <petr.pa...@suse.com> wrote: >> >> The fix has been on modules-next only since yesterday but should be safe. > > Hmm. > > At a minimum, the *description* of this bug is garbage. > > It talks about an "uninitialized completion pointer", but then the fix > actually depends on it being initialized - just initialized to NULL. > > I do believe that it always is initialized, and I have pulled this. > but I really think the explanations here are actively misleading. > > Because there's a big difference between "uninitialized" and "not > pointing to a completion".
Right, the description is in this aspect misleading, my bad. -- Petr
