mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Parri <parri.andrea@gmail.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Hyunwoo Kim <imv4bel@gmail.com>, Oleg Nesterov <oleg@redhat.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	John Stultz <jstultz@google.com>, Ingo Molnar <mingo@kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [patch V3 8/8] posix-timers: Handle exit in do_exit() completely
Date: Wed, 16 Sep 2026 22:12:48 +0200	[thread overview]
Message-ID: <aqr4QJgA-G_aoYow@andreayoga.localdomain> (raw)
In-Reply-To: <20260911090541.947206186@kernel.org>

> @@ -167,12 +167,6 @@ static void __exit_signal(struct release
>  					lockdep_tasklist_lock_is_held());
>  	spin_lock(&sighand->siglock);
>  
> -#ifdef CONFIG_POSIX_TIMERS
> -	posix_cpu_timers_exit(tsk);
> -	if (group_dead)
> -		posix_cpu_timers_exit_group(tsk);
> -#endif
> -

Now that __exit_signal() no longer touches the CPU timer queues, does
the block comment above timer_lock_sighand() need an update in the same
patch?  It still credits __exit_signal() with invoking
posix_cpu_timers_exit()/posix_cpu_timers_exit_group().

The barrier diagram further down in timer_lock_sighand() describes the
same old callchain, and it is what the WARN_ON_ONCE() right below the
diagram relies on.  Would it help to spell the new chain out so that the
WARN_ON_ONCE() keeps a documented ordering argument?


> @@ -661,18 +661,29 @@ static void cleanup_timers(struct posix_
>  	cleanup_timerqueue(&pct->bases[CPUCLOCK_SCHED].tqhead);
>  }
>  
> +static inline void posix_cpu_timers_exit_work(void);
> +
>  /*
> - * These are both called with the siglock held, when the current thread
> - * is being reaped.  When the final (leader) thread in the group is reaped,
> - * posix_cpu_timers_exit_group will be called after posix_cpu_timers_exit.
> + * Invoked from posixtimer_exit_task() after PF_EXITING was set in tsk::flags or
> + * from posixtimer_exec_cleanup().

Should these be posixtimer_exit() and posixtimer_exec()?  Neither
posixtimer_exit_task() nor posixtimer_exec_cleanup() exists in the tree.
The callers are posixtimer_exit()->posix_cpu_timers_exit_task(),
posixtimer_exec()->posix_cpu_timers_exit_task() and
posix_cpu_timers_exit_group()->posix_cpu_timers_exit_task().


>   */
> -void posix_cpu_timers_exit(struct task_struct *tsk)
> +void posix_cpu_timers_exit_task(void)
>  {
> -	cleanup_timers(&tsk->posix_cputimers);
> +	posix_cpu_timers_exit_work();
> +
> +	guard(spinlock_irq)(&current->sighand->siglock);
> +	cleanup_timers(&current->posix_cputimers);
>  }
> -void posix_cpu_timers_exit_group(struct task_struct *tsk)
> +
> +/*
> + * Invoked from posixtimer_exit_group() after PF_EXITING was set in tsk::flags.

Same question here: the only caller is posixtimer_exit(), and
posixtimer_exit_group() does not exist.


> + */
> +void posix_cpu_timers_exit_group(void)
>  {
> -	cleanup_timers(&tsk->signal->posix_cputimers);
> +	posix_cpu_timers_exit_task();
> +
> +	guard(spinlock_irq)(&current->sighand->siglock);
> +	cleanup_timers(&current->signal->posix_cputimers);
>  }
>  
>  /*

  Andrea

  parent reply	other threads:[~2026-09-16 20:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  9:09 [patch V3 0/8] exec/exit: POSIX timer related bugfixes and related cleanups Thomas Gleixner
2026-09-11  9:09 ` [patch V3 1/8] signal: Prevent exec() race Thomas Gleixner
2026-09-11 13:08   ` Frederic Weisbecker
2026-09-16 16:48   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2026-09-16 20:37   ` [patch V3 1/8] " Andrea Parri
2026-09-11  9:09 ` [patch V3 2/8] exec: Cleanup POSIX timers right after de_thread() Thomas Gleixner
2026-09-16 16:48   ` [tip: timers/core] " tip-bot2 for Hyunwoo Kim
2026-09-11  9:09 ` [patch V3 3/8] posix-timers: Move posixtimer_exec_cleanup() out of exec.c Thomas Gleixner
2026-09-11 13:58   ` Oleg Nesterov
2026-09-16 16:48   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2026-09-16 20:31   ` [patch V3 3/8] " Andrea Parri
2026-09-11  9:09 ` [patch V3 4/8] posix-timers: Move POSIX timer group exit related code out of do_exit() Thomas Gleixner
2026-09-11 13:59   ` Oleg Nesterov
2026-09-16 16:48   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2026-09-11  9:09 ` [patch V3 5/8] posix-cpu-timers: Move inlines out of public header Thomas Gleixner
2026-09-11 13:59   ` Oleg Nesterov
2026-09-16 16:48   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2026-09-11  9:09 ` [patch V3 6/8] posix-cpu-timers: Use PF_EXITING to indicate exit Thomas Gleixner
2026-09-11 13:15   ` Frederic Weisbecker
2026-09-11 14:00   ` Oleg Nesterov
2026-09-16 16:48   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2026-09-16 20:21   ` [patch V3 6/8] " Andrea Parri
2026-09-11  9:09 ` [patch V3 7/8] posix-cpu-timers: Prevent enqueueing when PF_EXITING is set Thomas Gleixner
2026-09-12 21:09   ` Frederic Weisbecker
2026-09-16 16:48   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2026-09-11  9:09 ` [patch V3 8/8] posix-timers: Handle exit in do_exit() completely Thomas Gleixner
2026-09-11 14:02   ` Oleg Nesterov
2026-09-12 22:17   ` Frederic Weisbecker
2026-09-16 16:48   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2026-09-16 20:12   ` Andrea Parri [this message]
2026-09-12 14:20 ` [patch V3 0/8] exec/exit: POSIX timer related bugfixes and related cleanups Kijo Park

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=aqr4QJgA-G_aoYow@andreayoga.localdomain \
    --to=parri.andrea@gmail.com \
    --cc=brauner@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=frederic@kernel.org \
    --cc=imv4bel@gmail.com \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tglx@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®