[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZxozmnCyYpRI2t2Y@localhost.localdomain>
Date: Thu, 24 Oct 2024 13:46:34 +0200
From: Frederic Weisbecker <frederic@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
Anna-Maria Behnsen <anna-maria@...utronix.de>,
John Stultz <jstultz@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>, Stephen Boyd <sboyd@...nel.org>,
Eric Biederman <ebiederm@...ssion.com>,
Oleg Nesterov <oleg@...hat.com>
Subject: Re: [patch V5 05/26] posix-timers: Drop signal if timer has been
deleted or reprogrammed
Le Thu, Oct 24, 2024 at 10:40:08AM +0200, Thomas Gleixner a écrit :
> On Mon, Oct 21 2024 at 14:29, Frederic Weisbecker wrote:
> > Le Tue, Oct 01, 2024 at 10:42:06AM +0200, Thomas Gleixner a écrit :
> >> No point in delivering a signal from the past. POSIX does not specify the
> >> behaviour here:
> >>
> >> - "The effect of disarming or resetting a timer with pending expiration
> >> notifications is unspecified."
> >>
> >> - "The disposition of pending signals for the deleted timer is unspecified."
> >>
> >> In both cases it is reasonable to expect that pending signals are
> >> discarded. Especially in the reprogramming case it does not make sense to
> >> account for previous overruns or to deliver a signal for a timer which has
> >> been disarmed.
> >
> > The change below indeed checks if the timer has been deleted but not if
> > it has been reprogrammed/disarmed/reset.
> >
> > Or am I missing something?
>
> No. You are right. This is a change log left over from a previous
> version. This rearm/disarm part is handled later in the series.
Right, I realized that after. Anyway:
Reviewed-by: Frederic Weisbecker <frederic@...nel.org>
>
> Thanks,
>
> tglx
Powered by blists - more mailing lists