Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750919AbbEDQq0 (ORCPT ); Mon, 4 May 2015 12:46:26 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48892 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750779AbbEDQqQ (ORCPT ); Mon, 4 May 2015 12:46:16 -0400 Date: Mon, 4 May 2015 18:45:35 +0200 From: Oleg Nesterov To: Andrew Morton , Ingo Molnar Cc: Linus Torvalds , Neil Brown , Evgeniy Polyakov , Stephen Smalley , Alex Williamson , linux-kernel , kvm , Paul Moore , Eric Paris Subject: [PATCH 0/1] signals: don't abuse __flush_signals() in selinux_bprm_committed_creds() Message-ID: <20150504164535.GA10118@redhat.com> References: <1430502057.4472.255.camel@redhat.com> <20150501193813.GA2812@gmail.com> <20150503173401.GA22052@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150503173401.GA22052@redhat.com> 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 Content-Length: 689 Lines: 24 On 05/03, Oleg Nesterov wrote: > > On 05/01, Ingo Molnar wrote: > > > > > I also found a __flush_signals() use in: > > > > security/selinux/hooks.c > > > and I simply can't understand this code... but I feel that it can't > be correct ;) Will try to re-read tomorrow. Yes, this doesn't look right. Lets kill __flush_signals() first, there are no other users. And I am not sure it is fine to flush SIGSTOP... do we really want this? Oleg. -- 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/