From owner-freebsd-hackers@freebsd.org Sun Jan 3 09:55:58 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 580C4A6018A; Sun, 3 Jan 2016 09:55:58 +0000 (UTC) (envelope-from ilya@bakulin.de) Received: from olymp.kibab.com (olymp6.kibab.com [IPv6:2a01:4f8:160:84c1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 08BE51A28; Sun, 3 Jan 2016 09:55:57 +0000 (UTC) (envelope-from ilya@bakulin.de) DKIM-Filter: OpenDKIM Filter v2.10.3 olymp.kibab.com DBCC14E76D DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bakulin.de; s=default; t=1451814955; bh=4nY1rmF6ktwUoLOILKZ5CojkbAO06M52FQHmtyIJKDE=; h=Subject:References:Cc:To:From:Date:In-Reply-To; b=eEJYuw7UpRFFgM+2I0Z71x762hUfC+2BO6x8sNtQHGe1la/1OOzN4/Bb3EFxFPWq5 cjrZ3lKHXVPRhFB6KGlhl3vroR858cPDh6+DuoGREE1s9SquZdUjPPD62XXmHouCyH 4lPrr6LUF0kUjqk13difA9Qg2clMkQxEiOQB7HlY= Subject: Re: MMC/SDIO stack under CAM References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> Cc: Adrian Chadd , Alexander Motin , "freebsd-arm@freebsd.org" , Warner Losh To: "freebsd-hackers@freebsd.org" From: Ilya Bakulin X-Enigmail-Draft-Status: N1110 Message-ID: <5688F015.4090002@bakulin.de> Date: Sun, 3 Jan 2016 10:55:33 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdKPQb5BR1laisQxTkM8FwTwAWJqK4t22" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 09:55:58 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --sdKPQb5BR1laisQxTkM8FwTwAWJqK4t22 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable So, more than one year has passed, and I'd like to resurrect this work and move forward. I have uploaded a new diff and created a completely new revision to track the development: https://reviews.freebsd.org/D4761 What it is able to do now: * Read/write on SD/SDHC/MMC cards! * Detect SDIO cards and create devices that correspond to SDIO functions This all works only on BeagleBone currently, because some changes need to be done in each SDHCI-compliant driver to make it interact with CAM. I have purchased a Wandboard Quad that has an integrated SDIO WiFi chip, so I hope to tweak its SDHCI driver as well. I haven't profiled the stack because: * Now we have only SD/MMC cards that are slow anyway; * I don't know how to do it in FreeBSD :-) Please review this diff and tell what you think! On 01/03/14 18:05, Adrian Chadd wrote: > On 1 March 2014 08:46, Ilya Bakulin wrote: >> Hi Adrian, >> >> On 24.02.14, 16:59, Adrian Chadd wrote: >>> hi, >>> >>> Let me just reiterate some .. well, experience doing this stuff at QC= A. >>> >>> You really, absolutely don't want too much overhead in the MMC/SDIO >>> path between whatever is issuing things and the network driver. >>> >>> There was significant performance work done at QCA on a local MMC/SDI= O >>> driver and bus to get extremely low latency and CPU utilisation when >>> pushing around small transactions. The current CAM locking model is >>> not geared towards getting to high transaction rates. >> So here you mean some work done on Linux MMC/SDIO stack by QCA >> which made it far better than current Linux MMC stack in terms of >> high SDIO I/O rates? > Yup. The stock MMC stack/driver in Linux wasn't "fast" enough at small > transactions to sustain the wifi speeds customers required. > >>> You may think this is a very architecturally pretty solution and it >>> indeed may be. But if it doesn't perform as well as the existing loca= l >>> hacks that vendors have done, no company deploying this hardware is >>> going to want to use it. They'll end up realising there's this massiv= e >>> CAM storage layer in between and either have to sit down to rip it up= >>> and replace it with something lightweight, or they'll say "screw it" >>> and go back to the vendor supplied hacked up Linux solution. >> I think that if the "architecturally pretty solution" behaves worse th= an >> some ugly hacks, then it may be not so pretty or the architecture is >> just broken >> by design. >> >>> So I highly recommend you profile things - and profile things with >>> lots of small transactions. If the CAM overhead is more than a tiny, >>> tiny fraction of CPU at 25,000 pps, your solution won't scale. :-) >> I don't really know what to compare with. For MMC/SD cards it is prett= y >> obvious, but then these cards will be likely the bottleneck, not the s= tack. >> And the only goal would be to not make the stack slower than it is now= =2E >> But, as ATA devices are much faster than MMC/SD, I don't think this wi= ll >> be a problem. >> >> For SDIO things are different. But we don't have any drivers (yet), ex= cept >> mv_sdiowl that I'm writing, to test on. So I have to bring the SDIO >> stack on CAM, >> than bring mv_sdiowl to the state when it can actually transmit the >> data, and then >> compare performance with the vendor-supplied Linux driver. >> We'll see then if there is a room for improvement... > That sounds like a plan. > > Just note that although storage looks like it's doing much more > throughput, the IO size also matters. As I said above, it's not > uncommon to have > 1000 receive frames a second on 802.11n; and that > can peak much higher than that. That's not the kind of IO rate you see > on SD cards. :-) > > > > -a > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" > --=20 Regards, Ilya Bakulin --sdKPQb5BR1laisQxTkM8FwTwAWJqK4t22 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlaI8BsACgkQo9vlj1oadwjUfACguMrOckb94Xll9QDLznZg3WAJ BS4AoPJnEHpH3gg/0+voWbDOQ017IHs+ =gbnk -----END PGP SIGNATURE----- --sdKPQb5BR1laisQxTkM8FwTwAWJqK4t22-- From owner-freebsd-hackers@freebsd.org Sun Jan 3 10:00:56 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9901DA605BE; Sun, 3 Jan 2016 10:00:56 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 953571E2E; Sun, 3 Jan 2016 10:00:55 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pf0-x22a.google.com with SMTP id 78so188206888pfw.2; Sun, 03 Jan 2016 02:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5s8UiRE627CkJHK8lj0z9ZF0Qz9fbGVlbxWKDs2/wlY=; b=KOFNG/u81c6Bm10K9DSNikUTLkFFLdzPRabS81Cw5OSD/Q+Y0pkdAGmB1YTXjpeCek MU18+I2q3iVadgx2eVb7d/h6hIe6icc0wXoOusEFNsQOYb8eXIHoYXFrTtEY+B+fxhso NRLfehH0eamCedlypfuGp33dIgRGhAwzgQCdWbIgMY3qfviMKD34ucTpw56QI8cnWsCa ILoiUDBvxgoMS4seuMFHQuUt+tao5cF7oVcdcgmEHV5EXCq5EcLGqDv9h8STl2xXxJ6c CpnzVBVOs+itsjyuDe2KX7f9Oh8GeTBhOHMRRkvXv9mvFTAv/wpl+M7dOk947pAMqw+V nwnQ== X-Received: by 10.98.9.2 with SMTP id e2mr118170135pfd.89.1451815255039; Sun, 03 Jan 2016 02:00:55 -0800 (PST) Received: from [192.168.20.7] (c-24-16-212-205.hsd1.wa.comcast.net. [24.16.212.205]) by smtp.gmail.com with ESMTPSA id t76sm82259533pfi.26.2016.01.03.02.00.53 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 03 Jan 2016 02:00:53 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: MMC/SDIO stack under CAM From: NGie Cooper In-Reply-To: <5688F015.4090002@bakulin.de> Date: Sun, 3 Jan 2016 02:00:52 -0800 Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Alexander Motin , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> <5688F015.4090002@bakulin.de> To: Ilya Bakulin X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 10:00:56 -0000 > On Jan 3, 2016, at 01:55, Ilya Bakulin wrote: >=20 > So, more than one year has passed, and I'd like to resurrect this work > and move forward. >=20 > I have uploaded a new diff and created a completely new revision to > track the development: https://reviews.freebsd.org/D4761 >=20 > What it is able to do now: >=20 > * Read/write on SD/SDHC/MMC cards! > * Detect SDIO cards and create devices that correspond to SDIO = functions >=20 > This all works only on BeagleBone currently, because some changes need > to be done in each SDHCI-compliant driver to make it interact with = CAM. > I have purchased a Wandboard Quad that has an integrated SDIO WiFi = chip, > so I hope to tweak its SDHCI driver as well. >=20 > I haven't profiled the stack because: > * Now we have only SD/MMC cards that are slow anyway; > * I don't know how to do it in FreeBSD :-) As for =93I don=92t know how=85=94, please take a look at the wiki pages = on dtrace: https://wiki.freebsd.org/DTrace . ktr might be helpful as = well... Cheers! -NGie= From owner-freebsd-hackers@freebsd.org Sun Jan 3 13:38:34 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EDD6A5F3BA for ; Sun, 3 Jan 2016 13:38:34 +0000 (UTC) (envelope-from robbinsondefau@gmail.com) Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F2D9E18A4 for ; Sun, 3 Jan 2016 13:38:33 +0000 (UTC) (envelope-from robbinsondefau@gmail.com) Received: by mail-ig0-x234.google.com with SMTP id ik10so63172349igb.1 for ; Sun, 03 Jan 2016 05:38:33 -0800 (PST) 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=+OtP97j88XAAqxT45lcGkxBxGqCtpR8Ofi/F6af7dWI=; b=WG3l7X0UvbvcF1JTJ4yPmEbRc79lUdimcQMQ5FJ7Ux0hkK+KXlAL/t0EmXQGNOqQ+l oFFheiPAgpTGfe0KJOw/CLCp0EyPSVQSvBBf/a4N5OKcGy0iSPQ+Ro7GmqM823jgK1S4 Oo15o2KvYF7EpKSOzTNoaqsRE5L2ucwVkognCOhJznWtGxhOQXtVMpwDb705xaxB8/Yh fea7gMBoXsUX0KqCO24Pjek2oEAXjmmnQ8Vd8H2d55xD3FHTsVN+lY6k0Ylfb8p0KGZT py9XKuaOwRmkb0kb0xmzbj3LNWlxgH8ROhnotL26Xpwd5QyvZnhKFStboP2ntVxQxNRE Ok/Q== MIME-Version: 1.0 X-Received: by 10.50.147.73 with SMTP id ti9mr18851630igb.36.1451828313369; Sun, 03 Jan 2016 05:38:33 -0800 (PST) Received: by 10.36.29.20 with HTTP; Sun, 3 Jan 2016 05:38:33 -0800 (PST) Date: Sun, 3 Jan 2016 14:38:33 +0100 Message-ID: Subject: variables optimized out From: robbinson defau To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Sun, 03 Jan 2016 13:57:17 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 13:38:34 -0000 Hi all, Im debugging some issues in the kernel and as the kernel is compiled by default with -O2, a lot of variables are optimized out. So i made changes to make.conf (CFLAGS and COPTFLAGS).\ All builds fine, but I get the weirdest of panics that most certainly not happen with -O2. So it's likely i'm doing something wrong. What would be the correct way to be able to debug the kernel and have it build such that locals and function arguments are not optimized out? Thanks in advance, /DF From owner-freebsd-hackers@freebsd.org Sun Jan 3 14:31:08 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE9CFA60308 for ; Sun, 3 Jan 2016 14:31:08 +0000 (UTC) (envelope-from kah@kahnews.net) Received: from nl.kahnews.net (nl.kahnews.net [IPv6:2a01:7c8:aab0:4bb::2001]) by mx1.freebsd.org (Postfix) with ESMTP id BEABD1378 for ; Sun, 3 Jan 2016 14:31:08 +0000 (UTC) (envelope-from kah@kahnews.net) Received: from [192.168.1.20] (cm-84.215.48.116.getinternet.no [84.215.48.116]) by nl.kahnews.net (Postfix) with ESMTPSA id 7E4AEAB4F6 for ; Sun, 3 Jan 2016 15:30:58 +0100 (CET) Subject: Re: variables optimized out To: freebsd-hackers@freebsd.org References: From: "Kristian A. Hiorth" Message-ID: <568930A0.6010405@kahnews.net> Date: Sun, 3 Jan 2016 15:30:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 14:31:09 -0000 On 01/03/2016 02:38 PM, robbinson defau wrote: > Hi all, > > Im debugging some issues in the kernel and as the kernel is compiled by > default with -O2, a lot of variables are optimized out. So i made changes > to make.conf (CFLAGS and COPTFLAGS).\ > > All builds fine, but I get the weirdest of panics that most certainly not > happen with -O2. So it's likely i'm doing something wrong. What would be > the correct way to be able to debug the kernel and have it build such that > locals and function arguments are not optimized out? > > Thanks in advance, > > /DF Hi, sounds like stack overflows, did you try increasing kernel stack size? Stuff like WITNESS causes a lot of stack growth when the optimizer inlines fewer calls. I've run an -O0 kernel with options KSTACK_PAGES=6 without too many problems. Hope this helps, Kristian From owner-freebsd-hackers@freebsd.org Sun Jan 3 14:59:34 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3475CA60EE6 for ; Sun, 3 Jan 2016 14:59:34 +0000 (UTC) (envelope-from lists@bertram-scharpf.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.75]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 875E319E6 for ; Sun, 3 Jan 2016 14:59:32 +0000 (UTC) (envelope-from lists@bertram-scharpf.de) Received: from becker.bs.l ([85.180.10.248]) by mrelayeu.kundenserver.de (mreue101) with ESMTPSA (Nemesis) id 0LfzrP-1ZruZr3oXD-00pd7q for ; Sun, 03 Jan 2016 15:59:25 +0100 Received: from bsch by becker.bs.l with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1aFk7v-000851-Mn for freebsd-hackers@freebsd.org; Sun, 03 Jan 2016 15:59:23 +0100 Date: Sun, 3 Jan 2016 15:59:23 +0100 From: Bertram Scharpf To: freebsd-hackers@freebsd.org Subject: Re: variables optimized out Message-ID: <20160103145923.GA16970@becker.bs.l> Mail-Followup-To: freebsd-hackers@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: Bertram Scharpf X-Provags-ID: V03:K0:NpDXK0W4a/c7Q45JA6jTnl0mzLSh6vQKPxuL5t1K9rPRNxCJyWq 0BCKGh5SHedZJ9Kqq5eNwBs1V/uJ/wWpBlcPrPFyZFn4LVquWPCarKVvRrm4p4sB5/1TkvR PiA/hPtMlkIZP40apw5sA/+gYAGBfc8GL7YmTuW6klMkG9cXo4AY2r0tH/yybCo3wspp5pE IRkJfGdPqBzju+5schb2w== X-UI-Out-Filterresults: notjunk:1;V01:K0:tQenCKCz1ik=:FwYQhEw4aHD/3F8NDs92dd 3qKi1/MMeAaalMZxbCjLK0kjksP9LvVZK0Gm7NE4lwJkyaCN0DC3qT6nVdvyDUQzZUact97Zy xWj1P4fYbeJvswKfycXyWUbKWHesSfPIpd+9r6huLhBDl55GMBPbUjdgQynXoFMK2Li7bMcgS JPmjCcUwn4L5ET3h8iI6tM6gaw2aosmwxYQL9D7yiARkiHvmNhSKcm+Y63rnfTTd4D11oTOiv ogdNNFmjzF2lzaNdNrU0leausgqsyBw9PSd7cAsYI5urxhSJAFgXtvjZfjCPR6Rur1V4VLxkz Ov/cB1UYGrBUxDm9ZxsffZZvhlvLAEeOLyMIj4gVU9/zzKtLhzWC4Gg/bOFXrLCChwFOWCiUV Rshbh5KGSN2DLRzkpeCi6J/u3NHA4N42h4/T6taHvnOk71b8WXb7c7HRfpnmt73HAWfEad6Nx H+6xk07ePAHYhB5Vl5lY+3dxVuAXjdJ9h07Ih45Sx7nGG76Y1kP+QlJiiA75MhbwAGIrowMXL B+cAmJF6JWvm8G/Gh1gxtNqdNJ8aaspUh+QMiaV6b62rhpKvn08B7XWxmw+Tcp8Ihs2SK1W+k jkCAJyPpCx/AbkjAJqqcCsizVXgKLkAe0JXp280oSZ0t86Ip6pQizHSJLUMq/l2if+T5KNty5 6nE2DI95uM4TBDads6csKiTOL1VXAnLxhiXLQlZmalxQRjlY1Tvep0WWLlD7ft7sBSzk= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 14:59:34 -0000 Hi, On Sunday, 03. Jan 2016, 14:38:33 +0100, robbinson defau wrote: > Im debugging some issues in the kernel and as the kernel is compiled by > default with -O2, a lot of variables are optimized out. So i made changes > to make.conf (CFLAGS and COPTFLAGS).\ >=20 > All builds fine, but I get the weirdest of panics that most certainly not > happen with -O2. [...] I just had a look at "man make.conf" and that says: CFLAGS (str) Controls the compiler setting when compiling C code. Optimization levels other than -O and -O2 are not sup=E2=80=90 ported. At least to me this is a surprise. I'm really disappointed about what programming style has become common. Bertram --=20 Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de From owner-freebsd-hackers@freebsd.org Sun Jan 3 16:23:18 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8753DA60B28 for ; Sun, 3 Jan 2016 16:23:18 +0000 (UTC) (envelope-from stoa@gmx.us) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E354518B3 for ; Sun, 3 Jan 2016 16:23:17 +0000 (UTC) (envelope-from stoa@gmx.us) Received: from archlinux ([24.116.197.15]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MFi1J-1aTqRq0Dzx-00EcAg for ; Sun, 03 Jan 2016 17:23:15 +0100 Date: Sun, 3 Jan 2016 10:23:05 -0600 From: Dutch Ingraham To: freebsd-hackers@freebsd.org Subject: Re: variables optimized out Message-ID: <20160103162304.GA456@archlinux> References: <20160103145923.GA16970@becker.bs.l> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160103145923.GA16970@becker.bs.l> User-Agent: Mutt/1.5.24 (2015-08-30) X-Provags-ID: V03:K0:yxZfAYqBUsAiRlYAsyVsIEj+CzCVg2zhjDtdQIP8SGNoCDF+1ci +e/bVVSA2/bADKd8qC9Bylmd/VLls9rh37FTWwGQaITntiMaq3JoaHvvBWPzIyid92ZXHvL ATAunzVtnd2gqctVbP3XqpM+3GH14i3jV2aWOk1h5h8KY6k+NOO++AohvB8qthvveiXcRaS Qs89UO1SnxfbOryoc1VhQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:YyDTy63TZWs=:e28rE2iKfHdkQyl0mpEHhM rInNWTl32MCn0KoX/9ex19qdQ1yrFMsKhSCZGUpS2RERwe5bwhuo1PLShvbFBzCgG/5Mr9DfS KDCm6+dWF4ggkT4GUoji1gwqMrlxZJWKC0+SljJOBmITUsBs+vRpoWASV2wF72IKy9KBQlfO4 L4cju7NaUlJ1KzmRIgZGJQLB6vw/yVGBmLp7XS2pliRiXQjR3/3PKYgBbCYJh4S8cIDTBaQFg /oHMKXOv1qWYm5gkShn17xnkcqVihcrr4+Ph/LjysZwsefw+wmfFFnNiF9GQYBlU0jMqQyMtP Lo5HIQbYwjgPYlHEyuqY7EtZ8Jkp5ae+VX3yNOhaViuBBZb7YKDiT1bql2A+B2KvJ9469I1oi qgbpAMsS+aUTadh0XAlRsEXYLjN+mGVp0p+2IMQJDuMU6vK0jSxO/bwaAeHrfnPurSzq82e+f mw9A7jM0+aeh56eUjfspfKWjSR6UFXS/ruB5/VXOzeT89SJKvYHA8mi0kyVAfWAmfpO9Hsnz0 TuJREijd0wdmuD0OoriHaTFVOPIPxN1xGOEFYVSISpaIcnyJMDnSwgOV/IvuHdPLLMx7UtYwf DXmjebS5i3UMDWHdYyAlBOUymS68sXgoiMIROeThbfHaGUOTdkLQ/Rj8/sjP3yYbMbyxNjpy/ 38JEBg/gAHmLRPmH6PuEcSoDJFpE90tjrD9Ot0uJtm7EYzOwj4JEPKUA9tRbvhDz81QYkmphe PoLgSCPMry0DKbipeHIYoebRMm3U7HyT2PMBSKng6rhXisbMIfyWUFjroHg= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 16:23:18 -0000 On Sun, Jan 03, 2016 at 03:59:23PM +0100, Bertram Scharpf wrote: > > I just had a look at "man make.conf" and that says: > > CFLAGS (str) Controls the compiler setting when compiling C code. > Optimization levels other than -O and -O2 are not sup‐ > ported. > > At least to me this is a surprise. I'm really disappointed > about what programming style has become common. > > Bertram > I'm not sure what you mean by "programming style," but this optimization restriction seems limited to Freebsd and some of its derivatives. [1][2] [1] https://dev.gentoo.org/~zmedico/portage/doc/man/make.conf.5.html [2] https://www.dragonflybsd.org/cgi/web-man?command=make.conf§ion=5 From owner-freebsd-hackers@freebsd.org Sun Jan 3 16:57:29 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06719A5FA43 for ; Sun, 3 Jan 2016 16:57:29 +0000 (UTC) (envelope-from robbinsondefau@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CCA8D1FCD for ; Sun, 3 Jan 2016 16:57:28 +0000 (UTC) (envelope-from robbinsondefau@gmail.com) Received: by mail-io0-x229.google.com with SMTP id 1so91152778ion.1 for ; Sun, 03 Jan 2016 08:57:28 -0800 (PST) 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=co0OTRC8mK+TFCMdXHMKcjDbKbSsHxJo7hjcmXhKX30=; b=KpwYBk2XbgLaOhApKBIF3v2LgEGJSyysuBMsUcKHcktBPPLyeAPKwvzVqXk/dbez3s RR+I9huWXEEGKgYyU5ko9YwesnM0PWgsc1z2sorrgf580Oc65kcNYAFXsmpeew306VPt mytnIAQ5MYT23Hrr1/6++abLwT0E2qNHPipmvLfCePJCsFYAftdsX/zjMeky4sc7pqSK iLkm/oaviIZUFybnIP/B4r/1sJiyDg1Pm7iboa1r3iOI11Bp6wiQ9MC8CvFrchR8IKbQ /gSxPAkKMr2D0LHp49B25x1rQUJOD4sEWduytdTECIrKSemlbwe5tOEF1nsjk4qDoZQX WoLA== MIME-Version: 1.0 X-Received: by 10.107.166.78 with SMTP id p75mr72072970ioe.59.1451840248270; Sun, 03 Jan 2016 08:57:28 -0800 (PST) Received: by 10.36.29.20 with HTTP; Sun, 3 Jan 2016 08:57:28 -0800 (PST) In-Reply-To: <568930A0.6010405@kahnews.net> References: <568930A0.6010405@kahnews.net> Date: Sun, 3 Jan 2016 17:57:28 +0100 Message-ID: Subject: Re: variables optimized out From: robbinson defau To: "Kristian A. Hiorth" Cc: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Sun, 03 Jan 2016 17:40:39 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 16:57:29 -0000 Hi, That seems to help a lot. Thanks for the info! /DF On Sun, Jan 3, 2016 at 3:30 PM, Kristian A. Hiorth wrote: > On 01/03/2016 02:38 PM, robbinson defau wrote: > >> Hi all, >> >> Im debugging some issues in the kernel and as the kernel is compiled by >> default with -O2, a lot of variables are optimized out. So i made changes >> to make.conf (CFLAGS and COPTFLAGS).\ >> >> All builds fine, but I get the weirdest of panics that most certainly not >> happen with -O2. So it's likely i'm doing something wrong. What would be >> the correct way to be able to debug the kernel and have it build such that >> locals and function arguments are not optimized out? >> >> Thanks in advance, >> >> /DF >> > > Hi, > > sounds like stack overflows, did you try increasing kernel stack size? > Stuff like WITNESS causes a lot of stack growth when the optimizer inlines > fewer calls. > > I've run an -O0 kernel with > options KSTACK_PAGES=6 > > without too many problems. > > Hope this helps, > Kristian > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://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 Jan 3 18:11:49 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9CF80A606D7 for ; Sun, 3 Jan 2016 18:11:49 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4187C1A7C for ; Sun, 3 Jan 2016 18:11:48 +0000 (UTC) (envelope-from joerg@britannica.bec.de) X-RZG-AUTH: :JiIXek6mfvEEUpFQdo7Fj1/zg48CFjWjQuEfXeSt/nWoxNEod/GGOF9MfA4zuWcD X-RZG-CLASS-ID: mo00 Received: from britannica.bec.de ([37.203.150.109]) by smtp.strato.de (RZmta 37.15 AUTH) with ESMTPSA id V071d8s03IBjcAT (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Sun, 3 Jan 2016 19:11:45 +0100 (CET) Date: Sun, 3 Jan 2016 19:11:39 +0100 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Subject: Re: variables optimized out Message-ID: <20160103181139.GA16659@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20160103145923.GA16970@becker.bs.l> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160103145923.GA16970@becker.bs.l> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 18:11:49 -0000 On Sun, Jan 03, 2016 at 03:59:23PM +0100, Bertram Scharpf wrote: > Hi, > > On Sunday, 03. Jan 2016, 14:38:33 +0100, robbinson defau wrote: > > Im debugging some issues in the kernel and as the kernel is compiled by > > default with -O2, a lot of variables are optimized out. So i made changes > > to make.conf (CFLAGS and COPTFLAGS).\ > > > > All builds fine, but I get the weirdest of panics that most certainly not > > happen with -O2. [...] > > I just had a look at "man make.conf" and that says: > > CFLAGS (str) Controls the compiler setting when compiling C code. > Optimization levels other than -O and -O2 are not sup‐ > ported. > > At least to me this is a surprise. I'm really disappointed > about what programming style has become common. There are two strong historical reasons from GCC behavior: - a lot of the -O3 optimisations has been known to break questionable code - a lot of the warnings significantly change behavior depending on the optmizer. While the former is not a big problem for disabling optimisation, the latter certainly is. Note that with clang there is no difference between -O and -O2. Joerg From owner-freebsd-hackers@freebsd.org Sun Jan 3 18:24:46 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79F4AA60ACD for ; Sun, 3 Jan 2016 18:24:46 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 51A3E1245 for ; Sun, 3 Jan 2016 18:24:46 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pa0-x22c.google.com with SMTP id uo6so165256014pac.1 for ; Sun, 03 Jan 2016 10:24:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ue5rSjH5+6PBb9BDU8hVUi3FXBoeY0EFFXqaOrj107Y=; b=tPIdVaZtpcd7KwNYLHSj+aO7hiNngs3L/gj9+PGTkobXPIwX3D2Xd2p8VNzdCg6dDB F4OxDcg4QkzQP1bGnfXOi+Ct273z9E9onzTmTJQ2+CS2lsFYynFxK4mWUqXgdtI9amIx lSKfRwvLN1yIls2QCDES58CO/ehy9/B582HQ8HG1u+A4QVB/RTuzRH2wX5UMtMFu6Bzc VlJx/cKnVGSlOGXwO1438OyTKbGMvfMw4hpbPFqSIR25IzRZStKBRWeI67aZ+VTa8Bhp zoMDBSGbG+SEGFpPL6lK2tggJRX1KV06kZglgfJmUCoK3lO1Q/U5627vWqroamx2C8le 68wA== X-Received: by 10.66.55.66 with SMTP id q2mr54487937pap.120.1451845485929; Sun, 03 Jan 2016 10:24:45 -0800 (PST) Received: from [192.168.20.7] (c-24-16-212-205.hsd1.wa.comcast.net. [24.16.212.205]) by smtp.gmail.com with ESMTPSA id 71sm26223558pfh.4.2016.01.03.10.24.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 03 Jan 2016 10:24:44 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: variables optimized out From: NGie Cooper In-Reply-To: <20160103181139.GA16659@britannica.bec.de> Date: Sun, 3 Jan 2016 10:24:43 -0800 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <51901B1D-BCB2-4C9B-977C-C69E56C60A4D@gmail.com> References: <20160103145923.GA16970@becker.bs.l> <20160103181139.GA16659@britannica.bec.de> To: Joerg Sonnenberger X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 18:24:46 -0000 > On Jan 3, 2016, at 10:11, Joerg Sonnenberger = wrote: >=20 > On Sun, Jan 03, 2016 at 03:59:23PM +0100, Bertram Scharpf wrote: >> Hi, >>=20 >> On Sunday, 03. Jan 2016, 14:38:33 +0100, robbinson defau wrote: >>> Im debugging some issues in the kernel and as the kernel is compiled = by >>> default with -O2, a lot of variables are optimized out. So i made = changes >>> to make.conf (CFLAGS and COPTFLAGS).\ >>>=20 >>> All builds fine, but I get the weirdest of panics that most = certainly not >>> happen with -O2. [...] >>=20 >> I just had a look at "man make.conf" and that says: >>=20 >> CFLAGS (str) Controls the compiler setting when compiling C = code. >> Optimization levels other than -O and -O2 are not = sup=E2=80=90 >> ported. >>=20 >> At least to me this is a surprise. I'm really disappointed >> about what programming style has become common. >=20 > There are two strong historical reasons from GCC behavior: > - a lot of the -O3 optimisations has been known to break questionable > code > - a lot of the warnings significantly change behavior depending on the > optmizer. >=20 > While the former is not a big problem for disabling optimisation, the > latter certainly is. Note that with clang there is no difference = between > -O and -O2. Hi Joerg, We had some discussion on this a while ago internally at $work. = clang optimizes a lot of variables away and doesn=E2=80=99t track them = like later versions of gcc does (unfortunately 4.2.1 in base also lacks = this capability): https://llvm.org/bugs/show_bug.cgi?id=3D23636 (clang = lacks -ftracking[-assignments]). The only way you can reliably debug a = program today is to compile code with `DEBUG_FLAGS=3D"-g -O0=E2=80=9D`, = but that might change behavior of the code due to how it was optimized = (and it might make things less efficient), so caveat emptor. You will = definitely need to increase your stack space with the kernel for = instance. Hope this helps! -NGie= From owner-freebsd-hackers@freebsd.org Sun Jan 3 19:37:50 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A704A6007E for ; Sun, 3 Jan 2016 19:37:50 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0511C10A7 for ; Sun, 3 Jan 2016 19:37:50 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: by mail-io0-x229.google.com with SMTP id 77so108783555ioc.2 for ; Sun, 03 Jan 2016 11:37:50 -0800 (PST) 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=Nh+Ho4UaB14wh5U7xX+IspbJduERkc24I3R5utK69YY=; b=o//AFvYd1cu5o7XntjFwjAuA//gHZFHZAVh5wDSphac3mFq4xmdkLvLFx5ejJII3KR zpYQGgmaXCpzCPHlUT1spdGnPs97J3SBiM9YgXm/QeZKKTsxM4LhXZcybbi2TAhDo6tw 3xwXhfrBGcjrpEglM4nh90IxMYwsuNQ8+Fed/cof/tCa6PLjtvbPKI4BvgZ2dvQpT8qv zwKYXHXISVD9/sTeAF0siQ6gSDoErzFKHatUUqpwXI7z7JQMw9Ojmku+ppEI7t7p8ZWv n0Gy6mTM542qViz0vU1SzT3bhZQ9VexS02Vdk15dUnYYqSWaatuYYSqvnFCbIkKcSsCl FWSw== MIME-Version: 1.0 X-Received: by 10.107.31.17 with SMTP id f17mr21498095iof.68.1451849869391; Sun, 03 Jan 2016 11:37:49 -0800 (PST) Received: by 10.64.120.68 with HTTP; Sun, 3 Jan 2016 11:37:49 -0800 (PST) Date: Sun, 3 Jan 2016 11:37:49 -0800 Message-ID: Subject: Re: Getting a core dump of a process without killing it? From: Dieter BSD To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 19:37:50 -0000 Oliver Pinter helpfully replied: > Take a look at gcore command. Works great. Thank you. (Wondering why I didn't think to try man -k core?) From owner-freebsd-hackers@freebsd.org Mon Jan 4 01:17:33 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39C90A619CA for ; Mon, 4 Jan 2016 01:17:33 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E04641A74 for ; Mon, 4 Jan 2016 01:17:32 +0000 (UTC) (envelope-from tim@kientzle.com) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id u041Ibs3022906; Mon, 4 Jan 2016 01:18:37 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.112] (192.168.1.101 [192.168.1.101]) by kientzle.com with SMTP id 23nhcgus6xbav7yh5bvqhqfz3s; Mon, 04 Jan 2016 01:18:37 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: variables optimized out From: Tim Kientzle In-Reply-To: <20160103145923.GA16970@becker.bs.l> Date: Sun, 3 Jan 2016 17:17:16 -0800 Cc: Freebsd hackers list Content-Transfer-Encoding: quoted-printable Message-Id: <93DD470E-39F0-482E-B949-40C42234D779@kientzle.com> References: <20160103145923.GA16970@becker.bs.l> To: Bertram Scharpf X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jan 2016 01:17:33 -0000 > On Jan 3, 2016, at 6:59 AM, Bertram Scharpf = wrote: >=20 > Hi, >=20 > On Sunday, 03. Jan 2016, 14:38:33 +0100, robbinson defau wrote: >> Im debugging some issues in the kernel and as the kernel is compiled = by >> default with -O2, a lot of variables are optimized out. So i made = changes >> to make.conf (CFLAGS and COPTFLAGS).\ >>=20 >> All builds fine, but I get the weirdest of panics that most certainly = not >> happen with -O2. [...] >=20 > I just had a look at "man make.conf" and that says: >=20 > CFLAGS (str) Controls the compiler setting when compiling C = code. > Optimization levels other than -O and -O2 are not = sup=E2=80=90 > ported. >=20 > At least to me this is a surprise. I'm really disappointed > about what programming style has become common. This comment really just means that noone has stepped up to test the kernel when compiled with other settings and fix the problems uncovered by it. If you have time and skills to do so, I'm sure patches would be appreciated... Cheers, Tim From owner-freebsd-hackers@freebsd.org Tue Jan 5 05:14:29 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96FFFA617CD for ; Tue, 5 Jan 2016 05:14:29 +0000 (UTC) (envelope-from peterchencs@gmail.com) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5DEB61532 for ; Tue, 5 Jan 2016 05:14:29 +0000 (UTC) (envelope-from peterchencs@gmail.com) Received: by mail-ob0-x233.google.com with SMTP id pp16so3973766obb.2 for ; Mon, 04 Jan 2016 21:14:29 -0800 (PST) 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=yqzoc5Zkada1b1DiSfLlDZ88dVSVprJfc0u5bf3lJs4=; b=huwxccP0GomcUMcLRmdqRqrC7GgCr2h8eiIldUbBzGFsvfMokQjGpx6pl388AAr9Ug kJi5kmExv4c5I7DVNxDuYMbE/SRhDvyqyRwPuVTFIo6yi56jFNMJfzyqNVxwZ64Z8KST KEx0ay4gMPTN3SOW2IDuFRgonaA2VLQJVzY/L+RDRch6lyMPNIG255rairWUR4RbSZ3G PbTslKcAtemQIMb9+GcMnzz2dhDtNckJu+m9te7/MYBTlOKtk1B01CM6iQZ8gyeLSePH Vbdyr9VExKf8F2JaA4fNjMEBn2mn1Cy/UyuGRFl5Hwi4Im6tt/ockjQgzwDHUZ5q3cdD Ujuw== MIME-Version: 1.0 X-Received: by 10.182.106.198 with SMTP id gw6mr365960obb.11.1451970868674; Mon, 04 Jan 2016 21:14:28 -0800 (PST) Received: by 10.202.188.130 with HTTP; Mon, 4 Jan 2016 21:14:28 -0800 (PST) Date: Tue, 5 Jan 2016 00:14:28 -0500 Message-ID: Subject: Nginx Vulnerability on FreeBSD From: Peter Chen To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 05:14:29 -0000 Hi, I am trying to do a security research experiment on FreeBSD. I try to test the Nginx Vulnerability CVE-2013-2028 on FreeBSD x86-64, with Nginx 1.3.9/1.4.0. (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2028) However, most exploit samples can succeed on Linux, but not FreeBSD. The basic idea for the exploit, is to send a packet with a very large chunk size, making the victim process stack-overflow. After Nginx's many crashes, the attacker can find enough gadgets to launch a return-oriented programming attack. However, it is hard to let Nginx worker process crash (due to overwritten return address) on FreeBSD. Process crash is the first step of the whole exploit. I guess (probably a wrong guess) the reason may be: the exploit needs to set MTU to a large value. But FreeBSD seems only to allows a max MTU of 16110. It is probably because of other reasons. Any comments/suggestions on this, just to make the victim process crash? Here are two exploit code examples, which can run against Linux target, but fail to make the Nginx worker process crash on FreeBSD: http://www.scs.stanford.edu/brop/ http://www.scs.stanford.edu/brop/nginx-1.4.0-exp.tgz https://www.exploit-db.com/docs/27074.pdf http://seclists.org/fulldisclosure/2013/Jul/att-90/ngxunlock_pl.bin Thanks!! Best, Peter From owner-freebsd-hackers@freebsd.org Tue Jan 5 05:23:29 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 836F5A61B9C; Tue, 5 Jan 2016 05:23:29 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E352D1A76; Tue, 5 Jan 2016 05:23:28 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074423-f797f6d0000023d0-6d-568b521a4519 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id C1.FB.09168.A125B865; Tue, 5 Jan 2016 00:18:18 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id u055IHSh026145; Tue, 5 Jan 2016 00:18:18 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u055IE3m016669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jan 2016 00:18:17 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u055IEJB027470; Tue, 5 Jan 2016 00:18:14 -0500 (EST) Date: Tue, 5 Jan 2016 00:18:14 -0500 (EST) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Third call for 2015Q4 quarterly status reports In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOIsWRmVeSWpSXmKPExsUixCmqrSsV1B1mMOGBnsWua6fZLea8+cBk sX3zP0YHZo8Zn+azBDBGcdmkpOZklqUW6dslcGUce/CIreAeT8WzCz9YGhjXc3UxcnJICJhI 9Ny+yg5hi0lcuLeerYuRi0NIYDGTRPP006wQzgZGibtTYTIHmST+bN7GBtIiJFAvcauzE8jm 4GAR0JK4eSoKJMwmoCbxeG8zK8RURYnNpyYxg5SICMhLLDhvDxJmBjL/X7nMBGILC5hLPHz0 AuwITgEniR83HzOD2LwCjhLL3qxmhdjkKLG2aQ9YXFRAR2L1/iksEDWCEidnPmGBmKklsXz6 NpYJjEKzkKRmIUktYGRaxSibklulm5uYmVOcmqxbnJyYl5dapGuml5tZopeaUrqJERS+7C7K Oxj/HFQ6xCjAwajEw8vxsitMiDWxrLgy9xCjJAeTkigvk1d3mBBfUn5KZUZicUZ8UWlOavEh RgkOZiUR3jYjoBxvSmJlVWpRPkxKmoNFSZx37hffMCGB9MSS1OzU1ILUIpisDAeHkgTv7QCg RsGi1PTUirTMnBKENBMHJ8hwHqDhPIEgw4sLEnOLM9Mh8qcYFaXEec+BNAuAJDJK8+B6well N5PqK0ZxoFeEec1A2nmAqQmu+xXQYCagwW8q2kEGlyQipKQaGJe+7Ct6rWB1wynh7ebbJ443 uTP03woVYuhT6Pp9NX3myxQbn2rrJEGZAO/LS2LtUprl/0/002xLWbJ8n5L119D4vbsDbuh9 TJzD6iqeVRB74n6+qbmF1eTX07dc5/9rdZA5aW/92t0CEqWPZRg9loiovNaycI2vXn5SNt+w c2uH24a0kCMflFiKMxINtZiLihMBrnM3pwoDAAA= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 05:23:29 -0000 One last reminder -- less than a week remains to submit entries for the 2015Q4 report! -Ben On Mon, 28 Dec 2015, Benjamin Kaduk wrote: > Dear FreeBSD Community, > > There are less than two weeks left before the deadline for the next > FreeBSD Quarterly Status update -- submissions are due on January 7, 2016, > for work done in October through December. > > Status report submissions do not have to be very long. They may be about > anything happening in the FreeBSD project and community, and provide a > great way to inform FreeBSD users and developers about what you're working > on. Submission of reports is not restricted to committers. Anyone doing > anything interesting and FreeBSD-related can -- and should -- write one! > > The preferred and easiest submission method is to use the XML generator > [1] with the results emailed to the status report team at monthly at > freebsd.org . There is also an XML template [2] which can be filled out > manually and attached if preferred. For the expected content and style, > please study our guidelines on how to write a good status report [3]. > You can also review previous issues [4][5] for ideas on the style and > format. > > We are looking forward to all of your 2015Q4 reports! > > Thanks, > > Ben (on behalf of monthly@) > > [1] http://www.freebsd.org/cgi/monthly.cgi > [2] http://www.freebsd.org/news/status/report-sample.xml > [3] http://www.freebsd.org/news/status/howto.html > [4] http://www.freebsd.org/news/status/report-2015-04-2015-06.html > [5] http://www.freebsd.org/news/status/report-2015-07-2015-09.html > > From owner-freebsd-hackers@freebsd.org Tue Jan 5 05:49:43 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9BB8A62580 for ; Tue, 5 Jan 2016 05:49:42 +0000 (UTC) (envelope-from henry.hu.sh@gmail.com) Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AAA111A4D for ; Tue, 5 Jan 2016 05:49:42 +0000 (UTC) (envelope-from henry.hu.sh@gmail.com) Received: by mail-qg0-x234.google.com with SMTP id o11so271540484qge.2 for ; Mon, 04 Jan 2016 21:49:42 -0800 (PST) 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=AbssWPqDYjQpF9NYg1Yt9DrxRgHlwVcGe8Wq7Db9Okk=; b=V0KmcNFbQrpzgkdLdO9gk8XjiF0yPcgKEEverr8bL5/WWZfVtYo92b8xoZef3NBHKt ixU5g5J68G9WT7R8LPuWmYyC2KRbB2tJYipLxHA3kd4T5dLp0jEHMF4BTY+D20nVhMNt RfR34oDRh0smKyb+dDjta9TyJ7RqMnq7mj5oDKjUjpxt8j1xG1ei3xXWkMTJpasb1sOD H46wAgI2JZMz0jNMLudR2m4621d3RnJI2q+fKi/nCvsaTBt4sFbqOdVXC2NEgoSoQCjR oqSXlvhP7KK6ZCFXZDuRJC67bA4h9mjAHWDMOp81BFUBO86B2WP3uBTJ7sfR99mGD3uW NBPA== X-Received: by 10.140.142.207 with SMTP id 198mr117565300qho.77.1451972981663; Mon, 04 Jan 2016 21:49:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.81.198 with HTTP; Mon, 4 Jan 2016 21:49:02 -0800 (PST) In-Reply-To: References: From: Henry Hu Date: Tue, 5 Jan 2016 00:49:02 -0500 Message-ID: Subject: Re: Nginx Vulnerability on FreeBSD To: Peter Chen Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 05:49:43 -0000 On Tue, Jan 5, 2016 at 12:14 AM, Peter Chen wrote: > Hi, > > I am trying to do a security research experiment on FreeBSD. > I try to test the Nginx Vulnerability CVE-2013-2028 on FreeBSD x86-64, with > Nginx 1.3.9/1.4.0. > (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2028) > > However, most exploit samples can succeed on Linux, but not FreeBSD. > The basic idea for the exploit, is to send a packet with a very large chunk > size, making the victim process stack-overflow. After Nginx's many crashes, > the attacker can find enough gadgets to launch a return-oriented > programming attack. > > However, it is hard to let Nginx worker process crash (due to overwritten > return address) on FreeBSD. Process crash is the first step of the whole > exploit. > > I guess (probably a wrong guess) the reason may be: the exploit needs to > set MTU to a large value. But FreeBSD seems only to allows a max MTU of > 16110. > > It is probably because of other reasons. Any comments/suggestions on this, > just to make the victim process crash? > > Here are two exploit code examples, which can run against Linux target, but > fail to make the Nginx worker process crash on FreeBSD: > > http://www.scs.stanford.edu/brop/ > http://www.scs.stanford.edu/brop/nginx-1.4.0-exp.tgz > > https://www.exploit-db.com/docs/27074.pdf > http://seclists.org/fulldisclosure/2013/Jul/att-90/ngxunlock_pl.bin > > With a simple experiment on nginx 1.4.0, it's possible that FreeBSD has more strict checks in recvfrom. For the exploit: Pwning IP 127.0.0.1 Pwning Checking for vuln... Not vuln2 >From error.log: 2016/01/05 00:43:35 [alert] 79819#0: *14 recv() failed (22: Invalid argument) while sending response to client, client: 127.0.0.1, server: localhost, request: "GET / HTTP/1.1", host: "bla.com" >From ktrace: 79819 nginx CALL recvfrom(0x3,0x801a15400,0x400,0,0,0) 79819 nginx GIO fd 3 read 104 bytes "GET / HTTP/1.1\r ... 79819 nginx CALL recvfrom(0x3,0x7fffffffcf30,0xeadbeefdeadbef03,0,0,0) 79819 nginx RET recvfrom -1 errno 22 Invalid argument >From an analysis, this should succeed: (from http://www.vnsecurity.net/research/2013/05/21/analysis-of-nginx-cve-2013-2028.html ) strace -p 11337 -s 5000 2>&1 | grep recv recvfrom(3, "GET / HTTP/1.1rnHost: 1337.vnsecurity.netrnAccept: */*rnTransfer-Encoding: chunkedrnrnfff...snip..fff0f0f0f0f", 1024, 0, NULL, NULL) = 1024 recvfrom(3, "AAA..snip..AACCCCCCCC", 18446744069667229461, 0, NULL, NULL) = 4112 > > Thanks!! > > Best, > Peter > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Cheers, Henry From owner-freebsd-hackers@freebsd.org Tue Jan 5 05:59:21 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 149F9A62930 for ; Tue, 5 Jan 2016 05:59:21 +0000 (UTC) (envelope-from peterchencs@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D3EB21E61 for ; Tue, 5 Jan 2016 05:59:20 +0000 (UTC) (envelope-from peterchencs@gmail.com) Received: by mail-oi0-x22c.google.com with SMTP id o62so263324496oif.3 for ; Mon, 04 Jan 2016 21:59:20 -0800 (PST) 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=uOgWl8ASQXoBJ4BLPnkoddu0YlH6fBjQxZYfhx/7W8M=; b=c/s+ijGji0IXrnfKzH6Kfa/5+ytUHbquTubZvplmYe0RxwSVsXodiafSrPqM0Slfc2 bZJ9C0Y/CD+BP32Oj/OrHZ+Cdsvcs/ltc3oaNTBmXJrloBHENwwWHiaKtIN56ORzDoeq 4yxQLGSa2bNUBpqfsIArnZuedhbst7Af2V6mqJ0LRJUGbg9nlW+8Pagk/8HGTY2UXkX6 T+zSoZxfPek82eZdZj1HSmJ8r4iXV86+ow7soUM1kbegxQfeNfGLyqk080t3e663Q9/a X/AjjvGUn5xWXppo2KzI51OrwwZya/bjH1rX9KkEQoGXQbm305A311nPoeJwDcwpvd4T gGdw== MIME-Version: 1.0 X-Received: by 10.202.200.79 with SMTP id y76mr56544417oif.111.1451973560030; Mon, 04 Jan 2016 21:59:20 -0800 (PST) Received: by 10.202.188.130 with HTTP; Mon, 4 Jan 2016 21:59:19 -0800 (PST) In-Reply-To: References: Date: Tue, 5 Jan 2016 00:59:19 -0500 Message-ID: Subject: Re: Nginx Vulnerability on FreeBSD From: Peter Chen To: Henry Hu Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 05:59:21 -0000 Thanks a million for the prompt reply! I'll try http://www.vnsecurity.net/research/2013/05/21/analysis-of-nginx-cve-2013-2028.html . On Tue, Jan 5, 2016 at 12:49 AM, Henry Hu wrote: > > > On Tue, Jan 5, 2016 at 12:14 AM, Peter Chen wrote: > >> Hi, >> >> I am trying to do a security research experiment on FreeBSD. >> I try to test the Nginx Vulnerability CVE-2013-2028 on FreeBSD x86-64, >> with >> Nginx 1.3.9/1.4.0. >> (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2028) >> >> However, most exploit samples can succeed on Linux, but not FreeBSD. >> The basic idea for the exploit, is to send a packet with a very large >> chunk >> size, making the victim process stack-overflow. After Nginx's many >> crashes, >> the attacker can find enough gadgets to launch a return-oriented >> programming attack. >> >> However, it is hard to let Nginx worker process crash (due to overwritten >> return address) on FreeBSD. Process crash is the first step of the whole >> exploit. >> >> I guess (probably a wrong guess) the reason may be: the exploit needs to >> set MTU to a large value. But FreeBSD seems only to allows a max MTU of >> 16110. >> >> It is probably because of other reasons. Any comments/suggestions on this, >> just to make the victim process crash? >> >> Here are two exploit code examples, which can run against Linux target, >> but >> fail to make the Nginx worker process crash on FreeBSD: >> >> http://www.scs.stanford.edu/brop/ >> http://www.scs.stanford.edu/brop/nginx-1.4.0-exp.tgz >> >> https://www.exploit-db.com/docs/27074.pdf >> http://seclists.org/fulldisclosure/2013/Jul/att-90/ngxunlock_pl.bin >> >> > With a simple experiment on nginx 1.4.0, it's possible that FreeBSD has > more strict checks in recvfrom. > > For the exploit: > Pwning IP 127.0.0.1 > Pwning > Checking for vuln... Not vuln2 > > From error.log: > 2016/01/05 00:43:35 [alert] 79819#0: *14 recv() failed (22: Invalid > argument) while sending response to client, client: 127.0.0.1, server: > localhost, request: "GET / HTTP/1.1", host: "bla.com" > From ktrace: > 79819 nginx CALL recvfrom(0x3,0x801a15400,0x400,0,0,0) > 79819 nginx GIO fd 3 read 104 bytes > "GET / HTTP/1.1\r > ... > 79819 nginx CALL recvfrom(0x3,0x7fffffffcf30,0xeadbeefdeadbef03,0,0,0) > 79819 nginx RET recvfrom -1 errno 22 Invalid argument > > > From an analysis, this should succeed: > (from > http://www.vnsecurity.net/research/2013/05/21/analysis-of-nginx-cve-2013-2028.html > ) > > strace -p 11337 -s 5000 2>&1 | grep recv > recvfrom(3, "GET / HTTP/1.1rnHost: 1337.vnsecurity.netrnAccept: > */*rnTransfer-Encoding: chunkedrnrnfff...snip..fff0f0f0f0f", 1024, 0, NULL, > NULL) = 1024 > recvfrom(3, "AAA..snip..AACCCCCCCC", 18446744069667229461, 0, NULL, NULL) > = 4112 > > >> >> Thanks!! >> >> Best, >> Peter >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org >> " >> > > > > -- > Cheers, > Henry > From owner-freebsd-hackers@freebsd.org Thu Jan 7 02:12:56 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27C3DA6557C for ; Thu, 7 Jan 2016 02:12:56 +0000 (UTC) (envelope-from mark@heily.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F199E153B for ; Thu, 7 Jan 2016 02:12:55 +0000 (UTC) (envelope-from mark@heily.com) Received: by mail-io0-x234.google.com with SMTP id q21so237559297iod.0 for ; Wed, 06 Jan 2016 18:12:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heily-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BYq/BLHrrAKzk9CvuEz757KfPQh7EZCsUbclryGWbRo=; b=mYFBTsUGOV8SObKyJc8fv6Vxmx3vrgzil1GYLggToIaspQMqxg/mzqw33tc7jlSdbP N9OzBUl7Pgwb4JkQL7IoGjV9CCc46oo2xK6EGqUeT8toxh51aBhCN1fBeuwjjTwNMWkS dbXiQvt0VEhQtHX86hYd+3/c7ZjLcXm652RCJzaEsYFZxeMaBElNoT3UsANzaJNHOS7R dSTI0JRjVJ9L28aPga4jpNW8XW1w+ZfYGQ7q7V5kUDTVvzigiAWYOKJr3mJ+Y9CgDsxW 55CmT31QqTYivb3X40Lz28xgokOF1ggV/iZrRnFCJ1VtcVwEzt1gIkA6k0g5BQX5mN3a Jezw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=BYq/BLHrrAKzk9CvuEz757KfPQh7EZCsUbclryGWbRo=; b=mFv17NPXD1dx3PfN/tgaXhRDMX4J0jb/p02hbLgXWIxytzpe2xNnGaJwb1dF7J0Ez9 E6BVHlojezqVrIK38v5nxQdMUkPRu9Y1zs5h9QIhSB/psDceZOsY/6/Brn0nmTmcgsRp 8pJ1BLyqjUOndT4+etlEYCtXjy2FJP+CrzTqvneRWPDSR6Ng2syuiJViL5qJoUoR3PG+ giZF+ApWtGa0EHEL6OVDQQXCoX8swWhQGBO2RXdOAF7xsl7DmIAe/MT2M367SWJ6B+JU K1qWLafdX9IWTykEPY1qjHHvsl2C1s0Ra9MKT0l2ANVHBwkP6IOBhbs2yFfdnkxPq7RM gZxw== X-Gm-Message-State: ALoCoQlJI14g4JLZ3Tg07+Mw1b892FtyJmKC3yQMchAiBolc1g+H1K4J3de8JHiXu6qMkiWZcxEiwtHU3Ck/tz85yeLtJuiNQQ== MIME-Version: 1.0 X-Received: by 10.107.30.144 with SMTP id e138mr4354567ioe.158.1452132775123; Wed, 06 Jan 2016 18:12:55 -0800 (PST) Received: by 10.79.34.196 with HTTP; Wed, 6 Jan 2016 18:12:55 -0800 (PST) X-Originating-IP: [71.70.175.250] In-Reply-To: <5687D3A9.5050400@NTLWorld.com> References: <5687D3A9.5050400@NTLWorld.com> Date: Wed, 6 Jan 2016 21:12:55 -0500 Message-ID: Subject: Re: relaunchd: a portable clone of launchd From: Mark Heily To: Jonathan de Boyne Pollard Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 02:12:56 -0000 On Sat, Jan 2, 2016 at 8:42 AM, Jonathan de Boyne Pollard wrote: > > I recommend, to anyone going down this route, looking towards finishing > systembsd, especially instead of inventing a wholly new suite of protocols. > > * https://uglyman.kremlin.cc/gitweb/gitweb.cgi?p=systembsd.git > * > http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/debian-systemd-packaging-hoo-hah.html > * https://news.ycombinator.com/item?id=10176275 > > The reason is that finishing systemdbsd will make happy all of the people > who want the desktop environments whose design is driven largely by Linux to > work on FreeBSD/PC-BSD. The desktop environments that they'd like to use > have been or are being modified to work with these daemons, over this D-Bus > protocol. > I strongly disagree with your recommendation to adopt DBus and systemd as core components of FreeBSD. >From a practical perspective, the proposal has a low probability of success. Systemd is written for Linux and is largely driven by a commercial Linux vendor. It is a rapidly moving target, with no sense of scope or boundaries. It eagerly consumes the latest and greatest innovations in the Linux kernel, with open disdain for portability. >From a philosophical perspective, I don't agree with the direction that systemd is taking Linux. It's one of the reasons I switched to BSD after many years in the Linux camp. To quote Spock, "Logic clearly dictates that the needs of the many outweigh the needs of the few". In case of FreeBSD, this means that the needs of the desktop users should not outweigh the needs of the server/jail/embedded/appliance users. My concern with systemd and DBus is that these tools are highly desktop-centric, and introduce a large degree of unwanted change, complexity, and risk to everyone else. If you really believe that implementing more systemd compatibility layers is the way to go, maybe you should import systembsd into the Nosh source tree, and carry on the work there? From owner-freebsd-hackers@freebsd.org Thu Jan 7 02:57:36 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C532A66603 for ; Thu, 7 Jan 2016 02:57:36 +0000 (UTC) (envelope-from peterchencs@gmail.com) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C8E6B12D9 for ; Thu, 7 Jan 2016 02:57:35 +0000 (UTC) (envelope-from peterchencs@gmail.com) Received: by mail-oi0-x230.google.com with SMTP id o124so305457155oia.1 for ; Wed, 06 Jan 2016 18:57:35 -0800 (PST) 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=rKZnCNQerm0Ay0UW+zLSmyYwEpteoXfgz5CDWbF/UxE=; b=iT50D7xCJNCqxtgzoPaD2wo9E/LYpEweu3l2zdDcW++Z+OvC53o2HwUmrG0J7NX4JK GK/bnfGH5/hDKhCS6gHqhg+9YuupqoUh5uFUlZg5e9+f7K5bkD4rLjS/jdxDvZgLDPmU sR92+0zLYraKvRticMQSj7m0eMALmDWHXwaGq7GNLhgy62q6aw9F1fMxPOzd6gwLfny2 S7CivH9FXPwsea2jjgnq5ethdDjVDIPPrTvT4/Iq64UHRXYShJAAkk9mVIox5bf5Nlrd gy/iLIuwuNCizrHFxPZAHKMMnsTm6SZ8yZiMQrXnNfQzeq1FEV6PnyBuzFavoheV/8O0 SPkQ== MIME-Version: 1.0 X-Received: by 10.202.207.206 with SMTP id f197mr71004922oig.50.1452135454629; Wed, 06 Jan 2016 18:57:34 -0800 (PST) Received: by 10.202.188.130 with HTTP; Wed, 6 Jan 2016 18:57:34 -0800 (PST) In-Reply-To: References: Date: Wed, 6 Jan 2016 21:57:34 -0500 Message-ID: Subject: Re: Nginx Vulnerability on FreeBSD From: Peter Chen To: Henry Hu Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 02:57:36 -0000 After I tried that on FreeBSD, and used "truss" to trace system calls, the Nginx worker process still cannot crash. It seems that FreeBSD's recvfrom() automatically divide the received data into 4096-sized chunks, and it will not overflow. The system call trace is as follows (different from http://www.vnsecurity.net/research/2013/05/21/analysis-of-nginx-cve-2013-2028.html 's 1024 and 4112, here the recvfrom's received size is 1024, 4096 and 16): ======================================================== kevent(8,{},0,{0x6,EVFILT_READ,0x0,0,0x1,0x801cd3000},512,0x0) = 1 (0x1) gettimeofday({1452134269.299028 },0x0) = 0 (0x0) accept4(0x6,0x7fffffffe650,0x7fffffffe6bc,0x20000000,0xffff,0x2) = 3 (0x3) kevent(8,{0x3,EVFILT_READ,EV_ADD|EV_ENABLE|EV_CLEAR,0,0x0,0x801cd30e0},1,{0x3,EVFILT_READ,EV_CLEAR,0,0x1410,0x801cd30e0},512,{60.000000000 }) = 1 (0x1) gettimeofday({1452134269.299901 },0x0) = 0 (0x0) recvfrom(3,"GET / HTTP/1.1rnHost: 1337.vnsec"...,1024,0x0,NULL,0x0) = 1024 (0x400) writev(0x3,0x7fffffffdcb0,0x2,0x7fffffffffffef87,0x68,0x1) = 172 (0xac) shutdown(3,SHUT_WR) = 0 (0x0) recvfrom(3,"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"...,4096,0x0,NULL,0x0) = 4096 (0x1000) recvfrom(3,"AAAAAAAACCCCCCCC",4096,0x0,NULL,0x0) = 16 (0x10) kevent(8,{},0,{0x3,EVFILT_READ,EV_CLEAR|EV_EOF,54,0x0,0x801cd30e0},512,{5.000000000 }) = 1 (0x1) gettimeofday({1452134269.306013 },0x0) = 0 (0x0) write(4,"172.16.187.1 - - [06/Jan/2016:21"...,1089) = 1089 (0x441) close(3) ======================================================== Any idea how to make the crash happen? I can modify the kernel if needed. But I did not find recvfrom()'s maximum "len" in the recvfrom system call implementation -- sys_recvfrom. ( https://github.com/freebsd/freebsd/blob/63cd1c131acbe2c4896430de52395b168ee9b73d/sys/kern/uipc_syscalls.c ) Thanks!! On Tue, Jan 5, 2016 at 12:59 AM, Peter Chen wrote: > Thanks a million for the prompt reply! I'll try > http://www.vnsecurity.net/research/2013/05/21/analysis-of-nginx-cve-2013-2028.html > . > > On Tue, Jan 5, 2016 at 12:49 AM, Henry Hu wrote: > >> >> >> On Tue, Jan 5, 2016 at 12:14 AM, Peter Chen >> wrote: >> >>> Hi, >>> >>> I am trying to do a security research experiment on FreeBSD. >>> I try to test the Nginx Vulnerability CVE-2013-2028 on FreeBSD x86-64, >>> with >>> Nginx 1.3.9/1.4.0. >>> (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2028) >>> >>> However, most exploit samples can succeed on Linux, but not FreeBSD. >>> The basic idea for the exploit, is to send a packet with a very large >>> chunk >>> size, making the victim process stack-overflow. After Nginx's many >>> crashes, >>> the attacker can find enough gadgets to launch a return-oriented >>> programming attack. >>> >>> However, it is hard to let Nginx worker process crash (due to overwritten >>> return address) on FreeBSD. Process crash is the first step of the whole >>> exploit. >>> >>> I guess (probably a wrong guess) the reason may be: the exploit needs to >>> set MTU to a large value. But FreeBSD seems only to allows a max MTU of >>> 16110. >>> >>> It is probably because of other reasons. Any comments/suggestions on >>> this, >>> just to make the victim process crash? >>> >>> Here are two exploit code examples, which can run against Linux target, >>> but >>> fail to make the Nginx worker process crash on FreeBSD: >>> >>> http://www.scs.stanford.edu/brop/ >>> http://www.scs.stanford.edu/brop/nginx-1.4.0-exp.tgz >>> >>> https://www.exploit-db.com/docs/27074.pdf >>> http://seclists.org/fulldisclosure/2013/Jul/att-90/ngxunlock_pl.bin >>> >>> >> With a simple experiment on nginx 1.4.0, it's possible that FreeBSD has >> more strict checks in recvfrom. >> >> For the exploit: >> Pwning IP 127.0.0.1 >> Pwning >> Checking for vuln... Not vuln2 >> >> From error.log: >> 2016/01/05 00:43:35 [alert] 79819#0: *14 recv() failed (22: Invalid >> argument) while sending response to client, client: 127.0.0.1, server: >> localhost, request: "GET / HTTP/1.1", host: "bla.com" >> From ktrace: >> 79819 nginx CALL recvfrom(0x3,0x801a15400,0x400,0,0,0) >> 79819 nginx GIO fd 3 read 104 bytes >> "GET / HTTP/1.1\r >> ... >> 79819 nginx CALL >> recvfrom(0x3,0x7fffffffcf30,0xeadbeefdeadbef03,0,0,0) >> 79819 nginx RET recvfrom -1 errno 22 Invalid argument >> >> >> From an analysis, this should succeed: >> (from >> http://www.vnsecurity.net/research/2013/05/21/analysis-of-nginx-cve-2013-2028.html >> ) >> >> strace -p 11337 -s 5000 2>&1 | grep recv >> recvfrom(3, "GET / HTTP/1.1rnHost: 1337.vnsecurity.netrnAccept: >> */*rnTransfer-Encoding: chunkedrnrnfff...snip..fff0f0f0f0f", 1024, 0, NULL, >> NULL) = 1024 >> recvfrom(3, "AAA..snip..AACCCCCCCC", 18446744069667229461, 0, NULL, NULL) >> = 4112 >> >> >>> >>> Thanks!! >>> >>> Best, >>> Peter >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to " >>> freebsd-hackers-unsubscribe@freebsd.org" >>> >> >> >> >> -- >> Cheers, >> Henry >> > > From owner-freebsd-hackers@freebsd.org Thu Jan 7 04:34:49 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DD5BA66533 for ; Thu, 7 Jan 2016 04:34:49 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-yk0-f174.google.com (mail-yk0-f174.google.com [209.85.160.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47C941E20 for ; Thu, 7 Jan 2016 04:34:48 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-yk0-f174.google.com with SMTP id a85so250660217ykb.1 for ; Wed, 06 Jan 2016 20:34:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=yd8yx4CfmXsPamZ7jZTmFS7fIhPkN2yryjcC/vi4L90=; b=PTOOuiKBXKFyvgIFHG7/B4W8Z9gRGiXxtS+krNG8rW9QZOk2p5suG0gQZtMaWdaS3H 5Z9tcn0h4Y9hA7sWTX9muj1E/Av5ACnisRF2nXktlpCUgfEJU1TEGdD0aQgChbJSbofe UELymCnrIfl2xOQoAEPioRbyVar4pjiFtPr80fSGUDBHUbc+Osog0hFVQWO0eA7g+pHH M19LJGYeDvNJUUZu8PzxFoocbVHLTEMiVfpC1XOLUBr8CJEgdL+LAxgKGcTeedq3zS24 3y9Ww4lQiLBVxN92VuJXWnIig73Wn9iCyEs26GKjQiU/NA0qfnV6jerfQLTc4AN3nX4N Rr0w== X-Received: by 10.13.216.12 with SMTP id a12mr66153956ywe.245.1452140799723; Wed, 06 Jan 2016 20:26:39 -0800 (PST) Received: from mail-yk0-f180.google.com (mail-yk0-f180.google.com. [209.85.160.180]) by smtp.gmail.com with ESMTPSA id p63sm83773662ywf.8.2016.01.06.20.26.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2016 20:26:39 -0800 (PST) Received: by mail-yk0-f180.google.com with SMTP id x67so328152874ykd.2 for ; Wed, 06 Jan 2016 20:26:39 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.129.153.129 with SMTP id q123mr84366555ywg.281.1452140799190; Wed, 06 Jan 2016 20:26:39 -0800 (PST) Reply-To: cem@FreeBSD.org Received: by 10.37.4.69 with HTTP; Wed, 6 Jan 2016 20:26:39 -0800 (PST) In-Reply-To: References: <5687D3A9.5050400@NTLWorld.com> Date: Wed, 6 Jan 2016 20:26:39 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: relaunchd: a portable clone of launchd From: Conrad Meyer To: Mark Heily Cc: Jonathan de Boyne Pollard , FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 04:34:49 -0000 On Wed, Jan 6, 2016 at 6:12 PM, Mark Heily wrote: > On Sat, Jan 2, 2016 at 8:42 AM, Jonathan de Boyne Pollard > wrote: >> >> I recommend, to anyone going down this route, looking towards finishing >> systembsd, especially instead of inventing a wholly new suite of protocols. >> >> * https://uglyman.kremlin.cc/gitweb/gitweb.cgi?p=systembsd.git >> * >> http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/debian-systemd-packaging-hoo-hah.html >> * https://news.ycombinator.com/item?id=10176275 > > I strongly disagree with your recommendation to adopt DBus and systemd > as core components of FreeBSD. Hi Mark, Hold on a minute, read any of the links above or below, and calm down. Systembsd is *not* systemd. http://undeadly.org/cgi?action=article&sid=20140915064856 FreeBSD isn't going to adopt Systemd, period. Save the anti-systemd screed for a Linux community. Thanks, Conrad From owner-freebsd-hackers@freebsd.org Thu Jan 7 05:11:48 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE41CA651F6 for ; Thu, 7 Jan 2016 05:11:48 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 559C41BD2 for ; Thu, 7 Jan 2016 05:11:48 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-wm0-x230.google.com with SMTP id b14so105349900wmb.1 for ; Wed, 06 Jan 2016 21:11:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=XJbP4jLsIYS6Yp+qbu6s6FLBwSAd43q/DzsSpzO/oXk=; b=Gwr6/yTpHW6prIaLl8YVn3gUJEr6AMVmsbvJjRYlTNwSYdWjFiRfHA8GhNZz/XoPrb cNRMmvOReOJu8G0s+iWvp3LIFFqJ5CsWA1oVFqbWMcLeyrXZf5MIHVwFZdikOCSGkkBN 0f8i4gO06moRZhshaBqfUwKyWszMlAflFW5LM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=XJbP4jLsIYS6Yp+qbu6s6FLBwSAd43q/DzsSpzO/oXk=; b=NzPFP6HLudPWi2zBi++LNrDkdt1Qho5IzhyLLefxlLgbITMhibC2BGLaVOtCDWSpFi DzkX59arnxZP61mbwNAnxovmU7hRjR6B7tt6jLFTOZcT7DFjS6kmhtv4xHFIfmQdl+eZ 50lb4JAD29cP2KWjKOe2usRkfymsP7GR+aGfGZrCZaZJ9Cc2NnKqDe9Ce3sTTO7siF3x 3wILIjkQCzFwTcMmQ+F6MPeuhsuu377H1RABpt8QaVI4wULAsyCa7TCLdxjdl70LpWoy rrZGn3qUb7dJ28+8I2NmkNymuZic7mDXM+9hDZT7tQF48luDCpGKPWMcSJRyQKUjmUMw b/pA== X-Gm-Message-State: ALoCoQkoqCDUyGlYTgrn89QXgTfAAW3t18vRktUnqcdrrwHpLuyRW9Jfe6jCI7+gD/r7ZoCQQsSlfRykYJ/8jQMCgU6UjOApHA== X-Received: by 10.28.85.129 with SMTP id j123mr15131616wmb.77.1452143506053; Wed, 06 Jan 2016 21:11:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.43.1 with HTTP; Wed, 6 Jan 2016 21:11:16 -0800 (PST) In-Reply-To: References: From: Eitan Adler Date: Wed, 6 Jan 2016 21:11:16 -0800 Message-ID: Subject: Re: master.passwd UID/GID number To: araujo@freebsd.org, FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 05:11:48 -0000 this was accidentally sent to a private list. Forwarding to the correct list. On 6 January 2016 at 19:48, Marcelo Araujo wrote: > Hello all, > > I need to add a new special user on master.passwd for ypldap. > I'm wondering what are the rules to choose the number for UID/GID if there > is any. Pick an arbitrary but low number. Anything below 1000 is typically okay - look to see what other users use. -- Eitan Adler From owner-freebsd-hackers@freebsd.org Thu Jan 7 10:11:15 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13785A66D19 for ; Thu, 7 Jan 2016 10:11:15 +0000 (UTC) (envelope-from trtrmitya@gmail.com) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9317F1FAB for ; Thu, 7 Jan 2016 10:11:14 +0000 (UTC) (envelope-from trtrmitya@gmail.com) Received: by mail-lf0-x22e.google.com with SMTP id y184so329106627lfc.1 for ; Thu, 07 Jan 2016 02:11:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vm2bn5NZwodS5tF7Aua7bQhNtkd3rH4lDAjcYmueTJ8=; b=N4XqHsu8Qi5D+6z37Z8q/s3XflHsjpGt5S4cPCTE/dhBgY/dRXzU/rAvx1oI++vReO WDqXczGndE48/xFnEra8rpP9Zrpo7LXaCbvRBA6Wnrt2nT2w0xb2VUyyvPtOLXMvg6Cq yYJN9sDeufv5Qon81YdzsuChTNTubJV9OrQ4pdsXtPJxeO3Tx+HqxhU0r+IbeJvqaveT DD2aTruFCEn9rDuIbKtM/yWVZ4DAAQTRm5gJIhe8QWqw8+SgcS+75zafKqPmhDh/H1hW qfCNK5GGXZDRfVilhSBwhbSQXdYWpR6MW4NNAXOuDTqb36+wuUtb9VuwuE+WjetL4nYV Lylw== X-Received: by 10.25.18.231 with SMTP id 100mr37449678lfs.25.1452161472583; Thu, 07 Jan 2016 02:11:12 -0800 (PST) Received: from [10.0.1.2] (broadband-5-228-251-240.nationalcablenetworks.ru. [5.228.251.240]) by smtp.gmail.com with ESMTPSA id k3sm8086477lbp.9.2016.01.07.02.11.11 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Jan 2016 02:11:11 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: relaunchd: a portable clone of launchd From: Dmitry Sivachenko In-Reply-To: Date: Thu, 7 Jan 2016 13:11:10 +0300 Cc: Jonathan de Boyne Pollard , FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <817860B6-5D67-41A3-ADD7-9757C7E67C35@gmail.com> References: <5687D3A9.5050400@NTLWorld.com> To: Mark Heily X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 10:11:15 -0000 > On 07 Jan 2016, at 05:12, Mark Heily wrote: >=20 > On Sat, Jan 2, 2016 at 8:42 AM, Jonathan de Boyne Pollard > wrote: >>=20 >> I recommend, to anyone going down this route, looking towards = finishing >> systembsd, especially instead of inventing a wholly new suite of = protocols. >>=20 >> * https://uglyman.kremlin.cc/gitweb/gitweb.cgi?p=3Dsystembsd.git >> * >> = http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/debian-systemd-p= ackaging-hoo-hah.html >> * https://news.ycombinator.com/item?id=3D10176275 >>=20 >> The reason is that finishing systemdbsd will make happy all of the = people >> who want the desktop environments whose design is driven largely by = Linux to >> work on FreeBSD/PC-BSD. The desktop environments that they'd like to = use >> have been or are being modified to work with these daemons, over this = D-Bus >> protocol. >>=20 >=20 > I strongly disagree with your recommendation to adopt DBus and systemd > as core components of FreeBSD. >=20 > =46rom a practical perspective, the proposal has a low probability of > success. Systemd is written for Linux and is largely driven by a > commercial Linux vendor. It is a rapidly moving target, with no sense > of scope or boundaries. It eagerly consumes the latest and greatest > innovations in the Linux kernel, with open disdain for portability. >=20 > =46rom a philosophical perspective, I don't agree with the direction > that systemd is taking Linux. It's one of the reasons I switched to > BSD after many years in the Linux camp. To quote Spock, "Logic clearly > dictates that the needs of the many outweigh the needs of the few". In > case of FreeBSD, this means that the needs of the desktop users should > not outweigh the needs of the server/jail/embedded/appliance users. My > concern with systemd and DBus is that these tools are highly > desktop-centric, and introduce a large degree of unwanted change, > complexity, and risk to everyone else. I totally agree. systemd is an ugly beast, solving simple problem in complex way. After using FreeBSD's rc system for years, I think that switching to = something systemd-related would be huge mistake. No reason to clone everything that happens in Linux world.= From owner-freebsd-hackers@freebsd.org Thu Jan 7 13:01:01 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80A91A65AFA for ; Thu, 7 Jan 2016 13:01:01 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 707DF1E8F for ; Thu, 7 Jan 2016 13:01:01 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from msam.nabble.com (unknown [162.253.133.85]) by mbob.nabble.com (Postfix) with ESMTP id 5859E1D9D383 for ; Thu, 7 Jan 2016 04:58:43 -0800 (PST) Date: Thu, 7 Jan 2016 06:00:55 -0700 (MST) From: grahamperrin To: freebsd-hackers@freebsd.org Message-ID: <1452171655162-6065689.post@n5.nabble.com> In-Reply-To: References: Subject: FreeBSD 2015Q4 status report: expected date of publication MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 13:01:01 -0000 >From I see that the report for 2015Q3 was announced on 2015-10-25. Please: is it reasonable to assume that the report for 2015Q4 will be published before the end of this month? (I have nothing to submit. I'm an interested reader, relatively new to FreeBSD.) -- View this message in context: http://freebsd.1045724.n5.nabble.com/second-call-for-2015Q4-quarterly-status-reports-tp6063452p6065689.html Sent from the freebsd-hackers mailing list archive at Nabble.com. From owner-freebsd-hackers@freebsd.org Thu Jan 7 13:14:10 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A45FEA6603D for ; Thu, 7 Jan 2016 13:14:10 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 8DC9C1794 for ; Thu, 7 Jan 2016 13:14:10 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from msam.nabble.com (unknown [162.253.133.85]) by mbob.nabble.com (Postfix) with ESMTP id E27521D9DB42 for ; Thu, 7 Jan 2016 05:11:57 -0800 (PST) Date: Thu, 7 Jan 2016 06:14:09 -0700 (MST) From: grahamperrin To: freebsd-hackers@freebsd.org Message-ID: <1452172449792-6065692.post@n5.nabble.com> In-Reply-To: References: <8FF83C2F-D8CD-4366-A890-7EF605050456@netgate.com> Subject: Re: relaunchd: a portable clone of launchd MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 13:14:10 -0000 I'm not a developer but I follow these discussions with interest. I'm a former tester of OS X, in which launchd is (in my experience) very satisfactory.=20 Mark Heily wrote > Allow me to clarify the goals of relaunchd and how this affects the > existing init(8) and rc(8) system in FreeBSD. >=20 > Unlike the original launchd project, relaunchd is not trying to become PI= D > #1 or replace anything in the base system. I am simply asking for help > getting it fixed up and committed to the ports tree, so it can become an > alternative for people who want to configure their systems to take > advantage of the featureset that launchd provides. Choice is good, and I > don't want to take away people's ability to use nosh, openrc, svc, or > whatever else meets their needs. That seems reasonable.=20 nosh caught my eye a couple of months ago. Some attention to PC-BSD was apparent so I posted highlights under https://forums.pcbsd.org/thread-20272.html =E2=80=A6 ending when I found a = section on the nosh project within the FreeBSD 2015Q3 status report.=20 Re: the third call for 2015Q4 quarterly status reports :=20 * the deadline for submissions is today =E2=80=93 if it's not too late, I wonder whether something submitted *now* = could help the report, when it appears, to put things in context without causing unnecessary alarm. An explanation of how developments in both project areas (nosh and relaunchd) may be complementary. =20 > I will try to develop relaunchd in such a way that it *could* be used to > replace rc(8) if desired, but that would require a lot of work and > discussion and buy-in from the FreeBSD project leadership. Because > relaunchd is such a young project, I want to have more realistic goals an= d > not worry about what might happen in the longer term. I would consider it > a major success if, a year from now, the majority of the daemons in the > ports tree offer support for running under launchd(8) in addition to the > traditional rc(8) init scripts. -- View this message in context: http://freebsd.1045724.n5.nabble.com/relaunch= d-a-portable-clone-of-launchd-tp6053155p6065692.html Sent from the freebsd-hackers mailing list archive at Nabble.com. From owner-freebsd-hackers@freebsd.org Thu Jan 7 15:18:03 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B287AA65FE1 for ; Thu, 7 Jan 2016 15:18:03 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 665BF1EDA for ; Thu, 7 Jan 2016 15:18:02 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074423-f797f6d0000023d0-12-568e81a2ee15 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id C0.20.09168.2A18E865; Thu, 7 Jan 2016 10:17:54 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id u07FHs7x001112; Thu, 7 Jan 2016 10:17:54 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u07FHp4b022734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 7 Jan 2016 10:17:53 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u07FHoPN025637; Thu, 7 Jan 2016 10:17:50 -0500 (EST) Date: Thu, 7 Jan 2016 10:17:50 -0500 (EST) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: grahamperrin cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 2015Q4 status report: expected date of publication In-Reply-To: <1452171655162-6065689.post@n5.nabble.com> Message-ID: References: <1452171655162-6065689.post@n5.nabble.com> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmleLIzCtJLcpLzFFi42IR4hRV1l3U2BdmsGS3pcX2zf8YLU61Gjgw ecz4NJ/FY+esu+wBTFFcNimpOZllqUX6dglcGa3t/9kKjrNUrGrfzdbAeJe5i5GTQ0LAROLd radMELaYxIV769m6GLk4hAQWM0nc2dLLDuFsYJRoeNnJClIlJHCQSaL3txSEXS+x5N1sNhCb RUBL4sSpc2A2m4CaxOO9zawQUxUlNp+aBLZNREBTYsf042DbmAXkJS5sPsQIYgsLuEvcu/AZ rJdTwFxi5cTrQPUcHLwCjhJte6AOWsQo8Xn2d7CZogI6Eqv3T2EBsXkFBCVOznzCAjFTS2L5 9G0sExiFZiFJzUKSWsDItIpRNiW3Sjc3MTOnODVZtzg5MS8vtUjXTC83s0QvNaV0EyMofNld lHcw/jmodIhRgINRiYc3ILEvTIg1say4MvcQoyQHk5Iob34DUIgvKT+lMiOxOCO+qDQntfgQ owQHs5II7896oBxvSmJlVWpRPkxKmoNFSZx37hffMCGB9MSS1OzU1ILUIpisDAeHkgTvEZCh gkWp6akVaZk5JQhpJg5OkOE8QMPLQWp4iwsSc4sz0yHypxh1ORb8uL2WSYglLz8vVUqc1xik SACkKKM0D24OOO3sZlJ9xSgO9JYwbzhIFQ8wZcFNegW0hAloCUNRN8iSkkSElFQD4ykx3p1R nivn7HM9EWp0VvlN2xVX17b5+gbbPNekfmj4rH6mJX+DQ6JGyOEZ1+oYOZbb/Hg764hNQsR3 Q3HDQAWzVuOD+3Uk/3nc2fPm+rM3U458Zla/mbNwg1aVe+S5J5OFZbk/xHYb9metOz7teSyT xO15M3tubep5cs2NIfecw6+yI4uvrVdiKc5INNRiLipOBAB99axHFgMAAA== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 15:18:03 -0000 On Thu, 7 Jan 2016, grahamperrin wrote: > From I see > that the report for 2015Q3 was announced on 2015-10-25. > > Please: is it reasonable to assume that the report for 2015Q4 will be > published before the end of this month? That's correct. We usually give ourselves about a week after the submission deadline to finish processing submissions, edit for consistency of style, write an introduction, and so forth. The 2015Q3 report took longer due to personal circumstances of the monthly@ team. -Ben From owner-freebsd-hackers@freebsd.org Thu Jan 7 15:24:40 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C26B2A66383 for ; Thu, 7 Jan 2016 15:24:40 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 64694141E for ; Thu, 7 Jan 2016 15:24:40 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id u188so102744769wmu.1 for ; Thu, 07 Jan 2016 07:24:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:mime-version :content-type; bh=+5kBZ7KtlJafdrzDb5KMUA6dZmPgdqY3/rk2p1Fp9xg=; b=oP+AdWCs36Jyph2kCHj7QNb2gKPxDzn3ZlENB2hfQixvhGWmapDW3tZn0U7Y5MMBun auy0uHqSFwlT3XveNi68/tyCFYJUcJptdVYguVpQgQ/L6CrtgpWC52LBenbmevA0dXc+ 6qyymjROwUrMo04lBxn9wBEiMyjb7++tU9uhgfB5wkTAjLyHUgahJ7vCwyaOBco3qNC6 ypA6K4/cuP8mWg9xF2p1vIG7k+TPKJ2Fi27Ef3BGTJpq28ph+a461/cZgeHSXIkZcg+O ciR1Tt5LzVNzBUXgoJSbT7nt3D58tIkXbjWwA9a47z4J9BeEiqGNw2NPWdfoQNcJmUF6 44mg== X-Received: by 10.28.194.69 with SMTP id s66mr18595337wmf.93.1452180278875; Thu, 07 Jan 2016 07:24:38 -0800 (PST) Received: from localhost (li195-236.members.linode.com. [178.79.139.236]) by smtp.gmail.com with ESMTPSA id q6sm101580380wjx.28.2016.01.07.07.24.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2016 07:24:37 -0800 (PST) From: Malcolm Matalka To: freebsd-hackers@freebsd.org Subject: Can PIPE_BUF be increased? Date: Thu, 07 Jan 2016 15:24:35 +0000 Message-ID: <86ziwho1jg.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 15:24:40 -0000 As far as I can tell, PIPE_BUF is 512 bytes by default. Using getconf and looking at the header files /usr/include. I'm writing a program that would benefit from a larger PIPE_BUF, is it possible to change this value? It looks like Linux and OS X have a higher default and OS X will do some magic to increase the size if necessary. I haven't found anything indicating the same in FreeBSD. Thanks, /Malcolm From owner-freebsd-hackers@freebsd.org Thu Jan 7 15:27:58 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59222A66544 for ; Thu, 7 Jan 2016 15:27:58 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 034C4175D for ; Thu, 7 Jan 2016 15:27:58 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id f206so102169755wmf.0 for ; Thu, 07 Jan 2016 07:27:57 -0800 (PST) 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=7/E040bytIFkAgrO0D35GvHfSnUY2W7ZR095cjO4R4c=; b=fG6mHvvwrOrSb5DyDIdU4iAXy5kSarw1CGdRI4xK9RU8wssief4YMn2bBjaZoavpTv CS5RHBm1jgkz1OqzCa4v/+/EM5pxUX7i1DaNUeQjenpODI2DH+2BvAWVwGHiVwyJ9EDh 9qrwJjfEvqj0WwPjqlbBTdibq+ackZj4xnh0cVIjVX0rYjM6lLlAfGsITcoXWcZnQbDq yWS5sAxK5KJe35wK//zJr32/TpW72d8kc80BKO/15AD7yPvTai/5wY8hLfsXxm7SnBzu 5/yYhRVXTeIoo4HT9lPLqorQdtpI2Cu8u0wpoUQzWaMtXbdqBJBVPithFCjaucJRKIKh +pBg== MIME-Version: 1.0 X-Received: by 10.28.153.148 with SMTP id b142mr18292412wme.5.1452180476600; Thu, 07 Jan 2016 07:27:56 -0800 (PST) Received: by 10.28.154.2 with HTTP; Thu, 7 Jan 2016 07:27:56 -0800 (PST) Received: by 10.28.154.2 with HTTP; Thu, 7 Jan 2016 07:27:56 -0800 (PST) In-Reply-To: <86ziwho1jg.fsf@gmail.com> References: <86ziwho1jg.fsf@gmail.com> Date: Thu, 7 Jan 2016 16:27:56 +0100 Message-ID: Subject: Re: Can PIPE_BUF be increased? From: Malcolm Matalka To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 15:27:58 -0000 Den 7 jan 2016 4:24 em skrev "Malcolm Matalka" : > > As far as I can tell, PIPE_BUF is 512 bytes by default. Using getconf > and looking at the header files /usr/include. I'm writing a program > that would benefit from a larger PIPE_BUF, is it possible to change this > value? It looks like Linux and OS X have a higher default and OS X will > do some magic to increase the size if necessary. I haven't found > anything indicating the same in FreeBSD. > I realized I might not be clear enough here: I'm trying to increase the number if bytes i can write to a pipe atomically. > Thanks, > /Malcolm > From owner-freebsd-hackers@freebsd.org Thu Jan 7 16:30:47 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E19FA67D28 for ; Thu, 7 Jan 2016 16:30:47 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mailhost.stack.nl", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B9F91556 for ; Thu, 7 Jan 2016 16:30:46 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 1F2A5358C67; Thu, 7 Jan 2016 17:30:42 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id CE02D28494; Thu, 7 Jan 2016 17:30:41 +0100 (CET) Date: Thu, 7 Jan 2016 17:30:41 +0100 From: Jilles Tjoelker To: Malcolm Matalka Cc: freebsd-hackers@freebsd.org Subject: Re: Can PIPE_BUF be increased? Message-ID: <20160107163041.GA35588@stack.nl> References: <86ziwho1jg.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 16:30:47 -0000 On Thu, Jan 07, 2016 at 04:27:56PM +0100, Malcolm Matalka wrote: > Den 7 jan 2016 4:24 em skrev "Malcolm Matalka" : > > As far as I can tell, PIPE_BUF is 512 bytes by default. Using > > getconf and looking at the header files /usr/include. I'm writing a > > program that would benefit from a larger PIPE_BUF, is it possible to > > change this value? It looks like Linux and OS X have a higher > > default and OS X will do some magic to increase the size if > > necessary. I haven't found anything indicating the same in FreeBSD. > I realized I might not be clear enough here: I'm trying to increase > the number if bytes i can write to a pipe atomically. An active pipe buffer is always at least 4096 bytes, so this value can be increased somewhat without increasing memory usage. Going all the way to 4096 is probably unwise since it may require -- in low memory situations -- the buffer to be emptied completely before select/poll/kqueue report the pipe as writable again. You will need to recompile the kernel and filesystem and ABI compatibility modules after making the change in sys/sys/syslimits.h. FreeBSD automatically resizes pipe buffers and copies large (>= 8192 bytes) blocking writes directly from sender to receiver, but this does not provide atomicity guarantees. -- Jilles Tjoelker From owner-freebsd-hackers@freebsd.org Thu Jan 7 17:09:43 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32A52A66DA6 for ; Thu, 7 Jan 2016 17:09:43 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D79301BDA for ; Thu, 7 Jan 2016 17:09:42 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id b14so133891668wmb.1 for ; Thu, 07 Jan 2016 09:09:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=inAJYkDmh18CCELnPKB1gbearTnTnTV7B6qMNm88bFs=; b=g1u1HTXfZjYrL48YRX541GCu5vr2L3Wa6HCmUNGihjC/MAqfu4t7Cnfe8WoClxDEPv 5LHhI0iiHrdp+IAJxKFsXIDrQ8hRSQWcdYDbuY04sPkTHQpJCMBDQDj5NGAb7NB3IQY1 Pq+hkeiHfMq4ewxgjE0OqN1vW3AgflmGHLmNWRWN3JZ4PQ+JnJbdo4xKL2wAafkt7C5Z 9AeDzGZs5/wqXwdPc5wf2K3cAxsIVjXcGZI363XrG0bhnp4GRUM/LcDEF66g1+HnJXXB kZnsNaD7e8sV93z+ca8QtQ32sUhoHhXh301M8A0HddY+g2Xe6h5UkTHOMNToY2rkfj1F +gSw== X-Received: by 10.194.22.167 with SMTP id e7mr5195908wjf.29.1452186581311; Thu, 07 Jan 2016 09:09:41 -0800 (PST) Received: from localhost (li195-236.members.linode.com. [178.79.139.236]) by smtp.gmail.com with ESMTPSA id kb5sm101552886wjc.20.2016.01.07.09.09.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2016 09:09:39 -0800 (PST) From: Malcolm Matalka To: Jilles Tjoelker Cc: freebsd-hackers@freebsd.org Subject: Re: Can PIPE_BUF be increased? References: <86ziwho1jg.fsf@gmail.com> <20160107163041.GA35588@stack.nl> Date: Thu, 07 Jan 2016 17:09:37 +0000 In-Reply-To: <20160107163041.GA35588@stack.nl> (Jilles Tjoelker's message of "Thu, 7 Jan 2016 17:30:41 +0100") Message-ID: <86vb75nwoe.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 17:09:43 -0000 Jilles Tjoelker writes: > On Thu, Jan 07, 2016 at 04:27:56PM +0100, Malcolm Matalka wrote: >> Den 7 jan 2016 4:24 em skrev "Malcolm Matalka" : > >> > As far as I can tell, PIPE_BUF is 512 bytes by default. Using >> > getconf and looking at the header files /usr/include. I'm writing a >> > program that would benefit from a larger PIPE_BUF, is it possible to >> > change this value? It looks like Linux and OS X have a higher >> > default and OS X will do some magic to increase the size if >> > necessary. I haven't found anything indicating the same in FreeBSD. > >> I realized I might not be clear enough here: I'm trying to increase >> the number if bytes i can write to a pipe atomically. > > An active pipe buffer is always at least 4096 bytes, so this value can > be increased somewhat without increasing memory usage. Going all the way > to 4096 is probably unwise since it may require -- in low memory > situations -- the buffer to be emptied completely before > select/poll/kqueue report the pipe as writable again. > > You will need to recompile the kernel and filesystem and ABI > compatibility modules after making the change in sys/sys/syslimits.h. > > FreeBSD automatically resizes pipe buffers and copies large (>= 8192 > bytes) blocking writes directly from sender to receiver, but this does > not provide atomicity guarantees. If I understand you correctly, I cannot do anything, with strong guarantees, without recompiling the kernel? Thank you for the answer! /Malcolm From owner-freebsd-hackers@freebsd.org Fri Jan 8 02:48:11 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D16F6A6667D for ; Fri, 8 Jan 2016 02:48:11 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 699DB1115 for ; Fri, 8 Jan 2016 02:48:10 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074423-f797f6d0000023d0-9a-568f23694f99 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id B5.30.09168.9632F865; Thu, 7 Jan 2016 21:48:09 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id u082m8or025151; Thu, 7 Jan 2016 21:48:08 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u082m5QC014195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 7 Jan 2016 21:48:08 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u082m5Sc022390; Thu, 7 Jan 2016 21:48:05 -0500 (EST) Date: Thu, 7 Jan 2016 21:48:04 -0500 (EST) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: grahamperrin cc: freebsd-hackers@freebsd.org Subject: Re: relaunchd: a portable clone of launchd In-Reply-To: <1452172449792-6065692.post@n5.nabble.com> Message-ID: References: <8FF83C2F-D8CD-4366-A890-7EF605050456@netgate.com> <1452172449792-6065692.post@n5.nabble.com> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprAKsWRmVeSWpSXmKPExsUixG6nopup3B9m8O8wn8X2zf8YLU61Gjgw ecz4NJ/FY+esu+wBTFFcNimpOZllqUX6dglcGZOWb2MsaOSq+HtiPXsD4wqOLkZODgkBE4n3 D7ayQ9hiEhfurWfrYuTiEBJYzCTx8cVVFpCEkMAGRonZF5wgEgeZJH5u+MUOkaiXaFi/nBXE ZhHQkji86BsTiM0moCbxeG8zK8RURYnNpyYxg9giApoSO6YfB6thFpCXuLD5ECOILSxgLDH1 yW6wGk4Bc4kNCy+wgdi8Ao4SbWd2sUAs3sws8bB/HdhiUQEdidX7p7BAFAlKnJz5hAViaIDE jxMnmSYwCs1CkpqFJAVhq0s0PjjLBmFrS9y/2ca2gJFlFaNsSm6Vbm5iZk5xarJucXJiXl5q ka6ZXm5miV5qSukmRnDAuyjvYPxzUOkQowAHoxIPL8eOvjAh1sSy4srcQ4ySHExKorzFgv1h QnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4JeSBcrwpiZVVqUX5MClpDhYlcd65X3zDhATSE0tS s1NTC1KLYLIyHBxKErzCSkCNgkWp6akVaZk5JQhpJg5OkOE8QMOVQGp4iwsSc4sz0yHypxgV pcR55UASAiCJjNI8uF5wQtrNpPqKURzoFWHenSBVPMBkBtf9CmgwE9BghqJukMEliQgpqQbG c7oXrcovqx5aUPHGJDw87mu1X+dPc45kgUty+bcfetftuejUKlGzMHiF+YQI3y3iJldXPlyy lXVl79XgWh9PlYtK9dMN/fvkb2661rPiOrPbxQbrXU06lb7Kf7w7FPYJzN92xXXi3V2lHzTk wmQun/8frN2YzKb2SeHYwgXTnMQPOZ3RuOOoxFKckWioxVxUnAgASjxG9CMDAAA= Content-Type: TEXT/PLAIN; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 02:48:12 -0000 On Thu, 7 Jan 2016, grahamperrin wrote: > nosh caught my eye a couple of months ago. Some attention to PC-BSD was > apparent so I posted highlights under > https://forums.pcbsd.org/thread-20272.html =E2=80=A6 ending when I found = a section > on the nosh project within the FreeBSD 2015Q3 status report. > > Re: the third call for 2015Q4 quarterly status reports > : > > * the deadline for submissions is today > > =E2=80=93 if it's not too late, I wonder whether something submitted *now= * could > help the report, when it appears, to put things in context without causin= g > unnecessary alarm. An explanation of how developments in both project are= as > (nosh and relaunchd) may be complementary. A submission on this topic would be welcomed even if it came in on Saturday (the 9th). -Ben (with monthly@ hat) From owner-freebsd-hackers@freebsd.org Fri Jan 8 08:06:56 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2A19A673FB for ; Fri, 8 Jan 2016 08:06:56 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B12061D63 for ; Fri, 8 Jan 2016 08:06:55 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from chamsa.cs.huji.ac.il ([132.65.80.19]) by kabab.cs.huji.ac.il with esmtp id 1aHS4H-000Eup-Eo for freebsd-hackers@freebsd.org; Fri, 08 Jan 2016 10:06:41 +0200 From: Daniel Braniss Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: watchdog not rebooting Message-Id: <95D6F157-70B1-48F3-B512-9A4B7D6F9EA4@cs.huji.ac.il> Date: Fri, 8 Jan 2016 10:06:41 +0200 To: Freebsd hackers list Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 08:06:57 -0000 Hi, on real hardware, with hardware watchdog, it does the right thing, = panics and reboots, but on vmware, it enters the debugger, and =E2=80=98cont=E2=80=99 will = resume. the kernel in both cases(it=E2=80=99s the same) has option KDB and = ALT_BREAK_TO_DEBUGGER so how can I get the vm to reboot? thanks, danny From owner-freebsd-hackers@freebsd.org Fri Jan 8 08:41:06 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFE68A67F8E for ; Fri, 8 Jan 2016 08:41:06 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5DF21081 for ; Fri, 8 Jan 2016 08:41:06 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: by mail-oi0-x22c.google.com with SMTP id o62so324894719oif.3 for ; Fri, 08 Jan 2016 00:41:06 -0800 (PST) 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=7sCGZGMD0FayOb0B0XaDBFNFQyP9jX0IMbk7k6Vth9s=; b=qKkocS5FsIWiQjfistRaiuysyC+GzwkHBREFfLAET1jFVFUZsfK3Fk+HXlcq7dZ474 Dw44ZUGDOJdsEzTQEvU8akeq0lrHcKGn0SDSdsojSTJjMwg8WK4bODjeb3WuORrX/zmt AlMztAiZFlQDD/+wpWXWGm1AZJEL8m4IZIGMq0Xwt+T8QyXmeqmqbyn7ngsyeFbf7j7X wKydwh1s1BIjZ2PHTnaYWLP5I/bJGffH7KqLLY8Rc/TEfWX2YSFHqJJKrFh+6uAWt0bm C8IVZNI/sKBdrU6YwFkUNTlWCpGC/5ZbTJwdsL4JjpyKzdrGlMLne9VaGJCq3vcSWzOK f9WQ== X-Received: by 10.202.88.130 with SMTP id m124mr78836117oib.36.1452242466032; Fri, 08 Jan 2016 00:41:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.202.72.197 with HTTP; Fri, 8 Jan 2016 00:40:26 -0800 (PST) In-Reply-To: <1452172449792-6065692.post@n5.nabble.com> References: <8FF83C2F-D8CD-4366-A890-7EF605050456@netgate.com> <1452172449792-6065692.post@n5.nabble.com> From: Outback Dingo Date: Fri, 8 Jan 2016 09:40:26 +0100 Message-ID: Subject: Re: relaunchd: a portable clone of launchd To: grahamperrin Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 08:41:07 -0000 On Thu, Jan 7, 2016 at 2:14 PM, grahamperrin wrote= : > I'm not a developer but I follow these discussions with interest. I'm a > former tester of OS X, in which launchd is (in my experience) very > satisfactory. > > > Mark Heily wrote > > Allow me to clarify the goals of relaunchd and how this affects the > > existing init(8) and rc(8) system in FreeBSD. > > > > Unlike the original launchd project, relaunchd is not trying to become > PID > > #1 or replace anything in the base system. I am simply asking for help > > getting it fixed up and committed to the ports tree, so it can become a= n > > alternative for people who want to configure their systems to take > > advantage of the featureset that launchd provides. Choice is good, and = I > > don't want to take away people's ability to use nosh, openrc, svc, or > > whatever else meets their needs. > > That seems reasonable. > > nosh caught my eye a couple of months ago. Some attention to PC-BSD was > apparent so I posted highlights under > https://forums.pcbsd.org/thread-20272.html =E2=80=A6 ending when I found = a section > on the nosh project within the FreeBSD 2015Q3 status report. > Everyone has and is entitled to their own opinions, and as such, those of us who have been involved in some of this have already reviewed the current technologies and the works in the past, that being said we have a difference of opinions on nosh and relaucnhd, of which have been reviewed heavily for merit on the basis of the works and technology by many people. Hashing this out and pointing to simple facts for myself and knowing the varied opinions of others, and has been expressed before. I find what has the most merit to date is the newer launchd project being done in NextBSD, even though in my own opinion, I would have preferred a non-mach implementation I can see the reasoning behind it. I cant quite grasp the reasoning for relaunchd itself, when there is already launchd_xml and the NextBSD launchd. However, the same with such as openrc, it does work quite well on FreeBSD. What i find troubling is the "fracture" with so many efforts in other directions, instead of a single effort in one direction. And the long term adoption of one of these efforts. Just because its been written about, doesnt mean that theres is even an interest. > > Re: the third call for 2015Q4 quarterly status reports > < > http://freebsd.1045724.n5.nabble.com/second-call-for-2015Q4-quarterly-sta= tus-reports-tp6063452p6064992.html > >: > > * the deadline for submissions is today > > =E2=80=93 if it's not too late, I wonder whether something submitted *now= * could > help the report, when it appears, to put things in context without causin= g > unnecessary alarm. An explanation of how developments in both project are= as > (nosh and relaunchd) may be complementary. > > > > I will try to develop relaunchd in such a way that it *could* be used t= o > > replace rc(8) if desired, but that would require a lot of work and > > discussion and buy-in from the FreeBSD project leadership. Because > > relaunchd is such a young project, I want to have more realistic goals > and > > not worry about what might happen in the longer term. I would consider = it > > a major success if, a year from now, the majority of the daemons in the > > ports tree offer support for running under launchd(8) in addition to th= e > > traditional rc(8) init scripts. > > > > > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/relaunchd-a-portable-clone-of-launch= d-tp6053155p6065692.html > Sent from the freebsd-hackers mailing list archive at Nabble.com. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://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 Jan 8 11:11:00 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0144A68804 for ; Fri, 8 Jan 2016 11:11:00 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 67DE3194D for ; Fri, 8 Jan 2016 11:11:00 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u08BAQuO061677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 8 Jan 2016 12:10:27 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: danny@cs.huji.ac.il Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u08BAKF6029780 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 8 Jan 2016 18:10:20 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: watchdog not rebooting To: Daniel Braniss , Freebsd hackers list References: <95D6F157-70B1-48F3-B512-9A4B7D6F9EA4@cs.huji.ac.il> From: Eugene Grosbein Message-ID: <568F9916.2000802@grosbein.net> Date: Fri, 8 Jan 2016 18:10:14 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <95D6F157-70B1-48F3-B512-9A4B7D6F9EA4@cs.huji.ac.il> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 11:11:00 -0000 08.01.2016 15:06, Daniel Braniss пишет: > Hi, > on real hardware, with hardware watchdog, it does the right thing, panics and reboots, > but on vmware, it enters the debugger, and ‘cont’ will resume. > the kernel in both cases(it’s the same) has option KDB and ALT_BREAK_TO_DEBUGGER > > so how can I get the vm to reboot? debug.debugger_on_panic=0 in the /boot/loader.conf and/or options KDB_UNATTENDED in the kernel config. From owner-freebsd-hackers@freebsd.org Fri Jan 8 11:14:16 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61DE5A68987 for ; Fri, 8 Jan 2016 11:14:16 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F23711C2D for ; Fri, 8 Jan 2016 11:14:15 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u08BDkAv061697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 8 Jan 2016 12:13:47 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: danny@cs.huji.ac.il Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u08BDgHe029810 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 8 Jan 2016 18:13:42 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: watchdog not rebooting To: Daniel Braniss , Freebsd hackers list References: <95D6F157-70B1-48F3-B512-9A4B7D6F9EA4@cs.huji.ac.il> <568F9916.2000802@grosbein.net> From: Eugene Grosbein Message-ID: <568F99E0.5080008@grosbein.net> Date: Fri, 8 Jan 2016 18:13:36 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <568F9916.2000802@grosbein.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 11:14:16 -0000 >> on real hardware, with hardware watchdog, it does the right thing, panics and reboots, >> but on vmware, it enters the debugger, and ‘cont’ will resume. >> the kernel in both cases(it’s the same) has option KDB and ALT_BREAK_TO_DEBUGGER >> >> so how can I get the vm to reboot? > > debug.debugger_on_panic=0 in the /boot/loader.conf and/or options KDB_UNATTENDED in the kernel config. Hmm, no - in case of watchdog, only kernel options KDB_UNATTENDED will help, debug.debugger_on_panic will not. From owner-freebsd-hackers@freebsd.org Fri Jan 8 15:00:11 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E386DA68889 for ; Fri, 8 Jan 2016 15:00:11 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CD2B1867 for ; Fri, 8 Jan 2016 15:00:11 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from e-bsd.cs.huji.ac.il ([132.65.80.241] helo=outmail.cs.huji.ac.il) by kabab.cs.huji.ac.il with esmtp id 1aHYWM-000JBa-Q7; Fri, 08 Jan 2016 17:00:06 +0200 Received: from [132.65.179.20] (helo=mbpro2.bs.cs.huji.ac.il) by outmail.cs.huji.ac.il with esmtpsa id 1aHYWM-000GQN-Mu; Fri, 08 Jan 2016 17:00:06 +0200 Subject: Re: watchdog not rebooting X-Apple-Auto-Saved: 1 X-Apple-Mail-Remote-Attachments: YES From: Daniel Braniss X-Apple-Base-Url: x-msg://9/ In-Reply-To: <568F99E0.5080008@grosbein.net> X-Apple-Windows-Friendly: 1 Date: Fri, 8 Jan 2016 16:51:06 +0200 Cc: Freebsd hackers list X-Apple-Mail-Signature: SKIP_SIGNATURE Message-Id: <5E7E2FE3-F461-434D-A846-3DE9F5E15A4E@cs.huji.ac.il> References: <95D6F157-70B1-48F3-B512-9A4B7D6F9EA4@cs.huji.ac.il> <568F9916.2000802@grosbein.net> <568F99E0.5080008@grosbein.net> X-Uniform-Type-Identifier: com.apple.mail-draft To: Eugene Grosbein X-Mailer: Apple Mail (2.3112) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 15:00:12 -0000 From owner-freebsd-hackers@freebsd.org Fri Jan 8 15:02:40 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C8A2A689F4 for ; Fri, 8 Jan 2016 15:02:40 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4706D1BAD for ; Fri, 8 Jan 2016 15:02:39 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from e-bsd.cs.huji.ac.il ([132.65.80.241] helo=outmail.cs.huji.ac.il) by kabab.cs.huji.ac.il with esmtp id 1aHYYn-000JJE-MN; Fri, 08 Jan 2016 17:02:37 +0200 Received: from [132.65.179.20] (helo=mbpro2.bs.cs.huji.ac.il) by outmail.cs.huji.ac.il with esmtpsa id 1aHYYn-000GQs-Is; Fri, 08 Jan 2016 17:02:37 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: watchdog not rebooting From: Daniel Braniss In-Reply-To: <568F99E0.5080008@grosbein.net> Date: Fri, 8 Jan 2016 17:02:36 +0200 Cc: Freebsd hackers list Content-Transfer-Encoding: quoted-printable Message-Id: References: <95D6F157-70B1-48F3-B512-9A4B7D6F9EA4@cs.huji.ac.il> <568F9916.2000802@grosbein.net> <568F99E0.5080008@grosbein.net> To: Eugene Grosbein X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 15:02:40 -0000 > On 8 Jan 2016, at 1:13 PM, Eugene Grosbein wrote: >=20 >>> on real hardware, with hardware watchdog, it does the right thing, = panics and reboots, >>> but on vmware, it enters the debugger, and =E2=80=98cont=E2=80=99 = will resume. >>> the kernel in both cases(it=E2=80=99s the same) has option KDB and = ALT_BREAK_TO_DEBUGGER >>>=20 >>> so how can I get the vm to reboot? >>=20 >> debug.debugger_on_panic=3D0 in the /boot/loader.conf and/or options = KDB_UNATTENDED in the kernel config. >=20 > Hmm, no - in case of watchdog, only kernel options KDB_UNATTENDED will = help, > debug.debugger_on_panic will not. >=20 I just tried an older kernel, 10.1, and it works as expected, with = debugger_on_panic =3D 0, it reboots. so something changed. I actually tried this on different hardware, and = so far it fails on 10.2 and works ok on 10.1= From owner-freebsd-hackers@freebsd.org Fri Jan 8 15:30:17 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 268FBA672C2 for ; Fri, 8 Jan 2016 15:30:17 +0000 (UTC) (envelope-from beckman@angryox.com) Received: from nog2.angryox.com (nog2.angryox.com [70.164.19.85]) by mx1.freebsd.org (Postfix) with ESMTP id CF4181AAB for ; Fri, 8 Jan 2016 15:30:16 +0000 (UTC) (envelope-from beckman@angryox.com) Received: by nog2.angryox.com (Postfix, from userid 1001) id 1EB4E171E679; Fri, 8 Jan 2016 15:20:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=angryox.com; s=powerfulgood; t=1452266446; bh=IWqwnzSx7rIMb6Cb2rxfIkS62WCWBa790oMWSWEo2FU=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=gkVsQux5dwi9/ScKfdmROL+wW4sBc4E6DPb2Brk49YnpknBZ4lWHUxJ+Zw6fvLr81 vgaBiyn4sFJrZ1W3U6Vp5KrbMB0aZWrFHmBW74/ASMzAqQkx6n6XduYyz2QMi1HSiL btT/MebXG9MJPVKd1YopV/DmcmURLU70GRfFlRfM= Received: from localhost (localhost [127.0.0.1]) by nog2.angryox.com (Postfix) with ESMTP id 1C889171E676; Fri, 8 Jan 2016 10:20:46 -0500 (EST) Date: Fri, 8 Jan 2016 10:20:46 -0500 From: Peter Beckman To: Dmitry Sivachenko cc: Mark Heily , FreeBSD Hackers , Jonathan de Boyne Pollard Subject: Re: relaunchd: a portable clone of launchd In-Reply-To: <817860B6-5D67-41A3-ADD7-9757C7E67C35@gmail.com> Message-ID: References: <5687D3A9.5050400@NTLWorld.com> <817860B6-5D67-41A3-ADD7-9757C7E67C35@gmail.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 15:30:17 -0000 On Thu, 7 Jan 2016, Dmitry Sivachenko wrote: > >> On 07 Jan 2016, at 05:12, Mark Heily wrote: >> >> On Sat, Jan 2, 2016 at 8:42 AM, Jonathan de Boyne Pollard >> wrote: >>> >>> I recommend, to anyone going down this route, looking towards finishing >>> systembsd, especially instead of inventing a wholly new suite of protocols. >>> >>> * https://uglyman.kremlin.cc/gitweb/gitweb.cgi?p=systembsd.git >>> * >>> http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/debian-systemd-packaging-hoo-hah.html >>> * https://news.ycombinator.com/item?id=10176275 >>> >>> The reason is that finishing systemdbsd will make happy all of the people >>> who want the desktop environments whose design is driven largely by Linux to >>> work on FreeBSD/PC-BSD. The desktop environments that they'd like to use >>> have been or are being modified to work with these daemons, over this D-Bus >>> protocol. >>> >> >> I strongly disagree with your recommendation to adopt DBus and systemd >> as core components of FreeBSD. >> >> From a practical perspective, the proposal has a low probability of >> success. Systemd is written for Linux and is largely driven by a >> commercial Linux vendor. It is a rapidly moving target, with no sense >> of scope or boundaries. It eagerly consumes the latest and greatest >> innovations in the Linux kernel, with open disdain for portability. >> >> From a philosophical perspective, I don't agree with the direction >> that systemd is taking Linux. It's one of the reasons I switched to >> BSD after many years in the Linux camp. To quote Spock, "Logic clearly >> dictates that the needs of the many outweigh the needs of the few". In >> case of FreeBSD, this means that the needs of the desktop users should >> not outweigh the needs of the server/jail/embedded/appliance users. My >> concern with systemd and DBus is that these tools are highly >> desktop-centric, and introduce a large degree of unwanted change, >> complexity, and risk to everyone else. > > > I totally agree. > > systemd is an ugly beast, solving simple problem in complex way. > > After using FreeBSD's rc system for years, I think that switching to something systemd-related would be huge mistake. > No reason to clone everything that happens in Linux world. Utterly and strongly agreed. --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ --------------------------------------------------------------------------- From owner-freebsd-hackers@freebsd.org Fri Jan 8 20:17:03 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60F1EA66F08 for ; Fri, 8 Jan 2016 20:17:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 41A821DD6; Fri, 8 Jan 2016 20:17:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B04EEB917; Fri, 8 Jan 2016 15:17:01 -0500 (EST) From: John Baldwin To: Andriy Gapon Cc: Ryan Stone , "freebsd-hackers@freebsd.org" Subject: Re: How to get anything useful out of kgdb? Date: Fri, 08 Jan 2016 12:05:59 -0800 Message-ID: <16207260.7oBjvc4tcM@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <560EF73A.8050505@FreeBSD.org> References: <554E41EE.2010202@ignoranthack.me> <1595419.L0rkNTMkPe@ralph.baldwin.cx> <560EF73A.8050505@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 08 Jan 2016 15:17:01 -0500 (EST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 20:17:03 -0000 On Saturday, October 03, 2015 12:29:30 AM Andriy Gapon wrote: > On 02/10/2015 19:12, John Baldwin wrote: > > On Friday, October 02, 2015 09:26:23 AM Andriy Gapon wrote: > >> On 15/05/2015 20:57, Ryan Stone wrote: > >>> *Sigh*, kgdb isn't unwinding the trap frame properly. You can try this to > >>> figure out where it was running: > >> > >> I wonder, what is a reason for this? > >> Can that be fixed in kgdb itself? > >> It seems that usually kgdb handles trap frames just fine, but not always? > > > > It should be fixable. If this doesn't work under newer kgdb let me know and I'll > > try to fix it. > > Okay, letting you know :-) > The backtraces from the in-tree kgdb and the newer kgdb both abort at the same > frame (output from the newer kgdb is in my message in another kgdb related thread). So I figured out why newer kgdb wasn't unwinding through NULL function pointer traps yesterday. I'm not sure if the fix will help with your case as well, but it might be worth trying. The changes are in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206044 -- John Baldwin