From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [GIT pull] timers/urgent for v5.15-rc3
Date: Sun, 26 Sep 2021 12:30:07 +0200 (CEST) [thread overview]
Message-ID: <163265189373.178609.1258692845178002939.tglx@xen13> (raw)
In-Reply-To: 163265189226.178609.9712455554034472888.tglx@xen13
Linus,
please pull the latest timers/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-2021-09-26
up to: 8cd9da85d2bd: posix-cpu-timers: Prevent spuriously armed 0-value itimer
A single fix for the recently introduced regression in posix CPU timers
which failed to stop the timer when requested. That caused unexpected
signals to be sent to the process/thread causing malfunction.
Thanks,
tglx
------------------>
Frederic Weisbecker (1):
posix-cpu-timers: Prevent spuriously armed 0-value itimer
kernel/time/posix-cpu-timers.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/time/posix-cpu-timers.c b/kernel/time/posix-cpu-timers.c
index ee736861b18f..643d412ac623 100644
--- a/kernel/time/posix-cpu-timers.c
+++ b/kernel/time/posix-cpu-timers.c
@@ -1404,7 +1404,8 @@ void set_process_cpu_timer(struct task_struct *tsk, unsigned int clkid,
}
}
- *newval += now;
+ if (*newval)
+ *newval += now;
}
/*
next prev parent reply other threads:[~2021-09-26 10:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 10:30 [GIT pull] irq/urgent for v5.15-rc3 Thomas Gleixner
2021-09-26 10:30 ` Thomas Gleixner [this message]
2021-09-26 17:27 ` [GIT pull] timers/urgent " pr-tracker-bot
2021-09-26 10:30 ` [GIT pull] x86/urgent " Thomas Gleixner
2021-09-26 17:21 ` Linus Torvalds
2021-09-26 18:15 ` Borislav Petkov
2021-09-26 19:10 ` Linus Torvalds
2021-09-28 17:56 ` Borislav Petkov
2021-09-28 20:13 ` Linus Torvalds
2021-09-28 20:41 ` Borislav Petkov
2021-09-28 22:44 ` Linus Torvalds
2021-09-29 18:10 ` [PATCH] x86/insn: Use get_unaligned() instead of memcpy() Borislav Petkov
2021-09-30 0:00 ` Masami Hiramatsu
2021-10-04 9:48 ` [tip: x86/misc] " tip-bot2 for Borislav Petkov
2021-10-06 10:02 ` tip-bot2 for Borislav Petkov
2021-09-26 17:27 ` [GIT pull] x86/urgent for v5.15-rc3 pr-tracker-bot
2021-09-26 17:27 ` [GIT pull] irq/urgent " pr-tracker-bot
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=163265189373.178609.1258692845178002939.tglx@xen13 \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).