From owner-freebsd-stable@FreeBSD.ORG Fri Sep 10 02:55:51 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 632D5106566C; Fri, 10 Sep 2010 02:55:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 308618FC0A; Fri, 10 Sep 2010 02:55:51 +0000 (UTC) Received: from bigwig.baldwin.cx (unknown [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 67AA446C08; Thu, 9 Sep 2010 14:38:34 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 31A068A04E; Thu, 9 Sep 2010 14:37:47 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 9 Sep 2010 14:37:21 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100819; KDE/4.4.5; amd64; ; ) References: <20100909143357.GG34314@home.opsec.eu> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201009091437.21563.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 09 Sep 2010 14:37:47 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Gareth de Vaux , stable@freebsd.org, Kurt Jaeger , Jack Vogel Subject: Re: MSIX failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 02:55:51 -0000 On Thursday, September 09, 2010 12:41:07 pm Jack Vogel wrote: > On Thu, Sep 9, 2010 at 7:33 AM, Kurt Jaeger wrote: > > > Hi! > > > > > > Is this within a jail or something else along those lines? I can't > > > > reproduce the problem otherwise. Frustrating! Someone else on the > > list > > > > might have ideas as to what could cause this. > > > > > > Nope, this's a normal host. I've got securelevel on 1, but doubt that > > > would affect this? > > > > I assume it affects it. > > > > http://www.freebsd.org/doc/en/books/faq/security.html#SECURELEVEL > > > > Basically, when the securelevel is positive, the kernel restricts > > certain tasks; not even the superuser (i.e., root) is allowed to > > do them. > > > > There: > > > > # Write to kernel memory via /dev/mem and /dev/kmem. > > > > So I assume it also restricts reading /dev/kmem ? > > > > > OH YUCK, another root isn't really root, so is it also possibly > the reason for the MSIX failure?? Is this pile, er feature, on by default? securelevel does not affect any of the MSI/MSI-X bits. -- John Baldwin