linux-kernel - [PATCH 0/2] sched: static_key sched

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <cover.1404315388.git.jbaron@akamai.com>
Date:	Wed,  2 Jul 2014 15:52:38 +0000 (GMT)
From:	Jason Baron <jbaron@...mai.com>
To:	peterz@...radead.org, mingo@...nel.org
Cc:	linux-kernel@...r.kernel.org, andi@...stfloor.org,
	rostedt@...dmis.org
Subject: [PATCH 0/2] sched: static_key sched_feat race + cleanup

Hi,

Andi Kleen previously pointed out a get/set race in the sched_feat()
infrastructure. I had previously proposed to address this with a new
static_key set_true/set_false API:

http://www.gossamer-threads.com/lists/linux/kernel/1955879

However, I think its simpler to just add higher level locking as
Ingo previously suggested, and that is how other consumers of the
this interface are already operating. It seems a bit like overkill
to add this new API, just for this one case.

So, this locking change is in patch 2. Patch 1 is a small cleanup, but
no functional change.

Thanks,

-Jason

Jason Baron (2):
  sched: remove extra static_key function indirection
  sched: fix static_key race with sched_feat

 kernel/sched/core.c  |  5 +++++
 kernel/sched/sched.h | 12 +-----------
 2 files changed, 6 insertions(+), 11 deletions(-)

-- 
1.8.2.rc2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/