From owner-freebsd-hackers@FreeBSD.ORG Mon May 16 12:00:29 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 612E4106566C for ; Mon, 16 May 2011 12:00:17 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id CE4B18FC0A for ; Mon, 16 May 2011 12:00:16 +0000 (UTC) Received: by bwz12 with SMTP id 12so5383849bwz.13 for ; Mon, 16 May 2011 05:00:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4kCj3evQpix6QrLjvXIV7QaSGeXe9wmay378GTmm53Y=; b=p1NdrPnGZMhFkIIDeZ3NnnCqT2lFabp8rcEn93ywa8bHCNkIO4tGeXlUOH7xb33un1 TebdENmRw3YeuL2ydQ9SuLeZtuLyAuGpDXK2n7htGuzahJMuBBeWs0bn+1GwcN4RrZP4 zD/mK3TY2z/4kdCWjJi6UaEqFWDhDMjTjeJko= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=k8yDMtXUpoPgz4eMyQoHxQqlzWGbKelIZf1ZcuR6LPdJPPXOGuAO5JLVE/gvK9QIWi WKO1SrcIdP0Jcoprjt55ldn16LKeY2M439uOtRpKfSp7REkE+bXvU7bAE4QYqJNEO86b 1oIulp7KOhL9A76OS+eXNCUe+SFqfzbYvOh3g= MIME-Version: 1.0 Received: by 10.205.32.65 with SMTP id sj1mr435251bkb.36.1305545671873; Mon, 16 May 2011 04:34:31 -0700 (PDT) Received: by 10.204.38.3 with HTTP; Mon, 16 May 2011 04:34:31 -0700 (PDT) In-Reply-To: References: <00b601cc11d5$5c83f5c0$158be140$@vicor.com> <24057187-9777-4CFF-92D1-1D6103B35280@vicor.com> Date: Mon, 16 May 2011 12:34:31 +0100 Message-ID: From: Tom Evans To: Mehmet Erol Sanliturk Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Devin Teske Subject: Re: [RELEASE] New Boot-Loader Menu -- version 1.5 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2011 12:00:29 -0000 On Sat, May 14, 2011 at 9:36 PM, Mehmet Erol Sanliturk wrote: > My main idea is that the present Boot-Loader Menu -- version 1.5 is a very > good menu . Instead of destroying its elegant structure , the already > available FreeBSD Boot Loader ( actually Kernel selection ) menu could be > improved and may be used IF IT IS SUITABLE for the USER ( otherwise the user > may not select it during installation ) . > I disagree entirely, the boot loader knows nothing of kernels, it only presents the bootable drives/partitions as the BIOS sees it. Calling the boot loader a kernel selection menu is disingenuous, since this is simply a by-product of having different kernels on different drives/partitions, whilst the most commonly desired kernel selection (kernel vs kernel.old) is not available via this method. Cheers Tom From owner-freebsd-hackers@FreeBSD.ORG Mon May 16 12:50:31 2011 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FDA91065670 for ; Mon, 16 May 2011 12:50:31 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D4BAC8FC13 for ; Mon, 16 May 2011 12:50:30 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA01286; Mon, 16 May 2011 15:50:27 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DD11D93.2070307@FreeBSD.org> Date: Mon, 16 May 2011 15:50:27 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Tom Evans References: <00b601cc11d5$5c83f5c0$158be140$@vicor.com> <24057187-9777-4CFF-92D1-1D6103B35280@vicor.com> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: "freebsd-hackers@freebsd.org" Subject: Re: [RELEASE] New Boot-Loader Menu -- version 1.5 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2011 12:50:31 -0000 on 16/05/2011 14:34 Tom Evans said the following: > I disagree entirely, the boot loader knows nothing of kernels Eh? Maybe I misunderstand what you are saying, but: set kernel=kernel.old boot IMHO, it shows that you can tell the loader about kernels. Having a kernel-choice sub-menu would be convenient. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Mon May 16 13:03:30 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7948A1065672 for ; Mon, 16 May 2011 13:03:30 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 181BC8FC13 for ; Mon, 16 May 2011 13:03:29 +0000 (UTC) Received: by vxc34 with SMTP id 34so4222793vxc.13 for ; Mon, 16 May 2011 06:03:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=s6szIJxs/Z2qx447sZDvfGg6h2hnJ7iVFJekjCTwOPY=; b=A6Rmv6CAoPeSjx4qSeJmLftx7Tr0tMGz4Z7+zsn2G5OzgNbCQy+1HXjijGgxtIbr5/ MwEAQJtUK5Zp35hgGHIIduc8tzkwdYp+xkJdk4iwY6OzR4KDE++bCd2h1SIzzpX0eGAI 8Ty7QPb2we467Ak7+E7CSxv8LTW0uus+JsOK0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YSBp1TFYshvge2+QrbJCFWIzbsyIXJs25tnY9QJxtMVSvHw9hoGkTDkki8kksFQ74D R2DhmqE+eU9J3prJGjLqqw/KHm48jMhIhi1KsEVrqF5j9CTm+EuCUrXX9s3OJr2NFmyZ 4Fvcvmuo48AFr3PZpfIEFHZ3peJJQZ3c4CKi4= MIME-Version: 1.0 Received: by 10.52.97.197 with SMTP id ec5mr71831vdb.112.1305551009337; Mon, 16 May 2011 06:03:29 -0700 (PDT) Received: by 10.52.183.73 with HTTP; Mon, 16 May 2011 06:03:29 -0700 (PDT) In-Reply-To: <4DD11D93.2070307@FreeBSD.org> References: <00b601cc11d5$5c83f5c0$158be140$@vicor.com> <24057187-9777-4CFF-92D1-1D6103B35280@vicor.com> <4DD11D93.2070307@FreeBSD.org> Date: Mon, 16 May 2011 14:03:29 +0100 Message-ID: From: Tom Evans To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-hackers@freebsd.org" Subject: Re: [RELEASE] New Boot-Loader Menu -- version 1.5 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2011 13:03:30 -0000 On Mon, May 16, 2011 at 1:50 PM, Andriy Gapon wrote: > on 16/05/2011 14:34 Tom Evans said the following: >> I disagree entirely, the boot loader knows nothing of kernels > > Eh? =C2=A0Maybe I misunderstand what you are saying, but: > > set kernel=3Dkernel.old > boot > > IMHO, it shows that you can tell the loader about kernels. > Having a kernel-choice sub-menu would be convenient. > s/boot loader/boot manager/ My bad for the confusion. The loader should definitely know about kernels; the boot manager, which knows about BIOS bootable drives/partitions only, should not. Cheers Tom From owner-freebsd-hackers@FreeBSD.ORG Mon May 16 18:36:29 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0024E1065674 for ; Mon, 16 May 2011 18:36:28 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-bw0-f45.google.com (mail-bw0-f45.google.com [209.85.214.45]) by mx1.freebsd.org (Postfix) with ESMTP id 7DF2D8FC1C for ; Mon, 16 May 2011 18:36:28 +0000 (UTC) Received: by bwz16 with SMTP id 16so6042713bwz.18 for ; Mon, 16 May 2011 11:36:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:x-mailer; bh=tgGHYrUBuZIVIodmKYPjZVLIz2WPb95ydBx0rNqdZkw=; b=Bdd7Q3bfJ+NYuOvidQgAITo+k4Nc5RMHusURBZvXZDhAHJJy3Rg2olTym+bO33myED GITMzXNTV4zXn1pIl7L+gdwONWVHg9ZNCtS38dlzE6I2lpXskUd7ZaXunmjeTUq/he9i JJnsrrRASTssYb4QdHXluIC9UfyujnT8QztBw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:x-mailer; b=XuAS44XBY+3O82YF09Rx/RWdw5bOk0Ht+cA+e1jgO70K6Rv9Ci5tNezl5nT5ov03FQ mp3B93rZIrddJgks8bF1m/L82NqU8xxmcI/ISOeGcIS+jsOwl24nztvyYo2QXuwmUVs7 rZn5fuRVVS34Lx4iF5couXm/4MmtuA0FAdnQg= Received: by 10.204.154.199 with SMTP id p7mr4368615bkw.114.1305570987157; Mon, 16 May 2011 11:36:27 -0700 (PDT) Received: from DEV ([82.193.208.173]) by mx.google.com with ESMTPS id c11sm3174281bkc.2.2011.05.16.11.36.11 (version=SSLv3 cipher=OTHER); Mon, 16 May 2011 11:36:25 -0700 (PDT) Message-ID: <20110516.183617.687.1@DEV> From: rank1seeker@gmail.com To: freebsd-hackers@freebsd.org Date: Mon, 16 May 2011 20:36:17 +0200 X-Mailer: POP Peeper (3.7.0.0) Subject: MD ROOT and image size limitation (makes kernel panic) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2011 18:36:29 -0000 I have a 4 GB or ram, so why kernel panic with my MD ROOT, if larger then ~40 MB? I've tried to split up root in 20MB image and usr in 160 MB Via loader.conf root becomes md0 and usr md1 and panic occurs even when they are split I had to get rid of md1, to be able to boot with md0 as a root. What exactly imposes limitation, inside kernel's code to SIZE of an image? My hardware definatelly isn't ... Is this different on amd64? I've tested this, only with i386. Domagoj S. From owner-freebsd-hackers@FreeBSD.ORG Mon May 16 19:18:21 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 846E3106566C for ; Mon, 16 May 2011 19:18:21 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 38C178FC12 for ; Mon, 16 May 2011 19:18:20 +0000 (UTC) Received: by vws18 with SMTP id 18so4593013vws.13 for ; Mon, 16 May 2011 12:18:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+3doIIys2PBH05Oa7aKNdmt9pm3HNMJqjJvG8yIkAPk=; b=gMY42iWo3Xaw2gZwZerCyr+9vkVhe/vs8/kUM0fA0mW/8G1saw4ng3/wU+yBASpsQd JpSTrOA3dy80ts0WIBlv3nsW5Io7Qt1FHgHy6ZERk90CdCOX2YKS/CQE/pitw1V5EAxZ GqmMunLytXB41qVh+Y/5Hr72TEssmwT9dYFNM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ugvHcfKfT23Q7XpJTFLZue7YLRR7IPrk8LmRrrSIRqqiNDROY1NUcRdxbMtifh+xTn 9jrbpqNtA6HcCMI50/ff5sChARssq9HXSedSfazD5vkRcbUKzD8yxZG2cb4BuFKT4Tmv AiHrDvaLSaOAqayUx1R1dLmo3dGATPAjo6ylU= MIME-Version: 1.0 Received: by 10.220.247.139 with SMTP id mc11mr1376915vcb.107.1305573500006; Mon, 16 May 2011 12:18:20 -0700 (PDT) Received: by 10.220.188.202 with HTTP; Mon, 16 May 2011 12:18:19 -0700 (PDT) In-Reply-To: <20110516.183617.687.1@DEV> References: <20110516.183617.687.1@DEV> Date: Mon, 16 May 2011 12:18:19 -0700 Message-ID: From: Garrett Cooper To: rank1seeker@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: MD ROOT and image size limitation (makes kernel panic) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2011 19:18:21 -0000 On Mon, May 16, 2011 at 11:36 AM, wrote: > I have a 4 GB or ram, so why kernel panic with my MD ROOT, if larger then > ~40 MB? > I've tried to split up root in 20MB image and usr in 160 MB > Via loader.conf root becomes md0 and usr md1 and panic occurs even when > they are split > > I had to get rid of md1, to be able to boot with md0 as a root. > > What exactly imposes limitation, inside kernel's code to SIZE of an image? > My hardware definatelly isn't ... > > Is this different on amd64? > I've tested this, only with i386. Screenshot please? Thanks, -Garrett From owner-freebsd-hackers@FreeBSD.ORG Mon May 16 20:44:46 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07543106564A for ; Mon, 16 May 2011 20:44:46 +0000 (UTC) (envelope-from lgj@usenix.org) Received: from lonestar.usenix.org (lonestar.usenix.org [131.106.3.102]) by mx1.freebsd.org (Postfix) with ESMTP id CA1CB8FC0C for ; Mon, 16 May 2011 20:44:45 +0000 (UTC) Received: from negroni.usenix.org (negroni.usenix.org [131.106.3.145]) (authenticated bits=0) by lonestar.usenix.org (8.14.2/8.14.2) with ESMTP id p4GKiT0m014549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 16 May 2011 13:44:45 -0700 (PDT) From: Lionel Garth Jones Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 16 May 2011 13:44:44 -0700 Message-Id: <53929555-F55D-44F0-B307-F363B273C0A3@usenix.org> To: freebsd-hackers@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-DCC-Usenix-Metrics: lonestar; whitelist X-Spam-Status: No, score=0.7 required=6.0 tests=ALL_TRUSTED, FH_DATE_PAST_20XX autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lonestar X-Mailman-Approved-At: Mon, 16 May 2011 21:05:05 +0000 Subject: USENIX HotCloud '11 Program Now Available X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2011 20:44:46 -0000 We'd like to invite you to attend the 3rd USENIX Workshop on Hot Topics in Cloud Computing (HotCloud '11), taking place in Portland, OR, June 14-15, 2011. HotCloud '11 will discuss challenges in the cloud computing paradigm, including the design, implementation, and deployment of virtualized clouds. The program includes: -- Refereed paper sessions on scheduling and resource management, economics, security, OSes and frameworks, and more -- Joint ATC, WebApps, and HotCloud Keynote Address: "An Agenda for Empirical Cyber Crime Research," by Stefan Savage, UCSD -- Joint ATC, WebApps, and HotCloud Invited Talk: "Helping Humanity with Phones and Clouds" by Matthew Faulkner and Michael Olson, Caltech -- Panel -- Poster Session: This session provides an opportunity to present early-stage work and receive feedback from the community. Posters provide a great way to have more in-depth conversations between authors and audience--so much so that we are automatically granting each accepted paper a poster slot. We welcome submissions from those who are not paper authors also. The submission deadline is Monday, May 30, 2011, at 3:00 p.m. PDT. Find out more at: http://www.usenix.org/events/hotcloud11/poster.html The full program can be found at http://www.usenix.org/hotcloud11/proga Don't miss this opportunity to engage in dynamic discussion on key topics in the cloud computing community. Register today at http://www.usenix.org/events/fcw11/registration/ HotCloud '11 is part of 2011 USENIX Federated Conferences Week, which will take place June 14-17, 2011, in Portland, OR. http://www.usenix.org/fcw11/ We look forward to seeing you in Portland! Ion Stoica, University of California, Berkeley John Wilkes, Google HotCloud '11 Program Co-Chairs hotcloud11chairs@usenix.org ---------------------------------- 3rd USENIX Workshop on Hot Topics in Cloud Computing (HotCloud '11) June 14-15, 2011 Portland, OR Sponsored by USENIX in cooperation with ACM SIGOPS Early Bird Registration Deadline: Monday, May 23, 2011 http://www.usenix.org/hotcloud11/proga ---------------------------------- From owner-freebsd-hackers@FreeBSD.ORG Mon May 16 21:57:29 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D29DE1065670 for ; Mon, 16 May 2011 21:57:29 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 91F908FC08 for ; Mon, 16 May 2011 21:57:29 +0000 (UTC) Received: by ywf7 with SMTP id 7so2100130ywf.13 for ; Mon, 16 May 2011 14:57:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=BqcwoY7hzn7XlvEvkFcZIdvbkNEERkXpA47NXCgP80Y=; b=w+JzXSV2eX5Y1WCdjmdAVVBbkE1BKI9fEeaM6RZMz7NLNc510Sm3CyI9S0yXlVF2Si fG1KT6k/FM0f135clb4xMzGGO2jCdvEHaUVJWYlX2kntXzN8WKD/lF3OMXyVNajP0JT/ 0JdHSIKv1MA7Hjd+yvJnKvzTk4DhRC4088T04= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=NCQhoxetx9fLOrpkzPjDQE9uRdLrKf2EjogJRECd/3Y6Kx+wirQT+SM3nroDtNwseG oe9dRqUwWcPYpXVduUcc5oMLJdh01mI2t9qX1VJUGNghZPwKijNBvMT2DyXXp0TU4Sbi svtI8C2jwqDZpB99BKWFMwVcvl3AWY8dIBRzA= MIME-Version: 1.0 Received: by 10.236.108.177 with SMTP id q37mr4969618yhg.14.1305581228931; Mon, 16 May 2011 14:27:08 -0700 (PDT) Received: by 10.236.109.167 with HTTP; Mon, 16 May 2011 14:27:08 -0700 (PDT) In-Reply-To: <20110516.183617.687.1@DEV> References: <20110516.183617.687.1@DEV> Date: Mon, 16 May 2011 14:27:08 -0700 Message-ID: From: Neel Natu To: rank1seeker@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: MD ROOT and image size limitation (makes kernel panic) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2011 21:57:29 -0000 Hi, On Mon, May 16, 2011 at 11:36 AM, wrote: > I have a 4 GB or ram, so why kernel panic with my MD ROOT, if larger then > ~40 MB? > I've tried to split up root in 20MB image and usr in 160 MB > Via loader.conf root becomes md0 and usr md1 and panic occurs even when > they are split > > I had to get rid of md1, to be able to boot with md0 as a root. > > What exactly imposes limitation, inside kernel's code to SIZE of an image? > My hardware definatelly isn't ... > > Is this different on amd64? > I've tested this, only with i386. > We hit this problem at work and the solution was to increase NKPT. If you are using -current then NKPT is already a kernel config option. With 8.x you will need to modify . best Neel > > Domagoj S. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 01:04:40 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C517106566B for ; Tue, 17 May 2011 01:04:40 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 3C9348FC1F for ; Tue, 17 May 2011 01:04:39 +0000 (UTC) Received: by qyk35 with SMTP id 35so2118857qyk.13 for ; Mon, 16 May 2011 18:04:39 -0700 (PDT) Received: by 10.224.64.97 with SMTP id d33mr10043qai.309.1305592488541; Mon, 16 May 2011 17:34:48 -0700 (PDT) Received: from [192.168.10.19] (pool-68-239-206-132.nwrk.east.verizon.net [68.239.206.132]) by mx.google.com with ESMTPS id s9sm7188qco.12.2011.05.16.17.34.46 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2011 17:34:47 -0700 (PDT) From: Mark Saad Content-Type: text/plain; charset=us-ascii X-Mailer: iPod Mail (8G4) Message-Id: To: "hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (iPod Mail 8G4) Cc: Subject: Freebsd on the sun x4440 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Tue, 17 May 2011 01:04:40 -0000 X-Original-Date: Wed, 16 May 2012 20:34:50 -0400 X-List-Received-Date: Tue, 17 May 2011 01:04:40 -0000 All I am setting up 3 sun x4440 with freebsd 7.3 amd64 . The severs have 4x 4-= core opterons and 128G of ram each . Once the servers boot they are a good f= it for what we are doing and preform well . The odd thing I am seeing is a l= ong delay in boot up . Once in the initial loading of the kernel at the "|" f= or 1-2 mins . Then again shortly after printing the kernel banner "freebsd 7= .3-release etc etc etc" . This delay is about 1-2 mins as well. So my ques= tion does any one know what I could do to speed up the boot up ? I suspect t= he first delay is due to a serial device probe the second is a mystery . al= so the bios load up time is about 5 mins on this box does anyone have any id= eas on speeding that up ? ---- mark saad=20 Nonesuch@longcount.org= From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 01:11:51 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40AB1106564A for ; Tue, 17 May 2011 01:11:51 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 019688FC08 for ; Tue, 17 May 2011 01:11:50 +0000 (UTC) Received: by qwc9 with SMTP id 9so17314qwc.13 for ; Mon, 16 May 2011 18:11:50 -0700 (PDT) Received: by 10.229.67.66 with SMTP id q2mr8920qci.282.1305592934836; Mon, 16 May 2011 17:42:14 -0700 (PDT) Received: from [192.168.10.19] (pool-68-239-206-132.nwrk.east.verizon.net [68.239.206.132]) by mx.google.com with ESMTPS id s16sm4926qco.37.2011.05.16.17.42.13 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2011 17:42:14 -0700 (PDT) From: Mark Saad X-Mailer: iPod Mail (8G4) Message-Id: <83D72FE6-15E8-4113-9811-05299D9C2402@longcount.org> To: "freebsd-hackers@freebsd.org" Mime-Version: 1.0 (iPod Mail 8G4) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Freebsd And the sun x4440 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Tue, 17 May 2011 01:11:51 -0000 X-Original-Date: Wed, 16 May 2012 20:42:46 -0400 X-List-Received-Date: Tue, 17 May 2011 01:11:51 -0000 All I am setting up 3 sun x4440 with freebsd 7.3 amd64 . The severs have 4x 4-c= ore opterons and 128G of ram each . Once the servers boot they are a good fi= t for what we are doing and preform well . The odd thing I am seeing is a lo= ng delay in boot up . Once in the initial loading of the kernel at the "|" f= or 1-2 mins . Then again shortly after printing the kernel banner "freebsd 7= .3-release etc etc etc" . This delay is about 1-2 mins as well. So my ques= tion does any one know what I could do to speed up the boot up ? I suspect t= he first delay is due to a serial device probe the second is a mystery . al= so the bios load up time is about 5 mins on this box does anyone have any id= eas on speeding that up ? ---- mark saad=20 Nonesuch@longcount.org From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 02:31:31 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25EAA106566C for ; Tue, 17 May 2011 02:31:31 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id 0EC4A8FC0C for ; Tue, 17 May 2011 02:31:30 +0000 (UTC) Received: from [127.0.0.1] (proxy8.corp.yahoo.com [216.145.48.13]) by mrout2.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p4H2L5Su065211; Mon, 16 May 2011 19:21:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=yahoo-inc.com; s=cobra; t=1305598865; bh=m0Wc5qMYmUFIPRd2VYJ+/wUajW273V0ONeWKwvdzRzA=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=cquyJ8XJAskCL+YQV487pnXi94lTvWDFJDHOR12UgqekiOUhABopiQ7Lwt2V8Urq4 f/SkH+Gp8oASF9/zCh1Rh2Yj/uVMGyeM3WHevs8SnNwZ0rsHX55Zcs6pVqrJkZJbK+ zaQcw6JH3gM1M3Hph/Z8UPs47tdPEJmqawxlXTPo= From: Sean Bruno To: Mark Saad In-Reply-To: <83D72FE6-15E8-4113-9811-05299D9C2402@longcount.org> References: <83D72FE6-15E8-4113-9811-05299D9C2402@longcount.org> Content-Type: text/plain; charset="UTF-8" Date: Mon, 16 May 2011 19:21:05 -0700 Message-ID: <1305598865.2633.4.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Cc: "freebsd-hackers@freebsd.org" Subject: Re: Freebsd And the sun x4440 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 02:31:31 -0000 On Wed, 2012-05-16 at 17:42 -0700, Mark Saad wrote: > Once in the initial loading of the kernel at the "|" for 1-2 mins . > Then again shortly after printing the kernel banner "freebsd > 7.3-release etc etc etc" . This delay is about 1-2 mins as well. This looked like the "memory check" in my tests of -Current in the projects/largeSMP tree. You may want to try to manually disable the check using the following as a base. This is my diff to -Current. Your mileage may vary. Index: sys/amd64/amd64/machdep.c =================================================================== --- sys/amd64/amd64/machdep.c (revision 221963) +++ sys/amd64/amd64/machdep.c (working copy) @@ -1430,6 +1430,8 @@ && pa >= trunc_page(dcons_addr) && pa < dcons_addr + dcons_size) goto do_dump_avail; + if (1) + goto baluba; page_bad = FALSE; @@ -1474,6 +1476,7 @@ */ if (page_bad == TRUE) continue; +baluba: /* * If this good page is a continuation of the * previous set of good pages, then just increase Sean From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 05:59:14 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CB751065672 for ; Tue, 17 May 2011 05:59:14 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 204D78FC08 for ; Tue, 17 May 2011 05:59:13 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p4H5xA1X092404 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 16 May 2011 22:59:13 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DD20EA9.5060300@freebsd.org> Date: Mon, 16 May 2011 22:59:05 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Mark Saad References: <83D72FE6-15E8-4113-9811-05299D9C2402@longcount.org> In-Reply-To: <83D72FE6-15E8-4113-9811-05299D9C2402@longcount.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-hackers@freebsd.org" Subject: Re: Freebsd And the sun x4440 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 05:59:14 -0000 On 5/16/12 5:42 PM, Mark Saad wrote: > All > I am setting up 3 sun x4440 with freebsd 7.3 amd64 . The severs have 4x 4-core opterons and 128G of ram each . Once the servers boot they are a good fit for what we are doing and preform well . The odd thing I am seeing is a long delay in boot up . Once in the initial loading of the kernel at the "|" for 1-2 mins . Then again shortly after printing the kernel banner "freebsd 7.3-release etc etc etc" . This delay is about 1-2 mins as well. So my question does any one know what I could do to speed up the boot up ? I suspect the first delay is due to a serial device probe the second is a mystery . also the bios load up time is about 5 mins on this box does anyone have any ideas on speeding that up ? I'd suspect that all three are some sort of memory probe or test. you might also check they are not trying to do a PXE boot first. > ---- > mark saad > Nonesuch@longcount.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 08:35:12 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 987B3106566C for ; Tue, 17 May 2011 08:35:12 +0000 (UTC) (envelope-from zafer@aydogan.de) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 569B28FC13 for ; Tue, 17 May 2011 08:35:11 +0000 (UTC) Received: by qyk35 with SMTP id 35so2263654qyk.13 for ; Tue, 17 May 2011 01:35:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.32.210 with SMTP id e18mr255312qad.139.1305621310507; Tue, 17 May 2011 01:35:10 -0700 (PDT) Received: by 10.229.75.76 with HTTP; Tue, 17 May 2011 01:35:10 -0700 (PDT) In-Reply-To: References: <20110513073331.GA2059@tops> Date: Tue, 17 May 2011 10:35:10 +0200 Message-ID: From: =?UTF-8?Q?Zafer_Aydo=C4=9Fan?= To: Gleb Kurtsou Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: OpenGrok for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 08:35:12 -0000 2011/5/13 Zafer Aydo=C4=9Fan : > 2011/5/13 Gleb Kurtsou : >> On (12/05/2011 22:45), Zafer Aydo=C4=9Fan wrote: >>> Hello List, >>> >>> I've set up an OpenGrok service for the FreeBSD sources (current). >>> OpenGrok is a source code search engine and cross reference. >>> I'm updating the sources once a day. I'm a NetBSD developer and I'm >>> also maintaining http://nxr.netbsd.org >>> >>> Feel free to use it: >>> http://fxr.aydogan.net >> Thanks! >> >> What do you think about having index for different kernels in one place >> like now defunct http://grok.x12.su/source/ or >> http://fxr.watson.org/fxr/source/?v=3DHEAD >> > > That's possible, but OpenGrok contains the whole source tree > and not only the kernel. > Therefore I would group it with ports/, projects/, www/. etc. > > I didn't know about grok.x12.su, but I see its broken anyway. > > Zafer. > Hmm... there seems to be very little interest so far. Although this tool is mainly useful for developers, what is the correct mailing list to announce it ? Zafer. From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 09:29:46 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12156106566B for ; Tue, 17 May 2011 09:29:46 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 926808FC0A for ; Tue, 17 May 2011 09:29:45 +0000 (UTC) Received: by fxm11 with SMTP id 11so342133fxm.13 for ; Tue, 17 May 2011 02:29:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:content-type :content-transfer-encoding:in-reply-to:references:x-mailer; bh=PiIrFOlwZLH7mcd+7Nv277tdRoNCwqdjNfFlcF80sOw=; b=pNpLwDioy9JbGqfrNzH0sCblXooIGQCDZMaW8Gn849+AHVUuUtpJEqSvhbG3rAIkf0 jzbj4cIj4KjFL9wbcQ7D238FB0bkrznGaWplNHSEFYwljvsbakQZ9cFL71UwzNQ9s5XE 6nZnqnpuvIvGdJPe+KTmSTWEbHkf4iEvzuqj4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:content-type :content-transfer-encoding:in-reply-to:references:x-mailer; b=I5lqBkH2j9dp8eTE6VXrGuDEtVtaBWKb6fu+xDj+nmBmRjURSqq9xjKVfgjsjl9d/+ 0B8uwe8nvvWVrRbPwZo8MHvYBWEetQCFB4wBqiJTO0UwqQ0hLuHQZlzmA1Pw0lTrijaW ChSgeIy0pIXy60VTWxCd42dgp99tDF2Z9OUCg= Received: by 10.223.77.4 with SMTP id e4mr532317fak.51.1305624584442; Tue, 17 May 2011 02:29:44 -0700 (PDT) Received: from DEV ([82.193.208.173]) by mx.google.com with ESMTPS id d16sm129529faa.12.2011.05.17.02.29.28 (version=SSLv3 cipher=OTHER); Tue, 17 May 2011 02:29:43 -0700 (PDT) Message-ID: <20110517.092939.312.1@DEV> From: rank1seeker@gmail.com To: freebsd-hackers@freebsd.org Date: Tue, 17 May 2011 11:29:39 +0200 Content-Type: text/plain; charset="Windows-1250" Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <20110516.183617.687.1@DEV> X-Mailer: POP Peeper (3.7.0.0) Subject: Re: MD ROOT and image size limitation (makes kernel panic) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 09:29:46 -0000 > Hi,=0D=0A> =0D=0A> On Mon, May 16, 2011 at 11:36 AM, = wrote:=0D=0A> > I have a 4 GB or ram, so why = kernel panic with my MD ROOT, if larger then=0D=0A> > ~40 MB?=0D=0A> > = I've tried to split up root in 20MB image and usr in 160 MB=0D=0A> > Via = loader.conf root becomes md0 and usr md1 and panic occurs even = when=0D=0A> > they are split=0D=0A> >=0D=0A> > I had to get rid of md1, = to be able to boot with md0 as a root.=0D=0A> >=0D=0A> > What exactly = imposes limitation, inside kernel's code to SIZE of an image?=0D=0A> > My = hardware definatelly isn't ...=0D=0A> >=0D=0A> > Is this different on = amd64?=0D=0A> > I've tested this, only with i386.=0D=0A> >=0D=0A> =0D=0A> = We hit this problem at work and the solution was to increase NKPT.=0D=0A> = =0D=0A> If you are using -current then NKPT is already a kernel config = option.=0D=0A> With 8.x you will need to modify = .=0D=0A=0D=0A=0D=0AWell ..., it looks like my 8.2 RELEASE = src, has it, but ONLY for i386=0D=0A=0D=0A=0D=0A# less = /usr/src/sys/i386/conf/NOTES=0D=0A=0D=0A--=0D=0A#=0D=0A# Number of = initial kernel page table pages used for early bootstrap.=0D=0A# This = number should include enough pages to map the kernel, any=0D=0A# modules = or other data loaded with the kernel by the loader, and data=0D=0A# = structures allocated before the VM system is initialized such as = the=0D=0A# vm_page_t array. Each page table page maps 4MB (2MB with = PAE).=0D=0A#=0D=0Aoptions NKPT=3D31=0D=0A--=0D=0A=0D=0ASo, that = would be 124 MB for kernel and it's modules or other data loaded with the = kernel by the loader (i.e; md image)=0D=0AIn those nums, md image has = only about ~45 MB for itself.=0D=0A=0D=0AKernel itself and it's ..., = needs ~80 MB=0D=0A=0D=0A=0D=0AI'll build a custom kernel, for "lifting" = md image ...=0D=0A=0D=0A=0D=0A=0D=0ADomagoj Smol=E8i=E6=0D=0A=0D=0A From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 09:30:14 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 419CA1065675 for ; Tue, 17 May 2011 09:30:14 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id B48758FC08 for ; Tue, 17 May 2011 09:30:05 +0000 (UTC) Received: by mail-fx0-f54.google.com with SMTP id 11so342133fxm.13 for ; Tue, 17 May 2011 02:30:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=nJpX0rKP6vTOcbX6GIHYzD5+Ty2VMCbg1iLp46F9vOk=; b=n7xUJw2qAnffXDKRk2iNOtX4rLYwC0IwgatPze6ZzVzVYzuRR8iGSVK3iwI/YXTiTv qCpgM+Gp/J/ki8bkmQbk2w/d3yhQEzDWhBKJYXner7DKEp2d0e4JLtqczZqXOdw3IqQv 9e3iOqKqpf7qSW+SV+R8yqsXLF1A4kt2o7rD4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=SjJgt+QrT40LdEBpRCxTUzkwoJXjkfuusouFaDIH6BRQA5GIorPRGquIZniPEV2WiH ZO9uGfnZRcetzlmXXXJyKNTZQD6BZ/8SJhEPWv6c4guszWypHReTRC9x/hPbIIRzk3a5 kKcycdQiZSyoTu9bB1mNc87StmdLVXq8JzrcQ= Received: by 10.223.145.13 with SMTP id b13mr507984fav.65.1305623280078; Tue, 17 May 2011 02:08:00 -0700 (PDT) Received: from [172.29.1.142] (altimet-gw.cs2.dp.wnet.ua [217.20.178.249]) by mx.google.com with ESMTPS id 9sm118585fat.39.2011.05.17.02.07.58 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2011 02:07:58 -0700 (PDT) Message-ID: <4DD23C23.5050101@gmail.com> Date: Tue, 17 May 2011 12:13:07 +0300 From: Vitaly Magerya User-Agent: Thunderbird MIME-Version: 1.0 To: =?UTF-8?B?WmFmZXIgQXlkb8SfYW4=?= References: <20110513073331.GA2059@tops> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, Gleb Kurtsou Subject: Re: OpenGrok for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 09:30:14 -0000 Zafer Aydoğan wrote: > Hmm... there seems to be very little interest so far. FWIW, I find this tool useful, but since it's most helpful when you need to dig into a previously unknown portion of code, which doesn't happen that often, it's reasonable to expect infrequent usage -- don't mistake that for lack of interest (i.e. I bookmarked the thing, but don't know when I'll get a chance to need it). > Although this tool is mainly useful for developers, > what is the correct mailing list to announce it ? This would be the correct list, I guess. PS. The history pages are hard to decode; they are sorted by something other than date or revision number; and which branch do they show? Compare [1] and [2]; revisions starting from 1.6.2.5 are not from the same branch, are they? [1] http://fxr.aydogan.net/history/src/usr.sbin/powerd/powerd.c [2] http://svnweb.freebsd.org/base/head/usr.sbin/powerd/powerd.c?view=log From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 09:51:00 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E45BD106566B for ; Tue, 17 May 2011 09:51:00 +0000 (UTC) (envelope-from zafer@aydogan.de) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id A73188FC1B for ; Tue, 17 May 2011 09:51:00 +0000 (UTC) Received: by qwc9 with SMTP id 9so200656qwc.13 for ; Tue, 17 May 2011 02:51:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.69.213 with SMTP id a21mr279599qcj.222.1305625859869; Tue, 17 May 2011 02:50:59 -0700 (PDT) Received: by 10.229.75.76 with HTTP; Tue, 17 May 2011 02:50:59 -0700 (PDT) In-Reply-To: <4DD23C23.5050101@gmail.com> References: <20110513073331.GA2059@tops> <4DD23C23.5050101@gmail.com> Date: Tue, 17 May 2011 11:50:59 +0200 Message-ID: From: =?UTF-8?Q?Zafer_Aydo=C4=9Fan?= To: Vitaly Magerya Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Gleb Kurtsou Subject: Re: OpenGrok for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 09:51:01 -0000 2011/5/17 Vitaly Magerya : > Zafer Aydo=C4=9Fan wrote: >> Hmm... there seems to be very little interest so far. > > FWIW, I find this tool useful, but since it's most helpful when you > need to dig into a previously unknown portion of code, which doesn't > happen that often, it's reasonable to expect infrequent usage -- don't > mistake that for lack of interest (i.e. I bookmarked the thing, but > don't know when I'll get a chance to need it). > >> Although this tool is mainly useful for developers, >> what is the correct mailing list to announce it ? > > This would be the correct list, I guess. > > PS. The history pages are hard to decode; they are sorted by something > other than date or revision number; and which branch do they show? > Compare [1] and [2]; revisions starting from 1.6.2.5 are not from the > same branch, are they? > > [1] http://fxr.aydogan.net/history/src/usr.sbin/powerd/powerd.c > [2] http://svnweb.freebsd.org/base/head/usr.sbin/powerd/powerd.c?view=3Dl= og > The branches are sorted below HEAD. Its hard to say which branch, unless its noted in the commit log. This is done by opengrok. Its a feature, I guess. Zafer. From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 16:18:53 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BF1B106566C for ; Tue, 17 May 2011 16:18:53 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id DD6FE8FC0A for ; Tue, 17 May 2011 16:18:52 +0000 (UTC) Received: by gwb15 with SMTP id 15so270113gwb.13 for ; Tue, 17 May 2011 09:18:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=sQVIMOwmWxr8v4ileDIJMJaluytQZzHCzCSoDbpLihg=; b=kuWRyRdAtXOyWPsZ1hzlZMqwRhtb3LGAX3W6f3zJiV+tOcFxhxVqhHKVWwBjM/buJl vWKKko82px2WlU8Jkhe84sSUPvcDkKBstC2uGmzPUQh91QMY/Qk+ce1o+4XUBrSr5cfT PGeewwwybinatpEi8mQDRQHj/4JDGIMlLQ6+8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=u9/CjxBqlRIs+7Qw3KABHR7pSMBlBIrL4px5PKWLLlLoT9LGZGwwGhqGKOt06xYbm3 8BbOc+E4bntQMBCoS2To4+aashCj17zb32nLyjT7UzwcRpiwTSkXRFvcRncbWxwRNNaG kI+FI8tDTViE7jIwQHxm/5xjVfCf7JYbmyTDM= MIME-Version: 1.0 Received: by 10.236.78.1 with SMTP id f1mr735983yhe.391.1305647295580; Tue, 17 May 2011 08:48:15 -0700 (PDT) Received: by 10.236.103.52 with HTTP; Tue, 17 May 2011 08:48:14 -0700 (PDT) In-Reply-To: References: Date: Tue, 17 May 2011 16:48:14 +0100 Message-ID: From: krad To: Mark Saad X-Mailman-Approved-At: Tue, 17 May 2011 16:22:08 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "hackers@freebsd.org" Subject: Re: Freebsd on the sun x4440 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 16:18:53 -0000 On 17 May 2012 01:34, Mark Saad wrote: > All > I am setting up 3 sun x4440 with freebsd 7.3 amd64 . The severs have 4x > 4-core opterons and 128G of ram each . Once the servers boot they are a good > fit for what we are doing and preform well . The odd thing I am seeing is a > long delay in boot up . Once in the initial loading of the kernel at the "|" > for 1-2 mins . Then again shortly after printing the kernel banner "freebsd > 7.3-release etc etc etc" . This delay is about 1-2 mins as well. So my > question does any one know what I could do to speed up the boot up ? I > suspect the first delay is due to a serial device probe the second is a > mystery . also the bios load up time is about 5 mins on this box does anyone > have any ideas on speeding that up ? > > ---- > mark saad > Nonesuch@longcount.org_______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > why 7.3? You might have better luck with 8.2. Not I real answer but sometimes its easier to go around issues From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 16:55:07 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20B52106566B for ; Tue, 17 May 2011 16:55:07 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id D9ED38FC08 for ; Tue, 17 May 2011 16:55:06 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p4HGsv58096819 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 17 May 2011 09:54:59 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DD2A862.5080003@freebsd.org> Date: Tue, 17 May 2011 09:54:58 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: =?UTF-8?B?WmFmZXIgQXlkb8SfYW4=?= References: <20110513073331.GA2059@tops> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, Gleb Kurtsou Subject: Re: OpenGrok for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 16:55:07 -0000 On 5/17/11 1:35 AM, Zafer Aydoğan wrote: > 2011/5/13 Zafer Aydoğan: >> Zafer. >> > Hmm... there seems to be very little interest so far. > Although this tool is mainly useful for developers, > what is the correct mailing list to announce it ? The service seems to be good but most people who are developers have their own ways of acting with the sources already and asking them to change their habits built up over many years is hard to do.. people who are looking at sources using a web sute are probably already using fxr.watson.org that doesn't mean that it's not useful, just that it takes people a while to start using a new service.. how does it disambiguate teh same finction names in a kernel and in a /bin program? > Zafer. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 19:57:07 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFDC6106566B for ; Tue, 17 May 2011 19:57:07 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id 9A0CC8FC1B for ; Tue, 17 May 2011 19:57:07 +0000 (UTC) Received: from [127.0.0.1] (proxy8.corp.yahoo.com [216.145.48.13]) by mrout2.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p4HJuffI070274 for ; Tue, 17 May 2011 12:56:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=yahoo-inc.com; s=cobra; t=1305662201; bh=ubsMDKY9S8ukGwVJJYdMEIsGOOynKgnEEi8xhv9Zb/Y=; h=Subject:From:Reply-To:To:Content-Type:Date:Message-ID: Mime-Version:Content-Transfer-Encoding; b=VgRu6gHcPspEvrpFOm3fqTWfst0jVgOzDORx/cYZNCnLidiyvx9vZXq9HEEkjnaKG sAR5cc9PqFMEqWkolm6iKyNntedLYuOOIwIro2rXT5ObYMH/PP8gSMQKaq4CMemQ/X fRrf2nf/xpNAZ8RlcCpBPPEO86VVf3G1rHGMuS1c= From: Sean Bruno To: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Tue, 17 May 2011 12:56:40 -0700 Message-ID: <1305662200.2633.11.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Subject: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 19:57:07 -0000 Silly thing I ran into today. User wanted to NFS mount a dir inside a jail. After I groaned about the security implication of this, I noted that there is a sysctl that looks like it should allow this. Namely, security.jail.mount_allowed. I noted that setting this follows a path that *should* have allowed this silly thing to happen, except that the credentials in the nfsclient were not setup correctly. e.g. VFS_SET(nfs_vfsops, oldnfs, VFCF_NETWORK); ------ I changed this to: VFS_SET(nfs_vfsops, oldnfs, VFCF_NETWORK|VFCF_JAIL); This seems to allow the user's desired effect after setting security.jail.mount_allowed=1 I *think* this is the correct behavior, if a bit silly when taking into account the purpose of a jail. Thoughts? Sean From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 20:17:27 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99BA91065674 for ; Tue, 17 May 2011 20:17:27 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3C9E08FC12 for ; Tue, 17 May 2011 20:17:27 +0000 (UTC) Received: from outgoing.leidinger.net (p5B155F90.dip.t-dialin.net [91.21.95.144]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id EC6D784401B; Tue, 17 May 2011 22:17:12 +0200 (CEST) Received: from unknown (IO.Leidinger.net [192.168.2.110]) by outgoing.leidinger.net (Postfix) with ESMTP id 397FD257A; Tue, 17 May 2011 22:17:10 +0200 (CEST) Date: Tue, 17 May 2011 22:17:12 +0200 From: Alexander Leidinger To: sbruno@freebsd.org Message-ID: <20110517221712.00006e91@unknown> In-Reply-To: <1305662200.2633.11.camel@hitfishpass-lx.corp.yahoo.com> References: <1305662200.2633.11.camel@hitfishpass-lx.corp.yahoo.com> X-Mailer: Claws Mail 3.7.8cvs47 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: EC6D784401B.A1C6C X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1306268234.89759@asVXUHfWskZwec+Av05vCg X-EBL-Spam-Status: No X-Mailman-Approved-At: Tue, 17 May 2011 21:12:42 +0000 Cc: "freebsd-hackers@freebsd.org" Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 20:17:27 -0000 On Tue, 17 May 2011 12:56:40 -0700 Sean Bruno wrote: > Silly thing I ran into today. User wanted to NFS mount a dir inside a > jail. After I groaned about the security implication of this, I noted > that there is a sysctl that looks like it should allow this. Namely, > security.jail.mount_allowed. I noted that setting this follows a path > that *should* have allowed this silly thing to happen, except that the > credentials in the nfsclient were not setup correctly. As you noticed, this is supposed to allow to mount inside a jail, IF the FS you want to mount is marked as secure/safe to do so. Nearly no FS is marked as such, as nobody wants to guarantee that it is safe (root in a jail should not be able to panic a system by trying to mount a corrupt/malicious FS-image) and secure (not possible to get elevated access/privileges). For NFS there is theoretically the problem that the outgoing address on requests could be the one of the physical host instead of the IP of the jail. If this is true in practice, I do not know. This could be the reason why NFS is not marked with VFCF_JAIL. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Tue May 17 23:14:17 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84EA71065675 for ; Tue, 17 May 2011 23:14:17 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 549C08FC0C for ; Tue, 17 May 2011 23:14:17 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p4HNEEgo098011 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 17 May 2011 16:14:15 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DD30142.4010103@freebsd.org> Date: Tue, 17 May 2011 16:14:10 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Alexander Leidinger References: <1305662200.2633.11.camel@hitfishpass-lx.corp.yahoo.com> <20110517221712.00006e91@unknown> In-Reply-To: <20110517221712.00006e91@unknown> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-hackers@freebsd.org" Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 23:14:17 -0000 On 5/17/11 1:17 PM, Alexander Leidinger wrote: > On Tue, 17 May 2011 12:56:40 -0700 Sean Bruno > wrote: > >> Silly thing I ran into today. User wanted to NFS mount a dir inside a >> jail. After I groaned about the security implication of this, I noted >> that there is a sysctl that looks like it should allow this. Namely, >> security.jail.mount_allowed. I noted that setting this follows a path >> that *should* have allowed this silly thing to happen, except that the >> credentials in the nfsclient were not setup correctly. > As you noticed, this is supposed to allow to mount inside a jail, IF > the FS you want to mount is marked as secure/safe to do so. Nearly no > FS is marked as such, as nobody wants to guarantee that it is safe > (root in a jail should not be able to panic a system by trying to > mount a corrupt/malicious FS-image) and secure (not possible to get > elevated access/privileges). > > For NFS there is theoretically the problem that the outgoing address on > requests could be the one of the physical host instead of the IP of the > jail. If this is true in practice, I do not know. This could be > the reason why NFS is not marked with VFCF_JAIL. a vimage jail would not have that problem if we've done it right. > Bye, > Alexander. > From owner-freebsd-hackers@FreeBSD.ORG Wed May 18 00:11:34 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E227106566B for ; Wed, 18 May 2011 00:11:34 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by mx1.freebsd.org (Postfix) with ESMTP id 3F5368FC0A for ; Wed, 18 May 2011 00:11:33 +0000 (UTC) X-AuditID: 12074425-b7b78ae000007e02-d4-4dd30b326714 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id C4.F4.32258.23B03DD4; Tue, 17 May 2011 19:56:34 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id p4HNuVaE005661; Tue, 17 May 2011 19:56:32 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p4HNuUhj001718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 17 May 2011 19:56:31 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id p4HNuTqV029743; Tue, 17 May 2011 19:56:29 -0400 (EDT) Date: Tue, 17 May 2011 19:56:29 -0400 (EDT) From: Benjamin Kaduk To: Mark Saad In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFIsWRmVeSWpSXmKPExsUixG6nrmvEfdnX4MQ9TosNCwotlm7uYXJg 8pjxaT6Lx7Gl29gDmKK4bFJSczLLUov07RK4Mro+ixT85K54s+s0WwPjKc4uRk4OCQETiaub ZrFD2GISF+6tZ+ti5OIQEtjHKNHz6TAjhLOBUeJ053Yo5wCTxK+pc1ggnAZGiaeX1jKD9LMI aEvsnfIAbBabgIrEzDcbgWZxcIgIqEmsO8gDYjIL6Et8ueQDUiEsoCoxd8lBVhCbU8BRYv+c BywgNq+Ag8Sefa8ZQWwhgVKJma+2sYHYogI6Eqv3T4GqEZQ4OfMJmM0sYCnxb+0v1gmMgrOQ pGYhSS1gZFrFKJuSW6Wbm5iZU5yarFucnJiXl1qka6GXm1mil5pSuokRHKQuqjsYJxxSOsQo wMGoxMNb3nvJV4g1say4MvcQoyQHk5IorwLXZV8hvqT8lMqMxOKM+KLSnNTiQ4wSHMxKIrwt Sy/6CvGmJFZWpRblw6SkOViUxHnnS6r7CgmkJ5akZqemFqQWwWRlODiUJHhVQIYKFqWmp1ak ZeaUIKSZODhBhvMADQ8GqeEtLkjMLc5Mh8ifYlSUEufNA0kIgCQySvPgemFJ5BWjONArwrwu IFU8wAQE1/0KaDAT0OBVpy6ADC5JREhJNTBaCPs+MWmVKCg40OjjZjHNKWHrl4CLD5YK8Okp fJ4ba9Sw3v5d6+rmJa++Sn85um3JpwnPFW7eqbb8si6b7U1QydN4pmcS7RsnmG9W0XH+z9Rt yGjiPGFxRXXf759TD/R5rLm95s70x++P+M5a+0TYOnWxdL3PqbMZzDcve/ZW1H/fYhPc9m6L EktxRqKhFnNRcSIAw8GEXv0CAAA= Cc: "hackers@freebsd.org" Subject: Re: Freebsd on the sun x4440 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 00:11:34 -0000 On Tue, 17 May 2011, krad wrote: > On 17 May 2012 01:34, Mark Saad wrote: > >> All >> I am setting up 3 sun x4440 with freebsd 7.3 amd64 . The severs have 4x >> 4-core opterons and 128G of ram each . Once the servers boot they are a good >> fit for what we are doing and preform well . The odd thing I am seeing is a >> long delay in boot up . Once in the initial loading of the kernel at the "|" >> for 1-2 mins . Then again shortly after printing the kernel banner "freebsd >> 7.3-release etc etc etc" . This delay is about 1-2 mins as well. So my >> question does any one know what I could do to speed up the boot up ? I >> suspect the first delay is due to a serial device probe the second is a >> mystery . also the bios load up time is about 5 mins on this box does anyone >> have any ideas on speeding that up ? >> >> ---- >> mark saad >> Nonesuch@longcount.org_______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > > why 7.3? You might have better luck with 8.2. Not I real answer but > sometimes its easier to go around issues As Sean Bruno said in the other thread, this is probably the ~useless "memory check" done at boot; you can find the full thread where it was recently discussed here: http://lists.freebsd.org/pipermail/freebsd-arch/2011-March/011198.html --kaduk From owner-freebsd-hackers@FreeBSD.ORG Wed May 18 00:29:50 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19B77106566B for ; Wed, 18 May 2011 00:29:50 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id C01428FC12 for ; Wed, 18 May 2011 00:29:49 +0000 (UTC) Received: by qwc9 with SMTP id 9so729284qwc.13 for ; Tue, 17 May 2011 17:29:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ejdqE/Wqv+mmmMVnq0ln5MXHL09TEgV6SKVlvXpM2dA=; b=eIghuMJAcVQphrfYITW5hVCoxcedCAoHrkd7YaP5q0tbXGeUXNn0Qmtfga4J0p4ubh 51LNDbQHfVM71BRkXhmn2XTIUr3/2l+UsUoIznTemSx8wJtpUyZa+5hp1RVY7LQHNvlC DrWGUP3bghCYyNxO9hx41b6Arg2IWfA8gN2iA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YjWCQo/pvisHqaWFeWnjkhhdHynREeD6T7FHyUacP6NoJUHDIIIc10h/ahwIY5/P22 TBjlcn2gLihhwZwR5B5dYyvQrZO9ulr45GuiD5jCBvnEtrWk99FaW5w3UdFHaHt0K/il e8ShLnb7xsOy6dgaOka64IZt5a6Nzm1wl9XSw= MIME-Version: 1.0 Received: by 10.229.102.165 with SMTP id g37mr954026qco.120.1305676987666; Tue, 17 May 2011 17:03:07 -0700 (PDT) Received: by 10.229.88.131 with HTTP; Tue, 17 May 2011 17:03:07 -0700 (PDT) In-Reply-To: <1305581685-5144-4-git-send-email-fenghua.yu@intel.com> References: <1305581685-5144-1-git-send-email-fenghua.yu@intel.com> <1305581685-5144-4-git-send-email-fenghua.yu@intel.com> Date: Wed, 18 May 2011 02:03:07 +0200 Message-ID: From: Oliver Pinter To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Fwd: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 00:29:50 -0000 ---------- Forwarded message ---------- From: Fenghua Yu Date: Mon, 16 May 2011 14:34:44 -0700 Subject: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP To: Ingo Molnar , Thomas Gleixner , H Peter Anvin , Asit K Mallick , Linus Torvalds , Avi Kivity , Arjan van de Ven , Andrew Morton , Andi Kleen Cc: linux-kernel , Fenghua Yu From: Fenghua Yu Enable newly documented SMEP (Supervisor Mode Execution Protection) CPU feature in kernel. SMEP prevents the CPU in kernel-mode to jump to an executable page that does not have the kernel/system flag set in the pte. This prevents the kernel from executing user-space code accidentally or maliciously, so it for example prevents kernel exploits from jumping to specially prepared user-mode shell code. The violation will cause page fault #PF and will have error code identical to XD violation. CR4.SMEP (bit 20) is 0 at power-on. If the feature is supported by CPU (X86_FEATURE_SMEP), enable SMEP by setting CR4.SMEP. New kernel option nosmep disables the feature even if the feature is supported by CPU. Signed-off-by: Fenghua Yu --- arch/x86/kernel/head_32.S | 17 +++++++++++++---- arch/x86/kernel/head_64.S | 13 +++++++++++-- 2 files changed, 24 insertions(+), 6 deletions(-) diff --git a/arch/x86/kernel/head_32.S b/arch/x86/kernel/head_32.S index ce0be7c..5325c02 100644 --- a/arch/x86/kernel/head_32.S +++ b/arch/x86/kernel/head_32.S @@ -308,11 +308,20 @@ default_entry: movl cr4_bits,%edx andl %edx,%edx jz 6f - movl %cr4,%eax # Turn on paging options (PSE,PAE,..) - orl %edx,%eax - movl %eax,%cr4 + movl %cr4,%edi # Turn on paging options (PSE,PAE,..) + orl %edx,%edi - testb $X86_CR4_PAE, %al # check if PAE is enabled + /* Check if SMEP is supported by the processor */ + movl $0x7, %eax + movl $0, %ecx + cpuid + btl $7, %ebx + jnc 1f + /* Enable SMEP */ + orl $(X86_CR4_SMEP), %edi +1: movl %edi, %cr4 + + test $X86_CR4_PAE, %di # check if PAE is enabled jz 6f /* Check if extended functions are implemented */ diff --git a/arch/x86/kernel/head_64.S b/arch/x86/kernel/head_64.S index e11e394..220ec5f 100644 --- a/arch/x86/kernel/head_64.S +++ b/arch/x86/kernel/head_64.S @@ -161,8 +161,17 @@ ENTRY(secondary_startup_64) */ /* Enable PAE mode and PGE */ - movl $(X86_CR4_PAE | X86_CR4_PGE), %eax - movq %rax, %cr4 + movl $(X86_CR4_PAE | X86_CR4_PGE), %edi + + /* Check if SMEP is supported by the processor */ + movl $0x7, %eax + movl $0, %ecx + cpuid + btl $7, %ebx + jnc 1f + /* Enable PAE mode, PGE, and SMEP */ + movl $(X86_CR4_PAE | X86_CR4_PGE | X86_CR4_SMEP), %edi +1: movq %rdi, %cr4 /* Setup early boot stage 4 level pagetables. */ movq $(init_level4_pgt - __START_KERNEL_map), %rax -- 1.7.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ From owner-freebsd-hackers@FreeBSD.ORG Wed May 18 01:04:01 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 965FF106566B for ; Wed, 18 May 2011 01:04:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 154C98FC14 for ; Wed, 18 May 2011 01:04:00 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p4I13vwr026745 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2011 04:03:57 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p4I13uld096623; Wed, 18 May 2011 04:03:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p4I13uLu096622; Wed, 18 May 2011 04:03:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 18 May 2011 04:03:55 +0300 From: Kostik Belousov To: Oliver Pinter Message-ID: <20110518010353.GQ48734@deviant.kiev.zoral.com.ua> References: <1305581685-5144-1-git-send-email-fenghua.yu@intel.com> <1305581685-5144-4-git-send-email-fenghua.yu@intel.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H6JajqBy5V+yykme" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-hackers@freebsd.org Subject: Re: Fwd: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 01:04:01 -0000 --H6JajqBy5V+yykme Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 18, 2011 at 02:03:07AM +0200, Oliver Pinter wrote: > ---------- Forwarded message ---------- > From: Fenghua Yu > Date: Mon, 16 May 2011 14:34:44 -0700 > Subject: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP > To: Ingo Molnar , Thomas Gleixner , > H Peter Anvin , Asit K Mallick > , Linus Torvalds > , Avi Kivity , Arjan > van de Ven , Andrew Morton > , Andi Kleen > Cc: linux-kernel , Fenghua Yu > >=20 > From: Fenghua Yu >=20 > Enable newly documented SMEP (Supervisor Mode Execution Protection) CPU > feature in kernel. >=20 > SMEP prevents the CPU in kernel-mode to jump to an executable page that d= oes > not have the kernel/system flag set in the pte. This prevents the kernel > from executing user-space code accidentally or maliciously, so it for exa= mple > prevents kernel exploits from jumping to specially prepared user-mode she= ll > code. The violation will cause page fault #PF and will have error code > identical to XD violation. >=20 > CR4.SMEP (bit 20) is 0 at power-on. If the feature is supported by CPU > (X86_FEATURE_SMEP), enable SMEP by setting CR4.SMEP. New kernel > option nosmep disables the feature even if the feature is supported by CP= U. >=20 > Signed-off-by: Fenghua Yu So, where is the mentioned documentation for SMEP ? Rev. 38 of the Intel(R) 64 and IA-32 Architectures Software Developer's Manual does not contain the description, at least at the places where I looked and expected to find it. Looking forward to hear from you. --H6JajqBy5V+yykme Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk3TGvkACgkQC3+MBN1Mb4grKQCeLFCbpD4Im9Es+5wj7T1F49Zp rTcAoIoLUlOSTGGqJSWOH6UVihcuiHVG =yV+Y -----END PGP SIGNATURE----- --H6JajqBy5V+yykme-- From owner-freebsd-hackers@FreeBSD.ORG Wed May 18 12:31:18 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4A761065781 for ; Wed, 18 May 2011 12:31:18 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-ww0-f68.google.com (mail-ww0-f68.google.com [74.125.82.68]) by mx1.freebsd.org (Postfix) with ESMTP id 77A3D8FC14 for ; Wed, 18 May 2011 12:31:17 +0000 (UTC) Received: by wwb17 with SMTP id 17so194366wwb.7 for ; Wed, 18 May 2011 05:31:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=I8LM58au+HGgVd7zLWITgEoBI/3rr2+HfnbTp6pUmAo=; b=n+sNtl2bIkovdm1XZ1JYPV/sEXD+Rt6TiIb5c0UMi1rZRzdKOW37/hgvZsGjWKOPo7 /G36ZIDV0j70/DeJonGn8exthelnSqApLRrCSeVa/AWWmsGyNj27zHZPcAKVVdXfuux4 y9py/5GuRgNiCtPv7Fc7vqL5eNnasyQTswAgA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Ee6sRK+CerhinaQQ3ZGYXq+Sv5evqo98cxpuXDtMXgMaebVq2NL54vYavLR3CQu2H8 kKNRc/KosFIq0XVrA/Lzt2zcp+CB03OAq3nzCSpW7VeWdmQXQ6goGKxc3+W5KpG89Ezy pm2YaQqu39+mNhPzY5VynNc4DjNo4NaTEwQVs= MIME-Version: 1.0 Received: by 10.227.55.20 with SMTP id s20mr1853370wbg.15.1305721875761; Wed, 18 May 2011 05:31:15 -0700 (PDT) Received: by 10.227.209.209 with HTTP; Wed, 18 May 2011 05:31:15 -0700 (PDT) In-Reply-To: <20110518010353.GQ48734@deviant.kiev.zoral.com.ua> References: <1305581685-5144-1-git-send-email-fenghua.yu@intel.com> <1305581685-5144-4-git-send-email-fenghua.yu@intel.com> <20110518010353.GQ48734@deviant.kiev.zoral.com.ua> Date: Wed, 18 May 2011 14:31:15 +0200 Message-ID: From: Oliver Pinter To: Kostik Belousov Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Fwd: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 12:31:19 -0000 On 5/18/11, Kostik Belousov wrote: > On Wed, May 18, 2011 at 02:03:07AM +0200, Oliver Pinter wrote: >> ---------- Forwarded message ---------- >> From: Fenghua Yu >> Date: Mon, 16 May 2011 14:34:44 -0700 >> Subject: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP >> To: Ingo Molnar , Thomas Gleixner , >> H Peter Anvin , Asit K Mallick >> , Linus Torvalds >> , Avi Kivity , Arjan >> van de Ven , Andrew Morton >> , Andi Kleen >> Cc: linux-kernel , Fenghua Yu >> >> >> From: Fenghua Yu >> >> Enable newly documented SMEP (Supervisor Mode Execution Protection) CPU >> feature in kernel. >> >> SMEP prevents the CPU in kernel-mode to jump to an executable page that >> does >> not have the kernel/system flag set in the pte. This prevents the kernel >> from executing user-space code accidentally or maliciously, so it for >> example >> prevents kernel exploits from jumping to specially prepared user-mode >> shell >> code. The violation will cause page fault #PF and will have error code >> identical to XD violation. >> >> CR4.SMEP (bit 20) is 0 at power-on. If the feature is supported by CPU >> (X86_FEATURE_SMEP), enable SMEP by setting CR4.SMEP. New kernel >> option nosmep disables the feature even if the feature is supported by >> CPU. >> >> Signed-off-by: Fenghua Yu > > So, where is the mentioned documentation for SMEP ? Rev. 38 of the > Intel(R) 64 and IA-32 Architectures Software Developer's Manual does > not contain the description, at least at the places where I looked and > expected to find it. http://www.intel.com/Assets/PDF/manual/325384.pdf Intel=AE 64 and IA-32 Architectures Software Developer=92s Manual Volume 3 (3A & 3B): System Programming Guide > > Looking forward to hear from you. > > From owner-freebsd-hackers@FreeBSD.ORG Wed May 18 14:03:54 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2EAB1065675 for ; Wed, 18 May 2011 14:03:53 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 802828FC1A for ; Wed, 18 May 2011 14:03:53 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 63D8145EAA; Wed, 18 May 2011 16:03:52 +0200 (CEST) Received: from localhost (58.wheelsystems.com [83.12.187.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 1763345E94; Wed, 18 May 2011 16:03:47 +0200 (CEST) Date: Wed, 18 May 2011 16:03:26 +0200 From: Pawel Jakub Dawidek To: Alexander Leidinger Message-ID: <20110518140326.GD1867@garage.freebsd.pl> References: <1305662200.2633.11.camel@hitfishpass-lx.corp.yahoo.com> <20110517221712.00006e91@unknown> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jL2BoiuKMElzg3CS" Content-Disposition: inline In-Reply-To: <20110517221712.00006e91@unknown> X-OS: FreeBSD 9.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-3.9 required=4.5 tests=ALL_TRUSTED,BAYES_00, RCVD_IN_SORBS_DUL autolearn=ham version=3.0.4 Cc: "freebsd-hackers@freebsd.org" Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 14:03:54 -0000 --jL2BoiuKMElzg3CS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 17, 2011 at 10:17:12PM +0200, Alexander Leidinger wrote: > On Tue, 17 May 2011 12:56:40 -0700 Sean Bruno > wrote: >=20 > > Silly thing I ran into today. User wanted to NFS mount a dir inside a > > jail. After I groaned about the security implication of this, I noted > > that there is a sysctl that looks like it should allow this. Namely, > > security.jail.mount_allowed. I noted that setting this follows a path > > that *should* have allowed this silly thing to happen, except that the > > credentials in the nfsclient were not setup correctly. >=20 > As you noticed, this is supposed to allow to mount inside a jail, IF > the FS you want to mount is marked as secure/safe to do so. Nearly no > FS is marked as such, as nobody wants to guarantee that it is safe > (root in a jail should not be able to panic a system by trying to > mount a corrupt/malicious FS-image) and secure (not possible to get > elevated access/privileges). >=20 > For NFS there is theoretically the problem that the outgoing address on > requests could be the one of the physical host instead of the IP of the > jail. If this is true in practice, I do not know. This could be > the reason why NFS is not marked with VFCF_JAIL. It is not marked with VFCF_JAIL, because I just had no time to audit that it is safe. It might be safe in theory. There are some file systems types that can't be securely mounted within a jail no matter what, like UFS, MSDOFS, EXTFS, XFS, REISERFS, NTFS, etc. because the user mounting it has access to raw storage and can corrupt it in a way that it will panic entire system. There are other file systems that don't require access to raw storage for the user doing the mount and chances are they are safe to mount from within a jail, like ZFS (user can have access to ZFS datasets, but don't need access to ZFS pool), NFS, SMBFS, NULLFS, UNIONFS, PROCFS, FDESCFS, etc. I added VFCF_JAIL flag, so there is general mechanism to mark file systems as jail-friendly, but back then I only needed it for ZFS. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --jL2BoiuKMElzg3CS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk3T0a4ACgkQForvXbEpPzQhJwCg3/5m91AHM9BzuoPJXQvbm2lG 2hcAoLCLpgqpQnj+sZ7THlovOmspkeZc =eUsx -----END PGP SIGNATURE----- --jL2BoiuKMElzg3CS-- From owner-freebsd-hackers@FreeBSD.ORG Wed May 18 14:50:31 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B240E106566B for ; Wed, 18 May 2011 14:50:31 +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 870C38FC1C for ; Wed, 18 May 2011 14:50:31 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 27C3146B06; Wed, 18 May 2011 10:50:31 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id AA37A8A050; Wed, 18 May 2011 10:50:30 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 18 May 2011 10:50:30 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <1305581685-5144-1-git-send-email-fenghua.yu@intel.com> <20110518010353.GQ48734@deviant.kiev.zoral.com.ua> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Message-Id: <201105181050.30128.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 18 May 2011 10:50:30 -0400 (EDT) Cc: Kostik Belousov , Oliver Pinter Subject: Re: Fwd: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 14:50:31 -0000 On Wednesday, May 18, 2011 8:31:15 am Oliver Pinter wrote: > On 5/18/11, Kostik Belousov wrote: > > On Wed, May 18, 2011 at 02:03:07AM +0200, Oliver Pinter wrote: > >> ---------- Forwarded message ---------- > >> From: Fenghua Yu > >> Date: Mon, 16 May 2011 14:34:44 -0700 > >> Subject: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP > >> To: Ingo Molnar , Thomas Gleixner , > >> H Peter Anvin , Asit K Mallick > >> , Linus Torvalds > >> , Avi Kivity , Arjan > >> van de Ven , Andrew Morton > >> , Andi Kleen > >> Cc: linux-kernel , Fenghua Yu > >> > >> > >> From: Fenghua Yu > >> > >> Enable newly documented SMEP (Supervisor Mode Execution Protection) CPU > >> feature in kernel. > >> > >> SMEP prevents the CPU in kernel-mode to jump to an executable page that > >> does > >> not have the kernel/system flag set in the pte. This prevents the kern= el > >> from executing user-space code accidentally or maliciously, so it for > >> example > >> prevents kernel exploits from jumping to specially prepared user-mode > >> shell > >> code. The violation will cause page fault #PF and will have error code > >> identical to XD violation. > >> > >> CR4.SMEP (bit 20) is 0 at power-on. If the feature is supported by CPU > >> (X86_FEATURE_SMEP), enable SMEP by setting CR4.SMEP. New kernel > >> option nosmep disables the feature even if the feature is supported by > >> CPU. > >> > >> Signed-off-by: Fenghua Yu > > > > So, where is the mentioned documentation for SMEP ? Rev. 38 of the > > Intel(R) 64 and IA-32 Architectures Software Developer's Manual does > > not contain the description, at least at the places where I looked and > > expected to find it. >=20 > http://www.intel.com/Assets/PDF/manual/325384.pdf >=20 > Intel=AE 64 and IA-32 Architectures Software Developer=92s Manual > Volume 3 (3A & 3B): > System Programming Guide Which revision? It is not documented in revision 38 from April 2011. I just downloaded that link, and it is still revision 38 and has no mention= =20 'SMEP'. Also, bit 20 of CR4 is still marked as Reserved in that manual=20 (section 2.5). =2D-=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed May 18 15:40:12 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4EBE106564A; Wed, 18 May 2011 15:40:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 62A2D8FC0C; Wed, 18 May 2011 15:40:11 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p4IFe7O1015166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2011 18:40:07 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p4IFe72Q000963; Wed, 18 May 2011 18:40:07 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p4IFe7VD000962; Wed, 18 May 2011 18:40:07 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 18 May 2011 18:40:07 +0300 From: Kostik Belousov To: John Baldwin Message-ID: <20110518154007.GR48734@deviant.kiev.zoral.com.ua> References: <1305581685-5144-1-git-send-email-fenghua.yu@intel.com> <20110518010353.GQ48734@deviant.kiev.zoral.com.ua> <201105181050.30128.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mqabeeRFEDQfpoIl" Content-Disposition: inline In-Reply-To: <201105181050.30128.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-hackers@freebsd.org, Oliver Pinter Subject: Re: Fwd: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 15:40:12 -0000 --mqabeeRFEDQfpoIl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 18, 2011 at 10:50:30AM -0400, John Baldwin wrote: > On Wednesday, May 18, 2011 8:31:15 am Oliver Pinter wrote: > > On 5/18/11, Kostik Belousov wrote: > > > On Wed, May 18, 2011 at 02:03:07AM +0200, Oliver Pinter wrote: > > >> ---------- Forwarded message ---------- > > >> From: Fenghua Yu > > >> Date: Mon, 16 May 2011 14:34:44 -0700 > > >> Subject: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP > > >> To: Ingo Molnar , Thomas Gleixner , > > >> H Peter Anvin , Asit K Mallick > > >> , Linus Torvalds > > >> , Avi Kivity , Arjan > > >> van de Ven , Andrew Morton > > >> , Andi Kleen > > >> Cc: linux-kernel , Fenghua Yu > > >> > > >> > > >> From: Fenghua Yu > > >> > > >> Enable newly documented SMEP (Supervisor Mode Execution Protection) = CPU > > >> feature in kernel. > > >> > > >> SMEP prevents the CPU in kernel-mode to jump to an executable page t= hat > > >> does > > >> not have the kernel/system flag set in the pte. This prevents the ke= rnel > > >> from executing user-space code accidentally or maliciously, so it for > > >> example > > >> prevents kernel exploits from jumping to specially prepared user-mode > > >> shell > > >> code. The violation will cause page fault #PF and will have error co= de > > >> identical to XD violation. > > >> > > >> CR4.SMEP (bit 20) is 0 at power-on. If the feature is supported by C= PU > > >> (X86_FEATURE_SMEP), enable SMEP by setting CR4.SMEP. New kernel > > >> option nosmep disables the feature even if the feature is supported = by > > >> CPU. > > >> > > >> Signed-off-by: Fenghua Yu > > > > > > So, where is the mentioned documentation for SMEP ? Rev. 38 of the > > > Intel(R) 64 and IA-32 Architectures Software Developer's Manual does > > > not contain the description, at least at the places where I looked and > > > expected to find it. > >=20 > > http://www.intel.com/Assets/PDF/manual/325384.pdf > >=20 > > Intel? 64 and IA-32 Architectures Software Developer?s Manual > > Volume 3 (3A & 3B): > > System Programming Guide >=20 > Which revision? It is not documented in revision 38 from April 2011. >=20 > I just downloaded that link, and it is still revision 38 and has no menti= on=20 > 'SMEP'. Also, bit 20 of CR4 is still marked as Reserved in that manual= =20 > (section 2.5). This is exactly what I said about rev. 38 in my original reply. --mqabeeRFEDQfpoIl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk3T6FcACgkQC3+MBN1Mb4i6bACgxDsmB8Xdzjrx728CaaFis+sd 5v0AoKnzcbE0AAWzbNh6ayeULLg6/0tv =1K4X -----END PGP SIGNATURE----- --mqabeeRFEDQfpoIl-- From owner-freebsd-hackers@FreeBSD.ORG Wed May 18 16:02:29 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FCD51065670; Wed, 18 May 2011 16:02:29 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id DB4558FC0A; Wed, 18 May 2011 16:02:28 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p4IG2Pxm016772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2011 19:02:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p4IG2PCs001098; Wed, 18 May 2011 19:02:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p4IG2PKY001097; Wed, 18 May 2011 19:02:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 18 May 2011 19:02:25 +0300 From: Kostik Belousov To: Pawel Jakub Dawidek Message-ID: <20110518160225.GS48734@deviant.kiev.zoral.com.ua> References: <1305662200.2633.11.camel@hitfishpass-lx.corp.yahoo.com> <20110517221712.00006e91@unknown> <20110518140326.GD1867@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zLM+hZtO9R0ndG7f" Content-Disposition: inline In-Reply-To: <20110518140326.GD1867@garage.freebsd.pl> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Alexander Leidinger , "freebsd-hackers@freebsd.org" Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 16:02:29 -0000 --zLM+hZtO9R0ndG7f Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 18, 2011 at 04:03:26PM +0200, Pawel Jakub Dawidek wrote: > On Tue, May 17, 2011 at 10:17:12PM +0200, Alexander Leidinger wrote: > > On Tue, 17 May 2011 12:56:40 -0700 Sean Bruno > > wrote: > >=20 > > > Silly thing I ran into today. User wanted to NFS mount a dir inside a > > > jail. After I groaned about the security implication of this, I noted > > > that there is a sysctl that looks like it should allow this. Namely, > > > security.jail.mount_allowed. I noted that setting this follows a path > > > that *should* have allowed this silly thing to happen, except that the > > > credentials in the nfsclient were not setup correctly. > >=20 > > As you noticed, this is supposed to allow to mount inside a jail, IF > > the FS you want to mount is marked as secure/safe to do so. Nearly no > > FS is marked as such, as nobody wants to guarantee that it is safe > > (root in a jail should not be able to panic a system by trying to > > mount a corrupt/malicious FS-image) and secure (not possible to get > > elevated access/privileges). > >=20 > > For NFS there is theoretically the problem that the outgoing address on > > requests could be the one of the physical host instead of the IP of the > > jail. If this is true in practice, I do not know. This could be > > the reason why NFS is not marked with VFCF_JAIL. >=20 > It is not marked with VFCF_JAIL, because I just had no time to audit > that it is safe. It might be safe in theory. >=20 > There are some file systems types that can't be securely mounted within > a jail no matter what, like UFS, MSDOFS, EXTFS, XFS, REISERFS, NTFS, > etc. because the user mounting it has access to raw storage and can > corrupt it in a way that it will panic entire system. >=20 > There are other file systems that don't require access to raw storage > for the user doing the mount and chances are they are safe to mount from > within a jail, like ZFS (user can have access to ZFS datasets, but don't > need access to ZFS pool), NFS, SMBFS, NULLFS, UNIONFS, PROCFS, FDESCFS, > etc. I added VFCF_JAIL flag, so there is general mechanism to mark file > systems as jail-friendly, but back then I only needed it for ZFS. If user does nfs or smbfs mount to the local (or any other controllable) server, then he definitely can plant the DoS or resource starvation attacks. --zLM+hZtO9R0ndG7f Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk3T7ZAACgkQC3+MBN1Mb4g7hACgxz27wbgivjXxoIIM+8KlDOU5 H+IAn2slVRmBHe5fJAkBg/yH5g03E3+O =1Uyz -----END PGP SIGNATURE----- --zLM+hZtO9R0ndG7f-- From owner-freebsd-hackers@FreeBSD.ORG Wed May 18 18:48:03 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64D691065672; Wed, 18 May 2011 18:48:03 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id C6E7D8FC17; Wed, 18 May 2011 18:48:02 +0000 (UTC) Received: by wyf23 with SMTP id 23so1930754wyf.13 for ; Wed, 18 May 2011 11:48:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=aqtG2oJ86j0x2nWX3gMyoFBr6QwnmMHejDbmWcE6wcg=; b=wqGuckbuV5g812JZXNRllE2X6bLyGz2Tdw1ZqJc228kK6eld1ImggwU28b04H3HZ8K 74d2yRdG/uJ4JyDZVteN45on7vWkAZTiBG2a3/3WJy4+EV/YdJZbKbl4JTkgQg1+ZawE 2aOIvDjzKQYvYVw6t/GAhiNuD55ibcMQ3GhQk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ca2I9Ac+P0vUpT6hqmzwRAnC3aU/HohxB8bFPb6GgwvCdG6tvePjR0ymo6x2eOaO+O C2OF8F7OVFqNgccBlaKlOGzPjU4NzPGPgs2TJnYSzEiNNxwztvPU0lOt8C6j/f61X60c 6rzI3iM0fGd/RwNWfI8rUhW3O6QplAS3q6Mkw= MIME-Version: 1.0 Received: by 10.227.55.20 with SMTP id s20mr2238842wbg.15.1305744481136; Wed, 18 May 2011 11:48:01 -0700 (PDT) Received: by 10.227.209.209 with HTTP; Wed, 18 May 2011 11:48:01 -0700 (PDT) In-Reply-To: <20110518154007.GR48734@deviant.kiev.zoral.com.ua> References: <1305581685-5144-1-git-send-email-fenghua.yu@intel.com> <20110518010353.GQ48734@deviant.kiev.zoral.com.ua> <201105181050.30128.jhb@freebsd.org> <20110518154007.GR48734@deviant.kiev.zoral.com.ua> Date: Wed, 18 May 2011 20:48:01 +0200 Message-ID: From: Oliver Pinter To: Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: Fwd: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 18:48:03 -0000 On 5/18/11, Kostik Belousov wrote: > On Wed, May 18, 2011 at 10:50:30AM -0400, John Baldwin wrote: >> On Wednesday, May 18, 2011 8:31:15 am Oliver Pinter wrote: >> > On 5/18/11, Kostik Belousov wrote: >> > > On Wed, May 18, 2011 at 02:03:07AM +0200, Oliver Pinter wrote: >> > >> ---------- Forwarded message ---------- >> > >> From: Fenghua Yu >> > >> Date: Mon, 16 May 2011 14:34:44 -0700 >> > >> Subject: [PATCH v2 3/4] x86, head_32/64.S: Enable SMEP >> > >> To: Ingo Molnar , Thomas Gleixner >> > >> , >> > >> H Peter Anvin , Asit K Mallick >> > >> , Linus Torvalds >> > >> , Avi Kivity , Arjan >> > >> van de Ven , Andrew Morton >> > >> , Andi Kleen >> > >> Cc: linux-kernel , Fenghua Yu >> > >> >> > >> >> > >> From: Fenghua Yu >> > >> >> > >> Enable newly documented SMEP (Supervisor Mode Execution Protection) >> > >> CPU >> > >> feature in kernel. >> > >> >> > >> SMEP prevents the CPU in kernel-mode to jump to an executable page >> > >> that >> > >> does >> > >> not have the kernel/system flag set in the pte. This prevents the >> > >> kernel >> > >> from executing user-space code accidentally or maliciously, so it for >> > >> example >> > >> prevents kernel exploits from jumping to specially prepared user-mode >> > >> shell >> > >> code. The violation will cause page fault #PF and will have error >> > >> code >> > >> identical to XD violation. >> > >> >> > >> CR4.SMEP (bit 20) is 0 at power-on. If the feature is supported by >> > >> CPU >> > >> (X86_FEATURE_SMEP), enable SMEP by setting CR4.SMEP. New kernel >> > >> option nosmep disables the feature even if the feature is supported >> > >> by >> > >> CPU. >> > >> >> > >> Signed-off-by: Fenghua Yu >> > > >> > > So, where is the mentioned documentation for SMEP ? Rev. 38 of the >> > > Intel(R) 64 and IA-32 Architectures Software Developer's Manual does >> > > not contain the description, at least at the places where I looked and >> > > expected to find it. >> > >> > http://www.intel.com/Assets/PDF/manual/325384.pdf >> > >> > Intel? 64 and IA-32 Architectures Software Developer?s Manual >> > Volume 3 (3A & 3B): >> > System Programming Guide >> >> Which revision? It is not documented in revision 38 from April 2011. >> >> I just downloaded that link, and it is still revision 38 and has no >> mention no, under the original intel link i find rev.39 Order Number: 325384-039US May 2011 uploaded here: http://oliverp.teteny.bme.hu/up/325384.pdf >> 'SMEP'. Also, bit 20 of CR4 is still marked as Reserved in that manual >> (section 2.5). > This is exactly what I said about rev. 38 in my original reply. > From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 02:37:25 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE66E106566C; Thu, 19 May 2011 02:37:25 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0B4E58FC13; Thu, 19 May 2011 02:37:24 +0000 (UTC) Received: by iyj12 with SMTP id 12so2552437iyj.13 for ; Wed, 18 May 2011 19:37:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=uACOKuWyB7QLHEpPIdwWzRaeZhHJSGAp6u4+9xCY1qg=; b=qXfHPDHwibAbfwyZVUTZeuxk8NQQP3UDiycW/232jxS7kgEkMy4frzWYl03eEYNTpI K8oKBArVpJvRGXx2GSwpv9ePNQQGC2gPcn77GS3fWVa+CKgg0YcKS0cen7BaKF4t3e1w fjChzrJ2NjD+MYad//Qc3fgAZyYidgwF0v6XU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=OP0J32QDlxO31+jSs1yGmMqmLb+maHdmvZ+sgpHPqi6Ud6k93+dT2+/TOc6kX11JIV e2Enr4Ed1OTnim6o8cSNE6aMFXZU3udrOMcnuF8SJzTmmJSW/BJIiz9DcZeBdtE2SrJF mRks7GBQeoGMlIZSEvec98Y7QCV8vja6jTwow= MIME-Version: 1.0 Received: by 10.43.131.70 with SMTP id hp6mr3096643icc.210.1305772644351; Wed, 18 May 2011 19:37:24 -0700 (PDT) Received: by 10.42.177.10 with HTTP; Wed, 18 May 2011 19:37:24 -0700 (PDT) In-Reply-To: <20110518140326.GD1867@garage.freebsd.pl> References: <1305662200.2633.11.camel@hitfishpass-lx.corp.yahoo.com> <20110517221712.00006e91@unknown> <20110518140326.GD1867@garage.freebsd.pl> Date: Wed, 18 May 2011 22:37:24 -0400 Message-ID: From: Arnaud Lacombe To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Alexander Leidinger , "freebsd-hackers@freebsd.org" Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 02:37:25 -0000 Hi, On Wed, May 18, 2011 at 10:03 AM, Pawel Jakub Dawidek wro= te: > On Tue, May 17, 2011 at 10:17:12PM +0200, Alexander Leidinger wrote: >> On Tue, 17 May 2011 12:56:40 -0700 Sean Bruno >> wrote: >> >> > Silly thing I ran into today. =A0User wanted to NFS mount a dir inside= a >> > jail. =A0After I groaned about the security implication of this, I not= ed >> > that there is a sysctl that looks like it should allow this. =A0Namely= , >> > security.jail.mount_allowed. =A0I noted that setting this follows a pa= th >> > that *should* have allowed this silly thing to happen, except that the >> > credentials in the nfsclient were not setup correctly. >> >> As you noticed, this is supposed to allow to mount inside a jail, IF >> the FS you want to mount is marked as secure/safe to do so. Nearly no >> FS is marked as such, as nobody wants to guarantee that it is safe >> (root in a jail should not be able to panic a system by trying to >> mount a corrupt/malicious FS-image) and secure (not possible to get >> elevated access/privileges). >> >> For NFS there is theoretically the problem that the outgoing address on >> requests could be the one of the physical host instead of the IP of the >> jail. If this is true in practice, I do not know. This could be >> the reason why NFS is not marked with VFCF_JAIL. > > It is not marked with VFCF_JAIL, because I just had no time to audit > that it is safe. It might be safe in theory. > > There are some file systems types that can't be securely mounted within > a jail no matter what, like UFS, MSDOFS, EXTFS, XFS, REISERFS, NTFS, > etc. =A0because the user mounting it has access to raw storage and can > corrupt it in a way that it will panic entire system. > This should at least be configurable somehow for people who are using jails for separation and do not care about security. I'd expect that security decision whether or not to allow something is user relevant, not developer relevant. - Arnaud > There are other file systems that don't require access to raw storage > for the user doing the mount and chances are they are safe to mount from > within a jail, like ZFS (user can have access to ZFS datasets, but don't > need access to ZFS pool), NFS, SMBFS, NULLFS, UNIONFS, PROCFS, FDESCFS, > etc. I added VFCF_JAIL flag, so there is general mechanism to mark file > systems as jail-friendly, but back then I only needed it for ZFS. > From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 08:46:10 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C8ED106566B for ; Thu, 19 May 2011 08:46:10 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 15AC28FC0A for ; Thu, 19 May 2011 08:46:09 +0000 (UTC) Received: by pzk27 with SMTP id 27so1415621pzk.13 for ; Thu, 19 May 2011 01:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:date:message-id:subject :from:to:content-type; bh=5kA6mpDcd+I2FwhAYosEhSG8k2bG3injZg6Kco00NRc=; b=ERaB1jpVWCGd2x2S/XdjP4VRwNS/lt9ixBVYExsovnx9TuJNpUBMzW5yTi56eQJHbL 9wZebqfxUdRibOqFOJzg48XGYsvrqexyFFEGxJ9LS0aEDFmj5AAqUD6T3sn2rvpiZPwW gUnrhS8s9LRjE3lfY848F1wBfOBMa9N40rMbo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; b=fGjrfbOyubk0Xu/niqaocZPzAyLNL5wHn93FLPHl4oTyg7MCpAq8WK33BeJBqXoein Qe2yKym1+A9WWhx/v4yguGRA69qVtJNKi/36DtKV2WnpTZe6FyVPLalgF1V5SsK6KsKr /GgLsT+NZ5h0klEiP75F70HLtQCxCS4eQCbuQ= MIME-Version: 1.0 Received: by 10.68.56.193 with SMTP id c1mr4401289pbq.225.1305788201345; Wed, 18 May 2011 23:56:41 -0700 (PDT) Received: by 10.68.63.104 with HTTP; Wed, 18 May 2011 23:56:41 -0700 (PDT) Date: Wed, 18 May 2011 23:56:41 -0700 Message-ID: From: Josh Carroll To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: How to use Core i7 turbo X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 08:46:10 -0000 I'm running FreeBSD 8.2-RELEASE/amd64 on a Core i7 2600k system with the ASUS P8Z68-V PRO motherboard. I'm trying to get the turbo mode (http://en.wikipedia.org/wiki/Intel_Turbo_Boost) to work in FreeBSD, but I can't seem to make it happen. I've tried: 1. auto settings (3.4 GHz base frequency, 3.8 GHz turbo (on one core) or 3.5 GHz on all cores). 2. manually setting the turbo ratio per core to 38 or 40 3. setting the turbo ratio to 40 "for all cores" I'm running an ffmpeg encode to test the performance, and I'm seeing identical results for both a single-threaded encode (e.g. ffmpeg without -threads) and also if I specify 4, 8 or auto (0) threads with ffmpeg. No matter what I do, the encode runs in the same amount of time. hw.clockrate reports 3400, and dev.cpu.0.freq reports 2900 sometimes and 3401 other times, but never over 3400. I tried setting cx_lowest to C3 for all cores and then running a single threaded ffmpeg encode, in the hopes it was just the other 3 cores idling so that ffmpeg could run on the single core. But that made things much slower (2x slower in fact) for a mult-threaded ffmpeg encode, and about the same for a single threaded ffmpeg encode. Do I need to be running powerd or setting some other sysctl or loader tunables to be able to use this turbo feature? Ideally, I'd like to set things up so they run at 3.8 or 4.0 at all times, but I don't know if there is a way with these SandyBridge CPUs to just do a "simple overclock" as was possible in the past. I don't plan to run it at 4 GHz forever, I just figured I should be able to see at least a 10-15% increase in speed (if not more) if the turbo were working. And so far I'm not seeing any evidence of the turbo working. I appreciate any help you all can provide. Regards, Josh From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 12:44:27 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9964106566C; Thu, 19 May 2011 12:44:27 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 613718FC1A; Thu, 19 May 2011 12:44:27 +0000 (UTC) Received: from outgoing.leidinger.net (p5B155EB3.dip.t-dialin.net [91.21.94.179]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 9438B844015; Thu, 19 May 2011 14:44:12 +0200 (CEST) Received: from webmail.leidinger.net (webmail.Leidinger.net [IPv6:fd73:10c7:2053:1::3:102]) by outgoing.leidinger.net (Postfix) with ESMTP id D2B762714; Thu, 19 May 2011 14:44:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1305809049; bh=npMA8ixizRGzpacyuVrm5XvMREztD8ng/mf70RoeX3w=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=RUZbd/97E9KQFE3LiYdvFMhvFzRSQVyB2qZKah9x71jsZIQnqF8E72LVZRxOsJ7zR q4Lahk4GzIoe18YWwcJ1hVYt9emqmlnNDfZ6V7Q9DA9OzHfx7SwN6sM8YHwkfBz7sG cscQQouiA0rDWCcyjDdERUgUrh8YvoxPj1+q2odDXoTgDi39b3WH1qCeM7LxYB4HyQ lITWihdOJcAytizgpNY2clWKhhZM2O7RVyFfl7nSL/nFrg4P6fDSbR+b2JKWT4TzDR 53DwsAleFaw3p0ya9kEz/fqo1m5tpLz4uJmEBl6v+a0FlqA4wQB5JBSGxCxmdz/KQ/ 97rzI9croVDgA== Received: (from www@localhost) by webmail.leidinger.net (8.14.4/8.14.4/Submit) id p4JCi8s9023537; Thu, 19 May 2011 14:44:08 +0200 (CEST) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: webmail.leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from pslux.ec.europa.eu (pslux.ec.europa.eu [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Thu, 19 May 2011 14:44:08 +0200 Message-ID: <20110519144408.472431slzujrg49k@webmail.leidinger.net> Date: Thu, 19 May 2011 14:44:08 +0200 From: Alexander Leidinger To: Arnaud Lacombe References: <1305662200.2633.11.camel@hitfishpass-lx.corp.yahoo.com> <20110517221712.00006e91@unknown> <20110518140326.GD1867@garage.freebsd.pl> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.6) X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 9438B844015.AE055 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-0.1, required 6, autolearn=disabled, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1306413853.50703@IcECKYaL7rHvU17CON3zvg X-EBL-Spam-Status: No X-Mailman-Approved-At: Thu, 19 May 2011 13:20:42 +0000 Cc: "freebsd-hackers@freebsd.org" , Pawel Jakub Dawidek Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 12:44:27 -0000 Quoting Arnaud Lacombe (from Wed, 18 May 2011 =20 22:37:24 -0400): > Hi, > > On Wed, May 18, 2011 at 10:03 AM, Pawel Jakub Dawidek =20 > wrote: >> There are some file systems types that can't be securely mounted within >> a jail no matter what, like UFS, MSDOFS, EXTFS, XFS, REISERFS, NTFS, >> etc. =C2=A0because the user mounting it has access to raw storage and ca= n >> corrupt it in a way that it will panic entire system. >> > This should at least be configurable somehow for people who are using > jails for separation and do not care about security. I'd expect that > security decision whether or not to allow something is user relevant, > not developer relevant. The hardcoded version of this which I use exacly for the purpose you =20 told here is at http://www.leidinger.net/FreeBSD/current-patches/sys:fs.diff Bye, Alexander. --=20 I think my career is ruined! http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 14:08:14 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CC5E1065678 for ; Thu, 19 May 2011 14:08:14 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id A17F98FC14 for ; Thu, 19 May 2011 14:08:13 +0000 (UTC) Received: by fxm11 with SMTP id 11so2668521fxm.13 for ; Thu, 19 May 2011 07:08:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.100.86 with SMTP id x22mr23080fan.108.1305814092551; Thu, 19 May 2011 07:08:12 -0700 (PDT) Received: by 10.223.83.198 with HTTP; Thu, 19 May 2011 07:08:12 -0700 (PDT) X-Originating-IP: [68.239.212.221] In-Reply-To: <4DD20EA9.5060300@freebsd.org> References: <83D72FE6-15E8-4113-9811-05299D9C2402@longcount.org> <4DD20EA9.5060300@freebsd.org> Date: Thu, 19 May 2011 10:08:12 -0400 Message-ID: From: Mark Saad To: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Freebsd And the sun x4440 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 14:08:14 -0000 On Tue, May 17, 2011 at 1:59 AM, Julian Elischer wrote= : > On 5/16/12 5:42 PM, Mark Saad wrote: >> >> All >> =C2=A0I am setting up 3 sun x4440 with freebsd 7.3 amd64 . The severs ha= ve 4x >> 4-core opterons and 128G of ram each . Once the servers boot they are a = good >> fit for what we are doing and preform well . The odd thing I am seeing i= s a >> long delay in boot up . Once in the initial loading of the kernel at the= "|" >> for 1-2 mins . Then again shortly after printing the kernel banner "free= bsd >> 7.3-release etc etc etc" . =C2=A0This delay is about 1-2 mins as well. = =C2=A0So my >> question does any one know what I could do to speed up the boot up ? I >> suspect the first delay is due to a serial =C2=A0device probe the second= is a >> mystery . also the bios load up time is about 5 mins on this box does an= yone >> have any ideas on speeding that up ? > > I'd suspect that all three are some sort of memory probe or test. > you might also check they are not trying to do a PXE boot first. > > PXE Booting did not make any change in the boot up time. I feel that that what bz@ noted in http://lists.freebsd.org/pipermail/freebsd-arch/2011-March/011198.html is what I am seeing . This along with some serial port weirdness. One the one hand I wish sun would release an updated bios for this server that shows some progress meter on boot up. You literally stare at the same data on the screen for little over 5 mins , its a bit maddening . That combined with the memory check freebsd is doing can make you easily think there is an issue with the hardware . --=20 mark saad | nonesuch@longcount.org From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 17:54:17 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A14CC106566B for ; Thu, 19 May 2011 17:54:17 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.freebsd.org (Postfix) with ESMTP id 599378FC14 for ; Thu, 19 May 2011 17:54:17 +0000 (UTC) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO internal.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 19 May 2011 10:25:30 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by internal.ambrisko.com (8.14.4/8.14.4) with ESMTP id p4JHP0Tf023592; Thu, 19 May 2011 10:25:00 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.4/8.14.4/Submit) id p4JHOxBJ023590; Thu, 19 May 2011 10:24:59 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <201105191724.p4JHOxBJ023590@ambrisko.com> In-Reply-To: To: Arnaud Lacombe Date: Thu, 19 May 2011 10:24:59 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL124d (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Cc: Alexander Leidinger , Pawel Jakub Dawidek , "freebsd-hackers@freebsd.org" Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 17:54:17 -0000 Arnaud Lacombe writes: | Hi, | | On Wed, May 18, 2011 at 10:03 AM, Pawel Jakub Dawidek wrote: | > On Tue, May 17, 2011 at 10:17:12PM +0200, Alexander Leidinger wrote: | >> On Tue, 17 May 2011 12:56:40 -0700 Sean Bruno | >> wrote: | >> | >> > Silly thing I ran into today. ?User wanted to NFS mount a dir inside a | >> > jail. ?After I groaned about the security implication of this, I noted | >> > that there is a sysctl that looks like it should allow this. ?Namely, | >> > security.jail.mount_allowed. ?I noted that setting this follows a path | >> > that *should* have allowed this silly thing to happen, except that the | >> > credentials in the nfsclient were not setup correctly. | >> | >> As you noticed, this is supposed to allow to mount inside a jail, IF | >> the FS you want to mount is marked as secure/safe to do so. Nearly no | >> FS is marked as such, as nobody wants to guarantee that it is safe | >> (root in a jail should not be able to panic a system by trying to | >> mount a corrupt/malicious FS-image) and secure (not possible to get | >> elevated access/privileges). | >> | >> For NFS there is theoretically the problem that the outgoing address on | >> requests could be the one of the physical host instead of the IP of the | >> jail. If this is true in practice, I do not know. This could be | >> the reason why NFS is not marked with VFCF_JAIL. | > | > It is not marked with VFCF_JAIL, because I just had no time to audit | > that it is safe. It might be safe in theory. | > | > There are some file systems types that can't be securely mounted within | > a jail no matter what, like UFS, MSDOFS, EXTFS, XFS, REISERFS, NTFS, | > etc. ?because the user mounting it has access to raw storage and can | > corrupt it in a way that it will panic entire system. | | This should at least be configurable somehow for people who are using | jails for separation and do not care about security. I'd expect that | security decision whether or not to allow something is user relevant, | not developer relevant. Yes, we need to look at having sysctl's to enable more permissive options when jails/vimage are not used to isolate users from systems but other uses. I'm now starting to use vimage in 8.2 and -current to make my "host" trivial but do all of the "smarts" in a vimage. This lets me spin up a new image quickly and migrate. One challenge is wireless. You can't run wpa_supplicant in a vimage. I can understand whey the ioctls are blocked since you could have a wireless instance in one jail and another instance in another jail. However, to manage that instance can require the ioctls and the host doesn't have access to it anymore either. Running an X server in a vimage has some issues. Most are pretty easy to over-come. Maybe it might be good to have a sysctl to not do any checks at all so it acts like a chroot like security.jail.param.allow.all? Doug A. From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 19:26:34 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 519FC106564A for ; Thu, 19 May 2011 19:26:34 +0000 (UTC) (envelope-from lgj@usenix.org) Received: from lonestar.usenix.org (lonestar.usenix.org [131.106.3.102]) by mx1.freebsd.org (Postfix) with ESMTP id 3A7C58FC1D for ; Thu, 19 May 2011 19:26:33 +0000 (UTC) Received: from negroni.usenix.org (negroni.usenix.org [131.106.3.145]) (authenticated bits=0) by lonestar.usenix.org (8.14.2/8.14.2) with ESMTP id p4JJP6QI024627 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 19 May 2011 12:26:33 -0700 (PDT) From: Lionel Garth Jones Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 19 May 2011 12:26:33 -0700 Message-Id: <055DD506-1397-4960-91AF-3D126E5E425A@usenix.org> To: freebsd-hackers@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-DCC-USENIX-Metrics: lonestar; whitelist X-Spam-Status: No, score=0.7 required=6.0 tests=ALL_TRUSTED, FH_DATE_PAST_20XX autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lonestar X-Mailman-Approved-At: Thu, 19 May 2011 20:50:23 +0000 Subject: 2011 USENIX Federated Conferences Week Events and Reminders X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 19:26:34 -0000 You were recently invited to the 2011 USENIX Federated Conferences Week taking place June 14-17, 2011, in Portland, OR. The Early Bird Registration Deadline is approaching. Register online by May 23, 2011, for the greatest possible discount. http://www.usenix.org/fcw11/progb Planning to stay in the conference hotel? Rooms are going fast. Book your room today! http://www.usenix.org/events/fcw11/hotel.html The USENIX Federated Conferences Week offers a unique opportunity to gain insight into a variety of hot topics, while the joint lunches, breaks, and evening events provide cross-topic networking possibilities. Create Your Own Conference Experience USENIX is making it easier than ever to customize a program to meet your needs. Your daily registration gets you into all the events happening that day: tutorials, talks, workshops--you name it. Plus, registration packages offer expanded discounts. The more days you attend, the more you save! USENIX Federated Conferences Week includes: - HotCloud '11: 3rd USENIX Workshop on Hot Topics in Cloud Computing Tuesday-Wednesday, June 14-15, 2011 http://www.usenix.org/events/hotcloud11 HotCloud '11 will discuss challenges in the design, implementation, and deployment of cloud computing. It will be a forum for academics and practitioners to share their experiences and identify emerging trends. - HotStorage '11: 3rd USENIX Workshop on Hot Topics in Storage and File Systems Tuesday, June 14, 2011 http://www.usenix.org/events/hotstorage11 HotStorage '11 will discuss the new opportunities presented by the increase in the volume and variety of digital data, "big data," the proliferation of consumer-electronics storage devices, and more. - WIOV '11: 3rd Workshop on I/O Virtualization Tuesday, June 14, 2011 http://www.usenix.org/events/wiov11 The focus of WIOV '11 is on the interplay of I/O with virtualization and cloud technologies. Our goal is to provide a forum to discuss the impact and challenges of I/O virtualization along multiple dimensions. - Tutorial: Securing Linux Servers Tuesday, June 14, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#t1 This class for Linux sysadmins and security managers shows you how to maintain a strong security posture by minimizing risks through careful configuration and proper use of Linux tools and services. - USENIX ATC '11: 2011 USENIX Annual Technical Conference Wednesday-Friday, June 15-17, 2011 http://www.usenix.org/events/atc11 USENIX ATC '11 offers you cutting-edge systems research and insights into a variety of topics--virtualization, cloud computing, storage, security, distributed systems, personal devices, scheduling, and more. - WebApps '11: 2nd USENIX Conference on Web Application Development Wednesday-Thursday, June 15-16, 2011 http://www.usenix.org/events/webapps11 WebApps '11 is designed to bring together experts in all aspects of developing and deploying Web applications. The program includes refereed papers, posters, invited talks, and a panel. - Tutorial: SELinux (Security-Enhanced Linux) Wednesday, June 15, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#w1 Learn to work with SELinux: how to determine if SELinux is blocking an application and how to adjust policy to move beyond problems. This class is intended for Linux sysadmins and security managers. - Tutorial: VMware vCloud Overview and Design Considerations Wednesday, June 15, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#w2 Sysadmins and architects, get the knowledge you need to deploy a VMware cloud for use as an enterprise private cloud by learning how to implement and manage VMware vCloud technologies. - Tutorial: Linux Performance Tuning Thursday, June 16, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#r1 Intended for intermediate and advanced sysadmins, this class will cover the tools that can be used to monitor and analyze a Linux system, plus key tuning parameters to optimize Linux for server applications. - Tutorial: SANS Security 464: Hacker Detection for Systems Administrators Thursday-Friday, June 16-17, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#r2 This 2-day course is designed to help sysadmins better understand what is required by security teams and auditors and to turn into the human sensors for malicious activity. - Tutorial: Introduction to Automating System Administration with Cfengine 3 Friday, June 17, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#f1 This is your opportunity to get a thorough grounding in automated system administration and configuration using Cfengine v3, and the ability to implement configuration policies on your systems. Whether you are interested in the latest systems computing breakthroughs or want to get the low-down on Web application development, this week in June will have everything you need to stay ahead of the curve. See you in Portland! P.S. Connect with other attendees, check out additional discounts, and help spread the word! Facebook: http://www.facebook.com/event.php?eid=176554335729285 Twitter: http://twitter.com/usenix #FCW11 Additional Discounts: http://www.usenix.org/events/fcw11/discounts.html Help Promote: http://www.usenix.org/events/fcw11/promote.html From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 21:38:52 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D33C106566B; Thu, 19 May 2011 21:38:52 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.freebsd.org (Postfix) with ESMTP id 268C38FC13; Thu, 19 May 2011 21:38:52 +0000 (UTC) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO internal.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 19 May 2011 14:39:10 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by internal.ambrisko.com (8.14.4/8.14.4) with ESMTP id p4JLceZh053382; Thu, 19 May 2011 14:38:40 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.4/8.14.4/Submit) id p4JLceuH053381; Thu, 19 May 2011 14:38:40 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <201105192138.p4JLceuH053381@ambrisko.com> In-Reply-To: <20110519231641.0000242f@unknown> To: Alexander Leidinger Date: Thu, 19 May 2011 14:38:40 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL124d (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Cc: Pawel Jakub Dawidek , Arnaud Lacombe , "freebsd-hackers@freebsd.org" Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 21:38:52 -0000 Alexander Leidinger writes: | On Thu, 19 May 2011 10:24:59 -0700 (PDT) Doug Ambrisko | wrote: | | > doesn't have access to it anymore either. Running an X server in a | > vimage has some issues. Most are pretty easy to over-come. | | Are you using my patch | (http://www.leidinger.net/FreeBSD/current-patches/0_jail.diff) + a | custom devfs.rules to get the 2D part (the last time I tried the DRI | part of my patch, it paniced the machine) of the X server working in a | jail, or did you come up with something yourself? If it is the later, I | would be interested how you did it. Nope, didn't know about it when I played with it. I should try it. I added case PRIV_IO: return (0); to kern_jail.c to get X to work. This was with the Intel graphics. The main problem I have now is on resume the X server dies and restarts. I use xdm. Without jail with vimage then it works okay. My laptop can use either Intel or ATI graphics. I just switched it to ATI to see what happens. I should try some more tests. It seems my BIOS likes to reset this setting and enable both :-( I don't seem to have panics. This is with a month or so old -current. Doug A. From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 21:16:58 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBE9E106566B; Thu, 19 May 2011 21:16:58 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id A68548FC16; Thu, 19 May 2011 21:16:58 +0000 (UTC) Received: from outgoing.leidinger.net (p5B155EB3.dip.t-dialin.net [91.21.94.179]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id F086D844015; Thu, 19 May 2011 23:16:44 +0200 (CEST) Received: from unknown (IO.Leidinger.net [192.168.2.110]) by outgoing.leidinger.net (Postfix) with ESMTP id 3CE8A274A; Thu, 19 May 2011 23:16:42 +0200 (CEST) Date: Thu, 19 May 2011 23:16:41 +0200 From: Alexander Leidinger To: Doug Ambrisko Message-ID: <20110519231641.0000242f@unknown> In-Reply-To: <201105191724.p4JHOxBJ023590@ambrisko.com> References: <201105191724.p4JHOxBJ023590@ambrisko.com> X-Mailer: Claws Mail 3.7.8cvs47 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: F086D844015.A1A53 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-0.4, required 6, autolearn=disabled, ALL_TRUSTED -1.00, J_CHICKENPOX_55 0.60) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1306444606.14309@LW28TYr0v2w2CNZzqpLlnA X-EBL-Spam-Status: No X-Mailman-Approved-At: Thu, 19 May 2011 22:14:36 +0000 Cc: "freebsd-hackers@freebsd.org" , Pawel Jakub Dawidek , Arnaud Lacombe Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 21:16:59 -0000 On Thu, 19 May 2011 10:24:59 -0700 (PDT) Doug Ambrisko wrote: > doesn't have access to it anymore either. Running an X server in a > vimage has some issues. Most are pretty easy to over-come. Are you using my patch (http://www.leidinger.net/FreeBSD/current-patches/0_jail.diff) + a custom devfs.rules to get the 2D part (the last time I tried the DRI part of my patch, it paniced the machine) of the X server working in a jail, or did you come up with something yourself? If it is the later, I would be interested how you did it. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 22:26:40 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C4CA106564A for ; Thu, 19 May 2011 22:26:40 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id D0FB18FC14 for ; Thu, 19 May 2011 22:26:39 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.4/8.14.4) with ESMTP id p4JMD7Ka018500 for ; Thu, 19 May 2011 15:13:07 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.4/8.14.4/Submit) id p4JMD7Wk018499 for hackers@freebsd.org; Thu, 19 May 2011 15:13:07 -0700 (PDT) (envelope-from david) Date: Thu, 19 May 2011 15:13:07 -0700 From: David Wolfskill To: hackers@freebsd.org Message-ID: <20110519221307.GK2135@albert.catwhisker.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="P7Tqkd/m/Jnohiaz" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: Disk quota reporting for usage >2TB X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 22:26:40 -0000 --P7Tqkd/m/Jnohiaz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I recently found that, running FreBSD/i386 stable/8 as of around r221857, the disk quota subsystem appears to overflow & wrap as it crosses the 2TB mark. Evidence: I ran a task in a loop, invoking "quota -h" after each iteration. Each invocation should write about 114.2GB to the file system. Eliding redundant headers, a relevant excerpt of the output, along with "df -h" output for the file system in question: =20 Disk quotas for user ,...] (uid 9874):=20 Filesystem usage quota limit grace files quota limit g= race /d 1.8T 0B 0B 25217562 0 0 = =20 /d 1.9T 0B 0B 26793658 0 0 = =20 /d 14G 0B 0B 28369755 0 0 = =20 =2E.. /d 815G 0B 0B 39402435 0 0 = =20 Filesystem Size Used Avail Capacity Mounted on /dev/mfid1 15T 2.8T 11T 19% /d Now, this is a machine I'm testing -- I'm the only one writing to that file system (other than the quota.user file). Now, I don't have a defined quota; the intent is not to use the quota subsystem to restrict how myuch disk space folks use, but rather, to use it to measure and track the usage. For this purpose, I really have no particular desire for precision to the KB; precision could easily be as coarse as to the GB and still be useful -- for this purpose, under these circumstances. Does anyone see a way to use the disk quota subsystem to track storage >2TB on a single (UFS2) file system? Thanks! Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --P7Tqkd/m/Jnohiaz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEARECAAYFAk3VlfIACgkQmprOCmdXAD36CwCfXgeWqrHlt5vu2qcQdNNplnRz 33AAniu7J8d0KV4fPTzvGrksIlUcNh/b =HHJP -----END PGP SIGNATURE----- --P7Tqkd/m/Jnohiaz-- From owner-freebsd-hackers@FreeBSD.ORG Thu May 19 22:47:01 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42026106566C for ; Thu, 19 May 2011 22:47:01 +0000 (UTC) (envelope-from benl@google.com) Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by mx1.freebsd.org (Postfix) with ESMTP id ECF2B8FC13 for ; Thu, 19 May 2011 22:47:00 +0000 (UTC) Received: from wpaz17.hot.corp.google.com (wpaz17.hot.corp.google.com [172.24.198.81]) by smtp-out.google.com with ESMTP id p4JMakqr023633 for ; Thu, 19 May 2011 15:36:46 -0700 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1305844606; bh=ZvunpOlHjuDSsCYD3raWy8JUDiU=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=IZCNf9AnyVZkc1o0RhS/0M1s19ly7QPurzQARoXF3JSlGx1xzzFXdFGtykEjJOAaw 7HnDWP3qIaImF5gq3m49w== Received: from pwi15 (pwi15.prod.google.com [10.241.219.15]) by wpaz17.hot.corp.google.com with ESMTP id p4JMaf5O032444 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Thu, 19 May 2011 15:36:45 -0700 Received: by pwi15 with SMTP id 15so1843465pwi.5 for ; Thu, 19 May 2011 15:36:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=LNv9PPGdD6O3p/3j8N//YFt/bzKe9kRw5YIEqspO9Eg=; b=JMzY3gsZ6mQ78EYrCcWkjNTh4qk1oBuVlDndAsE0LNUUoI4eZDbEwPlMbTs5xarRNE 5aOopIAJDe112cQv0HiQ== DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:date:message-id:subject:from:to:content-type; b=LR2HqhJQaUD16hovMB2TqpPc0GeMRYVmrsHGSr78zEmcUTRHTIRNXQzhje9PsdrTKZ vUPntCLIwCDk73slysoQ== MIME-Version: 1.0 Received: by 10.142.125.2 with SMTP id x2mr2232385wfc.200.1305844604753; Thu, 19 May 2011 15:36:44 -0700 (PDT) Received: by 10.143.92.7 with HTTP; Thu, 19 May 2011 15:36:44 -0700 (PDT) Date: Thu, 19 May 2011 15:36:44 -0700 Message-ID: From: Ben Laurie To: hackers@freebsd.org X-System-Of-Record: true X-Mailman-Approved-At: Fri, 20 May 2011 00:02:43 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: __asm_printf__ X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 22:47:01 -0000 So, I'm fixing clang warnings. One I don't have much idea what to do with, mainly because this attribute appears to be completely undocumented, is: /scratch/tmp/benl/work/head/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/outpu\ t.h:123:6: warning: 'format' attribute argument not supported: __asm_fprintf__ any clues? From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 00:03:05 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98AEB1065687 for ; Fri, 20 May 2011 00:03:05 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4A79D8FC15 for ; Fri, 20 May 2011 00:03:05 +0000 (UTC) Received: by vws18 with SMTP id 18so3177198vws.13 for ; Thu, 19 May 2011 17:03:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=96sEyoFFGa4JlLODk56WYYAf4yKtNAwTvacVUYff6K4=; b=kpoYZrjMEYOHFRnDoyJq2aJtSg7T44zDDEg25UFgohdryacBf/SZ8mQZvQ82b7L9zS DNWdJtadofiDrZ015hgVOyOJiwCOPR3KLx5RIo7I/Gzg433hndvr4R7+Oy288GpmlhqF tLgcyO6BBoQb0IgVTsEBfeNIFn0TPRyO/vFEo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=gI0++U3BWe0En9SCEkoFF7hiF4QRzr5HtYz6LEcFicIZl0Glt4vY68DEt3GTWwej/n Bw0hJFB/jgsGsJnchxZi9dyvjSkNH+ouqEpmFAK0lXrg2EoWepIWYm1yrviRBeXUCbjR SMzwOckt3UdXXbNVN6hYJOP1VOPZaNI+9x29c= MIME-Version: 1.0 Received: by 10.220.132.137 with SMTP id b9mr1041380vct.247.1305848316162; Thu, 19 May 2011 16:38:36 -0700 (PDT) Received: by 10.220.188.202 with HTTP; Thu, 19 May 2011 16:38:36 -0700 (PDT) In-Reply-To: <20110519221307.GK2135@albert.catwhisker.org> References: <20110519221307.GK2135@albert.catwhisker.org> Date: Thu, 19 May 2011 16:38:36 -0700 Message-ID: From: Garrett Cooper To: David Wolfskill Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: hackers@freebsd.org Subject: Re: Disk quota reporting for usage >2TB X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 00:03:05 -0000 On Thu, May 19, 2011 at 3:13 PM, David Wolfskill wro= te: > I recently found that, running FreBSD/i386 stable/8 as of around > r221857, the disk quota subsystem appears to overflow & wrap as it > crosses the 2TB mark. > > Evidence: =A0I ran a task in a loop, invoking "quota -h" after each > iteration. =A0Each invocation should write about 114.2GB to the file > system. =A0Eliding redundant headers, a relevant excerpt of the output, > along with "df -h" output for the file system in question: > > Disk quotas for user ,...] (uid 9874): > =A0 =A0 Filesystem =A0 usage =A0 quota =A0 limit =A0 grace =A0 files =A0 = quota =A0 limit =A0 grace > =A0 =A0 =A0 =A0 =A0 =A0 /d =A0 =A01.8T =A0 =A0 =A00B =A0 =A0 =A00B =A0 = =A0 =A0 =A0 25217562 =A0 =A0 =A0 0 =A0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0 /d =A0 =A01.9T =A0 =A0 =A00B =A0 =A0 =A00B =A0 = =A0 =A0 =A0 26793658 =A0 =A0 =A0 0 =A0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0 /d =A0 =A0 14G =A0 =A0 =A00B =A0 =A0 =A00B =A0 = =A0 =A0 =A0 28369755 =A0 =A0 =A0 0 =A0 =A0 =A0 0 > ... > =A0 =A0 =A0 =A0 =A0 =A0 /d =A0 =A0815G =A0 =A0 =A00B =A0 =A0 =A00B =A0 = =A0 =A0 =A0 39402435 =A0 =A0 =A0 0 =A0 =A0 =A0 0 > > Filesystem =A0 =A0Size =A0 =A0Used =A0 Avail Capacity =A0Mounted on > /dev/mfid1 =A0 =A0 15T =A0 =A02.8T =A0 =A0 11T =A0 =A019% =A0 =A0/d > > Now, this is a machine I'm testing -- I'm the only one writing to > that file system (other than the quota.user file). > > Now, I don't have a defined quota; the intent is not to use the quota > subsystem to restrict how myuch disk space folks use, but rather, to use > it to measure and track the usage. > > For this purpose, I really have no particular desire for precision to > the KB; precision could easily be as coarse as to the GB and still be > useful -- for this purpose, under these circumstances. > > Does anyone see a way to use the disk quota subsystem to track storage >>2TB on a single (UFS2) file system? des@ and mckusick@ completed the 64-bit quota work on CURRENT last year, but it hasn't been MFCed to 8-STABLE (probably because it breaks KBIs). More info can be found here: http://www.freebsd.org/projects/bigdisk/index.html . HTH, -Garrett From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 03:13:25 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BD461065679 for ; Fri, 20 May 2011 03:13:25 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 8FB9D8FC18 for ; Fri, 20 May 2011 03:13:24 +0000 (UTC) Received: from sbhfislrext02.fnfis.com ([192.168.249.140]) by SCSFISLTC02 (8.14.3/8.14.3) with ESMTP id p4K3DNeQ009033; Thu, 19 May 2011 22:13:23 -0500 Received: from sbhfisltcgw01.FNFIS.COM (Not Verified[10.132.248.121]) by sbhfislrext02.fnfis.com with MailMarshal (v6, 5, 4, 7535) id ; Thu, 19 May 2011 22:13:28 -0500 Received: from SBHFISLTCGW04.FNFIS.COM ([10.132.248.123]) by sbhfisltcgw01.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Thu, 19 May 2011 22:13:23 -0500 Received: from [10.0.0.102] ([10.132.254.136]) by SBHFISLTCGW04.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 19 May 2011 22:13:22 -0500 Mime-Version: 1.0 (Apple Message framework v1084) From: Devin Teske In-Reply-To: Date: Thu, 19 May 2011 20:13:21 -0700 Message-Id: <736597F0-4582-450D-B176-D9D9E073CAEE@vicor.com> References: <00b601cc11d5$5c83f5c0$158be140$@vicor.com> <24057187-9777-4CFF-92D1-1D6103B35280@vicor.com> <4DD11D93.2070307@FreeBSD.org> To: FreeBSD Hackers X-Mailer: Apple Mail (2.1084) X-OriginalArrivalTime: 20 May 2011 03:13:23.0105 (UTC) FILETIME=[E09D5110:01CC169B] Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: [RELEASE] New Boot-Loader Menu -- version 1.6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 03:13:25 -0000 Hi Hackers, I'm pleased to announce version 1.6 of my new boot loader menu software. NOTE: Version 1.6 has the same look and feel as version 1.5. No new screens= hots needed. This is a general cleanup with the below notable changes: 1. Change chkpassword.4th to query "password" environment variable instead = of "loader_password" (for backward compatibility) 2. Rename chkpasswd function in chkpassword.4th to check-password (for back= ward compatibility) 3. Rename chkpassword.4th to check-password.4th (for consistency) 4. Replace conflicting check-password function in /boot/loader.4th with "in= clude /boot/check-password.4th" 5. Remove conflicting password routines from /boot/support.4th 6. [Re-]Implement beastie-start in beastie.4th (for backward compatibility) 7. Replace loader.rc in the package with the default version provided on i3= 86-compatible installs 8. Remove default delay in loading /boot/menu.rc (still available by settin= g loader_delay in loader.conf(5) but disabled by default now) 9. Add $FreeBSD$ CVS keywords in preparation of commit to HEAD 10. Fix a couple typos in comments 11. Add support for autoboot_delay=3D"NO" or autoboot_delay=3D"-1" in menu.= 4th to disable the menu timeout 12. Add missing cleanup routine to menu-clear in menu.4th 13. Add the following manpages: /usr/share/man/man8/beastie.4th.8.gz /usr/share/man/man8/brand.4th.8.gz /usr/share/man/man8/check-password.4th.8.gz /usr/share/man/man8/color.4th.8.gz /usr/share/man/man8/delay.4th.8.gz /usr/share/man/man8/menu.4th.8.gz /usr/share/man/man8/version.4th.8.gz 14. Update loader.conf.5 manpage to include documentation on new loader_log= o values (``orb'' and ``orbbw''), also documenting the new default (orbbw). You can get your update from either: http://druidbsd.sourceforge.net/ or http://druidbsd.sourceforge.net/download/loader_menu-1.6.tgz --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. _____________ From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 06:29:28 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 190CE106564A; Fri, 20 May 2011 06:29:27 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 683A18FC12; Fri, 20 May 2011 06:29:27 +0000 (UTC) Received: from outgoing.leidinger.net (p5B153850.dip.t-dialin.net [91.21.56.80]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 33AA1844015; Fri, 20 May 2011 08:29:10 +0200 (CEST) Received: from webmail.leidinger.net (webmail.Leidinger.net [IPv6:fd73:10c7:2053:1::3:102]) by outgoing.leidinger.net (Postfix) with ESMTP id 702CE27BB; Fri, 20 May 2011 08:29:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1305872947; bh=qbZoqp1gkrJWaU+VWyoRPEDeCX+iCZ5WR0JeYKJ4ahc=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=1fO11qwgJJpHkC06J64dN88WiAiufG5A5Cl2ADDY3AfDZfgooJwplg70f9yd7eTlC U33HZLlhPMhZebF2eg0UGRxr4VyJWSRbunYjyoF2IlqNa95b/4yt8VJenkeJC3825g ludSk40iI8dj1lF0FKJPD2CJa/KYig0xn/7c1W7pec9mP4kU/B5lur051yXW68JPXk X+wGHfak25gD5+LVI+YUWWj4MmXjrvUJUfxH6NoPJA4qjxTLo7IicXKNbdKnwRzv5F c7Gcar4mXPZ8aO6i/pnnC3u1c9dzU2TSRLEDfhXRUSOcgMdodCimtUc31gL6p6vwK4 e9ySdp6Xx2XdQ== Received: (from www@localhost) by webmail.leidinger.net (8.14.4/8.14.4/Submit) id p4K6T5VQ066412; Fri, 20 May 2011 08:29:05 +0200 (CEST) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: webmail.leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from pslux.ec.europa.eu (pslux.ec.europa.eu [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Fri, 20 May 2011 08:29:05 +0200 Message-ID: <20110520082905.1914751s9bwb2w4x@webmail.leidinger.net> Date: Fri, 20 May 2011 08:29:05 +0200 From: Alexander Leidinger To: Doug Ambrisko References: <201105192138.p4JLceuH053381@ambrisko.com> In-Reply-To: <201105192138.p4JLceuH053381@ambrisko.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.6) X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 33AA1844015.AE109 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=0.5, required 6, autolearn=disabled, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, J_CHICKENPOX_55 0.60) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1306477754.54569@yagWpQhFEP7PatIGf9L2YQ X-EBL-Spam-Status: No X-Mailman-Approved-At: Fri, 20 May 2011 11:02:32 +0000 Cc: "freebsd-hackers@freebsd.org" , Pawel Jakub Dawidek , Arnaud Lacombe Subject: Re: NFS mount inside jail fails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 06:29:28 -0000 Quoting Doug Ambrisko (from Thu, 19 May 2011 14:38:40 -0700 (PDT)): > Alexander Leidinger writes: > | On Thu, 19 May 2011 10:24:59 -0700 (PDT) Doug Ambrisko > | wrote: > | > | > doesn't have access to it anymore either. Running an X server in a > | > vimage has some issues. Most are pretty easy to over-come. > | > | Are you using my patch > | (http://www.leidinger.net/FreeBSD/current-patches/0_jail.diff) + a > | custom devfs.rules to get the 2D part (the last time I tried the DRI > | part of my patch, it paniced the machine) of the X server working in a > | jail, or did you come up with something yourself? If it is the later, I > | would be interested how you did it. > > Nope, didn't know about it when I played with it. I should try it. > I added > case PRIV_IO: > return (0); > > to kern_jail.c to get X to work. This was with the Intel graphics. > The main problem I have now is on resume the X server dies and restarts. > I use xdm. Without jail with vimage then it works okay. I use it without vimage in a jail. This is with a radeon card (corresponding kernel module loaded at boot to get 2D acceleration, as the X server obviously can not load modules in a jail). > My laptop can use either Intel or ATI graphics. I just switched it to > ATI to see what happens. I should try some more tests. It seems > my BIOS likes to reset this setting and enable both :-( > > I don't seem to have panics. This is with a month or so old -current. You do not allow access to the dri device, so I do not expect a panic. If you give access to the dri device (which can be enabled separately in my patch), I would not be surprised to see a panic (the last time I tried it is a year or two ago, I didn't take the time to investigate why it panics). Bye, Alexander. -- FORTUNE'S RULES TO LIVE BY: #2 Never goose a wolverine. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 12:08:24 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E1ED106566B for ; Fri, 20 May 2011 12:08:24 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.freebsd.org (Postfix) with ESMTP id 37A218FC19 for ; Fri, 20 May 2011 12:08:23 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 1QNNvQ-000MGW-Ke for hackers@freebsd.org; Fri, 20 May 2011 14:31:24 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 May 2011 14:31:24 +0300 From: Daniel Braniss Message-ID: Cc: Subject: who is in swap? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 12:08:24 -0000 Hi, We have a host, providing mainly http/postgres service, and its swap usage is increasing. Is there any way to check which process is using swap space? some facts it's running 8.2-stable/amd64 has 24gb of memory zfs seems to be ok, arc size too. top says 32G in use, while vmstat avm is around 2G (can't figure this one) top seems to be concervative as to free memory vs. vmstat it's dataless. the swap usage is monotonic increasing, but it will take some 20 days to exhaust the space, it will hang before that :-( - which is what I'm trying to find why cheers, danny From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 12:43:42 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D67C81065673 for ; Fri, 20 May 2011 12:43:42 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 8353B8FC12 for ; Fri, 20 May 2011 12:43:42 +0000 (UTC) Received: from overdrive.ws.pitbpa0.priv.collaborativefusion.com (overdrive.ws.pitbpa0.priv.collaborativefusion.com [192.168.2.119]) (AUTH: LOGIN wmoran, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Fri, 20 May 2011 08:32:49 -0400 id 0003F439.000000004DD65F71.0001271A Date: Fri, 20 May 2011 08:32:48 -0400 From: Bill Moran To: Daniel Braniss Message-Id: <20110520083248.0e7c249f.wmoran@collaborativefusion.com> In-Reply-To: References: Organization: Bill Moran X-Mailer: Sylpheed 3.0.3 (GTK+ 2.20.1; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: who is in swap? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 12:43:42 -0000 In response to Daniel Braniss : > Hi, > We have a host, providing mainly http/postgres service, and its > swap usage is increasing. Is there any way to check which process > is using swap space? > > some facts > it's running 8.2-stable/amd64 > has 24gb of memory > zfs seems to be ok, arc size too. > top says 32G in use, while vmstat avm is around 2G (can't figure this one) > top seems to be concervative as to free memory vs. vmstat > it's dataless. > > the swap usage is monotonic increasing, but it will take some 20 days > to exhaust the space, it will hang before that :-( - which > is what I'm trying to find why top -o res Will sort the top display by largest user of memory. keep in mind that PostgreSQL can be deceiving because it includes the shared memory in that display, which is shared by all PG processes and therefore not as bit a hit as it seems. That output should allow you to narrow down which process is allocating so much RAM. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran@collaborativefusion.com Phone: 412-422-3463x4023 **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. **************************************************************** From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 15:55:32 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2718E106567C for ; Fri, 20 May 2011 15:55:32 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id D4F008FC12 for ; Fri, 20 May 2011 15:55:31 +0000 (UTC) Received: by vws18 with SMTP id 18so3794303vws.13 for ; Fri, 20 May 2011 08:55:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=MyMMfli82vyM/XP5cLTHQC6sxVTldvEmqsxcMgRXsa4=; b=EV7BO2d9Mb9N6sXEjjDvRGiq+d84QVgw6KjVJcaUP9EcpMd3bfoN0wKwE6wD5D+8jW xIwHrGBZF9q/OMRBpsRpWLGJSyPpmD5lk43qnOaA6ptxkwBKUU5qVy6KeyJhC5IMw9wC 1LkNaE+idc422fopcsMAMuhL1YJvbdwz5rDGk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=gcjIfllpzCmY7RUzwJbBdWX1aH1ye1XWqERIsK2RuKJDEwu50KogqE1zqfLXfg4p3K F/OgpNgMRqG6Pb7WOELNL4Bj5afpdHfl/trrFsqdwTzdfE3jbZoUdMaUDr2fn86LXOqk ziWsD/GZQWEyAho2g3+mB7jJ2DMSVUzupQsOU= MIME-Version: 1.0 Received: by 10.52.67.146 with SMTP id n18mr1727500vdt.232.1305906931055; Fri, 20 May 2011 08:55:31 -0700 (PDT) Received: by 10.220.183.11 with HTTP; Fri, 20 May 2011 08:55:30 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 May 2011 08:55:30 -0700 Message-ID: From: Garrett Cooper To: Ben Laurie Content-Type: text/plain; charset=ISO-8859-1 Cc: hackers@freebsd.org Subject: Re: __asm_printf__ X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 15:55:32 -0000 On Thu, May 19, 2011 at 3:36 PM, Ben Laurie wrote: > So, I'm fixing clang warnings. > > One I don't have much idea what to do with, mainly because this attribute > appears to be completely undocumented, is: > > /scratch/tmp/benl/work/head/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/outpu\ > t.h:123:6: warning: 'format' attribute argument not supported: > __asm_fprintf__ > > any clues? Look through contrib/gcc/ChangeLog // search google for more details. It looks like a good place to start. Thanks, -Garrett From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 18:00:20 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D23B106564A for ; Fri, 20 May 2011 18:00:20 +0000 (UTC) (envelope-from sathler90@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id EE0788FC14 for ; Fri, 20 May 2011 18:00:19 +0000 (UTC) Received: by fxm11 with SMTP id 11so3919118fxm.13 for ; Fri, 20 May 2011 11:00:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=4Qh6QqvGMjhNuy5Y9AX2jLv/iAc5m+mwgrbDdLo3Bz4=; b=iZQl4PWTl3SRRO2tJBoeOd44VfDgSiNTmi5ZvHhOFmGGJWxHr0/v6c1tXtWfFN8fvh tG3omvnuGL85Uv/ZU/lgTnbsoonLtvi5oyhwtM2yAV0VIobxIM2BVulPP1Ck76Ao822r IodR0+a7JCblv5o1XWhOhOoe205UNmqe8MAz0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=JbiGKOia1KJ2WOl66WlV75tQsPsMt2TIAV96vAVpKcFafF1zRoAHw51Ylet56TZ0ue gtVIeqwlGalFLBRPmpDSMWaBLOPXWSwKcIKcK6UsVM2KaWkiGo9fSDlK9mZ+CkiVRCQD Wl4CMweUsoLPsvPPutqLyzS92CyEcIlo5/kb4= MIME-Version: 1.0 Received: by 10.223.17.141 with SMTP id s13mr5331835faa.23.1305912979242; Fri, 20 May 2011 10:36:19 -0700 (PDT) Received: by 10.223.72.198 with HTTP; Fri, 20 May 2011 10:36:19 -0700 (PDT) Date: Fri, 20 May 2011 14:36:19 -0300 Message-ID: From: Eduardo To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: upgrade to version 8 - can not mount root X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 18:00:20 -0000 Greetings, I have 2 machines on version 7 and I am having trouble trying an upgrade to version 8 ... already tried 8.0, 8.2 and 8 stable ... same problem, can not mount root file system on both of them. I follow the 'standard' upgrade procedure, ie, csup, buildworld, buildkernel, installkernel and reboot.I have been using the GENERIC kernel, ie, no customizations. I had the same problem on a server (dell 1650) a few months ago and ended up upgrading to 7.4, so it is a weird problem that only happens to version 8. This one machine I am doing now is a box on my desk, so I can try anything to debug it ... (it is an old IBM netfinity with a PIII and 2 scsi disks). I even tought it was somewhat related to disk, so I switched the fstab to the geom labels ... but no luck ... had the same problem. boot messages are below: da0 at ahc0 bus0 scbus0 target 5 lun 0 da0 messages ... da0 at ahc0 bus0 scbus0 target 6 lun 0 da1 messages ... Trying to mount root from ufs:/dev/da0s1a ROOT MOUNT ERROR: If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=3Drw and then remove invalid mount options from /etc/fstab Loader variables: vfs.root.mountfrom=3Dufs:/dev/da0s1a vfs.root.mountfrom.options=3Drw Manual root filesystem specification: ...etc.. mountroot> pani: Root mount failed, startup aborted. cpuid=3D0 KBD: stack backtrace: #0 0xc08ebe67 at kdb_backtrace+0x47 #1 0xc08bc627 at panic+0x117 #2 0xc0943fc7 at vfs_mountroot+0x4f7 #3 0xc08737c0 at start_init+0x60 #4 0xc0890f51 at fork_exit+0x91 #5 0xc0bd5b84 at fork_trampoline+0x8 I can boot the old kernel at 7.2 and recompile again with debug flags as ne= eded. One thing I did try just now was to install 8.2 from the CD ... after I choose install options and he goes to create the filesystems I get these error messages: Unable to find device node for /dev/da0s1b in /dev! The creation of filesystems will be aborted. Couldn=B4t make filesystems properly. Aborting. thanks in advance, -Eduardo. From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 18:51:10 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42C66106566B for ; Fri, 20 May 2011 18:51:10 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 2E4FB8FC14 for ; Fri, 20 May 2011 18:51:08 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p4KIB2rp023996 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 20 May 2011 11:11:04 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DD6AEB4.3090609@freebsd.org> Date: Fri, 20 May 2011 11:11:00 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Bill Moran References: <20110520083248.0e7c249f.wmoran@collaborativefusion.com> In-Reply-To: <20110520083248.0e7c249f.wmoran@collaborativefusion.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: who is in swap? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 18:51:10 -0000 On 5/20/11 5:32 AM, Bill Moran wrote: > In response to Daniel Braniss: > no, Who's on 3rd From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 19:41:39 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11B7D106566B for ; Fri, 20 May 2011 19:41:39 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 94DF78FC12 for ; Fri, 20 May 2011 19:41:38 +0000 (UTC) Received: by fxm11 with SMTP id 11so3993170fxm.13 for ; Fri, 20 May 2011 12:41:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=n0HNLCeLOGGl9Yma2/69VM9gI10WUqaQ58Lgiv75UAI=; b=KlwIjRs4nrC80P+/W9q/IqRhoWjs4IHy7CJyc9cQmKclwclkjE/4r0wNfFMwoSAEP1 DUVqPOwS0Avw8exOukM7r0nkrHTggvdLqK6DVKi8tT8xh+ZkVaotJIOA+JfSWFBz5cEM oGyC/EE/9h7u4sQexdGYNdbPoVHqQxcQQvvN8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=OUCTXgazAIc3wOAfObP+WWHIqEkFAK0ApYRuK+0B8Zo0s2ge2sRPYBakHaxCa3t3/5 wqOXEkORzPBXbBthyPYyJc7zAp17b83UQPqi/+tfcuk00LYe/1FOmhra3YU4HRIaUtOh +zrVclPNc6YJ7wT4TFo8jbNjAvfXIq9J9mFxE= MIME-Version: 1.0 Received: by 10.223.72.202 with SMTP id n10mr5404900faj.88.1305918972833; Fri, 20 May 2011 12:16:12 -0700 (PDT) Received: by 10.223.118.148 with HTTP; Fri, 20 May 2011 12:16:12 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 May 2011 14:16:12 -0500 Message-ID: From: Adam Vande More To: Daniel Braniss Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hackers@freebsd.org Subject: Re: who is in swap? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 19:41:39 -0000 On Fri, May 20, 2011 at 6:31 AM, Daniel Braniss wrote: > Hi, > We have a host, providing mainly http/postgres service, and its > swap usage is increasing. Is there any way to check which process > is using swap space? > > some facts > it's running 8.2-stable/amd64 > has 24gb of memory > zfs seems to be ok, arc size too. > top says 32G in use, while vmstat avm is around 2G (can't figure this one) > top seems to be concervative as to free memory vs. vmstat > it's dataless. > > the swap usage is monotonic increasing, but it will take some 20 days > to exhaust the space, it will hang before that :-( - which > is what I'm trying to find why > ps ax If second character of state column is W, the process is swapped out. -- Adam Vande More From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 21:57:13 2011 Return-Path: Delivered-To: hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07DB31065670; Fri, 20 May 2011 21:57:13 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f11:66f:2::11]) by mx1.freebsd.org (Postfix) with ESMTP id AC9A48FC12; Fri, 20 May 2011 21:57:12 +0000 (UTC) Received: from thor.farley.org (HPooka@thor.farley.org [IPv6:2001:470:1f11:66f:1::5]) by mail.farley.org (8.14.5/8.14.5) with ESMTP id p4KLvA2s097415; Fri, 20 May 2011 17:57:10 -0400 (EDT) (envelope-from scf@FreeBSD.org) Date: Fri, 20 May 2011 17:57:10 -0400 (EDT) From: "Sean C. Farley" To: Julian Elischer In-Reply-To: <4DD6AEB4.3090609@freebsd.org> Message-ID: References: <20110520083248.0e7c249f.wmoran@collaborativefusion.com> <4DD6AEB4.3090609@freebsd.org> User-Agent: Alpine 2.02 (BSF 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-1.3 required=4.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.farley.org Cc: hackers@FreeBSD.org Subject: Re: who is in swap? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 21:57:13 -0000 On Fri, 20 May 2011, Julian Elischer wrote: > On 5/20/11 5:32 AM, Bill Moran wrote: >> In response to Daniel Braniss: >> > no, Who's on 3rd No. I Don't Know is on 3rd. Who's on 1st. Sean -- scf@FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 22:30:40 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 930CC106566B for ; Fri, 20 May 2011 22:30:40 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 4CB128FC0C for ; Fri, 20 May 2011 22:30:40 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p4KMUbq7024690 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 20 May 2011 15:30:39 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DD6EB8A.2000805@freebsd.org> Date: Fri, 20 May 2011 15:30:34 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: "Sean C. Farley" References: <20110520083248.0e7c249f.wmoran@collaborativefusion.com> <4DD6AEB4.3090609@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: who is in swap? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 22:30:40 -0000 On 5/20/11 2:57 PM, Sean C. Farley wrote: > On Fri, 20 May 2011, Julian Elischer wrote: > >> On 5/20/11 5:32 AM, Bill Moran wrote: >>> In response to Daniel Braniss: >>> >> no, Who's on 3rd > > No. I Don't Know is on 3rd. Who's on 1st. I don't KNOW who's on 1st! > > Sean From owner-freebsd-hackers@FreeBSD.ORG Fri May 20 23:34:07 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E76E5106566B; Fri, 20 May 2011 23:34:07 +0000 (UTC) (envelope-from damjan.marion@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3F5978FC0C; Fri, 20 May 2011 23:34:06 +0000 (UTC) Received: by bwz12 with SMTP id 12so4742544bwz.13 for ; Fri, 20 May 2011 16:34:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=dGtb197qGGIaKQASPQvaomsCXgzlCjzIJEot0yg2zdw=; b=QoNHSWRNG7kwSWN0m61kFuireEzkSywMrgx4eqwCQ/5sLd0c1AmtoPhcc5KNqvy2PJ Yw9ywdiuBt73pvQGRvziSH7ZW9BeA+ASd4QOojZmhhERXlfmUo2qcLzazNmAMYzSPMVr hfON7U0g5eVm2mQODjET/zV7eCjc27jL2GvvI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=X8ebut4Et2SZUQPfwIUw40UE+4wVd3rpj4KMRfmKFS9httJgf7eRMyY/lB+fOvQZQM qrnqk/V1keTRg434KxW/HYx0CKQylgtOEwa/UxXLae7ybegiSihDqv4iz8PdKSSgaUM7 FaIgVr5cdDQPxfWXVQeLazs4AGDpkXcWM7myA= Received: by 10.204.80.223 with SMTP id u31mr139642bkk.121.1305934445917; Fri, 20 May 2011 16:34:05 -0700 (PDT) Received: from [192.168.123.4] (cpe-109-60-66-194.zg3.cable.xnet.hr [109.60.66.194]) by mx.google.com with ESMTPS id q24sm2423690bks.21.2011.05.20.16.34.04 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 20 May 2011 16:34:04 -0700 (PDT) From: Damjan Marion Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 21 May 2011 01:34:02 +0200 Message-Id: To: freebsd-arm@freebsd.org, freebsd-hackers@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Cc: Subject: vm_fault when accessing PCI address space X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 23:34:08 -0000 Hi, I'm made some progress on porting existing marvell orion ARM code=20 to work on 88F5181L SoC which have embedded PCI controller. PCI driver detects resources and recognizes Atheros wlan card,=20 however when driver tries to access 1st register with bus_space_write_4 vm_fault happens: vm_fault(0xc0e4f000, e8007000, 2, 0) -> 1 Fatal kernel mode data abort: 'Translation Fault (S)' trapframe: 0xc0d3faa4 FSR=3D00000005, FAR=3De800704c, spsr=3D600000d3 r0 =3D00000000, r1 =3De8000000, r2 =3D0000704c, r3 =3D00000003 r4 =3Dc13cd000, r5 =3Dc0c4bd60, r6 =3Dc0bece04, r7 =3Dc12dd000 r8 =3D00000023, r9 =3Dc0d074c8, r10=3Dc0d3fba4, r11=3Dc0d3fb00 r12=3D00000000, ssp=3Dc0d3faf0, slr=3Dc095f830, pc =3Dc0bece04 [ thread pid 0 tid 100000 ] Stopped at generic_bs_w_4: str r3, [r1, r2] 0xe8000000 is PCI mem space. I can see that PCI driver (mv_pci.c) = allocates this resource: pcib0: mem = 0xf1030000-0xf1031fff irq 0 on fdtbus0 pci0: on pcib0 mv_pcib_alloc_resource: start=3D0xe8000000 end=3D0xe800ffff = count=3D0x00010000 flags=3D0x00 What can be the reason for this vm_fault?=20 Thanks for any hint or idea, Damjan From owner-freebsd-hackers@FreeBSD.ORG Sat May 21 06:29:54 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 975FB1065672 for ; Sat, 21 May 2011 06:29:54 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by mx1.freebsd.org (Postfix) with ESMTP id 43FBD8FC19 for ; Sat, 21 May 2011 06:29:53 +0000 (UTC) X-AuditID: 12074425-b7b78ae000007e02-b8-4dd7585d4d7c Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id C7.CC.32258.D5857DD4; Sat, 21 May 2011 02:14:53 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id p4L6Ep6d021134 for ; Sat, 21 May 2011 02:14:51 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p4L6EmKP026725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 21 May 2011 02:14:51 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id p4L6ElRq027871; Sat, 21 May 2011 02:14:47 -0400 (EDT) Date: Sat, 21 May 2011 02:14:47 -0400 (EDT) From: Benjamin Kaduk To: freebsd-hackers@freebsd.org Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-2023889498-1305958487=:6818" X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLKsWRmVeSWpSXmKPExsUixG6nrhsbcd3X4MwxFYvtm/8xOjB6zPg0 nyWAMYrLJiU1J7MstUjfLoEro3/7GraC7REV5w6FNDA+Cupi5OSQEDCRmDH5PDOELSZx4d56 NhBbSGAfo8TF9+FdjFxA9iVGiU+HfjBCOI+YJK6/3sAG4TQwSvTPuscC0sIioC3x/FwD2Cg2 ARWJmW82AhVxcIgIyEssOG8PEhYWsJBYvm4lWDmvgIPE/VtTmUBsUQEdidX7p0DFBSVOznwC ZjMLBEg0Nq1jncDINwtJahaSFIRtKfFv7S84e9LD30wQtqLE5gO7oeIOEtf72hghbFGJFTfm QNlGEmceLYSaaSZx9/tXFmx6fx5rYMfUayyxeO8p1gWMvKsYZVNyq3RzEzNzilOTdYuTE/Py Uot0LfRyM0v0UlNKNzGCY8pFdQfjhENKhxgFOBiVeHh/Nl7zFWJNLCuuzD3EKMnBpCTKezT8 uq8QX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd51wUA53pTEyqrUonyYlDQHi5I473xJdV8hgfTE ktTs1NSC1CKYrAwHh5IEbxPIUMGi1PTUirTMnBKENBMHJ8hwHqDhS0FqeIsLEnOLM9Mh8qcY dTmWXf59gFGIJS8/L1VKnHcbSJEASFFGaR7cHFgqfMUoDvSWMO8ukCoeYBqFm/QKaAkT0JKP eddAlpQkIqSkGhgNrklousyw9oq9Onv+7dvu72WviRxt4NtrKsi6+VzwxQrHz57WO5dv47ix qcVFbllJy4vvhVrnvvOZ10j6VitftHvs/3B63Lk5gas3fqpgVbw9d9amxY3aM31NI/7EXjB0 fOb/9Fze8dsB85UEvpS4dBT5Llvy1GHxxwuhOq+yr1dGeX19bhqqxFKckWioxVxUnAgAifKw F2ADAAA= Subject: porting third-party build system to bsd.kmod.mk X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2011 06:29:54 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-2023889498-1305958487=:6818 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII After getting a few pointers from jhb at BSDCan on what a bsd.kmod.mk-using Makefile should look like, I have been trying my hand at porting the OpenAFS kernel module build system to use it. (The main thing this gets us is not having to manually track version- and architecture-dependent CFLAGS and the like.) However, the path is not exactly smooth. A lot of the difficulty is in getting an autogenerated vnode_if.h while using a list of files to include in the module(from the common OpenAFS code) that's given as a list of object files. If there's already a vnode_if.h sitting around, I can just use OBJS and things progress quite nicely; however, if I have to get back to SRCS for the use of sys/conf/kmod.mk's vnode_if.h logic, I get this sort of build failure (full log attached) with the attached Makefile: gcc -I. -I.. -I../nfs [more includes and defines] -I/usr/devel/openafs/git/openafs/include/afs -I@/sys -Imachine -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wno-redundant-decls -Wsystem-headers -Werror -Wno-pointer-sign -o osi_crypto.o -c /usr/devel/openafs/git/openafs/src/afs/FBSD/osi_crypto.c /usr/devel/openafs/git/openafs/src/libafs/MODLOAD/../../afs/FBSD/osi_crypto.c vnode_if.h gcc: cannot specify -o with -c or -S with multiple files That last bit, "-o osi_crypto.o -c /path/to/osi_crypto.c /path/to/osi_crypto.c vnode_if.h" is quite troublesome. Any thoughts on what is causing those extra files to be listed would be greatly appreciated. (Comments on other issues in the Makefile are welcome, too -- it's still in pretty rough shape.) I should note that though Makefile.common does define a osi_crypto.o target, "make -d A" reports: using existing source /usr/devel/openafs/git/openafs/src/afs/FBSD/osi_crypto.c applying .c -> .o to "osi_crypto.o" Thanks, Ben Kaduk ---559023410-2023889498-1305958487=:6818 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=Makefile Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=Makefile IyBDb3B5cmlnaHQgMjAwMCwgSW50ZXJuYXRpb25hbCBCdXNpbmVzcyBNYWNo aW5lcyBDb3Jwb3JhdGlvbiBhbmQgb3RoZXJzLg0KIyBBbGwgUmlnaHRzIFJl c2VydmVkLg0KIw0KIyBUaGlzIHNvZnR3YXJlIGhhcyBiZWVuIHJlbGVhc2Vk IHVuZGVyIHRoZSB0ZXJtcyBvZiB0aGUgSUJNIFB1YmxpYw0KIyBMaWNlbnNl LiAgRm9yIGRldGFpbHMsIHNlZSB0aGUgTElDRU5TRSBmaWxlIGluIHRoZSB0 b3AtbGV2ZWwgc291cmNlDQojIGRpcmVjdG9yeSBvciBvbmxpbmUgYXQgaHR0 cDovL3d3dy5vcGVuYWZzLm9yZy9kbC9saWNlbnNlMTAuaHRtbA0KIw0Kc3Jj ZGlyPS4NCmluY2x1ZGUgL3Vzci9kZXZlbC9vcGVuYWZzL2dpdC9vcGVuYWZz L3NyYy9jb25maWcvTWFrZWZpbGUuY29uZmlnDQojIHdlIHVuc2V0IHRoZXNl IHRvIHdvcmsgYXJvdW5kIGZsYWdzIHdlIGRvbid0IHdhbnQNCiMgWENGTEFH UyBzZXRzIC1mUElDLCB3aGljaCBpcyBmb3JiaWRkZW4gZm9yIG1jbW9kZWw9 a2VybmVsDQpYQ0ZMQUdTPQ0KQ09NTU9OX0NGTEFHUz0NCiMgWFhYIG5vdCBz dXJlIGlmIHRoZXNlIG5lZWQgdG8gYmUgKHJlKWRlZmluZWQgaGVyZQ0KSU5T VEFMTCA9IC91c3IvYmluL2luc3RhbGwgLWMNCklOU1RBTExfREFUQSA9ICR7 SU5TVEFMTH0gLW0gNjQ0DQpJTlNUQUxMX1BST0dSQU0gPSAke0lOU1RBTEx9 IA0KSU5TVEFMTF9TQ1JJUFQgPSAke0lOU1RBTEx9DQoNCiMgU3lzdGVtIHNw ZWNpZmljIGJ1aWxkIGNvbW1hbmRzIGFuZCBmbGFncw0KS1NSQyA9IC91c3Iv c3JjL3N5cw0KS0JMRCA9IC91c3Ivb2JqL3Vzci9zcmMvc3lzL0dFTkVSSUMN Cg0KIyBXZSBzdWNrDQpXQVJOUz0gMQ0KIyBzZXR0aW5nIFdBUk5TPTAgZGlk IG5vdCBoZWxwIHdpdGggdGhpcz8hDQpDV0FSTkZMQUdTKz0gLVduby1yZWR1 bmRhbnQtZGVjbHMNCg0KIyBzZXR1cCBmb3IgYnNkLmttb2QubWsgaW5mcmFz dHJ1Y3R1cmUNCi5QQVRIOgkkey5DVVJESVJ9Ly4uLy4uL2FmcyBcDQoJJHsu Q1VSRElSfS8uLi8uLi9hZnMvRkJTRCBcDQoJJHsuQ1VSRElSfS8uLi8uLi9h ZnMvVk5PUFMNCktNT0RESVI9L2Jvb3QvbW9kdWxlcw0KS01PRD0JbGliYWZz DQpTWVNESVI9ICR7S1NSQ30NCiMgTmFtZSBvZiBkaXJlY3RvcnkgdG8gaG9s ZCBvYmplY3QgZmlsZXMgYW5kIGxpYnJhcmllcy4NCktPQkogPSBNT0RMT0FE DQoNCiMgVGhpcyB0ZWxscyBNYWtlZmlsZS5jb21tb24gdG8gdXNlIGl0J3Mg c2luZ2xlIGRpcmVjdG9yeSBidWlsZCB0YXJnZXQuDQpDT01QRElSUyA9IHNp bmdsZV9jb21wZGlyDQpJTlNURElSUyA9IHNpbmdsZV9pbnN0ZGlyDQpERVNU RElSUyA9IHNpbmdsZV9kZXN0ZGlyDQoNCiMgVmVyeSB1Z2x5LiAgQnV0IG1h bnkgb2YgdGhlc2UgbGlua3MgYXJlIG5lZWRlZCBmb3IgY29tbW9uIGNvZGUg dG8gd29yay4NCnNldHVwOg0KCS1ta2RpciAkKEtPQkopDQoJLSQoUk0pICQo S09CSikvTWFrZWZpbGUgJChLT0JKKS9NYWtlZmlsZS5jb21tb24NCglsbiAt ZnMgLi4vTWFrZWZpbGUgJChLT0JKKS9NYWtlZmlsZQ0KCWxuIC1mcyAuLi9N YWtlZmlsZS5jb21tb24gJChLT0JKKS9NYWtlZmlsZS5jb21tb24NCgktJChS TSkgLWYgIGggcnBjIHVmcyBtYWNoaW5lDQoJLWxuIC1mcyAke0tTUkN9L2Ft ZDY0L2luY2x1ZGUgbWFjaGluZQ0KCS1sbiAtZnMgJHtLU1JDfS91ZnMvdWZz IHVmcw0KCS1sbiAtZnMgJHtLU1JDfS9ycGMgcnBjDQoJLWxuIC1mcyAke0tT UkN9L3N5cyBoDQoNCiMgTWFrZWZpbGUuY29tbW9uIHNldHMgQUZTQU9CSlMs IENPTU1PTl9JTkNMVURFLCBUT1Bfe1NSQyxPQkp9KiwgYW5kIHRoZSBsaWtl Lg0KIyBXZSBtdXN0IGxpdmUgd2l0aCBpdHMgb3RoZXIgcG9sbHV0aW9uIG9m IHRhcmdldHMgYW5kIGJ1aWxkIHJ1bGVzLg0KaW5jbHVkZSBNYWtlZmlsZS5j b21tb24NCg0KIyBUaGlzIGlzIHF1aXRlIGF3a3dhcmQuICBUaGUgY29kZSBp biBrbW9kLm1rIGNoZWNrcyBmb3Igdm5vZGVfaWYuaCBpbg0KIyBTUkNTLCBi dXQgSSBhbSBnaXZlbiBhIGxpc3Qgb2Ygb2JqZWN0IGZpbGVzIGZyb20gdGhl IGNvbW1vbiBjb2RlLg0KIyBSZXNvcnQgdG8gdmFyaWFibGUgc3Vic3RpdHV0 aW9uIGJsYWNrIG1hZ2ljLCBiZWxvdy4NClNSQ1MgPSB2bm9kZV9pZi5oDQoN CiMgT1Mgc3BlY2lmaWMgb2JqZWN0IGZpbGVzOg0KQUZTX09TX09CSlMgPSBv c2lfY3J5cHRvLm8gXA0KCW9zaV9nY3BhZ3MubyBcDQoJb3NpX2dyb3Vwcy5v IFwNCglvc2lfZmlsZS5vIFwNCglvc2lfaW5vZGUubyBcDQoJb3NpX21pc2Mu byBcDQoJb3NpX3NsZWVwLm8gXA0KCW9zaV92Y2FjaGUubyBcDQoJb3NpX3Zt Lm8gXA0KCW9zaV92bm9kZW9wcy5vIFwNCglvc2lfbW9kdWxlLm8gDQoNCkFG U19PU19OT05GU09CSlMgPSBcDQoJb3NpX3Zmc29wcy5vDQoNClNSQ1MrPQkk e0FGU19PU19PQkpTOlMvLm8kLy5jL2d9ICR7QUZTX09TX05PTkZTT0JKUzpT Ly5vJC8uYy9nfSBcDQoJJHtBRlNBT0JKUzpTLy5vJC8uYy9nfQ0KDQpERUZJ TkVTPSAtREFGU0RFQlVHIC1ES0VSTkVMIC1EQUZTIC1EVklDRSAtRE5GUyAt RFVGUyAtRElORVQgLURRVU9UQSAtREdFVE1PVU5UDQpDRkxBR1MrPSAkKERF RklORVMpICR7Q09NTU9OX0lOQ0xVREV9IC1JQC9zeXMgLUltYWNoaW5lDQoN CklOU1RfTElCQUZTID0gJHtERVNURElSfSR7YWZza2VybmVsZGlyfS8ke0xJ QkFGU30NCklOU1RfTElCQUZTTk9ORlMgPSAke0RFU1RESVJ9JHthZnNrZXJu ZWxkaXJ9LyR7TElCQUZTTk9ORlN9DQoNCkRFU1RfTElCQUZTID0gJHtERVNU fS9yb290LmNsaWVudC9iaW4vJHtMSUJBRlN9DQpERVNUX0xJQkFGU05PTkZT ID0gJHtERVNUfS9yb290LmNsaWVudC9iaW4vJHtMSUJBRlNOT05GU30NCg0K aW5zdGFsbF9saWJhZnM6CWluc3RhbGwNCg0KZGVzdF9saWJhZnM6ICQoTElC QUZTTk9ORlMpDQoJJHtJTlNUQUxMfSAtZCAke0RFU1R9L3Jvb3QuY2xpZW50 L2Jpbg0KCSR7SU5TVEFMTH0gLW0gNjQ0ICQoTElCQUZTTk9ORlMpICQoREVT VF9MSUJBRlNOT05GUykNCg0KIyBUaGlzIGlzIHVnbHksIGJ1dCB0aGUgY29t bW9uIGluZnJhc3RydWN0dXJlIG5lZWRzIGEgbGliYWZzIHRhcmdldC4NCmxp YmFmczogbGliYWZzLmtvDQoNCi5pbmNsdWRlIDxic2Qua21vZC5taz4NCg== ---559023410-2023889498-1305958487=:6818 Content-Type: APPLICATION/octet-stream; name=build.log Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=build.log bWtkaXIgTU9ETE9BRApta2RpcjogTU9ETE9BRDogRmlsZSBleGlzdHMKKioq IEVycm9yIGNvZGUgMSAoaWdub3JlZCkKcm0gTU9ETE9BRC9NYWtlZmlsZSBN T0RMT0FEL01ha2VmaWxlLmNvbW1vbgpsbiAtZnMgLi4vTWFrZWZpbGUgTU9E TE9BRC9NYWtlZmlsZQpsbiAtZnMgLi4vTWFrZWZpbGUuY29tbW9uIE1PRExP QUQvTWFrZWZpbGUuY29tbW9uCnJtIC1mICBoIHJwYyB1ZnMgbWFjaGluZQps biAtZnMgL3Vzci9zcmMvc3lzL2FtZDY0L2luY2x1ZGUgbWFjaGluZQpsbiAt ZnMgL3Vzci9zcmMvc3lzL3Vmcy91ZnMgdWZzCmxuIC1mcyAvdXNyL3NyYy9z eXMvcnBjIHJwYwpsbiAtZnMgL3Vzci9zcmMvc3lzL3N5cyBoCmNkIE1PRExP QUQgOyAgZWNobyBtYWtlIERFU1RESVI9IHNpbmdsZV9jb21wZGlyX2xpYmFm czsgIG1ha2UgREVTVERJUj0gIHNpbmdsZV9jb21wZGlyX2xpYmFmcwptYWtl IERFU1RESVI9IHNpbmdsZV9jb21wZGlyX2xpYmFmcwpnY2MgLUkuIC1JLi4g LUkuLi9uZnMgIC1JL3Vzci9kZXZlbC9vcGVuYWZzL2dpdC9vcGVuYWZzL3Ny Yy9jcnlwdG8vaGNyeXB0by9rZXJuZWwgIC1JL3Vzci9kZXZlbC9vcGVuYWZz L2dpdC9vcGVuYWZzL3NyYyAgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0L29w ZW5hZnMvc3JjL2FmcyAgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0L29wZW5h ZnMvc3JjL2Fmcy9GQlNEICAtSS91c3IvZGV2ZWwvb3BlbmFmcy9naXQvb3Bl bmFmcy9zcmMvY29uZmlnICAtSS91c3IvZGV2ZWwvb3BlbmFmcy9naXQvb3Bl bmFmcy9zcmMvcngvRkJTRCAgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0L29w ZW5hZnMvc3JjL2V4dGVybmFsL2hlaW1kYWwgIC1JL3Vzci9kZXZlbC9vcGVu YWZzL2dpdC9vcGVuYWZzL3NyYyAgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0 L29wZW5hZnMvc3JjL2FmcyAgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0L29w ZW5hZnMvc3JjL2Fmcy9GQlNEICAtSS91c3IvZGV2ZWwvb3BlbmFmcy9naXQv b3BlbmFmcy9zcmMvY29uZmlnICAtSS91c3IvZGV2ZWwvb3BlbmFmcy9naXQv b3BlbmFmcy9zcmMvZnNpbnQgIC1JL3Vzci9kZXZlbC9vcGVuYWZzL2dpdC9v cGVuYWZzL3NyYy92bHNlcnZlciAgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0 L29wZW5hZnMvc3JjL2F1dGggIC1JL3Vzci9kZXZlbC9vcGVuYWZzL2dpdC9v cGVuYWZzL2luY2x1ZGUgIC1JL3Vzci9kZXZlbC9vcGVuYWZzL2dpdC9vcGVu YWZzL2luY2x1ZGUvYWZzIC1nIC1PIC1EQUZTREVCVUcgLURLRVJORUwgLURB RlMgLURWSUNFIC1ETkZTIC1EVUZTIC1ESU5FVCAtRFFVT1RBIC1ER0VUTU9V TlQgLVdlcnJvciAtRF9LRVJORUwgLURLTERfTU9EVUxFIC1ub3N0ZGluYyAg LUkuIC1JLi4gLUkuLi9uZnMgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0L29w ZW5hZnMvc3JjL2NyeXB0by9oY3J5cHRvL2tlcm5lbCAtSS91c3IvZGV2ZWwv b3BlbmFmcy9naXQvb3BlbmFmcy9zcmMgLUkvdXNyL2RldmVsL29wZW5hZnMv Z2l0L29wZW5hZnMvc3JjL2FmcyAtSS91c3IvZGV2ZWwvb3BlbmFmcy9naXQv b3BlbmFmcy9zcmMvYWZzL0ZCU0QgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0 L29wZW5hZnMvc3JjL2NvbmZpZyAtSS91c3IvZGV2ZWwvb3BlbmFmcy9naXQv b3BlbmFmcy9zcmMvcngvRkJTRCAtSS91c3IvZGV2ZWwvb3BlbmFmcy9naXQv b3BlbmFmcy9zcmMvZXh0ZXJuYWwvaGVpbWRhbCAtSS91c3IvZGV2ZWwvb3Bl bmFmcy9naXQvb3BlbmFmcy9zcmMgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0 L29wZW5hZnMvc3JjL2FmcyAtSS91c3IvZGV2ZWwvb3BlbmFmcy9naXQvb3Bl bmFmcy9zcmMvYWZzL0ZCU0QgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0L29w ZW5hZnMvc3JjL2NvbmZpZyAtSS91c3IvZGV2ZWwvb3BlbmFmcy9naXQvb3Bl bmFmcy9zcmMvZnNpbnQgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0L29wZW5h ZnMvc3JjL3Zsc2VydmVyIC1JL3Vzci9kZXZlbC9vcGVuYWZzL2dpdC9vcGVu YWZzL3NyYy9hdXRoIC1JL3Vzci9kZXZlbC9vcGVuYWZzL2dpdC9vcGVuYWZz L2luY2x1ZGUgLUkvdXNyL2RldmVsL29wZW5hZnMvZ2l0L29wZW5hZnMvaW5j bHVkZS9hZnMgLUlAL3N5cyAtSW1hY2hpbmUgLUkuIC1JQCAtSUAvY29udHJp Yi9hbHRxIC1maW5saW5lLWxpbWl0PTgwMDAgLS1wYXJhbSBpbmxpbmUtdW5p dC1ncm93dGg9MTAwIC0tcGFyYW0gbGFyZ2UtZnVuY3Rpb24tZ3Jvd3RoPTEw MDAgLWZuby1jb21tb24gIC1mbm8tb21pdC1mcmFtZS1wb2ludGVyICAtbWNt b2RlbD1rZXJuZWwgLW1uby1yZWQtem9uZSAgLW1mcG1hdGg9Mzg3IC1tbm8t bW14IC1tbm8tM2Rub3cgLW1uby1zc2UgLW1uby1zc2UyIC1tbm8tc3NlMyAg LW1zb2Z0LWZsb2F0IC1mbm8tYXN5bmNocm9ub3VzLXVud2luZC10YWJsZXMg LWZmcmVlc3RhbmRpbmcgLWZzdGFjay1wcm90ZWN0b3IgLXN0ZD1pc285ODk5 OjE5OTkgLWZzdGFjay1wcm90ZWN0b3IgLVduby1yZWR1bmRhbnQtZGVjbHMg LVdzeXN0ZW0taGVhZGVycyAtV2Vycm9yIC1Xbm8tcG9pbnRlci1zaWduICAt byBvc2lfY3J5cHRvLm8gLWMgL3Vzci9kZXZlbC9vcGVuYWZzL2dpdC9vcGVu YWZzL3NyYy9hZnMvRkJTRC9vc2lfY3J5cHRvLmMgL3Vzci9kZXZlbC9vcGVu YWZzL2dpdC9vcGVuYWZzL3NyYy9saWJhZnMvTU9ETE9BRC8uLi8uLi9hZnMv RkJTRC9vc2lfY3J5cHRvLmMgdm5vZGVfaWYuaApnY2M6IGNhbm5vdCBzcGVj aWZ5IC1vIHdpdGggLWMgb3IgLVMgd2l0aCBtdWx0aXBsZSBmaWxlcwoqKiog RXJyb3IgY29kZSAxCgpTdG9wIGluIC91c3IvZGV2ZWwvb3BlbmFmcy9naXQv b3BlbmFmcy9zcmMvbGliYWZzL01PRExPQUQuCioqKiBFcnJvciBjb2RlIDEK ClN0b3AgaW4gL3Vzci9kZXZlbC9vcGVuYWZzL2dpdC9vcGVuYWZzL3NyYy9s aWJhZnMuCg== ---559023410-2023889498-1305958487=:6818-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 21 07:30:31 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D19A1065672 for ; Sat, 21 May 2011 07:30:31 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.freebsd.org (Postfix) with ESMTP id D617C8FC15 for ; Sat, 21 May 2011 07:30:30 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 1QNgdn-000FXV-Sq; Sat, 21 May 2011 10:30:27 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Julian Elischer In-reply-to: <4DD6AEB4.3090609@freebsd.org> References: <20110520083248.0e7c249f.wmoran@collaborativefusion.com> <4DD6AEB4.3090609@freebsd.org> Comments: In-reply-to Julian Elischer message dated "Fri, 20 May 2011 11:11:00 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 May 2011 10:30:27 +0300 From: Daniel Braniss Message-ID: Cc: hackers@freebsd.org, Bill Moran Subject: Re: who is in swap? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2011 07:30:31 -0000 > On 5/20/11 5:32 AM, Bill Moran wrote: > > In response to Daniel Braniss: > > > no, Who's on 3rd > what's on 2nd! btw, there was something similar using unix commands ... From owner-freebsd-hackers@FreeBSD.ORG Sat May 21 09:20:28 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E2BF106564A for ; Sat, 21 May 2011 09:20:28 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9D0FD8FC0A for ; Sat, 21 May 2011 09:20:27 +0000 (UTC) Received: by fxm11 with SMTP id 11so4303843fxm.13 for ; Sat, 21 May 2011 02:20:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:date:from:to:subject:message-id:in-reply-to :references:reply-to:x-mailer:mime-version:content-type :content-transfer-encoding; bh=cRUnBFVAkN7ENTfRBkHMHhm2vBpvanFuGfb5haO7bJE=; b=urkucmln4DQEzZHbddDyI0DAi3RgmrRt9N6Wf73w9YlrCIcwkP+YB6n2N9fD3YIdWT GwZ2qHUyiMXu49r6Gq7HveRMzNiV/E4kV6nOZy5caz2n3v7J6EtuUFgAM8px9ToajX9N njw4L/EiuGtTjmlBh3VmhuddkYbhu5QIRVqTI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=uHDguYmm+XdhZ9BAV7akAKR/yUTok29efhMLXJ9H3U6xl70tdffExnv4avXVKFbIT6 9aqIh5iyMpxFbJoZbTCqGbYbpAnfF7SkfTlJuJk9QgwgOS+G3R1++VR6zdutmwxC0SoX OGdtp9W9EDnllki8wxFqwPzRhBsHjX0ok64Sk= Received: by 10.223.97.142 with SMTP id l14mr449617fan.137.1305969626411; Sat, 21 May 2011 02:20:26 -0700 (PDT) Received: from ernst.jennejohn.org (p578E218D.dip.t-dialin.net [87.142.33.141]) by mx.google.com with ESMTPS id c24sm1675740fak.7.2011.05.21.02.20.24 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 21 May 2011 02:20:25 -0700 (PDT) Date: Sat, 21 May 2011 11:20:23 +0200 From: Gary Jennejohn To: freebsd-hackers@freebsd.org Message-ID: <20110521112023.17e42a69@ernst.jennejohn.org> In-Reply-To: <4DD6EB8A.2000805@freebsd.org> References: <20110520083248.0e7c249f.wmoran@collaborativefusion.com> <4DD6AEB4.3090609@freebsd.org> <4DD6EB8A.2000805@freebsd.org> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: who is in swap? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2011 09:20:28 -0000 On Fri, 20 May 2011 15:30:34 -0700 Julian Elischer wrote: > On 5/20/11 2:57 PM, Sean C. Farley wrote: > > On Fri, 20 May 2011, Julian Elischer wrote: > > > >> On 5/20/11 5:32 AM, Bill Moran wrote: > >>> In response to Daniel Braniss: > >>> > >> no, Who's on 3rd > > > > No. I Don't Know is on 3rd. Who's on 1st. > I don't KNOW who's on 1st! > Natcherly -- Gary Jennejohn