linux-kernel - Re: [PATCH] context_tracking: Restore previous state in schedule

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Dec 2014 18:31:23 -0500
From:	Dave Jones <davej@...hat.com>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Richard Guy Briggs <rgb@...hat.com>,
	Eric Paris <eparis@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH] context_tracking: Restore previous state in schedule_user

On Wed, Dec 03, 2014 at 03:18:41PM -0800, Andy Lutomirski wrote:
 > It appears that some SCHEDULE_USER (asm for schedule_user) callers
 > in arch/x86/kernel/entry_64.S are called from RCU kernel context,
 > and schedule_user will return in RCU user context.  This causes RCU
 > warnings and possible failures.
 > 
 > This is intended to be a minimal fix suitable for 3.18.
 > 
 > Reported-by: Dave Jones <davej@...hat.com>
 > Cc: Oleg Nesterov <oleg@...hat.com>
 > Cc: Frédéric Weisbecker <fweisbec@...il.com>
 > Cc: Paul McKenney <paulmck@...ux.vnet.ibm.com>
 > Signed-off-by: Andy Lutomirski <luto@...capital.net>
 > ---
 > 
 > Hi all-
 > 
 > This is intended to be a suitable last-minute fix for the RCU issue that
 > Dave saw.
 > 
 > Dave, can you confirm that this fixes it?

ACK, feel free to add my Tested-by:

	Dave
--
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/