From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: ebiederm@xmission.com, oleg@redhat.com, brauner@kernel.org,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/5] pid: sprinkle tasklist_lock asserts
Date: Wed, 5 Feb 2025 15:26:59 -0500 [thread overview]
Message-ID: <wzbq4zk7uln5pzjkho4olu3hku2xv2taxymv3ien437tjxivlm@sz5kxj5oohsq> (raw)
In-Reply-To: <20250205193221.402150-4-mjguzik@gmail.com>
* Mateusz Guzik <mjguzik@gmail.com> [250205 14:33]:
If a patch is worth doing, it's worth explaining. I'm surprised you
didn't add a comment after the last revision missed a comment on patch
2/6. This is literally in the submitting patches document [1].
I don't mean to delay this series, but I do want to know why things are
done when I'm hunting through git logs. Having a change log isn't
optional, and now you know that Andrews script won't fix this problem
[2].
I see you are upset by this considering the terse and lack of
punctuation in patch 2, but please try to understand these comments
serve a purpose in maintaining the code years later.
[1]. https://www.kernel.org/doc/html/v6.12/process/submitting-patches.html#describe-your-changes
[2]. https://lore.kernel.org/all/20250203175128.80319b42c9739f0d420080a4@linux-foundation.org/
> Reviewed-by: Oleg Nesterov <oleg@redhat.com>
> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
> ---
> kernel/pid.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/pid.c b/kernel/pid.c
> index 924084713be8..2ae872f689a7 100644
> --- a/kernel/pid.c
> +++ b/kernel/pid.c
> @@ -339,17 +339,23 @@ static struct pid **task_pid_ptr(struct task_struct *task, enum pid_type type)
> */
> void attach_pid(struct task_struct *task, enum pid_type type)
> {
> - struct pid *pid = *task_pid_ptr(task, type);
> + struct pid *pid;
> +
> + lockdep_assert_held_write(&tasklist_lock);
> +
> + pid = *task_pid_ptr(task, type);
> hlist_add_head_rcu(&task->pid_links[type], &pid->tasks[type]);
> }
>
> static void __change_pid(struct task_struct *task, enum pid_type type,
> struct pid *new)
> {
> - struct pid **pid_ptr = task_pid_ptr(task, type);
> - struct pid *pid;
> + struct pid **pid_ptr, *pid;
> int tmp;
>
> + lockdep_assert_held_write(&tasklist_lock);
> +
> + pid_ptr = task_pid_ptr(task, type);
> pid = *pid_ptr;
>
> hlist_del_rcu(&task->pid_links[type]);
> @@ -386,6 +392,8 @@ void exchange_tids(struct task_struct *left, struct task_struct *right)
> struct hlist_head *head1 = &pid1->tasks[PIDTYPE_PID];
> struct hlist_head *head2 = &pid2->tasks[PIDTYPE_PID];
>
> + lockdep_assert_held_write(&tasklist_lock);
> +
> /* Swap the single entry tid lists */
> hlists_swap_heads_rcu(head1, head2);
>
> @@ -403,6 +411,7 @@ void transfer_pid(struct task_struct *old, struct task_struct *new,
> enum pid_type type)
> {
> WARN_ON_ONCE(type == PIDTYPE_PID);
> + lockdep_assert_held_write(&tasklist_lock);
> hlist_replace_rcu(&old->pid_links[type], &new->pid_links[type]);
> }
>
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2025-02-05 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 19:32 [PATCH v4 0/5] reduce tasklist_lock hold time on exit and do some pid cleanup Mateusz Guzik
2025-02-05 19:32 ` [PATCH v4 1/5] exit: perform add_device_randomness() without tasklist_lock Mateusz Guzik
2025-02-05 19:55 ` Oleg Nesterov
2025-02-05 20:00 ` Mateusz Guzik
2025-02-05 19:32 ` [PATCH v4 2/5] exit: hoist get_pid() in release_task() outside of tasklist_lock Mateusz Guzik
2025-02-05 19:32 ` [PATCH v4 3/5] pid: sprinkle tasklist_lock asserts Mateusz Guzik
2025-02-05 20:26 ` Liam R. Howlett [this message]
2025-02-05 20:34 ` Mateusz Guzik
2025-02-05 20:42 ` Liam R. Howlett
2025-02-05 20:58 ` Mateusz Guzik
2025-02-05 19:32 ` [PATCH v4 4/5] pid: perform free_pid() calls outside of tasklist_lock Mateusz Guzik
2025-02-05 19:32 ` [PATCH v4 5/5] pid: drop irq disablement around pidmap_lock 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=wzbq4zk7uln5pzjkho4olu3hku2xv2taxymv3ien437tjxivlm@sz5kxj5oohsq \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjguzik@gmail.com \
--cc=oleg@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