Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753387Ab2KTDBI (ORCPT ); Mon, 19 Nov 2012 22:01:08 -0500 Received: from mail-ob0-f174.google.com ([209.85.214.174]:56655 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752869Ab2KTDBG (ORCPT ); Mon, 19 Nov 2012 22:01:06 -0500 MIME-Version: 1.0 In-Reply-To: References: <20121119233459.GA9524@www.outflux.net> Date: Mon, 19 Nov 2012 19:01:04 -0800 X-Google-Sender-Auth: NlUWATeFFFCQ_ipu52cIARgxCm8 Message-ID: Subject: Re: [PATCH] Yama: remove locking from delete path From: Kees Cook To: James Morris Cc: linux-kernel@vger.kernel.org, James Morris , John Johansen , "Serge E. Hallyn" , Eric Paris , linux-security-module@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 940 Lines: 31 On Mon, Nov 19, 2012 at 6:23 PM, James Morris 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 >> Signed-off-by: Kees Cook > > 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 > Kees: can you think about using git to push changes to me for Yama? If this pace of changes keeps up, sure thing. Thanks! -Kees -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/