| 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
| ||
|
Message-ID: <alpine.LRH.2.02.1211201445410.1844@tundra.namei.org> Date: Tue, 20 Nov 2012 14:46:35 +1100 (EST) From: James Morris <jmorris@...ei.org> To: Kees Cook <keescook@...omium.org> cc: linux-kernel@...r.kernel.org, James Morris <james.l.morris@...cle.com>, John Johansen <john.johansen@...onical.com>, "Serge E. Hallyn" <serge.hallyn@...ntu.com>, Eric Paris <eparis@...hat.com>, linux-security-module@...r.kernel.org Subject: Re: [PATCH] Yama: remove locking from delete path On Mon, 19 Nov 2012, Kees Cook wrote: > On Mon, Nov 19, 2012 at 6:23 PM, James Morris <jmorris@...ei.org> wrote: > > On Mon, 19 Nov 2012, Kees Cook wrote: > > > >> Instead of locking the list during a delete, mark entries as invalid > >> and trigger a workqueue to clean them up. This lets us easily handle > >> task_free from interrupt context. > >> > >> Cc: Sasha Levin <sasha.levin@...cle.com> > >> Signed-off-by: Kees Cook <keescook@...omium.org> > > > > This doesn't apply cleanly to my -next branch. > > Did you already apply this from last week? > https://lkml.org/lkml/2012/11/13/808 Nope. > > > Kees: can you think about using git to push changes to me for Yama? > > If this pace of changes keeps up, sure thing. In any case, please check that your patches apply cleanly to my -next branch. - James -- James Morris <jmorris@...ei.org> -- 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