Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754461AbZD1WfA (ORCPT ); Tue, 28 Apr 2009 18:35:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753358AbZD1Wev (ORCPT ); Tue, 28 Apr 2009 18:34:51 -0400 Received: from mx2.redhat.com ([66.187.237.31]:50408 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753243AbZD1Weu (ORCPT ); Tue, 28 Apr 2009 18:34:50 -0400 Date: Wed, 29 Apr 2009 00:30:25 +0200 From: Oleg Nesterov To: David Howells , Eric Paris , James Morris , Roland McGrath , Stephen Smalley Cc: linux-kernel@vger.kernel.org Subject: Q: selinux_bprm_committed_creds() && signals/do_wait Message-ID: <20090428223025.GA11997@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: 1257 Lines: 39 selinux_bprm_committed_creds: rc = avc_has_perm() if (rc) { flush_signals(current); This doesn't look right. If the task was SIGKILL'ed we must not proceed, the task should die. The fix is simple, we should check SIGNAL_GROUP_EXIT and do nothing in this case, the task will exit before return to user space. If SIGNAL_GROUP_EXIT is set, it is just wrong to drop SIGKILL and continue. But, before fixing, I'd like to understand why we are doing flush_signal_handlers(current, 1); sigemptyset(¤t->blocked); later. Could someone explain ? This looks unneeded. Another question, wake_up_interruptible(¤t->parent->signal->wait_chldexit); Shouldn't we use ->real_parent ? Afaics, we shouldn't worry about the tracer if current is ptraced, exec must not succeed if the tracer has no rights to trace this task after cred changing. But we should notify ->real_parent which is, well, real parent. Also, we don't need _irq to take tasklist_lock, and we don't actually need ->siglock. 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/