public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Song Liu <song@kernel.org>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
	jpoimboe@kernel.org, jikos@kernel.org, mbenes@suse.cz,
	joe.lawrence@redhat.com
Subject: Re: [PATCH v3 0/2] add sysfs entry "patched" for each klp_object
Date: Fri, 23 Sep 2022 16:50:36 +0200	[thread overview]
Message-ID: <Yy3HvGe/kcW2OCam@alley> (raw)
In-Reply-To: <20220902205208.3117798-1-song@kernel.org>

On Fri 2022-09-02 13:52:06, Song Liu wrote:
> I was debugging an issue that a livepatch appears to be attached, but
> actually not. It turns out that there is a mismatch in module name
> (abc-xyz vs. abc_xyz), klp_find_object_module failed to find the module.
> Add a sysfs entry for each klp_object, so that it is easier to debug
> such issues.
> 
> Changes v2 => v3:
> 1. Improve selftest. (Petr Mladek and Joe Lawrence)
> 
> Changes v1 => v2:
> 1. Add selftest. (Petr Mladek)
> 2. Update documentation. (Petr Mladek)
> 3. Use sysfs_emit. (Petr Mladek)
> 
> Song Liu (2):
>   livepatch: add sysfs entry "patched" for each klp_object
>   selftests/livepatch: add sysfs test

For both patches:

Reviewed-by: Petr Mladek <pmladek@suse.com>

And I have pushed the patchset into livepatching.git,
for-6.1/sysfs-patched-object.

Best Regards,
Petr

      parent reply	other threads:[~2022-09-23 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 20:52 [PATCH v3 0/2] add sysfs entry "patched" for each klp_object Song Liu
2022-09-02 20:52 ` [PATCH v3 1/2] livepatch: " Song Liu
2022-09-23 14:59   ` Petr Mladek
2022-09-02 20:52 ` [PATCH v3 2/2] selftests/livepatch: add sysfs test Song Liu
2022-09-23 14:50 ` Petr Mladek [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=Yy3HvGe/kcW2OCam@alley \
    --to=pmladek@suse.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox