From: Petr Mladek <pmladek@suse.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
Miroslav Benes <mbenes@suse.cz>, Yannick Cote <ycote@redhat.com>,
Dennis Li <denli@redhat.com>
Subject: Re: [PATCH] selftests/livepatch: normalize sysctl error message
Date: Fri, 23 Sep 2022 15:46:49 +0200 [thread overview]
Message-ID: <Yy24yV+xd9KTBMBb@alley> (raw)
In-Reply-To: <20220811212138.182575-1-joe.lawrence@redhat.com>
On Thu 2022-08-11 17:21:38, Joe Lawrence wrote:
> The livepatch kselftests rely on comparing expected and actual output
> from such commands as sysctl. A recent commit in procps-ng v4.0.0 [1]
> changed sysctl's output to emit key pathnames like:
>
> sysctl: setting key "/proc/sys/kernel/ftrace_enabled": Device or resource busy
>
> versus previous dotted output:
>
> sysctl: setting key "kernel.ftrace_enabled": Device or resource busy
>
> The modification in output was later reverted [2], but since the change
> has been tagged in procps-ng v4.0.0, update the livepatch kselftest to
> handle either case.
>
> [1] https://gitlab.com/procps-ng/procps/-/commit/6389deca5bf667f5fab5912acde78ba8e0febbc7
> [2] https://gitlab.com/procps-ng/procps/-/commit/b159c198c9160a8eb13254e2b631d0035b9b542c
>
> Reported-by: Dennis(Zhuoheng) Li <denli@redhat.com>
> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
JFYI, the patch has been committed into livepatching.git, branch
for-6.1/fixes.
Best Regards,
Petr
prev parent reply other threads:[~2022-09-23 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 21:21 [PATCH] selftests/livepatch: normalize sysctl error message Joe Lawrence
2022-08-19 5:59 ` Kamalesh Babulal
2022-09-23 13:46 ` 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=Yy24yV+xd9KTBMBb@alley \
--to=pmladek@suse.com \
--cc=denli@redhat.com \
--cc=joe.lawrence@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=ycote@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).