From owner-cvs-all@FreeBSD.ORG Fri Mar 12 14:33:23 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F0A16A4CE; Fri, 12 Mar 2004 14:33:23 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EADAA43D39; Fri, 12 Mar 2004 14:33:22 -0800 (PST) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id E00805C82B; Fri, 12 Mar 2004 14:33:22 -0800 (PST) Date: Fri, 12 Mar 2004 23:33:22 +0100 From: Maxime Henrion To: Kris Kennaway Message-ID: <20040312223322.GF35475@elvis.mu.org> References: <200403122106.i2CL6Kb6090102@repoman.freebsd.org> <20040312215450.GB46054@xor.obsecurity.org> <20040312220439.GC4588@ip.net.ua> <20040312222242.GA46557@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040312222242.GA46557@xor.obsecurity.org> User-Agent: Mutt/1.4.1i cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: Ruslan Ermilov cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_exec.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Mar 2004 22:33:23 -0000 Kris Kennaway wrote: > On Sat, Mar 13, 2004 at 12:04:39AM +0200, Ruslan Ermilov wrote: > > On Fri, Mar 12, 2004 at 01:54:50PM -0800, Kris Kennaway wrote: > > > On Fri, Mar 12, 2004 at 01:06:20PM -0800, Ruslan Ermilov wrote: > > > > ru 2004/03/12 13:06:20 PST > > > > > > > > FreeBSD src repository > > > > > > > > Modified files: > > > > sys/kern kern_exec.c > > > > Log: > > > > Do what the execve(2) manpage says and enforce what a Strictly > > > > Conforming POSIX application should do by disallowing the argv > > > > argument to be NULL. > > > > > > > > PR: kern/33738 > > > > Submitted by: Marc Olzheim, Serge van den Boom > > > > OK'ed by: nectar > > > > > > Is this likely to break any third party software (e.g. ports)? If so, > > > please bump __FreeBSD_version. > > > > > It'll break only broken software, so I don't think the bump is in order. > > Well, that doesn't follow. When third party software suddenly stops > running on FreeBSD, we need a way to predict in advance whether or not > it will run on a given kernel -- whether the software is "broken" in > an ideological sense or not. For example, we need to mark the port > BROKEN on those versions of FreeBSD so the user doesn't waste their > time worrying about or reporting a known problem. > > __FreeBSD_version bumps have negligible cost, so if we're both wrong > and this has no effect, then no harm is done. I believe that what Ruslan wanted to say is that since software that will break after this commit are already broken, we can just patch the application via the port and have it working whatever version of FreeBSD you're running. This isn't like if that change was an API change that forces us to do stuff in one way for some __FreeBSD_version and in another way for another __FreeBSD_version. We can, and should, do it in just one way, the correct one. So I don't think a __FreeBSD_version bump is needed either. Cheers, Maxime