From owner-freebsd-hackers@freebsd.org Sun Sep 18 13:09: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 A10CCBDECB2 for ; Sun, 18 Sep 2016 13:09:22 +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 696BC110A for ; Sun, 18 Sep 2016 13:09:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1blbqR-0005Us-3J for freebsd-hackers@freebsd.org; Sun, 18 Sep 2016 16:09:19 +0300 Date: Sun, 18 Sep 2016 16:09:19 +0300 From: Slawa Olhovchenkov To: freebsd-hackers@freebsd.org Subject: DTrace and curproc Message-ID: <20160918130918.GJ2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 13:09:22 -0000 Is a way to get curproc in DTrace script? Direct using curproc give me error: "failed to resolve curproc: Unknown variable name" From owner-freebsd-hackers@freebsd.org Sun Sep 18 17:24:29 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68931BE02A7 for ; Sun, 18 Sep 2016 17:24:29 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::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 434A8917 for ; Sun, 18 Sep 2016 17:24:29 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pa0-x22f.google.com with SMTP id hm5so8640871pac.0 for ; Sun, 18 Sep 2016 10:24:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=HuTQ6GYia6xUy5JvTcLDgJUEexq0vDqePEgAZnlbfI4=; b=PpB0Lp8u4ElajiHgEbBSD9zcvjDsZYn4j5ZIYNUklxNISVSkYFls1DuJCvVHGY+RKV 3MT2S3sTLiGFF22oe8JTv2TeSsePiFtkUfnOZM+ftASmEpe77H/8Vs5ajpyRBkkIdD6Y R4W8k5ju1RGsU+A9s2Odv94z/pgENMFlMokleIeeQxtOtF5qntoZwtyi4MW819TVGg2P KrDgeGE6TqmMMgotkScf1oElVbjb5wzmRj5p4BNKHf016XBXHUumCX6gjhuDwoL4zDTS VpPcF8FOQtgNIy+eqNej7OdnI7iTzKg9AZfO6aioUoD9GhEUuV/OE2o+I9jnwTxUld8T dkbQ== 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:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=HuTQ6GYia6xUy5JvTcLDgJUEexq0vDqePEgAZnlbfI4=; b=jiD+SmrN8sguOeiQpuAzOBkohqRvgLVe68EcVTUKqUrLnkudv3ISMJjPRvuZxpKkMG cDd8rtLe/aTJ7I9hGWBs0x2wN1QX5G09koznX2lYowMYBRFWZ8pTUi3CbBBMygIo+Gdn MbRgng4gVQ7Ei9du9dDoqUZG2+f1UHgHeqB7czPtmCZIe4VG2Denef7gZwmwQsj5Tol1 WyjoyAhuR34+PJkkFtiYuSyI4raIxdf2gHo40OnWaIoIEEFlOZ4mpYPwTtl2jfdRPTCn isCf5TBoSjXCe3qSpZAjYfsYCAiJ1k+lkmEBpDH34O1HQ4AoEZvM62KTbEtmzDiQx2Xl N1oA== X-Gm-Message-State: AE9vXwPLkQc0BV2sg9IrEJge5bEud2Dfa3KMRlx2kGNsFGmi0cgqtHSq1SYDAFOLmc5wOQ== X-Received: by 10.66.232.106 with SMTP id tn10mr40501173pac.130.1474219468693; Sun, 18 Sep 2016 10:24:28 -0700 (PDT) Received: from raichu ([2604:4080:1102:0:ca60:ff:fe9d:3963]) by smtp.gmail.com with ESMTPSA id y3sm65626973pfy.36.2016.09.18.10.24.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Sep 2016 10:24:28 -0700 (PDT) Sender: Mark Johnston Date: Sun, 18 Sep 2016 10:24:24 -0700 From: Mark Johnston To: Slawa Olhovchenkov Cc: freebsd-hackers@freebsd.org Subject: Re: DTrace and curproc Message-ID: <20160918172424.GA57218@raichu> References: <20160918130918.GJ2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160918130918.GJ2840@zxy.spb.ru> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 17:24:29 -0000 On Sun, Sep 18, 2016 at 04:09:19PM +0300, Slawa Olhovchenkov wrote: > Is a way to get curproc in DTrace script? > Direct using curproc give me error: > > "failed to resolve curproc: Unknown variable name" You can use curthread->td_proc, which is equivalent. "curpsinfo" from Solaris is also implemented. From owner-freebsd-hackers@freebsd.org Wed Sep 21 09:29: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 41E20BE2BF8; Wed, 21 Sep 2016 09:29:16 +0000 (UTC) (envelope-from pkubaj@anongoth.pl) Received: from anongoth.pl (anongoth.pl [88.156.79.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anongoth.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D514E9B; Wed, 21 Sep 2016 09:29:15 +0000 (UTC) (envelope-from pkubaj@anongoth.pl) Received: from mail (unknown [127.0.1.10]) by anongoth.pl (Postfix) with ESMTP id 132555049; Wed, 21 Sep 2016 11:19:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at anongoth.pl Received: from anongoth.pl ([127.0.1.10]) by mail (anongoth.pl [127.0.1.10]) (amavisd-new, port 10024) with LMTP id y5RxehkTIqO7; Wed, 21 Sep 2016 11:19:15 +0200 (CEST) Received: from [10.10.0.70] (unknown [46.248.161.165]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: pkubaj) by anongoth.pl (Postfix) with ESMTPSA id 2414F5036; Wed, 21 Sep 2016 11:19:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=anongoth.pl; s=ANONGOTH; t=1474449555; bh=F2aoAI031hVQey/kFVGGdwh0vG0oocskD1A0flP3NBA=; h=To:From:Subject:Date; b=oZ5NWUN0qo7SWcPKVyF+madLVjFPSUBnod8t8lOMJzQgzyCK2rhlpAx42OU9SfFyE nIQb8+nk294hdZbj2AtJhFJCwzk8LUA9zj+25APHVaK7ewdNwELegh6qGC1nLGDRGm 3VivE1gIgYb05ZQwQKaFbPAYovCmfkN/aANylHOm35lC9X577s7z6ojgOPpCTSuqNR 4IR1ufRgjX6lzNuBDois48YKczNkAFHOQcxIUeVOmW/HEWMa9lp2yZYpy4GvN2Ujyc zFG5tGt0qfv0yzYz24hzAgxSip8swxP8rddQM/toqlwM8ezCyYllAkLFHNZS5/8DeS 2+uaHli06ARWA== To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org From: Piotr Kubaj Subject: Freeze during booting of ASUS F2A85-M motherboard with Coreboot Message-ID: Date: Wed, 21 Sep 2016 11:19:05 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KGws6EercWTvinA1jpAjEsavFJXufSAxh" X-Mailman-Approved-At: Wed, 21 Sep 2016 11:00:59 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 09:29:16 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --KGws6EercWTvinA1jpAjEsavFJXufSAxh Content-Type: multipart/mixed; boundary="2SjToMQFS6akU9EDXVNXr3gWXE0jFdR1i" From: Piotr Kubaj To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Message-ID: Subject: Freeze during booting of ASUS F2A85-M motherboard with Coreboot --2SjToMQFS6akU9EDXVNXr3gWXE0jFdR1i Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I'm trying to boot the ASUS F2A85-M board with flashed Coreboot 4.4 and SeaBIOS 1.9.1 as a payload. This board works nicely with stock UEFI, it can also boot Slackware 14.2 from Coreboot with SeaBIOS without any issues. But it seems to have problems with FreeBSD (I've tried 11.0-RC3 and later 12.0-CURRENT). That's why I'm posting it here, instead of Coreboot mailing lists. Booting freezes after printing: pcib1: failed to allocate initial I/O port window: 0x1000-0x1fff After that, I've waited for about 30 minutes. Nothing happened, altough my DVD drive was spinning for a while, which may indicate that the OS was actually booting, but without printing anything (I was booting from DVD). I use external NVIDIA GPU (GF GT650TI), which may matter. Any ideas what I can do with it? My Coreboot config is at: http://cxg.de/_98b2f4.htm SeaBIOS config: http://cxg.de/_020d57.htm --2SjToMQFS6akU9EDXVNXr3gWXE0jFdR1i-- --KGws6EercWTvinA1jpAjEsavFJXufSAxh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX4lCRAAoJEHpZm4Ugg5ydNEwP/1MANzDpq03tFiVgJYc8a40U F27UuUm1g+Vh81Mna2ETB+moeeKVUtfo5emucJ2bWT2BVa0droiXUwqaxJzbhzTW 9EXPktaQXzAvUc+e2Wmvt/wxb7nkvl2B/MutGiGgm4+WhrL5CEKASci/+6b2wPiU R09ULmHCRaiIViuqHocBYWitgMcq5PPJ5PHA/8U9YC2WriXb8EPO7SSuT6FKxRc1 VzmZ5oMy/CDfTafA1rNIHGtuSHvbgvs3DebkN+5q2abNBJ/X9JpiIofJ0yE2w+cu IbZa9F/JDddxCPnaR8Pa04CPyWmsmtfEZVog4N/ciMFY6AQzYqP64SY9vm67wXji AkdxCqPCzzcqoa6ifbFBASc8ulW86pKNEmZvGG5rqyqngecOJ6jRUDiyvfQZyJmu yvzVaEiEmIrg52kR6GNm4mmXfNASZwrn3/AvewucWrOW8b6hHKptrPxpfq+ITaWN QRPByQeqZ8ca7Iaj6MsFjy3SF0wZvUKOVAXxZ63lb/l58FVxdukmj1unmysqR4df sEbldyPMvOvQkShv3J7yO0wZa8TzvHKuHRv9s2Rv1Zc7m6BtzdR+5j02ai3Gy+ad fAadNh59Ac3CAKxmJRAdH4keDyz1WoWGsG0QLJ1vZRE/ZfGESDosEdMaxg4Y6/vJ S/wlk6Ec6xEqOvshoSkA =l7lJ -----END PGP SIGNATURE----- --KGws6EercWTvinA1jpAjEsavFJXufSAxh-- From owner-freebsd-hackers@freebsd.org Fri Sep 23 10:09: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 D1F14BE5A6F; Fri, 23 Sep 2016 10:09:36 +0000 (UTC) (envelope-from def@FreeBSD.org) Received: from troz.pl (troz.pl [37.187.125.115]) by mx1.freebsd.org (Postfix) with ESMTP id 87BE9B53; Fri, 23 Sep 2016 10:09:35 +0000 (UTC) (envelope-from def@FreeBSD.org) Received: from [192.168.81.123] (unknown [109.111.229.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by troz.pl (Postfix) with ESMTPSA id 9D22B409; Fri, 23 Sep 2016 12:09:34 +0200 (CEST) Subject: Re: How to bring au_to_attr(3) back to the userland? To: "Robert N. M. Watson" , Mateusz Piotrowski <0mp@FreeBSD.org> References: <83CC669E-FED9-4ABE-A5A5-376E1A743AF8@FreeBSD.org> <09D137C4-2630-4B93-ACDC-CB3AFC86D89F@FreeBSD.org> <93122C2D-A660-4A47-A780-44E8309E4377@FreeBSD.org> Cc: freebsd-hackers@freebsd.org, trustedbsd-discuss@freebsd.org, trustedbsd-audit@freebsd.org From: Konrad Witaszczyk Message-ID: <08154690-df05-9314-702e-4e0cdd661f04@FreeBSD.org> Date: Fri, 23 Sep 2016 12:09:30 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <93122C2D-A660-4A47-A780-44E8309E4377@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tqie9SOJmMNO0r42m8w0uJ24GwhGngFil" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 10:09:36 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --tqie9SOJmMNO0r42m8w0uJ24GwhGngFil Content-Type: multipart/mixed; boundary="QhWplOJG4rl41lSBCn4LIBfPPjGLtLTmM"; protected-headers="v1" From: Konrad Witaszczyk To: "Robert N. M. Watson" , Mateusz Piotrowski <0mp@FreeBSD.org> Cc: freebsd-hackers@freebsd.org, trustedbsd-discuss@freebsd.org, trustedbsd-audit@freebsd.org Message-ID: <08154690-df05-9314-702e-4e0cdd661f04@FreeBSD.org> Subject: Re: How to bring au_to_attr(3) back to the userland? References: <83CC669E-FED9-4ABE-A5A5-376E1A743AF8@FreeBSD.org> <09D137C4-2630-4B93-ACDC-CB3AFC86D89F@FreeBSD.org> <93122C2D-A660-4A47-A780-44E8309E4377@FreeBSD.org> In-Reply-To: <93122C2D-A660-4A47-A780-44E8309E4377@FreeBSD.org> --QhWplOJG4rl41lSBCn4LIBfPPjGLtLTmM Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 08/17/2016 08:47, Robert N. M. Watson wrote: > On 17 Aug 2016, at 00:18, Mateusz Piotrowski <0mp@FreeBSD.org> wrote: > >> To sum it up. The idea is to: >> >> 1. Rename vnode_au_info to au_vattr. >> 2. Keep au_to_attr away from the userland. >> 3. Add au_to_vattr (the parameter of which is struct au_vattr) to the = libbsm >> API and make it available to the userland. >> 4. Re-craft au_vattr to use the same types that are present in the und= erlying=20 >> attribute token. >> >> I am not sure if I understand this properly; do we want to simply rena= me=20 >> vnode_au_info to au_vattr and make it available in the userland after = a couple=20 >> of modifications? If so then it sounds like a good idea to me as long = as I don't=20 >> break something accidentally. Wouldn't renaming and modifying struct v= node_au_info=20 >> cause compatibility problems and potentially break someone's software?= > I guess you have two choices: > > (1) Retain existing KPIs to slightly ease merging to FreeBSD and Mac OS= X; they can adopt the new in-kernel interfaces when ready. I think it won't be hard to adopt the changes in the FreeBSD kernel toget= her with the changes in libbsm. Would you still consider it as an issue becau= se of macOS if we fix it in FreeBSD? I don't know how important it is to their developers to stick with the current OpenBSM implementation. > (2) Simply remove the old KPIs and consider it a feature. > > The former probably does marginally ease merging the new OpenBSM versio= n (one fewer kernel changes for FreeBSD and Mac OS X at the point of merg= e), so I see no harm in retaining it. However, as it=E2=80=99s ifdef=E2=80= =99d _KERNEL || KERNEL in the OpenBSM header, it has not been exposed to = user applications, just the kernel. > > Remember that changes in these structures don=E2=80=99t affect the layo= ut and interpretation of the tokens at all =E2=80=94 it=E2=80=99s really = just on the producer side that a KPI changes =E2=80=94 and the informatio= n we=E2=80=99re able to expose. > > The existing vnode_au_info isn=E2=80=99t really an appropriate public i= nterface, so do make sure not to remove the ifdefs preventing its use =E2= =80=94 instead, we should focus on a new interface that is appropriate to= be public by virtue of (a) having an appropriate struct type argument th= at has both the fields we require and is as non-OS-specific as possible; = (b) doesn=E2=80=99t conflict with the current interface on FreeBSD/Mac OS= X; and (c) doesn=E2=80=99t conflict with the current interface on Solari= s. > >> Apart from that it sounds like a reasonable solution. >> >> Thank you very much for the detailed introduction to the complexity of= this problem. >> Although the GSoC is coming to an end and I plan to focus on integrati= ng my work >> into auditdistd, I hope to apply the solutions we discuss here sometim= e later. > The problems are all about compatibility, and I think we have a reasona= ble path here that does what we need without too much work. > > Robert > --QhWplOJG4rl41lSBCn4LIBfPPjGLtLTmM-- --tqie9SOJmMNO0r42m8w0uJ24GwhGngFil Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJX5P9bXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGREI1MzAxNjZGNTBCM0NCRUQ5QjZGNzdF MUMxMjI1QjBCMjZBNEYwAAoJEOHBIlsLJqTwzEIQAKAf2csdzjrIBYmEejXXoUxA 1e1mSyxeDQDNrWvk2xBpfkDsGgJubR7WCpJhm8u7T85D/Dg34e4YYHsuCevMdOEt DVg+cPskSSv/ZE16VYelcUI6lZCJqhB7rsi6E4nislXMVhqUzh4+CxnpOwCrNc5b xaTSYkex/rUFQJosMDM0bHHSep3Nc9a9sBSIaTnZpUemIQYKZPBRYd9TvOlrTWqd 60sMZJBdqyiVPus3boe29kPjrJLRL+LOdJxLyP8/a8/LQUT0DFjn/SHj10UDyWtw jS8LB+eDku0ckMNJtZ9RC8mQ/z0Lp6tDjdPfVwINgtpi82pcUafLgwno5gk4oujE 1/AQWIhKbTdcahA3WivS0AJqYaxk9JZAfTSLyPicmKWCY5Qugt/x3sjfDpjjoNQ6 xE1Ahs4GZTZy8T2bEWB4ZjqxzNBYX3+KvGNvAI+2HhTRWod9XOLZasutgj+zBNGi 8p4zTOTqTWMXPYnDr6Xfw1PwCslLiZVVpWNx75wvuQNss3kUCI9/52iVQZ/9TPAm Mo7R0Egu5Dz6VfwkarxE8bjKiHbqzTbjxSiDuaoUUzbLnYMlQwRWgFwKNyUTvTRD raIgjDAGQQ+ZGbZHUgSRdgy+qR8NBzOa0g2uRicxhZRDrss/sbNEwFTQyOwBGDp4 M7AEV/WF4xdXH9ksejng =NKx4 -----END PGP SIGNATURE----- --tqie9SOJmMNO0r42m8w0uJ24GwhGngFil-- From owner-freebsd-hackers@freebsd.org Fri Sep 23 10:19:29 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDA77BE5F61; Fri, 23 Sep 2016 10:19:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [198.74.231.69]) by mx1.freebsd.org (Postfix) with ESMTP id 8ACD4FD6; Fri, 23 Sep 2016 10:19:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from [192.168.81.201] (unknown [212.163.6.23]) by cyrus.watson.org (Postfix) with ESMTPSA id ABE2446CF5; Fri, 23 Sep 2016 06:19:27 -0400 (EDT) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: How to bring au_to_attr(3) back to the userland? From: "Robert N. M. Watson" In-Reply-To: <08154690-df05-9314-702e-4e0cdd661f04@FreeBSD.org> Date: Fri, 23 Sep 2016 11:19:26 +0100 Cc: Mateusz Piotrowski <0mp@FreeBSD.org>, freebsd-hackers@freebsd.org, trustedbsd-discuss@freebsd.org, trustedbsd-audit@freebsd.org Message-Id: References: <83CC669E-FED9-4ABE-A5A5-376E1A743AF8@FreeBSD.org> <09D137C4-2630-4B93-ACDC-CB3AFC86D89F@FreeBSD.org> <93122C2D-A660-4A47-A780-44E8309E4377@FreeBSD.org> <08154690-df05-9314-702e-4e0cdd661f04@FreeBSD.org> To: Konrad Witaszczyk X-Mailer: Apple Mail (2.3124) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 10:19:29 -0000 On 23 Sep 2016, at 11:09, Konrad Witaszczyk wrote: >> I guess you have two choices: >>=20 >> (1) Retain existing KPIs to slightly ease merging to FreeBSD and Mac = OS X; they can adopt the new in-kernel interfaces when ready. >=20 > I think it won't be hard to adopt the changes in the FreeBSD kernel = together > with the changes in libbsm. Would you still consider it as an issue = because of > macOS if we fix it in FreeBSD? I don't know how important it is to = their > developers to stick with the current OpenBSM implementation. While the kernel and userspace share code from OpenBSM in both FreeBSD = and Mac OS X, it=E2=80=99s useful to be able to upgrade userspace = without necessarily changing kernel code =E2=80=94 e.g., if security = patches are required in parsing, etc. I think it would be best to = differentiate the new programming interface by giving it a new name, and = keeping the existing interface, but marked to be removed at a future = date. We could even discourage its use by making if #ifdef = OPENBSM_DEPRECATED or such, requiring that it be explicitly enabled to = be available to hint to those doing merges that it=E2=80=99s time to = move to the new KPI. Robert=