From: Yafang Shao <laoar.shao@gmail.com>
To: jpoimboe@kernel.org, jikos@kernel.org, mbenes@suse.cz,
pmladek@suse.com, joe.lawrence@redhat.com, song@kernel.org
Cc: live-patching@vger.kernel.org, Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH v2 0/2] ivepatch: Fix several bugs found during replace set implementation
Date: Sun, 16 Aug 2026 17:04:40 +0800 [thread overview]
Message-ID: <20260816090442.18128-1-laoar.shao@gmail.com> (raw)
These fixes were found while implementing the replace set series [0].
They are independent of that series and can be applied separately.
Link: https://lore.kernel.org/live-patching/20260809091954.22930-1-laoar.shao@gmail.com [0]
Changes:
v1->v2:
- minor improvements and acked-by (Song)
- fix issues reported by sashiko
v1: https://lore.kernel.org/live-patching/20260813030408.9761-1-laoar.shao@gmail.com/
Yafang Shao (2):
livepatch: Fix wrong index in funcs cleanup error path
livepatch: Fix UAF of unregistered patch kobjects
include/linux/livepatch.h | 6 +++++
kernel/livepatch/core.c | 50 ++++++++++++++++++++++++++++++++++++---
scripts/livepatch/init.c | 2 +-
3 files changed, 54 insertions(+), 4 deletions(-)
--
2.52.0
next reply other threads:[~2026-08-16 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 9:04 Yafang Shao [this message]
2026-08-16 9:04 ` [PATCH v2 1/2] livepatch: Fix wrong index in funcs cleanup error path Yafang Shao
2026-08-16 9:04 ` [PATCH v2 2/2] livepatch: Fix UAF of unregistered patch kobjects Yafang Shao
2026-08-19 11:18 ` Petr Mladek
2026-08-19 12:37 ` Yafang Shao
2026-08-19 12:59 ` Petr Mladek
2026-08-19 10:24 ` [PATCH v2 0/2] ivepatch: Fix several bugs found during replace set implementation Petr Mladek
2026-08-20 15:40 ` Josh Poimboeuf
2026-08-21 3:14 ` Yafang Shao
2026-08-21 8:51 ` Petr Mladek
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=20260816090442.18128-1-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=song@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.