From: Petr Pavlu <petr.pavlu@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Antipov <dmantipov@yandex.ru>
Subject: [GIT PULL] Modules fixes for v6.15-rc6
Date: Fri, 9 May 2025 17:09:54 +0200 [thread overview]
Message-ID: <0e82be0f-a305-4aba-b9ab-79596f595277@suse.com> (raw)
The following changes since commit 92a09c47464d040866cf2b4cd052bc60555185fb:
Linux 6.15-rc5 (2025-05-04 13:55:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git/ tags/modules-6.15-rc6
for you to fetch changes up to a6aeb739974ec73e5217c75a7c008a688d3d5cf1:
module: ensure that kobject_put() is safe for module type kobjects (2025-05-07 20:24:59 +0200)
----------------------------------------------------------------
Modules fixes for v6.15-rc6
A single fix to prevent use of an uninitialized completion pointer when
releasing a module_kobject in specific situations.
This addresses a latent bug exposed by commit f95bbfe18512 ("drivers: base:
handle module_kobject creation"), which was merged in 6.15-rc5. The fix has
been on modules-next only since yesterday but should be safe.
----------------------------------------------------------------
Dmitry Antipov (1):
module: ensure that kobject_put() is safe for module type kobjects
kernel/params.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
next reply other threads:[~2025-05-09 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 15:09 Petr Pavlu [this message]
2025-05-09 16:19 ` Linus Torvalds
2025-05-10 5:25 ` Petr Pavlu
2025-05-12 18:14 ` Dmitry Antipov
2025-05-12 18:56 ` Linus Torvalds
2025-05-09 18:31 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e82be0f-a305-4aba-b9ab-79596f595277@suse.com \
--to=petr.pavlu@suse.com \
--cc=da.gomez@samsung.com \
--cc=dmantipov@yandex.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=samitolvanen@google.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®