From: Wardenjohn <zhangwarden@gmail.com>
To: jpoimboe@kernel.org, mbenes@suse.cz, jikos@kernel.org,
pmladek@suse.com, joe.lawrence@redhat.com
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V3 0/1] livepatch: Add "stack_order" sysfs attribute
Date: Sun, 29 Sep 2024 22:43:33 +0800 [thread overview]
Message-ID: <20240929144335.40637-1-zhangwarden@gmail.com> (raw)
As previous discussion, maintainers think that patch-level sysfs interface is the
only acceptable way to maintain the information of the order that klp_patch is
applied to the system.
However, the previous patch introduce klp_ops into klp_func is a optimization
methods of the patch introducing 'using' feature to klp_func.
But now, we don't support 'using' feature to klp_func and make 'klp_ops' patch
not necessary.
Therefore, this new version is only introduce the sysfs feature of klp_patch
'stack_order'.
V1 -> V2:
1. According to the suggestion from Petr, to make the meaning more clear, rename
'order' to 'stack_order'.
2. According to the suggestion from Petr and Miroslav, this patch now move the
calculating process to stack_order_show function. Adding klp_mutex lock protection.
V2 -> V3:
1. Squash 2 patches into 1. Update description of stack_order in ABI Document.
(Suggested by Miroslav)
2. Update subject and commit log. (Suggested by Miroslav)
3. Update code format for some line of the patch. (Suggested by Miroslav)
Regards.
Wardenjohn.
next reply other threads:[~2024-09-29 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 14:43 Wardenjohn [this message]
2024-09-29 14:43 ` [PATCH V3 1/1] livepatch: Add "stack_order" sysfs attribute Wardenjohn
2024-09-30 23:26 ` Josh Poimboeuf
2024-10-03 6:26 ` zhang warden
2024-10-03 11:52 ` Petr Mladek
2024-10-03 14:59 ` zhang warden
2024-10-03 15:25 ` Josh Poimboeuf
2024-10-06 8:32 ` zhang warden
2024-10-02 11:44 ` [PATCH V3 0/1] " Miroslav Benes
2024-10-03 8:09 ` zhang warden
[not found] ` <CADDyLDU4Hsp-FCjocEyfEmY6-JOKeH+YjsBfUr+xbO=opOEhgw@mail.gmail.com>
2024-10-03 11:56 ` 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=20240929144335.40637-1-zhangwarden@gmail.com \
--to=zhangwarden@gmail.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--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