From: Ming Lei <ming.lei@redhat.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
live-patching@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Ming Lei <ming.lei@redhat.com>
Subject: [PATCH V2 0/3] livepatch: cleanup kpl_patch kobject release
Date: Mon, 1 Nov 2021 08:31:29 +0800 [thread overview]
Message-ID: <20211101003132.3336497-1-ming.lei@redhat.com> (raw)
Hello,
The 1st patch moves module_put() to release handler of klp_patch
kobject.
The 2nd patch changes to free klp_patch and other kobjects without
klp_mutex.
The 3rd patch switches to synchronous kobject release for klp_patch.
V2:
- remove enabled attribute before deleting this klp_patch kobject,
for avoiding deadlock in deleting me
Ming Lei (3):
livepatch: remove 'struct completion finish' from klp_patch
livepatch: free klp_patch object without holding klp_mutex
livepatch: free klp_patch object synchronously
include/linux/livepatch.h | 2 --
kernel/livepatch/core.c | 67 ++++++++++++++++-------------------
kernel/livepatch/core.h | 3 +-
kernel/livepatch/transition.c | 23 ++++++++----
kernel/livepatch/transition.h | 2 +-
5 files changed, 50 insertions(+), 47 deletions(-)
--
2.31.1
next reply other threads:[~2021-11-01 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 0:31 Ming Lei [this message]
2021-11-01 0:31 ` [PATCH V2 1/3] livepatch: remove 'struct completion finish' from klp_patch Ming Lei
2021-11-01 0:31 ` [PATCH V2 2/3] livepatch: free klp_patch object without holding klp_mutex Ming Lei
2021-11-01 0:31 ` [PATCH V2 3/3] livepatch: free klp_patch object synchronously Ming Lei
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=20211101003132.3336497-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=pmladek@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).