All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: brauner@kernel.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] exit: call add_device_randomness() without tasklist_lock
Date: Tue, 28 Jan 2025 16:21:25 +0100	[thread overview]
Message-ID: <20250128152125.GA24845@redhat.com> (raw)
In-Reply-To: <20250128140701.3136924-1-mjguzik@gmail.com>

On 01/28, Mateusz Guzik wrote:
>
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -141,13 +141,14 @@ static void __unhash_process(struct task_struct *p, bool group_dead)
>  /*
>   * This function expects the tasklist_lock write-locked.
>   */
> -static void __exit_signal(struct task_struct *tsk)
> +static unsigned long long __exit_signal(struct task_struct *tsk)
>  {
>  	struct signal_struct *sig = tsk->signal;
>  	bool group_dead = thread_group_leader(tsk);
>  	struct sighand_struct *sighand;
>  	struct tty_struct *tty;
>  	u64 utime, stime;
> +	unsigned long long randomness;
>  
>  	sighand = rcu_dereference_check(tsk->sighand,
>  					lockdep_tasklist_lock_is_held());
> @@ -174,8 +175,7 @@ static void __exit_signal(struct task_struct *tsk)
>  			sig->curr_target = next_thread(tsk);
>  	}
>  
> -	add_device_randomness((const void*) &tsk->se.sum_exec_runtime,
> -			      sizeof(unsigned long long));
> +	randomness = tsk->se.sum_exec_runtime;
>  
>  	/*
>  	 * Accumulate here the counters for all threads as they die. We could
> @@ -214,6 +214,8 @@ static void __exit_signal(struct task_struct *tsk)
>  		flush_sigqueue(&sig->shared_pending);
>  		tty_kref_put(tty);
>  	}
> +
> +	return randomness;
>  }
>  
>  static void delayed_put_task_struct(struct rcu_head *rhp)
> @@ -242,6 +244,7 @@ void release_task(struct task_struct *p)
>  	struct task_struct *leader;
>  	struct pid *thread_pid;
>  	int zap_leader;
> +	unsigned long long randomness;
>  repeat:
>  	/* don't need to get the RCU readlock here - the process is dead and
>  	 * can't be modifying its own credentials. But shut RCU-lockdep up */
> @@ -254,7 +257,7 @@ void release_task(struct task_struct *p)
>  	write_lock_irq(&tasklist_lock);
>  	ptrace_release_task(p);
>  	thread_pid = get_pid(p->thread_pid);
> -	__exit_signal(p);
> +	randomness = __exit_signal(p);
>  
>  	/*
>  	 * If we are the last non-leader member of the thread
> @@ -280,6 +283,8 @@ void release_task(struct task_struct *p)
>  	put_pid(thread_pid);
>  	release_thread(p);
>  	put_task_struct_rcu_user(p);
> +	add_device_randomness((const void*) &randomness,
> +			      sizeof(unsigned long long));
>  
>  	p = leader;
>  	if (unlikely(zap_leader))

Hmm, why not simply shift add_device_randomness(sum_exec_runtime) to
release_release_task() ?

Oleg.

--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -174,9 +174,6 @@ static void __exit_signal(struct task_struct *tsk)
 			sig->curr_target = next_thread(tsk);
 	}
 
-	add_device_randomness((const void*) &tsk->se.sum_exec_runtime,
-			      sizeof(unsigned long long));
-
 	/*
 	 * Accumulate here the counters for all threads as they die. We could
 	 * skip the group leader because it is the last user of signal_struct,
@@ -279,6 +276,8 @@ void release_task(struct task_struct *p)
 	proc_flush_pid(thread_pid);
 	put_pid(thread_pid);
 	release_thread(p);
+	add_device_randomness((const void*)&p->se.sum_exec_runtime,
+			      sizeof(unsigned long long));
 	put_task_struct_rcu_user(p);
 
 	p = leader;


  parent reply	other threads:[~2025-01-28 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 14:07 [PATCH] exit: call add_device_randomness() without tasklist_lock Mateusz Guzik
2025-01-28 14:50 ` Mateusz Guzik
2025-01-28 15:21 ` Oleg Nesterov [this message]
2025-01-28 15:23   ` Mateusz Guzik

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=20250128152125.GA24845@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@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 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.