From owner-freebsd-audit Sun Jun 17 2:30:17 2001 Delivered-To: freebsd-audit@freebsd.org Received: from assaris.sics.se (h122n4fls32o892.telia.com [213.64.47.122]) by hub.freebsd.org (Postfix) with ESMTP id DB01C37B401; Sun, 17 Jun 2001 02:30:13 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id LAA72326; Sun, 17 Jun 2001 11:30:18 +0200 (CEST) (envelope-from assar) From: Assar Westerlund To: Peter Pentchev Cc: freebsd-audit@freebsd.org, jlemon@freebsd.org Subject: Re: GLOB_LIMIT vs GLOB_MAXPATH References: <5ld783cvnq.fsf@assaris.sics.se> <20010617122017.F777@ringworld.oblivion.bg> Date: 17 Jun 2001 11:30:18 +0200 In-Reply-To: Peter Pentchev's message of "Sun, 17 Jun 2001 12:20:17 +0300" Message-ID: <5l66dvcv2t.fsf@assaris.sics.se> Lines: 18 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev writes: > I wonder if this would require revision of the glob(3) advisory.. I don't see why. It says that 4.3 and above doesn't have the problem and that continues to be the case. The patches apply to older versoins. > And I wonder if this would qualify as an API change on the -stable > branch, which seems to be frowned upon by some, or if it wouldn't > be MFC'd, which would cause an API incompatibility between -stable > and -current :) Well, compatibility between -current and -stable should be a goal I think, hence if this goes in it should also be MFC:ed. I agree that it changes the API and I wish I had found this issue before 4.3 but I didn't. Either you can argue for nobody (except me/us :-) using this API or just leave the GLOB_MAXPATH for backwards compatibility. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message