From: zhang warden <zhangwarden@gmail.com>
To: Marcos Paulo de Souza <mpdesouza@suse.com>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, Jiri Kosina <jikos@kernel.org>,
Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] livepatch: introduce 'stack_order' sysfs interface to klp_patch
Date: Thu, 26 Sep 2024 19:23:44 +0800 [thread overview]
Message-ID: <8A6A3E71-DB43-4305-95FC-202D20B5EC16@gmail.com> (raw)
In-Reply-To: <0fe8f8d36fb5fc78c645b26c20b5ae365bb59991.camel@suse.com>
> On Sep 25, 2024, at 21:08, Marcos Paulo de Souza <mpdesouza@suse.com> wrote:
>
> On Wed, 2024-09-25 at 14:40 +0800, Wardenjohn wrote:
>> 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'.
>
> The approach seems ok to me, but I would like to see selftests for this
> new attribute. We have been trying to add more and more selftests for
> existing known behavior, so IMO adding a new attribute should contain a
> new test to exercise the correct behavior.
>
> Other than that, for the series:
>
> Acked-by: Marcos Paulo de Souza <mpdesouza@suse.com>
>
Hi, Macros!
Thanks a lot.
I will add selftest case for it as soon as possible.
Regards.
Wardenjohn.
(This email is resent because it seemed not sent to LKML...)
prev parent reply other threads:[~2024-09-26 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 6:40 [PATCH 0/2] livepatch: introduce 'stack_order' sysfs interface to klp_patch Wardenjohn
2024-09-25 6:40 ` [PATCH] " Wardenjohn
2024-09-27 14:11 ` Miroslav Benes
2024-09-29 1:51 ` zhang warden
2024-09-29 14:47 ` zhang warden
2024-09-25 6:40 ` [PATCH] Documentation: Add description to stack_order interface Wardenjohn
2024-09-27 13:49 ` Miroslav Benes
2024-09-25 13:08 ` [PATCH 0/2] livepatch: introduce 'stack_order' sysfs interface to klp_patch Marcos Paulo de Souza
2024-09-26 11:23 ` zhang warden [this message]
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=8A6A3E71-DB43-4305-95FC-202D20B5EC16@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=mpdesouza@suse.com \
--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