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: Wed, 20 Feb 2013 14:52:11 +0100 From: Ingo Molnar <mingo@...nel.org> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: Mandeep Singh Baines <msb@...omium.org>, linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>, Tejun Heo <tj@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, Ingo Molnar <mingo@...hat.com> Subject: Re: [PATCH v3] lockdep: check that no locks held at freeze time * Rafael J. Wysocki <rjw@...k.pl> wrote: > On Wednesday, February 20, 2013 11:37:19 AM Ingo Molnar wrote: > > > > * Mandeep Singh Baines <msb@...omium.org> wrote: > > > > > We shouldn't try_to_freeze if locks are held. Verified that > > > I get no lockdep warnings after applying this patch and > > > "vfork: don't freezer_count() for in-kernel users of CLONE_VFORK". > > > > > > Changes since v1: > > > * LKML: <20130215111635.GA26955@...il.com> Ingo Molnar > > > * Added a msg string that gets passed in. > > > * LKML: <20130215154449.GD30829@...hat.com> Oleg Nesterov > > > * Check PF_NOFREEZE in try_to_freeze(). > > > Changes since v2: > > > * LKML: <20130216170605.GC4910@...hat.com> Oleg Nesterov > > > * Avoid unnecessary PF_NOFREEZE check when !CONFIG_LOCKDEP. > > > * Mandeep Singh Baines > > > * Generalize an exit specific printk. > > > > > > Signed-off-by: Mandeep Singh Baines <msb@...omium.org> > > > CC: Oleg Nesterov <oleg@...hat.com> > > > CC: Tejun Heo <tj@...nel.org> > > > CC: Andrew Morton <akpm@...ux-foundation.org> > > > CC: Rafael J. Wysocki <rjw@...k.pl> > > > CC: Ingo Molnar <mingo@...hat.com> > > > > Looks good to me now. > > > > Acked-by: Ingo Molnar <mingo@...nel.org> > > > > Which tree should this go through? > > Well, I can take it if that's OK. Sure, that's fine with me - this is mainly a freezer feature after all. Thanks, Ingo -- 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