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
| ||
|
Date: Fri, 6 Feb 2015 23:14:53 -0800 From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> To: Rik van Riel <riel@...hat.com> Cc: Frederic Weisbecker <fweisbec@...il.com>, kvm@...r.kernel.org, borntraeger@...ibm.com, linux-kernel@...r.kernel.org, mtosatti@...hat.com, mingo@...nel.orgm, ak@...ux.intel.com, oleg@...hat.com, masami.hiramatsu.pt@...achi.com, lcapitulino@...hat.com, pbonzini@...hat.com Subject: Re: [PATCH 1/5] rcu,nohz: add state parameter to context_tracking_user_enter/exit On Fri, Feb 06, 2015 at 10:34:21PM -0800, Paul E. McKenney wrote: > On Fri, Feb 06, 2015 at 10:53:34PM -0500, Rik van Riel wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On 02/06/2015 06:15 PM, Frederic Weisbecker wrote: > > > > > Just a few things then: > > > > > > 1) In this case rename context_tracking_user_enter/exit() to > > > context_tracking_enter() and context_tracking_exit(), since it's > > > not anymore about user only but about any generic context. > > > > > > 2) We have the "WARN_ON_ONCE(!current->mm);" condition that is a > > > debug check specific to userspace transitions because kernel > > > threads aren't expected to resume to userspace. Can we also expect > > > that we never switch to/from guest from a kernel thread? AFAICS > > > this happens from an ioctl (thus user task) in x86 for kvm. But I > > > only know this case. > > > > > > 3) You might want to update a few comments that assume we only deal > > > with userspace transitions. > > > > > > 4) trace_user_enter/exit() should stay user-transitions specific. > > > > Paul, would you like me to send follow-up patches with the cleanups > > suggested by Frederic, or would you prefer me to send a new series > > with the cleanups integrated? > > I would prefer a new series, in order to prevent possible future > confusion. Of course, if Frederic would rather push them himself, I am fine with that. And in that case, you should ask him for his preferences, which just might differ from mine. ;-) Thanx, Paul -- 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/
Powered by blists - more mailing lists