From owner-freebsd-current@FreeBSD.ORG  Sun Dec 15 23:23:05 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D7D89DDB;
 Sun, 15 Dec 2013 23:23:05 +0000 (UTC)
Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72])
 by mx1.freebsd.org (Postfix) with ESMTP id 9DC691A67;
 Sun, 15 Dec 2013 23:23:05 +0000 (UTC)
Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149])
 by mail.dawidek.net (Postfix) with ESMTPSA id 696304FC;
 Mon, 16 Dec 2013 00:16:23 +0100 (CET)
Date: Mon, 16 Dec 2013 00:23:41 +0100
From: Pawel Jakub Dawidek <pjd@FreeBSD.org>
To: Tim Kientzle <kientzle@freebsd.org>
Subject: Re: dhclient can't limit bpf descriptor?
Message-ID: <20131215232341.GA1343@garage.freebsd.pl>
References: <D88167A6-8DE9-40A1-B55C-667776ABB00D@freebsd.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4"
Content-Disposition: inline
In-Reply-To: <D88167A6-8DE9-40A1-B55C-667776ABB00D@freebsd.org>
X-OS: FreeBSD 11.0-CURRENT amd64
User-Agent: Mutt/1.5.22 (2013-10-16)
Cc: FreeBSD current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Dec 2013 23:23:05 -0000


--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 14, 2013 at 12:12:23PM -0800, Tim Kientzle wrote:
> Opened up an old VM from a month or so ago (r257910) and dhclient won=E2=
=80=99t start.
>=20
> Specifically, dhclient complains (when run by root):
>  =E2=80=9Ccan=E2=80=99t limit bpf descriptor: Bad address=E2=80=9D
> and then immediately exits.
>=20
> What does this mean?   I don=E2=80=99t know anything about the capabiliti=
es
> framework and certainly haven=E2=80=99t configured it in any way.

Maybe your userland and kernel are out of sync? There was
backward-incompatible change in Capsicum that could result in error like
that (capability rights are now passed as a pointer to a structure and
not uint64_t bitfield).

--=20
Pawel Jakub Dawidek                       http://www.wheelsystems.com
FreeBSD committer                         http://www.FreeBSD.org
Am I Evil? Yes, I Am!                     http://mobter.com

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iEYEARECAAYFAlKuOf0ACgkQForvXbEpPzTnfgCgx/Ssrs88reKmI4GqK9BkiPQp
hcMAni9qUF0VXVwtibHMWdqY46MTDgti
=dy9k
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--