[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190904120336.GC24568@redhat.com>
Date: Wed, 4 Sep 2019 14:03:37 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
paulmck <paulmck@...ux.ibm.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Russell King, ARM Linux" <linux@...linux.org.uk>,
Chris Metcalf <cmetcalf@...hip.com>,
Chris Lameter <cl@...ux.com>, Kirill Tkhai <tkhai@...dex.ru>,
Mike Galbraith <efault@....de>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [RFC PATCH 1/2] Fix: sched/membarrier: p->mm->membarrier_state
racy load
On 09/04, Peter Zijlstra wrote:
>
> + struct task_struct *g, *t;
> +
> + read_lock(&tasklist_lock);
> + do_each_thread(g, t) {
for_each_process_thread() looks better
> + if (t->mm == mm) {
> + atomic_or(MEMBARRIER_STATE_GLOBAL_EXPEDITED,
> + &t->membarrier_state);
> + }
then you also need to change dup_task_struct(), it should clear
->membarrier_state unless CLONE_VM.
And probably unuse_mm() should clear current->membarrier_state too.
Hmm. And it can race with copy_process() anyway, tasklist_lock can't
really help. So copy_process() needs to do
write_lock_irq(&tasklist_lock);
...
if (clone_flags & CLONE_VM)
p->membarrier_state = current->membarrier_state;
else
p->membarrier_state = 0;
Oleg.
Powered by blists - more mailing lists