From owner-freebsd-current@FreeBSD.ORG Sat Aug 14 06:35:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11A2216A4CE; Sat, 14 Aug 2004 06:35:45 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF29E43D5E; Sat, 14 Aug 2004 06:35:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-67-115-74-195.dsl.lsan03.pacbell.net [67.115.74.195]) i7E6ZiEU021994; Sat, 14 Aug 2004 02:35:44 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 411A651383; Fri, 13 Aug 2004 23:35:42 -0700 (PDT) Date: Fri, 13 Aug 2004 23:35:42 -0700 From: Kris Kennaway To: Kris Kennaway , kientzle@FreeBSD.org Message-ID: <20040814063541.GA43063@xor.obsecurity.org> References: <20040813235434.GA75875@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20040813235434.GA75875@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: current@FreeBSD.org Subject: Re: Spurious EACCES errors from apache X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Aug 2004 06:35:45 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 13, 2004 at 04:54:34PM -0700, Kris Kennaway wrote: > Since a recent world+kernel update, apache is frequently reporting > errors like: >=20 > [Fri Aug 13 23:29:19 2004] [error] [client 216.136.204.42] (13)Permission= denied: access to /errorlogs/i386-4-packages-latest/All/pkgconfig-0.15.0_1= .tgz failed because search permissions are missing on a component of the pa= th >=20 > There is nothing wrong with the permissions of that path, and > refetching the same file will usually succeed. >=20 > Did someone break something in the kernel, perhaps some recent VM > changes? With help from rwatson we tracked it down to bsdtar, which seems to be setting and resetting permissions on every path component when extracting a tarball. This is bad when some of those directories already exist, because other processes trying to access files in the directory hierarchy may lose the race and fail. Kris --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBHbK9Wry0BWjoQKURAiUqAJ4pknj4hpj4zQ+Tz8rQX0ch5TBn1gCglk7H c4mN4cFlfLGYDlz5c1a/BW4= =ws7g -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--