All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Lawrence <joe.lawrence@redhat.com>
To: Petr Mladek <pmladek@suse.com>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Jessica Yu <jeyu@kernel.org>, Jiri Kosina <jikos@kernel.org>,
	Miroslav Benes <mbenes@suse.cz>,
	Chris J Arges <chris.j.arges@canonical.com>
Subject: Re: [PATCH v5 3/3] livepatch: add transition notices
Date: Wed, 27 Sep 2017 11:45:26 -0400	[thread overview]
Message-ID: <c00cbd75-83f4-dcd7-a3cf-4691a0df7f62@redhat.com> (raw)
In-Reply-To: <20170927114908.GM21048@pathway.suse.cz>

On 09/27/2017 07:49 AM, Petr Mladek wrote:
> On Thu 2017-08-31 10:53:53, Joe Lawrence wrote:
>> Log a few kernel debug messages at the beginning of the following livepatch
>> transition functions:
>>
>>   klp_complete_transition()
>>   klp_cancel_transition()
>>   klp_init_transition()
>>   klp_reverse_transition()
>>
>> Also update the log notice message in klp_start_transition() for similar
>> verbiage as the above messages.
>>
>> Suggested-by: Josh Poimboeuf <jpoimboe@redhat.com>
>> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
>> ---
>>  kernel/livepatch/transition.c | 18 +++++++++++++++++-
>>  1 file changed, 17 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/livepatch/transition.c b/kernel/livepatch/transition.c
>> index 53887f0bca10..3d44a3cf27be 100644
>> --- a/kernel/livepatch/transition.c
>> +++ b/kernel/livepatch/transition.c
>> @@ -82,6 +82,10 @@ static void klp_complete_transition(void)
>>  	unsigned int cpu;
>>  	bool immediate_func = false;
>>  
>> +	pr_debug("'%s': completing %s transition\n",
>> +		 klp_transition_patch->mod->name,
>> +		 klp_target_state == KLP_PATCHED ? "patching" : "unpatching");
>> +
>>  	if (klp_target_state == KLP_UNPATCHED) {
>>  		/*
>>  		 * All tasks have transitioned to KLP_UNPATCHED so we can now
>> @@ -163,6 +167,9 @@ void klp_cancel_transition(void)
>>  	if (WARN_ON_ONCE(klp_target_state != KLP_PATCHED))
>>  		return;
>>  
>> +	pr_debug("'%s': canceling transition, unpatching\n",
> 
> This sentence is a bit confusing. It is related to the Mirek's concern
> about that the following message would be "completing unpatching transition".
> 
> What about using something like:
> 
> 	pr_debug("'%s': canceling patching transition, going to unpatch\n",
> 
> 
> Best Regards,
> Petr

Yeah, what I had was more of a comma splice for brevity... no problem
adopting a clearer wording as you suggested.

Thanks

-- Joe

      reply	other threads:[~2017-09-27 15:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 14:53 [PATCH v5 0/3] livepatch callbacks Joe Lawrence
2017-08-31 14:53 ` [PATCH v5 1/3] livepatch: add (un)patch callbacks Joe Lawrence
2017-09-12  8:53   ` Miroslav Benes
2017-09-12 15:48     ` Joe Lawrence
2017-09-12 22:05       ` Joe Lawrence
2017-09-12 22:22         ` Josh Poimboeuf
2017-09-13  7:29           ` Miroslav Benes
2017-09-13 13:53             ` Joe Lawrence
2017-09-13 21:36               ` [RFC] livepatch: unpatch all klp_objects if klp_module_coming fails Joe Lawrence
2017-09-20 11:19                 ` Miroslav Benes
2017-09-20 15:17                   ` Joe Lawrence
2017-09-27 12:17                 ` Petr Mladek
2017-09-13  7:22       ` [PATCH v5 1/3] livepatch: add (un)patch callbacks Miroslav Benes
2017-09-26 14:49   ` Petr Mladek
2017-09-26 19:01     ` Joe Lawrence
2017-09-27  8:02       ` Petr Mladek
2017-08-31 14:53 ` [PATCH v5 2/3] livepatch: move transition "complete" notice into klp_complete_transition() Joe Lawrence
2017-09-12  9:09   ` Miroslav Benes
2017-09-27 11:35   ` Petr Mladek
2017-08-31 14:53 ` [PATCH v5 3/3] livepatch: add transition notices Joe Lawrence
2017-09-12  9:29   ` Miroslav Benes
2017-09-27 11:49   ` Petr Mladek
2017-09-27 15:45     ` Joe Lawrence [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=c00cbd75-83f4-dcd7-a3cf-4691a0df7f62@redhat.com \
    --to=joe.lawrence@redhat.com \
    --cc=chris.j.arges@canonical.com \
    --cc=jeyu@kernel.org \
    --cc=jikos@kernel.org \
    --cc=jpoimboe@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.