From owner-freebsd-hackers@freebsd.org Sun May 22 07:26:52 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 DF491B4482F; Sun, 22 May 2016 07:26:52 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CE39E131E; Sun, 22 May 2016 07:26:52 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1463902009908382.22307607552875; Sun, 22 May 2016 00:26:49 -0700 (PDT) Date: Sun, 22 May 2016 00:26:49 -0700 From: Matthew Macy To: "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <154d75bfa01.110355533120837.2862753920701204888@nextbsd.org> Subject: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 07:26:53 -0000 I'm happy to announce a call for testers for the 4.6 update of drm and i915. The driver has been successfully tested on IvyBridge, Haswell, Broadwell and Skylake. At least basic HW 3D acceleration should work, VGA and DP out are known to work. Video decode has only been tried once and that did not work. At this point I'm most interested in taking an inventory of what is broken where. My priorities are common sense: a) stability b) fixing 2D artifacts c) fixing 3D problems d) video decode d) output support e) other features At this time "prime" (needed for switching between GPUs, compute APIs, and DRI3) is not yet supported. All the pieces are in place but support existing functionality is a higher priority. Userptr (mapping user memory in to the driver) requires VM changes. Support is planned, but likely post-11. A few caveats are in order: - The only reported test on Sandy Bridge indicated severe artifacts. - Arrandale (pre-Sandy Bridge) and earlier are not yet supported by this update. The intel_i810 code has been heavily localized for FreeBSD making it more difficult to integrate. Thus there are holes in the gmch support. - This update is 64-bit only. There is no good reason to be running in 32-bit mode on any of the hardware supported by this driver. - Although it works fine for me on my Skylake the one other tester I have reports from indicates that the driver isn't actually attaching and creating aliases for the drm device nodes. Please send issue/success reports to the freebsd-x11 mailing list. I may be preoccupied with work matters for periods of time. Sending it to the list makes sure that the messages don't get lost. If you encounter problems with startx, please try loading the i915 kmod in isolation and make sure that it switches correctly to vt_fb. If you're not running efifb you'll notice a change in resolution. If it works but is slow or has artifacts you may try switching to UXA by removing /etc/X11/xorg.conf.d/20-intel.conf (if you're using the USB image). If you've built from source, try configuring SNA instead. SNA is much better behaved for me. The usual rules apply for kernel debugging. There should be copious information on that in the handbook and elsewhere. If that proves to be problematic for people I will send out a follow up mail. A couple observations: - The FreeBSD PTB insist that a debugger be in tree but that it pre-date GPL2, consequently kernels are, by default compiled with DWARF2 which is very poor at retain debug information in the presence of any optimization. If this is a problem, either recompile everything with -O0 (add CFLAGS += -O0 in drm2 and i915kms Makefiles, and pass COPTFLAGS=-O0 to buildkernel) or install a newer kgdb from ports. - The purpose of encrypted swap is that the data on disk be unrecoverable. This is somewhat at cross purposes with savecore. So don't do that. Now that this is out I will be switching gears to bringing up amdgpu and radeon support. I have no hardware that uses the radeon driver so I will have to rely on Jean for testing and support there. Those of you wishing to try your hand at testing from source can fetch our repo from github at: https://github.com/iotamudelta/freebsd-base-graphics Make sure to check out the drm-next-4.6 branch. If you'd rather just try it on a usb pen driver you can also obtain a prebuilt memstick image with this branch installed along with xorg and some commonly used ports at: http://www.bsddesktop.com/images/disk_YYMMDDHH.img.xz There is no root password and the user/pw is joeuser/joeuser. If you're curious about what's on it, the script used to create the image is here: http://www.bsddesktop.com/images/usbcreate.sh If you'd like to help out with collecting data on what laptops are supported please run Warren Block's notebookstats script: http://www.bsddesktop.com/images/notebookstats It's also installed under /usr/local/bin on the image. If I've missed anything please let me know and I will follow up. -M From owner-freebsd-hackers@freebsd.org Sun May 22 08:14:26 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 32B86B44654; Sun, 22 May 2016 08:14:26 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC8731DB3; Sun, 22 May 2016 08:14:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1b4OWe-0009ow-Ti; Sun, 22 May 2016 11:14:16 +0300 Date: Sun, 22 May 2016 11:14:16 +0300 From: Slawa Olhovchenkov To: Matthew Macy Cc: "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported Message-ID: <20160522081416.GU1447@zxy.spb.ru> References: <154d75bfa01.110355533120837.2862753920701204888@nextbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <154d75bfa01.110355533120837.2862753920701204888@nextbsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 08:14:26 -0000 On Sun, May 22, 2016 at 12:26:49AM -0700, Matthew Macy wrote: > I'm happy to announce a call for testers for the 4.6 update of drm and > i915. The driver has been successfully tested on IvyBridge, Haswell, > Broadwell and Skylake. At least basic HW 3D acceleration should work, > VGA and DP out are known to work. Video decode has only been tried > once and that did not work. > > At this point I'm most interested in taking an inventory of what is > broken where. My priorities are common sense: > > a) stability > b) fixing 2D artifacts > c) fixing 3D problems > d) video decode > d) output support > e) other features > > At this time "prime" (needed for switching between GPUs, compute > APIs, and DRI3) is not yet supported. All the pieces are in place but > support existing functionality is a higher priority. Userptr (mapping > user memory in to the driver) requires VM changes. Support is > planned, but likely post-11. Can you do commit placeholder changes for VM for future MFC? From owner-freebsd-hackers@freebsd.org Sun May 22 07:20:39 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 700C9B44639; Sun, 22 May 2016 07:20:39 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 51AE31F4E; Sun, 22 May 2016 07:20:38 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1463901630376682.8613684666619; Sun, 22 May 2016 00:20:30 -0700 (PDT) Date: Sun, 22 May 2016 00:20:30 -0700 From: Matthew Macy To: "freebsd-current@freebsd.org" , "freebsd-x11@freebsd.org" , "freebsd-hackers@freebsd.org" Message-ID: <154d7562f75.116fac600120763.1508477402245154899@nextbsd.org> Subject: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-Mailman-Approved-At: Sun, 22 May 2016 11:16:15 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 07:20:39 -0000 I'm happy to announce a call for testers for the 4.6 update of drm and i915. The driver has been successfully tested on IvyBridge, Haswell, Broadwell and Skylake. At least basic HW 3D acceleration should work, VGA and DP out are known to work. Video decode has only been tried once and that did not work. At this point I'm most interested in taking an inventory of what is broken where. My priorities are common sense: a) stability b) fixing 2D artifacts c) fixing 3D problems d) video decode=20 d) output support e) other features At this time "prime" (needed for switching between GPUs, compute APIs, and DRI3) is not yet supported. All the pieces are in place but support existing functionality is a higher priority. Userptr (mapping user memory in to the driver) requires VM changes. Support is planned, but likely post-11. A few caveats are in order: - The only reported test on Sandy Bridge indicated severe artifacts. - Arrandale (pre-Sandy Bridge) and earlier are not yet supported by =C2=A0 this update. The intel_i810 code has been heavily localized for=20 =C2=A0 FreeBSD making it more difficult to integrate. Thus there are =C2=A0 holes in the gmch support. - This update is 64-bit only. There is no good reason to be running =C2=A0 in 32-bit mode on any of the hardware supported by this driver. - Although it works fine for me on my Skylake the one other tester =C2=A0 I have reports from indicates that the driver isn't actually =C2=A0 attaching and creating aliases for the drm device nodes. Please send issue/success reports to the freebsd-x11 mailing list. I may be preoccupied with work matters for periods of time. Sending it to the list makes sure that the messages don't get lost. If you encounter problems with startx, please try loading the i915 kmod in isolation and make sure that it switches correctly to vt_fb. If you're not running efifb you'll notice a change in resolution. If it works but is slow or has artifacts you may try switching to UXA by removing =C2=A0/etc/X11/xorg.conf.d/20-intel.conf (if you're using the USB image). If you've built from source, try configuring SNA instead. SNA is much better behaved for me. The usual rules apply for kernel debugging. There should be copious information on that in the handbook and elsewhere. If that proves to be problematic for people I will send out a follow up mail. A couple observations: - The FreeBSD PTB insist that a debugger be in tree but that it =C2=A0 pre-date GPL2, consequently kernels are, by default compiled with =C2=A0 DWARF2 which is very poor at retain debug information in the =C2=A0 presence of any optimization. If this is a problem, either =C2=A0 recompile everything with -O0 (add CFLAGS +=3D -O0 in drm2 and =C2=A0 i915kms Makefiles, and pass COPTFLAGS=3D-O0 to buildkernel) or =C2=A0 install a newer kgdb from ports. - The purpose of encrypted swap is that the data on disk be =C2=A0 unrecoverable. This is somewhat at cross purposes with savecore. =C2=A0 So don't do that. =C2=A0=20 Now that this is out I will be switching gears to bringing up amdgpu and radeon support. I have no hardware that uses the radeon driver so I will have to rely on Jean for testing and support there. Those of you wishing to try your hand at testing from source can fetch our repo from github at: https://github.com/iotamudelta/freebsd-base-graphics Make sure to check out the drm-next-4.6 branch. If you'd rather just try it on a usb pen driver you can also obtain a prebuilt memstick image with this branch installed along with xorg and some commonly used ports at:=20 http://www.bsddesktop.com/images/disk_YYMMDDHH.img.xz There is no root password and the user/pw is joeuser/joeuser. If you're curious about what's on it, the script used to create the image is here: http://www.bsddesktop.com/images/usbcreate.sh If you'd like to help out with collecting data on what laptops are supported please run Warren Block's notebookstats script: http://www.bsddesktop.com/images/notebookstats It's also installed under /usr/local/bin on the image. If I've missed anything please let me know and I will follow up. -M From owner-freebsd-hackers@freebsd.org Sun May 22 12:40:52 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 E27DAB450F6 for ; Sun, 22 May 2016 12:40:52 +0000 (UTC) (envelope-from kefehcollins@gmail.com) Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (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 ABEAC1FDE for ; Sun, 22 May 2016 12:40:52 +0000 (UTC) (envelope-from kefehcollins@gmail.com) Received: by mail-io0-x242.google.com with SMTP id s67so959387ios.0 for ; Sun, 22 May 2016 05:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=2veJlBahkUYNvVm3DnAuPZWNiD+hSkSJDnlpKxI1mBU=; b=AvrrT4xwlJcEBfCHC11bRAkb7Zldli9QHlizvg3QFcmRzlu7Wf8r8t7qe9XFxGaVMw TQFRy/fxdgphr8YflFF023erDIDviwuzI+2JeD7Fk64w+702cG/KNPPbITqPVLzwbZho PKg8oSgaoiLeqXtbaEfFGqK6dM8nFe92G5qVn56VUztBPVaADEoGYDzg1ryaIwZUsWvQ rjwClOVEf8dVEIFtrmb2zhAjYwvWgdecqZznxoCNT/QywIM2RpW6KTJJeuADkFTPPyAW wK2whtIby1j6tRgrSlM/HhYTEY2FjgIDGKZSVPANlOKVw2Jc+pVl5f9tOQqFRwZSuKvA wk4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=2veJlBahkUYNvVm3DnAuPZWNiD+hSkSJDnlpKxI1mBU=; b=A35oNHnfUDt9IvsLY4YHuCFASUE0RfnKk2svijeKPtdWR2nvQrcgX/5zKVRlZZNEVo NQeL5fjE+NinTmJbhSB6iK5Iers8Pl7t824BV5jk2BF2Xe4fxKCHd7qoFW0+KRq3adRY 24kqH3FfFDpzDyQTf4dz7f7efm2JjoA07DFN48zlml0b4QANwJpHg+pKBa0WJr/A5+MO f7PTnzJMgOhyxHmImHZ518Nxam5Ujs/+8ObrccmIdQGH9uWgECO7XZQzJB4WXYTK3oql 1cT+2gRizllQanuZncWpO0pXGnyn+igbm3o2qClrYW8S4tDffS1Rf9pjwatbgt77h9X8 eS0g== X-Gm-Message-State: AOPr4FUbIf9XPzcUYZfQXqI1Dqd1zzSqbK2nurmi4iffGY3pCWQweimzxxffIxUL/jxxTTEvtoBSA7GNSd8dSw== MIME-Version: 1.0 X-Received: by 10.107.11.18 with SMTP id v18mr7214725ioi.184.1463920851922; Sun, 22 May 2016 05:40:51 -0700 (PDT) Received: by 10.64.228.70 with HTTP; Sun, 22 May 2016 05:40:51 -0700 (PDT) Date: Sun, 22 May 2016 13:40:51 +0100 Message-ID: Subject: contributing to open source From: Kefeh Collins To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 12:40:53 -0000 hello i am a second year computer science student, program in c and c++ and am interested in contributing in operating system (kernel) directed projects please i need guidance thanks in advance From owner-freebsd-hackers@freebsd.org Sun May 22 17:54:55 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 3436EB456A4 for ; Sun, 22 May 2016 17:54:55 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (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 E41AF1713 for ; Sun, 22 May 2016 17:54:54 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: by mail-vk0-x235.google.com with SMTP id r140so20802573vkf.0 for ; Sun, 22 May 2016 10:54:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=NWX89KF5DJkQz5ljFm6Uf1LKoN6e9n29LRvegt3nZhc=; b=WvbD4i2tOw9h8zrhVnTOMRBdHpXY5wCiNHWvQV+6w/QNyQ6FuV+meQS7GVTM9hJrHf 5pP8wmCeswGLE+F3ps6XXmytfWqwqRNUi048KA4O4P0BMYtzyDM8Xg2TFowAIR0Pj25r hXLJfgjjr4dnmOCh3uRcHn8LND9cBzfK90jSLCcZuXQNupkbF4AsvVpYPVfonZqSjnnQ eQQ3bpwDn5rXe7GdrIx+91+9SgNH4eGWlBOnJu+DdxGb6YsIrn4+nSNh8Nf9Kr0p5QQw 0LQOBo57sem2IZPtBF1Oiz9Y/KShDlbLCEy5bzhlsQ1E8LbRaTZduL+AN2TE/gCHi7yU 7oKQ== 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; bh=NWX89KF5DJkQz5ljFm6Uf1LKoN6e9n29LRvegt3nZhc=; b=DBTPb29pX9Gpm1mn3N4YGWcZYtcPcgCV7axZYSLBi8cwC6WLUWqLqjZos/PLKXbFsB W5JlLmsJS0RG1hYo3AuVgAXYjAWwEB9c+j1EMnhgAgG+AcIUNd6eHf/LuAY3kSAs/mIZ 5HKOpdVDoJikCLhn0Xqk6VNkMHFrXZnGRPT7wSrh/cEZ55ygRkvoWNEfwnWf9YXBHw1v w+CyOjLkfNE2bAUGFQ4yieH+jtNvogrHjbdXf7a7ebOIoqLdb/TBp2RCpyaW7mfpgm+a mowSikB9Dg6EnQNBoy8fIJhzIQx5b64WTlD+UHw4rm4K4UdNxWKBIlTydk9pmcY1IyEm gBGA== X-Gm-Message-State: AOPr4FVkGiqffuIeYjklmaW8+0o229+CnfKZFjkM0UwEHqdGV5SBVjWIrqlxy8Sdqq/A7QlNeGkAsGb/HDF4cQ== MIME-Version: 1.0 X-Received: by 10.31.162.203 with SMTP id l194mr7603694vke.116.1463939694027; Sun, 22 May 2016 10:54:54 -0700 (PDT) Received: by 10.103.21.135 with HTTP; Sun, 22 May 2016 10:54:53 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 May 2016 13:54:53 -0400 Message-ID: Subject: Re: contributing to open source From: Joe Nosay To: Kefeh Collins Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 17:54:55 -0000 You need to clarify that which you are asking. In the skill set that you have, what do you create naturally? Now, think about applying that knowledge of C and C++ to an application that you find beneficial to others and yourself. The first thing for you to do is to install the system on a variety of computers. You need some of different architectures. Why? Because every CPU is not designed to do the same job; nor are they going to perform the same way. Grab yourself an UltraSPARC station, a PowerMac G4, a PowerMac G5, a Raspberry pi, and two standard AMD64 laptops - they will be for both 32 bit and 64 bit compiling. You will need to take notes on paper because the system is simple and complex at the same time. The kernel has to match the hardware; and, you will need to learn a few more languages. You have forth, lua, haskell, pascal, python, and java as a start. You will need to learn to map the devices before you think of using them. Believe me, it makes sense. You are going to have to correct a lot of software errors. And, you will have to deal with people on a personal basis. This means you need to write more legibly. On Sun, May 22, 2016 at 8:40 AM, Kefeh Collins wrote: > hello > i am a second year computer science student, program in c and c++ and am > interested in contributing in operating system (kernel) directed projects > please i need guidance > > thanks in advance > _______________________________________________ > 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 May 22 18:51: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 8E535B45798 for ; Sun, 22 May 2016 18:51:08 +0000 (UTC) (envelope-from tyler@tysdomain.com) Received: from tds-solutions.net (tds-solutions.net [174.136.96.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6E9C31653 for ; Sun, 22 May 2016 18:51:08 +0000 (UTC) (envelope-from tyler@tysdomain.com) Received: from tds-solutions.net (localhost [127.0.0.1]) by tds-solutions.net (Postfix) with ESMTP id 5355C2087901; Sun, 22 May 2016 14:51:02 -0400 (EDT) X-Virus-Scanned: amavisd-new at tds-solutions.net Received: from tds-solutions.net ([127.0.0.1]) by tds-solutions.net (tds-solutions.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id NlN5fFoQCht3; Sun, 22 May 2016 14:51:01 -0400 (EDT) Received: from [10.21.96.50] (c-24-147-10-153.hsd1.ma.comcast.net [24.147.10.153]) (Authenticated sender: sorressean) by tds-solutions.net (Postfix) with ESMTPSA id 6610F208779C; Sun, 22 May 2016 14:51:01 -0400 (EDT) Reply-To: tyler@tysdomain.com Subject: Re: contributing to open source References: To: Joe Nosay , Kefeh Collins Cc: FreeBSD Hackers From: "Littlefield, Tyler" Message-ID: <1944f9ca-14fa-9839-11bc-b7597337866f@tysdomain.com> Date: Sun, 22 May 2016 14:50:31 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 18:51:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pleas disregard everything that was previously mentioned in the email below mine. I don't like to top post, but I also don't like to quote such garbage. firstly, to the writing better: english is not everyone's first language. Also see [1]. Secondly, you do not need to get 90 different systems to contribute to development. If you have unsupported hardware, you could begin by working on drivers for that hardware. Otherwise, check out the FreeBSD wiki page at [2] for a todo. [1]: https://en.wikipedia.org/wiki/Muphry's_law [2]: https://wiki.freebsd.org/IdeasPage On 5/22/2016 1:54 PM, Joe Nosay wrote: > You need to clarify that which you are asking. In the skill set > that you have, what do you create naturally? Now, think about > applying that knowledge of C and C++ to an application that you > find beneficial to others and yourself. The first thing for you to > do is to install the system on a variety of computers. You need > some of different architectures. Why? Because every CPU is not > designed to do the same job; nor are they going to perform the > same way. Grab yourself an UltraSPARC station, a PowerMac G4, a > PowerMac G5, a Raspberry pi, and two standard AMD64 laptops - they > will be for both 32 bit and 64 bit compiling. You will need to take > notes on paper because the system is simple and complex at the same > time. The kernel has to match the hardware; and, you will need to > learn a few more languages. You have forth, lua, haskell, pascal, > python, and java as a start. You will need to learn to map the > devices before you think of using them. Believe me, it makes > sense. You are going to have to correct a lot of software errors. > And, you will have to deal with people on a personal basis. This > means you need to write more legibly. > > On Sun, May 22, 2016 at 8:40 AM, Kefeh Collins > wrote: > >> hello i am a second year computer science student, program in c >> and c++ and am interested in contributing in operating system >> (kernel) directed projects please i need guidance >> >> thanks in advance >> _______________________________________________ >> 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" >> > _______________________________________________ > 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" > - -- Take care, Ty Twitter: @sorressean Web: https://tysdomain.com Pubkey: https://tysdomain.com/files/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJXQf93AAoJEAdP60+BYxejCuMH/j35STynOYCiZ0zXKQpYtKDv No4Q4BJEffy1m/+WZEXtx1lYodh+5x3k5yMX9OZb1f1lmBoosekCaG5I+llX+SMU h/7cseAerswGMap+NzmFJdDVBfN+x/70+zp5i2jqjMrbvrDgrEUYwNY8JbzA5q1L N32Y+EC3ey+Mg9O03K/qqTIbDGkBZsCK6Dimvnx8iKYZsbHl4FiYHbM1u61mlauC MM+cHETuZ4TiOCYAJ4d0KuF83YfcMhbMr6FFXZNHMtHN7mIx4aVJdK4CLLJHd/d/ +U5LwMUN1e55cVqEWw4sUB8QsKIhnF3Ia4yZgucH6K0J80E2RMqLnuftnr1IiK4= =+n/7 -----END PGP SIGNATURE----- From owner-freebsd-hackers@freebsd.org Sun May 22 20:43: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 665C9B4566E for ; Sun, 22 May 2016 20:43:00 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::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 148BE10C4 for ; Sun, 22 May 2016 20:43:00 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: by mail-vk0-x230.google.com with SMTP id f66so201033659vkh.2 for ; Sun, 22 May 2016 13:43:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Zi/5BLzAAu8+NJkEl253lpgO9Py9jK74J7WZ/FMM+/U=; b=zjoAwUgtO7FDLrNajw8INLnSP9ezHPdjZY54ymPiyxfrm8uVOkpTBIr6O1mM+uHHEr OTLMwxZw44m+Bgh3ACJO3EctRMWA84/ZsMLruzpiMgOqizlwuPXKXO3BfHZxozsXj4If CjPKfpnkUozH2lwmy1kjkg6I3PZnfQ7ylPu+8w5SXcblBmORT8EMCrQ8V1mUfCYl72+F WR1QUw+HQ56fxbOpzHh20Vaxfx1pA8MfcRyqaUTyGgHRbpo1mejfxPBULCbu7edyA5AU /Sh1VIq8HdrpdNRfczwgQVTw4CSSxbi/ZfUftj99D1NmMh34M/vO2iz3joWkx2M6e5ez VQsg== 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; bh=Zi/5BLzAAu8+NJkEl253lpgO9Py9jK74J7WZ/FMM+/U=; b=Nc1IVjV1Hcj+cVD4ev40BdXMv/l5S0CydHCkArknT5lUGwxyWNeY+4XyjCMal6+dpQ oCnOB3GgFNcKo39rK2hDsXvuqIL1Jbl6e9kOGyd/1TFHIO3ucyxboLzxMIKI4mC4Zbwl zH+fW+ytl0CUm6JhfcTkBfhtAOeGnHblNE//dL7VfRlrXm5Nx3lbwkfKY+sY3KmHbkE2 b+O3Ss5TkfQ+CJNTC/x10qZ36bGBNGwfVBqc39LDjYhRoCCed6qEZ+Ia/JLglkrzvnjI t54SOrnMmA3n2b6n6Vz5VNUDsfhhvvg9Lb44Fgf4arrkOciphNxKJalEsPnXUOxfJRsy U6NA== X-Gm-Message-State: ALyK8tLuHsKo0y1eDUkbHjehvjOajLOpQi+ttmasoZcyQJnnwf+tUGKej6FP2+cKCVMph+i0P2PiSOO3zCNnxA== MIME-Version: 1.0 X-Received: by 10.176.2.151 with SMTP id 23mr1612294uah.106.1463949779191; Sun, 22 May 2016 13:42:59 -0700 (PDT) Received: by 10.103.21.135 with HTTP; Sun, 22 May 2016 13:42:59 -0700 (PDT) In-Reply-To: <1944f9ca-14fa-9839-11bc-b7597337866f@tysdomain.com> References: <1944f9ca-14fa-9839-11bc-b7597337866f@tysdomain.com> Date: Sun, 22 May 2016 16:42:59 -0400 Message-ID: Subject: Re: contributing to open source From: Joe Nosay To: sorressean Cc: Kefeh Collins , FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 20:43:00 -0000 Had you replied to the gentleman before I did, the conversation would not have been printed. Yes, start with one computer; and, if you have a certain idea in mind, research what would be best and go from there. My mother is Brazilian and her native language is portuguese. Don't play that with me again, understand. I took everything into consideration. With that aside, please enjoy your stay with us. On Sun, May 22, 2016 at 2:50 PM, Littlefield, Tyler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Pleas disregard everything that was previously mentioned in the email > below mine. I don't like to top post, but I also don't like to quote > such garbage. > firstly, to the writing better: english is not everyone's first > language. Also see [1]. > Secondly, you do not need to get 90 different systems to contribute to > development. If you have unsupported hardware, you could begin by > working on drivers for that hardware. Otherwise, check out the FreeBSD > wiki page at [2] for a todo. > [1]: https://en.wikipedia.org/wiki/Muphry's_law > [2]: https://wiki.freebsd.org/IdeasPage > On 5/22/2016 1:54 PM, Joe Nosay wrote: > > You need to clarify that which you are asking. In the skill set > > that you have, what do you create naturally? Now, think about > > applying that knowledge of C and C++ to an application that you > > find beneficial to others and yourself. The first thing for you to > > do is to install the system on a variety of computers. You need > > some of different architectures. Why? Because every CPU is not > > designed to do the same job; nor are they going to perform the > > same way. Grab yourself an UltraSPARC station, a PowerMac G4, a > > PowerMac G5, a Raspberry pi, and two standard AMD64 laptops - they > > will be for both 32 bit and 64 bit compiling. You will need to take > > notes on paper because the system is simple and complex at the same > > time. The kernel has to match the hardware; and, you will need to > > learn a few more languages. You have forth, lua, haskell, pascal, > > python, and java as a start. You will need to learn to map the > > devices before you think of using them. Believe me, it makes > > sense. You are going to have to correct a lot of software errors. > > And, you will have to deal with people on a personal basis. This > > means you need to write more legibly. > > > > On Sun, May 22, 2016 at 8:40 AM, Kefeh Collins > > wrote: > > > >> hello i am a second year computer science student, program in c > >> and c++ and am interested in contributing in operating system > >> (kernel) directed projects please i need guidance > >> > >> thanks in advance > >> _______________________________________________ > >> 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" > >> > > _______________________________________________ > > 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" > > > > > - -- > Take care, > Ty > Twitter: @sorressean > Web: https://tysdomain.com > Pubkey: https://tysdomain.com/files/pubkey.asc > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBAgAGBQJXQf93AAoJEAdP60+BYxejCuMH/j35STynOYCiZ0zXKQpYtKDv > No4Q4BJEffy1m/+WZEXtx1lYodh+5x3k5yMX9OZb1f1lmBoosekCaG5I+llX+SMU > h/7cseAerswGMap+NzmFJdDVBfN+x/70+zp5i2jqjMrbvrDgrEUYwNY8JbzA5q1L > N32Y+EC3ey+Mg9O03K/qqTIbDGkBZsCK6Dimvnx8iKYZsbHl4FiYHbM1u61mlauC > MM+cHETuZ4TiOCYAJ4d0KuF83YfcMhbMr6FFXZNHMtHN7mIx4aVJdK4CLLJHd/d/ > +U5LwMUN1e55cVqEWw4sUB8QsKIhnF3Ia4yZgucH6K0J80E2RMqLnuftnr1IiK4= > =+n/7 > -----END PGP SIGNATURE----- > From owner-freebsd-hackers@freebsd.org Sun May 22 21:01: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 0F275B45CCE for ; Sun, 22 May 2016 21:01:16 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 508901110 for ; Sun, 22 May 2016 21:01:14 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: (qmail 78938 invoked from network); 22 May 2016 20:54:30 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 22 May 2016 20:54:30 -0000 To: freebsd-hackers@freebsd.org From: Dirk Engling Subject: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: Date: Sun, 22 May 2016 22:54:30 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 21:01:16 -0000 When trying to bsdiff two DVD images, I noticed it failing due to read(2) returning EINVAL to the tool. man 2 read says, this would only happen for a negative value for fildes, which clearly was not true. After more digging I found that read internally wraps a single call to readv, preparing a temporary struct iovec. man 2 readv in turn says that it will fail with EINVAL, if The sum of the iov_len values in the iov array overflowed a 32-bit integer. I saw the same behaviour on a linux system, so I kind of assume there is a standard that allows read(2) doing that. Still I think that 1) the man page must be corrected to match this behaviour, or 2) the read(2) syscall must wrap multiple calls to readv However, the http://www.daemonology.net/bsdiff/ page claims that: Providing that off_t is defined properly, bsdiff and bspatch support files of up to 2^61-1 = 2Ei-1 bytes. which I could not confirm on any system. I could easily fix this by using mmap instead of read to get pointers to file contents. Now, where should I start? erdgeist From owner-freebsd-hackers@freebsd.org Sun May 22 21:36:31 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 E3429B46B9E for ; Sun, 22 May 2016 21:36:31 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-1.mit.edu (dmz-mailsec-scanner-1.mit.edu [18.9.25.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9111019A5 for ; Sun, 22 May 2016 21:36:31 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190c-12fff7000000490a-7e-57422529d48e Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 1E.A5.18698.92522475; Sun, 22 May 2016 17:31:21 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id u4MLVLhp022076; Sun, 22 May 2016 17:31:21 -0400 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 u4MLVHkZ013451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 22 May 2016 17:31:20 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u4MLVGgS005806; Sun, 22 May 2016 17:31:16 -0400 (EDT) Date: Sun, 22 May 2016 17:31:16 -0400 (EDT) From: Benjamin Kaduk To: Kefeh Collins cc: freebsd-hackers@freebsd.org Subject: Re: contributing to open source 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+NgFnrDIsWRmVeSWpSXmKPExsUixG6nrqup6hRucHyCjsX2zf8YLWa+usPk wOQx49N8Fo+ds+6yBzBFcdmkpOZklqUW6dslcGWcefSQvaCHtWLN2rWMDYytLF2MnBwSAiYS i689ZOti5OIQEmhjkphx4hgzhLORUWLpka/sEM4hJonO9l5WkBYhgQZGiU+747sYOThYBLQl nsz0BgmzCahIzHyzkQ3EFhHQkngx/xqYzSwgL3Fh8yFGEFtYQEPi5pUVTCA2p0CgxLSfZ8Gu 4BVwlLi16CoLxPgAiX0b5zOD2KICOhKr90+BqhGUODnzCQvETC2J5dO3sUxgFJiFJDULSWoB I9MqRtmU3Crd3MTMnOLUZN3i5MS8vNQiXUO93MwSvdSU0k2MoIDklOTZwXjmjdchRgEORiUe Xg4Wp3Ah1sSy4srcQ4ySHExKoryp3fbhQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4Gd45hgvx piRWVqUW5cOkpDlYlMR5C/efDhMSSE8sSc1OTS1ILYLJynBwKEnw+qkA7REsSk1PrUjLzClB SDNxcIIM5wEavg2khre4IDG3ODMdIn+KUZdjwY/ba5mEWPLy81KlxHkbQYoEQIoySvPg5oAT yW4m1VeM4kBvCfO+UAaq4gEmIbhJr4CWMAEteSjtALKkJBEhJdXAqBl6tVq1NaEqXOra9Zrn wT29+Vc59Dv8JllenT2n7N+tz9x2Zu8qQs6dWPZmi7aC8b7VCh0qOUeWcVQ02bZvW8fe8fOq g1LdqoNrFmfNuaNk/NVu3pxd3BsDD25f28lX+qZ7UluQ8Asjh4jOOY6dD2yfue4Vef+R75/g SZ52bw47Oa1317X2K7EUZyQaajEXFScCAM0GLOX/AgAA X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 21:36:32 -0000 On Sun, 22 May 2016, Kefeh Collins wrote: > hello > i am a second year computer science student, program in c and c++ and am > interested in contributing in operating system (kernel) directed projects > please i need guidance A couple of thoughts: (1) There's an "ideas list" at https://wiki.freebsd.org/IdeasPage and links to some other things as well, if you are just wanting potential topics to work on (2) You might try to join an IRC channel or two to get a sense for what is going on and get to know some other developers. #bsdcode or #bsddev on EFnet come to mind, but see also https://wiki.freebsd.org/IrcChannels -Ben From owner-freebsd-hackers@freebsd.org Sun May 22 22:29:39 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 D6582B455EB for ; Sun, 22 May 2016 22:29:39 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id B70861B32 for ; Sun, 22 May 2016 22:29:39 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 06DEE17E82; Sun, 22 May 2016 15:29:38 -0700 (PDT) Date: Sun, 22 May 2016 15:29:37 -0700 From: hiren panchasara To: Benjamin Kaduk Cc: Kefeh Collins , freebsd-hackers@freebsd.org Subject: Re: contributing to open source Message-ID: <20160522222937.GG41763@strugglingcoder.info> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pE2VAHO2njSJCslu" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 22:29:39 -0000 --pE2VAHO2njSJCslu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 05/22/16 at 05:31P, Benjamin Kaduk wrote: > On Sun, 22 May 2016, Kefeh Collins wrote: >=20 > > hello > > i am a second year computer science student, program in c and c++ and = am > > interested in contributing in operating system (kernel) directed projec= ts > > please i need guidance >=20 > A couple of thoughts: >=20 > (1) There's an "ideas list" at https://wiki.freebsd.org/IdeasPage and > links to some other things as well, if you are just wanting potential > topics to work on >=20 > (2) You might try to join an IRC channel or two to get a sense for what is > going on and get to know some other developers. #bsdcode or #bsddev on > EFnet come to mind, but see also https://wiki.freebsd.org/IrcChannels Good points, Ben. I'd add: (3) Look at https://bugs.freebsd.org/bugzilla/ and see if you can find anything you'd like to work on. If you do, propose a patch or ask a question there without hesitation. (4) If you are interested/willing, you can setup a machine (or a VM) running FreeBSD. (Not directly related to programming but this can give you a good idea of how FreeBSD works.) Thank you for your interest in FreeBSD! Cheers, Hiren --pE2VAHO2njSJCslu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJXQjLOXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lVB0H/0fgGKnmS2HjZDMiTJTlhtjQ c/VHvovlwATclGU8a8K0UVOzr2I5HFqm6xtms3/loP15oh4ocToTvghfL3A1c7Db Gw9dJW5cm5OU7sQFqBsQ1+iVGm5XJIGJVlCtNO/VPn2d9Ne9jg2Xh6GX4eaNVgDf ktgK+pdQnxLN58MXZhDxoLF3BLyMsCu38rrPN+PjIVNcOZTnc/+LEgF1gcYKGU0s Br9LewAu55FlFsAse2ECjPc9loZ/PGHqRdC85EMMY9AmrpV2dJBDnN8IaziRN1hx ieQ66RZ7M7djYZeR0OnHfM/k6+OJXAfZLEhID6diWPMrLOc7rFvmDU5EU7n2fM4= =szkN -----END PGP SIGNATURE----- --pE2VAHO2njSJCslu-- From owner-freebsd-hackers@freebsd.org Sun May 22 22:54:23 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 C0978B3B09A for ; Sun, 22 May 2016 22:54:23 +0000 (UTC) (envelope-from joerg@bec.de) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [IPv6:2001:4b98:c:538::197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BE5B1747 for ; Sun, 22 May 2016 22:54:23 +0000 (UTC) (envelope-from joerg@bec.de) Received: from mfilter11-d.gandi.net (mfilter11-d.gandi.net [217.70.178.131]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id 4DBBA41C080 for ; Mon, 23 May 2016 00:54:21 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter11-d.gandi.net Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter11-d.gandi.net (mfilter11-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id OAHF3Ve2Hszk for ; Mon, 23 May 2016 00:54:19 +0200 (CEST) X-Originating-IP: 108.61.101.156 Received: from britannica.bec.de (unknown [108.61.101.156]) (Authenticated sender: joerg@bec.de) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id E9E7F41C07D for ; Mon, 23 May 2016 00:54:18 +0200 (CEST) Date: Mon, 23 May 2016 00:54:14 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160522225414.GB24398@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 22:54:23 -0000 On Sun, May 22, 2016 at 10:54:30PM +0200, Dirk Engling wrote: > When trying to bsdiff two DVD images, I noticed it failing due to > read(2) returning EINVAL to the tool. man 2 read says, this would only > happen for a negative value for fildes, which clearly was not true. I would classify that as implementation bug. It seems perfectly sensible to turn overly large requests into a short read/write, even for blocking files. But erroring out seems to be quite wrong to me. Joerg From owner-freebsd-hackers@freebsd.org Sun May 22 22:56: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 0ACF2B3B137 for ; Sun, 22 May 2016 22:56:36 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com [209.85.213.171]) (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 D3612187D for ; Sun, 22 May 2016 22:56:35 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-ig0-f171.google.com with SMTP id l10so15964881igk.0 for ; Sun, 22 May 2016 15:56:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc; bh=qmptOknLy2XKuWHp00djqmwbtxTmDLhLQtxG7g8YlVI=; b=PjrL/n9j0XMyUoJoptjU6BSVZPCQBGF6+J1yHKsAHCGCOevdkrGpQeBhjo3nBARLBI Rj2fxAhqyGXZSahY0h4XX5ZQkWf2AkAI3UhrbklYD7WthjP7qVvB5+vVXvk9sebSFe/W aRpLj6AqcTD7Z4vufp/x0q7zc1AyY+JKmzq8x6eq/5sTNopO7XX3+sydoP+f1vfDIwsM ZGNEr1W1e7jvCKvx0dvEQkjlRAsrdUijlUcYV8N65TczB/4rQuWPuifNvHVF99rxTAdB phLL1CtavfF1bry1OtlUHa3ejgki21ud9yQzZDB6xYd1H4qXXH+fXg5hU7tiqA6vHA5O 295Q== X-Gm-Message-State: ALyK8tIYz8njkAW5GvH/Xfb/U7k/mHh0X6LMl5s1XAXJWOVuXw5czTRIvnai0sGcC/qQNw== X-Received: by 10.50.7.100 with SMTP id i4mr2838033iga.69.1463957794726; Sun, 22 May 2016 15:56:34 -0700 (PDT) Received: from mail-ig0-f172.google.com (mail-ig0-f172.google.com. [209.85.213.172]) by smtp.gmail.com with ESMTPSA id yb2sm2917107igc.9.2016.05.22.15.56.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 May 2016 15:56:34 -0700 (PDT) Received: by mail-ig0-f172.google.com with SMTP id ww4so24153526igb.1 for ; Sun, 22 May 2016 15:56:34 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.244.180 with SMTP id xh20mr10175035igc.48.1463957793978; Sun, 22 May 2016 15:56:33 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.36.205.70 with HTTP; Sun, 22 May 2016 15:56:33 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 May 2016 15:56:33 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes From: Conrad Meyer To: Dirk Engling Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 22:56:36 -0000 On Sun, May 22, 2016 at 1:54 PM, Dirk Engling wrote: > When trying to bsdiff two DVD images, I noticed it failing due to > read(2) returning EINVAL to the tool. man 2 read says, this would only > happen for a negative value for fildes, which clearly was not true. Actually, it's documented at the very bottom of the first section: ERRORS The read(), readv(), pread() and preadv() system calls will succeed unless: ... [EINVAL] The value nbytes is greater than INT_MAX. It does seem silly to me given nbytes is a size_t. I think it should error if nbytes is greater than SSIZE_T_MAX, but on platforms where size_t is larger than int (e.g. amd64) it shouldn't error for nbytes in [INT_MAX, SSIZE_T_MAX - 1]. As far as I can tell, this INT_MAX behavior is not required by POSIX. > After more digging I found that read internally wraps a single call to > readv, preparing a temporary struct iovec. man 2 readv in turn says that > it will fail with EINVAL, if > > The sum of the iov_len values in the iov array overflowed a 32-bit integer. > > I saw the same behaviour on a linux system, so I kind of assume there is > a standard that allows read(2) doing that. Still I think that > > 1) the man page must be corrected to match this behaviour, or > 2) the read(2) syscall must wrap multiple calls to readv > > However, the http://www.daemonology.net/bsdiff/ page claims that: > > Providing that off_t is defined properly, bsdiff and bspatch support > files of up to 2^61-1 = 2Ei-1 bytes. > > which I could not confirm on any system. I could easily fix this by > using mmap instead of read to get pointers to file contents. > > Now, where should I start? I think read(2) could be fixed to not exhibit this behavior. Or you could change the application to loop INT_MAX or smaller reads. Best, Conrad From owner-freebsd-hackers@freebsd.org Sun May 22 23:02:07 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 4FDD7B3B3A1 for ; Sun, 22 May 2016 23:02:07 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4381D1BAA for ; Sun, 22 May 2016 23:02:07 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1463958122647529.1151203261937; Sun, 22 May 2016 16:02:02 -0700 (PDT) Date: Sun, 22 May 2016 16:02:02 -0700 From: Matthew Macy To: "Joerg Sonnenberger" Cc: "" Message-ID: <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> In-Reply-To: <20160522225414.GB24398@britannica.bec.de> References: <20160522225414.GB24398@britannica.bec.de> Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 23:02:07 -0000 ---- On Sun, 22 May 2016 15:54:14 -0700 Joerg Sonnenberger wrote ---- > On Sun, May 22, 2016 at 10:54:30PM +0200, Dirk Engling wrote: > > When trying to bsdiff two DVD images, I noticed it failing due to > > read(2) returning EINVAL to the tool. man 2 read says, this would only > > happen for a negative value for fildes, which clearly was not true. > > I would classify that as implementation bug. It seems perfectly sensible > to turn overly large requests into a short read/write, even for blocking > files. But erroring out seems to be quite wrong to me. > read(2) takes a size_t so this is clearly an internal bug where it's an int and treating it as a negative value. -M From owner-freebsd-hackers@freebsd.org Sun May 22 23:09: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 40291B3B5F4 for ; Sun, 22 May 2016 23:09:49 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 B44DB102A; Sun, 22 May 2016 23:09:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u4MN9gZN097397 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 23 May 2016 02:09:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u4MN9gZN097397 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u4MN9gZj097396; Mon, 23 May 2016 02:09:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 23 May 2016 02:09:42 +0300 From: Konstantin Belousov To: Conrad Meyer Cc: Dirk Engling , FreeBSD Hackers Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160522230942.GP89104@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 23:09:49 -0000 On Sun, May 22, 2016 at 03:56:33PM -0700, Conrad Meyer wrote: > On Sun, May 22, 2016 at 1:54 PM, Dirk Engling wrote: > > When trying to bsdiff two DVD images, I noticed it failing due to > > read(2) returning EINVAL to the tool. man 2 read says, this would only > > happen for a negative value for fildes, which clearly was not true. > > Actually, it's documented at the very bottom of the first section: > > ERRORS > The read(), readv(), pread() and preadv() system calls will succeed > unless: > ... > [EINVAL] The value nbytes is greater than INT_MAX. > > It does seem silly to me given nbytes is a size_t. I think it should > error if nbytes is greater than SSIZE_T_MAX, but on platforms where > size_t is larger than int (e.g. amd64) it shouldn't error for nbytes > in [INT_MAX, SSIZE_T_MAX - 1]. It does not look silly to me, due to the typical if (read() < 0) checks in the code. Even if (read() == -1) is vulnerable. > > As far as I can tell, this INT_MAX behavior is not required by POSIX. >From POSIX page for read(): RETURN VALUE Upon successful completion, these functions shall return a non-negative integer indicating the number of bytes actually read. Otherwise, the functions shall return -1 and set errno to indicate the error. From owner-freebsd-hackers@freebsd.org Sun May 22 23:11:05 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 8A716B3B6EA for ; Sun, 22 May 2016 23:11:05 +0000 (UTC) (envelope-from joerg@bec.de) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 534791319; Sun, 22 May 2016 23:11:05 +0000 (UTC) (envelope-from joerg@bec.de) Received: from mfilter14-d.gandi.net (mfilter14-d.gandi.net [217.70.178.142]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id 3B3D9A80C2; Mon, 23 May 2016 01:10:57 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter14-d.gandi.net Received: from relay3-d.mail.gandi.net ([IPv6:::ffff:217.70.183.195]) by mfilter14-d.gandi.net (mfilter14-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id I5PUNUZLeW94; Mon, 23 May 2016 01:10:55 +0200 (CEST) X-Originating-IP: 108.61.101.156 Received: from britannica.bec.de (unknown [108.61.101.156]) (Authenticated sender: joerg@bec.de) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id A5AFDA80C6; Mon, 23 May 2016 01:10:53 +0200 (CEST) Date: Mon, 23 May 2016 01:10:48 +0200 From: Joerg Sonnenberger To: Conrad Meyer Cc: Dirk Engling , FreeBSD Hackers Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160522231048.GA25503@britannica.bec.de> Mail-Followup-To: Conrad Meyer , Dirk Engling , FreeBSD Hackers References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 23:11:05 -0000 On Sun, May 22, 2016 at 03:56:33PM -0700, Conrad Meyer wrote: > On Sun, May 22, 2016 at 1:54 PM, Dirk Engling wrote: > > When trying to bsdiff two DVD images, I noticed it failing due to > > read(2) returning EINVAL to the tool. man 2 read says, this would only > > happen for a negative value for fildes, which clearly was not true. > > Actually, it's documented at the very bottom of the first section: > > ERRORS > The read(), readv(), pread() and preadv() system calls will succeed > unless: > ... > [EINVAL] The value nbytes is greater than INT_MAX. > > It does seem silly to me given nbytes is a size_t. I think it should > error if nbytes is greater than SSIZE_T_MAX, but on platforms where > size_t is larger than int (e.g. amd64) it shouldn't error for nbytes > in [INT_MAX, SSIZE_T_MAX - 1]. There are a lot of valid reasons for not doing arbitrarily large operations, especially since a certain amount of atomicity is expected for local IO. That doesn't mean that it can't be turned into a short read/write instead. Erroring out seeems completely unjustified. Joerg From owner-freebsd-hackers@freebsd.org Sun May 22 23:12:12 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 4AE3DB3B8FA for ; Sun, 22 May 2016 23:12:12 +0000 (UTC) (envelope-from joerg@bec.de) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [IPv6:2001:4b98:c:538::197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 12F8D16C7 for ; Sun, 22 May 2016 23:12:12 +0000 (UTC) (envelope-from joerg@bec.de) Received: from mfilter33-d.gandi.net (mfilter33-d.gandi.net [217.70.178.164]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id C320141C088 for ; Mon, 23 May 2016 01:12:10 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter33-d.gandi.net Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter33-d.gandi.net (mfilter33-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id gvN-kEVR4Yt8 for ; Mon, 23 May 2016 01:12:09 +0200 (CEST) X-Originating-IP: 108.61.101.156 Received: from britannica.bec.de (unknown [108.61.101.156]) (Authenticated sender: joerg@bec.de) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 6074E41C086 for ; Mon, 23 May 2016 01:12:07 +0200 (CEST) Date: Mon, 23 May 2016 01:12:03 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160522231203.GB25503@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20160522225414.GB24398@britannica.bec.de> <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 23:12:12 -0000 On Sun, May 22, 2016 at 04:02:02PM -0700, Matthew Macy wrote: > > > > ---- On Sun, 22 May 2016 15:54:14 -0700 Joerg Sonnenberger wrote ---- > > On Sun, May 22, 2016 at 10:54:30PM +0200, Dirk Engling wrote: > > > When trying to bsdiff two DVD images, I noticed it failing due to > > > read(2) returning EINVAL to the tool. man 2 read says, this would only > > > happen for a negative value for fildes, which clearly was not true. > > > > I would classify that as implementation bug. It seems perfectly sensible > > to turn overly large requests into a short read/write, even for blocking > > files. But erroring out seems to be quite wrong to me. > > > > read(2) takes a size_t so this is clearly an internal bug where it's an int and treating it as a negative value. Not exactly. The reason for cutting it off are many fold. Using int in the kernel is one argument. The requirement for locking the IO range for concurrent read/write operations from other threads is a bigger argument. Joerg From owner-freebsd-hackers@freebsd.org Sun May 22 23:26:42 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 2A0A1B3BD3C for ; Sun, 22 May 2016 23:26:42 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) (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 EE1741D9D for ; Sun, 22 May 2016 23:26:41 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi0-f50.google.com with SMTP id x19so253830978oix.2 for ; Sun, 22 May 2016 16:26:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to; bh=lJ67+3atXlDnTA2X5r01wCCzF0pOqOPK3DznIAnvt0M=; b=PNBCBfZlsiwhJEjZcf+M+0KJzDxekSDl8Rnb00iqfJINpkX+GH/VbWAQiOHSx+c8IO Bx6IQp2hBlAsV71dUGOKuigvZJONUxswJp9FLFvdBcLp8x/Z6kLzsxBmcGGCgZ6eQiav 6CVEPS8BTRmEvCF5kp2DN2Rar5uODE6YgqC2AUa7NH/0EPJ6y3ADhkHxAkaIvBtdxEeF SQkYOSI+AN4elXg34ufLOtDN7yrCJpNaEAsOxF0L5lqVIpwn0gqNCdO3UyEVCE9q19E1 vJKA0JrTr8xw6s6ubRsZIth8DC5EN5J9d7q4EVqqb27Kwu75ML/Wmz+R5kl08JZ96pke dF2Q== X-Gm-Message-State: ALyK8tKY7GyMwpN4KV831+mgQpesr0Cnj9iXjUfu+jCqbWGJQAEIjWyTapu4rf9HLCPbzw== X-Received: by 10.157.47.102 with SMTP id h93mr2379532otb.25.1463959594942; Sun, 22 May 2016 16:26:34 -0700 (PDT) Received: from mail-io0-f179.google.com (mail-io0-f179.google.com. [209.85.223.179]) by smtp.gmail.com with ESMTPSA id g93sm4363838otg.7.2016.05.22.16.26.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 May 2016 16:26:34 -0700 (PDT) Received: by mail-io0-f179.google.com with SMTP id t40so90102564ioi.0 for ; Sun, 22 May 2016 16:26:34 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.38.79 with SMTP id m76mr12132764iom.7.1463959594345; Sun, 22 May 2016 16:26:34 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.36.205.70 with HTTP; Sun, 22 May 2016 16:26:34 -0700 (PDT) In-Reply-To: <20160522231048.GA25503@britannica.bec.de> References: <20160522231048.GA25503@britannica.bec.de> Date: Sun, 22 May 2016 16:26:34 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes From: Conrad Meyer To: Dirk Engling , FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 23:26:42 -0000 On Sun, May 22, 2016 at 4:10 PM, Joerg Sonnenberger wrote: > On Sun, May 22, 2016 at 03:56:33PM -0700, Conrad Meyer wrote: >> ERRORS >> The read(), readv(), pread() and preadv() system calls will succeed >> unless: >> ... >> [EINVAL] The value nbytes is greater than INT_MAX. >> >> It does seem silly to me given nbytes is a size_t. I think it should >> error if nbytes is greater than SSIZE_T_MAX, but on platforms where >> size_t is larger than int (e.g. amd64) it shouldn't error for nbytes >> in [INT_MAX, SSIZE_T_MAX - 1]. > > There are a lot of valid reasons for not doing arbitrarily large > operations, especially since a certain amount of atomicity is expected > for local IO. That doesn't mean that it can't be turned into a short > read/write instead. Erroring out seeems completely unjustified. Sure; those reasons also apply to INT_MAX-sized IOs (2 GB). Conrad From owner-freebsd-hackers@freebsd.org Sun May 22 23:30: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 1671BB3BF2A for ; Sun, 22 May 2016 23:30:46 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) (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 DACEF1155; Sun, 22 May 2016 23:30:45 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi0-f52.google.com with SMTP id b65so109643112oia.1; Sun, 22 May 2016 16:30:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc; bh=kPAoLZczWozA9V4FS0juplv9hj2g/1NogpZUa30OasY=; b=B+yIYPHtMZO1pRWeG26TJ2QcNvpl4p0q19XdaUmsoeJm/9mQKanm+4KHrWzlEw6Mzt awSjXe5HS7uLaBVOvU9v/5GPhbS3tx/3beOWO8Wt0CZBXPkM4qxrAMBaaKqCOovdZXFI GUTgKFZwWJUo8ZOUoYorGvI6xdykDWbn8ggS71w8oOvb2wYo6+4OffladA5HHGG51Otz 7hZGgqjUv81Lydf77JAkrRHfEYqtkSJhNoHwfELEGjldImaGtrImfF+ponOmerNn5yxO P31J0OV04bSeSmIpLtgZAAJhDhwnfPgBgzzqOaTHg+FVWv5nbQL8RjoDhYGpRbV9vrVI 8ZtQ== X-Gm-Message-State: AOPr4FX5CdaHzJSIwjUleJqWAEdR00iXE7FaN2X34NJpiU2ng7Cj4/iPWrIixqKTVp/1bA== X-Received: by 10.157.57.138 with SMTP id y10mr7847457otb.64.1463959413684; Sun, 22 May 2016 16:23:33 -0700 (PDT) Received: from mail-io0-f181.google.com (mail-io0-f181.google.com. [209.85.223.181]) by smtp.gmail.com with ESMTPSA id 90sm9039692otx.14.2016.05.22.16.23.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 May 2016 16:23:33 -0700 (PDT) Received: by mail-io0-f181.google.com with SMTP id p64so90806462ioi.2; Sun, 22 May 2016 16:23:33 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.36.81.209 with SMTP id s200mr10867214ita.34.1463959412852; Sun, 22 May 2016 16:23:32 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.36.205.70 with HTTP; Sun, 22 May 2016 16:23:32 -0700 (PDT) In-Reply-To: <20160522230942.GP89104@kib.kiev.ua> References: <20160522230942.GP89104@kib.kiev.ua> Date: Sun, 22 May 2016 16:23:32 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes From: Conrad Meyer To: Konstantin Belousov Cc: Conrad Meyer , Dirk Engling , FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 23:30:46 -0000 On Sun, May 22, 2016 at 4:09 PM, Konstantin Belousov wrote: > On Sun, May 22, 2016 at 03:56:33PM -0700, Conrad Meyer wrote: >> On Sun, May 22, 2016 at 1:54 PM, Dirk Engling wrote: >> > When trying to bsdiff two DVD images, I noticed it failing due to >> > read(2) returning EINVAL to the tool. man 2 read says, this would only >> > happen for a negative value for fildes, which clearly was not true. >> >> Actually, it's documented at the very bottom of the first section: >> >> ERRORS >> The read(), readv(), pread() and preadv() system calls will succeed >> unless: >> ... >> [EINVAL] The value nbytes is greater than INT_MAX. >> >> It does seem silly to me given nbytes is a size_t. I think it should >> error if nbytes is greater than SSIZE_T_MAX, but on platforms where >> size_t is larger than int (e.g. amd64) it shouldn't error for nbytes >> in [INT_MAX, SSIZE_T_MAX - 1]. > It does not look silly to me, due to the typical > if (read() < 0) > checks in the code. Even > if (read() == -1) > is vulnerable. read(2) returns ssize_t; SSIZE_MAX is not a negative result. I agree that nbytes in [SSIZE_MAX+1, SIZE_MAX] should be disallowed (negative ssize_t value after cast from size_t). > >> >> As far as I can tell, this INT_MAX behavior is not required by POSIX. > From POSIX page for read(): > RETURN VALUE > Upon successful completion, these functions shall return a non-negative integer indicating the > number of bytes actually read. Otherwise, the functions shall return -1 and set errno to indicate > the error. There is a difference between int and ssize_t. They have different ranges on e.g. amd64. Best, Conrad From owner-freebsd-hackers@freebsd.org Sun May 22 23:38:23 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 14D9BB46178 for ; Sun, 22 May 2016 23:38:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 B2AC81688; Sun, 22 May 2016 23:38:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u4MNcGfe004756 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 23 May 2016 02:38:17 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u4MNcGfe004756 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u4MNcG2F004755; Mon, 23 May 2016 02:38:16 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 23 May 2016 02:38:16 +0300 From: Konstantin Belousov To: Conrad Meyer Cc: Dirk Engling , FreeBSD Hackers Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160522233816.GR89104@kib.kiev.ua> References: <20160522230942.GP89104@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 23:38:23 -0000 On Sun, May 22, 2016 at 04:23:32PM -0700, Conrad Meyer wrote: > On Sun, May 22, 2016 at 4:09 PM, Konstantin Belousov > wrote: > > On Sun, May 22, 2016 at 03:56:33PM -0700, Conrad Meyer wrote: > >> On Sun, May 22, 2016 at 1:54 PM, Dirk Engling wrote: > >> > When trying to bsdiff two DVD images, I noticed it failing due to > >> > read(2) returning EINVAL to the tool. man 2 read says, this would only > >> > happen for a negative value for fildes, which clearly was not true. > >> > >> Actually, it's documented at the very bottom of the first section: > >> > >> ERRORS > >> The read(), readv(), pread() and preadv() system calls will succeed > >> unless: > >> ... > >> [EINVAL] The value nbytes is greater than INT_MAX. > >> > >> It does seem silly to me given nbytes is a size_t. I think it should > >> error if nbytes is greater than SSIZE_T_MAX, but on platforms where > >> size_t is larger than int (e.g. amd64) it shouldn't error for nbytes > >> in [INT_MAX, SSIZE_T_MAX - 1]. > > It does not look silly to me, due to the typical > > if (read() < 0) > > checks in the code. Even > > if (read() == -1) > > is vulnerable. > > read(2) returns ssize_t; SSIZE_MAX is not a negative result. I agree > that nbytes in [SSIZE_MAX+1, SIZE_MAX] should be disallowed (negative > ssize_t value after cast from size_t). > > > > >> > >> As far as I can tell, this INT_MAX behavior is not required by POSIX. > > From POSIX page for read(): > > RETURN VALUE > > Upon successful completion, these functions shall return a non-negative integer indicating the > > number of bytes actually read. Otherwise, the functions shall return -1 and set errno to indicate > > the error. > > There is a difference between int and ssize_t. They have different > ranges on e.g. amd64. Well, on amd64 there is sysctl debug.iosize_max_clamp, allowing large but still non-negative ios (allowed in current). Except for devices io, which are controlled by debug.devfs_iosize_max_clamp, disabled by default since I was not able to audit that many drivers. From owner-freebsd-hackers@freebsd.org Sun May 22 23:41:45 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 3DEBCB4627A for ; Sun, 22 May 2016 23:41:45 +0000 (UTC) (envelope-from joerg@bec.de) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [IPv6:2001:4b98:c:538::194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07C371A49 for ; Sun, 22 May 2016 23:41:45 +0000 (UTC) (envelope-from joerg@bec.de) Received: from mfilter14-d.gandi.net (mfilter14-d.gandi.net [217.70.178.142]) by relay2-d.mail.gandi.net (Postfix) with ESMTP id 5DCBFC5A54 for ; Mon, 23 May 2016 01:41:43 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter14-d.gandi.net Received: from relay2-d.mail.gandi.net ([IPv6:::ffff:217.70.183.194]) by mfilter14-d.gandi.net (mfilter14-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id LHa4koj7CJo4 for ; Mon, 23 May 2016 01:41:41 +0200 (CEST) X-Originating-IP: 108.61.101.156 Received: from britannica.bec.de (unknown [108.61.101.156]) (Authenticated sender: joerg@bec.de) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id D4041C5A4F for ; Mon, 23 May 2016 01:41:40 +0200 (CEST) Date: Mon, 23 May 2016 01:41:35 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160522234135.GA27218@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20160522230942.GP89104@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160522230942.GP89104@kib.kiev.ua> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 23:41:45 -0000 On Mon, May 23, 2016 at 02:09:42AM +0300, Konstantin Belousov wrote: > On Sun, May 22, 2016 at 03:56:33PM -0700, Conrad Meyer wrote: > > On Sun, May 22, 2016 at 1:54 PM, Dirk Engling wrote: > > > When trying to bsdiff two DVD images, I noticed it failing due to > > > read(2) returning EINVAL to the tool. man 2 read says, this would only > > > happen for a negative value for fildes, which clearly was not true. > > > > Actually, it's documented at the very bottom of the first section: > > > > ERRORS > > The read(), readv(), pread() and preadv() system calls will succeed > > unless: > > ... > > [EINVAL] The value nbytes is greater than INT_MAX. > > > > It does seem silly to me given nbytes is a size_t. I think it should > > error if nbytes is greater than SSIZE_T_MAX, but on platforms where > > size_t is larger than int (e.g. amd64) it shouldn't error for nbytes > > in [INT_MAX, SSIZE_T_MAX - 1]. > It does not look silly to me, due to the typical > if (read() < 0) > checks in the code. Even > if (read() == -1) > is vulnerable. But that code can already fail in a number of situations. Short reads as well as short writes can happen in any of a number of situations. Joerg From owner-freebsd-hackers@freebsd.org Mon May 23 01:23: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 C482DB45C9D for ; Mon, 23 May 2016 01:23:00 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B704613D1 for ; Mon, 23 May 2016 01:23:00 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1463966579061252.86046957710755; Sun, 22 May 2016 18:22:59 -0700 (PDT) Date: Sun, 22 May 2016 18:22:58 -0700 From: Matthew Macy To: "Joerg Sonnenberger" Cc: "" Message-ID: <154db353935.dd5e87c1133922.4370692881788049491@nextbsd.org> In-Reply-To: <20160522231203.GB25503@britannica.bec.de> References: <20160522225414.GB24398@britannica.bec.de> <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> <20160522231203.GB25503@britannica.bec.de> Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 01:23:00 -0000 ---- On Sun, 22 May 2016 16:12:03 -0700 Joerg Sonnenberger wrote ---- > On Sun, May 22, 2016 at 04:02:02PM -0700, Matthew Macy wrote: > > > > > > > > ---- On Sun, 22 May 2016 15:54:14 -0700 Joerg Sonnenberger wrote ---- > > > On Sun, May 22, 2016 at 10:54:30PM +0200, Dirk Engling wrote: > > > > When trying to bsdiff two DVD images, I noticed it failing due to > > > > read(2) returning EINVAL to the tool. man 2 read says, this would only > > > > happen for a negative value for fildes, which clearly was not true. > > > > > > I would classify that as implementation bug. It seems perfectly sensible > > > to turn overly large requests into a short read/write, even for blocking > > > files. But erroring out seems to be quite wrong to me. > > > > > > > read(2) takes a size_t so this is clearly an internal bug where it's an int and treating it as a negative value. > > Not exactly. The reason for cutting it off are many fold. Using int in > the kernel is one argument. The requirement for locking the IO range for > concurrent read/write operations from other threads is a bigger > argument. > That still doesn't justify EINVAL as a return. Does read(2) need to make atomicity guarantees? -M From owner-freebsd-hackers@freebsd.org Mon May 23 09:07: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 4CEB8B46E08 for ; Mon, 23 May 2016 09:07:40 +0000 (UTC) (envelope-from sangeeta.manikonda@calsoftinc.com) Received: from mailrelay.nyi.net (mailrelay.nyi.net [64.90.175.133]) (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 2AFA41F67 for ; Mon, 23 May 2016 09:07:39 +0000 (UTC) (envelope-from sangeeta.manikonda@calsoftinc.com) Received: from [114.143.187.14] (helo=csom.calsofthq.com) by mailrelay.nyi.net with smtp (Exim 4.63) (envelope-from ) id 1b4lpT-0004sn-Mj for freebsd-hackers@freebsd.org; Mon, 23 May 2016 05:07:15 -0400 Received: from localhost (localhost [127.0.0.1]) by csom.calsofthq.com (Postfix) with ESMTP id CA8673A7F2 for ; Mon, 23 May 2016 14:37:41 +0530 (IST) X-Virus-Scanned: Debian amavisd-new at csom2.calsoft.org Received: from csom.calsofthq.com ([127.0.0.1]) by localhost (csom.calsofthq.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id ylHgXNwN1-7d for ; Mon, 23 May 2016 14:37:37 +0530 (IST) Received: from sangeeta.calsofthq.com (unknown [172.17.154.53]) by csom.calsofthq.com (Postfix) with ESMTPSA id 908C341C62 for ; Mon, 23 May 2016 14:37:16 +0530 (IST) Message-ID: <5742C836.3050303@calsoftinc.com> Date: Mon, 23 May 2016 14:37:02 +0530 From: sangeeta Manikonda User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: FreeBSD CIFS share authentication using FreeIPA Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 09:07:40 -0000 Hi, I'm resending this mail, sorry that I posted without subscribing to the mailing list. I'm trying to configure FreeBSD to authenticate CIFS using LDAP + Kerberos exposed by FreeIPA. To achieve it, I started with configuration of FreeIPA client on FreeBSD 9.3, added it as a host on the freeIPA server on CentOS6. Second step was creating a CIFS share on FreeBSD and related configuration on FreeBSD. I'm stuck at this point and need some help to achieve it. Thanks. Sangeeta From owner-freebsd-hackers@freebsd.org Mon May 23 12:21: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 2B755B459B7 for ; Mon, 23 May 2016 12:21:36 +0000 (UTC) (envelope-from joerg@bec.de) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [IPv6:2001:4b98:c:538::196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EBEA817D6 for ; Mon, 23 May 2016 12:21:35 +0000 (UTC) (envelope-from joerg@bec.de) Received: from britannica.bec.de (p20030057E21176048C47C6DE7E800516.dip0.t-ipconnect.de [IPv6:2003:57:e211:7604:8c47:c6de:7e80:516]) (Authenticated sender: joerg@bec.de) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 6A8051720BD; Mon, 23 May 2016 14:21:33 +0200 (CEST) Date: Mon, 23 May 2016 14:21:31 +0200 From: Joerg Sonnenberger To: Matthew Macy Cc: Joerg Sonnenberger , "" Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160523122131.GC8747@britannica.bec.de> Mail-Followup-To: Matthew Macy , Joerg Sonnenberger , "" References: <20160522225414.GB24398@britannica.bec.de> <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> <20160522231203.GB25503@britannica.bec.de> <154db353935.dd5e87c1133922.4370692881788049491@nextbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <154db353935.dd5e87c1133922.4370692881788049491@nextbsd.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 12:21:36 -0000 On Sun, May 22, 2016 at 06:22:58PM -0700, Matthew Macy wrote: > > > > ---- On Sun, 22 May 2016 16:12:03 -0700 Joerg Sonnenberger wrote ---- > > On Sun, May 22, 2016 at 04:02:02PM -0700, Matthew Macy wrote: > > > > > > > > > > > > ---- On Sun, 22 May 2016 15:54:14 -0700 Joerg Sonnenberger wrote ---- > > > > On Sun, May 22, 2016 at 10:54:30PM +0200, Dirk Engling wrote: > > > > > When trying to bsdiff two DVD images, I noticed it failing due to > > > > > read(2) returning EINVAL to the tool. man 2 read says, this would only > > > > > happen for a negative value for fildes, which clearly was not true. > > > > > > > > I would classify that as implementation bug. It seems perfectly sensible > > > > to turn overly large requests into a short read/write, even for blocking > > > > files. But erroring out seems to be quite wrong to me. > > > > > > > > > > read(2) takes a size_t so this is clearly an internal bug where it's an int and treating it as a negative value. > > > > Not exactly. The reason for cutting it off are many fold. Using int in > > the kernel is one argument. The requirement for locking the IO range for > > concurrent read/write operations from other threads is a bigger > > argument. > > > That still doesn't justify EINVAL as a return. Does read(2) need to > make atomicity guarantees? See my first sentence. I consider returning EINVAL for too large buffer size a bug. Yes, read/write operations should be atomic with regard to other processes on the system. Atomic meaning in this context that the read can be observed either completely or not at all. This still doesn't mean that read must execute the full size. Other cases for short read/writes are socket, pipes etc. Joerg From owner-freebsd-hackers@freebsd.org Mon May 23 12:31:19 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 87FE2B45C62 for ; Mon, 23 May 2016 12:31:19 +0000 (UTC) (envelope-from cedric.blancher@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 5ADA81D23 for ; Mon, 23 May 2016 12:31:19 +0000 (UTC) (envelope-from cedric.blancher@gmail.com) Received: by mail-pf0-x22a.google.com with SMTP id g64so11782070pfb.2 for ; Mon, 23 May 2016 05:31:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=ii3svPBaK7xV1A8Ud3Sf497OZlk9s0HcuaegPgYwzFA=; b=niMfDNH8sRRYm8+j68RxEItK33MOtlQONHB8WZ9tnLeamEnErchf75TCz2zQ7eYpVk r/V99yBpf0PvnVZl3BE61wUUGTkHpBwO5Qio0PPVwqDUadJ8fjp58HAa9vHSimdUWsaJ 8ruS6WbTCgjS0l5baZfC8/mGYvwGFMFepmHfMrlePnq3YOp539dpnOTEVfSMNFI5H549 AjavVTIXk9DpHeP9zi4CCTRabKxYbECtCK+cA464apqqzXYW+sHA4zHQEnDW/iKM6jgv JZtBA+/PVbN3bS49Gc2h9LPIcThxUk1jSCGUOPHjRyeySguvHmegJyzrI19l4BVLOWxH L4KA== 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; bh=ii3svPBaK7xV1A8Ud3Sf497OZlk9s0HcuaegPgYwzFA=; b=CRsnP1J6/xV9xBE8bGXv6tvExDeNidJAH32AsEPt7udZxDCFUTcojgDDkwQa42q85+ 1DDN+nWttQVva8WHrnJ47fbUa0LRVMTB50S28V4kSPn4nIZTNJUhE7u4i0NZyhT21QzM 03ZwVKlMCDG7X/zJ1wbJx9SxdVnT52kwd3WTQY3rqLSYKu88xR+5+jDFuyzpo33E/qp9 PbKBxjgSuWkxCDzFxsp3uPaNTxfu4ReBGDj7P0RfCVoB+m4RE35eIjymgnyCit7xyBzg HUdoAhfHawzRuLa6c7Ixh5YEayh7XlS+gEhuOS9m1tseg6hMP/J8kB2RmkwzOCKgFZR6 iS+g== X-Gm-Message-State: AOPr4FXLZH3WITJqbAKiOGQ7z2SV0Nbafu+NU8Lgz6r3ZKdSGYnTaSGKLhEv5w1iYwqhnjKOOjDFz5xExe82ww== MIME-Version: 1.0 X-Received: by 10.98.101.198 with SMTP id z189mr27369918pfb.76.1464006678777; Mon, 23 May 2016 05:31:18 -0700 (PDT) Received: by 10.66.183.232 with HTTP; Mon, 23 May 2016 05:31:18 -0700 (PDT) In-Reply-To: <20160523122131.GC8747@britannica.bec.de> References: <20160522225414.GB24398@britannica.bec.de> <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> <20160522231203.GB25503@britannica.bec.de> <154db353935.dd5e87c1133922.4370692881788049491@nextbsd.org> <20160523122131.GC8747@britannica.bec.de> Date: Mon, 23 May 2016 14:31:18 +0200 Message-ID: Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes From: Cedric Blancher To: Matthew Macy , Joerg Sonnenberger , "" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 12:31:19 -0000 Nothing in POSIX mandates that read()/write() are atomic. Old UNIX, SystemV, AIX, Solaris and HP-UX don't do that nor do they guarantee that. Ced On 23 May 2016 at 14:21, Joerg Sonnenberger wrote: > On Sun, May 22, 2016 at 06:22:58PM -0700, Matthew Macy wrote: >> >> >> >> ---- On Sun, 22 May 2016 16:12:03 -0700 Joerg Sonnenberger wrote ---- >> > On Sun, May 22, 2016 at 04:02:02PM -0700, Matthew Macy wrote: >> > > >> > > >> > > >> > > ---- On Sun, 22 May 2016 15:54:14 -0700 Joerg Sonnenberger wrote ---- >> > > > On Sun, May 22, 2016 at 10:54:30PM +0200, Dirk Engling wrote: >> > > > > When trying to bsdiff two DVD images, I noticed it failing due to >> > > > > read(2) returning EINVAL to the tool. man 2 read says, this would only >> > > > > happen for a negative value for fildes, which clearly was not true. >> > > > >> > > > I would classify that as implementation bug. It seems perfectly sensible >> > > > to turn overly large requests into a short read/write, even for blocking >> > > > files. But erroring out seems to be quite wrong to me. >> > > > >> > > >> > > read(2) takes a size_t so this is clearly an internal bug where it's an int and treating it as a negative value. >> > >> > Not exactly. The reason for cutting it off are many fold. Using int in >> > the kernel is one argument. The requirement for locking the IO range for >> > concurrent read/write operations from other threads is a bigger >> > argument. >> > >> That still doesn't justify EINVAL as a return. Does read(2) need to >> make atomicity guarantees? > > See my first sentence. I consider returning EINVAL for too large buffer > size a bug. Yes, read/write operations should be atomic with regard to > other processes on the system. Atomic meaning in this context that the > read can be observed either completely or not at all. This still doesn't > mean that read must execute the full size. Other cases for short > read/writes are socket, pipes etc. > > Joerg > _______________________________________________ > 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" -- Cedric Blancher Institute Pasteur From owner-freebsd-hackers@freebsd.org Mon May 23 12:37: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 63384B45E76 for ; Mon, 23 May 2016 12:37:03 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A2AF311BE for ; Mon, 23 May 2016 12:37:02 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: (qmail 36749 invoked from network); 23 May 2016 12:36:59 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 23 May 2016 12:36:59 -0000 Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes To: "" References: <20160522225414.GB24398@britannica.bec.de> <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> <20160522231203.GB25503@britannica.bec.de> <154db353935.dd5e87c1133922.4370692881788049491@nextbsd.org> <20160523122131.GC8747@britannica.bec.de> From: Dirk Engling Message-ID: <5a607409-1b98-8944-b1f2-4422b1d28248@erdgeist.org> Date: Mon, 23 May 2016 14:36:58 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <20160523122131.GC8747@britannica.bec.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 12:37:03 -0000 On 23.05.16 14:21, Joerg Sonnenberger wrote: > Atomic meaning in this context that the read can be observed either > completely or not at all. This still doesn't mean that read must > execute the full size. Other cases for short read/writes are socket, > pipes etc. On linux I found read() returning a short read, however I wonder if any user land application developer ever expects a read from local file to yield a short read and continue reading. Maybe I should scan base system sources for all occurrences of read. Best case scenario as found in bsdiff is if (read(fd,old,oldsize)!=oldsize) and I wonder if an API user SHOULD be expecting the short read behaviour at all, just because the nbytes crosses a certain arbitrary threshold. erdgeist From owner-freebsd-hackers@freebsd.org Mon May 23 13:38: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 4C612B462DE for ; Mon, 23 May 2016 13:38:46 +0000 (UTC) (envelope-from joerg@bec.de) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [IPv6:2001:4b98:c:538::196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 17CD31D60 for ; Mon, 23 May 2016 13:38:46 +0000 (UTC) (envelope-from joerg@bec.de) Received: from britannica.bec.de (p20030057E21176048C47C6DE7E800516.dip0.t-ipconnect.de [IPv6:2003:57:e211:7604:8c47:c6de:7e80:516]) (Authenticated sender: joerg@bec.de) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 887911720F8 for ; Mon, 23 May 2016 15:38:44 +0200 (CEST) Date: Mon, 23 May 2016 15:38:42 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160523133842.GA17056@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20160522225414.GB24398@britannica.bec.de> <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> <20160522231203.GB25503@britannica.bec.de> <154db353935.dd5e87c1133922.4370692881788049491@nextbsd.org> <20160523122131.GC8747@britannica.bec.de> <5a607409-1b98-8944-b1f2-4422b1d28248@erdgeist.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5a607409-1b98-8944-b1f2-4422b1d28248@erdgeist.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 13:38:46 -0000 On Mon, May 23, 2016 at 02:36:58PM +0200, Dirk Engling wrote: > On 23.05.16 14:21, Joerg Sonnenberger wrote: > > > Atomic meaning in this context that the read can be observed either > > completely or not at all. This still doesn't mean that read must > > execute the full size. Other cases for short read/writes are socket, > > pipes etc. > > On linux I found read() returning a short read, however I wonder if any > user land application developer ever expects a read from local file to > yield a short read and continue reading. Maybe I should scan base system > sources for all occurrences of read. They have to. Consider a signal interrupting the read. Joerg From owner-freebsd-hackers@freebsd.org Mon May 23 13:41: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 1E3CAB46479 for ; Mon, 23 May 2016 13:41:10 +0000 (UTC) (envelope-from joerg@bec.de) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [IPv6:2001:4b98:c:538::196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DF57F1F0F for ; Mon, 23 May 2016 13:41:09 +0000 (UTC) (envelope-from joerg@bec.de) Received: from britannica.bec.de (p20030057E21176048C47C6DE7E800516.dip0.t-ipconnect.de [IPv6:2003:57:e211:7604:8c47:c6de:7e80:516]) (Authenticated sender: joerg@bec.de) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 82FD11720B8 for ; Mon, 23 May 2016 15:41:08 +0200 (CEST) Date: Mon, 23 May 2016 15:41:06 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160523134106.GB17056@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20160522225414.GB24398@britannica.bec.de> <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> <20160522231203.GB25503@britannica.bec.de> <154db353935.dd5e87c1133922.4370692881788049491@nextbsd.org> <20160523122131.GC8747@britannica.bec.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 13:41:10 -0000 On Mon, May 23, 2016 at 02:31:18PM +0200, Cedric Blancher wrote: > Nothing in POSIX mandates that read()/write() are atomic. Old UNIX, > SystemV, AIX, Solaris and HP-UX don't do that nor do they guarantee > that. "I/O is intended to be atomic to ordinary files and pipes and FIFOs." Joerg From owner-freebsd-hackers@freebsd.org Mon May 23 14:31:25 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 D413FB470C9 for ; Mon, 23 May 2016 14:31:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 6B68A1EC6 for ; Mon, 23 May 2016 14:31:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u4NEVJ3N034058 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 23 May 2016 17:31:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u4NEVJ3N034058 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u4NEVJi7034057 for freebsd-hackers@freebsd.org; Mon, 23 May 2016 17:31:19 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 23 May 2016 17:31:19 +0300 From: Konstantin Belousov To: freebsd-hackers@freebsd.org Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160523143119.GV89104@kib.kiev.ua> References: <20160522225414.GB24398@britannica.bec.de> <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> <20160522231203.GB25503@britannica.bec.de> <154db353935.dd5e87c1133922.4370692881788049491@nextbsd.org> <20160523122131.GC8747@britannica.bec.de> <5a607409-1b98-8944-b1f2-4422b1d28248@erdgeist.org> <20160523133842.GA17056@britannica.bec.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160523133842.GA17056@britannica.bec.de> User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 14:31:25 -0000 On Mon, May 23, 2016 at 03:38:42PM +0200, Joerg Sonnenberger wrote: > On Mon, May 23, 2016 at 02:36:58PM +0200, Dirk Engling wrote: > > On 23.05.16 14:21, Joerg Sonnenberger wrote: > > > > > Atomic meaning in this context that the read can be observed either > > > completely or not at all. This still doesn't mean that read must > > > execute the full size. Other cases for short read/writes are socket, > > > pipes etc. > > > > On linux I found read() returning a short read, however I wonder if any > > user land application developer ever expects a read from local file to > > yield a short read and continue reading. Maybe I should scan base system > > sources for all occurrences of read. > > They have to. Consider a signal interrupting the read. FreeBSD ensures, at least for some filesystems, that reads are atomic WRT writes, by your definition of atomic. Previously, it was (mostly) ensured by keeping exclusive vnode lock around VOP_WRITE, and shared vnode lock around VOP_READ. Then ZFS was changed to only keep shared lock on write, but supposedly there was an internal range locking, preventing reads from starting if write happens for the intersecting range. Then UFS was modified to sometimes split read/write requests into smaller VOP calls and drop vnode locks between them. This was done to prevent recursing info VM/VFS on page faults during uiomove(9) from VOPs. As a compensation, VFS-level rangelocks were introduced for UFS only. And then, quite recently, ZFS was changed to operate in the same chunked mode as UFS and, implicitely, the same VFS rangelocks are currently applied for each read and write requests on both UFS and ZFS. But none of the local filesystems allow signals to interrupt the operations. Pending signal never results in the short read or write neither on UFS nor on ZFS (and msdosfs too). It might be allowed for NFS by a mount option. From owner-freebsd-hackers@freebsd.org Mon May 23 20:33: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 C255BB47430 for ; Mon, 23 May 2016 20:33:33 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::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 78E0B1DD7 for ; Mon, 23 May 2016 20:33:33 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: by mail-vk0-x22c.google.com with SMTP id c189so238632640vkb.1 for ; Mon, 23 May 2016 13:33:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=OvAHZDzBbyZYn8o/bDplZS1N725Br43rHDHbee9J1CE=; b=VjqiT6eAAsjR542BzUOgPo4gEg+Bq+93beGKdgo2Dkz4oPqRT3a842nsG0Hl9nJf/h HjMn5g4ku54X810rK39Qkl+/z4s4/GvSZFSwSt2NGyM0ISidg8YaTiyApWHGw7Zl59JQ fqcjqTamjCvpldaNcmGE9EcbMNJG8LvvjiCD1wKcVKysFU1JBW1BbukLE1y2qB9Rzn5H 9j2+wFl4o1pJrd2nLHkPM/RoZgUofaBT4QFk9lIA8hqzwJ4R1tCWHmvKaoJDDKIGlB9N 3XVPe6kKeFu86+ORqnpsFUdum00XQkPbpBenKSQUgPg0BMZyLXymaDZ6ek0rgeLQFmlt 4h2A== 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; bh=OvAHZDzBbyZYn8o/bDplZS1N725Br43rHDHbee9J1CE=; b=iWFsTk4WgT+44K2B/iwaHhFz9bHnZW2euYZjxxX1arrhr1kaOwhh8QiweBF+s4yd4Z +5OoZQ/AmfWchA7OoqIZjTBt6AiNpAvAosuZWAhl5WtNBL+PWqV4wBjjHlJw8YNowDoW vWszpJIijbtIN3KwVErGsa9289fSHpzes4y4dY8MDrfdtlEajb6hXm7Xay61KVZC5fXo 6NQACehVfaz9KVQLusxV4mcGjZMPQ9DeV/J+25+VNBP1dQkxOelXdaqEsUkFhJBq3V6I UTJ7hw3uZ/OKZRMdlYBbk2PsHytKKKuW9o18SgHvCgtDx/gnasyXbA0PYpsaSNx7LIXW WreQ== X-Gm-Message-State: ALyK8tLWypuZ10+XZ+y9+4sOAx+iRTvM4cAEdc1AMpt65giuSllHPTLDpnPvmkVIJgfk8DTYHVVO7dawJnXMng== MIME-Version: 1.0 X-Received: by 10.31.2.210 with SMTP id 201mr444591vkc.58.1464035612507; Mon, 23 May 2016 13:33:32 -0700 (PDT) Received: by 10.103.21.135 with HTTP; Mon, 23 May 2016 13:33:32 -0700 (PDT) In-Reply-To: References: <1944f9ca-14fa-9839-11bc-b7597337866f@tysdomain.com> Date: Mon, 23 May 2016 16:33:32 -0400 Message-ID: Subject: Re: contributing to open source From: Joe Nosay To: sorressean , FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 20:33:33 -0000 I am on the Chesapeake peninsula in the city of Salisbury, Maryland if you wish to approach me and call me a liar face to face about what I wrote. Any of you who want to make a statement to me about anything I write should come here in person and tell these things to me in person. I will be glad to show you my birth certificate. From there, we can go to Santa Monica , California and speak to my mother. It is much easier for you to be rude to me from afar than to approach me. You call me a liar; yet, you are not willing to visit me to prove that I am a liar. You say that I do not know that of which I write; yet, you are not willing to have a close, physical conversation with me to prove that I am wrong. Every single time that I print the truth, the lot of you make it out to be lies and falsehoods. So, why don't all of you come here and visit me to prove that I am a liar. I have proof and documentation to back up my claims. I am willing to take a mitochondrial DNA test to prove my background and to prove who my mother is. It is easy for you to laugh at me from the comfort and security of your own home or some other place; however, I very much doubt that you would be as willing to do such if you met me face to face. You could pay for me to visit you. If you are right, then there is no reason for you to worry. If you are wrong, then you will have no idea what I may or may not do to you. You are not bullet proof nor are you stab proof. I am excellent with crossbows and bows and arrows. I make my own spears. If I have an axe, it will be sharp enough to remove your head from your body. If you bother me enough times and continue to call me a liar, I will remove your head from your body and use you for a public example. You can be traced to the city in which you live. You can be traced to your home. I can find a way of going there without you knowing it. I know how to make bombs, poisons, and extract hallucinogens from plants. I know how to use a blow gun. I can pick you off from fifty to seventy five yards and not be traced. I can burn you alive with my own napalm formula. I am able to snap your neck and break your bones with my bare hands. Keep on talking your shit, just remember that we will meet sooner than later. And, that I am not one to forget what you say and write. All that I need is a few dollars and the memory of you calling me a liar when I am not for me to say, "Fuck it, I'm going to make sure that you are put in traction for life." And then to act upon it. I have given you and all others a warning - once again- and, I wish for none of you to make me keep my word and promise upon it, get it? This is a conditional statement. If so you choose to break the terms of this agreement, the original writer - being myself - has the legal right to fuck you up beyond recognition. So, Mr. Sorressean, are you and the others willing to meet me; or, are you and the others going to hide behind you computers and talk shit? I am ready for a confrontation. I have bamboo, sticks, pipes, rope. I plan on disemboweling anyone that makes a sudden move, even in the daytime. I will burn you with acid. I will make bombs and put them in your car. I will rid the entire universe of you and those like you who are willing to call the truth a lie. I am not Reiser. Why? Because his wife was innocent and all of you are not. She did not deserve what happened to her; but, all of you do deserve to be eliminated from this plane of existence. Remember, talk your shit to me face to face in person. On Sun, May 22, 2016 at 5:40 PM, Littlefield, Tyler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 5/22/2016 4:42 PM, Joe Nosay wrote: > > Had you replied to the gentleman before I did, the conversation > > would not have been printed. > Not have been printed? Did you print this email? > > Yes, start with one computer; and, if you have a certain idea in > > mind, research what would be best and go from there. > That is not what you said at all. What you said is get ten different > types of computers and a pen and paper. > > My mother is Brazilian and her native language is portuguese. Don't > > play that with me again, understand. I took everything into > > consideration. > Clearly not, if you're complaining about someone's lack of written > skills in English. > > With that aside, please enjoy your stay with us. > I love how you use "us" to refer to the community as if you're nothing > but a troll. > > > > On Sun, May 22, 2016 at 2:50 PM, Littlefield, Tyler > > > wrote: > > > > Pleas disregard everything that was previously mentioned in the > > email below mine. I don't like to top post, but I also don't like > > to quote such garbage. firstly, to the writing better: english is > > not everyone's first language. Also see [1]. Secondly, you do not > > need to get 90 different systems to contribute to development. If > > you have unsupported hardware, you could begin by working on > > drivers for that hardware. Otherwise, check out the FreeBSD wiki > > page at [2] for a todo. [1]: > > https://en.wikipedia.org/wiki/Muphry's_law [2]: > > https://wiki.freebsd.org/IdeasPage On 5/22/2016 1:54 PM, Joe Nosay > > wrote: > >> You need to clarify that which you are asking. In the skill set > >> that you have, what do you create naturally? Now, think about > >> applying that knowledge of C and C++ to an application that you > >> find beneficial to others and yourself. The first thing for you > >> to do is to install the system on a variety of computers. You > >> need some of different architectures. Why? Because every CPU is > >> not designed to do the same job; nor are they going to perform > >> the same way. Grab yourself an UltraSPARC station, a PowerMac G4, > >> a PowerMac G5, a Raspberry pi, and two standard AMD64 laptops - > >> they will be for both 32 bit and 64 bit compiling. You will need > >> to take notes on paper because the system is simple and complex > >> at the same time. The kernel has to match the hardware; and, you > >> will need to learn a few more languages. You have forth, lua, > >> haskell, pascal, python, and java as a start. You will need to > >> learn to map the devices before you think of using them. Believe > >> me, it makes sense. You are going to have to correct a lot of > >> software errors. And, you will have to deal with people on a > >> personal basis. This means you need to write more legibly. > > > >> On Sun, May 22, 2016 at 8:40 AM, Kefeh Collins > >> > wrote: > > > >>> hello i am a second year computer science student, program in > >>> c and c++ and am interested in contributing in operating > >>> system (kernel) directed projects please i need guidance > >>> > >>> thanks in advance > >>> _______________________________________________ > >>> 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 > > " > >>> > >> _______________________________________________ > >> 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 > > " > > > > > > > > > > > > - -- > Take care, > Ty > Twitter: @sorressean > Web: https://tysdomain.com > Pubkey: https://tysdomain.com/files/pubkey.asc > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBAgAGBQJXQidGAAoJEAdP60+BYxej/XIH/206uUFmmLvfcYaA4Dd/luCI > irsKdCWDmBJZeekrA6Lvhsil8sCKqsi/CSnCcK34PIQ1APLbzPgaKJRTpNhUsVhr > 4LDLLg1Z4In1kYtjjksINOIkQ2Dx2KrLxI8Xt1K0uYRUtAYG1Vp1yBKVLhHBAhNT > 0kq6qWxDZSvXfXyqjHhP6NLUB18bdQ59Q3fyI+7HG+Tts0pnLEVZenHny1vMHDwC > 3yCQNSrIYKNzMbvpDOmfwHZt9egmkbiPagPhSuNOq6XbhhmtLPYOgyA+/H8jWtwR > EmcBMNyE9h44G9mVRcVilVwpn7K2CjuhZHWRsrVyJepG4bYx9v5IDv+nmufbTzE= > =HU9f > -----END PGP SIGNATURE----- > From owner-freebsd-hackers@freebsd.org Mon May 23 20:44:22 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 5D49EB477C9 for ; Mon, 23 May 2016 20:44:22 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 291A614AF for ; Mon, 23 May 2016 20:44:21 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u4NKiFVN033481 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 May 2016 14:44:15 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u4NKiFUK033478; Mon, 23 May 2016 14:44:15 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 23 May 2016 14:44:15 -0600 (MDT) From: Warren Block To: Joe Nosay cc: sorressean , FreeBSD Hackers Subject: Re: contributing to open source In-Reply-To: Message-ID: References: <1944f9ca-14fa-9839-11bc-b7597337866f@tysdomain.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 23 May 2016 14:44:15 -0600 (MDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 20:44:22 -0000 On Mon, 23 May 2016, Joe Nosay wrote: A bunch of stuff that should not have been written or sent. This type of behavior is not acceptable on these lists, regardless of your personal circumstances or the real or perceived level of provocation. From owner-freebsd-hackers@freebsd.org Mon May 23 20:46:39 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 65FDAB478B0 for ; Mon, 23 May 2016 20:46:39 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5635E1711 for ; Mon, 23 May 2016 20:46:38 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1464036395276461.26047944224456; Mon, 23 May 2016 13:46:35 -0700 (PDT) Date: Mon, 23 May 2016 13:46:35 -0700 From: Matthew Macy To: "Warren Block" Cc: "Joe Nosay" , "FreeBSD Hackers" , "sorressean" Message-ID: <154df5e88d5.102b02e6a194657.2169771434194203417@nextbsd.org> In-Reply-To: References: <1944f9ca-14fa-9839-11bc-b7597337866f@tysdomain.com> Subject: Re: contributing to open source MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 20:46:39 -0000 We might consider whitelisting established subscribers and then moderating everyone else. intel-gfx for example is moderation only. whitelisting would minimize the burden on the moderator. -M ---- On Mon, 23 May 2016 13:44:15 -0700 Warren Block wrote ---- > On Mon, 23 May 2016, Joe Nosay wrote: > > A bunch of stuff that should not have been written or sent. This type > of behavior is not acceptable on these lists, regardless of your > personal circumstances or the real or perceived level of provocation. > _______________________________________________ > 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 Mon May 23 20:58:38 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 561F1B47C45 for ; Mon, 23 May 2016 20:58:38 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 17BCC1ED3 for ; Mon, 23 May 2016 20:58:38 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi0-x22f.google.com with SMTP id j1so60067086oih.3 for ; Mon, 23 May 2016 13:58:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=Pkmde8GXa97lse64Ohk7moqzRMsV7T6SlMvnA5txgmw=; b=Tc6CyL5MSYRccoW2eyLFnH0C1Xv1Dx/yzCsMKy3Wn9WFn+crskYevT9+jVjrZLbggA kR/N3t4DXE/gC4yHo0NLhMT8xFq/U9Ks8BL8rCh/NhjDGczwMomN80DiaVvc9OxBlslS Kk2kQeproMKyowbk8xEvDmMPK2y425Ra7/CxQn7PugjzvvhfrKP8nF3XaJ3x2tnjYP76 0zNgVthd1LOdCLWefLSlvjmlZbJuoOIsPvAuIypDV95Rg9YPsVT3wSkoOuQUET6wIw38 BZsqEyHaKU57e3/HMWR6MawRxfHoBYM0+79ga97NllUNbteyUmQP4fA0yCFgJ8JLeXpw 4O/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Pkmde8GXa97lse64Ohk7moqzRMsV7T6SlMvnA5txgmw=; b=eL5iXNK45Y2/ssqtr3FD2cZW9OilU16b2Vemg0yQ8qaStMr+Hq5OhM5ydwhg3zsTH/ THMzbTnHVRhpTR624h5yLb5v3brwt9E26uWBPJw1lwv2nXwJR+HO3clun8XIzul4xbpy UQaaa9GgxK5WbPuliR33SFL6xHpFADyQwx+yjMCokwgY7AxkWopd/Ss6lCLjFlXh8IJs fIChJCgrAmr3iPbwhAi0psNzc9AAMoOmDQPJJ6N+E0aVDsH+17RiGz4x3GfS2fUSD/S8 alEvKbciksvFD/XV8Nx0OtCgF4RZlw+Een6BA553N90JGLojFA1qsJ6o7rpmhWiJrVp/ 5GdQ== X-Gm-Message-State: AOPr4FWfD5EZbO+tlU27zEZ3fh5c1rkgcuqsu0yPj7OnsPZwRlEwDsYVnSj8VguT+ysIota12y5So9zoHHGuVw== MIME-Version: 1.0 X-Received: by 10.202.58.134 with SMTP id h128mr11031646oia.174.1464037117399; Mon, 23 May 2016 13:58:37 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.4.200 with HTTP; Mon, 23 May 2016 13:58:37 -0700 (PDT) In-Reply-To: <154df5e88d5.102b02e6a194657.2169771434194203417@nextbsd.org> References: <1944f9ca-14fa-9839-11bc-b7597337866f@tysdomain.com> <154df5e88d5.102b02e6a194657.2169771434194203417@nextbsd.org> Date: Mon, 23 May 2016 14:58:37 -0600 X-Google-Sender-Auth: hRmPqVemF6OCZf3L3-fjkBCGIew Message-ID: Subject: Re: contributing to open source From: Alan Somers To: Matthew Macy Cc: Warren Block , sorressean , FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 20:58:38 -0000 Honestly, it's very rarely a problem. A blacklist would be much easier to manage. Can we try that first before we resort to moderation? On Mon, May 23, 2016 at 2:46 PM, Matthew Macy wrote: > We might consider whitelisting established subscribers and then moderating > everyone else. intel-gfx for example is moderation only. whitelisting would > minimize the burden on the moderator. > > -M > > > ---- On Mon, 23 May 2016 13:44:15 -0700 Warren Block > wrote ---- > > On Mon, 23 May 2016, Joe Nosay wrote: > > > > A bunch of stuff that should not have been written or sent. This type > > of behavior is not acceptable on these lists, regardless of your > > personal circumstances or the real or perceived level of provocation. > > _______________________________________________ > > 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" > > > > _______________________________________________ > 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 Mon May 23 21:19: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 5E9DDB47222 for ; Mon, 23 May 2016 21:19:47 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-lb0-x244.google.com (mail-lb0-x244.google.com [IPv6:2a00:1450:4010:c04::244]) (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 D4287124C for ; Mon, 23 May 2016 21:19:46 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-lb0-x244.google.com with SMTP id sh2so1738618lbb.2 for ; Mon, 23 May 2016 14:19:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=5R23mbcBiZ1b459A4Kws8AKImOnm9H/usV/eMfd5CgU=; b=sxg4L8LqI37oo6O4agqd2N2WTrFtzshUKDRUFMUZFcWc4l5xtngTJKPqEQrMbSM+FC +HunUdGiOPu8lOTdzSwqNA5v0aXhPEcOjWKCVf49iTXNM10LhJBXqXrBzojsoAO4XyJe QYGxbqkKW0emmRnDm5xb9ViQx4yJ0BZov1pUQCUKAednL41H/Lt67BwT5/c6wvvWJWEv BxqzQCUYUCqTwzMIyapGeR4/bTxKbQCWD4oZLTFy/vTs2LxYmQNuaZmLJ828oe8Txy2T Hy7hG7/zPn2MogsIdm62WT24xmCE0XbJ8T/4AT7zUK0Wr9BYIwND36IExSsq3tekdF3u kF0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=5R23mbcBiZ1b459A4Kws8AKImOnm9H/usV/eMfd5CgU=; b=cGB7KEH+BHJtC+tWQPe20VsHIpt2ZOkXd+I6k3b959SlsCoWg+0f3vCCzG3QNLDoGl p0GBkv5ow/5gSs2SWhmXlKkITyzk8PpqH8bqMmAgXconTJszPtbqo5WQoF75H0Q1PODC R7vl/bqurDGXTzZt5QOgnIlqqefyrY21yfckYuFsRcHKv+AwWnCpsivQga4vsjlZ6aCY 3VW4lipAVCTOA3TaUuMoWA8GQAJ4nKlWjZNuYLzo1TOkOb+hlEzHSnrRu9MFzSwj8IWp alVp7TfUXYULGgcn6lkNkkntg+2VThEQW6CzUmFNOHluKz2WJX04BOVmM7qLedMW76OD Yaxg== X-Gm-Message-State: AOPr4FUidXVcmLtgCpFhxz6AL1mqpVNrjgNpoh3U2tew1zVFmFq94gn1cG0hCqDWYRrICg== X-Received: by 10.112.43.225 with SMTP id z1mr6610541lbl.14.1464038385092; Mon, 23 May 2016 14:19:45 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id a131sm6212786lfe.1.2016.05.23.14.19.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 May 2016 14:19:44 -0700 (PDT) Sender: Baptiste Daroussin Date: Mon, 23 May 2016 23:19:42 +0200 From: Baptiste Daroussin To: freebsd-hackers@freebsd.org Subject: Re: contributing to open source Message-ID: <20160523211941.GK11189@ivaldir.etoilebsd.net> References: <1944f9ca-14fa-9839-11bc-b7597337866f@tysdomain.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="x1F0m3RQhDZyj8sd" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 21:19:47 -0000 --x1F0m3RQhDZyj8sd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline This behaviour is unacceptable in the FreeBSD community. The sender has been banned from our public mailing lists. Best regards, Bapt on behalf of the FreeBSD core team --x1F0m3RQhDZyj8sd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXQ3PtAAoJEGOJi9zxtz5a1XwQAIbvvzHfIYvCVXU0P3Oq48Vm jzyXAK4icQG40FDIcHhNwfXAwT5oSOpdRIlD0/egvPX3MmLzXJTW2bSDyMYLqQRR FqmKxXx3lyzDiDDQwlu1Sgkq3WsN8wwo/5a7JoQ/HT7DBwCoH5EKaN9Cq514/Z9K N2N8kieHJo6mWWhcpIbgk1wHgXP/w5khSjQiuWoBdHKhRDuTtijBdeobWm4KL5S6 JUb8ndu/bBqrdzhT69PUETfGsgC1BRbAe0u+sr2c2zufdabAPs966RvlRa4vkQwN InhULHb4tsQcUsdLixtazHLkgFtvVJi/zXrQk0WA2HNcam8rigF3lb4bHw4ibwfq t7NsLrxfGeY/xDnSED0UMJLOrJjlp494KUbdbhbsiQoYqnmBwxEQBHvUTY9rXUXv faQm1O0Rjt3lDsQxKhvpYgN9iAbHn70dZSVw4dlKR2SlkIcZNE5xxja4VoeXMnqa czQPNeJIw+llYUlsAR7qgqv5rzQnbzc3iN3sjlkSL0EP9K2OpK1Nwvks3icNPe5r t7f9LSyoXt5g3Kh18rXiFDauanBF6ZmwjeShUj1YuYfHwLUmcSOyRprAn+TTQdft tVCegq0YU2rTov2Fx+9867pO8+4kbt/OqE6lGQjhhjHPzz67NdSOm1pDYuLIUNd+ WauC9IwHveLD4b2fsGFH =/3Nx -----END PGP SIGNATURE----- --x1F0m3RQhDZyj8sd-- From owner-freebsd-hackers@freebsd.org Mon May 23 21:41:05 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 0E22BB47882 for ; Mon, 23 May 2016 21:41:05 +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 E411C1287 for ; Mon, 23 May 2016 21:41:04 +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 031F8B94E; Mon, 23 May 2016 17:41:04 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Cc: Rick Miller Subject: Re: AIO in 10.0-RELEASE Date: Mon, 23 May 2016 13:54:18 -0700 Message-ID: <5493135.9JME949vIb@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: 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); Mon, 23 May 2016 17:41:04 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 21:41:05 -0000 On Thursday, April 07, 2016 01:45:46 PM Rick Miller wrote: > Please reply directly as I am not currently subscribed to this particular > mailing list... > > A user has been implementing AIO features in an application on FreeBSD > 10.0-RELEASE. They assert that, despite aio(4) stating that it is enabled > either statically (with VFS_AIO in the kernel config) or dynamically > (kldload), in their development environment there was no requirement for > either of these methods of enabling AIO. My google-foo is failing me when > it comes to FreeBSD's AIO. > > This question defies logic, but is it possible that AIO works by default in > earlier versions of 10.0 and not in more recent version of 10.0 without any > local system changes? > > It is understood that AIO has recently been enabled by default in FreeBSD > 10.3 and -CURRENT. This particular scenario is applicable to 10.0. I don't think 10.3 has enabled it by default. All of my changes are only in HEAD. I think you've always had to enable aio explicitly via kldload or VFS_AIO in a custom kernel prior to my changes in 11. -- John Baldwin From owner-freebsd-hackers@freebsd.org Mon May 23 21:41:07 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 D5BFFB4795E for ; Mon, 23 May 2016 21:41:07 +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 B670B12A3; Mon, 23 May 2016 21:41:07 +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 D2CACB9A8; Mon, 23 May 2016 17:41:06 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Cc: Andriy Gapon , FreeBSD Hackers Subject: Re: hpet as nmi watchdog Date: Mon, 23 May 2016 13:44:55 -0700 Message-ID: <2056148.ZvOkyra82H@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <56DEB97D.2010804@FreeBSD.org> References: <56DEB97D.2010804@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); Mon, 23 May 2016 17:41:06 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 21:41:08 -0000 On Tuesday, March 08, 2016 01:37:33 PM Andriy Gapon wrote: > > I toyed a little bit with an idea of using a HPET timer as an NMI watchdog. > The idea is that a HPET timer is somehow configured to generate an NMI when it > fires. The timer normally would not fire, of course, as it is constantly being > reprogrammed to some future time as is the case for all watchdogs. > > I have written some proof of concept code using two approaches. One approach is > to use the "FSB" (MSI-like) mode of a HPET timer and program a corresponding FSB > data register (HPET_TIMER_FSB_VAL) with a value that sets NMI delivery mode > using the IO-APIC specification. The other approach is to use legacy interrupt > mode for the HPET timer and program a corresponding IO-APIC pin for NMI deliver > mode. > In both cases I haven't got a desired result - instead of an NMI a test system > gets reset when the timer fires. I wonder if this is a quirk of my old hardware > (HPET in AMD SB7xx, family 10h processor) or if my idea is a non-starter. This is an interesting idea. You could also use one of the other timers (8254, etc.) as a watchdog by setting the I/O APIC pin to NMI as well. It maybe that for the MSI case the chipset treats the NMI delivery mode as an error, hence the reset. :-/ -- John Baldwin From owner-freebsd-hackers@freebsd.org Mon May 23 21: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 593B3B47947 for ; Mon, 23 May 2016 21:41:06 +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 3BC6D128E for ; Mon, 23 May 2016 21:41:06 +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 43336B978; Mon, 23 May 2016 17:41:05 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Cc: Willem Jan Withagen Subject: Re: Mising ENODATA Date: Mon, 23 May 2016 13:47:26 -0700 Message-ID: <5030334.fMbvND8flt@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <56E6C5EA.2080005@digiware.nl> References: <56E6C5EA.2080005@digiware.nl> 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); Mon, 23 May 2016 17:41:05 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 21:41:06 -0000 On Monday, March 14, 2016 03:08:42 PM Willem Jan Withagen wrote: > Hi, > > According the standard is ENODATA an extention of errno.h defines... > > http://pubs.opengroup.org/onlinepubs/9699919799/ > > The Open Group Base Specifications Issue 7 > IEEE Std 1003.1, 2013 Edition > > [ENODATA] > [OB XSR] [Option Start] > No message available. No message is available on the STREAM head > read queue. [Option End] > > [XSR] [Option Start] XSI STREAMS [Option End] > The functionality described is optional. The functionality described is > also an extension to the ISO C standard. > > Where applicable, functions are marked with the XSR margin legend in the > SYNOPSIS section. Where additional semantics apply to a function, the > material is identified by use of the XSR margin legend. > > [OB] [Option Start] Obsolescent [Option End] > The functionality described may be removed in a future version of this > volume of POSIX.1-2008. Strictly Conforming POSIX Applications and > Strictly Conforming XSI Applications shall not use obsolescent features. > > Where applicable, the material is identified by use of the OB margin legend. > ---- > > The OB part makes a bit strange to ask for definition, but would it be > possible to add ENODATA to our headers? > The alternative question is: why would we not? Well, it's defined for STREAMS and FreeBSD (and BSDs in general) don't implement STREAMS. OTOH, if Ceph has (ab)used it for their own internal errors then we could perhaps add our own ENODATA. Do you want to make a patch to do so? -- John Baldwin From owner-freebsd-hackers@freebsd.org Mon May 23 22:16: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 103BAB47592 for ; Mon, 23 May 2016 22:16:33 +0000 (UTC) (envelope-from ike@blackskyresearch.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DAC4812F7 for ; Mon, 23 May 2016 22:16:32 +0000 (UTC) (envelope-from ike@blackskyresearch.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CB43420881; Mon, 23 May 2016 18:16:25 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 23 May 2016 18:16:25 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= blackskyresearch.net; h=cc:content-transfer-encoding :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=0ge97 DJCLbil7uT/dICcEUkmgHo=; b=VWTsBwLTywWCcLYQtml+F0i8luwLyt1cpoDAp szVCG8qLsmYClrmNk+ITT+e1EJ5y4aNr8KHPz0fTmFR4jkTPw4oof0JDQJUnVEuk iL7BLqLrmzBv70JkcmK7RGKpstph/TsWP7t8w5oICxvGpc3ZAH2gx9/JnZ6bmkjw Ged55E= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=0ge97DJCLbil7uT /dICcEUkmgHo=; b=LfS0huFyUoKFlGJggdYEn/RlcgPMUkIV0pMW1s+FzhdKnkl SssUvUjUUKr0/6hHug4KVGwCA/CZa0J9yJ9LgxNbXh51AE1CHkb0ZyuxONNOeiek q+Ic0Pf68bK15v8VUmBBgNtseM96/TVPm+jAnzGHkOmMwypobVIFNi6NL/Pg= X-Sasl-enc: mIGEA7nk1IUGHZDC9zN04pLGi3xc8PhXr5jqzsrd6H8T 1464041785 Received: from [10.22.162.12] (64.90.176.98.static.nyinternet.net [64.90.176.98]) by mail.messagingengine.com (Postfix) with ESMTPA id 8A219CCD88; Mon, 23 May 2016 18:16:25 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: contributing to open source From: "Isaac (.ike) Levy" In-Reply-To: <20160522222937.GG41763@strugglingcoder.info> Date: Mon, 23 May 2016 18:16:24 -0400 Cc: Benjamin Kaduk , hiren panchasara , freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <2F06E9C5-B8DF-495F-B650-1433438E0B6D@blackskyresearch.net> References: <20160522222937.GG41763@strugglingcoder.info> To: Kefeh Collins X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 22:16:33 -0000 Hi Kefeh, All, One more recommendation as you explore, > On May 22, 2016, at 6:29 PM, hiren panchasara = wrote: > On 05/22/16 at 05:31P, Benjamin Kaduk wrote: >> On Sun, 22 May 2016, Kefeh Collins wrote: >>=20 >>> hello >>> i am a second year computer science student, program in c and c++ = and am >>> interested in contributing in operating system (kernel) directed = projects >>> please i need guidance >>=20 >> A couple of thoughts: >>=20 >> (1) There's an "ideas list" at https://wiki.freebsd.org/IdeasPage and >> links to some other things as well, if you are just wanting potential >> topics to work on >>=20 >> (2) You might try to join an IRC channel or two to get a sense for = what is >> going on and get to know some other developers. #bsdcode or #bsddev = on >> EFnet come to mind, but see also https://wiki.freebsd.org/IrcChannels >=20 > Good points, Ben. I'd add: >=20 > (3) Look at https://bugs.freebsd.org/bugzilla/ and see if you can find > anything you'd like to work on. If you do, propose a patch or ask a > question there without hesitation. >=20 > (4) If you are interested/willing, you can setup a machine (or a VM) > running FreeBSD. (Not directly related to programming but this can = give > you a good idea of how FreeBSD works.) >=20 > Thank you for your interest in FreeBSD! >=20 > Cheers, > Hiren (5) Try to find and attend a *BSD or other UNIX User Group in your area! = The FreeBSD site has a ton of listings, worldwide: https://www.freebsd.org/usergroups.html Best, .ike From owner-freebsd-hackers@freebsd.org Mon May 23 22:37: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 D4611B47A71 for ; Mon, 23 May 2016 22:37:40 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 609E3104A; Mon, 23 May 2016 22:37:39 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id DB6D315340D; Tue, 24 May 2016 00:37:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q8HdnNjciopq; Tue, 24 May 2016 00:37:06 +0200 (CEST) Received: from [192.168.10.10] (asus [192.168.10.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 5BCD1153401; Tue, 24 May 2016 00:37:06 +0200 (CEST) Subject: Re: Mising ENODATA To: John Baldwin , freebsd-hackers@freebsd.org References: <56E6C5EA.2080005@digiware.nl> <5030334.fMbvND8flt@ralph.baldwin.cx> From: Willem Jan Withagen Message-ID: Date: Tue, 24 May 2016 00:37:08 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <5030334.fMbvND8flt@ralph.baldwin.cx> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 22:37:40 -0000 On 23-5-2016 22:47, John Baldwin wrote: > On Monday, March 14, 2016 03:08:42 PM Willem Jan Withagen wrote: >> Hi, >> >> According the standard is ENODATA an extention of errno.h defines... >> >> http://pubs.opengroup.org/onlinepubs/9699919799/ >> >> The Open Group Base Specifications Issue 7 >> IEEE Std 1003.1, 2013 Edition >> >> [ENODATA] >> [OB XSR] [Option Start] >> No message available. No message is available on the STREAM head >> read queue. [Option End] >> >> [XSR] [Option Start] XSI STREAMS [Option End] >> The functionality described is optional. The functionality described is >> also an extension to the ISO C standard. >> >> Where applicable, functions are marked with the XSR margin legend in the >> SYNOPSIS section. Where additional semantics apply to a function, the >> material is identified by use of the XSR margin legend. >> >> [OB] [Option Start] Obsolescent [Option End] >> The functionality described may be removed in a future version of this >> volume of POSIX.1-2008. Strictly Conforming POSIX Applications and >> Strictly Conforming XSI Applications shall not use obsolescent features. >> >> Where applicable, the material is identified by use of the OB margin legend. >> ---- >> >> The OB part makes a bit strange to ask for definition, but would it be >> possible to add ENODATA to our headers? >> The alternative question is: why would we not? > > Well, it's defined for STREAMS and FreeBSD (and BSDs in general) don't > implement STREAMS. OTOH, if Ceph has (ab)used it for their own internal > errors then we could perhaps add our own ENODATA. Do you want to make a > patch to do so? Well actually I think it is Linux that has found a different purpose for the error value. It uses it as error value where FreeBSD would return ENOATTR.... The actual Linux value is 61, which on FreeBSD would give ECONNREFUSED. Looking at Linux manual pages they write: ENOATTR The named attribute does not exist, or the process has no access to this attribute. (ENOATTR is defined to be a synonym for ENODATA in .) So perhaps for FreeBSD we should do more or less the same, but the other way around? Although on CentOS it is actually in: xfs/linux.h:#define ENOATTR ENODATA /* Attribute not found */ And thus in errno.h include #define ENODATA ENOATTR This would also return the same error string for ENODATA as it would for ENOATTR. Perhaps not quite what was the intention of the Posix extension, but as close as possible to what Linux took it to be. No idea what FreeBSDs position is on this? --WjW Still it does not have the same value as it would on Linux, so over the wire they would still not be compatible. But I think it would work for code that is confined within a host. From owner-freebsd-hackers@freebsd.org Tue May 24 06:57:27 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 2D692B48CA5 for ; Tue, 24 May 2016 06:57:27 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD5141F4D for ; Tue, 24 May 2016 06:57:26 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vps.rulingia.com (8.15.2/8.15.2) with ESMTPS id u4O6vCSK025229 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 24 May 2016 16:57:17 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id u4O6v6wj082431 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 24 May 2016 16:57:07 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id u4O6v6QZ082430 for freebsd-hackers@freebsd.org; Tue, 24 May 2016 16:57:06 +1000 (AEST) (envelope-from peter) Date: Tue, 24 May 2016 16:57:06 +1000 From: Peter Jeremy To: freebsd-hackers@freebsd.org Subject: Re: read(2) and thus bsdiff is limited to 2^31 bytes Message-ID: <20160524065706.GG6157@server.rulingia.com> References: <20160522225414.GB24398@britannica.bec.de> <154dab43060.11208cdfd132112.2616144627831899155@nextbsd.org> <20160522231203.GB25503@britannica.bec.de> <154db353935.dd5e87c1133922.4370692881788049491@nextbsd.org> <20160523122131.GC8747@britannica.bec.de> <20160523134106.GB17056@britannica.bec.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Qz2CZ664xQdCRdPu" Content-Disposition: inline In-Reply-To: <20160523134106.GB17056@britannica.bec.de> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2016 06:57:27 -0000 --Qz2CZ664xQdCRdPu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2016-May-23 15:41:06 +0200, Joerg Sonnenberger wrote: >On Mon, May 23, 2016 at 02:31:18PM +0200, Cedric Blancher wrote: >> Nothing in POSIX mandates that read()/write() are atomic. Old UNIX, >> SystemV, AIX, Solaris and HP-UX don't do that nor do they guarantee >> that. > >"I/O is intended to be atomic to ordinary files and pipes and FIFOs." To expand that a little, the rationale (which is "informative") in http://pubs.opengroup.org/onlinepubs/009695399/functions/read.html states: "I/O is intended to be atomic to ordinary files and pipes and FIFOs. Atomic means that all the bytes from a single operation that started out together end up together, without interleaving from other I/O operations." This is slightly different. OTOH, the description does indicate that short reads from files can only occur due to EOF or interrupt (or exceeding {SSIZE_MAX}). --=20 Peter Jeremy --Qz2CZ664xQdCRdPu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXQ/tCXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0H1oP/jpFY7CXehbh4tjKFQ12Xypb t0htMZ2YJ9eiXSi1lOs3bSyaUayHnk/ttcT+MttlEzwY7CCa5JoXlCYxHaiYQ89M bGcVw/hFxov81Dz/aMpTA2ec1dzDkL0BaZGLAnDsu5Yg+U0s5vw5NF8aFPa75Zbv yc0bHmRZTnSOLJ7JXshFFR6mm84/WxSfpfUjdWmGdATO46yGvs5N1niikcaubaw4 wmThpl3Kf83YnBCfT+jJljQy/XWofjAPXcf14v3KRbGBtGxf3RuU/7YFKttcPedE fz44iWqX/FLbupXL0qR0sT52krHjZU4nV2Q0EIEfPAKG34saMBq36ejdnGncG/Pd MoL8CqC7NlPRdL5AVoCBBF7i6VMs3hdpKRg3bpHFr+EBNC6hLj0oQV2CfCrj4dkU XEz4IgUQmYi3UYsvJvG+VPgD/pHHTi2udw4joladw2qTQtlbO1v+w5CKUokqCoMb 723mnatJPkLq6gRHZd5psMQozouv14T7zbOTJq7ROEM2nf5I6906Roc1Biy+gdmk ifXLa/EUffOGn98jRWWmQs8i43d5f7HmCdeQ76KI5z5vd3G9MAubU2lLBJ9i7gqW O0ruNr4u5i4NzpgQ+oA63/qKVku02QreIGfA0N1sqT93rRN9v5MJTXQ1/zE4KF+G p7xDM5FwJ6O0ZwyLmg9a =D5EW -----END PGP SIGNATURE----- --Qz2CZ664xQdCRdPu-- From owner-freebsd-hackers@freebsd.org Tue May 24 20:33: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 81C90B49707 for ; Tue, 24 May 2016 20:33:43 +0000 (UTC) (envelope-from outro.pessoa@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 114271F1C; Tue, 24 May 2016 20:33:43 +0000 (UTC) (envelope-from outro.pessoa@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id q62so9487957wmg.3; Tue, 24 May 2016 13:33:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=G0nP9oO3HjDFF9IwON7uz3grm2sMm4F0bnWYZusimhY=; b=bR1/0yTngjOtP1HGgTG38o96vIlE2JFtvlKAM4f6jYQ6d2YKJowOC8TrO8A4vqhCnx sx9xT5Mlq/xyt44Q4c+6R8V1/dpK4IJ9TUuAA/bH7W1Y7OjRT7p9df/qbmO/wgabo8ki DDBZbtK3B8n+fnoWDnuSQ7s3lg1waa0P0CJeyBgYebv+GRAQZMm7f+0zPdQEhOp/g49/ gyZbVT9ifZ9C9ureVDjCTtaCep0jpIR92lQf7SgfYjV86n9+FMkaA++07Y/09FOSUi6g I+f7/lHuUQdL19orsjGwr8o28e36VQcmzHlNUA/Nw0MToR6+FEzSsGJYV7G+3E8llRS2 1Juw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=G0nP9oO3HjDFF9IwON7uz3grm2sMm4F0bnWYZusimhY=; b=ZgF/7efNigIb2bl645pcQ/jkqcR+3QxeReHd6dgjCey2IRVLtWCiS+x5IJjxtF0UHK BOQfjmsmC1J+EQMLoF998iSpj56+Ax34uKEBdQRa6KTWnojz9NvAHnsuNgfiKu2/8kbx zEakzmGReWGcTWYiOg8nxYNYYkD329MEUqDkEbuJ3736YmfoIdxKxOuQPzHxkS/yiQ3X bZua2lIZJgubnzUAr/64SQ2LA0pqKayPGRTyZsTt20qYXLFCfU7e0cZNQJhisa1kx9yu e+8yllNdksxxz2Zjj0Jxj2HQ27qC0+RDUvI6eh38uPSS3u/EyBWwWEOnmlzs+AQNMzmY if+w== X-Gm-Message-State: ALyK8tKe1TUDd7ZhmRriWPLBBH9yG+97WnDs1qgmTGbCHy99J4+nqt9qbryJSfVc+YIWLhykoGY68CWvSvSDCQ== MIME-Version: 1.0 X-Received: by 10.194.72.103 with SMTP id c7mr79770wjv.65.1464122021438; Tue, 24 May 2016 13:33:41 -0700 (PDT) Received: by 10.28.141.208 with HTTP; Tue, 24 May 2016 13:33:41 -0700 (PDT) Date: Tue, 24 May 2016 16:33:41 -0400 Message-ID: Subject: We have a problem here From: outro pessoa To: freebsd-hackers@freebsd.org, adrian@freebsd.org, wblock@wonkity.com, info@freebsd.org, sorressean , dru@freebsd.org, misc@openbsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2016 20:33:43 -0000 It seems that some of you are willing to accuse one of speaking and writing falsehoods. A man comes on her being honest and the first reaction you give him is that he is a liar. When his reaction is one that you do not expect, you become defensive and start setting down standards. Every single time that I am honest, one of you comes out and insults me to no end, expecting me just to suck up your bullshit as if nothing occurred. You speak to me and of me as if I were a piece of shit on your shoe. You disrespect me. And when I react and warn you, you start crying and you try to muscle up like the bullies that you are. All of you are behind your computers picking on the homeless guy who is trying to do something right. And you go from there to insult me and my family to no end. It is libel and slander for any of you to call me a liar about what is on my birth certificate. It is harassment for you people to continuously use me as your scapegoat for whatever reasons that make you ill. All of you are aware of my sensitivity; yet, you still go out of your way to harass me. If I had done the same to you, I would have been arrested and put in jail. And yet, you people are still free to annoy and harass me again. I am homeless. I was given equipment and I want to use it as an animation station for children. You will go out of your way -as you already have - to degrade me just for being humble, considerate and kind. You laugh at me when I try to aid others. What right do any of you have to judge me when you have broken your own laws many times? I am able to present documentation that will state none of you have the right to put me in any stressful situation. If doing such does occur, I have the right to file charges. Go through the mailing list. And read how Mr Sorrenson harassed me to no end. And then you will support him after he has broken state laws. You see, I want all of you to come here and meet me. I want all of you to bring your accusations against me in a court of law. Theo de Raadt also went beyond what was normal and insulted me to the point of harassment. And then he cried about my reaction. Unlike you - plural - I do not deny anything that I have said or done. I also do not admit to such until the time is right. I sit here and watch your conversations in person, overhearing - ear hustling, and reading the mailing lists and forums. You go back in your everyday lives with no regard of what you say or do... Until you fuck up and anger someone that did you no harm and no wrong. You called me a liar about my own mother and my birth when I told you the truth. What in the hell is wrong with all of you? Seriously, what do you have between your ears? Bullshit? I hear someone muttering "Wait a minute, man, and let us explain." Explain what? That you are all evil and selfish? That you care only for yourselves? Who do you think you are talking to right now, huh? My personality is the same no matter where I go. I don't put on faces. I am me. On the forums. In the streets. On the mailing lists. In the woods. Yeah, I said it. And you find it humorous that a man in my position would go out of his way to aid and assist others before taking care of himself. I have this equipment and it will go to aiding and assisting children and students. I have nothing. I am homeless. I look out for others. And, All that you people do is treat me like shit because I refuse to be as twisted as you. I am here waiting for any of you to approach me in person. Since you were warned, you should know now how to act accordingly. You will approach me with respect because I gave it to you when you did not give it to me. What do I mean? When you attack another without consideration, that is a sign of disrespect. You made an assumption of my character. Did any of you ever think that if it is not written or spoken, then I did not mean or want you to see such? I thought about the whole process before and decided that it would be better to say, "Write legibly," instead of accusing someone of wanting ignorance. Get it? And then Mr. Sorrenson - and before Mr. deRaadt - went out of their way to insult me, thinking it was cute and funny. Do any of you remember the youtube piece about the tiger that attacked the two idiots who were harassing it to no end? You do. Ah, yes. Well. You have annoyed the tiger. If you are so willing to harass me and my family, then you should be willing to go to court for what you do. From owner-freebsd-hackers@freebsd.org Tue May 24 23:41: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 3D74DB49A4D for ; Tue, 24 May 2016 23:41:03 +0000 (UTC) (envelope-from javocado@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::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 BCA451108 for ; Tue, 24 May 2016 23:41:02 +0000 (UTC) (envelope-from javocado@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id e130so11890818lfe.3 for ; Tue, 24 May 2016 16:41:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=FIDlbRQ6866nn97bEdiDmz1Cv/EmAxgudkYDcZlr7q8=; b=Brh19c38Q1XW9k5bdMOGwoNQvSgBXfYOPezFzh4FuBtBxf13Ip1gKmXFFrroud4Nds KOhcxDOY48eqxF4KKqnJ8SU5QwitTXp2izww+8A5WaCXngsGmMeJ48IhlVnldHSKtBrN tlNu6FNGtQI0XaCMvYWWT/ZLpGrJCNnX/S6OeAOCS7eTGPq5prTQGVSUXqDCCmmGtby1 1SJrXxEL8BN9RAmc0AWZjINkObq1gt1KN1ClK9DgCGEfSpehzyBViF6aMHe3M+ArNWmq Fp1WeqyPTVikXnFtPR7T96ebBmV3MR+7GalOkcRd/NrKt4IWYI2+GLeZuuWZpuoBe4tR fixA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=FIDlbRQ6866nn97bEdiDmz1Cv/EmAxgudkYDcZlr7q8=; b=DJ/EBmqEIyWvwgol2/myoFSNsezEdivhSgVXHU5WjfQgt83Lj0pu7gG3DCJfNMJ3nO ltqb6sHmd7B9RDFIYbxeyjNFA3NUm2DLDw7H3O4uhhg4NA18PX8SpGGb9AMc5j6Q7NDa WWT8dDibvUMKHhJwz4z9S6kT3Lj7b5rhv1C3w0oweslFueZ0wfe8kRHww7jT3JtcW0u+ ZqY9yU5Hnif9/qTCyO1Isaknupp23Rd1NbhQfETVXeifR28TQfcqXagCgNRHJHSzTnhw S8+Ow9ThgM9WjTqkCwifXVNkN0sHNnswbpwII7DCr1N18SoJ3NohCERdeAuajESehbT6 w8eg== X-Gm-Message-State: ALyK8tLETxG96bjySsXjLqpGnWtSO6magicPQZTwwLeIpIAKN1EhqCAZF7mSBgWKj8NJKKygXZt17OQ0WNnlIA== MIME-Version: 1.0 X-Received: by 10.25.162.76 with SMTP id l73mr165992lfe.45.1464133259781; Tue, 24 May 2016 16:40:59 -0700 (PDT) Received: by 10.114.175.212 with HTTP; Tue, 24 May 2016 16:40:59 -0700 (PDT) Date: Tue, 24 May 2016 16:40:59 -0700 Message-ID: Subject: UEFI support in bhyve (Solaris VM possible?) From: javocado To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Wed, 25 May 2016 01:25:38 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2016 23:41:03 -0000 What is the status of UEFI support for bhyve in FreeBSD-10.3-RELEASE? I am looking to run a Solaris VM and I believe this (UEFI) is the only way it can be done. Thanks! From owner-freebsd-hackers@freebsd.org Wed May 25 01:51: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 DFC01B4987B for ; Wed, 25 May 2016 01:51:00 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 9DC8216D9 for ; Wed, 25 May 2016 01:51:00 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qk0-x231.google.com with SMTP id x7so24940473qkd.3 for ; Tue, 24 May 2016 18:51:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=byv4OHyEDQv4ULOYLgLAg8jgKYm/vLDqj62CZQyr3A0=; b=TJ2clVywUNUvYSNUQmqQ3ZOhchvb5SV1GaUgDH2/nXQMs3gdSspV8GEFLCiH+wC9AB hzBVQxCbvjIPg2GZfmiOuewaJKtQ4K+G41tXjnkN1nsl2OLII4fJQFL/0dO9alPm70xV gJBg4U7cN2VJrZ3ojL+pZ2Fz8hp2Sgsado+sNG7wXvf0KHS+PAcpAmcs/dUvTevkyN6o VjFQRIoojWmPD147d0RfybV62D0rtumcOx/tzK/LaGoL1PReEHf+QxyE70mETMcdtj1R caDp/atl6rYH6c1sQvEGhlPeiOEeIpYQLfWACCFM90ceKZpg3WpsTldarLvhKOVzBNX6 9Smw== 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; bh=byv4OHyEDQv4ULOYLgLAg8jgKYm/vLDqj62CZQyr3A0=; b=PX3+N+BlRiul7X0MISf/iVhdIMUSlf5mJMrETCShosYw8H8MqMEIj8BRwOU8bczNKj sndeVTgsvPbECKQd0RVymCmfedyll94NJ4IL9UspfgT86IEnBjU2UZi8hhaPfRe3sxMC HKow3BV8NACJVmnmUBPouQxSN1q44zt/Y5MloJQQpByvRBAbWoYhzUra5qG2CmXmOoZf iA213VkKXC/FxHkY6P3LUqjtS55Sqs9BPC7xGfbLIjjvCNEKt7iAy+HB1WY4fbrpNghN HFm+KtynAGDrknlYVQ1L+6W8AbwHcuu9Fly1paPtWvyktMd4Z53jfZpZ3tPlMQo58mU4 BNXA== X-Gm-Message-State: ALyK8tJJPklUFBfQ+2XtSb55Bl6oukU8i3EB2vwsCUOl6f9Rtbn9y+Cl/jRHVv6sBeLqDrUjXR2oSeSUkmlS+w== MIME-Version: 1.0 X-Received: by 10.200.41.88 with SMTP id z24mr1255022qtz.78.1464141059564; Tue, 24 May 2016 18:50:59 -0700 (PDT) Received: by 10.55.154.194 with HTTP; Tue, 24 May 2016 18:50:59 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 May 2016 04:50:59 +0300 Message-ID: Subject: Re: UEFI support in bhyve (Solaris VM possible?) From: Andrey Fesenko To: javocado Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2016 01:51:01 -0000 On Wed, May 25, 2016 at 2:40 AM, javocado wrote: > What is the status of UEFI support for bhyve in FreeBSD-10.3-RELEASE? I am > looking to run a Solaris VM and I believe this (UEFI) is the only way it > can be done. > > Thanks! I'm run SmartOS (illumos/solaris) with https://github.com/churchers/vm-bhyve and https://people.freebsd.org/%7Egrehan/bhyve_uefi From owner-freebsd-hackers@freebsd.org Wed May 25 08:41: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 79F66B49985 for ; Wed, 25 May 2016 08:41:08 +0000 (UTC) (envelope-from noname.esst@yahoo.com) Received: from nm25-vm5.bullet.mail.ne1.yahoo.com (nm25-vm5.bullet.mail.ne1.yahoo.com [98.138.91.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 45D141D4C for ; Wed, 25 May 2016 08:41:07 +0000 (UTC) (envelope-from noname.esst@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1464165661; bh=8Y6oqJFjnurWhYolukbkpfp7z2O4K9cFN8Zh/XhLT8Y=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=TqUPhYapsjWaNTj7qjxFqr3KezXnvzg61Np0TMtqdQSzaNfQFAbfPvDohbrQa3wdGPGPoSTpOHYePmVKk00s/qDDjBI7e4ODpbZf8Ru7nRhcG/+i7kUe2CHHcCdiNQYnBTnZb5WQAbmZeMmTnWBzdoRacxoFpYo/3Gx7LunqDIZnWQFhah2GjaAVbsqZSK1ot+3MMU++NftKLFBhIjx+9gZUOFB+GChiyWJRjnWZSDIYJPNiHsh19rpL+0oh42DNBtU03fjTdSIkwvXZJxUw3TZYLTFGXDmEbRBeEqZpGOV3btoUSob6UfSbaUBI3TyY+LELYMcApGRcoYqWQJM4Rw== Received: from [98.138.100.103] by nm25.bullet.mail.ne1.yahoo.com with NNFMP; 25 May 2016 08:41:01 -0000 Received: from [98.138.226.163] by tm102.bullet.mail.ne1.yahoo.com with NNFMP; 25 May 2016 08:41:01 -0000 Received: from [127.0.0.1] by omp1064.mail.ne1.yahoo.com with NNFMP; 25 May 2016 08:41:01 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 188549.2099.bm@omp1064.mail.ne1.yahoo.com X-YMail-OSG: ZOYlvZkVM1lNQkz75yqXMNXmZJCjgXfEm0OcxHu5IsGmnPjUu.8lkpu_AHpwLeh LmSMLDZKCvYUz9oXp1qjlO8lB5ZMkrI5gC2nj2hvKWiaR3mbXIxPiEaizd3Os.1rj_dyvL56qvaY .M30yuHOs736QHLlVqDblr8pGrjS4kkU4BxWxYMHSTrGtcazNFaP2knl1M4WsvHfQl9ngSFTkTu0 2zh8Q4V2VnbyMXW.LiobWYylP5xCjhvlaLiMVIORyIYFLK8n_U2luyXk4uWnid48z754V896WRat T99W.kG9LSr.w52JFbcedSxjzdO5jQxv3tdd.a.jZcEdf.PUbc1crsMKksntn5640l0zfHaaQbv1 ksfaQ2WjGmtjlHQ8dwNYoqX.b7u7GnyFpS8VHq7KqzSXCoI5vShT8YXcT0tRAvP8pSqb13X45jE0 6LRpE77bWTk4FK8q5iRkDwqiZbyl.aaMUVTe1.E_0HmZQ26tVFfjaB5tHv.NBKnngmYuU36QcaIa kpEqJnAQ5eykHMg-- Received: from jws10014.mail.ne1.yahoo.com by sendmailws147.mail.ne1.yahoo.com; Wed, 25 May 2016 08:41:00 +0000; 1464165660.713 Date: Wed, 25 May 2016 08:41:00 +0000 (UTC) From: Nomad Esst Reply-To: Nomad Esst To: FreeBSD Hackers , FreeBSD Net Message-ID: <1807465361.275157.1464165660481.JavaMail.yahoo@mail.yahoo.com> Subject: Looking for a freelancer to do some netgraph stuff MIME-Version: 1.0 References: <1807465361.275157.1464165660481.JavaMail.yahoo.ref@mail.yahoo.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2016 08:41:08 -0000 HiI'm looking for some one to help us develop an application based on netgraph (you will be payed). Please let me know if you are interested. Thanks in advance. From owner-freebsd-hackers@freebsd.org Fri May 27 03:15: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 6B2ADB4BDE9 for ; Fri, 27 May 2016 03:15:48 +0000 (UTC) (envelope-from kefehcollins@gmail.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 36CF71F45 for ; Fri, 27 May 2016 03:15:48 +0000 (UTC) (envelope-from kefehcollins@gmail.com) Received: by mail-io0-x234.google.com with SMTP id 190so64931746iow.1 for ; Thu, 26 May 2016 20:15:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=lz2mYtIlj0qxb35xhIMFwAODQRNhF+Y73dmEZpHC/M4=; b=uEFzx3+cdC9ph7HQSSwGp+ztO1ae5vLMHJC5mwFw59S2h/wq2G14cmntIFBmfrD+pF jDidHJ/PQJy39f3xQvU7pFiUsvJWUOY3j9+myuHutPJeMcl1FfT642FGdPn5Y464cFlP bz0hbCykuqSu7bFtvkAIN67vJVedEkz2k7LRhjuipSAEv1JjQUbk7xAXx9hQdkYbuY/L 1sQQnutNz3jJvsdhx+sqPCMtHt1hFFWHssGl1qjOipzdTshodqYQtmHVkseDO3tGfSGb +an8vNoCKY8QuNRjoTfTCA8Q4t3tJHf3s7Zt1uTR9evAipLAPrDgyGQu2k5WEOCKLLn3 GB0g== 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; bh=lz2mYtIlj0qxb35xhIMFwAODQRNhF+Y73dmEZpHC/M4=; b=hPwjZ7kIQayH/nbn7UISMlF/dN2jYFarBi/ux8C0A6yBsBXVJ9YfJD8lCbO3SFCGhY UPeUQsyx8abz+QTOpB1h618AZuC/LfT1L+nyESrr4htlACcggRA6ZX+2bH5W14LFW5Ao qQqrsdTAul0RuJ4JCpZhgmqGKdPaa09VsCaOQ9VtgI32ItYA+eAJm5SUj/ZxTcWc+iE2 Q1FbBC435r9+zvZ5prqBE3Wq4/3AO8f6A8o5MsQLTxqQRiRdsR6Fw1tkHzhj7MnecDaS nxzWoIz2jkRfIVoebtOKISyeQBGh8K+V78vgb8zg9LotyNglO++aeN/Qt7v04YCX9YKE Z1wA== X-Gm-Message-State: ALyK8tJ0ubi1Hh67OiUPrmyKn6Ucb9DmmI/gHz1SBgyUpANbkItrqaXMcIsajh11EPSvwdK3M9Hh9iO1W1wfIQ== MIME-Version: 1.0 X-Received: by 10.107.11.18 with SMTP id v18mr12348664ioi.184.1464318947638; Thu, 26 May 2016 20:15:47 -0700 (PDT) Received: by 10.64.228.70 with HTTP; Thu, 26 May 2016 20:15:47 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 May 2016 04:15:47 +0100 Message-ID: Subject: Re: contributing to open source From: Kefeh Collins To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 03:15:48 -0000 good morning please i have downloaded the freebsd source code but i cant find any information on how to build it (in ubuntu 14.04) i will very much appreciate any help thanks in advance On Sun, May 22, 2016 at 1:40 PM, Kefeh Collins wrote: > hello > i am a second year computer science student, program in c and c++ and am > interested in contributing in operating system (kernel) directed projects > please i need guidance > > thanks in advance > From owner-freebsd-hackers@freebsd.org Fri May 27 03:20: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 0143AB4C043 for ; Fri, 27 May 2016 03:20:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id E729111E0; Fri, 27 May 2016 03:20:57 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id A98611F86; Fri, 27 May 2016 03:20:57 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 27 May 2016 03:20:56 +0000 From: Glen Barber To: Kefeh Collins Cc: freebsd-hackers@freebsd.org Subject: Re: contributing to open source Message-ID: <20160527032056.GA3335@FreeBSD.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="eb1XlXx8qH4KcAJ0" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 03:20:58 -0000 --eb1XlXx8qH4KcAJ0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm not entirely sure FreeBSD sources build on Linux, but I may be wrong. I know there is somewhat an ongoing effort to make sure FreeBSD is buildable on non-FreeBSD systems. As a semi-solution for you, we do have publicly-available virtual machine images, so you don't need to have a local FreeBSD physical machine to play around. Glen On Fri, May 27, 2016 at 04:15:47AM +0100, Kefeh Collins wrote: > good morning > please i have downloaded the freebsd source code but i cant fi= nd > any information on how to build it (in ubuntu 14.04) i will very much > appreciate any help >=20 > thanks in advance >=20 > On Sun, May 22, 2016 at 1:40 PM, Kefeh Collins > wrote: >=20 > > hello > > i am a second year computer science student, program in c and c++ and = am > > interested in contributing in operating system (kernel) directed projec= ts > > please i need guidance > > > > thanks in advance > > > _______________________________________________ > 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" --eb1XlXx8qH4KcAJ0 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXR70YAAoJEAMUWKVHj+KT6tQP/RfMrMGxms+4+LS9haGqtpVO 9OzRqO/n2fYKibJ2tVPIWUVjisADMcqUGaFBRzNaA0IrZc1DkX4w3c1Wc5dJGbJx /WNIlGsH6AhvcCp9+pZuauA3tx0yW5Zjbv1aixD1mCEH1Hw0T+3bMUArM9/Rnrj7 7ZkWLR089bDofWOxrXEg8lAtRjpypaAGao9+e3bWPLVhs7tgGrnHMbB/mCUQ8Bey OPIOkbtjeNeRJN5ymcGeFR1PL4+LbaRhYNPduLVxzdHoSp7sbY942H/apg0nYXQH Ymq7PFH/OHriv60oNjxbJZGeO3JNDKoyF+jojpLU3o9IUpnTo4QGOZ07ANQJjpkt AQ5bE0tY+DbW9c0QnXYaVxYlajmtLDjVv/Vtm+HaMYd8uWCE4AcGnyehOI5TlhtT Q4DQGVPj00m+XPhbCCsTlY/X/gSVlCZ9oGVm2/A9SHwSLHt8/jmv2oYuUXUIeCX7 y3hk2mXwJgmhQPloRHvHoyGQn6b7rGHZOv9v1jVQGQEupOD/vdszq+HGc2T6SKYn ALcQSQuOnM5xPE/Kzku3+n7BURRPcehAv/cT1xocaIjo/2HcrZeWlbjlHFpDTAhR iXdeeszTVN+z9dEz/dhp6UZ6JxZS1f1A3R+JcTQop/wT/IzcxgqZGffZ+hHS0kpt pnNvEe1OmLb1L3d9zHxz =QotE -----END PGP SIGNATURE----- --eb1XlXx8qH4KcAJ0-- From owner-freebsd-hackers@freebsd.org Fri May 27 03:21:22 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 93DC1B4C08E for ; Fri, 27 May 2016 03:21:22 +0000 (UTC) (envelope-from asomers@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 5AB6F1336 for ; Fri, 27 May 2016 03:21:22 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi0-x230.google.com with SMTP id w184so148190104oiw.2 for ; Thu, 26 May 2016 20:21:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=cx0SXvJQc91V7iX/dMRyR9faFBnUhEype61HkI6QZkI=; b=XlJm4kEq6FMEirICdW9Q2rRCjKWld0Fkd44i/w0BtJxNKPvw400+CuCwCn9xaOdtz2 OmjguzxCS1AWQY0Ei5oqaHTspy95slZD8SVx+eTa/tMoCRrtBEoUFabqSQ+mEY1tDGd0 zs88Ej8vd6BVtzQ0xtmLncn23Ai/AkEzRneMLqBRAcUPF++sMhJthepr52Hx2J8op9DX 37rW8OyMRx5f9kcPNQu80EZ1afnzTMfu8lWWRCCER0Bg0EejyKn7dCkjcpvZsF7fsTHu vbGVbrva7dbiSgsr5tbbG0Wf5M2tNFeIbmKl0vTEUCwOB6oKjG4KKc7bgARZEsSB4YsZ vSFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=cx0SXvJQc91V7iX/dMRyR9faFBnUhEype61HkI6QZkI=; b=Z9YEYgmz0GB/+DbpsczWFclh7GE3ljGREaTt249kljxN7Jd82w7VT4igyDagx/76CV TVHBtlNBP5epCGU8d+31jOLkGzleOM/D+iekeFsFZdU32W9eTKGaRfUQ9Ywe8H3qHQ3y mP4dC14N02iI9XNCzvAadFlaXMXfC9MF+KfdUscmqvJc/owHuiu1gSmUuhri+c93b0sC Gw8Xq9oez75sbRReb+LUIVV2VobX7lJ0gtqjxALmTXP5ZoDXEThALSsOR4UCc6Sb1/Xy JFCH3c+X8cZVmUxAh+FBM3y3tapBi3ND+MGKCxO7B2r0JZ/wcMfA11OUgy7BYWCCxi5k e2kQ== X-Gm-Message-State: ALyK8tJiTBXWcLJ3ZtVYCuZgFFaF6mlIquGk3EpAshylA7s3+QqkrsVVHSVkyPSOfksWwPEbTU6yt0KM7PGB6Q== MIME-Version: 1.0 X-Received: by 10.202.94.132 with SMTP id s126mr8171691oib.34.1464319281598; Thu, 26 May 2016 20:21:21 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.4.200 with HTTP; Thu, 26 May 2016 20:21:21 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 May 2016 21:21:21 -0600 X-Google-Sender-Auth: KSBTn5isYCfbRastH4xkGuP2tkI Message-ID: Subject: Re: contributing to open source From: Alan Somers To: Kefeh Collins Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 03:21:22 -0000 Only a very brave soul would attempt to build FreeBSD on Ubuntu. What you want to do is to download a FreeBSD VM image and boot that on Ubuntu using KVM or VirtualBox. Then you can rebuild FreeBSD from source. If you want to do FreeBSD development, I would start with the latest 11.0 snapshot. First just install it and follow all the instructions in the FreeBSD Handbook to get it configured as you like. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/11.0-CURRENT/amd64/20160518/ https://www.freebsd.org/doc/handbook/ -Alan On Thu, May 26, 2016 at 9:15 PM, Kefeh Collins wrote: > good morning > please i have downloaded the freebsd source code but i cant find > any information on how to build it (in ubuntu 14.04) i will very much > appreciate any help > > thanks in advance > > On Sun, May 22, 2016 at 1:40 PM, Kefeh Collins > wrote: > >> hello >> i am a second year computer science student, program in c and c++ and am >> interested in contributing in operating system (kernel) directed projects >> please i need guidance >> >> thanks in advance >> > _______________________________________________ > 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 May 27 14:09:24 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 22665B4BE33 for ; Fri, 27 May 2016 14:09:24 +0000 (UTC) (envelope-from mseqs@bsd.com.br) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 BD6511E91 for ; Fri, 27 May 2016 14:09:23 +0000 (UTC) (envelope-from mseqs@bsd.com.br) Received: by mail-wm0-x244.google.com with SMTP id e3so15246827wme.2 for ; Fri, 27 May 2016 07:09:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:date:message-id:subject:from:to; bh=oaNNllCrJFOrUoVxzJxcIlryxupKmUvIyXvhqVw4Wks=; b=Q1KlHxZUJZHbAKk6zI1fCRBN5KO7hfFM9H2z+/em3mo7Boom2W5HPQZFR4M3bVGr6b l2eC/44FoiDVYR4yKKHO5Igyrs/PTG2Hx9SY3nUgiJecKSQI3kbTz/GeHrqNvuGgWkLP GBwy5bLugUxiXdN0RYmaOQ2KIWg1yf36ZxwG0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=oaNNllCrJFOrUoVxzJxcIlryxupKmUvIyXvhqVw4Wks=; b=U3g9/TgdlqD5tzIZR882dEfNliQ/2M+kM8zYhdP8GKxsFcuHhuDTa42tPE2JLjuvHy o0YssXrDpmQyOu1pOBzwshXzj9TKgoxJtlPBc+RoQd6TgPd2xmxOlzJLVW+CYb9Z48mB S4AE3kJDDlycvQryfYE4qX+8qDu8rSVTbfbHDb1YIZke1OljnATdzMpXCZXELzgKZBgG TDqiyJcmwhXWxQ9dAMbQ7lLQv2W+MlnrwJx51w68syrrsTl6tjYCk24H7AwsowKcKQPk B8n1Ntubykoi2vd1A23KRSJxw0LF+LN0r6v3mH+55I/iydu0MxFhLEjk97FoXPyt3sEb ovvg== X-Gm-Message-State: ALyK8tJdKthFs0otfxKHAZ4BYKiZFxDXWtDrB9JvKvsasUkz9l2skos95vFur8ZjN27O3SV1GT4nqIeCtGKg/w== MIME-Version: 1.0 X-Received: by 10.194.86.200 with SMTP id r8mr14575296wjz.158.1464358162024; Fri, 27 May 2016 07:09:22 -0700 (PDT) Received: by 10.194.30.101 with HTTP; Fri, 27 May 2016 07:09:21 -0700 (PDT) Date: Fri, 27 May 2016 11:09:21 -0300 Message-ID: Subject: UEFI boot problem From: Rafael Rodrigues Nakano To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 14:09:24 -0000 Hello, I am trying to reinstall my FreeBSD in UEFI mode, primarly because I dual-boot with Windows 10 and for GPT partioned disks it must be UEFI, I need more than 4 partitions for both operating systems. So, the problem is, I got Windows 10, Ubuntu Linux and Debian Linux to boot (from USB and from DVD) on UEFI mode, also installed ubuntu this way to make sure its not my computer's fault or USB stick problem (also DVD), but when I try to boot from FreeBSD (I'm trying 11-CURRENT, but fails exactly the same way -RELEASE does. In my BIOS boot screen I select "UEFI: SanDisk USB ..." and it shows the FreeBSD boot screen (1: MultiUser [Enter] etc, with the beastie logo), and whatever option I try (multi or single user) it fails the same. The pc simply hangs with a message "UEFI FrameBuffer information", something like that with some hex values, but no response at all. Keyboard is dead, mouse is dead, on/off button does nothing, need force shutdown. I tried with dd (on both Linux and in a FreeBSD bios installation), tried Linux's unetbootin, tried Rufus, Unetbootin, USI on Windows and none works. What could be wrong? Thanks in advance From owner-freebsd-hackers@freebsd.org Fri May 27 22:31: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 DE060B4D561 for ; Fri, 27 May 2016 22:31:49 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id BC23B11F4 for ; Fri, 27 May 2016 22:31:49 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 1B51415F8; Fri, 27 May 2016 22:31:48 +0000 (UTC) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <27294407-6B25-418E-85BE-14AAEE75D7D9@metricspace.net> Cc: freebsd-hackers@freebsd.org X-Mailer: iPad Mail (13D15) From: Eric McCorkle Subject: Re: UEFI boot problem Date: Fri, 27 May 2016 18:31:48 -0400 To: Rafael Rodrigues Nakano X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 22:31:50 -0000 What terminal driver are you using? This sounds like you don't have efifb i= nstalled, and your graphics card isn't supported. > On May 27, 2016, at 10:09, Rafael Rodrigues Nakano wrot= e: >=20 > Hello, >=20 > I am trying to reinstall my FreeBSD in UEFI mode, primarly because I > dual-boot with Windows 10 and for GPT partioned disks it must be UEFI, I > need more than 4 partitions for both operating systems. >=20 > So, the problem is, I got Windows 10, Ubuntu Linux and Debian Linux to boo= t > (from USB and from DVD) on UEFI mode, also installed ubuntu this way to > make sure its not my computer's fault or USB stick problem (also DVD), but= > when I try to boot from FreeBSD (I'm trying 11-CURRENT, but fails exactly > the same way -RELEASE does. >=20 > In my BIOS boot screen I select "UEFI: SanDisk USB ..." and it shows the > FreeBSD boot screen (1: MultiUser [Enter] etc, with the beastie logo), and= > whatever option I try (multi or single user) it fails the same. The pc > simply hangs with a message "UEFI FrameBuffer information", something like= > that with some hex values, but no response at all. Keyboard is dead, mouse= > is dead, on/off button does nothing, need force shutdown. >=20 > I tried with dd (on both Linux and in a FreeBSD bios installation), tried > Linux's unetbootin, tried Rufus, Unetbootin, USI on Windows and none works= . > What could be wrong? Thanks in advance > _______________________________________________ > 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 May 27 23:39: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 E0A49B4D2F7 for ; Fri, 27 May 2016 23:39:58 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id B476F132E for ; Fri, 27 May 2016 23:39:58 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id E90F7160A for ; Fri, 27 May 2016 23:39:57 +0000 (UTC) Subject: EFI GELI support ready for testers From: Eric McCorkle Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (13D15) Message-Id: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> Date: Fri, 27 May 2016 19:39:57 -0400 To: "freebsd-hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 23:39:59 -0000 I am pleased to announce that my work to add support for GELI in the EFI boo= t loader (as well as perform more general refactoring) is now ready for test= ing. I am able to successfully detect multiple GELI partitions in boot1 and= pass the keys into the kernel. My work can be found here: https://github.com/emc2/freebsd/tree/geli_efi Also of note is the efize branch, which I posted about two weeks ago. I hav= e not yet merged this with master, but I will begin doing so on a regular sc= hedule. I have left the LOADER_PATH variable as "/boot/loader.tst" If you plan on t= esting this, I *strongly* recommend the following procedure: * Be aware that because of the nature of this patch, A PROBLEM COULD RESULT I= N YOUR FILES BEING INACCESSIBLE! Take necessary precautions to protect your= data, read carefully, ask before you leap, and proceed with caution! * Read and understand thoroughly the basics of EFI and the FreeBSD boot arch= itecture before you do anything. * Install an EFI shell program on your ESP. * Install the modified boot1 to something like /efi/boot/bootx64.tst on your= ESP * Install the modified loader to /boot/loader.tst * Try creating an auxiliary encrypted partition containing unimportant data f= irst * After this, try a minimal root image on the auxiliary partition. * Only move to an encrypted root once you have tried the above steps, and BA= CK UP YOUR DATA FIRST. I have personally done the following tests on this: * Detect ZFS filesystem at boot (ZFS checksum verification gives a high leve= l of certainty that decryption is correct) * Load a kernel and multiple modules from a ZFS partition and boot them. * AES CBC and XTS encryption (see notes on limited GELI feature support) * Multiple encrypted partitions with different keys, both shared and differe= nt pass phrases. * Ensure that keys are passed into the kernel properly. Normally I would convert my own system and wait a week or two; however, the g= raphics update 4.6 testing is going on, and I want to make sure my hardware (= purism laptop) is accounted for in that. Two experimental patches is just t= oo much branch management (especially when a misstep would effectively destr= oy all my files!) Due to the scope of this changeset and the material risks associated with it= , I am NOT recommending that it be considered for the 11 release. It's just= too close to be adding something like this. A note on GELI feature support: the current GELI boot code does not support a= ll features. Only AES encryption is supported, only 512 block sizes are sup= ported, authentication is not supported, and key files are not supported. (= These are limitations inherited from the GELI boot code, and my refactoring a= may make them easier to address). Make sure not to use an unsupported mode= ! The contents of this work break down into roughly four areas, which apply in= the following order: EFI Refactoring: see my earlier mail for full details. The abridged version= is that the EFI boot1 and loader are refactored to make much greater use of= the EFI API. Filesystems are now managed by attaching an EFI_SIMPLE_FILE_S= YSTEM_PROTOCOL interface. The filesystem drivers in loader have been replac= ed with a single driver that talks through this interface. This allows load= er to use any filesystem driver installed by itself, boot1 or another tool, o= r the native firmware. This refactoring also puts both boot1 and loader on a= common code base driver-wise, eliminating the duplication that previously e= xisted. I was unable to move the efipart and backend filesystem drivers ful= ly into the EFI driver model, however, as the bcache code is fundamental bui= lt on the model of static detection. Boot Crypto: this is a small refactoring that moves crypto code out of the e= xisting geliboot code and into a common framework. This should make the bus= iness of adding new ciphers easier. A difficulty with this is resolving the= need for building a 32-bit version of the library for legacy BIOS geliboot,= as well as a native version for EFI. I currently resolve this by building a= static library for EFI, and including the source files in the BIOS make fil= es. If someone with a better handle on the build system could figure out ho= w to build both a 32-bit and native version of the library, I'd be grateful.= GELI EFI driver: this is simply an EFI driver that detects GELI partitions a= nd creates a new device handle with a EFI_BLOCK_IO_PROTOCOL interface implem= enting access to the partition. This driver, as well as the kernel KMS driv= er could be exported from the FreeBSD sources and contributed to the likes o= f GRUB without much trouble. Kernel key intake framework: this adds a kernel interface (and one that will= likely be imminently useful, at the very least to the BIOS GELI support), s= o it warrants further discussion: * On the boot/loader side, there is a "kernel injector KMS" driver which cre= ates a device handle that implements the EFI_KMS_PROTOCOL. The GELI driver a= ttempts to obtain the handle supporting this interface, and uses it to repor= t both GELI pass phrases as well as the raw keys as it discovers them. It a= lso uses the handle to obtain previous keys and passphrases, and tries the b= efore asking for a new passphrase. * The kernel injector KMS uses the register client function to inform the KM= S of a kernel. This is done in the same code path that adds metadata to the= kernel image (the existing metadata is how the kernel gets the EFI frame bu= ffer info, among other things) * On the kernel side, a new kind of metadata is added for the key intake buf= fer. A simple interface for accessing the key intake buffer is presented in= crypto/intake.h * The GELI kernel-side code has been modified to check the intake buffer whe= n detecting GELI partitions at boot before asking for a passphrase. * The existing environment variable used by the BIOS GELI support has been l= eft alone. However, it would probably be a good idea to move to the key int= ake buffer, as it is more featureful and marginally more secure. A guiding principle behind this design was the desire to make it easy to add= support for hardware-based key storage options. This is why I used KMS int= erfaces on the EFI side. I also designed it to support a wider range of key= s than what GELI alone needed, intending for it to become a common interface= for communicating keys from the loader to the kernel. Let me know if there are any questions about this work. I would prefer that= it undergo a period of testing before moving towards commit (which is neces= sary anyway in light of the upcoming release).= From owner-freebsd-hackers@freebsd.org Fri May 27 23:48: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 5600CB4D916 for ; Fri, 27 May 2016 23:48:18 +0000 (UTC) (envelope-from mseqs@bsd.com.br) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::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 EE9F51C83 for ; Fri, 27 May 2016 23:48:17 +0000 (UTC) (envelope-from mseqs@bsd.com.br) Received: by mail-wm0-x22e.google.com with SMTP id a136so11288597wme.0 for ; Fri, 27 May 2016 16:48:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=KvBU9JdILXK1DJE65taWH5GNg8AXbGWuIkqa/TWvJyA=; b=CT1em7ckASRhtyqnSM+JxyJnrepcWA6deXRRTs4hsNNEEhuC+6QocOyQr37D7mq6eH mbiILZN/DMXqsP6RhHUMUy4yR9U2d84B3w2jh/KqJLgx8f3X0PZByqJvwZcrmdY5aik/ CxaNK51GW+u0AumW7dQZFp+xkSV3Ll2DDXCpA= 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; bh=KvBU9JdILXK1DJE65taWH5GNg8AXbGWuIkqa/TWvJyA=; b=aDqHgw5RXIxdwaHnHxQz1FLigl9gZDiP4m0212ZVqHpCdIZ4RMB+xXjsLTK3O+YjOM bZQB7u2YZXV6AS/QgPVLmF9dI0UudfqGONRkrLNoMxIes9LtvxGQBtSrQNDwYDhd4//u /s14/3D6w+Pog5QhwL7G65v/4vMZ6KJ94uxxflrA/0y6s/UmCuO573sTTau71zVeFjQn pd/EEFBzEQ5y3027EYki3BsUMGbV0EhwTG7VU9fddlNyYK5a47Fg/eRPWO5HmZedCIqS 2gIOWfUDb2bzlnya80i3Q1awyArM8c70boFyaCSwhrHODukh1bHCqkOrXIuUvcLWryIf q9KA== X-Gm-Message-State: ALyK8tJjjqvdCfkQyS6hXr0tlyIsiGKYik7CrkSCQhme2VZ6AmhG3VVZGNyDGATPUi1pKbnFeUB/JJxZt4+ykw== MIME-Version: 1.0 X-Received: by 10.28.15.79 with SMTP id 76mr983162wmp.53.1464392895273; Fri, 27 May 2016 16:48:15 -0700 (PDT) Received: by 10.194.30.101 with HTTP; Fri, 27 May 2016 16:48:15 -0700 (PDT) In-Reply-To: References: <27294407-6B25-418E-85BE-14AAEE75D7D9@metricspace.net> Date: Fri, 27 May 2016 20:48:15 -0300 Message-ID: Subject: Fwd: UEFI boot problem From: Rafael Rodrigues Nakano To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 23:48:18 -0000 I emailed at work so I could not provide more detailed information at the moment. I got a picture from the screen booting, see the link below. The system isn't installed yet, so I don't know which packages are installed on the live installation media. Picture from the problem: http://imgur.com/WHMsVPk From owner-freebsd-hackers@freebsd.org Sat May 28 00:07:09 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 05F8CB4A5B6 for ; Sat, 28 May 2016 00:07:09 +0000 (UTC) (envelope-from mseqs@bsd.com.br) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::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 9339C1151 for ; Sat, 28 May 2016 00:07:08 +0000 (UTC) (envelope-from mseqs@bsd.com.br) Received: by mail-wm0-x234.google.com with SMTP id a136so11622735wme.0 for ; Fri, 27 May 2016 17:07:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=nQvm1d8I83Jg6xb9VS+jCUP6lXopjPkLQmnbQ80LJck=; b=TOp//ENdRbpVO2dMKiLc+IJ/Pn80wv8NzSWKgylrKcDqNrJ1khoUWtOS5eklwQh5HG r7aDbjh+nL8/SQKzg770kbng7qImBda6yCwIVqXKOyj9xq8K9A9cnZQxv9+iMS+Pgf9w t4CjEKAXTMx2KWM2Bi4UIiSCDnvAUvNp5U+FQ= 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; bh=nQvm1d8I83Jg6xb9VS+jCUP6lXopjPkLQmnbQ80LJck=; b=i7Thb2eaPUS9LGs9Bfp1yUlpjoPSBBdqdd0KnDbFhqqF2XQwEn+oY15rud5Ydft8Pp CJ01LjuC7+c9mBGAD76ZXlYib9QnXt9boNY/shqFnk2I3eJDifgGYhlQ4Z632nYmelAf 3l5wZ7DdwP9xSy/9x7QOJispSSguDXIdyg0r3PqCReltWAPg3ccWjPWM2F3Ho1dqnKoB sHgootEvCh0uMpPFg+Ml57XY+RvApygLOAlt2alcqJ86aQBiqLn+4KzA9AFpXounqzwe qrJ7vxOymUKh89b8FwKBiTqOgHdzimHcj+g3kzge41XAtVxa2/B3s4hZ9BoL35H46l56 I1Nw== X-Gm-Message-State: ALyK8tIyiZxyAK6hApEJZdHpF14mOL96g3cs1nNBqTh6ieGskXByBqEX9/NMJybPp1pudoiJrOFmHvFow/ncAQ== MIME-Version: 1.0 X-Received: by 10.28.10.10 with SMTP id 10mr1088827wmk.102.1464394027088; Fri, 27 May 2016 17:07:07 -0700 (PDT) Received: by 10.194.30.101 with HTTP; Fri, 27 May 2016 17:07:06 -0700 (PDT) Received: by 10.194.30.101 with HTTP; Fri, 27 May 2016 17:07:06 -0700 (PDT) In-Reply-To: References: <27294407-6B25-418E-85BE-14AAEE75D7D9@metricspace.net> Date: Fri, 27 May 2016 21:07:06 -0300 Message-ID: Subject: UEFI boot problem From: Rafael Rodrigues Nakano To: Eric McCorkle , freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 00:07:09 -0000 >From BIOS mode it boots fine, which is pretty strange. How can I load it from the loader prompt at the boot screen? From owner-freebsd-hackers@freebsd.org Sat May 28 00:10: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 5023CB4A69E for ; Sat, 28 May 2016 00:10:50 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (207-172-209-83.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.83]) by mx1.freebsd.org (Postfix) with ESMTP id 22DB712E1 for ; Sat, 28 May 2016 00:10:49 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:94c9:651d:7312:89cd] (unknown [IPv6:2001:470:1f11:617:94c9:651d:7312:89cd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 7EA951651; Sat, 28 May 2016 00:10:43 +0000 (UTC) User-Agent: K-9 Mail for Android In-Reply-To: References: <27294407-6B25-418E-85BE-14AAEE75D7D9@metricspace.net> MIME-Version: 1.0 Subject: Re: UEFI boot problem From: Eric McCorkle Date: Fri, 27 May 2016 20:10:41 -0400 To: Rafael Rodrigues Nakano ,freebsd-hackers@freebsd.org Message-ID: <7B61CFE8-59ED-4DE8-9F13-2BA19BE83EB5@metricspace.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 00:10:50 -0000 Well, if you can boot from bios, I'd say just install the system, make sure you leave room for the ESP, and then build a kernel and make sure it has the efifb driver built in. On May 27, 2016 8:07:06 PM EDT, Rafael Rodrigues Nakano wrote: >From BIOS mode it boots fine, which is pretty strange. How can I load >it >from the loader prompt at the boot screen? -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-hackers@freebsd.org Sat May 28 03:30:44 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 432E6B4D301 for ; Sat, 28 May 2016 03:30:44 +0000 (UTC) (envelope-from kefehcollins@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 0F1A719D9 for ; Sat, 28 May 2016 03:30:44 +0000 (UTC) (envelope-from kefehcollins@gmail.com) Received: by mail-io0-x236.google.com with SMTP id f8so82502676ioe.3 for ; Fri, 27 May 2016 20:30:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=mEQAR/72zKK9RrABqtGOUClCi7pz1b/LtkueZGWwFKg=; b=jUKrn8COfFMRSH7j5SCpzdpIWqfmbliewkYaUlNLLHsFft7FsDNYZi6Y+jSVo30PrE F+Ffq7x4fTuHM3EWe4qU16/7qs5/5548e6PobUn/4wd29UFsjJqpRwRhxcZiiQXRVbyE cNLwqRxJNDRmhygobqNdUGzt5dJOP/i1lWVIKSR38sau2/4LBL9GkVm3gQOwZ9y5yxGf CuuRzslx4AYfeudU78ntKH3fDb+cJDAbWzmhChNk3UUkCcXODNM+aJ/Dw7ziH+fWSVhy ey2JivpF3PTv1maIH1VXpqLq9h0eCOIHsq+c/WdNk7g94UpT1P4QhDoaMsvlRvlNdcKC dqsw== 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; bh=mEQAR/72zKK9RrABqtGOUClCi7pz1b/LtkueZGWwFKg=; b=loTyK/OWUYYqSpeH6Zh+o56e0g7kIbhR1dpRuaag7TXTqRczscSI9BNkF1+DGICHOk at36F+0NobGQvMtLVoIOYSG2baWoGWOv3FmzIJavWTDu9GrGO5tR9Z59l9vOYwDiVxUs R+AmR41J1xsBKMIN1Zb5O+LFexaAQGALfcsfvHMCNwZF6Kqy333RXLVScdlXr2XHWE44 KaB2mbM6/9ryr+eDYUhH3BnNuUkUxN9kT8m6o/tdYXM2kte2MaGbT4LqpXZQzcPUPtcl GbPYizxcN+U4+9coR/n/SB2ewfTEhzNGdcHu+j7vR8QmWxxW8+iblSwGE3fwNrmAQ1kg BWhg== X-Gm-Message-State: ALyK8tKq9cu9j+eP6/fGPj83VbybnZpLwoZsKk7Jg+oNZ0ydBff9dYYhleRGgmmNfCSFRKl9nrRZ6YMiUFtedQ== MIME-Version: 1.0 X-Received: by 10.107.138.139 with SMTP id c11mr17698413ioj.143.1464406243453; Fri, 27 May 2016 20:30:43 -0700 (PDT) Received: by 10.64.228.70 with HTTP; Fri, 27 May 2016 20:30:43 -0700 (PDT) In-Reply-To: References: Date: Sat, 28 May 2016 04:30:43 +0100 Message-ID: Subject: Re: contributing to open source From: Kefeh Collins To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 03:30:44 -0000 hello please i need help installing freebsd using the virtual box actually am at my concluding phase but the problem is i downloaded a VM image with the .vhd.xz as well as the .raw.xz extensions but i cant unzip it and i cant locate it when choosing a virtual optical disk file any help is very much appreciated On Sun, May 22, 2016 at 1:40 PM, Kefeh Collins wrote: > hello > i am a second year computer science student, program in c and c++ and am > interested in contributing in operating system (kernel) directed projects > please i need guidance > > thanks in advance > From owner-freebsd-hackers@freebsd.org Sat May 28 03:37: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 7FF94B4D587 for ; Sat, 28 May 2016 03:37:03 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 4FE62104C for ; Sat, 28 May 2016 03:37:02 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 0B540D960 for ; Sat, 28 May 2016 03:37:02 +0000 (UTC) Subject: Re: contributing to open source To: freebsd-hackers@freebsd.org References: From: Allan Jude Message-ID: <53164a51-5389-7ca5-b40f-d58902fffe87@freebsd.org> Date: Fri, 27 May 2016 23:37:01 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 03:37:03 -0000 On 2016-05-27 23:30, Kefeh Collins wrote: > hello > please i need help installing freebsd using the virtual box > actually am at my concluding phase but the problem is i downloaded a VM > image with the .vhd.xz as well as the .raw.xz extensions > but i cant unzip it and i cant locate it when choosing a virtual > optical disk file > any help is very much appreciated > > On Sun, May 22, 2016 at 1:40 PM, Kefeh Collins > wrote: > >> hello >> i am a second year computer science student, program in c and c++ and am >> interested in contributing in operating system (kernel) directed projects >> please i need guidance >> >> thanks in advance >> > _______________________________________________ > 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" > To unzip it, type: unxz imagename.vhd.xz Then you will have a .vhd file and be able to use it normally. .vhd files are for Microsoft HyperV, so it is likely not the image you want. VirtualBox and VMware uses the .vmdk file -- Allan Jude From owner-freebsd-hackers@freebsd.org Sat May 28 08:25: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 1E219B4D722 for ; Sat, 28 May 2016 08:25:21 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::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 CC07B1802 for ; Sat, 28 May 2016 08:25:19 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-yw0-x22a.google.com with SMTP id x189so125484301ywe.3 for ; Sat, 28 May 2016 01:25:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=3aCshykFSDFDv+UP8CMfU+nVH3VOXrtdWx8H3Q2Z1AY=; b=HEAtPe+YeQjPZFdDgsU8RUXIUBTl2TQ0wDC3s2G5lVNEYdTXqWI05XQmC0sq5IV/zS 0OYbQF7rLT5z7NlZUY4CiAzUHBpepcaJhAe2pFNyKc+mM8r0LuelpM4ImnY61Pc2iJgb QrOu+3YdLiUh068giyETFutTuZjvyhQ8bB5jx4eZbIjqSGQqgLJ0U8rzBbimaXR1fBcF plNLvUAKefl2Go1F7iWcu1Bhf/FHFadU9YkoRg8LuTxmmGIDQ2UtAXW79OE++fX3BFb0 eU9S/EKDRDS0/FGVt8NNnXiuXXPx9P5ynioMpbdqii+8CTqxf9jPR38eliImrKs/Tk0p D+ug== 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; bh=3aCshykFSDFDv+UP8CMfU+nVH3VOXrtdWx8H3Q2Z1AY=; b=VfgRaPeXa0kDOLXGhi/Ucv1SiWQmLrxSRe0Wv1O/C7WihTZVu0/AglYUtllbnzUcGz LTac91BBmtPRLdEAppfcGlJqXfy26/Qpt2ejRI2f9WtVt8G4d0ok2ed++eefiMFsBDoP O8OXsDNKM3TKZtQdcaKSHWACjax+LFalCgXVLDVjSdz43eCn6CMeZxpeQ2ATdkryRw35 5/TpGrLHyFxyrpLREwmEN4LTGxdslt+Yv4EFKMqjlkSNquaTrelPfmRWP2EfmmvfWCIN C28tyop0sVeccI1b/WX54V/XXs84I7pOID9zP/1RxMF48Ety9JeCGz4JgA0qZxNWVJdr u2eA== X-Gm-Message-State: ALyK8tL3QYYFMBDkJB1aMNF11xjb6xGrgVmCdderPdxVD09EHO8wuBYq8PDeY+RdEt3UemLSBv54rviToap6Dg== MIME-Version: 1.0 X-Received: by 10.13.218.131 with SMTP id c125mr11255166ywe.310.1464423918987; Sat, 28 May 2016 01:25:18 -0700 (PDT) Received: by 10.13.201.199 with HTTP; Sat, 28 May 2016 01:25:18 -0700 (PDT) In-Reply-To: <53164a51-5389-7ca5-b40f-d58902fffe87@freebsd.org> References: <53164a51-5389-7ca5-b40f-d58902fffe87@freebsd.org> Date: Sat, 28 May 2016 10:25:18 +0200 Message-ID: Subject: Re: contributing to open source From: Ed Schouten To: Allan Jude Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 08:25:21 -0000 2016-05-28 5:37 GMT+02:00 Allan Jude : > To unzip it, type: > unxz imagename.vhd.xz Exactly! If you're on Windows, I think you can use 7-zip (http://www.7-zip.org/) to decompress the images. -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 From owner-freebsd-hackers@freebsd.org Sat May 28 08:37: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 2A3E7B4D986 for ; Sat, 28 May 2016 08:37:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 B9F871D7F for ; Sat, 28 May 2016 08:37:02 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u4S8avaY058022 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 28 May 2016 11:36:57 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u4S8avaY058022 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u4S8avGs058021; Sat, 28 May 2016 11:36:57 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 28 May 2016 11:36:57 +0300 From: Konstantin Belousov To: Eric McCorkle Cc: "freebsd-hackers@freebsd.org" Subject: Re: EFI GELI support ready for testers Message-ID: <20160528083656.GT38613@kib.kiev.ua> References: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 08:37:03 -0000 On Fri, May 27, 2016 at 07:39:57PM -0400, Eric McCorkle wrote: > I am pleased to announce that my work to add support for GELI in the EFI boot loader (as well as perform more general refactoring) is now ready for testing. I am able to successfully detect multiple GELI partitions in boot1 and pass the keys into the kernel. Can somebody explain in which way this is useful ? Same question for the GELI code for non-EFI loader. BIOS cannot read raw data from the encrypted partition, so you need either old boot or the loader and some additional data on EFI boot partition anyway. Features adds significant amount of code, which must be maintained in parallel with the kernel code. From owner-freebsd-hackers@freebsd.org Sat May 28 13:37:32 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 8B56BB4E839 for ; Sat, 28 May 2016 13:37:32 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (207-172-209-83.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.83]) by mx1.freebsd.org (Postfix) with ESMTP id 69CE517FC for ; Sat, 28 May 2016 13:37:32 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 620431753; Sat, 28 May 2016 13:37:30 +0000 (UTC) References: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> <20160528083656.GT38613@kib.kiev.ua> Mime-Version: 1.0 (1.0) In-Reply-To: <20160528083656.GT38613@kib.kiev.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <10841E12-488A-4B96-BD1D-832A5B3F7471@metricspace.net> Cc: "freebsd-hackers@freebsd.org" X-Mailer: iPad Mail (13D15) From: Eric McCorkle Subject: Re: EFI GELI support ready for testers Date: Sat, 28 May 2016 09:37:29 -0400 To: Konstantin Belousov X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 13:37:32 -0000 Full-disk encryption is a powerful security feature, and one which is availa= ble in one form or another in every major competing OS. It is a requirement= for data protection in many organizations, and something that many individu= als desire to help protect their data. In EFI, there is an EFI System Partition (ESP) which is expected to be forma= tted with msdosfs. This contains the boot1 program. This must be unencrypt= ed in order for EFI to be able to read it (unless you do something fancy wit= h coreboot or whatever). That is the only thing that needs to live on the E= SP, and the only thing that needs to be stored as plaintext. The rest of th= e system past that point can reside on encrypted partitions. Without suppor= t for GELI in the boot1/loader code, you have to keep part of the system une= ncrypted. Making it so that only boot1 has to be stored as plaintext dramatically redu= ces the attack surface. It can also be combined with EFI secure boot to cre= ate a powerful tamper-resistance scheme, wherein a per-machine private key i= s stored on the encrypted disk and used to sign boot1. This prevents an att= acker from modifying boot1, as they would need the signing key to do that, b= ut they can't get it without decrypting the disk. I'll also mention that my changes actually delete quite a bit of code and re= move the boot1-specific filesystem backends, so that boot1 and loader now us= e the same filesystem and backend code. > On May 28, 2016, at 04:36, Konstantin Belousov wrote= : >=20 >> On Fri, May 27, 2016 at 07:39:57PM -0400, Eric McCorkle wrote: >> I am pleased to announce that my work to add support for GELI in the EFI b= oot loader (as well as perform more general refactoring) is now ready for te= sting. I am able to successfully detect multiple GELI partitions in boot1 a= nd pass the keys into the kernel. >=20 > Can somebody explain in which way this is useful ? > Same question for the GELI code for non-EFI loader. >=20 > BIOS cannot read raw data from the encrypted partition, so you need > either old boot or the loader and some additional data on EFI boot > partition anyway. >=20 > Features adds significant amount of code, which must be maintained in > parallel with the kernel code. > _______________________________________________ > 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 Sat May 28 14:27:42 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 F000AB4D314 for ; Sat, 28 May 2016 14:27:42 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id D637F111D for ; Sat, 28 May 2016 14:27:42 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 6010BD095 for ; Sat, 28 May 2016 14:27:41 +0000 (UTC) Subject: Re: EFI GELI support ready for testers To: freebsd-hackers@freebsd.org References: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> <20160528083656.GT38613@kib.kiev.ua> From: Allan Jude Message-ID: Date: Sat, 28 May 2016 10:27:40 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <20160528083656.GT38613@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 14:27:43 -0000 On 2016-05-28 04:36, Konstantin Belousov wrote: > On Fri, May 27, 2016 at 07:39:57PM -0400, Eric McCorkle wrote: >> I am pleased to announce that my work to add support for GELI in the EFI boot loader (as well as perform more general refactoring) is now ready for testing. I am able to successfully detect multiple GELI partitions in boot1 and pass the keys into the kernel. > > Can somebody explain in which way this is useful ? > Same question for the GELI code for non-EFI loader. > > BIOS cannot read raw data from the encrypted partition, so you need > either old boot or the loader and some additional data on EFI boot > partition anyway. > > Features adds significant amount of code, which must be maintained in > parallel with the kernel code. > _______________________________________________ > 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" > The motivation for my work (GELI in boot2 and loader for non-EFI boot) was supporting ZFS boot environments. Previously, when you use GELI you needed to have two ZFS pools, one for an unencrypted /boot and one for the encrypted / This breaks ZFS boot environments, since a snapshot of the root file system won't include the correct kernel etc. The final version of my geliboot took an extra effort to reuse the AES code from sys/crypto/rijndael and sys/opencrypto and GELI directly from sys/geom/eli to avoid maintaining a separate copy of that code in sys/boot Hopefully the work I did to make sys/opencrypto and sys/geom/eli more reusable outside of the kernel will make it easier for Eric to do the same for the EFI version. The motivation for the EFI version is the same, ZFS boot environments, plus the obvious security advantages of having the kernel stored encrypted rather than not. -- Allan Jude From owner-freebsd-hackers@freebsd.org Sat May 28 15:23:42 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 D0A2DB4E456 for ; Sat, 28 May 2016 15:23:42 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id AE2D110CB; Sat, 28 May 2016 15:23:42 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 331611776; Sat, 28 May 2016 15:23:42 +0000 (UTC) References: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> <20160528083656.GT38613@kib.kiev.ua> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Cc: freebsd-hackers@freebsd.org X-Mailer: iPad Mail (13D15) From: Eric McCorkle Subject: Re: EFI GELI support ready for testers Date: Sat, 28 May 2016 11:23:41 -0400 To: Allan Jude X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 15:23:42 -0000 > On May 28, 2016, at 10:27, Allan Jude wrote: >=20 > The final version of my geliboot took an extra effort to reuse the AES > code from sys/crypto/rijndael and sys/opencrypto and GELI directly from > sys/geom/eli to avoid maintaining a separate copy of that code in sys/boot= >=20 > Hopefully the work I did to make sys/opencrypto and sys/geom/eli more > reusable outside of the kernel will make it easier for Eric to do the > same for the EFI version. It did indeed make things easier, though I think there is potential for work= to be done on the crypto framework. It looks like the crypto framework has= kind of accumulated code over time from different sources and has become so= mewhat disorganized. There seem to be two codebases (crypto and opencrypto),= and multiple differing implementations for some ciphers. I ran into this w= hen trying to figure out how to add Camellia support. There's a usable inte= rface for AES CBC/XTS, but not Camellia CBC. There are also some insecure c= iphers (DES, RC4, etc) in there, some more modern ciphers (like chacha20) ar= e missing, and it's possible to implement ciphers other than AES using AESNI= /AVX instructions to achieve hardware acceleration. It also ought to be simpler to share crypto code between kernel, boot, and u= serland, imo. In theory, one could have a single library (with multiple com= pilations for different ABIs) that could be statically linked into the kerne= l and boot loaders, and also installed in to the base OS. I'm not sure if there's any plans for crypto, but it might be worth a discus= sion. >=20 > The motivation for the EFI version is the same, ZFS boot environments, > plus the obvious security advantages of having the kernel stored > encrypted rather than not. >=20 The ability to have a single ZFS filesystem is indeed a motivator for the EFI= work. I forgot to mention it because my personal motivations are strongly f= ocused on security and tamper-resistance.= From owner-freebsd-hackers@freebsd.org Sat May 28 16:41:07 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 600D3B4E507 for ; Sat, 28 May 2016 16:41:07 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [194.1.144.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EA8B61752 for ; Sat, 28 May 2016 16:41:06 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.14.9) with ESMTPS id u4SGd1KZ086988 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 28 May 2016 18:39:01 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from laptop.wojtek.intra (localhost [127.0.0.1]) by laptop.wojtek.intra (8.14.9/8.14.9) with ESMTP id u4SGcwNN000986; Sat, 28 May 2016 18:38:58 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by laptop.wojtek.intra (8.14.9/8.14.9/Submit) with ESMTP id u4SGcq78000983; Sat, 28 May 2016 18:38:52 +0200 (CEST) (envelope-from wojtek@puchar.net) X-Authentication-Warning: laptop.wojtek.intra: wojtek owned process doing -bs Date: Sat, 28 May 2016 18:38:52 +0200 (CEST) From: Wojciech Puchar X-X-Sender: wojtek@laptop.wojtek.intra To: Konstantin Belousov cc: Eric McCorkle , "freebsd-hackers@freebsd.org" Subject: Re: EFI GELI support ready for testers In-Reply-To: <20160528083656.GT38613@kib.kiev.ua> Message-ID: References: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> <20160528083656.GT38613@kib.kiev.ua> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sat, 28 May 2016 18:39:01 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 16:41:07 -0000 >> I am pleased to announce that my work to add support for GELI in the EFI boot loader (as well as perform more general refactoring) is now ready for testing. I am able to successfully detect multiple GELI partitions in boot1 and pass the keys into the kernel. > > Can somebody explain in which way this is useful ? > Same question for the GELI code for non-EFI loader. No idea. simply keep /boot in separate partition no matter if booting with EFI or not. that's all. From owner-freebsd-hackers@freebsd.org Sat May 28 17:24: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 D9BFAB4D9C0 for ; Sat, 28 May 2016 17:24:56 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::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 A03031E7B; Sat, 28 May 2016 17:24:56 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi0-x22d.google.com with SMTP id w184so210842777oiw.2; Sat, 28 May 2016 10:24:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=f7CGhNaHBovkVVWb8IQiBwA8AY85iar9o19jiU9uexE=; b=oXR9P8w6+x27f/X9abJV2dJnPHLdyw1rmCIBmuEb/kxVdfFrL0EstooM+vpJRQtDGn ZJM+ItA8sqzDJcyfFpFldnCVtMfUFwWJ5vhAOjvFLqSnX7GoFgFn5Ef1g+ZlNKwpEPef U4gAUZt3yC1HJhsF+8BBnObQtN7pn/SGnumfADDY5CoI36+J1y7VT/OEbAnN7zk3rQIW VnqDCxv9vo/vOESqazfv7FpnpkQVu39e4oLmrKtIJC72swNzr0N4h2/1VtDKvbeMAnGn 2LWWItfwDg+nyrLNgJEsYryWvHv7DEtIWOdkJAvRCoFid0QRDmYgthvGQcYbkRiyS5B5 dvGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=f7CGhNaHBovkVVWb8IQiBwA8AY85iar9o19jiU9uexE=; b=ehzW/ZRefL8PvXtYmyXqUtZuHyu8xdtHk/Eh0f/ZllT/m6hhxgihY2f/MTKCAeGZuC duDkUFlku4J13y2dHU+Jc0MDQj1Q37upvPbxBm0f74nExLCNJjh5KH0FfEoUI6xdFOtz X4Nv2vcR76ecS8sC3qrrE133nJmlOtFItRTFpIE0qcB7mxmf/B2QhLQ1fh9Imq6qe7/T N/UG/kky2GrJ5+eIHcA4JqF0l+ifs88R1D2HHVDM8B6ykIL+FVfpBcvdn7aC5/rkHp7e uHfP10HeHEMP+tai32vUJ0f0sL4yl4IfHBrW6orWNf8hJgHC3amIX8o8Mv3cKpElmNtC xjTQ== X-Gm-Message-State: ALyK8tL+EQw/XuWeV2mwdFdWSqkZtJoMz6q2GDjN4wxAAkx7a6FoW1Zg3VsIgLF3dxN1LOGRzIfdd3M64kc2Fg== MIME-Version: 1.0 X-Received: by 10.202.224.85 with SMTP id x82mr9342759oig.176.1464456295711; Sat, 28 May 2016 10:24:55 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.4.200 with HTTP; Sat, 28 May 2016 10:24:55 -0700 (PDT) In-Reply-To: References: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> <20160528083656.GT38613@kib.kiev.ua> Date: Sat, 28 May 2016 11:24:55 -0600 X-Google-Sender-Auth: sk3yvvesd9_zy_fddKWVD-1Xf5k Message-ID: Subject: Re: EFI GELI support ready for testers From: Alan Somers To: Eric McCorkle Cc: Allan Jude , "freebsd-hackers@freebsd.org" , "Kenneth D. Merry" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 17:24:56 -0000 On Sat, May 28, 2016 at 9:23 AM, Eric McCorkle wrote= : > >> On May 28, 2016, at 10:27, Allan Jude wrote: >> >> The final version of my geliboot took an extra effort to reuse the AES >> code from sys/crypto/rijndael and sys/opencrypto and GELI directly from >> sys/geom/eli to avoid maintaining a separate copy of that code in sys/bo= ot >> >> Hopefully the work I did to make sys/opencrypto and sys/geom/eli more >> reusable outside of the kernel will make it easier for Eric to do the >> same for the EFI version. > > It did indeed make things easier, though I think there is potential for w= ork to be done on the crypto framework. It looks like the crypto framework= has kind of accumulated code over time from different sources and has beco= me somewhat disorganized. There seem to be two codebases (crypto and opencr= ypto), and multiple differing implementations for some ciphers. I ran into= this when trying to figure out how to add Camellia support. There's a usa= ble interface for AES CBC/XTS, but not Camellia CBC. There are also some i= nsecure ciphers (DES, RC4, etc) in there, some more modern ciphers (like ch= acha20) are missing, and it's possible to implement ciphers other than AES = using AESNI/AVX instructions to achieve hardware acceleration. > > It also ought to be simpler to share crypto code between kernel, boot, an= d userland, imo. In theory, one could have a single library (with multiple= compilations for different ABIs) that could be statically linked into the = kernel and boot loaders, and also installed in to the base OS. > > I'm not sure if there's any plans for crypto, but it might be worth a dis= cussion. > >> >> The motivation for the EFI version is the same, ZFS boot environments, >> plus the obvious security advantages of having the kernel stored >> encrypted rather than not. >> > > The ability to have a single ZFS filesystem is indeed a motivator for the= EFI work. I forgot to mention it because my personal motivations are stro= ngly focused on security and tamper-resistance. The problem with opencrypto is that it was written when crypto accelerators lived on PCI cards and were treated as shared resources. That's why userland programs wishing to use opencrypto have to send all of their data into the kernel. It's a very inefficient way of using CPU-resident accelerators like AESNI and Padlock. For clients within the kernel, it's not so bad. It adds a few extra stack frames and a lot of code but there are no additional data copies. crypto(3), OTOH, is part of OpenSSL. AFAIK it doesn't have the data copies problem, but it's still quite complicated. ken@ once tried to build OpenSSL into the kernel but gave up because it has too many dependencies. So neither of these libraries is suitable for use in both kernel and userland. I don't know of any that is (though I haven't looked). -Alan From owner-freebsd-hackers@freebsd.org Sat May 28 17:26:25 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 1D342B4DA6E for ; Sat, 28 May 2016 17:26:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 9D4241FAE; Sat, 28 May 2016 17:26:24 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u4SHQJoU092097 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 28 May 2016 20:26:19 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u4SHQJoU092097 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u4SHQICv092096; Sat, 28 May 2016 20:26:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 28 May 2016 20:26:18 +0300 From: Konstantin Belousov To: Allan Jude Cc: freebsd-hackers@freebsd.org Subject: Re: EFI GELI support ready for testers Message-ID: <20160528172618.GB38613@kib.kiev.ua> References: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> <20160528083656.GT38613@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 17:26:25 -0000 On Sat, May 28, 2016 at 10:27:40AM -0400, Allan Jude wrote: > On 2016-05-28 04:36, Konstantin Belousov wrote: > > On Fri, May 27, 2016 at 07:39:57PM -0400, Eric McCorkle wrote: > >> I am pleased to announce that my work to add support for GELI in the EFI boot loader (as well as perform more general refactoring) is now ready for testing. I am able to successfully detect multiple GELI partitions in boot1 and pass the keys into the kernel. > > > > Can somebody explain in which way this is useful ? > > Same question for the GELI code for non-EFI loader. > > > > BIOS cannot read raw data from the encrypted partition, so you need > > either old boot or the loader and some additional data on EFI boot > > partition anyway. > > > > Features adds significant amount of code, which must be maintained in > > parallel with the kernel code. > > _______________________________________________ > > 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" > > > > The motivation for my work (GELI in boot2 and loader for non-EFI boot) > was supporting ZFS boot environments. Previously, when you use GELI you > needed to have two ZFS pools, one for an unencrypted /boot and one for > the encrypted / > > This breaks ZFS boot environments, since a snapshot of the root file > system won't include the correct kernel etc. Why cannot /boot included into the boot environment ? When I last saw Solaris, somewhere in its 10-th, any amount of filesystems could be added to the bootenv. But whatever the definition of bootenv is used, it exists at a level of the shell scripts and selecting the actual partition for loader. Throw thousand lines of code into the unstable and very hard to debug environment of loader looks somewhat unproductive. > > The final version of my geliboot took an extra effort to reuse the AES > code from sys/crypto/rijndael and sys/opencrypto and GELI directly from > sys/geom/eli to avoid maintaining a separate copy of that code in sys/boot Which means that kernel code must be also runnable in the strange and incompatible environment of the loader. I cannot see how this reduces code maintanability even a bit. I am already rather unhappy about ZFS kernel code being compiled as the userspace library, which hurt me and other people more than once. Now (?) the kernel code must be also verified for the loader. > > Hopefully the work I did to make sys/opencrypto and sys/geom/eli more > reusable outside of the kernel will make it easier for Eric to do the > same for the EFI version. > > The motivation for the EFI version is the same, ZFS boot environments, > plus the obvious security advantages of having the kernel stored > encrypted rather than not. Obvious security advantages ? Seriously ? What is a single 'security' advantage of hiding the kernel ? Since you noted a 'security', I realized that your changes decrypt the keys in the pre-kernel environment. In other words, very sensitive material becoming accessible to strange and unknown code which is managed by firmware. Putting aside ineradicable evil of Intel ME or its AMD twin, and SMM handler, you are exposing keys to whatever code happen to inhabit the preboot env, not neccessary originating from the firmware vendor. Secure Boot would not help there, since when the measurement indicate that untrusted component was there, it is too late. I.e., you making much easier for malice hacker to steal the keys. From owner-freebsd-hackers@freebsd.org Sat May 28 20:02: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 40D07B4EF8E for ; Sat, 28 May 2016 20:02:46 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (207-172-209-83.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.83]) by mx1.freebsd.org (Postfix) with ESMTP id 13497197C; Sat, 28 May 2016 20:02:45 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id B4E5817E7; Sat, 28 May 2016 20:02:44 +0000 (UTC) References: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> <20160528083656.GT38613@kib.kiev.ua> <20160528172618.GB38613@kib.kiev.ua> Mime-Version: 1.0 (1.0) In-Reply-To: <20160528172618.GB38613@kib.kiev.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <6A9DADE0-B214-424A-BB14-0B0848F0D08D@metricspace.net> Cc: Allan Jude , freebsd-hackers@freebsd.org X-Mailer: iPad Mail (13D15) From: Eric McCorkle Subject: Re: EFI GELI support ready for testers Date: Sat, 28 May 2016 16:02:43 -0400 To: Konstantin Belousov X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 20:02:46 -0000 > On May 28, 2016, at 13:26, Konstantin Belousov wrote= : >=20 >> On Sat, May 28, 2016 at 10:27:40AM -0400, Allan Jude wrote: >>> On 2016-05-28 04:36, Konstantin Belousov wrote: >>>> On Fri, May 27, 2016 at 07:39:57PM -0400, Eric McCorkle wrote: >>>> I am pleased to announce that my work to add support for GELI in the EFI= boot loader (as well as perform more general refactoring) is now ready for t= esting. I am able to successfully detect multiple GELI partitions in boot1 a= nd pass the keys into the kernel. >>>=20 >>> Can somebody explain in which way this is useful ? >>> Same question for the GELI code for non-EFI loader. >>>=20 >>> BIOS cannot read raw data from the encrypted partition, so you need >>> either old boot or the loader and some additional data on EFI boot >>> partition anyway. >>>=20 >>> Features adds significant amount of code, which must be maintained in >>> parallel with the kernel code. >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.or= g" >>=20 >> The motivation for my work (GELI in boot2 and loader for non-EFI boot) >> was supporting ZFS boot environments. Previously, when you use GELI you >> needed to have two ZFS pools, one for an unencrypted /boot and one for >> the encrypted / >>=20 >> This breaks ZFS boot environments, since a snapshot of the root file >> system won't include the correct kernel etc. > Why cannot /boot included into the boot environment ? > When I last saw Solaris, somewhere in its 10-th, any amount of > filesystems could be added to the bootenv. But whatever the definition > of bootenv is used, it exists at a level of the shell scripts and selectin= g > the actual partition for loader. Throw thousand lines of code into > the unstable and very hard to debug environment of loader looks somewhat > unproductive. You misunderstand. Alan was talking about pure ZFS systems, where there is o= ne big ZFS pool holding everything. You need to be able to access /boot obv= iously, but ZFS does not allow you to assign separate out data on to a singl= e device. It creates a pool, which combines all devices. To have /boot unencrypted, you have to have a separate partition for just /b= oot, which is undesirable. >>=20 >> The final version of my geliboot took an extra effort to reuse the AES >> code from sys/crypto/rijndael and sys/opencrypto and GELI directly from >> sys/geom/eli to avoid maintaining a separate copy of that code in sys/boo= t > Which means that kernel code must be also runnable in the strange and > incompatible environment of the loader. I cannot see how this reduces > code maintanability even a bit. I am already rather unhappy about ZFS > kernel code being compiled as the userspace library, which hurt me > and other people more than once. Now (?) the kernel code must be also > verified for the loader. I mean, the loader has to be able to access the filesystems, there's no way a= round it (barring crazy coreboot stuff). Also, it should be possible to create a synthetic EFI test-harness that runs= in *userland*. EFI is basically just a bunch of tables of function pointers= , no bios interrupts or anything. As long as you implement the interfaces, a= ny loader should also run in your synthetic environment. I had plans to loo= k into this after this work is done. >>=20 >> Hopefully the work I did to make sys/opencrypto and sys/geom/eli more >> reusable outside of the kernel will make it easier for Eric to do the >> same for the EFI version. >>=20 >> The motivation for the EFI version is the same, ZFS boot environments, >> plus the obvious security advantages of having the kernel stored >> encrypted rather than not. >=20 > Obvious security advantages ? Seriously ? > What is a single 'security' advantage of hiding the kernel ? >=20 There are plenty. Right up at the top, an attacker able to access /boot is free to tamper with= anything, and can insert back-doors into the kernel, loader, or any module.= If you assume that the attacker can't write, then they can still scan the k= ernel and modules for signatures for known vulnerabilities (since the kernel= itself has a commit id and detailed version info, they can compare this aga= inst a CVE database). Even if they can't do that for some reason, they coul= d still potentially exfilt a kernel address map for use in rootkit attacks a= gainst your system. Lastly, general security principles say to minimize the= attack surface, which would definitely mean you should protect the core of t= he system. > Since you noted a 'security', I realized that your changes decrypt the > keys in the pre-kernel environment. In other words, very sensitive > material becoming accessible to strange and unknown code which is > managed by firmware. The likelihood of such an attack, while something I considered, is very low.= A key should look like random binary data (much like the GUIDs prevalent i= n EFI code). I seriously doubt someone could write a firmware module that c= ould dig through the memory state of an arbitrary OS's boot loader and find k= eys. You'd basically have to put a full online binary analysis framework in= the firmware, and have it run fast enough to not be noticed. That would be= some serious Turing award-worthy work kept secret from the world solely to b= uild firmware backdoors. I don't think even Lenovo would go that far. (I know I mentioned scanning the kernel as a threat above; that's an offline= attack that can be done on a copy. Online undetectable analysis of a runni= ng program is WAY harder.) Besides, if someone wants to do evil things in firmware, I think it's far mo= re likely they'd just backdoor the network or USB controllers to let someone= send an override packet and execute bundled code in kernel mode. That work= s every time for every OS and doesn't require surreptitiously picking apart a= rbitrary programs' data structures in real time. For what it's worth, I have considered possible hardening measures: using al= ias GUIDs to disguise interfaces and adding per-build padding or XOR masks t= o structures with keys to throw off scanners. However, I don't think the th= reat is realistic enough to warrant such measures. > Putting aside ineradicable evil of Intel ME or its > AMD twin, and SMM handler, you are exposing keys to whatever code happen > to inhabit the preboot env, not neccessary originating from the firmware > vendor. Secure Boot would not help there, since when the measurement > indicate that untrusted component was there, it is too late. I.e., > you making much easier for malice hacker to steal the keys. I mean, the same argument holds for the kernel, if not moreso. You have ACP= I bytecode, SMM, device blobs, anything that the boot environment chose to k= eep around for runtime by marking that memory as "unavailable", and of cours= e, the evil that is Intel ME. This is an unavoidable risk of having keys in= main memory ever. If you really want any kind of safety from this, you need to use a hardware c= rypto device that stores keys in a separate memory (which, I specifically de= signed things to make it easy to add support for one). Of course, you then h= ave to trust the device... > _______________________________________________ > 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 Sat May 28 20:19:14 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 B56D8B4E347 for ; Sat, 28 May 2016 20:19:14 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 8829B11B7; Sat, 28 May 2016 20:19:14 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [172.16.0.97] (unknown [172.16.0.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id D4C3E17EB; Sat, 28 May 2016 20:19:13 +0000 (UTC) User-Agent: K-9 Mail for Android In-Reply-To: References: <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> <20160528083656.GT38613@kib.kiev.ua> MIME-Version: 1.0 Subject: Re: EFI GELI support ready for testers From: Eric McCorkle Date: Sat, 28 May 2016 16:19:12 -0400 To: Alan Somers CC: Allan Jude , "freebsd-hackers@freebsd.org" , "Kenneth D. Merry" Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 20:19:14 -0000 I see. They're part device interface, part software crypto implementation. I guess the question is, does the software crypto *have* to live there, or could it be in a separate library? I'm less inclined to trust OpenSSL completely these days, and it certainly is a beast to integrate into anything. Some compelling alternatives have emerged in the wake of heartbleed. Off the cuff, I'd say NaCl is a good option: it's public domain and it's got some big names in crypto attached to it. But I don't know enough to say for sure if it could do what I proposed. On May 28, 2016 1:24:55 PM EDT, Alan Somers wrote: >On Sat, May 28, 2016 at 9:23 AM, Eric McCorkle >wrote: >> >>> On May 28, 2016, at 10:27, Allan Jude wrote: >>> >>> The final version of my geliboot took an extra effort to reuse the >AES >>> code from sys/crypto/rijndael and sys/opencrypto and GELI directly >from >>> sys/geom/eli to avoid maintaining a separate copy of that code in >sys/boot >>> >>> Hopefully the work I did to make sys/opencrypto and sys/geom/eli >more >>> reusable outside of the kernel will make it easier for Eric to do >the >>> same for the EFI version. >> >> It did indeed make things easier, though I think there is potential >for work to be done on the crypto framework. It looks like the crypto >framework has kind of accumulated code over time from different sources >and has become somewhat disorganized. There seem to be two codebases >(crypto and opencrypto), and multiple differing implementations for >some ciphers. I ran into this when trying to figure out how to add >Camellia support. There's a usable interface for AES CBC/XTS, but not >Camellia CBC. There are also some insecure ciphers (DES, RC4, etc) in >there, some more modern ciphers (like chacha20) are missing, and it's >possible to implement ciphers other than AES using AESNI/AVX >instructions to achieve hardware acceleration. >> >> It also ought to be simpler to share crypto code between kernel, >boot, and userland, imo. In theory, one could have a single library >(with multiple compilations for different ABIs) that could be >statically linked into the kernel and boot loaders, and also installed >in to the base OS. >> >> I'm not sure if there's any plans for crypto, but it might be worth a >discussion. >> >>> >>> The motivation for the EFI version is the same, ZFS boot >environments, >>> plus the obvious security advantages of having the kernel stored >>> encrypted rather than not. >>> >> >> The ability to have a single ZFS filesystem is indeed a motivator for >the EFI work. I forgot to mention it because my personal motivations >are strongly focused on security and tamper-resistance. > >The problem with opencrypto is that it was written when crypto >accelerators lived on PCI cards and were treated as shared resources. >That's why userland programs wishing to use opencrypto have to send >all of their data into the kernel. It's a very inefficient way of >using CPU-resident accelerators like AESNI and Padlock. For clients >within the kernel, it's not so bad. It adds a few extra stack frames >and a lot of code but there are no additional data copies. crypto(3), >OTOH, is part of OpenSSL. AFAIK it doesn't have the data copies >problem, but it's still quite complicated. ken@ once tried to build >OpenSSL into the kernel but gave up because it has too many >dependencies. > >So neither of these libraries is suitable for use in both kernel and >userland. I don't know of any that is (though I haven't looked). > >-Alan -- Sent from my Android device with K-9 Mail. Please excuse my brevity.