From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleg Nesterov Subject: Re: [PATCH v7] seccomp, ptrace: add support for dumping seccomp filters Date: Tue, 20 Oct 2015 20:21:41 +0200 Message-ID: <20151020182140.GA32087@redhat.com> References: <1444747626-8129-1-git-send-email-tycho.andersen@canonical.com> <1444747626-8129-2-git-send-email-tycho.andersen@canonical.com> <20151020180024.GA30486@redhat.com> <20151020181511.GN3982@smitten> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20151020181511.GN3982@smitten> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Tycho Andersen Cc: Kees Cook , Alexei Starovoitov , Will Drewry , Andy Lutomirski , Pavel Emelyanov , "Serge E. Hallyn" , Daniel Borkmann , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-api@vger.kernel.org On 10/20, Tycho Andersen wrote: > > If we're going to > unlock right after the checks, we probably don't need the current > task's lock at all. Agreed, current->signal->siglock looks unnecessary. Oleg. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752356AbbJTSZR (ORCPT ); Tue, 20 Oct 2015 14:25:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60120 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751287AbbJTSZO (ORCPT ); Tue, 20 Oct 2015 14:25:14 -0400 Date: Tue, 20 Oct 2015 20:21:41 +0200 From: Oleg Nesterov To: Tycho Andersen Cc: Kees Cook , Alexei Starovoitov , Will Drewry , Andy Lutomirski , Pavel Emelyanov , "Serge E. Hallyn" , Daniel Borkmann , linux-kernel@vger.kernel.org, linux-api@vger.kernel.org Subject: Re: [PATCH v7] seccomp, ptrace: add support for dumping seccomp filters Message-ID: <20151020182140.GA32087@redhat.com> References: <1444747626-8129-1-git-send-email-tycho.andersen@canonical.com> <1444747626-8129-2-git-send-email-tycho.andersen@canonical.com> <20151020180024.GA30486@redhat.com> <20151020181511.GN3982@smitten> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151020181511.GN3982@smitten> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/20, Tycho Andersen wrote: > > If we're going to > unlock right after the checks, we probably don't need the current > task's lock at all. Agreed, current->signal->siglock looks unnecessary. Oleg.