From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT pull] timers/urgent for v5.16-rc1
Date: Mon, 15 Nov 2021 17:07:20 +0100 [thread overview]
Message-ID: <YZKFuE0gpdlTiBOv@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <YZKCBqmb1gfKvFcR@hirez.programming.kicks-ass.net>
On Mon, Nov 15, 2021 at 04:51:34PM +0100, Peter Zijlstra wrote:
> diff --git a/kernel/time/posix-cpu-timers.c b/kernel/time/posix-cpu-timers.c
> index 96b4e7810426..3352759e6916 100644
> --- a/kernel/time/posix-cpu-timers.c
> +++ b/kernel/time/posix-cpu-timers.c
> @@ -1167,8 +1167,6 @@ void clear_posix_cputimers_work(struct task_struct *p)
> * A copied work entry from the old task is not meaningful, clear it.
> * N.B. init_task_work will not do this.
> */
> - memset(&p->posix_cputimers_work.work, 0,
> - sizeof(p->posix_cputimers_work.work));
Also, clearly that comments needs to go..
> init_task_work(&p->posix_cputimers_work.work,
> posix_cpu_timers_work);
> p->posix_cputimers_work.scheduled = false;
next prev parent reply other threads:[~2021-11-15 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 13:30 [GIT pull] irq/urgent for v5.16-rc1 Thomas Gleixner
2021-11-14 13:30 ` [GIT pull] locking/urgent " Thomas Gleixner
2021-11-14 19:10 ` pr-tracker-bot
2021-11-14 13:30 ` [GIT pull] timers/urgent " Thomas Gleixner
2021-11-14 19:02 ` Linus Torvalds
2021-11-14 19:24 ` Thomas Gleixner
2021-11-15 15:51 ` Peter Zijlstra
2021-11-15 16:07 ` Peter Zijlstra [this message]
2021-11-15 17:55 ` Linus Torvalds
2021-11-14 19:10 ` pr-tracker-bot
2021-11-14 19:10 ` [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=YZKFuE0gpdlTiBOv@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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