From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753039Ab3EPRRd (ORCPT ); Thu, 16 May 2013 13:17:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:1371 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752734Ab3EPRRb (ORCPT ); Thu, 16 May 2013 13:17:31 -0400 Date: Thu, 16 May 2013 19:13:37 +0200 From: Oleg Nesterov To: Lucas De Marchi Cc: Andrew Morton , Andi Kleen , Colin Walters , Denys Vlasenko , Jiri Slaby , Lennart Poettering , Neil Horman , security@kernel.org, lkml Subject: Re: [PATCH 1/1] usermodehelper: check subprocess_info->path != NULL Message-ID: <20130516171337.GA24031@redhat.com> References: <20130515201158.GA14606@redhat.com> <20130516154323.GA19060@redhat.com> <20130516154355.GB19060@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 05/16, Lucas De Marchi wrote: > > > > > - kill or justify ->path[0] check > > I'm not sure about this, it's already there before my refactor and I > don't think it makes any good. From modprobe pespective, I'd say it > would be better to give an error than say everything went ok. Agreed. And, I forgot to mention, if we kill this check then we do not need this patch (although I need to recheck), execve will fail and nothing bad should happen. Just I think it would be better to start with the trivial fix, then decide what should we actually do. > Acked-By: Lucas De Marchi Thanks, Oleg.