From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 5 01:29:26 2012 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 86C36106566C for ; Sun, 5 Aug 2012 01:29:26 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 5F4298FC08 for ; Sun, 5 Aug 2012 01:29:25 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q751TMu0071284; Sun, 5 Aug 2012 01:29:22 GMT (envelope-from kientzle@freebsd.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id ge9h2mrabv4zubekr4yds9h5qn; Sun, 05 Aug 2012 01:29:22 +0000 (UTC) (envelope-from kientzle@freebsd.org) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=windows-1251 From: Tim Kientzle In-Reply-To: <1344109912.1128.94.camel@revolution.hippie.lan> Date: Sat, 4 Aug 2012 18:29:20 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1344109912.1128.94.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1278) Cc: freebsd-hackers Subject: Re: How to Expose Chip-level Ethernet Statistics? 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: Sun, 05 Aug 2012 01:29:26 -0000 On Aug 4, 2012, at 12:51 PM, Ian Lepore wrote: > On Sat, 2012-08-04 at 12:21 -0700, Tim Kientzle wrote: >> I believe that some of the issues I'm having with this >> Ethernet driver might be easier to diagnose if I could >> expose the chip-level statistics counters (especially queue >> overrun counts). >>=20 >> Is there a standard way to do this? >>=20 >=20 > I don't know if this is exactly what you mean, but have a look at > src/tools/tools/ifinfo, and find some examples of drivers that fill in > that info by grepping for ifmib_iso_8802_3. >=20 > (I really know nothing about this stuff, except that your request > triggered a memory that the atmel if_ate driver gathers some stats = that > I've not seen in most other drivers.) Thanks, Ian! That's almost exactly what I'm looking for. Only tricky point: I don't immediately see where the standard MIB allows me to run a function when the sysctl query runs (which will be necessary if I want to expose the on-chip counters). That might lead me to use a separate sysctl tree for this. I'll also take at the atmel if_ate driver=85. Tim From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 5 14:36:34 2012 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 29B31106564A for ; Sun, 5 Aug 2012 14:36:34 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id 5EFB28FC0A for ; Sun, 5 Aug 2012 14:36:32 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q75EaUCH022351 for ; Sun, 5 Aug 2012 16:36:30 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id q75EaUDN022348 for ; Sun, 5 Aug 2012 16:36:30 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sun, 5 Aug 2012 16:36:30 +0200 (CEST) From: Wojciech Puchar To: freebsd-hackers@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Sun, 05 Aug 2012 16:36:30 +0200 (CEST) Subject: SMALL FreeBSD capable board 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: Sun, 05 Aug 2012 14:36:34 -0000 i am looking for SMALL and specifically low power board that can run from battery, can run FreeBSD and have at least one ethernet and one USB port, and reasonable amount of memory (32MB at least). WiFi not needed. some more than few MB flash is, as well as about 10 GPIO ports or useful SPI port. I already see a lot of useful supported ones in source tree, with ARM and MIPS. I want to make portable router PLUS my own add own hardware, and have full control over software running on it. Any recommendation. Ethernut 5 seems great http://www.ethernut.de/en/hardware/enut5/index.html but no info about price and availability in Poland From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 5 14:40:28 2012 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 186741065673 for ; Sun, 5 Aug 2012 14:40:28 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id C853C8FC25 for ; Sun, 5 Aug 2012 14:40:27 +0000 (UTC) Received: by yenl8 with SMTP id l8so2266283yen.13 for ; Sun, 05 Aug 2012 07:40:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=viirEkjGcS8poBDlqbHNWNPUDE0rCU8DAY8m7v1mXeQ=; b=STS/wcGAK9UYy7lpFyWNaNpu9fDcgjo2KKy7AyW6uZm2/hqICKFTg31ndFoa8iEmnd yTPWH5BCYDxuLRsfDC2oEutJth21PPttTgmM1aqXRGlQ+13yDmEQylwPG+0/1Sb1jkx3 aMeSwoYr8NCXCAYUzD4D+oWVI4x7nihbAT00JcG8l14TuOouNgbU8s5c0XyO3s0yRitH QUAtyn3x795+1j0g2+nV1OIhTnUmGy8/ty27Z/V7Wi45/rDNex3UYAind9bLj47d/6aS yP96AfDv1D47Vp5fB6gvuGfwK5iWp4WqOC7cb0AdHWx6rz3HzEeKhjXK6NKZRWCfuK4B ZmuQ== MIME-Version: 1.0 Received: by 10.50.140.106 with SMTP id rf10mr3181608igb.41.1344177626302; Sun, 05 Aug 2012 07:40:26 -0700 (PDT) Received: by 10.64.27.163 with HTTP; Sun, 5 Aug 2012 07:40:26 -0700 (PDT) In-Reply-To: References: Date: Sun, 5 Aug 2012 10:40:26 -0400 Message-ID: From: Outback Dingo To: Wojciech Puchar Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: SMALL FreeBSD capable board 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: Sun, 05 Aug 2012 14:40:28 -0000 if you can still find one a Ubiquiti RouterStation / RouterStation Pro works wonders and has full FreeBSD support On Sun, Aug 5, 2012 at 10:36 AM, Wojciech Puchar wrote: > i am looking for SMALL and specifically low power board that can run from > battery, can run FreeBSD and have at least one ethernet and one USB port, > and reasonable amount of memory (32MB at least). > WiFi not needed. some more than few MB flash is, as well as about 10 GPIO > ports or useful SPI port. > > I already see a lot of useful supported ones in source tree, with ARM and > MIPS. > > I want to make portable router PLUS my own add own hardware, and have full > control over software running on it. > > Any recommendation. > > Ethernut 5 seems great > http://www.ethernut.de/en/hardware/enut5/index.html > > but no info about price and availability in Poland > _______________________________________________ > 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 Sun Aug 5 15:14:11 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F1CC0106566C for ; Sun, 5 Aug 2012 15:14:10 +0000 (UTC) (envelope-from jamebus@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 743708FC08 for ; Sun, 5 Aug 2012 15:14:10 +0000 (UTC) Received: by lbbgk8 with SMTP id gk8so358328lbb.13 for ; Sun, 05 Aug 2012 08:14:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=5THO8HnL++9Lrx0IlAiU/bvomIj4isyM5AH8SuaPmtM=; b=BqGQV7BgEfXjToggR1DQ8lYfTwZTCuwdbmy0BcRn5wyZqRIMJL2rCxFhHf8v45lkCY NARea9VQfItqoI9KDetaVENCb9PnIxjpsbfJGeZvOW+raDW72VazuH/lKmPFSLBXIGxu lAyPyPDFg2UAAkX3MP6hlXjLbo7yezdXYE8qG4u6d5o6Aa77+BRaLTg3voypdUvSHqiJ u4rsl0Fpbw1WwQZqzLaw4SAGJuTPDDYzi5AYgV2vquj2CHxzZO+XJt1wngTC9Whllz9x 12XTH9fMWqY+XGCCX3t5WJj/DBiImd8hkeC2f+dyDwVmTKK0WFiGNPksrmEuSNK2VFBc 3GRg== MIME-Version: 1.0 Received: by 10.152.147.33 with SMTP id th1mr7909593lab.9.1344179649044; Sun, 05 Aug 2012 08:14:09 -0700 (PDT) Sender: jamebus@gmail.com Received: by 10.112.78.9 with HTTP; Sun, 5 Aug 2012 08:14:08 -0700 (PDT) In-Reply-To: References: Date: Sun, 5 Aug 2012 10:14:08 -0500 X-Google-Sender-Auth: WjrBV4UdQ2xgeB1DyCk9hzCFBDE Message-ID: From: James To: Wojciech Puchar Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: SMALL FreeBSD capable board 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: Sun, 05 Aug 2012 15:14:11 -0000 On Sun, Aug 5, 2012 at 9:36 AM, Wojciech Puchar wrote: > i am looking for SMALL and specifically low power board that can run > from battery, can run FreeBSD and have at least one ethernet and one > USB port, and reasonable amount of memory (32MB at least). WiFi not > needed. some more than few MB flash is, as well as about 10 GPIO > ports or useful SPI port. Soekris Engineering makes excellent boards. While they are based in the states, they do have a reseller in Europe. I use a bunch at work for various tasks. Very reliable hardware. They use various i386 compatible AMD Geode CPUs. You can give it whatever sized CF card you want or attach a small hard disk. Use a serial console to bootstrap and make sure you configure your FreeBSD system to use serial console. Some also have one or more PCI slots, useful for your GPIO/SPI interfaces. HTH! -- James. From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 5 15:37:11 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 13BE0106564A for ; Sun, 5 Aug 2012 15:37:11 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id 5CB8A8FC08 for ; Sun, 5 Aug 2012 15:37:09 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q75Fb8jm062503; Sun, 5 Aug 2012 17:37:08 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id q75Fb8q8062500; Sun, 5 Aug 2012 17:37:08 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sun, 5 Aug 2012 17:37:08 +0200 (CEST) From: Wojciech Puchar To: James In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Sun, 05 Aug 2012 17:37:08 +0200 (CEST) Cc: freebsd-hackers@freebsd.org Subject: Re: SMALL FreeBSD capable board 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: Sun, 05 Aug 2012 15:37:11 -0000 > Soekris Engineering makes excellent boards. While they are based > in the states, they do have a reseller in Europe. How much power does it use and at what voltage? the lower the better > > I use a bunch at work for various tasks. Very reliable hardware. > They use various i386 compatible AMD Geode CPUs. You can give it i DO NOT need i386 compatible. of course it won't hurt. > whatever sized CF card you want or attach a small hard disk. Use a > serial console to bootstrap and make sure you configure your > FreeBSD system to use serial console. Some also have one or more > PCI slots, useful for your GPIO/SPI interfaces. > > HTH! > found /usr/src/sys/mips/conf/TP-WN1043ND this TP link router is easily available and cheap. no problem to build kernel and userland but are there any guide/text about how to boot FreeBSD on it? From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 5 17:07:39 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA7D11065688 for ; Sun, 5 Aug 2012 17:07:39 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id 109958FC18 for ; Sun, 5 Aug 2012 17:07:38 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q75H7be3095699; Sun, 5 Aug 2012 19:07:37 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id q75H7bSX095689; Sun, 5 Aug 2012 19:07:37 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sun, 5 Aug 2012 19:07:36 +0200 (CEST) From: Wojciech Puchar To: Outback Dingo In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Sun, 05 Aug 2012 19:07:37 +0200 (CEST) Cc: freebsd-hackers@freebsd.org Subject: Re: SMALL FreeBSD capable board 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: Sun, 05 Aug 2012 17:07:39 -0000 thanks for answer. TP-Link TL-WR1043ND seems to be best choice for me. From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 5 17:29:53 2012 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 13ED8106571A for ; Sun, 5 Aug 2012 17:29:53 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 8826B8FC18 for ; Sun, 5 Aug 2012 17:29:52 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id E6375E656E; Sun, 5 Aug 2012 18:31:52 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=/VoaTz3sNXcC THKAptrENXzmn4c=; b=dmqdxGj4UI/k3K8Axrh6WlUcL1vD38Oe3rxJqGkbY5MY 3yDocMhMLFInSi8T08V84qKDNO4jMDOjk0fejwKLxvi2LmiNw8SGlwWM67+IWH2a xdpYPEKl5GiCCHHOO4HKfmYefRkN9kr37K5eiOnwN0HghoHuvs4fo2KVSFJf1iA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=l7dfQr mevA/J4FjryIqAJ4iKIU9fBQbcjFOaYnqNm1nztO8p8DCVnsd8E899UzkhT4mf0p hKKrD5Cx7H8JA1Gi4NVee32mBDeMloVr2wtcoMC5hcz5bACnj2ABd7Uur2c0H2Gc ApK9mxS1Riw7IZorSxlyYvIgUHQ4X9P9NnzRg= Received: from [192.168.2.33] (unknown [93.89.81.205]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 86698E6486; Sun, 5 Aug 2012 18:31:52 +0100 (BST) Message-ID: <501EAD8E.2000505@cran.org.uk> Date: Sun, 05 Aug 2012 18:29:50 +0100 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Olivier Smedts References: <86bojxow6x.fsf@ds4.des.no> <4FF35864.5030109@FreeBSD.org> <20120704185104.GA42355@DataIX.net> <4FF4B36A.2040608@FreeBSD.org> <20120704180134.7c649e1b@bhuda.mired.org> <4FF4BEED.10103@FreeBSD.org> <20120704225519.GB19945@DataIX.net> <4FF4CAD1.8080804@FreeBSD.org> <20120704234104.GA392@DataIX.net> <8E9DECBB-3D1E-4129-A958-9DB0DF69ECC3@kientzle.com> <4FF4E105.50502@FreeBSD.org> <20120704203711.2732b645@bhuda.mired.org> <2EA305F0-87D9-47BE-B3E6-366659BF77AF@kientzle.com> <20120704214216.29085927@bhuda.mired.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 05 Aug 2012 20:34:57 +0000 Cc: freebsd-hackers@freebsd.org, Mike Meyer Subject: Re: Re: Better error messages for command not found (was Re: Pull in upstream before 9.1 code freeze?) 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: Sun, 05 Aug 2012 17:29:53 -0000 On 05/07/2012 10:48, Olivier Smedts wrote: > And it really annoys me too because usually, instead of an immediate > "command not found", you've got a reply seconds later if on a not so > fast computer. When working on Ubuntu, after a typo or missing command > I have the time to realize that something strange is happening, to > read again what I typed and to hit ^C before any message is displayed. > That annoys me too. The openSUSE guys worked on the same problem (https://bugzilla.novell.com/show_bug.cgi?id=435160), going from a few seconds down to 700ms and got told they'd need to do better :) In the end they added a COMMAND_NOT_FOUND_AUTO variable, disabled by default, to do the slow search, and the standard behaviour became to print a message similar to "Command not found. If this isn't a typo, run "cnf " to find the package containing it" which is a solution I like. -- Bruce Cran From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 5 21:37:29 2012 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 6C51B106564A for ; Sun, 5 Aug 2012 21:37:29 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3B5B38FC0A for ; Sun, 5 Aug 2012 21:37:29 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so186752pbb.13 for ; Sun, 05 Aug 2012 14:37:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=7/gNEXIFgUhpKP6FcTg9djJ0al4g6E3zOVYydVoxn9o=; b=DBE8AecqDAW36v07+4j+8hCqx0sR1kieLc9JJbydIYrTYcwJrKoNe6WqIlMa0k/oyS JNzMkl3Vx3jn1Gtu5ZQ5HPHCmb3mG27xId6puSM03ViwVYF8VmZcoULzCapidiiVnRwT DF320f47sleb5X2YiYmct6RgaYzYBidG8MVZh/KepOasdF2Dk5tF3YBLqYIHfSd+rMmN uHjc+dYCe26336O2witkQRB7xsPKHSu1rNiQs6pAi6t06awzB5YAbWbwrFn+YyZC1rNn fw8TLnz8sy/k5GgcZyzdqzvNjG5FuXAEa921kQAbNvofo1K+fmCEZY5tFliJQlIvgL+K 7XIg== MIME-Version: 1.0 Received: by 10.68.116.17 with SMTP id js17mr5728051pbb.109.1344202648748; Sun, 05 Aug 2012 14:37:28 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.115.232 with HTTP; Sun, 5 Aug 2012 14:37:28 -0700 (PDT) In-Reply-To: References: Date: Sun, 5 Aug 2012 14:37:28 -0700 X-Google-Sender-Auth: kQuWtjuA0zIGZHYZ5kEKfSEwwmk Message-ID: From: Adrian Chadd To: Wojciech Puchar Content-Type: text/plain; charset=ISO-8859-1 Cc: Outback Dingo , freebsd-hackers@freebsd.org Subject: Re: SMALL FreeBSD capable board 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: Sun, 05 Aug 2012 21:37:29 -0000 On 5 August 2012 10:07, Wojciech Puchar wrote: > thanks for answer. > TP-Link TL-WR1043ND seems to be best choice for me. I'm not sure how much power the thing draws when operational. It'd be nice if someone started taking responsibility for power save support on the SoCs. I'm happy to eventually make the wifi side of things power-save enabled, but I can't also do the ARM/MIPS SoCs. :( Adrian From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 5 21:54:34 2012 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 401B21065680 for ; Sun, 5 Aug 2012 21:54:34 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay04.stack.nl [IPv6:2001:610:1108:5010::107]) by mx1.freebsd.org (Postfix) with ESMTP id CD1AB8FC0A for ; Sun, 5 Aug 2012 21:54:33 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id F0C8D1DD5AD; Sun, 5 Aug 2012 23:54:32 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id CB1132847B; Sun, 5 Aug 2012 23:54:32 +0200 (CEST) Date: Sun, 5 Aug 2012 23:54:32 +0200 From: Jilles Tjoelker To: Konstantin Belousov Message-ID: <20120805215432.GA28704@stack.nl> References: <20120730102408.GA19983@stack.nl> <20120730105303.GU2676@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120730105303.GU2676@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org Subject: Re: system() using vfork() or posix_spawn() 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: Sun, 05 Aug 2012 21:54:34 -0000 On Mon, Jul 30, 2012 at 01:53:03PM +0300, Konstantin Belousov wrote: > On Mon, Jul 30, 2012 at 12:24:08PM +0200, Jilles Tjoelker wrote: > > People sometimes use system() from large address spaces where it would > > improve performance greatly to use vfork() instead of fork(). > > A simple approach is to change fork() to vfork(), although I have not > > tried this. It seems safe enough to use sigaction and sigprocmask system > > calls in the vforked process. > > Alternatively, we can have posix_spawn() do the vfork() with signal > > changes. This avoids possible whining from compilers and static > > analyzers about using vfork() in system.c. However, I do not like the > > tricky code for signals and that it adds lines of code. > > This is lightly tested. > It is interesting to note that for some time our vfork(2) no longer > stops the whole forked process (parent), only the forking thread is > waiting for the child exit or exec. I am not sure is this point > important for system(3), but determined code can notice the difference > from the fork->vfork switch. Neither fork nor vfork call thread_single(SINGLE_BOUNDARY), so this is not a difference. Thread singling may be noticeable from a failing execve() (but only in the process doing execve()) and in the rare case of rfork() without RFPROC. -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 01:48:04 2012 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 902A9106564A; Mon, 6 Aug 2012 01:48:04 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 5E7498FC08; Mon, 6 Aug 2012 01:48:04 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1SyCQN-000I33-OA; Mon, 06 Aug 2012 01:48:03 +0000 Date: Sun, 05 Aug 2012 18:48:03 -0700 Message-ID: From: Randy Bush To: Kevin Oberman In-Reply-To: References: <612DA8A3-121E-4E72-9E5B-F3CBA9DEB7F7@bsdimp.com> <501A0258.4010101@FreeBSD.org> <45815622-3CE2-42E3-B118-702AA70C7E4C@samsco.org> <501AB08E.8020008@FreeBSD.org> <501B1D3A.6080501@freebsd.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Mon, 06 Aug 2012 02:15:06 +0000 Cc: FreeBSD Hackers , FreeBSD Current Subject: Re: On cooperative work [Was: Re: newbus' ivar's limitation..] 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, 06 Aug 2012 01:48:04 -0000 > I suggest the starting point is a webpage with a link to the slides > being presented and a simple audio stream. two way, please. i am amazed that ietf had two-way back when it was the mbone. with multicast actually deployed, now it is one-way. randy From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 03:49:17 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id A7898106564A; Mon, 6 Aug 2012 03:49:17 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 4089214DA83; Mon, 6 Aug 2012 03:49:17 +0000 (UTC) Message-ID: <501F3EBC.50100@FreeBSD.org> Date: Sun, 05 Aug 2012 20:49:16 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: David Chisnall References: <612DA8A3-121E-4E72-9E5B-F3CBA9DEB7F7@bsdimp.com> <501A0258.4010101@FreeBSD.org> <501AAEF2.8060202@FreeBSD.org> <501AB8C0.3020102@FreeBSD.org> <501ABD43.5090604@FreeBSD.org> <501AC7EF.4070605@FreeBSD.org> <0F923CD6-BCF1-4722-8E4A-9485A7D6E279@freebsd.org> In-Reply-To: <0F923CD6-BCF1-4722-8E4A-9485A7D6E279@freebsd.org> X-Enigmail-Version: 1.4.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers , freebsd-current@freebsd.org Subject: Re: On cooperative work [Was: Re: newbus' ivar's limitation..] 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, 06 Aug 2012 03:49:17 -0000 On 08/02/2012 12:18, David Chisnall wrote: > Thank you for your thoughtful reply, You too ... I let some time go by to see what others had to say. I think it's disappointing that more people aren't concerned about this issue. > On 2 Aug 2012, at 19:33, Doug Barton wrote: > >> However, my point is that in spite of the fact that it's >> non-trivial, the mindset on this topic needs to change if the dev >> summits are going to continue to be significant focii of both work >> being done and decisions being made (which of course, they are). > > I believe that, before that decision can be made, there needs to be > some consensus on what the purpose of the DevSummits is. In my view, > DevSummits do not exist to set project policy. And yet, that's exactly what happens. It's easy to understand why ... you have a bunch of people together in the same place, they all agree on a topic, and after all, since they are the ones who are there, they should be the ones to make the decision, right? It's not necessarily that they are trying to do something malicious, it's just human nature. I know, I used to travel to conferences for a living. > They are places where: > > - People can talk face to face about their current and planned > projects. - Developers can meet on a social basis, making remote > working easier. > > The latter is very important - I've found in other projects that it's > far easier to work with someone on the other side of the world when > you've chatted with them over a few beverages-of-choice. I agree with these points as well. (Again, been there, done that.) In fact I'm quite confident that a lot of the "issues" people have with me are related to this deficiency. :) > Any official conversations happen on the mailing lists. This should be true, but it isn't. This is my point. > DevSummits > are for people working on similar things to meet and discuss their > plans, and for people to have a chance to get to know what everyone > else is doing, ... so far, so good .. > for a limited set of 'everyone else'. ... and this is where I call shenanigans. This is an open project. Anything that is going to be done is going to be seen. If there are problems with a proposal it's better to see them early. If it's a good proposal, there is no reason not to share it. > Slides and > summaries so on from the more structured parts of this are available > afterwards, which helps people who can't attend get the same benefit > - they know what other people are working on. In the IETF context proposals often benefit from the real-time focus of attention, from both local and remote participants, that the meetings provide. There is no reason to believe that this would not be true in FreeBSD as well. > The original complaint that spawned this long discussion was that > decisions about the project are made behind closed doors. This is > obviously true in the literal sense, as code always wins over chatter > in an open source project, and the person willing to sit down and > write the code gets the final say on how it should work, That's an oft-repeated maxim, especially around here. But we've already demonstrated that it isn't true. The only time that this is true is if the work being done is in line with what the PTB want. I've demonstrated this time after time by volunteering to do various projects "my way" and being told that my efforts weren't welcome. Not to mention having my finished, working code reverted by a core team member for an inferior, broken result. So can we please stop repeating that BS and focus on the real issues? > although > ideally with code review, design feedback and so on from others. > Even if we broadcast everything that happens in the official parts of > the DevSummits, that won't necessarily fix anything because a lot of > the most productive conversations happen over dinner or in the pub. The community needs to not be accepting of the status quo, and demand that things be publicized on the lists first before decisions are made. Once again, if they are good decisions, they won't be harmed by sharing them in advance. If they are less-good, we could be saving someone efforts that would be otherwise wasted. > If there is a real problem to address, then it is people making > policy decisions at DevSummits, without adequate consultation. I > have not observed this happening, but I would regard it as no > different to people making policy decisions via private email, and > something that should be subject to the same response: revisit the > decisions in public if there are legitimate concerns raised about it, > subject to the usual open source rule that the person actually > willing to do the work gets to make the final call. Exactly. > Finance is not the only obstacle. In some venues, bandwidth is a > problem (not at Cambridge hopefully - people will have stopped using > it all to stream the olympics by then), but in other venues we only > have WiFi, which is shared with a room full of developers. If we buy > some equipment (decent microphones are not always available - we were > unable to find one at FOSDEM for remote attendees, for example), then > it would need to be transported between events, and someone would > need to be responsible for looking after it and ensuring that it is > set up correctly at each event. It's already been explained that this is a soluble problem, and Julian has already solved it. The only obstacle at this point is desire of the organizers. > Remote participation is bidirectional, and I am a lot more wary about > that. The productivity of a meeting is usually inversely > proportional to the number of attendees, and allowing a lot more > people in does not necessarily improve anything for anyone. It's > always tempting to speak up and make A Contribution (I have certainly > been guilty of this in the past, and no doubt will be in the future) > when really the meeting needs everyone to shut up and move on to the > next item. That's up to the leader of the session to draw a line. Allowing remote participation doesn't change this dynamic, as it's actually *easier* for someone in the room to be a mic-hog; especially if remote input is via jabber. > The main advantage of the small group meetings is that > they don't degenerate into bikesheds as easily. Of course, the down > side is that they also lack any kind of mandate because they are not > including everyone's opinions, which is why summaries are posted on > the wiki and linked to from the mailing list so that longer > discussions can take place online. I think you've covered the tradeoffs. But again, see above on how allowing remote participation doesn't change anything. > Encouraging remote participation also has the unintended side effect > of discouraging real participation. I've seen in other projects that > when you try to make remote participation easy it means a lot of > people think 'well, I can just join in remotely, I don't need to make > the effort to turn up'. In all of the many organizations I participate in, both in person and remotely, I've never seen this dynamic; primarily because of the "fringe" benefits you describe so well above. I doubt it would happen in FreeBSD. > If the majority are not present in person, then we may as well not > have a DevSummit at all, and just have a regular conference call > that's open to all. Or, to save bandwidth, a mailing list or IRC > channel... I think you're failing to understand the scale of the problem. We have over 300 unique committers alone, never mind the community of non-committer developers. Expecting that even a significant percentage of them will be able to attend any given summit, never mind the one(s) where the things they care about are going to be discussed, is not realistic. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 08:03:53 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id D4CEB106567F for ; Mon, 6 Aug 2012 08:03:53 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id CE19B15594B; Mon, 6 Aug 2012 08:03:42 +0000 (UTC) Message-ID: <501F7A5E.6070007@FreeBSD.org> Date: Mon, 06 Aug 2012 01:03:42 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: Yuri References: <501871FD.601@rawbw.com> In-Reply-To: <501871FD.601@rawbw.com> X-Enigmail-Version: 1.4.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org Subject: Re: How to diagnose system freezes? 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, 06 Aug 2012 08:03:53 -0000 On 07/31/2012 17:02, Yuri wrote: > One of my 9.1-BETA1 systems periodically freezes. If sound was playing, > it would usually cycle with a very short period. And system stops being > sensitive to keyboard/mouse. Also ping of this system doesn't get a > response. Just for fun, have you tried switching to the 4BSD scheduler in your kernel config? -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 08:05:15 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 4F967106566B for ; Mon, 6 Aug 2012 08:05:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 20A1A1558E6; Mon, 6 Aug 2012 08:05:15 +0000 (UTC) Message-ID: <501F7ABA.7040200@FreeBSD.org> Date: Mon, 06 Aug 2012 01:05:14 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: Fabian Keil References: <1341863341.6064.11.camel@powernoodle.corp.yahoo.com> <4FFB4770.7050209@FreeBSD.org> <20120710154128.192eb8d6@fabiankeil.de> <1341939155.2573.8.camel@powernoodle.corp.yahoo.com> <20120710205702.5e57168b@fabiankeil.de> <4FFC8479.9080608@FreeBSD.org> <20120711122935.1382e76d@fabiankeil.de> <20120712201741.34573af4@fabiankeil.de> <4FFF2171.1030800@FreeBSD.org> <20120712213615.39640d1f@fabiankeil.de> <4FFF27F0.4000106@FreeBSD.org> <742407DF-8026-4976-A1F9-A170A62EF87A@averesystems.com> <1343429097.5002.14.camel@powernoodle.corp.yahoo.com> <20120731184813.04bd8dc2@fabiankeil.de> In-Reply-To: <20120731184813.04bd8dc2@fabiankeil.de> X-Enigmail-Version: 1.4.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Sean Bruno Subject: Re: dtraceall.ko with old nfsclient 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, 06 Aug 2012 08:05:15 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07/31/2012 09:48, Fabian Keil wrote: > I think guessing that INET and INET6 are available is a lot more > reasonable than doing the same for the external NFS modules. FYI, there has been considerable work done to ensure that INET6 works without INET, so it's not safe to assume anything about the other just because 1 of them is present. TMK you still need one or the other though ... - -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQH3q6AAoJEFzGhvEaGryEGXsH/RjKJQYsQqhbNw/Hb+vQV32V t9GiDcxrsiGBYWPwoGBUXf9UXLKz6V1KM47BUjZJaX3AEpjLWpkc10lanA1c6j23 DHvyU5gQVz4xjDm9xpLsiygCVuIQYKHE80ZmQRajeFwUOrcFMCyKuWH9evNjPWGq M11LYMbpBYbPw63LhYDpvcoxmi6E0LhvagWjgJfL1XNOcYK4kEHgxWv4wYjfLyuH +Vd1jTipkHSNxI7IdA0lHOsp7pNNQu5tSl/mQkH+72DXRKxNva63PnxrngQrRRv/ HrmZMMPRxjSyDUGkk/GzrH083yB17IP75eRJmvVplcZ5ytBSs7v2uqdmTmj/124= =OrU7 -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 08:25:41 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6AC5A106566B for ; Mon, 6 Aug 2012 08:25:41 +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 C23F98FC1A for ; Mon, 6 Aug 2012 08:25:40 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q768PmQH010701; Mon, 6 Aug 2012 11:25:48 +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.5/8.14.5) with ESMTP id q768PZo6026385; Mon, 6 Aug 2012 11:25:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q768PZNs026384; Mon, 6 Aug 2012 11:25:35 +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: Mon, 6 Aug 2012 11:25:35 +0300 From: Konstantin Belousov To: Jilles Tjoelker Message-ID: <20120806082535.GI2676@deviant.kiev.zoral.com.ua> References: <20120730102408.GA19983@stack.nl> <20120730105303.GU2676@deviant.kiev.zoral.com.ua> <20120805215432.GA28704@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhJ190OLnagu9UvS" Content-Disposition: inline In-Reply-To: <20120805215432.GA28704@stack.nl> 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=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham 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: system() using vfork() or posix_spawn() 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, 06 Aug 2012 08:25:41 -0000 --AhJ190OLnagu9UvS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 05, 2012 at 11:54:32PM +0200, Jilles Tjoelker wrote: > On Mon, Jul 30, 2012 at 01:53:03PM +0300, Konstantin Belousov wrote: > > On Mon, Jul 30, 2012 at 12:24:08PM +0200, Jilles Tjoelker wrote: > > > People sometimes use system() from large address spaces where it would > > > improve performance greatly to use vfork() instead of fork(). >=20 > > > A simple approach is to change fork() to vfork(), although I have not > > > tried this. It seems safe enough to use sigaction and sigprocmask sys= tem > > > calls in the vforked process. >=20 > > > Alternatively, we can have posix_spawn() do the vfork() with signal > > > changes. This avoids possible whining from compilers and static > > > analyzers about using vfork() in system.c. However, I do not like the > > > tricky code for signals and that it adds lines of code. >=20 > > > This is lightly tested. >=20 > > It is interesting to note that for some time our vfork(2) no longer > > stops the whole forked process (parent), only the forking thread is > > waiting for the child exit or exec. I am not sure is this point > > important for system(3), but determined code can notice the difference > > from the fork->vfork switch. >=20 > Neither fork nor vfork call thread_single(SINGLE_BOUNDARY), so this is > not a difference. It is the difference, because vforked child shares parent address space. >=20 > Thread singling may be noticeable from a failing execve() (but only in > the process doing execve()) and in the rare case of rfork() without > RFPROC. No, other running threads in parent affect vforked child till exec or exit. In fact, I would classify this as bug, but not a serious one. --AhJ190OLnagu9UvS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAff38ACgkQC3+MBN1Mb4jB+ACg4tGn73m900YArlOgJJnXXN23 VpEAoMfnQYjoWd4MBo9dz6PCtzqdHyE2 =UYgY -----END PGP SIGNATURE----- --AhJ190OLnagu9UvS-- From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 13:08:37 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D2277106566B for ; Mon, 6 Aug 2012 13:08:37 +0000 (UTC) (envelope-from bcrisp@crispernetworks.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7BE888FC1A for ; Mon, 6 Aug 2012 13:08:37 +0000 (UTC) Received: by vbmv11 with SMTP id v11so1536363vbm.13 for ; Mon, 06 Aug 2012 06:08:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=IjO7pLxJofii5IP+41lfuJiaTfYBKzMlGvuiYJlFkW8=; b=LTL/mXqhIUhJ1ef5hRh9IvfUbu3GvYoPhviX9/Urh7Zk9KZuqrs06fKEtKyXW7ZtdY djkuSh/zzs5+CLdx8MyjH5vpRHto87ayBNneijo8mH5wkX1EQprLvjMWrr8JtiXT71aJ 8aTYyNWSNxtRYsveGDLyzta5jbRXHZzaF9kaOc2yDYVXvOG+SDjMtHDrQCGkUdoBgrpy eAbs1rzCxOmeN2hJpVRqg/feNlJnAHDP+Ui22hOu2z/ak2PcDKb+QY72b9/C8DiuRqLE lG4rph6AT6wXhYfanCecXyIQxoUuGyeCqnu+GHjzc1GbxMYwl19X3vbrkqo1QLpbs8BC tstg== MIME-Version: 1.0 Received: by 10.220.220.78 with SMTP id hx14mr8012769vcb.23.1344258516472; Mon, 06 Aug 2012 06:08:36 -0700 (PDT) Received: by 10.58.125.42 with HTTP; Mon, 6 Aug 2012 06:08:36 -0700 (PDT) In-Reply-To: References: <4FFF4B95.9080105@delphij.net> Date: Mon, 6 Aug 2012 09:08:36 -0400 Message-ID: From: Bill Crisp To: James X-Gm-Message-State: ALoCoQnNEjffOUD+210Xps1Wka+f5/HbgOpC6iSgXFh2ZVDaD7MiRWfjNO9VMmt8scfvVBrsPTg5 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, Xin Li Subject: Re: CVE-2012-0217 Intel's sysret Kernel Privilege Escalation and FreeBSD 6.2/6.3 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, 06 Aug 2012 13:08:37 -0000 Thanks for the patch! I gave it a try on a few servers, and saw a big increase in load on the servers, most of the load comes from apache under normal circumstances and it that load did go up a lot. I had to roll back the patched kernel and the load went back to what it normally is. Did you experience anything similar on any servers? On a server where the load was ~1 it went up with what seemed to be the same number of requests to something like ~6 or so on a single core servers. Ones that had higher load already also went up considerably. Any ideas on what I might be able to do? Let me know if you have a chance. On Wed, Jul 18, 2012 at 4:59 PM, James wrote: > On Wed, Jul 18, 2012 at 3:26 PM, Bill Crisp > wrote: > > > > Unfortunately I tried to put the code from the patch in place but there > > seems to be some missing functions in the header file and too many > > arguments to a function and some other errors below: > > Hi Bill. Yes, the patch for >= FreeBSD 7 won't apply directly to > 6. ksi and the refined SIGBUS traps don't exist yet. Here's how I > fixed it at work. Using this on multiple releng_6* branches. > > HTH! > > -- > James. > From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 14:40:01 2012 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 75852106566B; Mon, 6 Aug 2012 14:40:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 487F58FC0A; Mon, 6 Aug 2012 14:40:01 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 86C41B972; Mon, 6 Aug 2012 10:40:00 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 6 Aug 2012 10:07:37 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Message-Id: <201208061007.37898.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 06 Aug 2012 10:40:00 -0400 (EDT) Cc: Tim Kientzle Subject: Re: How to Expose Chip-level Ethernet Statistics? 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, 06 Aug 2012 14:40:01 -0000 On Saturday, August 04, 2012 3:21:23 pm Tim Kientzle wrote: > I believe that some of the issues I'm having with this > Ethernet driver might be easier to diagnose if I could > expose the chip-level statistics counters (especially queue > overrun counts). >=20 > Is there a standard way to do this? >=20 > I've looked at systat, netstat, and ifconfig but haven't > yet found a standard tool that queries this sort of > information. (If I could find that, I could figure out > which ioctl it used=85) >=20 > Pointers appreciated=85 In particular, if there's another > Ethernet driver that does this well, I can use that for a > reference. Several drivers (igb, em, cxgb, cxgbe, ixgbe, etc.) just expose a "stats" sysctl node under the device and populate that with stats. Typically they install a SYSCTL_PROC() that directly queries the register. In some cases they read the registers via a timer and cache the results and the sysctl handlers returned the cached results. =2D-=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 14:40:02 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 83C9E1065670 for ; Mon, 6 Aug 2012 14:40:02 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 535488FC0C for ; Mon, 6 Aug 2012 14:40:02 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 99D50B941; Mon, 6 Aug 2012 10:40:01 -0400 (EDT) From: John Baldwin To: Peter Jeremy Date: Mon, 6 Aug 2012 10:16:13 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120703111753.GB72292@server.rulingia.com> <20120708110516.GA38312@server.rulingia.com> <201207120826.05577.jhb@freebsd.org> In-Reply-To: <201207120826.05577.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201208061016.13065.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 06 Aug 2012 10:40:01 -0400 (EDT) Cc: freebsd-hackers@freebsd.org Subject: Re: contigmalloc() breaking Xorg 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, 06 Aug 2012 14:40:02 -0000 On Thursday, July 12, 2012 8:26:05 am John Baldwin wrote: > However, rather add a wiredmalloc(), I think you should just have > bus_dmamem_alloc() call kmem_alloc_attr() directly in this case. One of the > things I've been meaning to add to bus_dma is a way to allocate other memory > types (e.g. WC memory), and in that case it would be best to just call > kmem_alloc_attr() directly instead. After my recent changes, I think this would do the above. What do you think of this, and if it looks ok, can you test it? Index: busdma_machdep.c =================================================================== --- busdma_machdep.c (revision 239020) +++ busdma_machdep.c (working copy) @@ -533,13 +533,14 @@ bus_dmamem_alloc(bus_dma_tag_t dmat, void** vaddr, dmat->lowaddr >= ptoa((vm_paddr_t)Maxmem) && attr == VM_MEMATTR_DEFAULT) { *vaddr = malloc(dmat->maxsize, M_DEVBUF, mflags); + } else if (dmat->nsegments >= btoc(dmat->maxsize) && + dmat->alignment <= PAGE_SIZE && + (dmat->boundary == 0 || dmat->boundary >= dmat->lowaddr)) { + /* Page-based multi-segment allocations allowed */ + *vaddr = (void *)kmem_alloc_attr(kernel_map, dmat->maxsize, + mflags, 0ul, dmat->lowaddr, attr); + *mapp = &contig_dmamap; } else { - /* - * XXX Use Contigmalloc until it is merged into this facility - * and handles multi-seg allocations. Nobody is doing - * multi-seg allocations yet though. - * XXX Certain AGP hardware does. - */ *vaddr = (void *)kmem_alloc_contig(kernel_map, dmat->maxsize, mflags, 0ul, dmat->lowaddr, dmat->alignment ? dmat->alignment : 1ul, dmat->boundary, attr); -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 18:20:44 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 64E0610656F3 for ; Mon, 6 Aug 2012 18:20:44 +0000 (UTC) (envelope-from jamebus@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id D65AD8FC14 for ; Mon, 6 Aug 2012 18:20:43 +0000 (UTC) Received: by lbbgk8 with SMTP id gk8so1057452lbb.13 for ; Mon, 06 Aug 2012 11:20:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=QDqAvZxpJVQ9mgg50ShQ0lSCE5SIiMxjbHLHwqp2kQ4=; b=ikfGhYE46GaNn1EUFjpLkuXOVSry5r9BQr0xj4n7s2+M5ZJPFw0uFZnzuVVP3TX7yv Z5439b9UCLD9GQGe5Xi1oSeVLbNBpfPS2BQsdJaGnwxuS0IanCsQxuDRmsr2BdLzHTFl LKMu1o4jnfbLKovLavDq52rSQk+E00D8iJoe+0kbqtM40uR1S1X3MmJu8UPbbRrl0rEq ErZ1ZIkWfYFXUkg7oHaD7q6geCMHRnwRHhTeK4cKSctvuiAK1LRDJcMN/YOVyhMc0rjX Uwk5lc2pRYwbupRAqKp6KLerlVO8HM2r1C5motFXRT2SCUbGJs3SsCMWKo4zHnyFjIN4 Ho4g== MIME-Version: 1.0 Received: by 10.112.36.195 with SMTP id s3mr4997415lbj.42.1344277242194; Mon, 06 Aug 2012 11:20:42 -0700 (PDT) Sender: jamebus@gmail.com Received: by 10.112.78.9 with HTTP; Mon, 6 Aug 2012 11:20:42 -0700 (PDT) In-Reply-To: References: <4FFF4B95.9080105@delphij.net> Date: Mon, 6 Aug 2012 13:20:42 -0500 X-Google-Sender-Auth: kSovltaA6LyvyF7tCwo702LkzVE Message-ID: From: James To: Bill Crisp Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, Xin Li Subject: Re: CVE-2012-0217 Intel's sysret Kernel Privilege Escalation and FreeBSD 6.2/6.3 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, 06 Aug 2012 18:20:44 -0000 On Mon, Aug 6, 2012 at 8:08 AM, Bill Crisp wrote: > I gave it a try on a few servers, and saw a big increase in load on > the servers, most of the load comes from apache under normal > circumstances and it that load did go up a lot. I had to roll back > the patched kernel and the load went back to what it normally is. > Did you experience anything similar on any servers? On a server > where the load was ~1 it went up with what seemed to be the same > number of requests to something like ~6 or so on a single core > servers. Ones that had higher load already also went up > considerably. Any ideas on what I might be able to do? Hi Bill. I'm sorry you're having trouble. That's a pretty annoying problem. But no, I haven't noticed any increase in load averages. I'll keep an eye out, though. Wish I had a better answer for you now. -- James. From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 18:31:23 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CC51C1065677; Mon, 6 Aug 2012 18:31:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 92A998FC21; Mon, 6 Aug 2012 18:31:23 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so1696378pbb.13 for ; Mon, 06 Aug 2012 11:31:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EIeODR+mONY/qRNJNDl9B8w0GtfBxBA2d93mT9E2tsc=; b=jsP8nIIol5/A+yiqHFwmCiNaemrF1Lmp9nARk71ohM9gaX+/4BOuCYuSldUAUXwhAd QSlyt/W0yYX1+DUKAB5CI3UzcIIt0Pntc1kiVIUJF5qDRvWLWf93yPaNRb1nRvprxv8c S+wGVMWkqrngtTUBwbzc5MnbYNEDl4GZ2LyKF5vvZc3RYm/3nrIjaGsVDqh0r0q+4aZx zeeJ4R7jgKt8M2M0qW6mXJCZGQrCPVi5KvqdYXPnfwSwwPITP1+ejH/HfeF3tGemS+UV GCSuozt5EsnCcMqmx2RK9N9z3zBinh7a6W1uaMOpQZnMvz/0M0uQlH7wa1eqG5JOlVfI rosQ== MIME-Version: 1.0 Received: by 10.68.218.7 with SMTP id pc7mr20887245pbc.88.1344277883207; Mon, 06 Aug 2012 11:31:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.115.232 with HTTP; Mon, 6 Aug 2012 11:31:23 -0700 (PDT) In-Reply-To: <201208061007.37898.jhb@freebsd.org> References: <201208061007.37898.jhb@freebsd.org> Date: Mon, 6 Aug 2012 11:31:23 -0700 X-Google-Sender-Auth: 5jONyJdWXffaZzAXd67SnhZuJ38 Message-ID: From: Adrian Chadd To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, Tim Kientzle Subject: Re: How to Expose Chip-level Ethernet Statistics? 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, 06 Aug 2012 18:31:23 -0000 I think the Linux folk have tried to export some generic-y API for driver-driven statistics, via ethstats or something. This includes wifi statistics. Just FYI, Adrian From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 6 20:23:47 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C8465106564A; Mon, 6 Aug 2012 20:23:47 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 34CE78FC16; Mon, 6 Aug 2012 20:23:46 +0000 (UTC) Received: by weyx56 with SMTP id x56so2817019wey.13 for ; Mon, 06 Aug 2012 13:23:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=r+Takw7lmomJNT/1u0CQPztYsNZ7jsZGO73sgYa+XNU=; b=oj7zMIbJGEOuB3s7ar55GaFU+pBpO/TrVY1alaDPwEuBqmbCZhg3CRFEc601kIqWau gRhffF7DwP0kgAAgu7mTl33J9wxsDEWrrr41UtPKbqbWom80oy/INos/DcuXwkJKKnM5 WiNaWLhZBvor93/+obKrmR7Ab72j5l90CfQF0Mbcct26uauHzhrrGBgoduW5VQDMt2Jy 2xycsxXQPRdnl3D13nSwSWNdOWsaZE18HLED1Jdz1R4QhXN6F5D1WCjGFUCaNG9K1SdH 7FqYRsvz6KLCsdLNNG1Ara26HO1bDh2HznKhMKveocrm3G40D4Tx4rg+OODZSbwIpv2Q r+xw== MIME-Version: 1.0 Received: by 10.180.99.133 with SMTP id eq5mr7816554wib.0.1344284626002; Mon, 06 Aug 2012 13:23:46 -0700 (PDT) Received: by 10.216.24.197 with HTTP; Mon, 6 Aug 2012 13:23:45 -0700 (PDT) Date: Mon, 6 Aug 2012 23:23:45 +0300 Message-ID: From: Vitaly Magerya To: Doug Barton Content-Type: text/plain; charset=UTF-8 Cc: "Bjoern A. Zeeb" , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , Garrett Wollman , FreeBSD Hackers Subject: Re: Replacing BIND with unbound 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, 06 Aug 2012 20:23:47 -0000 Doug Barton wrote: > On 07/07/2012 16:33, Garrett Wollman wrote: >> The utilities (specifically host(1) and dig(1)) are the only >> user-visible interfaces I care about. [...] > ldns (a dependency of unbound) comes with drill, which is a dig-alike > tool. I'd like to see us produce a host-alike based on ldns as well, If there still is interest, I've got just that at [1]. This tool, ldns-host, implements all the options of bind9-host (except for debugging ones), and produces close (and often identical) output. There's a list of differences between ldns-host and bind9-host in the man page (see [2]); most items can be fixed if people will request for it. Some more exotic situations where not tested though, so that list is only partial. [1] http://hg.tx97.net/ldns-host/file/ [2] http://manweb.tx97.net/http://hg.tx97.net/ldns-host/raw-file/tip/ldns-host.1 From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 7 00:34:32 2012 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 852B310656D0; Tue, 7 Aug 2012 00:34:32 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 438C98FC0C; Tue, 7 Aug 2012 00:34:32 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q770YU4W028801; Mon, 6 Aug 2012 17:34:31 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <50206296.4060802@rawbw.com> Date: Mon, 06 Aug 2012 17:34:30 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120802 Thunderbird/14.0 MIME-Version: 1.0 To: John Baldwin References: <4F775DF5.1020704@rawbw.com> <4F8A8CD2.5020103@rawbw.com> <20120415093029.GR2358@deviant.kiev.zoral.com.ua> <201204160959.29089.jhb@freebsd.org> In-Reply-To: <201204160959.29089.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Konstantin Belousov , freebsd-hackers@freebsd.org Subject: Re: Is there any modern alternative to pstack? 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, 07 Aug 2012 00:34:32 -0000 On 04/16/2012 06:59, John Baldwin wrote: > I'm fine with putting it into the base. If so, we should import 1.2 first I > think and then apply the 1.3 patch. So are there plans to import it into the base? Maybe for 9.1? /usr/ports/sysutils/pstack is still i386 only. Yuri From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 7 18:50:16 2012 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 AFA14106564A for ; Tue, 7 Aug 2012 18:50:16 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6313D8FC0A for ; Tue, 7 Aug 2012 18:50:16 +0000 (UTC) Received: by ggnk4 with SMTP id k4so4891149ggn.13 for ; Tue, 07 Aug 2012 11:50:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=iemMaSl3mToLfUeS3Wj5T6qpLOcsrGpRb4JtKDUx1K8=; b=d3n4oSzgq3XJKIXb+KahQx9/zjm/1YDYDZA6jfHgdiJhmIaYjAUaGXfw2sMJbjCqSo 3bVBXJf+5+tt5/KYkIpVeNSqmuitfYzpNvsTUpPt+e/bJvxYtj8DuVZQ0dNjzlJj4thW 5njGwjwR/GKxL7adGJkTm1QY3bTx+3VabJWqiF+Di+Jw/N+8rOXysllTPYS42Y7QR4jy XG9VeLt81nhb+knkf3XmVWJ4y0CJT9m4E34p1d4xS55FJWmFxMJ8KkfPHKgxFxMtZ2xt cvNs02DsM9vbuNqp3XiruluRg2XaIPplCxz+FlPDlg6aE/2PDgXoaCnXk6PvEB6V22yN v4Ng== Received: by 10.60.12.234 with SMTP id b10mr25979206oec.72.1344365415448; Tue, 07 Aug 2012 11:50:15 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPS id o9sm15662005oeg.5.2012.08.07.11.50.14 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Aug 2012 11:50:14 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Tue, 7 Aug 2012 12:50:11 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <1878A9A5-E1E9-45D9-829F-D8F544346AA0@bsdimp.com> References: To: Wojciech Puchar X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQn6GOmFfiC2RWALnfGRtYrXM1q+1B1ldNh2e1QoyDj/aDTz4oTO+X/3B1NVRCA6FiVnL8Az Cc: freebsd-hackers@freebsd.org Subject: Re: SMALL FreeBSD capable board 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, 07 Aug 2012 18:50:16 -0000 On Aug 5, 2012, at 8:36 AM, Wojciech Puchar wrote: > i am looking for SMALL and specifically low power board that can run = from battery, can run FreeBSD and have at least one ethernet and one USB = port, and reasonable amount of memory (32MB at least). > WiFi not needed. some more than few MB flash is, as well as about 10 = GPIO ports or useful SPI port. >=20 > I already see a lot of useful supported ones in source tree, with ARM = and MIPS. >=20 > I want to make portable router PLUS my own add own hardware, and have = full control over software running on it. >=20 > Any recommendation. >=20 > Ethernut 5 seems great > http://www.ethernut.de/en/hardware/enut5/index.html >=20 > but no info about price and availability in Poland You're looking at about $250 or EU 200 for that. I'd recommend something like: http://www.glomationinc.com/product_9G20u.html which is US$55 + shipping. A friend got one too and will be building an = alarm clock out of it (complicated one). http://www.mini-box.com/pico-SAM9G45-X which is US$69, but has a 4 week lead time. I have both of these on = order. NAND isn't yet supported, but is high on my Atmel hit list. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 7 23:18:05 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 168011065673 for ; Tue, 7 Aug 2012 23:18:05 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id CD67F8FC0A for ; Tue, 7 Aug 2012 23:18:04 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q77NGqEp029750 for ; Tue, 7 Aug 2012 16:16:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1344381413; bh=EjRq0LwURzAMgUE0C6HSOL4EYrgv3FCyDdfo7zdy6b0=; h=Subject:From:Reply-To:To:Content-Type:Date:Message-ID: Mime-Version:Content-Transfer-Encoding; b=l4bA16XiBHg397fWod+cFpoW4s1SwncKrV5E2aRstCPr63G3GE1G4GLSYeC3YCLaS zn5ojqsT+piiMH6ka6Al9OYqLNLAJU/Xwgm4wJN40TJv+uYagf9cWz+q1U27EAcFPq DnWgWAHk8zKvtmjzI8A50JDJLmk+X2uEroT8P7Fs= From: Sean Bruno To: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Tue, 07 Aug 2012 16:16:51 -0700 Message-ID: <1344381411.18854.16.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 381412002 Subject: pmc warnings on stable/9 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, 07 Aug 2012 23:18:05 -0000 I have no idea the significance, or danger. When compiling on stable/9 I have always seen the following WARNINGS. Can we silence/fix these? Or is it supposed to be that way? :-) WARNING: hwpmc_soft.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_pmc.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_rwlock.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_sx.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_lock.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_intel.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_tsc.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_amd.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_clock.c: enum pmc_event has too many values: 1531 > 1023 WARNING: kern_mutex.c: enum pmc_event has too many values: 1531 > 1023 WARNING: trap.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_x86.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_uncore.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_piv.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_core.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_logging.c: enum pmc_event has too many values: 1531 > 1023 WARNING: hwpmc_mod.c: enum pmc_event has too many values: 1531 > 1023 From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 7 23:18:18 2012 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 8D90F106564A for ; Tue, 7 Aug 2012 23:18:18 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id 36F498FC12 for ; Tue, 7 Aug 2012 23:18:18 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q77NHikK030040 for ; Tue, 7 Aug 2012 16:17:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1344381465; bh=GjlSW/YRs/mw3Lbil2PsWD1k0Z2snFoRHPuhAPnF404=; h=Subject:From:Reply-To:To:Content-Type:Date:Message-ID: Mime-Version:Content-Transfer-Encoding; b=ppuJX0gZ2HWfeffTSUQFVH+4VZ+0J9k+WoGLvEfJYWto3YJomlFkPPwsQA/GAOY1G 8Kc1FCAO/ZS59yKJsS3Z7xBG+UssCh9V9FJBGW6BvwouKlVP1WheIZYfZbn+XOTTAm 4bdmoun4C6pkltvCGlBucUCHFypazU2eXALSZDl0= From: Sean Bruno To: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Tue, 07 Aug 2012 16:17:44 -0700 Message-ID: <1344381464.18854.17.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 381464005 Subject: ctfconvert failure on stable/9 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, 07 Aug 2012 23:18:18 -0000 Not sure what to make of this error: ERROR: ctfconvert: rc = 2 No entry found [dwarf_next_cu_header(57)] my kernel is compiling, but I seem to fail at understanding something? Sean From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 7 23:37:25 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E30E1065674; Tue, 7 Aug 2012 23:37:25 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3E1F78FC0C; Tue, 7 Aug 2012 23:37:24 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so224334vcb.13 for ; Tue, 07 Aug 2012 16:37:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=un6fDh/QTrYotz1oP5H9ta4Nva0r8xEtSZxTBW2kIaU=; b=GkGamzaUH7jPD8w3rcLuPs7iyWjQf/3nmzI9K9AGb8lGmW+pThjZfJvrFYritMXoAf Loc9XZCYWvguSRdvmvdOQFY40DSmAtgo5s5UjIN7thaNdO3e/bv/ClFJClxBAmWEqlDi SltyZqq1WTpRMFXDdDTK+x81Fl5FT/XG50oil0pu/UAh2qz0xA74ZwhHM76Zx747Ajr9 b+nN/nAoSPoBMH5ZOC/ShBXzDAKJEWEsnkG6MUZZOBm++mc0MY8Eh8EHlBIToxDWAoiI yrk5GEN9q0VgcxIWUj74OY6ArG9ihP+/I/tXyP0z+KlR3VInGPLGHnh9/eXvAq1G0Bv+ onhA== MIME-Version: 1.0 Received: by 10.221.10.13 with SMTP id oy13mr350640vcb.14.1344382644298; Tue, 07 Aug 2012 16:37:24 -0700 (PDT) Received: by 10.58.114.102 with HTTP; Tue, 7 Aug 2012 16:37:24 -0700 (PDT) In-Reply-To: <1344381411.18854.16.camel@powernoodle.corp.yahoo.com> References: <1344381411.18854.16.camel@powernoodle.corp.yahoo.com> Date: Tue, 7 Aug 2012 19:37:24 -0400 Message-ID: From: Ryan Stone To: sbruno@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-hackers@freebsd.org" Subject: Re: pmc warnings on stable/9 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, 07 Aug 2012 23:37:25 -0000 On Tue, Aug 7, 2012 at 7:16 PM, Sean Bruno wrote: > I have no idea the significance, or danger. When compiling on stable/9 > I have always seen the following WARNINGS. Can we silence/fix these? > Or is it supposed to be that way? :-) > > WARNING: hwpmc_soft.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_pmc.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_rwlock.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_sx.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_lock.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_intel.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_tsc.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_amd.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_clock.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_mutex.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: trap.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_x86.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_uncore.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_piv.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_core.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_logging.c: enum pmc_event has too many values: 1531 > > 1023 > WARNING: hwpmc_mod.c: enum pmc_event has too many values: 1531 > 1023 > > > _______________________________________________ > 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" These warnings(and the previous one from your other thread) both come from ctfconvert. I haven't looked into them in detail but I suspect that the CTF format is not able to represent things like enums with more than 1024 entries, or structures with more than a certain number of members. I've never seen any actual side-effects of the warnings, although I suspect that if you tried to use DTrace to examine variables with the affected types you wouldn't be able to inspect everything. As far as I know, DTrace is the only consumer of CTF data in the kernel. I have dreams of replacing DTrace's usage of CTF with libdwarf, but that's little more than idle musings on my part at this stage. From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 7 23:52:50 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A9B3106564A; Tue, 7 Aug 2012 23:52:50 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 934298FC0A; Tue, 7 Aug 2012 23:52:49 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so143205wgb.31 for ; Tue, 07 Aug 2012 16:52:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=J6v4ZmgB4Zn7P/JEpMKTnb+oLssm8RDJ5Dnp/yhHL4A=; b=UOU3kDcBozQc0LO+sANsQJCc6B0bokMsV++OkrOGLG/UlQbzkEeX2fM8cdranUL4DJ Lsyas1uCe1/Q9tumkptZ19x5+JbSyR0gwb5f/z1xz9AbxKVDPRo3/Gx6pZ18Z5WdcwfO pT01CgCBlAQuEnku2L0vxuhjjdqM4nzVaoTYZ+B53NtF4eE2vJoRqDXqHnUl2ACGWFXj 0IbpU+KJgUPGU4SVxMHM1izg+DiLZGTWSs+k0PNJm9XSZhAybjMjx982CKlywy3oebLQ C1RKO0GrkpsA/mUcw5cYh/vyR4bdHXQdKrhwqb4Dk/t81u/2ohvdWJN7oFbt7NFcoiuH cR7A== MIME-Version: 1.0 Received: by 10.216.232.204 with SMTP id n54mr9009823weq.182.1344383568445; Tue, 07 Aug 2012 16:52:48 -0700 (PDT) Received: by 10.216.241.203 with HTTP; Tue, 7 Aug 2012 16:52:48 -0700 (PDT) In-Reply-To: References: <1344381411.18854.16.camel@powernoodle.corp.yahoo.com> Date: Tue, 7 Aug 2012 16:52:48 -0700 Message-ID: From: Jim Harris To: Ryan Stone Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-hackers@freebsd.org" Subject: Re: pmc warnings on stable/9 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, 07 Aug 2012 23:52:50 -0000 On Tue, Aug 7, 2012 at 4:37 PM, Ryan Stone wrote: > On Tue, Aug 7, 2012 at 7:16 PM, Sean Bruno wrote: >> I have no idea the significance, or danger. When compiling on stable/9 >> I have always seen the following WARNINGS. Can we silence/fix these? >> Or is it supposed to be that way? :-) >> >> WARNING: hwpmc_soft.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_pmc.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_rwlock.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_sx.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_lock.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_intel.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_tsc.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_amd.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_clock.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: kern_mutex.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: trap.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_x86.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_uncore.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_piv.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_core.c: enum pmc_event has too many values: 1531 > 1023 >> WARNING: hwpmc_logging.c: enum pmc_event has too many values: 1531 > >> 1023 >> WARNING: hwpmc_mod.c: enum pmc_event has too many values: 1531 > 1023 >> >> >> _______________________________________________ >> 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" > > These warnings(and the previous one from your other thread) both come > from ctfconvert. I haven't looked into them in detail but I suspect > that the CTF format is not able to represent things like enums with > more than 1024 entries, or structures with more than a certain number > of members. I've never seen any actual side-effects of the warnings, > although I suspect that if you tried to use DTrace to examine > variables with the affected types you wouldn't be able to inspect > everything. As far as I know, DTrace is the only consumer of CTF data > in the kernel. > > I have dreams of replacing DTrace's usage of CTF with libdwarf, but > that's little more than idle musings on my part at this stage. > _______________________________________________ > 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" FYI - r207578 added this warning to FreeBSD's ctf, specifically to handle the large pmc_entry enumeration. http://svnweb.freebsd.org/base?view=revision&revision=207578 From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 8 00:24:45 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 08FC11065670 for ; Wed, 8 Aug 2012 00:24:45 +0000 (UTC) (envelope-from ali_mousa_zy@yahoo.com) Received: from nm15-vm2.bullet.mail.ne1.yahoo.com (nm15-vm2.bullet.mail.ne1.yahoo.com [98.138.91.91]) by mx1.freebsd.org (Postfix) with SMTP id A522B8FC0A for ; Wed, 8 Aug 2012 00:24:44 +0000 (UTC) Received: from [98.138.90.49] by nm15.bullet.mail.ne1.yahoo.com with NNFMP; 08 Aug 2012 00:24:37 -0000 Received: from [98.138.88.232] by tm2.bullet.mail.ne1.yahoo.com with NNFMP; 08 Aug 2012 00:24:37 -0000 Received: from [127.0.0.1] by omp1032.mail.ne1.yahoo.com with NNFMP; 08 Aug 2012 00:24:37 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 963818.46091.bm@omp1032.mail.ne1.yahoo.com Received: (qmail 41632 invoked by uid 60001); 8 Aug 2012 00:24:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1344385477; bh=odbLHTBCjbQL3crhl7dsMNZ4CjRiwUB/vsvIfXTWHlI=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=ux++4Tjyh8LB0x9yZy08sDVz0G9pmZjWcrbv/Vpg09Ds8Xkz0vvHEEA+tFT/FOB4ax1psjHGuPWAiYS3AsfeG7oL0dNzGr8xYYuYOXse51DrT7PRx+0V79gbolwckIvqu7nGR6nTKmEy7QGKJt+ESLPC9nvXZp8iAIj0cy8Ga1w= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=oZibMspKqNJXSJM6GR25mt0rirmoEccW9a5VlNvMRHGVl5fAXPyys00TkDjGZa4gmVG0juRjSRBjdwrSzkoW/WR7pJlZzx1NgoAmCzpR7mZY0IWQvir8TQnm3MRBvKsJRV+lYX6X73D6ynJqieGWztavgwbOdsF/eslNEud6lqE=; X-YMail-OSG: y6NNnGoVM1kwVuANdrDb2ifrwcumiQ0ENvQ4wDLABwEa_xU .cF0zgI_1Zkv.RX5x1ojJONsADCU.FE5FXTs1huLDhUjLWXHQ.ioUunfSL.O RY2tkibsZt8XKiyBFmavcoSx.9E03D8fb.3nHu044y9mTKJpD5Mp_noUZv6N Co_QFd9ARNw7pu75wP2PJPqFdkaVneJAqssqJU_JtkO8UjRg7j0YsFtt1CId iTIxTrclGH3aMKbTiaWAxCQ5YOsAjlvTbbTYMVK5SE_09RZ0y9KsiysfWG6f IlbC5puHLZpaJozfxf6wlLUopZG68KP9u35NHio3C96ijUZ84Lm.D8qdAsc6 mZZYue4BtL7JE2ldJw7It8zw53yn5q5OjWP6PEkqjnjPscKl1RlIiKz3J7tg Jo.8KvdS7ppsP8GqiPPLrhiwcYfPUbgdRMqUF91.KEoBVfZWKKJlIU4G2.Ei acUexWj_0L1E_WkApWr08ws5eH1Z0aOFGmdQ5ZLK1cngflzLplYZX2.oJxkF Vv76n3RNPxDB3LyDg3bBulvazejsyB8eUGmitzOf10A3pMFBIsfAuE_nWXA- - Received: from [46.185.156.227] by web125401.mail.ne1.yahoo.com via HTTP; Tue, 07 Aug 2012 17:24:37 PDT X-Mailer: YahooMailWebService/0.8.120.356233 Message-ID: <1344385477.41536.YahooMailNeo@web125401.mail.ne1.yahoo.com> Date: Tue, 7 Aug 2012 17:24:37 -0700 (PDT) From: ali mousa To: "freebsd-hackers@freebsd.org" MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 08 Aug 2012 02:28:38 +0000 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Published paper X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ali mousa List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Aug 2012 00:24:45 -0000 Hi, I have recently published a paper related to Operating System, can you please check it out http://www.ijcsi.org/papers/IJCSI-9-4-1-77-84.pdf and tell me your opinion, looking forward to hear from you ? From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 8 04:00:54 2012 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 940D4106564A for ; Wed, 8 Aug 2012 04:00:54 +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 63C708FC0A for ; Wed, 8 Aug 2012 04:00:54 +0000 (UTC) Received: from JRE-MBP-2.local (c-67-180-24-15.hsd1.ca.comcast.net [67.180.24.15]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id q7840kn9032847 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 7 Aug 2012 21:00:47 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5021E468.4070508@freebsd.org> Date: Tue, 07 Aug 2012 21:00:40 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: ali mousa References: <1344385477.41536.YahooMailNeo@web125401.mail.ne1.yahoo.com> In-Reply-To: <1344385477.41536.YahooMailNeo@web125401.mail.ne1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-hackers@freebsd.org" Subject: Re: [maybe spam] Published paper 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, 08 Aug 2012 04:00:54 -0000 On 8/7/12 5:24 PM, ali mousa wrote: > Hi, > > I have recently published a paper related to Operating System, can you please check it out http://www.ijcsi.org/papers/IJCSI-9-4-1-77-84.pdf and tell me your opinion, looking forward to hear from you ? Certainly interesting.. I will read more of it later. > _______________________________________________ > 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 Wed Aug 8 04:07:00 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B3A66106564A for ; Wed, 8 Aug 2012 04:07:00 +0000 (UTC) (envelope-from apeiron@isuckatdomains.net) Received: from isuckatdomains.net (unknown [IPv6:2600:3c01:e000:4::1]) by mx1.freebsd.org (Postfix) with ESMTP id 995EB8FC15 for ; Wed, 8 Aug 2012 04:07:00 +0000 (UTC) Received: from isuckatdomains.isuckatdomains.net (isuckatdomains.net [74.207.243.179]) by isuckatdomains.net (Postfix) with ESMTPSA id 700CE45E69 for ; Wed, 8 Aug 2012 00:07:00 -0400 (EDT) Date: Wed, 8 Aug 2012 00:06:59 -0400 From: Chris Nehren To: freebsd-hackers@freebsd.org Message-ID: <20120808040659.GE32344@isuckatdomains.isuckatdomains.net> Mail-Followup-To: freebsd-hackers@freebsd.org References: <1344385477.41536.YahooMailNeo@web125401.mail.ne1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h56sxpGKRmy85csR" Content-Disposition: inline In-Reply-To: <1344385477.41536.YahooMailNeo@web125401.mail.ne1.yahoo.com> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: Published paper 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, 08 Aug 2012 04:07:00 -0000 --h56sxpGKRmy85csR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 07, 2012 at 17:24:37 -0700 , ali mousa wrote: > Hi, >=20 > I have recently published a paper related to Operating System, can you > please check it out http://www.ijcsi.org/papers/IJCSI-9-4-1-77-84.pdf > and tell me your opinion, looking forward to hear from you ? The DragonFlyBSD project may also find this interesting, because AFAIR one of the reasons Matt forked FreeBSD was due to disagreements in the SMP implementation.=20 --=20 Thanks and best regards, Chris Nehren --h56sxpGKRmy85csR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJQIeXiAAoJEB3ywRGrHAnQFrEP/1BwEtmMNPMrmkUk0XnkXbdU RCkcacOR3VwN/ca2XSsy5/F7ECOlwr4wPXKW7/76UgV1TqLdkB053+Tif+FUdhiR +QW/j1zh/I8WBbO/1d2BSOPr46fAVIpHDmzBFRZmvFi8peeyWS5ex8emqFn8r3Hb szXavOgsU+UPDsZ9xz7l27nHp4fJ98Bt2dC4UUuk42o8nTWGuX5wg/cpN94ABOHn BImSvVTj3dvqz20hYhRPbVodvjKHRY5rCo6dnQEbJJffI+yOCWPMqy/qyYZCVdzu zA8P/KlH7jS30Q2kr4vRf9ioTLtEbjzXQgZPO+aX/IDaKlNm7mx9FqWQ+ifDvzQ/ AZ5RXi5zXpHGJcZwZ0YbutSoVlroSSw9rKowrym1KIC48nKO4wgfUUalO7S0chLh G0jYPDAbvoh+SJexyc/70TI7T1WjLD9H2nx4bqVSEeA1GlapCjTlKi88ASGZEp8j sNz7MaWEEcTPczXIrUzKOyHp744j7FhGs9k94AZNsBHWvpBdlLdaYYVaSmQxcfC9 IrelOU8b3P3vgjHTfDMxA2vCAqEMLvdNzEK0ouBkCnnZfmvNFw4zJpxlPAAao/zn EXrvD+LoSBRbKO2KyTMGtdiglCJnTwWApr//uFYHCm1s/RZ4gabPmh5UWNqLLvjH ZCjIRxEuW2vQ4IT6sxiC =pIJM -----END PGP SIGNATURE----- --h56sxpGKRmy85csR-- From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 8 09:20:53 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 73FCD1065676 for ; Wed, 8 Aug 2012 09:20:53 +0000 (UTC) (envelope-from volodymyr@shcherbyna.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 45B828FC15 for ; Wed, 8 Aug 2012 09:20:53 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so1224934pbb.13 for ; Wed, 08 Aug 2012 02:20:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=oysC0q5CXU28nnvLfWG65NE6QxMaMDIQso8bhrqM2RU=; b=k0mXO433V2L4aJL+o3V7vDfAqhy8Gbi9gUg4VLqSDWj4ePRn505PtqMIq5MHYkG4Hb kjVHdC2sDm0wXMahPkLbBFwIemHeFtVZD5K3msdBjqYLz0MJpms+OnOb4DB4utT1nufl 0GqlGyGgDV8Ewt4KNpKsY42ZYyJZ42OpDvGoCUBz2L6Ep1FZJfHjpe2pSD0SkxR67/g3 pfTj2XfVgdU5zKLWbBXxbtd/IIpZUqLe1+SKCyrNWHIzyPTPYeIdJDxNKL58nZYqTXt5 tScQCHOhfBIX4yghE2Y3nj0MDQ2Z9uMbV1Qq7Nhn7Li3YuAxV7+wV5UEa+wUdtGKWuZA jQFA== MIME-Version: 1.0 Received: by 10.68.191.234 with SMTP id hb10mr34697329pbc.2.1344417652763; Wed, 08 Aug 2012 02:20:52 -0700 (PDT) Received: by 10.68.200.106 with HTTP; Wed, 8 Aug 2012 02:20:52 -0700 (PDT) X-Originating-IP: [128.179.67.95] Date: Wed, 8 Aug 2012 11:20:52 +0200 Message-ID: From: Volodymyr Shcherbyna To: freebsd-hackers@FreeBSD.org X-Gm-Message-State: ALoCoQkrPiKOMhakiFcqjP2t2hAJdVEn9bXH0Jkgce2ZKyYHXIvgUsJ9WGr0JtJOqF9S6DK1Fbqk Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: WinNT compatible drive tagging so that the 3rd stage can provide an accurate mapping of BIOS geometries for disks 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, 08 Aug 2012 09:20:53 -0000 Hello Everyone, Thanks for making FreeBSD so good OS. I would like to contribute to FreeBSD and among high priority tasks I have found the one in the subject of this mail (source: http://doc.ctrlaltdel.ch/freebsd/handbook/contrib.html). Unfortunately, I did not find any details regarding specifications of the task as well as no information regarding accomplished progress in this direction. Can you please share with me this info? I.e., what have been done, what has to be done, and what are the goals? Thanks, -- with best regards, Volodymyr. From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 8 10:02:30 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 26A47106564A for ; Wed, 8 Aug 2012 10:02:30 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id 83C3C8FC0C for ; Wed, 8 Aug 2012 10:02:29 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q78A2P3q004217; Wed, 8 Aug 2012 12:02:25 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id q78A2PX2004214; Wed, 8 Aug 2012 12:02:25 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Wed, 8 Aug 2012 12:02:25 +0200 (CEST) From: Wojciech Puchar To: Volodymyr Shcherbyna In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Wed, 08 Aug 2012 12:02:26 +0200 (CEST) Cc: freebsd-hackers@freebsd.org Subject: Re: WinNT compatible drive tagging so that the 3rd stage can provide an accurate mapping of BIOS geometries for disks 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, 08 Aug 2012 10:02:30 -0000 > Thanks for making FreeBSD so good OS. I would like to contribute to FreeBSD > and among high priority tasks I have found the one in the subject of this > mail (source: http://doc.ctrlaltdel.ch/freebsd/handbook/contrib.html). can you explain what is a problem at all? what exactly doesn't work now at booting? From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 8 11:51:42 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 90E201065672 for ; Wed, 8 Aug 2012 11:51:42 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 00D678FC1A for ; Wed, 8 Aug 2012 11:51:41 +0000 (UTC) Received: by lage12 with SMTP id e12so246576lag.13 for ; Wed, 08 Aug 2012 04:51:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=irrelevant.org; s=irrelevant; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=gSe6N+7O7U4jyjQXIpgeOrAUTk/9PM2esBy0doaD9bU=; b=NZbMuM9odiTy9Z7J0ckJ2ZzEspFDRVotSK5BtuRiKkkeFG3XsVyLmGUKl0NnyvgPQv SYaVcMxQp5rGmtbrCS0VjNkrN8U3nSw51BsIuXXcETDxytP72apF8E0ETWSLC4HNjHcG DLzdY0fMJoIrO2WZ4GIXD066CnZacVKCvBQ6w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=gSe6N+7O7U4jyjQXIpgeOrAUTk/9PM2esBy0doaD9bU=; b=DmSUI5OUFgt4foq+Px2tc3ULDGDn1/MHypNVZvOCu+7fLra5kjbLJyohVj3R1XXrWM lg5na1zauNSV0CG27N4UwBE+SjFcImpBpRUCEWDLjlavyuJXRip0OBWLUawshbvdJG6C hQbFjfCwl5Koh8JU6+XakQgmSijfKEG2V0Zo7MZ+v2ANaaPbI933aCMcS4VdViy3E8hP EAc/nsykzeYvp9K4V1jkjcBSH9C0WW4Szf/lrJ6IQhL0yHSNykxX5jyxhH39WATB6tgO j3adUt7CnWgobuvqMs1p+ylCzFY/h+pXi0irR4dyaUJt/t48iIsyjf34H8L5vS44YKsR Wh3w== MIME-Version: 1.0 Received: by 10.152.111.200 with SMTP id ik8mr17777570lab.15.1344426695044; Wed, 08 Aug 2012 04:51:35 -0700 (PDT) Received: by 10.114.12.229 with HTTP; Wed, 8 Aug 2012 04:51:35 -0700 (PDT) X-Originating-IP: [94.31.26.5] In-Reply-To: References: Date: Wed, 8 Aug 2012 12:51:35 +0100 Message-ID: From: Simon Dick To: Volodymyr Shcherbyna Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmM/EezEGSYxbvlXcM/rszDp7aSPag7asqP5rRJRA8lt7YhWnNNIDMEWVwgzDxbiV2ivyAs Cc: freebsd-hackers@freebsd.org Subject: Re: WinNT compatible drive tagging so that the 3rd stage can provide an accurate mapping of BIOS geometries for disks 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, 08 Aug 2012 11:51:42 -0000 On 8 August 2012 10:20, Volodymyr Shcherbyna wrote: > Hello Everyone, > > Thanks for making FreeBSD so good OS. I would like to contribute to FreeBSD > and among high priority tasks I have found the one in the subject of this > mail (source: http://doc.ctrlaltdel.ch/freebsd/handbook/contrib.html). > > Unfortunately, I did not find any details regarding specifications of the > task as well as no information regarding accomplished progress in this > direction. Can you please share with me this info? I.e., what have been > done, what has to be done, and what are the goals? I think you may want to check the age of that handbook site, especially as the linux emulation part mentions stuff about installing on 2.1-STABLE so the issue you're asking about is probably no longer an issue in the first place. From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 8 20:59:52 2012 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 A6DC5106564A for ; Wed, 8 Aug 2012 20:59:52 +0000 (UTC) (envelope-from danismostlikely@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 58BFA8FC12 for ; Wed, 8 Aug 2012 20:59:52 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so1540401vcb.13 for ; Wed, 08 Aug 2012 13:59:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=l00kD5N93Nq5Betwah33x4UkH2MvnN/0ZemtkJk8iww=; b=vNFnlIQRjilKSC7MWM3ZuEYBL7TSsrP4vA9Kf/lf91JQOnrSjX4gGF1mhncUPYMEOa Kkgsfa5xed4QJ65VUsjHMpgrNbjJUxWyU2eD2K9qLEhfISOGse2JY4PKNhpVWOA1WvMb Yw2eCROItOVefN0x+mnrdQWVYOlF7afVUL5OP3UDpZXpin61TGpAGWJwTs7giWv1VtC4 L+bsphC74JOGVSYC90D9zFVbPvcJdCSBn8AgQ3dR9raOddyky03B2+IpoxSgfYQ70EWK aFjc+z/pf0yV3kmopIWIHhM5QTG+AFfcn3hzXjy65e0HBI/hjA/4479CYlaXznYCtD2T Ky4g== MIME-Version: 1.0 Received: by 10.52.36.129 with SMTP id q1mr1075835vdj.120.1344459591703; Wed, 08 Aug 2012 13:59:51 -0700 (PDT) Received: by 10.58.248.71 with HTTP; Wed, 8 Aug 2012 13:59:51 -0700 (PDT) Date: Wed, 8 Aug 2012 14:59:51 -0600 Message-ID: From: Dan McGregor To: freebsd-hackers@freebsd.org Content-Type: multipart/mixed; boundary=20cf3079b7e260dccd04c6c76427 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Consistent use of lex flags 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, 08 Aug 2012 20:59:52 -0000 --20cf3079b7e260dccd04c6c76427 Content-Type: text/plain; charset=ISO-8859-1 Hi. I was just noticing that mkcsmapper doesn't build with clang. I saw two ways to do this, the first being to #define YY_NO_INPUT, and the other to use the %option noinput lex flag. While there, I decided to explore and I changed a bunch of #defines to the standard lex way of doing things. I thought it would be good if all the code that originated in FreeBSD could be consistent. Thoughts? --20cf3079b7e260dccd04c6c76427 Content-Type: application/octet-stream; name="lex.diff" Content-Disposition: attachment; filename="lex.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h5mwidc60 SW5kZXg6IHVzci5iaW4vY3N1cC90b2tlbi5sCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIHVzci5iaW4vY3N1cC90 b2tlbi5sCShyZXZpc2lvbiAyMzkxNDEpCisrKyB1c3IuYmluL2NzdXAvdG9rZW4ubAkod29ya2lu ZyBjb3B5KQpAQCAtMzUsMTMgKzM1LDEyIEBACiAjaW5jbHVkZSAibWlzYy5oIgogI2luY2x1ZGUg InRva2VuLmgiCiAKLSNkZWZpbmUJWVlfTk9fVU5QVVQKLQogaW50IGxpbmVubyA9IDE7CiAKICV9 CiAKICVvcHRpb24gbm95eXdyYXAKKyVvcHRpb24gbm91bnB1dAogCiAlJQogCkluZGV4OiB1c3Iu YmluL2NvbGxkZWYvTWFrZWZpbGUKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gdXNyLmJpbi9jb2xsZGVmL01ha2Vm aWxlCShyZXZpc2lvbiAyMzkxNDEpCisrKyB1c3IuYmluL2NvbGxkZWYvTWFrZWZpbGUJKHdvcmtp bmcgY29weSkKQEAgLTQsNyArNCw3IEBACiBTUkNTPQlwYXJzZS55IHNjYW4ubCB5LnRhYi5oCiBM RkxBR1M9CS04IC1pCiBDRkxBR1MrPS1JLiAtSSR7LkNVUkRJUn0gLUkkey5DVVJESVJ9Ly4uLy4u L2xpYi9saWJjL2xvY2FsZQotQ0ZMQUdTKz0tRENPTExBVEVfREVCVUcgLURZWV9OT19VTlBVVCAt RFlZX05PX0lOUFVUCitDRkxBR1MrPS1EQ09MTEFURV9ERUJVRwogTERBREQ9CS1sbAogRFBBREQ9 CSR7TElCTH0KIApJbmRleDogdXNyLmJpbi9jb2xsZGVmL3NjYW4ubAo9PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSB1 c3IuYmluL2NvbGxkZWYvc2Nhbi5sCShyZXZpc2lvbiAyMzkxNDEpCisrKyB1c3IuYmluL2NvbGxk ZWYvc2Nhbi5sCSh3b3JraW5nIGNvcHkpCkBAIC00OSw2ICs0OSw4IEBACiAjZW5kaWYgLyogRkxF WF9ERUJVRyAqLwogaW50IHl5bGV4KHZvaWQpOwogJX0KKyVvcHRpb24gbm9pbnB1dAorJW9wdGlv biBub3VucHV0CiAlJQogPElOSVRJQUwsY2hhcm1hcCxuY2hhcixzdWJzLHN1YnMyPlsgXHRdKyAg ICAgIDsKIDxzdWJzMj5cIiAgICAgICAgICAgICAgIHsgcHRyID0gYnVmOyBCRUdJTihzdHJpbmcp OyB9CkluZGV4OiB1c3IuYmluL3hsaW50L2xpbnQxL3NjYW4ubAo9PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSB1c3Iu YmluL3hsaW50L2xpbnQxL3NjYW4ubAkocmV2aXNpb24gMjM5MTQxKQorKysgdXNyLmJpbi94bGlu dC9saW50MS9zY2FuLmwJKHdvcmtpbmcgY29weSkKQEAgLTUyLDcgKzUyLDYgQEAKICNpbmNsdWRl ICJjZ3JhbS5oIgogCiAjZGVmaW5lIENIQVJfTUFTSwkofih+MCA8PCBDSEFSX0JJVCkpCi0jZGVm aW5lIFlZX05PX1VOUFVUCiAKIC8qIEN1cnJlbnQgcG9zaXRpb24gKGl0cyBhbHNvIHVwZGF0ZWQg d2hlbiBhbiBpbmNsdWRlZCBmaWxlIGlzIHBhcnNlZCkgKi8KIHBvc190CWN1cnJfcG9zID0geyAx LCAiIiwgMCB9OwpAQCAtODYsNiArODUsOCBAQAogCiAlfQogCislb3B0aW9uIG5vdW5wdXQKKwog TAlbX0EtWmEtel0KIEQJWzAtOV0KIE5aRAlbMS05XQpJbmRleDogdXNyLmJpbi9hci9hY3BsZXgu bAo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09Ci0tLSB1c3IuYmluL2FyL2FjcGxleC5sCShyZXZpc2lvbiAyMzkxNDEpCisr KyB1c3IuYmluL2FyL2FjcGxleC5sCSh3b3JraW5nIGNvcHkpCkBAIC0zNiw4ICszNiw2IEBACiAK ICNpbmNsdWRlICJ5LnRhYi5oIgogCi0jZGVmaW5lIFlZX05PX1VOUFVUCi0jZGVmaW5lIFlZX05P X0lOUFVUCiBpbnQgbGluZW5vID0gMTsKIAogaW50CXl5bGV4KHZvaWQpOwpAQCAtNDUsNiArNDMs OCBAQAogJX0KIAogJW9wdGlvbiBub3l5d3JhcAorJW9wdGlvbiBub2lucHV0Cislb3B0aW9uIG5v dW5wdXQKIAogJSUKIApJbmRleDogdXNyLmJpbi9iYy9zY2FuLmwKPT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gdXNy LmJpbi9iYy9zY2FuLmwJKHJldmlzaW9uIDIzOTE0MSkKKysrIHVzci5iaW4vYmMvc2Nhbi5sCSh3 b3JraW5nIGNvcHkpCkBAIC00NiwxMyArNDYsMTMgQEAKIHN0YXRpYyB2b2lkCSBhZGRfc3RyKGNv bnN0IGNoYXIgKik7CiBzdGF0aWMgaW50CSBiY195eWlucHV0KGNoYXIgKiwgaW50KTsKIAotI2Rl ZmluZSBZWV9OT19JTlBVVAogI3VuZGVmIFlZX0lOUFVUCiAjZGVmaW5lIFlZX0lOUFVUKGJ1Zixy ZXR2YWwsbWF4KSBcCiAJKHJldHZhbCA9IGJjX3l5aW5wdXQoYnVmLCBtYXgpKQogJX0KIAogJW9w dGlvbiBhbHdheXMtaW50ZXJhY3RpdmUKKyVvcHRpb24gbm9pbnB1dAogCiBESUdJVAkJWzAtOUEt Rl0KIEFMUEhBCQlbYS16X10KSW5kZXg6IHVzci5iaW4vbWtjc21hcHBlci9sZXgubAo9PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09Ci0tLSB1c3IuYmluL21rY3NtYXBwZXIvbGV4LmwJKHJldmlzaW9uIDIzOTE0MSkKKysrIHVz ci5iaW4vbWtjc21hcHBlci9sZXgubAkod29ya2luZyBjb3B5KQpAQCAtNDMsNiArNDMsNyBAQAog CiBpbnQgbGluZV9udW1iZXIgPSAxOwogJX0KKyVvcHRpb24Jbm9pbnB1dAogJW9wdGlvbglub3Vu cHV0CiAKICV4CUNPTU1FTlQKSW5kZXg6IHVzci5zYmluL3JyZW51bWQvbGV4ZXIubAo9PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09Ci0tLSB1c3Iuc2Jpbi9ycmVudW1kL2xleGVyLmwJKHJldmlzaW9uIDIzOTE0MSkKKysrIHVz ci5zYmluL3JyZW51bWQvbGV4ZXIubAkod29ya2luZyBjb3B5KQpAQCAtMzIsOCArMzIsNiBAQAog ICovCiAKICV7Ci0jZGVmaW5lIFlZX05PX1VOUFVUCi0KICNpbmNsdWRlIDxzeXMvcGFyYW0uaD4K ICNpbmNsdWRlIDxzeXMvaW9jdGwuaD4KICNpbmNsdWRlIDxzeXMvc29ja2V0Lmg+CkBAIC02NCw2 ICs2Miw4IEBACiBpbnQgeXlsZXgodm9pZCk7CiAlfQogCislb3B0aW9uIG5vdW5wdXQKKwogLyog Y29tbW9uIHNlY3Rpb24gKi8KIG5sCQlcbgogd3MJCVsgXHRdKwpJbmRleDogdXNyLnNiaW4va2Jk Y29udHJvbC9sZXgubAo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSB1c3Iuc2Jpbi9rYmRjb250cm9sL2xleC5sCShy ZXZpc2lvbiAyMzkxNDEpCisrKyB1c3Iuc2Jpbi9rYmRjb250cm9sL2xleC5sCSh3b3JraW5nIGNv cHkpCkBAIC0zMSwxMSArMzEsMTIgQEAKICV7CiAKICNpbmNsdWRlICJsZXguaCIKLSNkZWZpbmUg WVlfTk9fVU5QVVQKLSNkZWZpbmUgWVlfTk9fSU5QVVQKIAogJX0KIAorJW9wdGlvbiBub2lucHV0 Cislb3B0aW9uIG5vdW5wdXQKKwogRAlbMC05XQogWAlbMC05YS1mQS1GXQogQQkuCkluZGV4OiB1 c3Iuc2Jpbi9qYWlsL2phaWxsZXgubAo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSB1c3Iuc2Jpbi9qYWlsL2phaWxs ZXgubAkocmV2aXNpb24gMjM5MTQxKQorKysgdXNyLnNiaW4vamFpbC9qYWlsbGV4LmwJKHdvcmtp bmcgY29weSkKQEAgLTM2LDkgKzM2LDYgQEAKICNpbmNsdWRlICJqYWlscC5oIgogI2luY2x1ZGUg InkudGFiLmgiCiAKLSNkZWZpbmUgWVlfTk9fSU5QVVQKLSNkZWZpbmUgWVlfTk9fVU5QVVQKLQog ZXh0ZXJuIGludCB5eW5lcnJzOwogCiBzdGF0aWMgc3NpemVfdCB0ZXh0Mmx2YWwoc2l6ZV90IHRy aW1sLCBzaXplX3QgdHJpbXIsIGludCB0b3Zhcik7CkBAIC00Nyw2ICs0NCw5IEBACiBzdGF0aWMg aW50IGxpbmVubyA9IDE7CiAlfQogCislb3B0aW9uIG5vaW5wdXQKKyVvcHRpb24gbm91bnB1dAor CiAlc3RhcnQgXyBEUQogCiAlJQpJbmRleDogdXNyLnNiaW4vbmRpc2N2dC9pbmYtdG9rZW4ubAo9 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09Ci0tLSB1c3Iuc2Jpbi9uZGlzY3Z0L2luZi10b2tlbi5sCShyZXZpc2lvbiAyMzkx NDEpCisrKyB1c3Iuc2Jpbi9uZGlzY3Z0L2luZi10b2tlbi5sCSh3b3JraW5nIGNvcHkpCkBAIC00 Myw4ICs0Myw2IEBACiAjaW5jbHVkZSAieS50YWIuaCIKIAogaW50IGxpbmVubyA9IDE7Ci0jZGVm aW5lIFlZX05PX1VOUFVUCi0jZGVmaW5lIFlZX05PX0lOUFVUCiAKIGludCB5eWxleCh2b2lkKTsK IHZvaWQgeXllcnJvcihjb25zdCBjaGFyICopOwpAQCAtNTksNiArNTcsOSBAQAogCiAlfQogCisl b3B0aW9uIG5vaW5wdXQKKyVvcHRpb24gbm91bnB1dAorCiAlJQogCiBbIFx0XSsJCQk7CkluZGV4 OiB1c3Iuc2Jpbi9hcG1kL2FwbWRsZXgubAo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSB1c3Iuc2Jpbi9hcG1kL2Fw bWRsZXgubAkocmV2aXNpb24gMjM5MTQxKQorKysgdXNyLnNiaW4vYXBtZC9hcG1kbGV4LmwJKHdv cmtpbmcgY29weSkKQEAgLTM2LDE0ICszNiwxMyBAQAogI2luY2x1ZGUgImFwbWQuaCIKICNpbmNs dWRlICJ5LnRhYi5oIgogCi0vKiBXZSBkb24ndCBuZWVkIGl0LCBhdm9pZCB0aGUgd2FybmluZy4g Ki8KLSNkZWZpbmUgWVlfTk9fVU5QVVQKLSNkZWZpbmUgWVlfTk9fSU5QVVQKLQogaW50IGxpbmVu bzsKIGludCBmaXJzdF90aW1lOwogJX0KIAorJW9wdGlvbiBub2lucHV0Cislb3B0aW9uIG5vdW5w dXQKKwogJXMgVE9QCiAKICUlCkluZGV4OiB1c3Iuc2Jpbi9jb25maWcvbGFuZy5sCj09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT0KLS0tIHVzci5zYmluL2NvbmZpZy9sYW5nLmwJKHJldmlzaW9uIDIzOTE0MSkKKysrIHVzci5z YmluL2NvbmZpZy9sYW5nLmwJKHdvcmtpbmcgY29weSkKQEAgLTM4LDkgKzM4LDYgQEAKICNpbmNs dWRlICJ5LnRhYi5oIgogI2luY2x1ZGUgImNvbmZpZy5oIgogCi0jZGVmaW5lIFlZX05PX1VOUFVU Ci0jZGVmaW5lIFlZX05PX0lOUFVUCi0KIC8qCiAgKiBEYXRhIGZvciByZXR1cm5pbmcgdG8gcHJl dmlvdXMgZmlsZXMgZnJvbSBpbmNsdWRlIGZpbGVzLgogICovCkBAIC05Nyw2ICs5NCwxMCBAQAog aW50IHl5ZXJyb3IoY29uc3QgY2hhciAqKTsKIAogJX0KKworJW9wdGlvbiBub2lucHV0Cislb3B0 aW9uIG5vdW5wdXQKKwogSUQJW0EtWmEtel9dWy1BLVphLXpfMC05XSoKIFBBVEgJWy4vXVstLy4l XkEtWmEtel8wLTldKwogJVNUQVJUIFRPRU9MCkluZGV4OiBsaWIvbGliYy9uZXQvbnNsZXhlci5s Cj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT0KLS0tIGxpYi9saWJjL25ldC9uc2xleGVyLmwJKHJldmlzaW9uIDIzOTE0MSkK KysrIGxpYi9saWJjL25ldC9uc2xleGVyLmwJKHdvcmtpbmcgY29weSkKQEAgLTUzLDEyICs1Mywx MSBAQAogCiAjaW5jbHVkZSAibnNwYXJzZXIuaCIKIAotI2RlZmluZQlZWV9OT19JTlBVVAotI2Rl ZmluZSBZWV9OT19VTlBVVAotCiAlfQogCiAlb3B0aW9uIHl5bGluZW5vCislb3B0aW9uIG5vaW5w dXQKKyVvcHRpb24gbm91bnB1dAogCiBCTEFOSwkJWyBcdF0KIENSCQlcbgpJbmRleDogc2Jpbi9k ZXZkL3Rva2VuLmwKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PQotLS0gc2Jpbi9kZXZkL3Rva2VuLmwJKHJldmlzaW9uIDIz OTE0MSkKKysrIHNiaW4vZGV2ZC90b2tlbi5sCSh3b3JraW5nIGNvcHkpCkBAIC0zNyw4ICszNyw2 IEBACiAjaW5jbHVkZSAieS50YWIuaCIKIAogaW50IGxpbmVubyA9IDE7Ci0jZGVmaW5lIFlZX05P X1VOUFVUCi0jZGVmaW5lIFlZX05PX0lOUFVUCiAKIHN0YXRpYyB2b2lkCiB1cGRhdGVfbGluZW5v KGNvbnN0IGNoYXIgKmNwKQpAQCAtNTAsNiArNDgsOSBAQAogCiAlfQogCislb3B0aW9uIG5vaW5w dXQKKyVvcHRpb24gbm91bnB1dAorCiAlJQogCiBbIFx0XSsJCQk7CkluZGV4OiBzYmluL2hhc3Rj dGwvTWFrZWZpbGUKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PQotLS0gc2Jpbi9oYXN0Y3RsL01ha2VmaWxlCShyZXZpc2lv biAyMzkxNDEpCisrKyBzYmluL2hhc3RjdGwvTWFrZWZpbGUJKHdvcmtpbmcgY29weSkKQEAgLTI3 LDkgKzI3LDYgQEAKIC5pZiAke01LX0lORVQ2X1NVUFBPUlR9ICE9ICJubyIKIENGTEFHUys9LURJ TkVUNgogLmVuZGlmCi0jIFRoaXMgaXMgbmVlZGVkIHRvIGhhdmUgV0FSTlMgPiAxLgotQ0ZMQUdT Kz0tRFlZX05PX1VOUFVUCi1DRkxBR1MrPS1EWVlfTk9fSU5QVVQKIAogRFBBREQ9CSR7TElCTH0g JHtMSUJVVElMfQogTERBREQ9CS1sbCAtbHV0aWwKSW5kZXg6IHNiaW4vc2V0a2V5L3Rva2VuLmwK PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PQotLS0gc2Jpbi9zZXRrZXkvdG9rZW4ubAkocmV2aXNpb24gMjM5MTQxKQorKysg c2Jpbi9zZXRrZXkvdG9rZW4ubAkod29ya2luZyBjb3B5KQpAQCAtNjUsNiArNjUsOCBAQAogaW50 IHl5cGFyc2Uodm9pZCk7CiAlfQogCislb3B0aW9uIG5vdW5wdXQKKwogLyogY29tbW9uIHNlY3Rp b24gKi8KIG5sCQlcbgogd3MJCVsgXHRdKwpJbmRleDogc2Jpbi9zZXRrZXkvTWFrZWZpbGUKPT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PQotLS0gc2Jpbi9zZXRrZXkvTWFrZWZpbGUJKHJldmlzaW9uIDIzOTE0MSkKKysrIHNi aW4vc2V0a2V5L01ha2VmaWxlCSh3b3JraW5nIGNvcHkpCkBAIC01MCw3ICs1MCw3IEBACiAKIFNS Q1MrPQl5LnRhYi5oCiB5LnRhYi5oOiBwYXJzZS55Ci1DRkxBR1MrPSAtRElQU0VDX0RFQlVHIC1E WVlfTk9fVU5QVVQKK0NGTEFHUys9IC1ESVBTRUNfREVCVUcKIC5pZiAke01LX0lORVQ2X1NVUFBP UlR9ICE9ICJubyIKIENGTEFHUys9IC1ESU5FVDYKIC5lbmRpZgo= --20cf3079b7e260dccd04c6c76427-- From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 8 22:40:57 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3CFC0106564A; Wed, 8 Aug 2012 22:40:57 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id EACF88FC16; Wed, 8 Aug 2012 22:40:56 +0000 (UTC) Received: by obbun3 with SMTP id un3so2352336obb.13 for ; Wed, 08 Aug 2012 15:40:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SA8jYT5RjN+GL32oLqZTmNYucduDo7Fve58QLG6VIiI=; b=i31yHpuc98DkN9g0hSsAIF+L83/78uzFcSIlt+fuIqIYLPjuFgHGJTTHsIQByIj5vN bqKUiisKWss5Pl+xrXZ+NKjfL6zCNuUzqgkOSV1/WI0pcg5ZYsr7shGsA4wE3OFKBxFB 7v7kpiVrTd3jIX8IM5SdUhWNT72VDaTUzX12GJF033cegFCfPNdnl84Exez+dGr3Tcs4 tqi+vDWZn5cFJ7r4lRnZqm1++Ot2+e3H8qwd2Coi7N/Zgrwl+LJTidMONZ1t2AfVlJ2R PRQdfZhBpFy9IkGwQcI49UuK67Rz4DDwOlnfT/ws3VGROrJjRHO6Cd1RKFr0zAYzeeZP cYuw== MIME-Version: 1.0 Received: by 10.60.3.194 with SMTP id e2mr32841684oee.1.1344465656253; Wed, 08 Aug 2012 15:40:56 -0700 (PDT) Received: by 10.76.84.7 with HTTP; Wed, 8 Aug 2012 15:40:56 -0700 (PDT) In-Reply-To: References: Date: Wed, 8 Aug 2012 15:40:56 -0700 Message-ID: From: Garrett Cooper To: Dan McGregor Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, Gabor Kovesdan Subject: Re: Consistent use of lex flags 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, 08 Aug 2012 22:40:57 -0000 On Wed, Aug 8, 2012 at 1:59 PM, Dan McGregor wrote: > Hi. > > I was just noticing that mkcsmapper doesn't build with clang. I saw two > ways to do this, the first being to #define YY_NO_INPUT, and the other to > use the %option noinput lex flag. > > While there, I decided to explore and I changed a bunch of #defines to the > standard lex way of doing things. I thought it would be good if all the > code that originated in FreeBSD could be consistent. > > Thoughts? Probably should CC gabor@ next time (done this time) and maybe involve the NetBSD folks as this code is sort of upstreamed from them IIRC. Cheers! -Garrett From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 9 05:24:29 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C4BF106564A; Thu, 9 Aug 2012 05:24:29 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id BB9748FC08; Thu, 9 Aug 2012 05:24:28 +0000 (UTC) Received: from server.rulingia.com (c220-239-247-45.belrs5.nsw.optusnet.com.au [220.239.247.45]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q795OLQU055369 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Aug 2012 15:24:22 +1000 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q795OFZF017310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 15:24:15 +1000 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q795OFux017309; Thu, 9 Aug 2012 15:24:15 +1000 (EST) (envelope-from peter) Date: Thu, 9 Aug 2012 15:24:15 +1000 From: Peter Jeremy To: John Baldwin Message-ID: <20120809052415.GB13662@server.rulingia.com> References: <20120703111753.GB72292@server.rulingia.com> <20120708110516.GA38312@server.rulingia.com> <201207120826.05577.jhb@freebsd.org> <201208061016.13065.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline In-Reply-To: <201208061016.13065.jhb@freebsd.org> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org Subject: Re: contigmalloc() breaking Xorg 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, 09 Aug 2012 05:24:29 -0000 --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Aug-06 10:16:13 -0400, John Baldwin wrote: >On Thursday, July 12, 2012 8:26:05 am John Baldwin wrote: >> However, rather add a wiredmalloc(), I think you should just have=20 >> bus_dmamem_alloc() call kmem_alloc_attr() directly in this case. One of= the=20 >> things I've been meaning to add to bus_dma is a way to allocate other me= mory=20 >> types (e.g. WC memory), and in that case it would be best to just call= =20 >> kmem_alloc_attr() directly instead. > >After my recent changes, I think this would do the above. What do >you think of this, and if it looks ok, can you test it? > >Index: busdma_machdep.c >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >--- busdma_machdep.c (revision 239020) >+++ busdma_machdep.c (working copy) >@@ -533,13 +533,14 @@ bus_dmamem_alloc(bus_dma_tag_t dmat, void** vaddr, > dmat->lowaddr >=3D ptoa((vm_paddr_t)Maxmem) && > attr =3D=3D VM_MEMATTR_DEFAULT) { > *vaddr =3D malloc(dmat->maxsize, M_DEVBUF, mflags); >+ } else if (dmat->nsegments >=3D btoc(dmat->maxsize) && >+ dmat->alignment <=3D PAGE_SIZE && >+ (dmat->boundary =3D=3D 0 || dmat->boundary >=3D dmat->lowaddr)) { >+ /* Page-based multi-segment allocations allowed */ >+ *vaddr =3D (void *)kmem_alloc_attr(kernel_map, dmat->maxsize, >+ mflags, 0ul, dmat->lowaddr, attr); >+ *mapp =3D &contig_dmamap; > } else { >- /* >- * XXX Use Contigmalloc until it is merged into this facility >- * and handles multi-seg allocations. Nobody is doing >- * multi-seg allocations yet though. >- * XXX Certain AGP hardware does. >- */ > *vaddr =3D (void *)kmem_alloc_contig(kernel_map, dmat->maxsize, > mflags, 0ul, dmat->lowaddr, dmat->alignment ? > dmat->alignment : 1ul, dmat->boundary, attr); I've tried this on a -current/amd64 box (r239130) that has 2GB RAM and ZFS. I looped tar(1)s of several bits of /usr/src whilst doing a "-j2 buildworld" and killing X every 30s for about 7 hours. (The Xserver grabs a 8192-page dmamem tag when it starts). It all seemed to work OK. I haven't tried it on the box where I originally saw the problem because that's running 8.x. I'll have a look at backporting your and alc@'s fixes when I get some spare time. --=20 Peter Jeremy --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAjSX8ACgkQ/opHv/APuId4XgCgk/87aZt8DKG3M4VAGzFiXV3p P64AoLgImj0PZK47zw6vJ6bH67lkjmgP =E/cO -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 9 10:56:51 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1FD6C106566C; Thu, 9 Aug 2012 10:56:51 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay04.stack.nl [IPv6:2001:610:1108:5010::107]) by mx1.freebsd.org (Postfix) with ESMTP id A83FF8FC12; Thu, 9 Aug 2012 10:56:50 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 592F81DD5BC; Thu, 9 Aug 2012 12:56:49 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 31ADE2847B; Thu, 9 Aug 2012 12:56:49 +0200 (CEST) Date: Thu, 9 Aug 2012 12:56:49 +0200 From: Jilles Tjoelker To: Konstantin Belousov , davidxu@freebsd.org Message-ID: <20120809105648.GA79814@stack.nl> References: <20120730102408.GA19983@stack.nl> <20120730105303.GU2676@deviant.kiev.zoral.com.ua> <20120805215432.GA28704@stack.nl> <20120806082535.GI2676@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120806082535.GI2676@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org Subject: Re: system() using vfork() or posix_spawn() and libthr 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, 09 Aug 2012 10:56:51 -0000 On Mon, Aug 06, 2012 at 11:25:35AM +0300, Konstantin Belousov wrote: > On Sun, Aug 05, 2012 at 11:54:32PM +0200, Jilles Tjoelker wrote: > > On Mon, Jul 30, 2012 at 01:53:03PM +0300, Konstantin Belousov wrote: > > > On Mon, Jul 30, 2012 at 12:24:08PM +0200, Jilles Tjoelker wrote: > > > > People sometimes use system() from large address spaces where it would > > > > improve performance greatly to use vfork() instead of fork(). > > > > A simple approach is to change fork() to vfork(), although I have not > > > > tried this. It seems safe enough to use sigaction and sigprocmask system > > > > calls in the vforked process. > > > > Alternatively, we can have posix_spawn() do the vfork() with signal > > > > changes. This avoids possible whining from compilers and static > > > > analyzers about using vfork() in system.c. However, I do not like the > > > > tricky code for signals and that it adds lines of code. > > > > This is lightly tested. > > > It is interesting to note that for some time our vfork(2) no longer > > > stops the whole forked process (parent), only the forking thread is > > > waiting for the child exit or exec. I am not sure is this point > > > important for system(3), but determined code can notice the difference > > > from the fork->vfork switch. > > Neither fork nor vfork call thread_single(SINGLE_BOUNDARY), so this is > > not a difference. > It is the difference, because vforked child shares parent address space. > > Thread singling may be noticeable from a failing execve() (but only in > > the process doing execve()) and in the rare case of rfork() without > > RFPROC. > No, other running threads in parent affect vforked child till exec or exit. > In fact, I would classify this as bug, but not a serious one. There are some ugly ways this parallel execution is depended on. If the vforked child calls sigaction() while another thread is also in sigaction() for that signal, the vforked child needs to wait for the other thread to release the lock. This uses a per-process lock to synchronize threads in different processes, which may not work properly. If the vforked child is killed (such as by SIGKILL) while holding the lock, the parent is not killed but its _thr_sigact is damaged. These problems could be avoided in libthr by skipping the lock in _sigaction() if a signal action is being set to SIG_DFL or SIG_IGN and the old action is not queried. In those cases, _thr_sigact is not touched so no lock is required. This change also helps applications, provided they call sigaction() and not signal(). Alternatively, posix_spawn() and system() could use the sigaction system call directly, bypassing libthr (if present). However, this will not help applications that call vfork() and sigaction() themselves (such as a shell that wants to implement ... & using vfork()). posix_spawn() likely still needs some adjustment so that having it reset all signals (sigfillset()) to the default action will not cause it to [EINVAL] because libthr does not allow changing SIGTHR's disposition. Index: lib/libthr/thread/thr_sig.c =================================================================== --- lib/libthr/thread/thr_sig.c (revision 238970) +++ lib/libthr/thread/thr_sig.c (working copy) @@ -519,8 +519,16 @@ return (-1); } - if (act) + if (act) { newact = *act; + /* + * Short-circuit cases where we do not touch _thr_sigact. + * This allows performing these safely in a vforked child. + */ + if ((newact.sa_handler == SIG_DFL || + newact.sa_handler == SIG_IGN) && oact == NULL) + return (__sys_sigaction(sig, &newact, NULL)); + } __sys_sigprocmask(SIG_SETMASK, &_thr_maskset, &oldset); _thr_rwl_wrlock(&_thr_sigact[sig-1].lock); -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 9 11:09:06 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 988BE106566B; Thu, 9 Aug 2012 11:09:06 +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 EE4788FC1B; Thu, 9 Aug 2012 11:09:05 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q79B93QN070775; Thu, 9 Aug 2012 14:09:03 +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.5/8.14.5) with ESMTP id q79B8pgQ002954; Thu, 9 Aug 2012 14:08:51 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q79B8o6o002953; Thu, 9 Aug 2012 14:08:50 +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: Thu, 9 Aug 2012 14:08:50 +0300 From: Konstantin Belousov To: Jilles Tjoelker Message-ID: <20120809110850.GA2425@deviant.kiev.zoral.com.ua> References: <20120730102408.GA19983@stack.nl> <20120730105303.GU2676@deviant.kiev.zoral.com.ua> <20120805215432.GA28704@stack.nl> <20120806082535.GI2676@deviant.kiev.zoral.com.ua> <20120809105648.GA79814@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Content-Disposition: inline In-Reply-To: <20120809105648.GA79814@stack.nl> 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=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham 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, davidxu@freebsd.org Subject: Re: system() using vfork() or posix_spawn() and libthr 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, 09 Aug 2012 11:09:06 -0000 --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 09, 2012 at 12:56:49PM +0200, Jilles Tjoelker wrote: > On Mon, Aug 06, 2012 at 11:25:35AM +0300, Konstantin Belousov wrote: > > No, other running threads in parent affect vforked child till exec or e= xit. > > In fact, I would classify this as bug, but not a serious one. >=20 > There are some ugly ways this parallel execution is depended on. If the > vforked child calls sigaction() while another thread is also in > sigaction() for that signal, the vforked child needs to wait for the > other thread to release the lock. >=20 > This uses a per-process lock to synchronize threads in different > processes, which may not work properly. >=20 > If the vforked child is killed (such as by SIGKILL) while holding the > lock, the parent is not killed but its _thr_sigact is damaged. >=20 > These problems could be avoided in libthr by skipping the lock in > _sigaction() if a signal action is being set to SIG_DFL or SIG_IGN and > the old action is not queried. In those cases, _thr_sigact is not > touched so no lock is required. This change also helps applications, > provided they call sigaction() and not signal(). >=20 > Alternatively, posix_spawn() and system() could use the sigaction system > call directly, bypassing libthr (if present). However, this will not > help applications that call vfork() and sigaction() themselves (such as > a shell that wants to implement ... & using vfork()). Third alternative, which seems to be even better, is to restore single-threading of the parent for vfork(). --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAjmkIACgkQC3+MBN1Mb4h/EwCdELtNIDK8mcLxy9Q/FCGp4VU6 ZrwAnRL+3P0PLyUZhhtG64UJS2qY0aug =hYJB -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j-- From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 9 14:44:56 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 781411065673 for ; Thu, 9 Aug 2012 14:44:56 +0000 (UTC) (envelope-from resit.sahin@inforcept.com) Received: from nusret.endersys.com (nusret.endersys.com [77.92.112.244]) by mx1.freebsd.org (Postfix) with ESMTP id F31E48FC12 for ; Thu, 9 Aug 2012 14:44:55 +0000 (UTC) Received: (surmail 4359 invoked from network); 9 Aug 2012 14:35:31 -0000 Received: from asy62.asy144.tellcom.com.tr (HELO AuthenticatedHELO) (resit.sahin@inforcept.com@[Authenticated]) (envelope-sender ) by nusret.endersys.com (surmail-1.0) with SMTP for ; 9 Aug 2012 14:35:31 -0000 Message-ID: <5023CB54.4090701@inforcept.com> Date: Thu, 09 Aug 2012 17:38:12 +0300 From: Resit Sahin Organization: Endersys-Inforcept User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: NUMA support in FreeBSD 9.0 / 9.1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: resit.sahin@inforcept.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Aug 2012 14:44:56 -0000 Hello, Does FreeBSD 9.0 or 9.1 "fully" support NUMA Architectures? It is said that FreeBSD 9.0 has an initial NUMA support but is this initial support enough for getting major performance gains? Regards, Resit Sahin From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 9 16:12:49 2012 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 95E071065672 for ; Thu, 9 Aug 2012 16:12:49 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 537D78FC0A for ; Thu, 9 Aug 2012 16:12:48 +0000 (UTC) Received: by obbun3 with SMTP id un3so1123160obb.13 for ; Thu, 09 Aug 2012 09:12:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=nKXzlXMRuDCxSrHsHG5Bnvr9LxuMtVmW9ErQI21B6lI=; b=HEf4dZN4p1+d5e5lPXXpzfeuugoHD9K6PM2ObYJbXws0Ux29VtlbEKiOeMGYTogq0N H8XMlkUaEV4fKNGOVkd+3rygVGmjPxMKLnY7RMzrRO9lYEBwFXs04mOL0dbYpnWA/p2Z 1Xq81t+zym6Xesy+Hp/ecDn4S6mZAlq0a/n7FSLqU2mmILchniKQx7nByG5crVU7xIzj /kk14fzYodF5SKoXMbHk7gsx1ujcjwtPajGYfqX+xXAxZI77pla3OwpN1fFHahlF9yC7 4YQI7SHIgMlr7/U+N23O6edTIZpbgbNdGeYFj73IfNoUAOmpEIgkWqlevLZjqK67xrRX Jqgg== Received: by 10.182.53.103 with SMTP id a7mr36625014obp.3.1344528768366; Thu, 09 Aug 2012 09:12:48 -0700 (PDT) Received: from [10.30.101.53] ([209.117.142.2]) by mx.google.com with ESMTPS id bp7sm1159272obc.12.2012.08.09.09.12.45 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Aug 2012 09:12:47 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Thu, 9 Aug 2012 10:12:44 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <538F7D01-690B-46A3-982D-F2BF9EFE8621@bsdimp.com> References: To: Dan McGregor X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQmv0AQrnz3Slsc9ClSnZW/NiKGQZMa66LA/mUqKRmzlkc5Wb/TqCgzoxwF8rfn/ufF6tMMv Cc: freebsd-hackers@freebsd.org Subject: Re: Consistent use of lex flags 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, 09 Aug 2012 16:12:49 -0000 All these changes look good. Since they aren't changes to lex itself, = but how the base uses standard lex interfaces, I'd say we should just = commit it. Warner On Aug 8, 2012, at 2:59 PM, Dan McGregor wrote: > Hi. >=20 > I was just noticing that mkcsmapper doesn't build with clang. I saw = two > ways to do this, the first being to #define YY_NO_INPUT, and the other = to > use the %option noinput lex flag. >=20 > While there, I decided to explore and I changed a bunch of #defines to = the > standard lex way of doing things. I thought it would be good if all = the > code that originated in FreeBSD could be consistent. >=20 > Thoughts? > _______________________________________________ > 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 Fri Aug 10 02:16:03 2012 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 0713A106564A for ; Fri, 10 Aug 2012 02:16:03 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E24318FC08; Fri, 10 Aug 2012 02:16:02 +0000 (UTC) Received: from xyf.my.dom (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7A2G06x078086; Fri, 10 Aug 2012 02:16:01 GMT (envelope-from davidxu@freebsd.org) Message-ID: <50246EE4.9090409@freebsd.org> Date: Fri, 10 Aug 2012 10:16:04 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:9.0) Gecko/20111229 Thunderbird/9.0 MIME-Version: 1.0 To: Jilles Tjoelker References: <20120730102408.GA19983@stack.nl> <20120730105303.GU2676@deviant.kiev.zoral.com.ua> <20120805215432.GA28704@stack.nl> <20120806082535.GI2676@deviant.kiev.zoral.com.ua> <20120809105648.GA79814@stack.nl> In-Reply-To: <20120809105648.GA79814@stack.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Konstantin Belousov , freebsd-hackers@freebsd.org Subject: Re: system() using vfork() or posix_spawn() and libthr 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, 10 Aug 2012 02:16:03 -0000 On 2012/08/09 18:56, Jilles Tjoelker wrote: > On Mon, Aug 06, 2012 at 11:25:35AM +0300, Konstantin Belousov wrote: >> On Sun, Aug 05, 2012 at 11:54:32PM +0200, Jilles Tjoelker wrote: >>> On Mon, Jul 30, 2012 at 01:53:03PM +0300, Konstantin Belousov wrote: >>>> On Mon, Jul 30, 2012 at 12:24:08PM +0200, Jilles Tjoelker wrote: >>>>> People sometimes use system() from large address spaces where it would >>>>> improve performance greatly to use vfork() instead of fork(). > >>>>> A simple approach is to change fork() to vfork(), although I have not >>>>> tried this. It seems safe enough to use sigaction and sigprocmask system >>>>> calls in the vforked process. > >>>>> Alternatively, we can have posix_spawn() do the vfork() with signal >>>>> changes. This avoids possible whining from compilers and static >>>>> analyzers about using vfork() in system.c. However, I do not like the >>>>> tricky code for signals and that it adds lines of code. > >>>>> This is lightly tested. > >>>> It is interesting to note that for some time our vfork(2) no longer >>>> stops the whole forked process (parent), only the forking thread is >>>> waiting for the child exit or exec. I am not sure is this point >>>> important for system(3), but determined code can notice the difference >>>> from the fork->vfork switch. > >>> Neither fork nor vfork call thread_single(SINGLE_BOUNDARY), so this is >>> not a difference. >> It is the difference, because vforked child shares parent address space. > >>> Thread singling may be noticeable from a failing execve() (but only in >>> the process doing execve()) and in the rare case of rfork() without >>> RFPROC. > >> No, other running threads in parent affect vforked child till exec or exit. >> In fact, I would classify this as bug, but not a serious one. > > There are some ugly ways this parallel execution is depended on. If the > vforked child calls sigaction() while another thread is also in > sigaction() for that signal, the vforked child needs to wait for the > other thread to release the lock. > > This uses a per-process lock to synchronize threads in different > processes, which may not work properly. > > If the vforked child is killed (such as by SIGKILL) while holding the > lock, the parent is not killed but its _thr_sigact is damaged. > > These problems could be avoided in libthr by skipping the lock in > _sigaction() if a signal action is being set to SIG_DFL or SIG_IGN and > the old action is not queried. In those cases, _thr_sigact is not > touched so no lock is required. This change also helps applications, > provided they call sigaction() and not signal(). > > Alternatively, posix_spawn() and system() could use the sigaction system > call directly, bypassing libthr (if present). However, this will not > help applications that call vfork() and sigaction() themselves (such as > a shell that wants to implement ...& using vfork()). > > posix_spawn() likely still needs some adjustment so that having it reset > all signals (sigfillset()) to the default action will not cause it to > [EINVAL] because libthr does not allow changing SIGTHR's disposition. > > Index: lib/libthr/thread/thr_sig.c > =================================================================== > --- lib/libthr/thread/thr_sig.c (revision 238970) > +++ lib/libthr/thread/thr_sig.c (working copy) > @@ -519,8 +519,16 @@ > return (-1); > } > > - if (act) > + if (act) { > newact = *act; > + /* > + * Short-circuit cases where we do not touch _thr_sigact. > + * This allows performing these safely in a vforked child. > + */ > + if ((newact.sa_handler == SIG_DFL || > + newact.sa_handler == SIG_IGN)&& oact == NULL) > + return (__sys_sigaction(sig,&newact, NULL)); > + } > > __sys_sigprocmask(SIG_SETMASK,&_thr_maskset,&oldset); > _thr_rwl_wrlock(&_thr_sigact[sig-1].lock); > Your patch is better than nothing, I don't object. The problem is visble to you, but there is also invisible user - rtld. If a symbol is never used in parent process, but now it is used in a vforked child, the rtld will be involved, if the child is killed, the rtld's data structure may be in inconsistent state, such as locking or link list etcs... I think this problem might be a non-fixable problem. From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 07:41:58 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4836106566B for ; Fri, 10 Aug 2012 07:41:58 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 21CA88FC0A for ; Fri, 10 Aug 2012 07:41:57 +0000 (UTC) Received: from OctaHexa64-MkII (HPQuadro64.dmpriest.net.uk [62.13.130.30]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3) with ESMTP id q7A7cYmW081625 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Aug 2012 08:38:34 +0100 (BST) Date: Fri, 10 Aug 2012 08:38:34 +0100 From: Karl Pielorz To: freebsd-hackers@FreeBSD.org Message-ID: <8E11701C93FCCC39AA97E4F1@OctaHexa64-MkII> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: FreeBSD 9.0-R em0 issues? 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, 10 Aug 2012 07:41:59 -0000 Hi, I've got a SuperMicro X8DTL-IF based server (with Intel L5630), 6Gb of RAM and two onboard Intel NIC's. afaik this is running the stock FreeBSD 9.0-R GENERIC kernel. em0: port 0xdc00-0xdc1f mem 0xfbce0000-0xfbcfffff,0xfbcdc000-0xfbcdffff irq 16 at device 0.0 on pci6 em0: Using MSIX interrupts with 3 vectors em0: Ethernet address: 00:25:90:31:82:46 em0: link state changed to UP em1: port 0xec00-0xec1f mem 0xfbde0000-0xfbdfffff,0xfbddc000-0xfbddffff irq 17 at device 0.0 on pci7 em1: Using MSIX interrupts with 3 vectors em1: Ethernet address: 00:25:90:31:82:47 em0 is the only one in use, and it 'freezes' every now and again. Symptoms are no traffic in, or out - but pretty 'insane' figures from 'netstat -i' e.g. Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em0 1500 00:25:90:31:82:46 610815304 22999549864725 0 518403896 6571299961350 3285649980675 The machines ARP cache expires at the time, and tcpdump shows no data at all on that interface. The switch port this is connected to disagrees with the errors (it has non logged currently for that port). The machine is a lightly loaded MySQL host. Considering the above was taken 'seconds' after the NIC stopped - I can't really see it had logged billions of legitimate errors in that small time frame? Doing an 'ifconfig em0 down' and 'ifconfig em0 up' makes no difference when it's hung. Rebooting the machine fixes the problem 'for a while'. Once rebooted no Oerrs, Coll errors or anything are shown by netstat -i Any suggestions what this could be? - Or what I can do to diagnose further? Nothing is logged on the console, or /var/log/messages When it failed last time, I did 'sysctl dev.em.0.debug=1' which netted: Interface is RUNNING and INACTIVE em0: hw tdh = -1, hw tdt = -1 em0: hw rdh = -1, hw rdt = -1 em0: Tx Queue Status = 1 em0: Tx descriptors avail = 986 em0: Tx Descriptors avail failure = 0 em0: RX discarded packets = 0 em0: RX Next to Check = 844 em0: RX Next to Refresh = 843 Should I be concerned about the '-1's? Thanks, -Karl From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 10:13:08 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1E4D5106568D; Fri, 10 Aug 2012 10:13:08 +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 73DF18FC17; Fri, 10 Aug 2012 10:13:07 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q7AADETO096228; Fri, 10 Aug 2012 13:13:14 +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.5/8.14.5) with ESMTP id q7AAD2gx009953; Fri, 10 Aug 2012 13:13:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q7AAD285009952; Fri, 10 Aug 2012 13:13:02 +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: Fri, 10 Aug 2012 13:13:02 +0300 From: Konstantin Belousov To: Jilles Tjoelker Message-ID: <20120810101302.GF2425@deviant.kiev.zoral.com.ua> References: <20120730102408.GA19983@stack.nl> <20120730105303.GU2676@deviant.kiev.zoral.com.ua> <20120805215432.GA28704@stack.nl> <20120806082535.GI2676@deviant.kiev.zoral.com.ua> <20120809105648.GA79814@stack.nl> <20120809110850.GA2425@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GLp9dJVi+aaipsRk" Content-Disposition: inline In-Reply-To: <20120809110850.GA2425@deviant.kiev.zoral.com.ua> 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=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham 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, davidxu@freebsd.org Subject: Re: system() using vfork() or posix_spawn() and libthr 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, 10 Aug 2012 10:13:08 -0000 --GLp9dJVi+aaipsRk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 09, 2012 at 02:08:50PM +0300, Konstantin Belousov wrote: > Third alternative, which seems to be even better, is to restore > single-threading of the parent for vfork(). I mean this patch. diff --git a/sys/kern/kern_fork.c b/sys/kern/kern_fork.c index 6cb95cd..e59ee21 100644 --- a/sys/kern/kern_fork.c +++ b/sys/kern/kern_fork.c @@ -756,7 +756,7 @@ fork1(struct thread *td, int flags, int pages, struct p= roc **procp, struct thread *td2; struct vmspace *vm2; vm_ooffset_t mem_charged; - int error; + int error, single_threaded; static int curfail; static struct timeval lastfail; #ifdef PROCDESC @@ -815,6 +815,19 @@ fork1(struct thread *td, int flags, int pages, struct = proc **procp, } #endif =20 + if (((p1->p_flag & (P_HADTHREADS | P_SYSTEM)) =3D=3D P_HADTHREADS) && + (flags & RFPPWAIT) !=3D 0) { + PROC_LOCK(p1); + if (thread_single(SINGLE_BOUNDARY)) { + PROC_UNLOCK(p1); + error =3D ERESTART; + goto fail2; + } + PROC_UNLOCK(p1); + single_threaded =3D 1; + } else + single_threaded =3D 0; + mem_charged =3D 0; vm2 =3D NULL; if (pages =3D=3D 0) @@ -945,6 +958,12 @@ fail1: if (vm2 !=3D NULL) vmspace_free(vm2); uma_zfree(proc_zone, newproc); + if (single_threaded) { + PROC_LOCK(p1); + thread_single_end(); + PROC_UNLOCK(p1); + } +fail2: #ifdef PROCDESC if (((flags & RFPROCDESC) !=3D 0) && (fp_procdesc !=3D NULL)) { fdclose(td->td_proc->p_fd, fp_procdesc, *procdescp, td); diff --git a/tools/test/pthread_vfork/pthread_vfork_test.c b/tools/test/pth= read_vfork/pthread_vfork_test.c index e004727..88956c2 100644 --- a/tools/test/pthread_vfork/pthread_vfork_test.c +++ b/tools/test/pthread_vfork/pthread_vfork_test.c @@ -29,6 +29,8 @@ #include __FBSDID("$FreeBSD$"); =20 +#include +#include #include #include #include @@ -39,10 +41,11 @@ __FBSDID("$FreeBSD$"); =20 #define NUM_THREADS 100 =20 -void * -vfork_test(void *threadid) +static void * +vfork_test(void *threadid __unused) { - pid_t pid; + pid_t pid, wpid; + int status; =20 for (;;) { pid =3D vfork(); @@ -50,10 +53,20 @@ vfork_test(void *threadid) _exit(0); else if (pid =3D=3D -1) err(1, "Failed to vfork"); + else { + wpid =3D waitpid(pid, &status, 0); + if (wpid =3D=3D -1) + err(1, "waitpid"); + } } return (NULL); } =20 +static void +sighandler(int signo __unused) +{ +} + /* * This program invokes multiple threads and each thread calls * vfork() system call. @@ -63,19 +76,24 @@ main(void) { pthread_t threads[NUM_THREADS]; struct sigaction reapchildren; + sigset_t sigchld_mask; int rc, t; =20 memset(&reapchildren, 0, sizeof(reapchildren)); - reapchildren.sa_handler =3D SIG_IGN; - - /* Automatically reap zombies. */ + reapchildren.sa_handler =3D sighandler; if (sigaction(SIGCHLD, &reapchildren, NULL) =3D=3D -1) err(1, "Could not sigaction(SIGCHLD)"); =20 + sigemptyset(&sigchld_mask); + sigaddset(&sigchld_mask, SIGCHLD); + if (sigprocmask(SIG_BLOCK, &sigchld_mask, NULL) =3D=3D -1) + err(1, "sigprocmask"); + for (t =3D 0; t < NUM_THREADS; t++) { rc =3D pthread_create(&threads[t], NULL, vfork_test, (void *)t); if (rc) errc(1, rc, "pthread_create"); } + pause(); return (0); } --GLp9dJVi+aaipsRk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAk3q4ACgkQC3+MBN1Mb4g29QCghHodkIf2zunuCoeJlrsux7QN fP8AoJ/taKj2h5VQAco2vg/NY90ZmyZW =c6ZU -----END PGP SIGNATURE----- --GLp9dJVi+aaipsRk-- From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 12:59:16 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99B0B106566C for ; Fri, 10 Aug 2012 12:59:16 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 31B368FC08 for ; Fri, 10 Aug 2012 12:59:15 +0000 (UTC) Received: from OctaHexa64-MkII (HPQuadro64.dmpriest.net.uk [62.13.130.30]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3) with ESMTP id q7ACxC5q051863 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Aug 2012 13:59:14 +0100 (BST) Date: Fri, 10 Aug 2012 13:59:12 +0100 From: Karl Pielorz To: freebsd-hackers@FreeBSD.org Message-ID: <933A64025C87497D5FBDCA75@OctaHexa64-MkII> In-Reply-To: <8E11701C93FCCC39AA97E4F1@OctaHexa64-MkII> References: <8E11701C93FCCC39AA97E4F1@OctaHexa64-MkII> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: FreeBSD 9.0-R em0 issues? - update... 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, 10 Aug 2012 12:59:16 -0000 The last time it hung, 'netstat -n -i' showed: " Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em0 1500 00:25:90:31:82:46 355482 10612864185945 0 291109 3032246910270 1516123455135 " That's from about 30 seconds after the interface 'stopped' - that number of ierrs/oerrs etc. - is just impossible for the traffic the machine handles, it looks like it's corrupt? Having dug around some more - I've now set: hw.em.enable_msix=0 After rebooting - the hang hasn't happened since - I'll leave it running like that for a while. If anyone can suggest anything to run when / if this happens again to track things down further - or any reason why it's doing it, that'd be great.. -Karl ps. Should have said before but the machine is running an amd64 kernel. From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 14:47:37 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E5C68106564A for ; Fri, 10 Aug 2012 14:47:36 +0000 (UTC) (envelope-from kuku@kukulies.org) Received: from kukulies.org (mail.kukulies.org [78.47.239.221]) by mx1.freebsd.org (Postfix) with ESMTP id 77F618FC0A for ; Fri, 10 Aug 2012 14:47:36 +0000 (UTC) Received: by kukulies.org (Postfix, from userid 5001) id 65E921AD860; Fri, 10 Aug 2012 16:47:35 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on kukulies.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=2.0 tests=ALL_TRUSTED autolearn=ham version=3.3.2 Received: from [172.27.4.215] (unknown [87.79.34.228]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kukulies.org (Postfix) with ESMTPSA id 892EF1AD85F for ; Fri, 10 Aug 2012 16:47:32 +0200 (CEST) Message-ID: <50251F03.4050400@kukulies.org> Date: Fri, 10 Aug 2012 16:47:31 +0200 From: "Christoph P.U. Kukulies" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: strange things happening with ping - am I hacked? 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, 10 Aug 2012 14:47:37 -0000 I have some machines in a companys' network that are interconnected with a piece of coaxial cable (ethernet 10base2). This trunk goes through a switch that acts also as a media converter and connects to the Internet router. For a while now I'm having trouble with this 10base2 trunk and I dropped in another FreeBSD machine to move the services I'm running to the newer (9.0) machine. At the moment the two FreeBSD boxes (one 9.0, the other 5.1) are on the net. Both have a DIVERT kernel and act as gateways between the in house network and the Internet (natd). Now strange things happen: When I ping from the 9.0 machine to another machine (a Windows XP) in the network, I don't get an immediate response from the ping but after some, day 20s or so I get: (I prefer to not use the real addresses in the source or destination) forum2# ping 80.90.34.226 forum2# tcpdump -i ed0 -l ip proto ICMP tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ed0, link-type EN10MB (Ethernet), capture size 65535 bytes 16:15:06.748522 IP 80.90.34.228 > 129.82.138.44: ICMP echo reply, id 50777, seq 49408, length 8 or: 16:15:06.748522 IP 80.90.34.228 > 129.82.138.44: ICMP echo reply, id 50777, seq 49408, length 8 16:17:01.920480 IP 80.90.34.228 > 203.178.148.19: ICMP echo reply, id 9061, seq 48393, length 8 ^C 2 packets captured 473 packets received by filter 0 packets dropped by kernel Doing the same ping from the 5.1 box (pretty sure it hasn't got to do with the OS versions), gives an echo reply immediately from the target address I pinged. So why does there come an echo reply from machines on the net which seem to exist and even have names like pinger-j2.ant.isi.edu or pinger6.netsec.colostate.edu? Does there some packet redirection take place? -- Christoph Kukulies From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 15:35:33 2012 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 6D424106564A for ; Fri, 10 Aug 2012 15:35:33 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by mx1.freebsd.org (Postfix) with ESMTP id E59388FC0A for ; Fri, 10 Aug 2012 15:35:32 +0000 (UTC) Received: from [194.32.164.22] (80-46-130-69.static.dsl.as9105.com [80.46.130.69]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id q7AFSICq078023; Fri, 10 Aug 2012 16:28:18 +0100 (BST) (envelope-from rb@gid.co.uk) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: Bob Bishop In-Reply-To: <50251F03.4050400@kukulies.org> Date: Fri, 10 Aug 2012 16:28:12 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <1668355C-7597-4878-9D0B-164B051E1CA7@gid.co.uk> References: <50251F03.4050400@kukulies.org> To: "Christoph P.U. Kukulies" X-Mailer: Apple Mail (2.1278) Cc: freebsd-hackers@freebsd.org Subject: Re: strange things happening with ping - am I hacked? 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, 10 Aug 2012 15:35:33 -0000 Hi, On 10 Aug 2012, at 15:47, Christoph P.U. Kukulies wrote: > I have some machines in a companys' network that are interconnected > with a piece of coaxial cable (ethernet 10base2). This trunk goes = through a > switch that acts also as a media converter and connects to the = Internet router. >=20 > For a while now I'm having trouble with this 10base2 trunk It might just be packets getting corrupted, just a few replies get back = with address field corruption.=20 > and I dropped in another FreeBSD > machine to move the services I'm running to the newer (9.0) machine. > At the moment the two FreeBSD boxes (one 9.0, the other 5.1) are on = the net. > Both have a DIVERT kernel and act as gateways between the in house = network and the Internet (natd). >=20 > Now strange things happen: > When I ping from the 9.0 machine to another machine (a Windows XP) in = the network, > I don't get an immediate response from the ping but after some, day = 20s or so I get: >=20 > (I prefer to not use the real addresses in the source or destination) > forum2# ping 80.90.34.226 > forum2# tcpdump -i ed0 -l ip proto ICMP > tcpdump: verbose output suppressed, use -v or -vv for full protocol = decode > listening on ed0, link-type EN10MB (Ethernet), capture size 65535 = bytes > 16:15:06.748522 IP 80.90.34.228 > 129.82.138.44: ICMP echo reply, id = 50777, seq 49408, length 8 >=20 > or: >=20 > 16:15:06.748522 IP 80.90.34.228 > 129.82.138.44: ICMP echo reply, id = 50777, seq 49408, length 8 > 16:17:01.920480 IP 80.90.34.228 > 203.178.148.19: ICMP echo reply, id = 9061, seq 48393, length 8 > ^C > 2 packets captured > 473 packets received by filter > 0 packets dropped by kernel >=20 > Doing the same ping from the 5.1 box (pretty sure it hasn't got to do = with the OS versions), > gives an echo reply immediately from the target address I pinged. >=20 > So why does there come an echo reply from machines on the net which = seem to exist and > even have names like pinger-j2.ant.isi.edu or = pinger6.netsec.colostate.edu? >=20 > Does there some packet redirection take place? > -- > Christoph Kukulies > _______________________________________________ > 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" >=20 -- Bob Bishop +44 (0)118 940 1243 rb@gid.co.uk fax +44 (0)118 940 1295 mobile +44 (0)783 626 4518 From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 16:06:48 2012 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 9AB6410656EF for ; Fri, 10 Aug 2012 16:06:48 +0000 (UTC) (envelope-from dplassche@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 294628FC1C for ; Fri, 10 Aug 2012 16:06:47 +0000 (UTC) Received: by wicr5 with SMTP id r5so445312wic.13 for ; Fri, 10 Aug 2012 09:06:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=3Lb29Zb7Gv/7T2bIoGKMRxoXbosMw7uQbIILOgLRXJ8=; b=I7fAg5wuheFPb5SWK5b3CZjDKf3kvtjiWpvur2vFi6a+9Qw1MKlj0m48iATayiGfNl zwfU0NxrXw2ZoL0fReLzWBuFt8q4ZQB2wQ35KSn02Hm+qqzkZxeKskZzASFSmJQVVhoz WdhzQa5x9Bbqd0baw1zsYzFvW6Lz/n6a/cBPNOzblj7P8NADHI7P4bVTFcXMs+8qMg8z oG70E/5nlZ2IHPt8fl+UoLEM9vvE6K25ZVGdQpiiD5F7knF4qyNMzm1AWabAlebxW1iG zLOH/TQhlRjg9okdPEGkJyai7xp2Xvry03NOXWSaYjDhMAqvvkp+YG87PjkWBv81FYIc faEw== MIME-Version: 1.0 Received: by 10.180.83.66 with SMTP id o2mr7113430wiy.14.1344614807051; Fri, 10 Aug 2012 09:06:47 -0700 (PDT) Received: by 10.223.134.7 with HTTP; Fri, 10 Aug 2012 09:06:46 -0700 (PDT) Date: Fri, 10 Aug 2012 12:06:46 -0400 Message-ID: From: Dan Plassche To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Fri, 10 Aug 2012 16:29:53 +0000 Subject: FreeBSD 1.x Binaries Work Except under Chroot 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, 10 Aug 2012 16:06:48 -0000 Hello, I'm successfully running FreeBSD 1.1.5.1 binaries from a directory on an 8.2 system. The goal is to ultimately setup a chroot build environment targeting 1.x for an old 386. However, whenever I chroot to the /freebsd-1.1.5.1 directory tree, the old binaries suddenly start failing with linker error messages such as this one: "ld.so: whereis: libc.so.1.1". I've tried to run ldconfig (static old and new versions) on clean copies of /freebsd-1.1.5.1 to correct the problem. Each copy of the tree has libc.so.1.1 under /usr/lib and the full /usr/lib/compat/aout (just in case). Running the old ldconfig with the -v flag against both library directories shows the libraries added and produces a new /var/run/ld.so.hints file. Running that same old ldconfig with -r shows "2:-lc.1.1 => /usr/lib/libc.so.1.1 (9-> -1)" but the binaries still fail in the chroot. The same process with the 8.2 ldconfig (after copying in /libexec/ld-elf.so.1 and /lib/libc.so.7 to make it work) also fails to resolve the problem after creating the aout /var/run/ld.so.hints file for /usr/lib/* and the elf /var/run/ld-elf.so.hints file for /lib. Would anyone have a suggestion please? The setup outside of the chroot works with the 1.x compat libraries combines with a kernel compiled with the compat options and PID_MAX set to 3000. Thank you, Dan Plassche -- Dan Plassche From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 17:07:21 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A9994106564A for ; Fri, 10 Aug 2012 17:07:21 +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 084E28FC12 for ; Fri, 10 Aug 2012 17:07:20 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q7AH7SHK031112; Fri, 10 Aug 2012 20:07:28 +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.5/8.14.5) with ESMTP id q7AH7FTO011918; Fri, 10 Aug 2012 20:07:15 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q7AH7Fp3011917; Fri, 10 Aug 2012 20:07:15 +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: Fri, 10 Aug 2012 20:07:15 +0300 From: Konstantin Belousov To: Dan Plassche Message-ID: <20120810170715.GI2425@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zqjkMoGlbUJ91oFe" 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=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham 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: FreeBSD 1.x Binaries Work Except under Chroot 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, 10 Aug 2012 17:07:21 -0000 --zqjkMoGlbUJ91oFe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 10, 2012 at 12:06:46PM -0400, Dan Plassche wrote: > Hello, >=20 > I'm successfully running FreeBSD 1.1.5.1 binaries from a > directory on an 8.2 system. The goal is to ultimately setup a > chroot build environment targeting 1.x for an old 386. However, > whenever I chroot to the /freebsd-1.1.5.1 directory tree, the old > binaries suddenly start failing with linker error messages such > as this one: "ld.so: whereis: libc.so.1.1". >=20 > I've tried to run ldconfig (static old and new versions) on > clean copies of /freebsd-1.1.5.1 to correct the problem. Each > copy of the tree has libc.so.1.1 under /usr/lib and the full > /usr/lib/compat/aout (just in case). >=20 > Running the old ldconfig with the -v flag against both library > directories shows the libraries added and produces a new > /var/run/ld.so.hints file. Running that same old ldconfig with > -r shows "2:-lc.1.1 =3D> /usr/lib/libc.so.1.1 (9-> -1)" but the > binaries still fail in the chroot. >=20 > The same process with the 8.2 ldconfig (after copying > in /libexec/ld-elf.so.1 and /lib/libc.so.7 to make it > work) also fails to resolve the problem after creating the > aout /var/run/ld.so.hints file for /usr/lib/* and the elf > /var/run/ld-elf.so.hints file for /lib. >=20 > Would anyone have a suggestion please? The setup outside of the > chroot works with the 1.x compat libraries combines with a kernel > compiled with the compat options and PID_MAX set to 3000. Try to ktrace the binaries to see what is going on. I suspect that sources for 1.1.5 are not in our cvs/svn, so it is troublesome to say anuthing without ktrace dump. --zqjkMoGlbUJ91oFe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAlP8MACgkQC3+MBN1Mb4gmtwCfaKwBh5MuLx424XhWqzzCF0jW gkQAn3j/gAktg7qUSMXv0jRsj6NlOaNj =bM3g -----END PGP SIGNATURE----- --zqjkMoGlbUJ91oFe-- From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 23:07:03 2012 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 B58F6106566C for ; Fri, 10 Aug 2012 23:07:03 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 1EE138FC16 for ; Fri, 10 Aug 2012 23:07:02 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBDF0F.dip.t-dialin.net [93.203.223.15]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id q7AMmWAM064093 for ; Fri, 10 Aug 2012 22:48:33 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id q7AMnEkW055355 for ; Sat, 11 Aug 2012 00:49:14 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id q7AMn8gF066402 for ; Sat, 11 Aug 2012 00:49:14 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201208102249.q7AMn8gF066402@fire.js.berklix.net> To: freebsd-hackers@freebsd.org From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Fri, 10 Aug 2012 20:07:15 +0300." <20120810170715.GI2425@deviant.kiev.zoral.com.ua> Date: Sat, 11 Aug 2012 00:49:08 +0200 Sender: jhs@berklix.com Subject: Re: FreeBSD 1.x Binaries Work Except under Chroot 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, 10 Aug 2012 23:07:03 -0000 > Try to ktrace the binaries to see what is going on. I suspect that > sources for 1.1.5 are not in our cvs/svn, so it is troublesome to > say anuthing without ktrace dump. Not that I need it, but I looked to see how old we go. (Sometimes its nice to have old stuff, eg to defeat patent claims) I dont see 1.1.5: /usr/cvs/src/Makefile,v : RELENG_2_1_0_RELEASE:1.57.4.8 RELENG_2_1_0:1.57.0.4 RELENG_2_1_0_BP:1.57 RELENG_2_0_5_RELEASE:1.57 RELENG_2_0_5:1.57.0.2 RELENG_2_0_5_BP:1.57 RELENG_2_0_5_ALPHA:1.56 RELEASE_2_0:1.30 BETA_2_0:1.30 ALPHA_2_0:1.29.0.2 bsd_44_lite:1.1.1.1 CSRG:1.1.1; cvs -Q -R export -r RELEASE_2_0 src Works (slowly, all the reverse diffs I guess): 100Meg http://www.freebsd.org/releases/ 2.0.5 (June, 1995) Announcement : Release Notes 2.0 (November, 1994) Announcement : Release Notes 1.1.5.1 (July, 1994) 1.1.5 Release Notes 1.1 (May, 1994) Release Notes 1.0 (November, 1993) http://www.freebsd.org/cgi/cvsweb.cgi/src/Makefile#diff shows diffs for src/Makefile back to Rev CVS tags: RELEASE_2_0, BETA_2_0 1.29 ALPHA_2_0 1.1.1.1 bsd_44_lite 1.1 ________ Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from Yahoo & Hotmail to be dumped @Berklix. http://berklix.org/yahoo/ From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 21:15:35 2012 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 861CB106566B for ; Fri, 10 Aug 2012 21:15:35 +0000 (UTC) (envelope-from dplassche@gmail.com) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by mx1.freebsd.org (Postfix) with ESMTP id 1448A8FC0C for ; Fri, 10 Aug 2012 21:15:34 +0000 (UTC) Received: by wibhq12 with SMTP id hq12so1485399wib.1 for ; Fri, 10 Aug 2012 14:15:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ocd31dIX67j33wtpWzUfvmAzvYU7+yJTjZg3RqQS8WE=; b=0Yuowd5skMpl6nCSRYaiAZyXqt/HcX166IkakqDAYwDieLGa3CbY1J2qMlzdKBxCE4 9o0FqJ65LXnR53LW6c0v7cnBNYyaFWhXJQA56AeTXCwvlagVt3POgskmnmQlEWMDzhZG 9Qe2seJ2ZBQHVfmFuvJfZdtXYRKAY8r/VyYcLYRvYjr1RLPTGi3cLr3tmAynykwUC4sj uW4crE1L30Qdo9f+k2Yw2c5bQJueVOV4l/RGnqcRlRW7yMB5x6z6dAy6kyM3hm6qw6rH 5BTq8c9ayNPEjr27eX0F9h73oA6DGDVEKW53PuyI2jXbSQ4BYUeuPQ9w9s1trjX5+YOg sHvQ== MIME-Version: 1.0 Received: by 10.217.1.197 with SMTP id n47mr2180921wes.27.1344633333784; Fri, 10 Aug 2012 14:15:33 -0700 (PDT) Received: by 10.223.134.7 with HTTP; Fri, 10 Aug 2012 14:15:33 -0700 (PDT) In-Reply-To: References: <20120810170715.GI2425@deviant.kiev.zoral.com.ua> Date: Fri, 10 Aug 2012 17:15:33 -0400 Message-ID: From: Dan Plassche To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Sat, 11 Aug 2012 00:09:02 +0000 Subject: Re: FreeBSD 1.x Binaries Work Except under Chroot 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, 10 Aug 2012 21:15:35 -0000 On Fri, Aug 10, 2012 at 1:07 PM, Konstantin Belousov wrote: > Try to ktrace the binaries to see what is going on. I suspect that > sources for 1.1.5 are not in our cvs/svn, so it is troublesome to > say anuthing without ktrace dump. Ok, below is the kdump from running basename as a simple example that produces the "ld.so: whereis: libc.so.1.1" error under a chrooted environment. I probably should have mentioned that I'm running these with "sysctl security.bsd.map_at_zero=1" set. The static binaries in /bin and /sbin also work under the chroot, but the others in /usr/bin and /usr/sbin fail with the ld.so error. Here's the kdump: 1144 ktrace-8.2 RET ktrace 0 1144 ktrace-8.2 CALL execve(0xbfbfee5b,0xbfbfed18,0xbfbfed20) 1144 ktrace-8.2 NAMI "/usr/bin/basename" 1144 basename RET execve 0 1144 basename CALL open(0x10a4,O_RDONLY,0) 1144 basename NAMI "/usr/libexec/ld.so" 1144 basename RET open 3 1144 basename CALL read(0x3,0xbfbfedd8,0x20) 1144 basename GIO fd 3 read 32 bytes 0x0000 cc00 8680 00d0 0000 0020 0000 8003 0000 |......... ......| 0x0010 0000 0000 2000 0000 0000 0000 0000 0000 |.... ...........| 1144 basename RET read 32/0x20 1144 basename CALL compat.mmap(0,0xd000,0x5,0x21,0x3,0) 1144 basename RET compat.mmap 536879104/0x20002000 1144 basename CALL compat.mmap(0x2000f000,0x2000,0x6,0x121,0x3,0xd000) 1144 basename RET compat.mmap 536932352/0x2000f000 1144 basename CALL compat.mmap(0x20011000,0x380,0x6,0x122,0xffffffff,0) 1144 basename RET compat.mmap 536940544/0x20011000 1144 basename CALL getuid 1144 basename RET getuid 0 1144 basename CALL geteuid 1144 basename RET geteuid 0 1144 basename CALL getgid 1144 basename RET getgid 0 1144 basename CALL getegid 1144 basename RET getegid 0 1144 basename CALL compat.mmap(0,0x8000,0x6,0x22,0xffffffff,0) 1144 basename RET compat.mmap 536944640/0x20012000 1144 basename CALL open(0x200032b0,O_RDONLY,0) 1144 basename NAMI "/var/run/ld.so.hints" 1144 basename RET open 4 1144 basename CALL compat.mmap(0,0x1000,0x4,0x21,0x4,0) 1144 basename RET compat.mmap 536977408/0x2001a000 1144 basename CALL munmap(0x2001a000,0x1000) 1144 basename RET munmap 0 1144 basename CALL open(0x20014000,O_RDONLY,0x2000f060) 1144 basename NAMI "/usr/lib" 1144 basename RET open 5 1144 basename CALL fcntl(0x5,F_SETFD,FD_CLOEXEC) 1144 basename RET fcntl 0 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x200150f4) 1144 basename RET compat.getdirentries 1024/0x400 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x200150f4) 1144 basename RET compat.getdirentries 512/0x200 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x200150f4) 1144 basename RET compat.getdirentries 0 1144 basename CALL close(0x5) 1144 basename RET close 0 1144 basename CALL open(0x20015000,O_RDONLY,0x2000f060) 1144 basename NAMI "/usr/X11R6/lib" 1144 basename RET open -1 errno 2 No such file or directory 1144 basename CALL open(0x20015020,O_RDONLY,0x2000f060) 1144 basename NAMI "/usr/X386/lib" 1144 basename RET open -1 errno 2 No such file or directory 1144 basename CALL open(0x20015060,O_RDONLY,0x2000f060) 1144 basename NAMI "/usr/local/lib" 1144 basename RET open 5 1144 basename CALL fcntl(0x5,F_SETFD,FD_CLOEXEC) 1144 basename RET fcntl 0 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x200150f4) 1144 basename RET compat.getdirentries 512/0x200 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x200150f4) 1144 basename RET compat.getdirentries 0 1144 basename CALL close(0x5) 1144 basename RET close 0 1144 basename CALL open(0x20015100,O_RDONLY,0) 1144 basename NAMI "/usr/lib/libgcc.so.1.1" 1144 basename RET open 5 1144 basename CALL read(0x5,0xbfbfed40,0x20) 1144 basename GIO fd 5 read 32 bytes 0x0000 cc00 8680 0030 0000 0010 0000 0000 0000 |.....0..........| 0x0010 600f 0000 2000 0000 0000 0000 0000 0000 |`... ...........| 1144 basename RET read 32/0x20 1144 basename CALL compat.mmap(0,0x4000,0x5,0x21,0x5,0) 1144 basename RET compat.mmap 536977408/0x2001a000 1144 basename CALL mprotect(0x2001d000,0x1000,PROT_READ|PROT_WRITE|PROT_EXEC) 1144 basename RET mprotect 0 1144 basename CALL close(0x5) 1144 basename RET close 0 1144 basename CALL open(0x20014000,O_RDONLY,0x2000f060) 1144 basename NAMI "/usr/lib" 1144 basename RET open 5 1144 basename CALL fcntl(0x5,F_SETFD,FD_CLOEXEC) 1144 basename RET fcntl 0 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x20015154) 1144 basename RET compat.getdirentries 1024/0x400 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x20015154) 1144 basename RET compat.getdirentries 512/0x200 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x20015154) 1144 basename RET compat.getdirentries 0 1144 basename CALL close(0x5) 1144 basename RET close 0 1144 basename CALL open(0x20015000,O_RDONLY,0x2000f060) 1144 basename NAMI "/usr/X11R6/lib" 1144 basename RET open -1 errno 2 No such file or directory 1144 basename CALL open(0x20015020,O_RDONLY,0x2000f060) 1144 basename NAMI "/usr/X386/lib" 1144 basename RET open -1 errno 2 No such file or directory 1144 basename CALL open(0x20015060,O_RDONLY,0x2000f060) 1144 basename NAMI "/usr/local/lib" 1144 basename RET open 5 1144 basename CALL fcntl(0x5,F_SETFD,FD_CLOEXEC) 1144 basename RET fcntl 0 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x20015154) 1144 basename RET compat.getdirentries 512/0x200 1144 basename CALL compat.getdirentries(0x5,0x20017000,0x400,0x20015154) 1144 basename RET compat.getdirentries 0 1144 basename CALL close(0x5) 1144 basename RET close 0 1144 basename CALL open(0x20015160,O_RDONLY,0) 1144 basename NAMI "/usr/lib/libc.so.1.1" 1144 basename RET open 5 1144 basename CALL read(0x5,0xbfbfed40,0x20) 1144 basename GIO fd 5 read 32 bytes 0x0000 cc00 8680 0070 0400 0060 0000 b86b 0000 |.....p...`...k..| 0x0010 b4b7 0000 2000 0000 0000 0000 0000 0000 |.... ...........| 1144 basename RET read 32/0x20 1144 basename CALL compat.mmap(0,0x4d000,0x5,0x21,0x5,0) 1144 basename RET compat.mmap 536993792/0x2001e000 1144 basename CALL mprotect(0x20065000,0x6000,PROT_READ|PROT_WRITE|PROT_EXEC) 1144 basename RET mprotect 0 1144 basename CALL close(0x5) 1144 basename RET close 0 1144 basename CALL compat.mmap(0x2006b000,0x6bb8,0x7,0x122,0xffffffff,0x4d000) 1144 basename RET compat.mmap -1 errno 22 Invalid argument 1144 basename CALL write(0x2,0xbfbfe5fc,0x7) 1144 basename GIO fd 2 wrote 7 bytes "ld.so: " 1144 basename RET write 7 1144 basename CALL write(0x2,0xbfbfe614,0x15) 1144 basename GIO fd 2 wrote 21 bytes "basename: libc.so.1.1" 1144 basename RET write 21/0x15 1144 basename CALL write(0x2,0xbfbfe5f4,0x2) 1144 basename GIO fd 2 wrote 2 bytes ": " 1144 basename RET write 2 1144 basename CALL write(0x2,0xbfbfe5f8,0x11) 1144 basename GIO fd 2 wrote 17 bytes "Invalid argument " 1144 basename RET write 17/0x11 1144 basename CALL exit(0x1) The sources are available from the FreeBSD old releases archive now that they are under the "Ancient UNIX" license, but yeah there's no CVS history for change tracking due to the purge with the switch to 4.4 Lite. Thanks, Dan From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 11 00:11:01 2012 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 9EB581065674 for ; Sat, 11 Aug 2012 00:11:01 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by mx1.freebsd.org (Postfix) with ESMTP id 384DE8FC14 for ; Sat, 11 Aug 2012 00:11:01 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.4/8.14.4) with ESMTP id q7B0Ase7054619 for ; Fri, 10 Aug 2012 20:10:59 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <5025A30E.6000008@m5p.com> Date: Fri, 10 Aug 2012 20:10:54 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120623 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <201208102249.q7AMn8gF066402@fire.js.berklix.net> In-Reply-To: <201208102249.q7AMn8gF066402@fire.js.berklix.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Fri, 10 Aug 2012 20:10:59 -0400 (EDT) X-Scanned-By: MIMEDefang 2.72 on 10.100.0.3 Subject: Re: FreeBSD 1.x Binaries Work Except under Chroot 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, 11 Aug 2012 00:11:01 -0000 On 08/10/12 18:49, Julian H. Stacey wrote: >> Try to ktrace the binaries to see what is going on. I suspect that >> sources for 1.1.5 are not in our cvs/svn, so it is troublesome to >> say anuthing without ktrace dump. > > Not that I need it, but I looked to see how old we go. > (Sometimes its nice to have old stuff, eg to defeat patent claims) > > I dont see 1.1.5: > > /usr/cvs/src/Makefile,v : > RELENG_2_1_0_RELEASE:1.57.4.8 > RELENG_2_1_0:1.57.0.4 > RELENG_2_1_0_BP:1.57 > RELENG_2_0_5_RELEASE:1.57 > RELENG_2_0_5:1.57.0.2 > RELENG_2_0_5_BP:1.57 > RELENG_2_0_5_ALPHA:1.56 > RELEASE_2_0:1.30 > BETA_2_0:1.30 > ALPHA_2_0:1.29.0.2 > bsd_44_lite:1.1.1.1 > CSRG:1.1.1; As I recall, 1.1.5.1 was the first version declared to be entitrely free of copyrighted code. There was probably an agreement not to distribute any earlier versions. -- George > > cvs -Q -R export -r RELEASE_2_0 src > Works (slowly, all the reverse diffs I guess): 100Meg > > http://www.freebsd.org/releases/ > 2.0.5 (June, 1995) Announcement : Release Notes > 2.0 (November, 1994) Announcement : Release Notes > 1.1.5.1 (July, 1994) > 1.1.5 Release Notes > 1.1 (May, 1994) Release Notes > 1.0 (November, 1993) > > http://www.freebsd.org/cgi/cvsweb.cgi/src/Makefile#diff > shows diffs for src/Makefile back to > Rev CVS tags: > RELEASE_2_0, BETA_2_0 > 1.29 ALPHA_2_0 > 1.1.1.1 bsd_44_lite > 1.1 ________ > > Cheers, > Julian > From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 11 02:01:54 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E6DF3106564A for ; Sat, 11 Aug 2012 02:01:54 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id B34048FC0A for ; Sat, 11 Aug 2012 02:01:54 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so3828039pbb.13 for ; Fri, 10 Aug 2012 19:01:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=/l4TIJt25VUo/stATvP+mqqNz2Tkzxbw6D5NikdNB0I=; b=dZF1s0Tcr3oEhWAO9md0PSJwjwGLmpzGbp1eOt4h97GMskalsoQMTHX+vjVDAZBqz/ FVFJZPJk2EZJ7YUeTegNHfnYxvFvmI7BHO+J92elY+xS/KgqoEmkFCpCmbtxgAuOLEgA ORs/q3nTtpx5px8fcawFK6wY9tBLKe9B8P0LBapYGkL8epDrMtCKibzsTvF7C/7MVzSU l4ZnqKRDIwZwmLaDI6+K94o49T3l70gVjlT4zDl8gp6UEh3hWJiK72GAOfDZAANcztoA HTQeYyiL2dC0XKfBP/kMMYl+VtLviYTEL5QIcCcmVmyAC2sxirhbon5BVqwz8ZHUqpXM U1vQ== Received: by 10.68.233.197 with SMTP id ty5mr16932962pbc.12.1344650507896; Fri, 10 Aug 2012 19:01:47 -0700 (PDT) Received: from [10.0.0.63] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id th6sm71644pbc.0.2012.08.10.19.01.47 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 10 Aug 2012 19:01:47 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <5025A30E.6000008@m5p.com> Date: Fri, 10 Aug 2012 20:01:44 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201208102249.q7AMn8gF066402@fire.js.berklix.net> <5025A30E.6000008@m5p.com> To: George Mitchell X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQlGbqFe/ilbPNxfWbmCOgN78dQPzCR4SViu2IUhYCcRaBW1QtF6pOTCLogI5ZGBPM6zZyvv Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 1.x Binaries Work Except under Chroot 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, 11 Aug 2012 02:01:55 -0000 On Aug 10, 2012, at 6:10 PM, George Mitchell wrote: > On 08/10/12 18:49, Julian H. Stacey wrote: >>> Try to ktrace the binaries to see what is going on. I suspect that >>> sources for 1.1.5 are not in our cvs/svn, so it is troublesome to >>> say anuthing without ktrace dump. >>=20 >> Not that I need it, but I looked to see how old we go. >> (Sometimes its nice to have old stuff, eg to defeat patent claims) >>=20 >> I dont see 1.1.5: >>=20 >> /usr/cvs/src/Makefile,v : >> RELENG_2_1_0_RELEASE:1.57.4.8 >> RELENG_2_1_0:1.57.0.4 >> RELENG_2_1_0_BP:1.57 >> RELENG_2_0_5_RELEASE:1.57 >> RELENG_2_0_5:1.57.0.2 >> RELENG_2_0_5_BP:1.57 >> RELENG_2_0_5_ALPHA:1.56 >> RELEASE_2_0:1.30 >> BETA_2_0:1.30 >> ALPHA_2_0:1.29.0.2 >> bsd_44_lite:1.1.1.1 >> CSRG:1.1.1; >=20 > As I recall, 1.1.5.1 was the first version declared to be entitrely > free of copyrighted code. There was probably an agreement not to > distribute any earlier versions. -- George Actually that was 2.0. The whole 1.1 tree was taken off line as part of = the AT&T lawsuit settlement. Warner= From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 11 06:31:38 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 44BC0106566B for ; Sat, 11 Aug 2012 06:31:38 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id F299C8FC08 for ; Sat, 11 Aug 2012 06:31:37 +0000 (UTC) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 7F8763B773; Sat, 11 Aug 2012 06:31:30 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id q7B6VTA2004833; Sat, 11 Aug 2012 06:31:30 GMT (envelope-from phk@phk.freebsd.dk) To: "Julian H. Stacey" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 11 Aug 2012 00:49:08 +0200." <201208102249.q7AMn8gF066402@fire.js.berklix.net> Content-Type: text/plain; charset=ISO-8859-1 Date: Sat, 11 Aug 2012 06:31:29 +0000 Message-ID: <4832.1344666689@critter.freebsd.dk> X-Mailman-Approved-At: Sat, 11 Aug 2012 11:10:45 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 1.x Binaries Work Except under Chroot 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, 11 Aug 2012 06:31:38 -0000 In message <201208102249.q7AMn8gF066402@fire.js.berklix.net>, "Julian H. Stacey " writes: >I dont see 1.1.5: It is not in our VCS because of the USL-BSD lawsuit. You can find the bits here: http://phk.freebsd.dk/FreeBSD/ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 11 13:10:50 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E0413106566B; Sat, 11 Aug 2012 13:10:50 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id 5FECF8FC08; Sat, 11 Aug 2012 13:10:50 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 382143592EF; Sat, 11 Aug 2012 15:10:49 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 03C1B2847B; Sat, 11 Aug 2012 15:10:48 +0200 (CEST) Date: Sat, 11 Aug 2012 15:10:48 +0200 From: Jilles Tjoelker To: David Xu Message-ID: <20120811131048.GA29572@stack.nl> References: <20120730102408.GA19983@stack.nl> <20120730105303.GU2676@deviant.kiev.zoral.com.ua> <20120805215432.GA28704@stack.nl> <20120806082535.GI2676@deviant.kiev.zoral.com.ua> <20120809105648.GA79814@stack.nl> <50246EE4.9090409@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50246EE4.9090409@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Konstantin Belousov , freebsd-hackers@freebsd.org Subject: Re: system() using vfork() or posix_spawn() and libthr 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, 11 Aug 2012 13:10:51 -0000 On Fri, Aug 10, 2012 at 10:16:04AM +0800, David Xu wrote: > On 2012/08/09 18:56, Jilles Tjoelker wrote: > > On Mon, Aug 06, 2012 at 11:25:35AM +0300, Konstantin Belousov wrote: > >> On Sun, Aug 05, 2012 at 11:54:32PM +0200, Jilles Tjoelker wrote: > >>> On Mon, Jul 30, 2012 at 01:53:03PM +0300, Konstantin Belousov wrote: > >>>> On Mon, Jul 30, 2012 at 12:24:08PM +0200, Jilles Tjoelker wrote: > >>>>> People sometimes use system() from large address spaces where it would > >>>>> improve performance greatly to use vfork() instead of fork(). > >>>>> A simple approach is to change fork() to vfork(), although I have not > >>>>> tried this. It seems safe enough to use sigaction and sigprocmask system > >>>>> calls in the vforked process. > >>>>> Alternatively, we can have posix_spawn() do the vfork() with signal > >>>>> changes. This avoids possible whining from compilers and static > >>>>> analyzers about using vfork() in system.c. However, I do not like the > >>>>> tricky code for signals and that it adds lines of code. > >>>>> This is lightly tested. > >>>> It is interesting to note that for some time our vfork(2) no longer > >>>> stops the whole forked process (parent), only the forking thread is > >>>> waiting for the child exit or exec. I am not sure is this point > >>>> important for system(3), but determined code can notice the difference > >>>> from the fork->vfork switch. > >>> Neither fork nor vfork call thread_single(SINGLE_BOUNDARY), so this is > >>> not a difference. > >> It is the difference, because vforked child shares parent address space. > >>> Thread singling may be noticeable from a failing execve() (but only in > >>> the process doing execve()) and in the rare case of rfork() without > >>> RFPROC. > >> No, other running threads in parent affect vforked child till exec or exit. > >> In fact, I would classify this as bug, but not a serious one. > > There are some ugly ways this parallel execution is depended on. If the > > vforked child calls sigaction() while another thread is also in > > sigaction() for that signal, the vforked child needs to wait for the > > other thread to release the lock. > > This uses a per-process lock to synchronize threads in different > > processes, which may not work properly. > > If the vforked child is killed (such as by SIGKILL) while holding the > > lock, the parent is not killed but its _thr_sigact is damaged. > > These problems could be avoided in libthr by skipping the lock in > > _sigaction() if a signal action is being set to SIG_DFL or SIG_IGN and > > the old action is not queried. In those cases, _thr_sigact is not > > touched so no lock is required. This change also helps applications, > > provided they call sigaction() and not signal(). > > Alternatively, posix_spawn() and system() could use the sigaction system > > call directly, bypassing libthr (if present). However, this will not > > help applications that call vfork() and sigaction() themselves (such as > > a shell that wants to implement ...& using vfork()). > > posix_spawn() likely still needs some adjustment so that having it reset > > all signals (sigfillset()) to the default action will not cause it to > > [EINVAL] because libthr does not allow changing SIGTHR's disposition. > > Index: lib/libthr/thread/thr_sig.c > > =================================================================== > > --- lib/libthr/thread/thr_sig.c (revision 238970) > > +++ lib/libthr/thread/thr_sig.c (working copy) > > @@ -519,8 +519,16 @@ > > return (-1); > > } > > > > - if (act) > > + if (act) { > > newact = *act; > > + /* > > + * Short-circuit cases where we do not touch _thr_sigact. > > + * This allows performing these safely in a vforked child. > > + */ > > + if ((newact.sa_handler == SIG_DFL || > > + newact.sa_handler == SIG_IGN)&& oact == NULL) > > + return (__sys_sigaction(sig,&newact, NULL)); > > + } > > > > __sys_sigprocmask(SIG_SETMASK,&_thr_maskset,&oldset); > > _thr_rwl_wrlock(&_thr_sigact[sig-1].lock); > > > Your patch is better than nothing, I don't object. > The problem is visble to you, but there is also invisible user - rtld. > If a symbol is never used in parent process, but now it is used > in a vforked child, the rtld will be involved, if the child > is killed, the rtld's data structure may be in inconsistent state, > such as locking or link list etcs... > I think this problem might be a non-fixable problem. Hmm. Rtld cannot be fixed like libthr because its data structures are inherently in userland. Perhaps signal handling should be different for a vforked child, like the default action of a signal sent to a thread affects the entire process and not just the thread. This cannot be implemented in the calling code because resolving execve() itself also needs rtld (ugly hacks like performing an execve() call that is guaranteed to fail aside). The rtld problem can be avoided specifically by linking with '-z now'. This might be acceptable for sh and csh; most applications can use posix_spawn() which would have to become a system call. -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 11 13:35:16 2012 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 89012106564A for ; Sat, 11 Aug 2012 13:35:16 +0000 (UTC) (envelope-from daved@tamu.edu) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5AD4C8FC0A for ; Sat, 11 Aug 2012 13:35:16 +0000 (UTC) Received: from [10.0.1.6] (pool-71-113-229-142.herntx.dsl-w.verizon.net [71.113.229.142]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7BDZFcU039811 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sat, 11 Aug 2012 08:35:15 -0500 (CDT) (envelope-from daved@tamu.edu) From: David Duchscher Content-Type: multipart/signed; boundary="Apple-Mail=_D7374F51-629E-4457-AC12-053383B73D6C"; protocol="application/pkcs7-signature"; micalg=sha1 Date: Sat, 11 Aug 2012 08:35:14 -0500 Message-Id: To: hackers@freebsd.org Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Received-SPF: pass (nostrum.com: 71.113.229.142 is authenticated by a trusted mechanism) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Disabling ethernet link on an Intel nic? 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, 11 Aug 2012 13:35:16 -0000 --Apple-Mail=_D7374F51-629E-4457-AC12-053383B73D6C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Greetings,=20 I have a need to turn off the link of an ethernet port on a Intel nic. = The issue is not a big deal but one we would like to solve. we have no = way of signaling an upstream router that a path is down but via turning = off the link of the ethernet port. This would only be used when = something goes wrong. The hope is that we could automate some problems = and handle other situations remotely avoiding having to visit the system = in person. Any thoughts? We can modify the system so if it means modifying the = driver or some other code, I am willing to try. Just need a little = direction. Thanks for your time, -- DaveD --Apple-Mail=_D7374F51-629E-4457-AC12-053383B73D6C-- From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 11 18:45:35 2012 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 4A28F106564A; Sat, 11 Aug 2012 18:45:35 +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 D64728FC14; Sat, 11 Aug 2012 18:45:33 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q7BIjZ4q081013; Sat, 11 Aug 2012 21:45:35 +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.5/8.14.5) with ESMTP id q7BIjNTR031037; Sat, 11 Aug 2012 21:45:23 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q7BIjNDC031036; Sat, 11 Aug 2012 21:45:23 +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: Sat, 11 Aug 2012 21:45:23 +0300 From: Konstantin Belousov To: Dan Plassche Message-ID: <20120811184522.GK2425@deviant.kiev.zoral.com.ua> References: <20120810170715.GI2425@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9a9Vq1BJdYBEXpLG" 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=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham 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: FreeBSD 1.x Binaries Work Except under Chroot 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, 11 Aug 2012 18:45:35 -0000 --9a9Vq1BJdYBEXpLG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Why did you stripped the public list from the Cc: ? On Fri, Aug 10, 2012 at 05:05:09PM -0400, Dan Plassche wrote: > On Fri, Aug 10, 2012 at 1:07 PM, Konstantin Belousov > wrote: >=20 > > Try to ktrace the binaries to see what is going on. I suspect that > > sources for 1.1.5 are not in our cvs/svn, so it is troublesome to > > say anuthing without ktrace dump. >=20 > Ok, below is the kdump from running basename as a simple example > that produces the "ld.so: whereis: libc.so.1.1" error under a > chrooted environment. >=20 > I probably should have mentioned that I'm running these with > "sysctl security.bsd.map_at_zero=3D1" set. The static binaries > in /bin and /sbin also work under the chroot, but the others in > /usr/bin and /usr/sbin fail with the ld.so error. You should have mentioned that it is only _some_ binaries which are affected, since I was not able to reproduce your issue at all with /bin/sh or /bin/ls in chroot. It took me a while to realize that you specifically shown the trace for basename. >=20 > Here's the kdump: > 1144 basename CALL > compat.mmap(0x2006b000,0x6bb8,0x7,0x122,0xffffffff,0x4d000) > 1144 basename RET compat.mmap -1 errno 22 Invalid argument And there is the problem, induced by more strict check added in r205536. Try the patch below, it could be applicable to 8.2 still. It worked for me on HEAD. diff --git a/sys/vm/vm_mmap.c b/sys/vm/vm_mmap.c index 3fccd9e..e89d586 100644 --- a/sys/vm/vm_mmap.c +++ b/sys/vm/vm_mmap.c @@ -207,11 +207,24 @@ sys_mmap(td, uap) =20 fp =3D NULL; =20 - /* Make sure mapping fits into numeric range, etc. */ - if ((uap->len =3D=3D 0 && !SV_CURPROC_FLAG(SV_AOUT) && - curproc->p_osrel >=3D P_OSREL_MAP_ANON) || - ((flags & MAP_ANON) && (uap->fd !=3D -1 || pos !=3D 0))) - return (EINVAL); + /* + * Enforce the constraints. + * Mapping of length 0 allowed for old binaries. + * + * Anonymous mapping shall specify -1 as filedescriptor and + * zero position for new code. Be nice to ancient a.out + * binaries and correct pos for anonymous mapping, since old + * ld.so sometimes issues anonymous map requests with non-zero + * pos. + */ + if (!SV_CURPROC_FLAG(SV_AOUT)) { + if ((uap->len =3D=3D 0 && curproc->p_osrel >=3D P_OSREL_MAP_ANON) || + ((flags & MAP_ANON) !=3D 0 && (uap->fd !=3D -1 || pos !=3D 0))) + return (EINVAL); + } else { + if ((flags & MAP_ANON) !=3D 0) + pos =3D 0; + } =20 if (flags & MAP_STACK) { if ((uap->fd !=3D -1) || --9a9Vq1BJdYBEXpLG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAmqEIACgkQC3+MBN1Mb4i2hACgrcmc3VuTWvy54u+rHNlz3O6W ZOUAnRiKMPAMlhGABKtEWp0avYZo+fUl =mq/V -----END PGP SIGNATURE----- --9a9Vq1BJdYBEXpLG-- From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 11 20:35:48 2012 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 84BD8106566B; Sat, 11 Aug 2012 20:35:48 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 75B5E8FC15; Sat, 11 Aug 2012 20:35:47 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1014171bkc.13 for ; Sat, 11 Aug 2012 13:35:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=EnSm6tcg/NXuPVavYDPRNTnpvLCj+1VeEimWlRv/hu8=; b=lp8XAW/jijKTptQTJBfQxoRp2pDxsGqUgaUl6jIEFAU5Ywgwm4dzFUjmw3PSoL7Pqy aZkwpOGHZzwEIJcMADnba1hNLbh0tcUKT2o99p9lXEYHfjcCA/iXeNF0+2RZFRulgC5C vzFp5HfcH+0d9U6i84KChG9OQK+roCX3OHxYPFHY/L0uTlo2nDemeg4XbvzvwYgFKFIu gV7wAcaibwpaK+mP7X/UPmCKYo4Y8xiBCBVGS2/5EljFvzft0lereBfD1zbiLuOju3cn quqFqOdp3AIFS1/6xyWpDHIoKwCHk9m2DutgY9TN1jOhmDsrHKMo/XTdZ/Fbw62zNeUs ICvw== Received: by 10.204.152.27 with SMTP id e27mr2520344bkw.56.1344717346095; Sat, 11 Aug 2012 13:35:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.231.7 with HTTP; Sat, 11 Aug 2012 13:35:15 -0700 (PDT) In-Reply-To: References: <4FFA3890.5060207@freebsd.org> From: Chris Rees Date: Sat, 11 Aug 2012 21:35:15 +0100 Message-ID: To: David Xu Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, Alex Kozlov , pho@freebsd.org Subject: Re: port devel/doxygen failing to test on -CURRENT and -STABLE 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, 11 Aug 2012 20:35:48 -0000 On 12 July 2012 18:52, Chris Rees wrote: > On 9 July 2012 02:49, David Xu wrote: >> On 2012/07/08 18:21, Chris Rees wrote: >>> >>> Hi all / David, >>> >>> doxygen has been failing for a while now on -CURRENT and apparently >>> -STABLE too. The current fix is disabling one of the tests in the >>> build, but obviously it points to a problem with our base system.... >>> >>> I've trussed [1] the failing code [2], and it looks as though it's >>> hanging on a _umtx call. I'm gratuitously ignorant of what goes on >>> there... but the timings of recent commits to umtx.h [3] could >>> indicate a link (hope it's not bogus...). >>> >>> Any pointers on what I should do next? >>> >>> Chris >>> >>> [1] http://www.bayofrum.net/~crees/scratch/doxygen-truss >>> >> _umtx_op(0x8012b0280,0x16,0x0,0x0,0x0,0x1) ERR#22 'Invalid argument' >> >> can you execute it in gdb and print its value ? >> >> print/x *(int *)0x8012b0280 >> print/x *(int *)(0x8012b0280+4) > > I've been having trouble debugging it since it's threaded, and so I > ran a binary search over the last few days of revisions from 1/Apr to > 1/May. > > Unfortunately I discovered to my horror today that all but the first > test was useless, because the patch I committed to disable the test > was of course readded to my ports tree, so none of the tests ran :/ > > I'll hopefully have it narrowed down to the offending commit over the > next few days. Extremely late now, I know; these tests take ages, and I've been dragged away on holiday. I've narrowed it down to cvsup checkout between 00:00 6/April and 12:00 6/April, which I assume corresponds to r233932-r233945. The only major change that I could see is melifaro's bpf changes in r233937; not sure why this test could use bpf. I'll keep digging, and I may owe you (David) an apology ;) Chris