[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjNj0vHh9v6-LTrbgtq=o6OS+RN3u3m03nV3n9V+urGtg@mail.gmail.com>
Date: Fri, 9 May 2025 09:19:24 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Petr Pavlu <petr.pavlu@...e.com>
Cc: Luis Chamberlain <mcgrof@...nel.org>, Sami Tolvanen <samitolvanen@...gle.com>,
Daniel Gomez <da.gomez@...sung.com>, linux-modules@...r.kernel.org,
linux-kernel@...r.kernel.org, Dmitry Antipov <dmantipov@...dex.ru>
Subject: Re: [GIT PULL] Modules fixes for v6.15-rc6
On Fri, 9 May 2025 at 08:09, Petr Pavlu <petr.pavlu@...e.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".
Linus
Powered by blists - more mailing lists