Live Patching
 help / color / mirror / Atom feed
From: Joe Lawrence <joe.lawrence@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>,
	jpoimboe@redhat.com, jikos@kernel.org, pmladek@suse.com
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
	axboe@kernel.dk
Subject: Re: [PATCH v2] livepatch: Replace the fake signal sending with TIF_NOTIFY_SIGNAL infrastructure
Date: Mon, 29 Mar 2021 09:45:37 -0400	[thread overview]
Message-ID: <c6dd4315-2e90-8786-e5ec-a377ac8c12f9@redhat.com> (raw)
In-Reply-To: <20210329132815.10035-1-mbenes@suse.cz>

On 3/29/21 9:28 AM, Miroslav Benes wrote:
> Livepatch sends a fake signal to all remaining blocking tasks of a
> running transition after a set period of time. It uses TIF_SIGPENDING
> flag for the purpose. Commit 12db8b690010 ("entry: Add support for
> TIF_NOTIFY_SIGNAL") added a generic infrastructure to achieve the same.
> Replace our bespoke solution with the generic one.
> 
> Reviewed-by: Jens Axboe <axboe@kernel.dk>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
> Signed-off-by: Miroslav Benes <mbenes@suse.cz>
> ---
> v2:
> - #include from kernel/signal.c removed [Petr]
> 
>   kernel/livepatch/transition.c | 5 ++---
>   kernel/signal.c               | 4 +---
>   2 files changed, 3 insertions(+), 6 deletions(-)
> 
> diff --git a/kernel/livepatch/transition.c b/kernel/livepatch/transition.c
> index f6310f848f34..3a4beb9395c4 100644
> --- a/kernel/livepatch/transition.c
> +++ b/kernel/livepatch/transition.c
> @@ -9,6 +9,7 @@
>   
>   #include <linux/cpu.h>
>   #include <linux/stacktrace.h>
> +#include <linux/tracehook.h>
>   #include "core.h"
>   #include "patch.h"
>   #include "transition.h"
> @@ -369,9 +370,7 @@ static void klp_send_signals(void)
>   			 * Send fake signal to all non-kthread tasks which are
>   			 * still not migrated.
>   			 */
> -			spin_lock_irq(&task->sighand->siglock);
> -			signal_wake_up(task, 0);
> -			spin_unlock_irq(&task->sighand->siglock);
> +			set_notify_signal(task);
>   		}
>   	}
>   	read_unlock(&tasklist_lock);
> diff --git a/kernel/signal.c b/kernel/signal.c
> index f2a1b898da29..604290a8ca89 100644
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -43,7 +43,6 @@
>   #include <linux/cn_proc.h>
>   #include <linux/compiler.h>
>   #include <linux/posix-timers.h>
> -#include <linux/livepatch.h>
>   #include <linux/cgroup.h>
>   #include <linux/audit.h>
>   
> @@ -181,8 +180,7 @@ void recalc_sigpending_and_wake(struct task_struct *t)
>   
>   void recalc_sigpending(void)
>   {
> -	if (!recalc_sigpending_tsk(current) && !freezing(current) &&
> -	    !klp_patch_pending(current))
> +	if (!recalc_sigpending_tsk(current) && !freezing(current))
>   		clear_thread_flag(TIF_SIGPENDING);
>   
>   }
> 

Looks good to me.  Thanks for checking on this and updating.

Acked-by: Joe Lawrence <joe.lawrence@redhat.com>

-- Joe


  reply	other threads:[~2021-03-29 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 13:28 [PATCH v2] livepatch: Replace the fake signal sending with TIF_NOTIFY_SIGNAL infrastructure Miroslav Benes
2021-03-29 13:45 ` Joe Lawrence [this message]
2021-03-30  7:41 ` Jiri Kosina

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=c6dd4315-2e90-8786-e5ec-a377ac8c12f9@redhat.com \
    --to=joe.lawrence@redhat.com \
    --cc=axboe@kernel.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox