public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: linux-kernel@vger.kernel.org, dvyukov@google.com,
	mingo@kernel.org, peterz@infradead.org, sasha.levin@oracle.com,
	torvalds@linux-foundation.org, hpa@zytor.com, tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/core] sched/core: Fix unserialized r-m-w scribbling stuff
Date: Wed, 6 Jan 2016 15:17:23 -0500	[thread overview]
Message-ID: <20160106201723.GH3660@htj.duckdns.org> (raw)
In-Reply-To: <tip-be958bdc96f18bc1356177bbb79d46ea0c037b96@git.kernel.org>

On Wed, Jan 06, 2016 at 10:48:15AM -0800, tip-bot for Peter Zijlstra wrote:
> Commit-ID:  be958bdc96f18bc1356177bbb79d46ea0c037b96
> Gitweb:     http://git.kernel.org/tip/be958bdc96f18bc1356177bbb79d46ea0c037b96
> Author:     Peter Zijlstra <peterz@infradead.org>
> AuthorDate: Wed, 25 Nov 2015 16:02:07 +0100
> Committer:  Ingo Molnar <mingo@kernel.org>
> CommitDate: Wed, 6 Jan 2016 11:01:07 +0100
> 
> sched/core: Fix unserialized r-m-w scribbling stuff
> 
> Some of the sched bitfieds (notably sched_reset_on_fork) can be set
> on other than current, this can cause the r-m-w to race with other
> updates.
> 
> Since all the sched bits are serialized by scheduler locks, pull them
> in a separate word.
> 
> Reported-by: Tejun Heo <tj@kernel.org>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Cc: Dmitry Vyukov <dvyukov@google.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Sasha Levin <sasha.levin@oracle.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: akpm@linux-foundation.org
> Cc: hannes@cmpxchg.org
> Cc: mhocko@kernel.org
> Cc: vdavydov@parallels.com
> Link: http://lkml.kernel.org/r/20151125150207.GM11639@twins.programming.kicks-ass.net
> Signed-off-by: Ingo Molnar <mingo@kernel.org>

cc stable?

-- 
tejun

      reply	other threads:[~2016-01-06 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151125150207.GM11639@twins.programming.kicks-ass.net>
2016-01-06 18:48 ` [tip:sched/core] sched/core: Fix unserialized r-m-w scribbling stuff tip-bot for Peter Zijlstra
2016-01-06 20:17   ` Tejun Heo [this message]

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=20160106201723.GH3660@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=dvyukov@google.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sasha.levin@oracle.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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