From: Miroslav Benes <mbenes@suse.cz>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Wardenjohn <zhangwarden@gmail.com>,
jikos@kernel.org, pmladek@suse.com, joe.lawrence@redhat.com,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] livepatch: Add using attribute to klp_func for using function show
Date: Fri, 6 Sep 2024 08:55:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.2409060851580.1385@pobox.suse.cz> (raw)
In-Reply-To: <20240905163449.ly6gbpizooqwwvt6@treble>
On Thu, 5 Sep 2024, Josh Poimboeuf wrote:
> On Thu, Sep 05, 2024 at 12:23:20PM +0200, Miroslav Benes wrote:
> > I am not a fan. Josh wrote most of my objections already so I will not
> > repeat them. I understand that the attribute might be useful but the
> > amount of code it adds to sensitive functions like
> > klp_complete_transition() is no fun.
> >
> > Would it be possible to just use klp_transition_patch and implement the
> > logic just in using_show()?
>
> Yes, containing the logic to the sysfs file sounds a lot better.
>
> > I have not thought through it completely but
> > klp_transition_patch is also an indicator that there is a transition going
> > on. It is set to NULL only after all func->transition are false. So if you
> > check that, you can assign -1 in using_show() immediately and then just
> > look at the top of func_stack.
>
> sysfs already has per-patch 'transition' and 'enabled' files so I don't
> like duplicating that information.
>
> The only thing missing is the patch stack order. How about a simple
> per-patch file which indicates that?
>
> /sys/kernel/livepatch/<patchA>/order => 1
> /sys/kernel/livepatch/<patchB>/order => 2
>
> The implementation should be trivial with the use of
> klp_for_each_patch() to count the patches.
Yes, it should work as well.
Wardenjohn, you should then get all the information that you need. Also,
please test your patches with livepatch kselftests before a submission
next time. New sysfs attributes need to be documented in
Documentation/ABI/testing/sysfs-kernel-livepatch and there should be a new
kselftest for them.
Thank you,
Miroslav
next prev parent reply other threads:[~2024-09-06 6:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 2:23 [PATCH v4 0/2] livepatch: Add using attribute to klp_func for using function Wardenjohn
2024-08-28 2:23 ` [PATCH v4 1/2] Introduce klp_ops into klp_func structure Wardenjohn
2024-09-05 10:10 ` Miroslav Benes
2024-09-05 14:33 ` zhang warden
2024-09-06 7:03 ` Miroslav Benes
2024-09-06 9:44 ` zhang warden
2024-09-13 9:46 ` zhang warden
2024-08-28 2:23 ` [PATCH v4 2/2] livepatch: Add using attribute to klp_func for using function show Wardenjohn
2024-09-04 1:54 ` zhang warden
2024-09-04 4:48 ` Josh Poimboeuf
2024-09-04 6:34 ` zhang warden
2024-09-04 7:14 ` Josh Poimboeuf
2024-09-04 7:30 ` zhang warden
2024-09-04 18:06 ` Josh Poimboeuf
2024-09-05 14:03 ` zhang warden
2024-09-05 16:30 ` Josh Poimboeuf
2024-09-05 10:23 ` Miroslav Benes
2024-09-05 14:17 ` zhang warden
2024-09-05 16:34 ` Josh Poimboeuf
2024-09-06 6:55 ` Miroslav Benes [this message]
2024-09-06 9:39 ` zhang warden
2024-09-06 16:39 ` Petr Mladek
2024-09-08 2:31 ` zhang warden
2024-09-06 16:13 ` Petr Mladek
2024-09-08 2:51 ` zhang warden
2024-09-10 8:01 ` Petr Mladek
2024-09-10 8:09 ` zhang warden
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=alpine.LSU.2.21.2409060851580.1385@pobox.suse.cz \
--to=mbenes@suse.cz \
--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=pmladek@suse.com \
--cc=zhangwarden@gmail.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
all inboxes | Powered by JetHome®