From owner-freebsd-current@freebsd.org Mon Dec 17 18:42:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6108E1348C8E for ; Mon, 17 Dec 2018 18:42:11 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.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 E621884498 for ; Mon, 17 Dec 2018 18:42:10 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 0094510B785; Mon, 17 Dec 2018 13:42:08 -0500 (EST) Subject: Re: 12.0 - (zpool upgrade ) /bootpool/boot/* new location for /boot/* ? To: Bruce Cantrall , "freebsd-current@freebsd.org" References: <8573D5C3-B749-487D-8A87-D7C93F4CA710@contoso.com> From: John Baldwin Openpgp: preference=signencrypt Autocrypt: addr=jhb@FreeBSD.org; keydata= mQGiBETQ+XcRBADMFybiq69u+fJRy/0wzqTNS8jFfWaBTs5/OfcV7wWezVmf9sgwn8TW0Dk0 c9MBl0pz+H01dA2ZSGZ5fXlmFIsee1WEzqeJzpiwd/pejPgSzXB9ijbLHZ2/E0jhGBcVy5Yo /Tw5+U/+laeYKu2xb0XPvM0zMNls1ah5OnP9a6Ql6wCgupaoMySb7DXm2LHD1Z9jTsHcAQMD /1jzh2BoHriy/Q2s4KzzjVp/mQO5DSm2z14BvbQRcXU48oAosHA1u3Wrov6LfPY+0U1tG47X 1BGfnQH+rNAaH0livoSBQ0IPI/8WfIW7ub4qV6HYwWKVqkDkqwcpmGNDbz3gfaDht6nsie5Z pcuCcul4M9CW7Md6zzyvktjnbz61BADGDCopfZC4of0Z3Ka0u8Wik6UJOuqShBt1WcFS8ya1 oB4rc4tXfSHyMF63aPUBMxHR5DXeH+EO2edoSwViDMqWk1jTnYza51rbGY+pebLQOVOxAY7k do5Ordl3wklBPMVEPWoZ61SdbcjhHVwaC5zfiskcxj5wwXd2E9qYlBqRg7QeSm9obiBCYWxk d2luIDxqaGJARnJlZUJTRC5vcmc+iGAEExECACAFAkTQ+awCGwMGCwkIBwMCBBUCCAMEFgID AQIeAQIXgAAKCRBy3lIGd+N/BI6RAJ9S97fvbME+3hxzE3JUyUZ6vTewDACdE1stFuSfqMvM jomvZdYxIYyTUpC5Ag0ERND5ghAIAPwsO0B7BL+bz8sLlLoQktGxXwXQfS5cInvL17Dsgnr3 1AKa94j9EnXQyPEj7u0d+LmEe6CGEGDh1OcGFTMVrof2ZzkSy4+FkZwMKJpTiqeaShMh+Goj XlwIMDxyADYvBIg3eN5YdFKaPQpfgSqhT+7El7w+wSZZD8pPQuLAnie5iz9C8iKy4/cMSOrH YUK/tO+Nhw8Jjlw94Ik0T80iEhI2t+XBVjwdfjbq3HrJ0ehqdBwukyeJRYKmbn298KOFQVHO EVbHA4rF/37jzaMadK43FgJ0SAhPPF5l4l89z5oPu0b/+5e2inA3b8J3iGZxywjM+Csq1tqz hltEc7Q+E08AAwUIAL+15XH8bPbjNJdVyg2CMl10JNW2wWg2Q6qdljeaRqeR6zFus7EZTwtX sNzs5bP8y51PSUDJbeiy2RNCNKWFMndM22TZnk3GNG45nQd4OwYK0RZVrikalmJY5Q6m7Z16 4yrZgIXFdKj2t8F+x613/SJW1lIr9/bDp4U9tw0V1g3l2dFtD3p3ZrQ3hpoDtoK70ioIAjjH aIXIAcm3FGZFXy503DOA0KaTWwvOVdYCFLm3zWuSOmrX/GsEc7ovasOWwjPn878qVjbUKWwx Q4QkF4OhUV9zPtf9tDSAZ3x7QSwoKbCoRCZ/xbyTUPyQ1VvNy/mYrBcYlzHodsaqUDjHuW+I SQQYEQIACQUCRND5ggIbDAAKCRBy3lIGd+N/BCO8AJ9j1dWVQWxw/YdTbEyrRKOY8YZNwwCf afMAg8QvmOWnHx3wl8WslCaXaE8= Message-ID: <28c3650e-befa-a62a-428b-e36d98b11440@FreeBSD.org> Date: Mon, 17 Dec 2018 10:42:12 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: <8573D5C3-B749-487D-8A87-D7C93F4CA710@contoso.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 17 Dec 2018 13:42:09 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2018 18:42:11 -0000 On 12/14/18 4:45 PM, Bruce Cantrall wrote: > Hi, First time poster. > Did the location for the files in /boot move to /bootpool/boot but the zpool upgrade did not know this in 12.0? > > # uname -a > FreeBSD filestore1b.phishline.com 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC amd64 > > # zpool upgrade zroot > This system supports ZFS pool feature flags. > > Enabled the following features on 'zroot': > large_dnode > spacemap_v2 > > If you boot from pool 'zroot', don't forget to update boot code. > Assuming you use GPT partitioning and da0 is your boot disk > the following command will do it: > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 > > ????????????? > (/boot does not exist but is now in /bootpool/boot) > > # gpart bootcode -b /bootpool/boot/pmbr -p /bootpool/boot/gptzfsboot -i 1 da0 > > (SNIP) > This system supports ZFS pool feature flags. > > Enabled the following features on 'bootpool': > large_dnode > spacemap_v2 > > # freebsd-update upgrade > src component not installed, skipped > Cannot identify running kernel > > Worked Ok when I added the /bootpool directory to the path. zpool upgrade's message is not very smart. I think it just uses hardcoded paths and a hardcode drive. (For example, it always says da0 even if you have a mirror in which case you should update the bootcode on all of the devices.) I have a fresh install of 12.0-RC3 here that still has the files in /boot and doesn't have a /bootpool directory at all. -- John Baldwin                                                                              From owner-freebsd-current@freebsd.org Wed Dec 19 01:06:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38A49134532D for ; Wed, 19 Dec 2018 01:06:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670046.outbound.protection.outlook.com [40.107.67.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 680458FE58 for ; Wed, 19 Dec 2018 01:06:01 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR01MB0395.CANPRD01.PROD.OUTLOOK.COM (10.166.150.143) by YTOPR01MB0218.CANPRD01.PROD.OUTLOOK.COM (10.166.151.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1425.19; Wed, 19 Dec 2018 01:05:59 +0000 Received: from YTOPR01MB0395.CANPRD01.PROD.OUTLOOK.COM ([fe80::cdca:7b49:ceab:91f]) by YTOPR01MB0395.CANPRD01.PROD.OUTLOOK.COM ([fe80::cdca:7b49:ceab:91f%3]) with mapi id 15.20.1425.023; Wed, 19 Dec 2018 01:05:59 +0000 From: Rick Macklem To: "freebsd-current@FreeBSD.org" Subject: possible POLA violation for NFS server to make it Linux compatible Thread-Topic: possible POLA violation for NFS server to make it Linux compatible Thread-Index: AQHUlzZLCZ8Tsqd2GkKmM/wWP+MyUQ== Date: Wed, 19 Dec 2018 01:05:59 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR01MB0218; 6:Tp1rqKt9QOV7mrqpRio4SeaJm/sTcqaOg9K0Tvt2k1u7eltkwXe7mwJNUAbHBUiG6/3ly9upDVdmfZ548LqC9Wl4l9EJmgIyBihK5i7JDhKDR+RIMLjK+BjveGLArAJVNJCgbj3CqEshoOsX3hJKhqT1QleXZJZEJVZXhlxIXnLaDthykjqVJWos5Fg9t7jQ2Jmnoa1jHzBMLd00ziDgLCTWm02A6ypmATCRIna01GQj4JeEmbHIjPqtj9mn/O54TwLCUIPwqGhsFHMmlVg3PB1StSz8TLOqXeQdxqqmrbFSMUygrlvHtRa3kDzI+DFe0Cz71tLSTkB9UNG/+gpkpJowShicGayCCpBQ4ObMrdQh2B/AuDZRx71HleF3hNe8Io4szllspnvgYlUK/US4annBnKLdTS0dWs/3qT6na+aztySUjiMLFsLDYAneLTzhdH71ABcX71YWNNe/AT49bQ==; 5:8nr6JIS4KKIKYHwvFVe2UIHpL4XrAht86ArGBSKLFlv0Evj/IvW6OHqqqxyHt6AQD3oQ/6wBNT38PPi8DlCzxHFqE++91js0yzeXRA0025EN5gg8UkRAt1hY7WrTD9p9nB/XSBLdMUudkEAGjM8A7NRhD1DeuP/fzd0U8A1mMFo=; 7:Sp5q3bCZYXk/Jyz4D7ZIr5WhfOsfgXqM6s4NHjYoyMbEnbxi1z2EDYSBCETjx4Lgac/Kp6TVyANCR8mS99aGiyXm3jjSsed6U9JQZJ60iwQW7ZrzU/2fmRLoTC9aKfJNh74+kmP+6sr1ZEaIx+liRg== x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: d53764e1-68cc-4bd8-e68b-08d6654e239b x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOPR01MB0218; x-ms-traffictypediagnostic: YTOPR01MB0218: x-microsoft-antispam-prvs: x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(3230021)(999002)(6040522)(2401047)(5005006)(8121501046)(3231475)(944501520)(52105112)(93006095)(93001095)(10201501046)(3002001)(148016)(149066)(150057)(6041310)(20161123562045)(20161123564045)(20161123560045)(20161123558120)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:YTOPR01MB0218; BCL:0; PCL:0; RULEID:; SRVR:YTOPR01MB0218; x-forefront-prvs: 0891BC3F3D x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(39860400002)(396003)(136003)(366004)(376002)(189003)(199004)(33656002)(6436002)(5640700003)(74316002)(25786009)(2501003)(6916009)(68736007)(305945005)(46003)(9686003)(71190400001)(71200400001)(8936002)(55016002)(2906002)(2351001)(8676002)(7696005)(97736004)(81156014)(81166006)(53936002)(786003)(486006)(102836004)(6506007)(316002)(478600001)(105586002)(5660300001)(186003)(476003)(14454004)(86362001)(74482002)(99286004)(256004)(106356001)(14444005); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR01MB0218; H:YTOPR01MB0395.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: Qk90QdeWZvD+Vlay8Qp0o+7gBerlJyqUx37upNH2okMCt8L5JvAIhD+hLsgTqipupGVrNNXIL10GIhdlACRjohsaMJ8/mwO0P6SXDJd9gmy7vOIE5oDuoAJN7RFNcgy1i97C97Eoeabjz/0AH9coOQIBrJFqTF9xikz8wUIrUy51RdGcdCWRbZ7syCcZ24UtgLj4EkMEB+zQz+PvyATrPHdBsHj4KCw8bpAMTeSGFCHdSWgUiYuRdszI2b1LeIMqEhhzU3uGY/8XmGRKHBKlZ3lVUv5qRHTylM/fWLlfzf1ayKGzhKasFW+BA9who+hu spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: d53764e1-68cc-4bd8-e68b-08d6654e239b X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Dec 2018 01:05:59.8152 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR01MB0218 X-Rspamd-Queue-Id: 680458FE58 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of rmacklem@uoguelph.ca designates 40.107.67.46 as permitted sender) smtp.mailfrom=rmacklem@uoguelph.ca X-Spamd-Result: default: False [-3.70 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/17]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com,mx2.hc184-76.ca.iphmx.com,mx1.hc184-76.ca.iphmx.com]; NEURAL_HAM_SHORT(-0.59)[-0.589,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8075, ipnet:40.64.0.0/10, country:US]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.995,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.996,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[uoguelph.ca]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.81)[ipnet: 40.64.0.0/10(-1.97), asn: 8075(-2.02), country: US(-0.08)]; RCVD_IN_DNSWL_NONE(0.00)[46.67.107.40.list.dnswl.org : 127.0.3.0]; TO_DN_EQ_ADDR_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 01:06:03 -0000 It was my understanding that the NFSv4 working group believed that the requ= irement for the NFSv4 client to use a priviledged port# (< 1024) should not exist. As such, I coded the server to ignore the vfs.nfsd.nfs_privport sysctl and = allow the mount for NFSv4. PR#234106 has reported this as a compatibility issue w.r.t. the Linux NFS s= erver. The change to make the FreeBSD NFSv4 server use vfs.nfsd.nfs_privport is tr= ivial and I think being compatible with Linux is important (I see it as the defac= to standard NFS implementation these days). However, I am concerned that this change will result in a slight POLA viola= tion for sites with vfs.nfsd.nfs_privport set, but doing NFSv4 mounts that might= now fail. What do others think I should do? rick From owner-freebsd-current@freebsd.org Wed Dec 19 01:33:09 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 666F21346361 for ; Wed, 19 Dec 2018 01:33:09 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it1-f181.google.com (mail-it1-f181.google.com [209.85.166.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8EF5391781 for ; Wed, 19 Dec 2018 01:33:08 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it1-f181.google.com with SMTP id w18so6928020ite.1 for ; Tue, 18 Dec 2018 17:33:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=ERR4M/OI7VHbwhqX+Qs0jdhypoxIzMGxgMl+rvnZxBs=; b=XO+vL04/qLwYvfBY1tTqf0NW01F4dreWbIz/j85FM8lRBA2e/SOPpeVk/XzNbEk9ws YkXFqPyl7tvfLn4D7dqqlYLV3KGQbC+6QNdQLRiWLLLhS5tiaL0Bz5TM41Duy8MmPZys NSePH30cNZUyIod0tv2XAm+nDXNRvyomyz+521SM2+dKwTyvW7ULUvWfXHHRejghRYPo IDf2GWhqQJkKkYQE+VfRzwrpsHxaYvkBnRhPHiAxoHnwxkgYau92x/78Drk6bNWKWi66 dMYIq7jh40dljvMZhJkLnTkqaxfWtdpor5DUZbmwbQ4wXdhlvxjZ2VyIoRPmQW+YvZjL zs1A== X-Gm-Message-State: AA+aEWbMo0fFjkCCfS7/EftTwL7lLzJ62JyU+32s/kRNsXyMAwKHntpU QXYVb8a5GON0iLp32sXpbECb+6Q5 X-Google-Smtp-Source: AFSGD/VEKA16WUI7Pm7pEiE8ggmQiUcDCY70X0cdZvfjbahwqtKNcyEp08NhxAj0Sjg5DLY1PrZpHg== X-Received: by 2002:a24:16cc:: with SMTP id a195mr4957337ita.38.1545183181130; Tue, 18 Dec 2018 17:33:01 -0800 (PST) Received: from mail-it1-f175.google.com (mail-it1-f175.google.com. [209.85.166.175]) by smtp.gmail.com with ESMTPSA id b91sm2541541itd.26.2018.12.18.17.33.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Dec 2018 17:33:00 -0800 (PST) Received: by mail-it1-f175.google.com with SMTP id a6so7051971itl.4 for ; Tue, 18 Dec 2018 17:33:00 -0800 (PST) X-Received: by 2002:a24:b64a:: with SMTP id d10mr4999257itj.149.1545183180446; Tue, 18 Dec 2018 17:33:00 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Reply-To: cem@freebsd.org From: Conrad Meyer Date: Tue, 18 Dec 2018 17:32:49 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: possible POLA violation for NFS server to make it Linux compatible To: Rick Macklem Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 8EF5391781 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of csecem@gmail.com designates 209.85.166.181 as permitted sender) smtp.mailfrom=csecem@gmail.com X-Spamd-Result: default: False [-5.91 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[cem@freebsd.org]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.95)[-0.945,0]; FORGED_SENDER(0.30)[cem@freebsd.org,csecem@gmail.com]; IP_SCORE(-2.95)[ip: (-9.72), ipnet: 209.85.128.0/17(-3.59), asn: 15169(-1.38), country: US(-0.08)]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_NEQ_ENVFROM(0.00)[cem@freebsd.org,csecem@gmail.com]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[181.166.85.209.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[181.166.85.209.rep.mailspike.net : 127.0.0.17] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 01:33:09 -0000 On Tue, Dec 18, 2018 at 5:07 PM Rick Macklem wrote: > The change to make the FreeBSD NFSv4 server use vfs.nfsd.nfs_privport is trivial > and I think being compatible with Linux is important (I see it as the defacto > standard NFS implementation these days). > > What do others think I should do? Hi Rick, I think we should go ahead and honor nfs_privport. Best, Conrad From owner-freebsd-current@freebsd.org Wed Dec 19 06:50:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F09A9134D7E7; Wed, 19 Dec 2018 06:50:01 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26BD36C4C1; Wed, 19 Dec 2018 06:50:01 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-it1-f175.google.com (mail-it1-f175.google.com [209.85.166.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id DC0F41F864; Wed, 19 Dec 2018 06:50:00 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-it1-f175.google.com with SMTP id h65so7847523ith.3; Tue, 18 Dec 2018 22:50:00 -0800 (PST) X-Gm-Message-State: AA+aEWb9d9IJj5VPhyCpu4gJv/qMURmy9sNQJmadVV4IFjPqhGBJ/SB2 WfqLPus3J55rEC2CStDMkJG3iOEB1qdH6cGmYY4= X-Google-Smtp-Source: AFSGD/VOhsA4adaigEJ11jv/JUmSBn/tNwxMk2hQNju4DIc4op2NBvwTnRjfPmXSfHlM+ag0Zks4PD1VAxdcP+PLWIA= X-Received: by 2002:a02:94eb:: with SMTP id x98mr18169446jah.88.1545202200039; Tue, 18 Dec 2018 22:50:00 -0800 (PST) MIME-Version: 1.0 From: Matthew Macy Date: Tue, 18 Dec 2018 22:49:48 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: The future of ZFS in FreeBSD To: freebsd-fs , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 26BD36C4C1 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_SHORT(-0.96)[-0.964,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 06:50:02 -0000 The sources for FreeBSD's ZFS support are currently taken directly from Illumos with local ifdefs to support the peculiarities of FreeBSD where the Solaris Portability Layer (SPL) shims fall short. FreeBSD has regularly pulled changes from Illumos and tried to push back any bug fixes and new features done in the context of FreeBSD. In the past few years the vast majority of new development in ZFS has taken place in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced that they will be moving to ZoL https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means that there will be little to no net new development of Illumos. While working through the git history of ZoL I have also discovered that many races and locking bugs have been fixed in ZoL and never made it back to Illumos and thus FreeBSD. This state of affairs has led to a general agreement among the stakeholders that I have spoken to that it makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf has graciously encouraged me to add FreeBSD support directly to ZoL https://github.com/zfsonfreebsd/ZoF so that we might all have a single shared code base. A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port Before it can be committed some additional functionality needs to be added to the FreeBSD opencrypto framework. These can be found at https://reviews.freebsd.org/D18520 This port will provide FreeBSD users with multi modifier protection, project quotas, encrypted datasets, allocation classes, vectorized raidz, vectorized checksums, and various command line improvements. Before ZoF can be merged back in to ZoL several steps need to be taken: - Integrate FreeBSD support into ZoL CI - Have most of the ZFS test suite passing - Complete additional QA testing at iX We at iX Systems need to port ZoL's EC2 CI scripts to work with FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. Being integrated in to their CI will mean that, among other things, most integration issues will be caught before a PR is merged upstream rather than many months later when it is MFVed into FreeBSD. I=E2=80=99m hoping to submit the PR to ZoL some time in January. This port will make it easy for end users on a range of releases to run the latest version of ZFS. Nonetheless, transitioning away from an Illumos based ZFS is not likely to be entirely seamless. The stakeholders I=E2=80=99ve spoken to all agree that this is the best path forward but some degree of effort needs to be made to accommodate downstream consumers. The current plan is to import ZoF and unhook the older Illumos based sources from the build on April 15th or two months after iX systems QA deems ZoF stable - which ever comes later. The Illumos based sources will be removed some time later - but well before 13. This will give users a 3 month period during which both the port and legacy Illumos based ZFS will be available to users. Pools should interoperate between ZoF and legacy provided the user does not enable any features available only in ZoF. We will try to accommodate any downstream consumers in the event that they need that date pushed back. We ask that any downstream consumers who are particularly sensitive to changes start testing the port when it is formally announced and report back any issues they have. I will do my best to ensure that this message is communicated to all those who it may concern. However, I can=E2=80=99t ensure that everyone reads these lists. T= hat is the responsibility of -CURRENT users. -M From owner-freebsd-current@freebsd.org Wed Dec 19 07:49:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CD10134EFB9; Wed, 19 Dec 2018 07:49:18 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CFB56E3F5; Wed, 19 Dec 2018 07:49:17 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pf1-x430.google.com with SMTP id c123so9468163pfb.0; Tue, 18 Dec 2018 23:49:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YxZATs9eih0qlUdDiJN17xxyi6ockrN7+QperSHg7Es=; b=A77ywLzRjUFednjbLZ5Tx90LahEcwkADQtZh2JF6jEffSC3ChK+c1RcsF+hqiDHX7A anvtW00OPKmcz3gVAlVDiZtnfCVlvcmKdP0l7bhi53c5h9k2fvyxOJJfUaUNC3Nzhati kv8jwJWHmNbTOgGsZWuSMk7gBzG4LlL4oKtGrX8rM/UmbtmzYlMfKCvTZcNJSjXAbE/F IPWMuzyUHrKh5E0kolwbmkWkFy5JiWZ9WeN3GLwg5ypD9GTyFL+4K0mN7DcL/AeOocsc saAkiW5HrPaQMTXWeDdTEbwYHKl4kJWjFAzWx8MOakpok0qwuGW64JjfLnEYI0QWSbaG a0uQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YxZATs9eih0qlUdDiJN17xxyi6ockrN7+QperSHg7Es=; b=oUXcnnVMDjPAP8inkQcROPGTkBYT5QO37TwBh6UFdBnh0umr+N2GzQiUGdx+287eRW C6mT6L8tp6K3CAmwwwvdmbeeIDRh1XW+g3toRE+qGXh+5/QcH6iHO120blDMC6bQ7U7H KEkAvrtc9V4kHrWuq0Dk9sppMCN+R6Duc8hIb8FFNmpwinezhFACRfJWIrGVHwAqLBSO 0sqlgyG+AxAJfEJToep8LKbOsBGhu7EIGKn7Ge8YSs9j+kUW1Zlj1/M9CuaGrTZsF89b PuE9uN1w6kCaQAMm10MrzCNxzWt15lI0w7A6wYAlau5dGmT5g5JY2ed9gZC3pky9AUx+ y4YQ== X-Gm-Message-State: AA+aEWYLsUp81ovGis+F8JcE5sf598ckjVL1/UuTBqUN3OOh60Z0a+DS H78Js2ELuM4Ttu/oEKT4+Et9ATKw X-Google-Smtp-Source: AFSGD/UNeqrTFV84LIZ7kkpM5G4kt3vl+imi5naYsM94ELRl5MMmZHw5oYF1QNpFu15hqf5ECIKQSQ== X-Received: by 2002:a63:5402:: with SMTP id i2mr17787893pgb.79.1545205755990; Tue, 18 Dec 2018 23:49:15 -0800 (PST) Received: from [192.168.20.7] (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id m20sm18816651pgv.93.2018.12.18.23.49.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Dec 2018 23:49:15 -0800 (PST) From: Enji Cooper Message-Id: <9C23F0C0-DEF7-45A4-ADEF-58A00F9714D8@gmail.com> Content-Type: multipart/signed; boundary="Apple-Mail=_5B9C960B-5159-4A51-ACDD-81A425A795AA"; protocol="application/pgp-signature"; micalg=pgp-sha256 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: The future of ZFS in FreeBSD Date: Tue, 18 Dec 2018 23:49:13 -0800 In-Reply-To: Cc: freebsd-fs , freebsd-current To: Matthew Macy References: X-Mailer: Apple Mail (2.3445.9.1) X-Rspamd-Queue-Id: 4CFB56E3F5 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=A77ywLzR; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::430 as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com X-Spamd-Result: default: False [-6.11 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MV_CASE(0.50)[]; HAS_ATTACHMENT(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-0.86)[-0.861,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; IP_SCORE(-0.64)[ipnet: 2607:f8b0::/32(-1.74), asn: 15169(-1.38), country: US(-0.08)]; RCVD_IN_DNSWL_NONE(0.00)[0.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 07:49:18 -0000 --Apple-Mail=_5B9C960B-5159-4A51-ACDD-81A425A795AA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hello Matthew, I appreciate the long write up, as someone who still uses FreeBSD ZFS on = my NAS box and knowing some of the history with ZFS on *Solaris, etc. = Something like this was bound to happen with post the Oracle buyout. > On Dec 18, 2018, at 10:49 PM, Matthew Macy wrote: >=20 > The sources for FreeBSD's ZFS support are currently taken directly > from Illumos with local ifdefs to support the peculiarities of FreeBSD > where the Solaris Portability Layer (SPL) shims fall short. FreeBSD > has regularly pulled changes from Illumos and tried to push back any > bug fixes and new features done in the context of FreeBSD. In the past > few years the vast majority of new development in ZFS has taken place > in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced > that they will be moving to ZoL > https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means > that there will be little to no net new development of Illumos. While > working through the git history of ZoL I have also discovered that > many races and locking bugs have been fixed in ZoL and never made it > back to Illumos and thus FreeBSD. This state of affairs has led to a > general agreement among the stakeholders that I have spoken to that it > makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf > has graciously encouraged me to add FreeBSD support directly to ZoL > https://github.com/zfsonfreebsd/ZoF so that we might all have a single > shared code base. >=20 > A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port > Before it can be committed some additional functionality needs to be > added to the FreeBSD opencrypto framework. These can be found at > https://reviews.freebsd.org/D18520 >=20 > This port will provide FreeBSD users with multi modifier protection, > project quotas, encrypted datasets, allocation classes, vectorized > raidz, vectorized checksums, and various command line improvements. >=20 > Before ZoF can be merged back in to ZoL several steps need to be = taken: > - Integrate FreeBSD support into ZoL CI > - Have most of the ZFS test suite passing > - Complete additional QA testing at iX Can you please describe the testing process that will be employed to = verify the sanity of the ZoL on FreeBSD port? Should other large = companies who use ZFS on FreeBSD (Panzura?) chime in and the ZFS on = FreeBSD community (as a whole) collaborate to better suss out issues = with the ZoL port? > We at iX Systems need to port ZoL's EC2 CI scripts to work with > FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. > Being integrated in to their CI will mean that, among other things, > most integration issues will be caught before a PR is merged upstream > rather than many months later when it is MFVed into FreeBSD. I=E2=80=99m= > hoping to submit the PR to ZoL some time in January. Could you please better describe this, in particular provide pointers to = any scripts that might be executed with the ZoL port? > This port will make it easy for end users on a range of releases to > run the latest version of ZFS. Nonetheless, transitioning away from an > Illumos based ZFS is not likely to be entirely seamless. The > stakeholders I=E2=80=99ve spoken to all agree that this is the best = path > forward but some degree of effort needs to be made to accommodate > downstream consumers. The current plan is to import ZoF and unhook the > older Illumos based sources from the build on April 15th or two months > after iX systems QA deems ZoF stable - which ever comes later. The > Illumos based sources will be removed some time later - but well > before 13. This will give users a 3 month period during which both the > port and legacy Illumos based ZFS will be available to users. Pools > should interoperate between ZoF and legacy provided the user does not > enable any features available only in ZoF. We will try to accommodate > any downstream consumers in the event that they need that date pushed > back. We ask that any downstream consumers who are particularly > sensitive to changes start testing the port when it is formally > announced and report back any issues they have. I will do my best to > ensure that this message is communicated to all those who it may > concern. However, I can=E2=80=99t ensure that everyone reads these = lists. That > is the responsibility of -CURRENT users. As a thought: is there a way for the ZoL port to run in parallel with = the non-ZoL port, kind of like in an audit/read-only/verify-only mode? Thanks so much, -Enji --Apple-Mail=_5B9C960B-5159-4A51-ACDD-81A425A795AA Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE5bk3FaGcY5rvqmb79YOpJmkwhhUFAlwZ9/kACgkQ9YOpJmkw hhXeBA//aK5RivUGqkKcORtDQ+P+l/0jXGs0lE42C7Yo89QO3QXnfM2po7PL/ZFV GaZGc8J+LIsiM2T48lx1u9S8qVbFRhdSbOnQKRFgm4ouQVJJUKiSCFLdugP2ADG4 q/EmRaO6tPo5Dc1XeyONahLymH/izPv0E97ua+HHTG2LSpe3uG0Wq4HMVGvqFklS b5Zy1HfNmBD8MxklHe6WDaCAtyns5l/zrNrIH8J3p9votYJ8zjJy3FMcXpu0BqSy 6eohgGykDtG/rL3BjgKaIi1JtSjZ/LBOJtkwM+owagBpnFvBoUHiem7dWxYuzosc 9NoFppsPflnAS3OC+2xwLg9ZtPcsOlDg88y9iChRBZYG/Lit6lBYxbjYC7E8GgFO ceqstQTgjkRTAe3+C4tGD0thI9DcjtUX5a3zoeu0glH8KcNDLAPy+ovqY8UaY4CK k18rVpk/j2pI7lmfPBZssuJop0idcJ6dUW+bicN1XsJZgdrzAIQQpqdrwjON35Ho bmseHWTQbhlit0+I+/HYchM1j1oAwdizuNF2MmMJGWrb/fiDqWp6n55kA1zmnTHV F7/v0qS4zqeyxq0zJrk177wb/ZhA/GcFpi+wAJ8+a4vEKFzkXgeYnmik9BucOplB ecjdqN1CsFR5E+PiVTUSk9dtoP7pUBVqvJjLC+EuYn212AO9syQ= =ypW9 -----END PGP SIGNATURE----- --Apple-Mail=_5B9C960B-5159-4A51-ACDD-81A425A795AA-- From owner-freebsd-current@freebsd.org Wed Dec 19 07:52:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4483B134F246 for ; Wed, 19 Dec 2018 07:52:48 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C71656E80C for ; Wed, 19 Dec 2018 07:52:46 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.183.38.10]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MTeVY-1gzowv2JCy-00QVC0 for ; Wed, 19 Dec 2018 08:52:37 +0100 Date: Wed, 19 Dec 2018 08:52:04 +0100 From: "O. Hartmann" To: FreeBSD CURRENT Subject: /usr/doc can not be build neither can it be installed Message-ID: <20181219085231.6f89aead@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:F/Z7WzdmJzZSMY+aChAtJFEfgy5AU/7AGuuo+e7yHOhnlSBXS2M Wag/k6tj+xW/hp+i5QbBeLXs0fw4F4oMLF8YdoV7VlDj6R92+6m+DYfhcIuKTJfKzkhZan6 8AWhQ2ASfOdx0gLAs83dQEL+ejXqW5I4F+8Y7KvTv/pWWqW4KeC6IGz9YPnvzhLWpYq11sR hZD6zUmGIVDcDl7H/AXiw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:uYxtpQExtyU=:8zlRT0hTqTolzXXW2Kt8Gb dyaxGro4zsSOULpo3KGQfK7HhwpbSIRa12xAxE9/f/LYkoXu+c7j7oNqb+mtW6mE7xhE1cG7Z guYyitb7qFcXhd79USgPe8A82c50wLizXrvM+iE506TpdK/fAVxMB7AUIWKZXQ5JrZu1MfJ3Q uq1i4RVo0SvUIzVmz4Qjn882hwUZbPbULd5fv5icsJU7o9sxZlolQP9ioS7CAvM7GqpFaMkbR FOht64XII7V9TCgZRJ/80O+wzwXM0B0mc//OosT0sDrVxefjMfeFXWBLVde3la6JeMib1o14P F46PP5DDAskIeHUI9x1Tyy9PSV2hXe7kM5Jg+cz+fmmiKi4D3rBQfpUdKppPBqVm7AhQUyZdl DE7o6oxaf0S8cc+r37BaQenjYgJSa/L6ZNLlQsEsjwd7rizjeYs/KxzU0SmEmT6EscoX2K6sw Cbdsa3/h4cy8MSYXEr0Ii1zimzcf0iOpRvfuX7ygX5zvYpF9il/BBXGKFZDSLZZMGtXMsIItz dsP0/rnPRzHAT2lt5fvEjQJX5fq5L+uxIZsBWn3JBHvmXuXTAJ+Y4bBxkEAuwQrqtkzHSaSc1 WA5meZeg2IGX/sBV1Za/LApSnfmVdV5GA0C6CxfvhZTt7+JskIM2cgES78JbdiAYo5WX7khct OvRqn0HDUNfFpmrjYWHOHqkMS/ov0wLy9iiKvYOHszECKLesaPWbc/y4hwvg0ySRCF7ztnry9 yeapB43mdB06pViyCxurVKWEtXjGkvCEck6Ssmu9O+0N5lGJDYW78ybdU6uUzy63hoU1SCswt 0am/oMFO4UhKy0QDj7lngfPvEHTZFGZBGDqG3vB/E+IVECSoZXq8mw/yzhdJk+yAiKC769X2j OrK8rQEvzPluCyJPoXdGXR2xfLF3/ty/wD84UesMa6cP9xViJg4ANbu7CLRaBtTe1tjQ+tHUk nKoCXcQjgxg== X-Rspamd-Queue-Id: C71656E80C X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.47 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[mx01.gmx.net,mx00.gmx.net]; MIME_BASE64_TEXT(0.10)[]; NEURAL_HAM_SHORT(-0.76)[-0.763,0]; RECEIVED_SPAMHAUS_PBL(0.00)[10.38.183.77.zen.spamhaus.org : 127.0.0.10]; RCVD_IN_DNSWL_LOW(-0.10)[20.17.227.212.list.dnswl.org : 127.0.3.1]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.91)[-0.910,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.97)[-0.972,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[walstatt.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.72)[ip: (-3.82), ipnet: 212.227.0.0/16(-0.31), asn: 8560(0.54), country: DE(-0.01)]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 07:52:48 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMjU2DQoNCkhlbGxv IEZyZWVCU0QgdXNlcnMgb3V0IHRoZXJlLg0KDQpNeSBsYXN0IGJ1aWxkIGFuZCB1cGRhdGUgb2Yg L3Vzci9kb2Mgd2FzIGVuZCBvZiBNYXkgMjAxNzsgc2luY2UgdGhlbiBhbnkgYXR0ZW1wdCBidWls ZGluZw0KdGhlIGRvYyBmcm9tIC91c3IvZG9jIGZhaWxlZCBvbiAxMi1DVVJSRU5UIHRvIDEyLVNU QUJMRSBhbmQgbm93IG9uIDEzLUNVUlJFTlQuDQoNCkkgYmVsaWV2ZSBhbGwgdGhlIHJlcXVpcmVk IHBvcnRzIChmb2xsb3dpbmcgdGhlIGluc3RydWN0aW9ucyBmcm9tIGZkcC1wcmltZXIgYW5kIG90 aGVyDQppbnN0cnVjdGlvbnMgZ2l2ZW4gYnkgdGhlIG9mZmljaWFsIHdlYiBzaXRlcyBwcm92aWRp bmcgbmV3ZXN0IGRvY3MpIGFyZSB1cCB0byBkYXRlIGFuZA0KdGhlIC91c3IvZG9jIHRyZWUgaXMg YWxzbyBhdCBpdHMgbW9zdCByZWNlbnQgcmV2aXNpb24gKHVzaW5nIHN2bik6DQoNCiMgc3ZuIGlu Zm8NClBhdGg6IC4NCldvcmtpbmcgQ29weSBSb290IFBhdGg6IC91c3IvZG9jDQpVUkw6IGh0dHBz Oi8vc3ZuLmZyZWVic2Qub3JnL2RvYy9oZWFkDQpSZWxhdGl2ZSBVUkw6IF4vaGVhZA0KUmVwb3Np dG9yeSBSb290OiBodHRwczovL3N2bi5mcmVlYnNkLm9yZy9kb2MNClJlcG9zaXRvcnkgVVVJRDog YzJlODc3NGYtYzQ5Zi1lMTExLWI0MzYtODYyYjJiYmM4OTU2DQpSZXZpc2lvbjogNTI2OTcNCk5v ZGUgS2luZDogZGlyZWN0b3J5DQpTY2hlZHVsZTogbm9ybWFsDQpMYXN0IENoYW5nZWQgQXV0aG9y OiByeXVzdWtlDQpMYXN0IENoYW5nZWQgUmV2OiA1MjY5Nw0KTGFzdCBDaGFuZ2VkIERhdGU6IDIw MTgtMTItMTggMTI6NDk6MTYgKzAxMDAgKFR1ZSwgMTggRGVjIDIwMTgpDQoNCkFwYXJ0IGZyb20g YW55IG90aGVyIGxhbmd1YWdlIChpLmUuIEdlcm1hbikgSSdkIGV4cGVjdCB0aGF0IHRoZSBlbl9V UyB2ZXJzaW9uIHdvdWxkIGJ1aWxkDQphdCBsZWFzdCwgYnV0IHdoZW5ldmVyIEkgaXNzdWU6DQoN CmNkIC91c3IvZG9jDQptYWtlIGNsZWFuDQptYWtlIHVwZGF0ZQ0KbWFrZSBhbGwNCg0KdGhlIGJ1 aWxkIGVuZHMgdXAgaW4gDQoNClsuLi5dDQoNCmVncmVwOiBjaGFwdGVycy5lbnQ6IE5vIHN1Y2gg ZmlsZSBvciBkaXJlY3RvcnkNCmVudg0KWE1MX0NBVEFMT0dfRklMRVM9ImZpbGU6Ly8vdXNyL29i ai91c3IvZG9jL2VuX1VTLklTTzg4NTktMS9ib29rcy9oYW5kYm9vay9jYXRhbG9nLWN3ZC54bWwN CmZpbGU6Ly8vdXNyL2RvYy9lbl9VUy5JU084ODU5LTEvc2hhcmUveG1sL2NhdGFsb2cueG1sDQpm aWxlOi8vL3Vzci9kb2Mvc2hhcmUveG1sL2NhdGFsb2cueG1sDQpmaWxlOi8vL3Vzci9sb2NhbC9z aGFyZS94bWwvY2F0YWxvZyIgL3Vzci9sb2NhbC9iaW4veG1sbGludCAtLW5vbmV0IC0tbm9lbnQg LS12YWxpZA0KLSAtLWRyb3BkdGQgLS14aW5jbHVkZSAvdXNyL2RvYy9lbl9VUy5JU084ODU5LTEv Ym9va3MvaGFuZGJvb2svYm9vay54bWwgPg0KYm9vay5wYXJzZWQueG1sLnRtcCB3YXJuaW5nOiBm YWlsZWQgdG8gbG9hZCBleHRlcm5hbCBlbnRpdHkNCiIvdXNyL2RvYy9lbl9VUy5JU084ODU5LTEv Ym9va3MvaGFuZGJvb2svbWlycm9ycy54bWwuZnRwLmluZGV4LmluYyIgL3Vzci9kb2MvZW5fVVMu SVNPODg1OS0xL2Jvb2tzL2hhbmRib29rL21pcnJvcnMvY2hhcHRlci54bWw6MTAwOg0KcGFyc2Vy IGVycm9yIDogRmFpbHVyZSB0byBwcm9jZXNzIGVudGl0eSBjaGFwLm1pcnJvcnMuZnRwLmluZGV4 LmluYw0KJmNoYXAubWlycm9ycy5mdHAuaW5kZXguaW5jOw0KXiAvdXNyL2RvYy9lbl9VUy5JU084 ODU5LTEvYm9va3MvaGFuZGJvb2svbWlycm9ycy9jaGFwdGVyLnhtbDoxMDA6IHBhcnNlciBlcnJv ciA6IEVudGl0eQ0KJ2NoYXAubWlycm9ycy5mdHAuaW5kZXguaW5jJyBub3QgZGVmaW5lZCAmY2hh cC5taXJyb3JzLmZ0cC5pbmRleC5pbmM7IF4gd2FybmluZzogZmFpbGVkDQp0byBsb2FkIGV4dGVy bmFsIGVudGl0eQ0KIi91c3IvZG9jL2VuX1VTLklTTzg4NTktMS9ib29rcy9oYW5kYm9vay9taXJy b3JzLmxhc3Rtb2QuaW5jIiAvdXNyL2RvYy9lbl9VUy5JU084ODU5LTEvYm9va3MvaGFuZGJvb2sv bWlycm9ycy9jaGFwdGVyLnhtbDoxMDI6DQpwYXJzZXIgZXJyb3IgOiBGYWlsdXJlIHRvIHByb2Nl c3MgZW50aXR5IGNoYXAubWlycm9ycy5sYXN0bW9kLmluYw0KJmNoYXAubWlycm9ycy5sYXN0bW9k LmluYzsNCl4gL3Vzci9kb2MvZW5fVVMuSVNPODg1OS0xL2Jvb2tzL2hhbmRib29rL21pcnJvcnMv Y2hhcHRlci54bWw6MTAyOiBwYXJzZXIgZXJyb3IgOiBFbnRpdHkNCidjaGFwLm1pcnJvcnMubGFz dG1vZC5pbmMnIG5vdCBkZWZpbmVkICZjaGFwLm1pcnJvcnMubGFzdG1vZC5pbmM7DQoNClsuLi5d DQoNCk15IGZpcnN0IGNvdW50ZXJtZWFzdXJlIHdhcyB0byByZWNvbXBpbGUvcmVpbnN0YWxsIGV2 ZXJ5IHBvcnQgcG9zc2libHkgaW52b2x2ZWQsIGJ1dCB0aGF0DQpkaWQgbm90IHJlc29sdmUgdGhl IHByb2JsZW0uDQoNCkEgc2ltaWxhciBzaXR1YXRpb24gaXMgd2l0aCBwb3VkcmllcmUgYnVpbGRz IGFuZCB0cmFkaXRpb25hbCBidWlsZHMgb2YgcG9ydHMNCm1pc2MvZnJlZWJzZC1kb2MtZW4gYW5k IG1pc2MvZnJlZWJzZC1kb2MtZGUuIFRoZXkgZW5kIHVwIGluIGEgc2ltaWxhciBmYWlsdXJlIG9u IGFsbA0Kc3lzdGVtcyBJJ3ZlIHJ1bm5pbmcgRkJTRCAxMy1DVVJSRU5UIGFuZCAxMi1TVEFCTEUg c28gZmFyLg0KDQpDYW4gc29tZW9uZSBwbGVhc2UgbG9vayBpbnRvIHRoaXMgYW5kIGZpeCB0aGUg cHJvYmxlbSBvciBwb2ludCBtZSB0byBteSBtaXN0YWtlPyBJJ20gb3V0DQpvZiBjbHVlcy4NCg0K VGhhbmtzIGluIGFkdmFuY2UgYW5kIGtpbmQgcmVnYXJkcywNCg0KTy4gSGFydG1hbm4NCg0KLSAt LSANCk8uIEhhcnRtYW5uDQoNCkljaCB3aWRlcnNwcmVjaGUgZGVyIE51dHp1bmcgb2RlciDDnGJl cm1pdHRsdW5nIG1laW5lciBEYXRlbiBmw7xyDQpXZXJiZXp3ZWNrZSBvZGVyIGbDvHIgZGllIE1h cmt0LSBvZGVyIE1laW51bmdzZm9yc2NodW5nICjCpyAyOCBBYnMuIDQgQkRTRykuDQotLS0tLUJF R0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KDQppSFVFQVJZSUFCMFdJUVN5OElCeEFQRGtxVkJhVEo0 NE4xWlpQYmE1UndVQ1hCbjR2d0FLQ1JBNE4xWlpQYmE1DQpSeUU1QVFEUkRWeDFnZUpsZUt0MW8r WnZWbUo0THllMmhKblFJYnRXNHZWeExGNlVtZ0QvVWJGMUM4T2FUTDVIDQpENkFGcW0xVGwrUjhp SkFqVW1JT0R0bjFObDFLdWdNPQ0KPS93N2MNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K From owner-freebsd-current@freebsd.org Wed Dec 19 08:35:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 952CD1350202; Wed, 19 Dec 2018 08:35:28 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D0176FB69; Wed, 19 Dec 2018 08:35:28 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-it1-f174.google.com (mail-it1-f174.google.com [209.85.166.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 140E369B; Wed, 19 Dec 2018 08:35:28 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-it1-f174.google.com with SMTP id g85so8459395ita.3; Wed, 19 Dec 2018 00:35:28 -0800 (PST) X-Gm-Message-State: AA+aEWaWw6echKikPcvFd6zEKLVqI+4J/Obb6EGc+Oe6kWcH1tKPEDHL N/jDA68UtfKyZkeq2he6FwsiZmiYK6Z+IIZLTxU= X-Google-Smtp-Source: AFSGD/Xx9pI73/QS6uetP/Df1kR6ujk+9O9i6ahs72BMZ0oHhSvZJIcM2EGmvJ4/VbNDWMWkl/VDiYUXNoFHupWLbfY= X-Received: by 2002:a02:8904:: with SMTP id o4mr18360276jaj.35.1545208527463; Wed, 19 Dec 2018 00:35:27 -0800 (PST) MIME-Version: 1.0 References: <9C23F0C0-DEF7-45A4-ADEF-58A00F9714D8@gmail.com> In-Reply-To: <9C23F0C0-DEF7-45A4-ADEF-58A00F9714D8@gmail.com> From: Matthew Macy Date: Wed, 19 Dec 2018 00:35:15 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Enji Cooper Cc: freebsd-fs , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 3D0176FB69 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.99)[-0.992,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 08:35:28 -0000 On Tue, Dec 18, 2018 at 11:49 PM Enji Cooper wrote: > > Hello Matthew, > > I appreciate the long write up, as someone who still uses FreeBSD ZFS on = my NAS box and knowing some of the history with ZFS on *Solaris, etc. Somet= hing like this was bound to happen with post the Oracle buyout. > > > On Dec 18, 2018, at 10:49 PM, Matthew Macy wrote: > > > > The sources for FreeBSD's ZFS support are currently taken directly > > from Illumos with local ifdefs to support the peculiarities of FreeBSD > > where the Solaris Portability Layer (SPL) shims fall short. FreeBSD > > has regularly pulled changes from Illumos and tried to push back any > > bug fixes and new features done in the context of FreeBSD. In the past > > few years the vast majority of new development in ZFS has taken place > > in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced > > that they will be moving to ZoL > > https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means > > that there will be little to no net new development of Illumos. While > > working through the git history of ZoL I have also discovered that > > many races and locking bugs have been fixed in ZoL and never made it > > back to Illumos and thus FreeBSD. This state of affairs has led to a > > general agreement among the stakeholders that I have spoken to that it > > makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf > > has graciously encouraged me to add FreeBSD support directly to ZoL > > https://github.com/zfsonfreebsd/ZoF so that we might all have a single > > shared code base. > > > > A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port > > Before it can be committed some additional functionality needs to be > > added to the FreeBSD opencrypto framework. These can be found at > > https://reviews.freebsd.org/D18520 > > > > This port will provide FreeBSD users with multi modifier protection, > > project quotas, encrypted datasets, allocation classes, vectorized > > raidz, vectorized checksums, and various command line improvements. > > > > Before ZoF can be merged back in to ZoL several steps need to be taken: > > - Integrate FreeBSD support into ZoL CI > > - Have most of the ZFS test suite passing > > - Complete additional QA testing at iX > > Can you please describe the testing process that will be employed to veri= fy the sanity of the ZoL on FreeBSD port? Should other large companies who = use ZFS on FreeBSD (Panzura?) chime in and the ZFS on FreeBSD community (as= a whole) collaborate to better suss out issues with the ZoL port? The ZFS test suite itself provides ~80% coverage https://codecov.io/gh/zfsonlinux/zfs/branch/master - FreeBSD currently lacks equivalent gcov support, but presumably it would provide comparable coverage here. Andrew Turner has some form of kernel gcov support that he uses with syzkaller. However, I believe that it isn't sufficient for this purpose. ZoL requires that coverage only increase over time. If a change would decrease total coverage new tests have to be included with the change. There is a command called ztest which runs in user space that quickly covers a large percentage of the code base where it doesn't integrate directly with geom or VFS (disk access is emulated with files, kernel threads are emulated with pthreads, etc). ztest has been broken in HEAD for the past 2 years (it triggers an assertion failure), whereas it is not broken in ZoF. Joe Maloney is the head of QA at iX and can likely give you more detail on their approach to testing. This e-mail was an implicit request to Panzura to do whatever testing that they can. > > > We at iX Systems need to port ZoL's EC2 CI scripts to work with > > FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. > > Being integrated in to their CI will mean that, among other things, > > most integration issues will be caught before a PR is merged upstream > > rather than many months later when it is MFVed into FreeBSD. I=E2=80=99= m > > hoping to submit the PR to ZoL some time in January. > > Could you please better describe this, in particular provide pointers to = any scripts that might be executed with the ZoL port? The ZFS test suite is in ZoL under tests, it makes some Linux specific assumptions about paths to binaries like ksh etc and it appears to require some additional configuration options. I started fixing things before I decided to punt and ask that a porter at iX fix it so that I could focus on areas that make more sense for me to spend my time on. If it doesn't get handled I will of course go back to it. The CI scripts are not something I've looked at. My intention is again that the people who would be responsible for keeping them up at iX would close the loop. It's close to Christmas time right now and folks are inevitably preoccupied with family matters. I sent this mail in advance of resolving these details to give any outside stakeholders a heads up as far out as possible. "Shadow" stakeholders coming out of the wood work to cry foul only after disruptive changes have been made - in spite of advance notice having been given on the mailing list(s) - has been an issue in the past. In this instance I intend to keep posting updates to the list so that no one can claim that sufficient effort was not made. > > This port will make it easy for end users on a range of releases to > > run the latest version of ZFS. Nonetheless, transitioning away from an > > Illumos based ZFS is not likely to be entirely seamless. The > > stakeholders I=E2=80=99ve spoken to all agree that this is the best pat= h > > forward but some degree of effort needs to be made to accommodate > > downstream consumers. The current plan is to import ZoF and unhook the > > older Illumos based sources from the build on April 15th or two months > > after iX systems QA deems ZoF stable - which ever comes later. The > > Illumos based sources will be removed some time later - but well > > before 13. This will give users a 3 month period during which both the > > port and legacy Illumos based ZFS will be available to users. Pools > > should interoperate between ZoF and legacy provided the user does not > > enable any features available only in ZoF. We will try to accommodate > > any downstream consumers in the event that they need that date pushed > > back. We ask that any downstream consumers who are particularly > > sensitive to changes start testing the port when it is formally > > announced and report back any issues they have. I will do my best to > > ensure that this message is communicated to all those who it may > > concern. However, I can=E2=80=99t ensure that everyone reads these list= s. That > > is the responsibility of -CURRENT users. > > > As a thought: is there a way for the ZoL port to run in parallel with the= non-ZoL port, kind of like in an audit/read-only/verify-only mode? Only one zfs kernel module can be loaded at a time. The command line utilities can't coexist due to libzfs differences. The closest one could come to this would be to switch between boot environments with the different kmods and utilities and run zdb from one on the pools that had been managed by the other. -M From owner-freebsd-current@freebsd.org Wed Dec 19 15:29:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3208F1338D0E for ; Wed, 19 Dec 2018 15:29:53 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C9E385370; Wed, 19 Dec 2018 15:29:51 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id Zdn9gR1Oo8uQmZdnAgpXPN; Wed, 19 Dec 2018 08:29:49 -0700 X-Authority-Analysis: v=2.3 cv=XKpOtjpE c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=2ur7OfE09M0A:10 a=xfDLHkLGAAAA:8 a=hF2rLc1pAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=-TuVeBny641Y19tWTGwA:9 a=CjuIK1q_8ugA:10 a=iB5APFlFwgEA:10 a=IfaqVvZgccqrtc8gcwf2:22 a=O9OM7dhJW_8Hj9EqqvKN:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id 191EFC9; Wed, 19 Dec 2018 07:29:47 -0800 (PST) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id wBJFTVvs016135; Wed, 19 Dec 2018 07:29:31 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id wBJFTUL4016132; Wed, 19 Dec 2018 07:29:30 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201812191529.wBJFTUL4016132@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: cem@freebsd.org cc: Rick Macklem , freebsd-current Subject: Re: possible POLA violation for NFS server to make it Linux compatible In-Reply-To: Message from Conrad Meyer of "Tue, 18 Dec 2018 17:32:49 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Dec 2018 07:29:30 -0800 X-CMAE-Envelope: MS4wfNOfV13XbUL+nk2HezgqooqfxS7Zu/oHCCL4P1pVp78d0aSdoAZKIhkrKqkPhgr+1EN0WhrqEPLpK627psM7r8CdjzihmL7eb6X6h5Fw1WzBEVeeKftB F+O+WpPSomW+0u0IcXO1JZzABItws1sTPx3BFcslNDhh74jkovBVCYVDFZYiIQGU0NKW/X0qrU8TDs8RcaN35iwgVEf2R03VRYHGZ+mEH9+jrUL9b8GF1STc zpZKhH6yIlGTnITMfOdUuw== X-Rspamd-Queue-Id: 1C9E385370 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-4.95 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; TO_DN_SOME(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.98)[-0.981,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[13.134.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-2.26)[ip: (-6.59), ipnet: 64.59.128.0/20(-2.56), asn: 6327(-2.05), country: CA(-0.09)]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 15:29:53 -0000 In message , Conrad Meyer writes: > On Tue, Dec 18, 2018 at 5:07 PM Rick Macklem wrote: > > The change to make the FreeBSD NFSv4 server use vfs.nfsd.nfs_privport is tr > ivial > > and I think being compatible with Linux is important (I see it as the defac > to > > standard NFS implementation these days). > > > > What do others think I should do? > > Hi Rick, > > I think we should go ahead and honor nfs_privport. Agreed and an UPDATING entry. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Wed Dec 19 15:41:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD518133971B for ; Wed, 19 Dec 2018 15:41:42 +0000 (UTC) (envelope-from Scoobi_doo@yahoo.com) Received: from sonic307-3.consmr.mail.bf2.yahoo.com (sonic307-3.consmr.mail.bf2.yahoo.com [74.6.134.42]) (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 B164386203 for ; Wed, 19 Dec 2018 15:41:41 +0000 (UTC) (envelope-from Scoobi_doo@yahoo.com) X-YMail-OSG: CbmDYQMVM1ky1qXD4smDVmMGulLJODj61q2EFruZ24b3LBe0PqVqDOU7QYGkPt. gJQY8TKIhXs7dRs4eLx1PpkO2bjMFoqVaxqL1M.opYpSzcLNg_9FR_2KQ6QTBqd3VV.lfvyPnN2j W9bmCZ3CrLg4bxej..Vk4fX5ZIzTSoDF3ZpzC0bdcTaq9vxWbfS4C6LjlfiylM4Ek0g5mz4nvUG5 vgEJ3RrgW.Hji1ZDzHJ3YNYWt5c1VghoJV5sHRd4K_LEONXxO8e3SUQIC_MxodNKhW37ci2GHWoM qJfpOjGwCjTjumayGcONw060DxLsKHg3ti9nmyP4kvELN.OO01lRmLRKns0g1mO1PBAdCZZRdpIo ixMbTdmlEUMn3PPK_IWs8BI8PceT5AavolnXi4bbIXckmA00WrD.CxEavpw9409JA.TCFqQaiVxc CVY5L.kDXLcc_WzRiXULg27IHqZYnsyT65fDUZCscRQM4F9X1sNg6gy3G7wInpZtFitjriJ6FZFf r4WFqzfwKHFrId0OnrO70731Um.Fm3L29C8WiIZa5KlUWalUW2t7LcRrYR7R7dndh2lgOYUKToGh olfd3y2JdwEumKm82R5PTnHH9OSweNFjqFSPyYLY1v.DGGvZe_1xo2Mah15Sgw9uNYj700fPrgAn .mByajXZ588nYeDudIG8BoCgg0L3bB_yJJW7k07mopDki9l57QtypWDtfk_dkPDszOlJaTHZatO1 vpwkZrKif7g6vRQOylQlpR8s_AlPeSJZ4WtbiAZVBoZC26jwR7PWGc8e8NGGe1Tv2FEoUfcb0W8_ znBbLxvIMDf6PE7lTLXDPxPU9CPAPBQWLMamY257UCCcEl0oWytYvEEY7CZdxD59TpsRcj7BIryr Jpb91mU7AA4XXmJU3WZz1oSyBWfgJAbtXeDTkdNsKZLrvxz8glylKQx1GIYDt.6WkEX1aso0hzl7 PxLZQiV8bdazc9e0YDgCDZcHBZiB7JnIELge7bTPjUO6QTb.lMyd6CLnCCVvNdeLuTPtqZtHPCAF AxDJUXCGNeyH2hgiuIYtbFHE_9CFZJmNiDFkZiu2AgtACeXIjX48ukKrSBDykWchv9uek6UJ5xGA N_ZQ_qm6VTakb3ssHFupHBKe.WUp9 Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.bf2.yahoo.com with HTTP; Wed, 19 Dec 2018 15:41:40 +0000 Received: from 192.34.49.8 (EHLO [10.228.144.28]) ([192.34.49.8]) by smtp416.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 7d0bfc118b6fd34b6d2b3451d96b4160; Wed, 19 Dec 2018 15:41:35 +0000 (UTC) Subject: Re: Composite PCI devices in FreeBSD (mfd in Linux) To: John Baldwin , Ian Lepore Cc: FreeBSD CURRENT , Gleb Popov <6yearold@gmail.com> References: <1544473194.1860.340.camel@freebsd.org> <05b1183c-6117-267b-42f9-19e750adfa07@FreeBSD.org> From: Anthony Jenkins Message-ID: <02e30a11-4adf-3efb-d2ce-89c598bda9cf@yahoo.com> Date: Wed, 19 Dec 2018 10:41:34 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: <05b1183c-6117-267b-42f9-19e750adfa07@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: B164386203 X-Spamd-Bar: + X-Spamd-Result: default: False [1.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:26101, ipnet:74.6.128.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.15)[-0.152,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_SPAM_SHORT(0.60)[0.598,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(1.35)[ip: (3.82), ipnet: 74.6.128.0/21(1.67), asn: 26101(1.34), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.31)[0.313,0]; RCVD_IN_DNSWL_NONE(0.00)[42.134.6.74.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 15:41:43 -0000 On 12/10/18 3:57 PM, John Baldwin wrote: > On 12/10/18 12:19 PM, Ian Lepore wrote: >> On Mon, 2018-12-10 at 14:42 -0500, Anthony Jenkins wrote: >>> On 12/10/18 1:26 PM, John Baldwin wrote: >>>> On 12/10/18 9:00 AM, Anthony Jenkins wrote: >>>>> Hi all, >>>>> >>>>> I'm trying to port an Intel PCI I2C controller from Linux to >>>>> FreeBSD. >>>>> Linux represents this device as an MFD (multi-function device), >>>>> meaning >>>>> it has these "sub-devices" that can be handed off to other >>>>> drivers to >>>>> actually attach devices to the system.  The Linux "super" PCI >>>>> device is >>>>> the intel-lpss-pci.c, and the "sub" device is i2c-designware- >>>>> platdrv.c, >>>>> which represents the DesignWare driver's "platform" attachment to >>>>> the >>>>> Linux system.  FreeBSD also has a DesignWare I2C controller >>>>> driver, >>>>> ig4(4), but it only has PCI and ACPI bus attachment >>>>> implementations. >>>>> >>>>> I have a port of the Linux intel-lpss driver to FreeBSD, but now >>>>> I'm >>>>> trying to figure out the best way to give FreeBSD's ig4(4) driver >>>>> access >>>>> to my lpss(4) device.  I'm thinking I could add an ig4_lpss.c >>>>> describing >>>>> the "attachment" of an ig4(4) to an lpss(4).  Its probe() method >>>>> would >>>>> scan the "lpss" devclass for devices, and its attach() method >>>>> would >>>>> attach itself as a child to the lpss device and "grab" the >>>>> portion of >>>>> PCI memory and the IRQ that the lpss PCI device got. >>>>> >>>>> Is this the "FreeBSD Way (TM)" of handling this type of device? >>>>> If not, >>>>> can you recommend an existing FreeBSD driver I can model my code >>>>> after? >>>>> If my approach is acceptable, how do I fully describe the ig4(4) >>>>> device's attachment to the system?  Is simply making it a child >>>>> of >>>>> lpss(4) sufficient?  It's "kind of" a PCI device (it is >>>>> controlled via >>>>> access to a PCI memory region and an IRQ), but it's a sub-device >>>>> of an >>>>> actual PCI device (lpss(4)) attached to PCI. >>>>> How would my ig4_lpss attachment get information from the lpss(4) >>>>> driver >>>>> about what it probed? >>>> There are some existing PCI drivers that act as "virtual" busses >>>> that attach >>>> child devices.  For example, vga_pci.c can have drm, agp, and >>>> acpi_video >>>> child devices.  There are also some SMBus drivers that are also >>>> PCI-ISA >>>> bridges and thus create separate child devices. >>> Yeah I was hoping to avoid using video PCI devices as a model, as >>> complex as they've gotten recently.  I'll check out its bus glue >>> logic. >>> >>>> For a virtual bus like this, you need to figure out how your child >>>> devices >>>> will be enumerated.  A simple way is to let child devices use an >>>> identify >>>> routine that looks at each parent device and decides if a child >>>> device >>>> for that driver makes sense.  It can then add a child device in the >>>> identify routine. >>> Really an lpss parent PCI parent device can only have the following: >>> >>>   * one of {I2C, UART, SPI} controller >>>   * optionally an IDMA64 controller >>> >>> so I was thinking a child ig4(4) device would attach to lpss iff >>> >>>   * the lpss device detected an I2C controller >>>   * no other ig4 device is already attached >>> >>> I haven't fiddled with identify() yet, will look at that tonight. >>> >> If this is just another "bus" an ig4 instance can attach to, I'd think >> the recipe would be to add another DRIVER_MODULE() to ig4_iic.c naming >> ig4_lpss as the parent. Then add a new ig4_lpss.c modeled after the >> existing pci and acpi attachment code, its DRIVER_MODULE() would name >> lpss as parent, and its probe routine would return BUS_PROBE_NOWILDCARD >> (attach only if specifically added by the parent). >> >> Then there would be a new lpss driver that does the resource managment >> stuff mentioned above, and if it detects configuration for I2C it would >> do a device_add_child(lpssdev, "ig4_lpss", -1) followed by >> bus_generic_attach(). There'd be no need for identify() in the child in >> that case, I think. >> >> But take jhb's word over mine on any of this stuff, he's been around >> since the days when these mechanisms were all invented, whereas I tend >> to cut and paste that bus and driver attachment stuff in semi-ignorance >> when I'm working on drivers. > Doing the device_add_child in the parent driver's attach routine is also > fine instead of using an identify routine. It's mostly a matter of which > driver should be in charge of adding the child device (e.g. would you want > lpss self-contained or should the parent driver know about it explicitly). > > If you have an existing ig4 driver you are going to reuse, then you will > need to ensure you fake up the resource stuff so that the existing code > works perhaps, though that depends on where the bus_alloc_resource calls > occur. If they are in shared code you have to fake more. If they are in > the bus-specific attach routines, then you can just put lpss specific > logic in the lpss-specific attach routine. > >>>> To handle things like resources, you want to have >>>> bus_*_resource methods that let your child device use the normal >>>> bus_* >>>> functions to allocate resources.  At the simplest end you don't >>>> need to >>>> permit any sharing of BARs among multiple children so you can just >>>> proxy >>>> the requests in the "real" PCI driver.  (vga_pci.c does this)  If >>>> you need >>>> the BARs to be shared you have a couple of options such as just >>>> using a >>>> refcount on the BAR resource but letting multiple devices allocate >>>> the same >>>> BAR.  If you want to enforce exclusivity (once a device allocates >>>> part of >>>> a BAR then other children shouldn't be permitted to do so), then >>>> you will >>>> need a more complicated solution. >>> Another homework assignment for me - bus_*_resource methods. >>> >>> There are 2 or 3 mutually-exclusive sub-regions in the single memory >>> BAR: >>> >>>   * 0x000 - 0x200 : I2C sub-device registers >>>   * 0x200 - 0x300 : lpss and I2C sub-device registers >>>   * 0x800 - 0x1000 : IDMA sub-device registers (optional) > Hmm, so with this arrangement, you could either "cheat" and let all the > children just use the same BAR, or you could get fancy and create a > separate rman and sub-allocate resources from that for the different > ranges that you assign to each child. So I've cobbled together an ig4_lpss that looks like it attaches to my fake lpss "bus" and /seems/ to even call the ig4_iic code to attach to an iicbus, but I don't get a /dev/iic0 device node... ajenkins@ajenkins-delllaptop ~/Projects/freebsd-intel-lpss (master) $ dmesg | grep '\(lpss\|ig4\|iic\|pcib0\|ioapic\)' ... ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 10 vector 52 lpss0: at device 21.0 on pci0 pcib0: allocated type 3 (0xb2000000-0xb2000fff) for rid 10 of lpss0 lpss0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xb2000000 pcib0: matched entry for 0.21.INTA pcib0: slot 21 INTA hardwired to IRQ 16 lpss0: IRQ: 0 lpss0: Capabilities: 0x00000200 lpss0: MFP device type: I2C lpss1: at device 21.1 on pci0 pcib0: allocated type 3 (0xb2001000-0xb2001fff) for rid 10 of lpss1 lpss1: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xb2001000 pcib0: matched entry for 0.21.INTB pcib0: slot 21 INTB hardwired to IRQ 17 lpss1: IRQ: 0 lpss1: Capabilities: 0x00000201 lpss1: MFP device type: I2C lpss0: ig4iic_lpss_identify: Entered. lpss0: lpss_add_child: Entered order=0 name="ig4iic_lpss" unit=-1. ig4iic_lpss0: ig4iic_lpss_probe: Returning BUS_PROBE_NOWILDCARD. ig4iic_lpss0: ig4iic_lpss_probe: Returning BUS_PROBE_NOWILDCARD. ig4iic_lpss0 on lpss0 ig4iic_lpss0: ig4iic_lpss_attach: Entered. lpss0: lpss_alloc_resource: Entered. lpss0: lpss_alloc_resource: Returning memory resource 0x0xfffff80005308100. ig4iic_lpss0: ig4iic_lpss_attach: Got memory resource. lpss0: lpss_alloc_resource: Entered. lpss0: lpss_alloc_resource: Returning IRQ resource 0x0xfffff80005308100. ig4iic_lpss0: ig4iic_lpss_attach: Got interrupt resource. ig4iic_lpss0: ig4iic_attach: Entered. ig4iic_lpss0: ig4iic_start: Entered. ig4iic_lpss0: ig4iic_attach: Returning 0. ig4iic_lpss0: ig4iic_lpss_attach: Returning 0. lpss1: ig4iic_lpss_identify: Entered. lpss1: lpss_add_child: Entered order=0 name="ig4iic_lpss" unit=-1. ig4iic_lpss1: ig4iic_lpss_probe: Returning BUS_PROBE_NOWILDCARD. ig4iic_lpss1: ig4iic_lpss_probe: Returning BUS_PROBE_NOWILDCARD. ig4iic_lpss1 on lpss1 ig4iic_lpss1: ig4iic_lpss_attach: Entered. lpss1: lpss_alloc_resource: Entered. lpss1: lpss_alloc_resource: Returning memory resource 0x0xfffff80005308000. ig4iic_lpss1: ig4iic_lpss_attach: Got memory resource. lpss1: lpss_alloc_resource: Entered. lpss1: lpss_alloc_resource: Returning IRQ resource 0x0xfffff80005308000. ig4iic_lpss1: ig4iic_lpss_attach: Got interrupt resource. ig4iic_lpss1: ig4iic_attach: Entered. ioapic0: routing intpin 17 (PCI IRQ 17) to lapic 0 vector 59 ig4iic_lpss1: ig4iic_start: Entered. ig4iic_lpss1: ig4iic_attach: Returning 0. ig4iic_lpss1: ig4iic_lpss_attach: Returning 0. In lpss, my bus_alloc_resource() just forwards the resource handles for the BAR and IRQ it acquired.  In earlier attempts I was hanging the box hard when I tried to call device_add_child() from lpss' attach method; I suspect I was getting into an infinite loop adding the same child. I'm not feeling too confident about the condition of the FreeBSD ig4 driver; the PCI attach code was calling pci_alloc_msi() wrong, passing a pointer to the rid (0) instead of a pointer to a count variable, and not passing bus_alloc_resource_any() an IRQ rid > 0 if it has an MSI.  I'd be happy(er) if ig4 created a /dev/iic0 node - I figured iicbus(4) took care of all that... https://github.com/ScoobiFreeBSD/freebsd-intel-lpss Anthony From owner-freebsd-current@freebsd.org Wed Dec 19 16:31:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4713D133BBD0 for ; Wed, 19 Dec 2018 16:31:39 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 092F188807 for ; Wed, 19 Dec 2018 16:31:38 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-ot1-x32d.google.com with SMTP id v23so19635550otk.9 for ; Wed, 19 Dec 2018 08:31:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=cPuAQaogYXEWkURGYic2nUqfsUFib1b9wz0LZwZEeVI=; b=kcFWAXxZ7wl7ViYFZK1s30H/x9w0xJTWqfJANuPO1S8xmV0O8c9EpU9bhxS9pKxUiA h2Wb91QicEz/QropBzNuuF3OZV5Q6s1p+A+iiISIWcxks4a+ouBx8MYT0ZmJzZje4gOT biKsZMwJsJMTCXJdJzPL/HxAdvEa1IRGkP8FLdNBNT1uTm15CEeuaMX1I/+fXZ/RkgTw psXe/1Apj87XqE4IujYGOZI7L1rAiEcdZ2dqikp8DdnIWY7bLmbF7hUs+iawJi8wtsIV DhEgoVKL1DVdusgcUB+GWX6Tpjrrck98N25Xw2HCuJR6qV2ckJho4ngNWCVJY/2FDRuZ ylCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=cPuAQaogYXEWkURGYic2nUqfsUFib1b9wz0LZwZEeVI=; b=T3o/2uT2m7Y0ywkbJKCDlsVSSRED2SnYO/Dj4tLjzQM/V2p8GMz3qMCLy/AEqSILmC XKqwdPykyQ/jN3d13swHXWoMvYZ9Sncf0zu6FPBBlbjeYpKXnA/tQaz4oOI1/YzlAbia I0idqZgfMY2iTiur8mEOTw2rsxmTBTPNOexScypENoVymrKHw3Rc8LQovQXiWNhqL4Lv aipIyOLXkqTZwrR4ydYz9bP4JuhG3eQDqXdTtKeALQddY6t8a4otcLPXneQsvQSsvxuw UNlvyG/gIonrU7QNtBqy/F5q5kk5jkhf/mxbtgd6JwiNGNTp3wMqhpBSogZfUe4fi7p+ bB4Q== X-Gm-Message-State: AA+aEWaVVcPPXiPwwUEmoQrcmI7lSZ7j8uguWsWmNscAM85Y2i6dytre wOq2BkmJLk5L+RiMzPEQ/XxNBSn6vrmPpA== X-Google-Smtp-Source: AFSGD/VsWFsJZrpM4UL1eBiWLxBEyZeAV76xSq+Dwa1Sv4Q7C7wQI0qq0T0iuLQmHid2v1B1w9+Ing== X-Received: by 2002:a9d:3b77:: with SMTP id z110mr5049525otb.352.1545237096850; Wed, 19 Dec 2018 08:31:36 -0800 (PST) Received: from mutt-hbsd ([185.100.87.129]) by smtp.gmail.com with ESMTPSA id k13sm16950451otj.19.2018.12.19.08.31.33 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 19 Dec 2018 08:31:36 -0800 (PST) Date: Wed, 19 Dec 2018 11:30:33 -0500 From: Shawn Webb To: Matthew Macy Cc: freebsd-fs , freebsd-current Subject: Re: The future of ZFS in FreeBSD Message-ID: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rlmvscpkcfr6pslq" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD mutt-hbsd 13.0-CURRENT FreeBSD 13.0-CURRENT HARDENEDBSD-13-CURRENT amd64 X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: NeoMutt/20180716 X-Rspamd-Queue-Id: 092F188807 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=hardenedbsd.org header.s=google header.b=kcFWAXxZ; spf=pass (mx1.freebsd.org: domain of shawn.webb@hardenedbsd.org designates 2607:f8b0:4864:20::32d as permitted sender) smtp.mailfrom=shawn.webb@hardenedbsd.org X-Spamd-Result: default: False [-2.17 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(0.00)[+ip6:2607:f8b0:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt1.aspmx.l.google.com]; DKIM_TRACE(0.00)[hardenedbsd.org:+]; NEURAL_HAM_SHORT(-0.91)[-0.915,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; IP_SCORE(-0.64)[ipnet: 2607:f8b0::/32(-1.75), asn: 15169(-1.39), country: US(-0.08)]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_XBL(3.00)[129.87.100.185.zen.spamhaus.org : 127.0.0.4]; R_DKIM_ALLOW(0.00)[hardenedbsd.org:s=google]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[hardenedbsd.org]; BAD_REP_POLICIES(0.10)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[d.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MID_RHS_NOT_FQDN(0.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 16:31:39 -0000 --rlmvscpkcfr6pslq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 18, 2018 at 10:49:48PM -0800, Matthew Macy wrote: > The sources for FreeBSD's ZFS support are currently taken directly > from Illumos with local ifdefs to support the peculiarities of FreeBSD > where the Solaris Portability Layer (SPL) shims fall short. FreeBSD > has regularly pulled changes from Illumos and tried to push back any > bug fixes and new features done in the context of FreeBSD. In the past > few years the vast majority of new development in ZFS has taken place > in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced > that they will be moving to ZoL > https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means > that there will be little to no net new development of Illumos. While > working through the git history of ZoL I have also discovered that > many races and locking bugs have been fixed in ZoL and never made it > back to Illumos and thus FreeBSD. This state of affairs has led to a > general agreement among the stakeholders that I have spoken to that it > makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf > has graciously encouraged me to add FreeBSD support directly to ZoL > https://github.com/zfsonfreebsd/ZoF so that we might all have a single > shared code base. >=20 > A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port > Before it can be committed some additional functionality needs to be > added to the FreeBSD opencrypto framework. These can be found at > https://reviews.freebsd.org/D18520 >=20 > This port will provide FreeBSD users with multi modifier protection, > project quotas, encrypted datasets, allocation classes, vectorized > raidz, vectorized checksums, and various command line improvements. >=20 > Before ZoF can be merged back in to ZoL several steps need to be taken: > - Integrate FreeBSD support into ZoL CI > - Have most of the ZFS test suite passing > - Complete additional QA testing at iX >=20 > We at iX Systems need to port ZoL's EC2 CI scripts to work with > FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. > Being integrated in to their CI will mean that, among other things, > most integration issues will be caught before a PR is merged upstream > rather than many months later when it is MFVed into FreeBSD. I???m > hoping to submit the PR to ZoL some time in January. >=20 > This port will make it easy for end users on a range of releases to > run the latest version of ZFS. Nonetheless, transitioning away from an > Illumos based ZFS is not likely to be entirely seamless. The > stakeholders I???ve spoken to all agree that this is the best path > forward but some degree of effort needs to be made to accommodate > downstream consumers. The current plan is to import ZoF and unhook the > older Illumos based sources from the build on April 15th or two months > after iX systems QA deems ZoF stable - which ever comes later. The > Illumos based sources will be removed some time later - but well > before 13. This will give users a 3 month period during which both the > port and legacy Illumos based ZFS will be available to users. Pools > should interoperate between ZoF and legacy provided the user does not > enable any features available only in ZoF. We will try to accommodate > any downstream consumers in the event that they need that date pushed > back. We ask that any downstream consumers who are particularly > sensitive to changes start testing the port when it is formally > announced and report back any issues they have. I will do my best to > ensure that this message is communicated to all those who it may > concern. However, I can???t ensure that everyone reads these lists. That > is the responsibility of -CURRENT users. Hey Matt, Thank you for your detailed and informative post. It really helps downstream consumers of FreeBSD. I'm curious what this means for OpenZFS. I was under the impression that OpenZFS was the upstream for all the ZFS implementations (sans Oracle). Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --rlmvscpkcfr6pslq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAlwaciUACgkQaoRlj1JF bu7GnxAAkKRQBJ1ypOD0J+FxS/K5fqXH+mBD2DW66/iU0EPcAsTZFPj5nhsCuhLL znBjvCH4nnMu1vYoTwn0Yeism1ioYz6EGxfdxVfyz/X+cOv1Bf9tGiKwvm5U8TvM AK2YIaRHL8lWLeQzMapJx5xm1PVPIo6FPyVOVZSCP0JetfJ96ahTPOOWcOozk8h6 vYurzIXnsA7IBxEy22/h3h1ZyJ4IxRFW81XAGsdQPdhWA2V2eBGka9UGisk5cgmZ vxRnZH/8RBjDaGNnzrpZBlND7Ukyu1PZeJmdF01wInB7ruTfDmdTYeQK2VMfmHOP feU70wyFI7AhVPQ2SbM1fUDVvwkG0kS1Q+qIX6X5EHqbOER9g0cUbphEYIvFpMQD ICr2m2LpeJGem1HMCtZb/j+rChRJtvKytIk60QC+lXDzhRhiR9irM7pfCNiJ1RW2 xCLhjEkCNtMYVw/5KpdqmN91GNBnp7BdhzKSKSW6xiB5CECWzEv9qexQlmxT7OzS 0bsg2EdYLc4C4YkL2fw2UF2y5oYUMI9niS7n0rRZpMbD8eTK6yhAlhHEBWDvhDUT c/ITYnduUf0yW39n9uQNQgYdauxnj8yJwK0eIQNFAIMgBxDZAgm+s0KmxAyCNg/P c8uSzZBPFdpHCBbeSybGCBEpABn9EULervJJ8KEFBeoaoNSqMvg= =IVGV -----END PGP SIGNATURE----- --rlmvscpkcfr6pslq-- From owner-freebsd-current@freebsd.org Wed Dec 19 17:53:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5BB7133E3EB; Wed, 19 Dec 2018 17:53:10 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fry.fubar.geek.nz (fry.fubar.geek.nz [139.59.165.16]) by mx1.freebsd.org (Postfix) with ESMTP id 2A1CF8BF81; Wed, 19 Dec 2018 17:53:07 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from [192.168.100.30] (unknown [185.201.60.232]) by fry.fubar.geek.nz (Postfix) with ESMTPSA id AF27A4E693; Wed, 19 Dec 2018 17:52:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fubar.geek.nz; s=mail; t=1545241947; bh=2jTW0oXQtVXSFTNoTNFg6fuGj3HRIfreps/0dhdiIJ8=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=pJutvXEZMl+P/UQlP83/gQq2JpAfrNBX/Nc8WCDliG0oGxh/Us68tMiK8in54H8NP eeizQf/NPaOXjckY2qyRhaW8o+4AsZjiU0dH5jcNdlOKkOKfPjd5+u+99nZJQjGz9b zqffgmGKO3p49JA8n8ZYey+DHAnjMrEfY5hz/LAPZeBqfQV5UmFQUb3UWU5zo2MKCT b0ga5VDyeQaXuLHcMC76WtiLaDWwYw0AFwTAkawISG4mDL8+QEq6VyUmp70onF9iiI kwcmHv6gRI2SdyelPAQLx4BtgMa4imTEKSlLb7WlWOcccRXN/kgoPrFfpYJPXRnPKE u61L/MMso0Y6PN75ImSfody/Z+fNY8PIn0sYOJ3nG9y9RCVdfYw72Yv8+Y/TH/g2/L 6JdSSEcErAVNZ8k0X8yw54S3QtKlPVrbgmube/YoUXW9YCR4dIVR3NSNJMP2jToi68 Y+3iVxrrlgQGUO1tsCoxRMsQCMhqO4WMKmOqUxFatS9p7sCnY89qwuedaIdsQTKc/D d+4po97KCPaMKzjI1F08jVlKe1JY2cN/O7fQdPAZniGqDYC8VKN0xw6rGwVhkBcxum NZ0XZ8QBskqE5cHZ9Asb0gR6fO3sHQZ2CZ+8apVlmliELiHcxGX6jxQJlzjulguGh9 RYTTdDi+2jwmLBV6GQ5JD554= From: Andrew Turner Message-Id: Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: The future of ZFS in FreeBSD Date: Wed, 19 Dec 2018 17:52:24 +0000 In-Reply-To: Cc: Enji Cooper , freebsd-fs , freebsd-current To: Matthew Macy References: <9C23F0C0-DEF7-45A4-ADEF-58A00F9714D8@gmail.com> X-Mailer: Apple Mail (2.3445.9.1) X-Rspamd-Queue-Id: 2A1CF8BF81 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=fubar.geek.nz header.s=mail header.b=pJutvXEZ; dmarc=pass (policy=none) header.from=fubar.geek.nz; spf=pass (mx1.freebsd.org: domain of andrew@fubar.geek.nz designates 139.59.165.16 as permitted sender) smtp.mailfrom=andrew@fubar.geek.nz X-Spamd-Result: default: False [3.25 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[fubar.geek.nz:s=mail]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_SPAM_SHORT(0.75)[0.752,0]; NEURAL_SPAM_MEDIUM(0.60)[0.604,0]; URI_COUNT_ODD(1.00)[11]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[fubar.geek.nz:+]; MX_GOOD(-0.01)[fry.fubar.geek.nz]; DMARC_POLICY_ALLOW(-0.50)[fubar.geek.nz,none]; NEURAL_SPAM_LONG(0.68)[0.679,0]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; IP_SCORE(0.63)[asn: 14061(3.22), country: US(-0.08)]; ASN(0.00)[asn:14061, ipnet:139.59.160.0/20, country:US]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 17:53:11 -0000 > On 19 Dec 2018, at 08:35, Matthew Macy wrote: >=20 > On Tue, Dec 18, 2018 at 11:49 PM Enji Cooper > wrote: >>=20 >> Hello Matthew, >>=20 >> I appreciate the long write up, as someone who still uses FreeBSD ZFS = on my NAS box and knowing some of the history with ZFS on *Solaris, etc. = Something like this was bound to happen with post the Oracle buyout. >>=20 >>> On Dec 18, 2018, at 10:49 PM, Matthew Macy = wrote: >>>=20 >>> The sources for FreeBSD's ZFS support are currently taken directly >>> from Illumos with local ifdefs to support the peculiarities of = FreeBSD >>> where the Solaris Portability Layer (SPL) shims fall short. FreeBSD >>> has regularly pulled changes from Illumos and tried to push back any >>> bug fixes and new features done in the context of FreeBSD. In the = past >>> few years the vast majority of new development in ZFS has taken = place >>> in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix = announced >>> that they will be moving to ZoL >>> https://www.delphix.com/blog/kickoff-future-eko-2018 This shift = means >>> that there will be little to no net new development of Illumos. = While >>> working through the git history of ZoL I have also discovered that >>> many races and locking bugs have been fixed in ZoL and never made it >>> back to Illumos and thus FreeBSD. This state of affairs has led to a >>> general agreement among the stakeholders that I have spoken to that = it >>> makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf >>> has graciously encouraged me to add FreeBSD support directly to ZoL >>> https://github.com/zfsonfreebsd/ZoF so that we might all have a = single >>> shared code base. >>>=20 >>> A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port >>> Before it can be committed some additional functionality needs to be >>> added to the FreeBSD opencrypto framework. These can be found at >>> https://reviews.freebsd.org/D18520 >>>=20 >>> This port will provide FreeBSD users with multi modifier protection, >>> project quotas, encrypted datasets, allocation classes, vectorized >>> raidz, vectorized checksums, and various command line improvements. >>>=20 >>> Before ZoF can be merged back in to ZoL several steps need to be = taken: >>> - Integrate FreeBSD support into ZoL CI >>> - Have most of the ZFS test suite passing >>> - Complete additional QA testing at iX >>=20 >> Can you please describe the testing process that will be employed to = verify the sanity of the ZoL on FreeBSD port? Should other large = companies who use ZFS on FreeBSD (Panzura?) chime in and the ZFS on = FreeBSD community (as a whole) collaborate to better suss out issues = with the ZoL port? >=20 > The ZFS test suite itself provides ~80% coverage > https://codecov.io/gh/zfsonlinux/zfs/branch/master = - FreeBSD currently > lacks equivalent gcov support, but presumably it would provide > comparable coverage here. Andrew Turner has some form of kernel gcov > support that he uses with syzkaller. However, I believe that it isn't > sufficient for this purpose. The code I have is to trace the kernel part of a single thread, e.g. = what happens in the kernel when you make a system call. It can trace = function either function entry or places in the code with a conditional = statement, e.g. an if, while, or switch statement. If this is enough for = your case a tool could be written to track coverage from the tests. I expect to update the review soon. I=E2=80=99m working on a man page, = but have been too busy with work and other projects recently to finish = writing it. Andrew From owner-freebsd-current@freebsd.org Wed Dec 19 18:32:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 180E3133FCFA for ; Wed, 19 Dec 2018 18:32:49 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 29C478E263 for ; Wed, 19 Dec 2018 18:32:48 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 86F1E1FF82 for ; Wed, 19 Dec 2018 18:32:46 +0000 (UTC) To: freebsd-current@freebsd.org References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> From: Allan Jude Openpgp: preference=signencrypt Autocrypt: addr=allanjude@freebsd.org; prefer-encrypt=mutual; keydata= mQINBFVwZcYBEADwrZDH0xe0ZVjc9ORCc6PcBLwS/RTXA6NkvpD6ea02pZ8lPOVgteuuugFc D34LdDbiWr+479vfrKBh+Y38GL0oZ0/13j10tIlDMHSa5BU0y6ACtnhupFvVlQ57+XaJAb/q 7qkfSiuxVwQ3FY3PL3cl1RrIP5eGHLA9hu4eVbu+FOX/q/XVKz49HaeIaxzo2Q54572VzIo6 C28McX9m65UL5fXMUGJDDLCItLmehZlHsQQ+uBxvODLFpVV2lUgDR/0rDa0B9zHZX8jY8qQ7 ZdCSy7CwClXI054CkXZCaBzgxYh/CotdI8ezmaw7NLs5vWNTxaDEFXaFMQtMVhvqQBpHkfOD 7rjjOmFw00nJL4FuPE5Yut0CPyx8vLjVmNJSt/Y8WxxmhutsqJYFgYfWl/vaWkrFLur/Zcmz IklwLw35HLsCZytCN5A3rGKdRbQjD6QPXOTJu0JPrJF6t2xFkWAT7oxnSV0ELhl2g+JfMMz2 Z1PDmS3NRnyEdqEm7NoRGXJJ7bgxDbN+9SXTyOletqGNXj/bSrBvhvZ0RQrzdHAPwQUfVSU2 qBhQEi2apSZstgVNMan0GUPqCdbE2zpysg+zT7Yhvf9EUQbzPL4LpdK1llT9fZbrdMzEXvEF oSvwJFdV3sqKmZc7b+E3PuxK6GTsKqaukd/3Cj8aLHG1T1im1QARAQABtCJBbGxhbiBKdWRl IDxhbGxhbmp1ZGVAZnJlZWJzZC5vcmc+iQI/BBMBAgApBQJVcGXGAhsjBQkSzAMABwsJCAcD AgEGFQgCCQoLBBYCAwECHgECF4AACgkQGZU1PhKYC34Muw/+JOKpSfhhysWFYiRXynGRDe07 Z6pVsn7DzrPUMRNZfHu8Uujmmy3p2nx9FelIY9yjd2UKHhug+whM54MiIFs90eCRVa4XEsPR 4FFAm0DAWrrb7qhZFcE/GhHdRWpZ341WAElWf6Puj2devtRjfYbikvj5+1V1QmDbju7cEw5D mEET44pTuD2VMRJpu2yZZzkM0i+wKFuPxlhqreufA1VNkZXI/rIfkYWK+nkXd9Efw3YdCyCQ zUgTUCb88ttSqcyhik/li1CDbXBpkzDCKI6I/8fAb7jjOC9LAtrZJrdgONywcVFoyK9ZN7EN AVA+xvYCmuYhR/3zHWH1g4hAm1v1+gIsufhajhfo8/wY1SetlzPaYkSkVQLqD8T6zZyhf+AN bC7ci44UsiKGAplB3phAXrtSPUEqM86kbnHg3fSx37kWKUiYNOnx4AC2VXvEiKsOBlpyt3dw WQbOtOYM+vkfbBwDtoGOOPYAKxc4LOIt9r+J8aD+gTooi9Eo5tvphATf9WkCpl9+aaGbSixB tUpvQMRnSMqTqq4Z7DeiG6VMRQIjsXDSLJEUqcfhnLFo0Ko/RiaHd5xyAQ4DhQ9QpkyQjjNf /3f/dYG7JAtoD30txaQ5V8uHrz210/77DRRX+HJjEj6xCxWUGvQgvEZf5XXyxeePvqZ+zQyT DX61bYw6w6a5Ag0EVXBlxgEQAMy7YVnCCLN4oAOBVLZ5nUbVPvpUhsdA94/0/P+uqCIh28Cz ar56OCX0X19N/nAWecxL4H32zFbIRyDB2V/MEh4p9Qvyu/j4i1r3Ex5GhOT2hnit43Ng46z5 29Es4TijrHJP4/l/rB2VOqMKBS7Cq8zk1cWqaI9XZ59imxDNjtLLPPM+zQ1yE3OAMb475QwN UgWxTMw8rkA7CEaqeIn4sqpTSD5C7kT1Bh26+rbgJDZ77D6Uv1LaCZZOaW52okW3bFbdozV8 yM2u+xz2Qs8bHz67p+s+BlygryiOyYytpkiK6Iy4N7FTolyj5EIwCuqzfk0SaRHeOKX2ZRjC qatkgoD/t13PNT38V9tw3qZVOJDS0W6WM8VSg+F+bkM9LgJ8CmKV+Hj0k3pfGfYPOZJ/v18i +SmZmL/Uw2RghnwDWGAsPCKu4uZR777iw7n9Io6Vfxndw2dcS0e9klvFYoaGS6H2F13Asygr WBzFNGFQscN4mUW+ZYBzpTOcHkdT7w8WS55BmXYLna+dYer9/HaAuUrONjujukN4SPS1fMJ2 /CS/idAUKyyVVX5vozoNK2JVC1h1zUAVsdnmhEzNPsvBoqcVNfyqBFROEVLIPwq+lQMGNVjH ekLTKRWf59MEhUC2ztjSKkGmwdg73d6xSXMuq45EgIJV2wPvOgWQonoHH/kxABEBAAGJAiUE GAECAA8FAlVwZcYCGwwFCRLMAwAACgkQGZU1PhKYC34w5A//YViBtZyDV5O+SJT9FFO3lb9x Zdxf0trA3ooCt7gdBkdnBM6T5EmjgVZ3KYYyFfwXZVkteuCCycMF/zVw5eE9FL1+zz9gg663 nY9q2F77TZTKXVWOLlOV2bY+xaK94U4ytogOGhh9b4UnQ/Ct3+6aviCF78Go608BXbmF/GVT 7uhddemk7ItxM1gE5Hscx3saxGKlayaOsdPKeGTVJCDEtHDuOc7/+jGh5Zxpk/Hpi+DUt1ot 8e6hPYLIQa4uVx4f1xxxV858PQ7QysSLr9pTV7FAQ18JclCaMc7JWIa3homZQL/MNKOfST0S 2e+msuRwQo7AnnfFKBUtb02KwpA4GhWryhkjUh/kbVc1wmGxaU3DgXYQ5GV5+Zf4kk/wqr/7 KG0dkTz6NLCVLyDlmAzuFhf66DJ3zzz4yIo3pbDYi3HB/BwJXVSKB3Ko0oUo+6/qMrOIS02L s++QE/z7K12CCcs7WwOjfCYHK7VtE0Sr/PfybBdTbuDncOuAyAIeIKxdI2nmQHzl035hhvQX s4CSghsP319jAOQiIolCeSbTMD4QWMK8RL/Pe1FI1jC3Nw9s+jq8Dudtbcj2UwAP/STUEbJ9 5rznzuuhPjE0e++EU/RpWmcaIMK/z1zZDMN+ce2v1qzgV936ZhJ3iaVzyqbEE81gDxg3P+IM kiYh4ZtPB4Q= Subject: Re: The future of ZFS in FreeBSD Message-ID: Date: Wed, 19 Dec 2018 13:32:43 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LZXkpUdvpWGjuMdklzWDpCX07UHw6frMz" X-Rspamd-Queue-Id: 29C478E263 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; NEURAL_HAM_SHORT(-0.99)[-0.985,0]; ASN(0.00)[asn:6939, ipnet:209.51.160.0/19, country:US]; NEURAL_HAM_LONG(-1.00)[-0.999,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 18:32:49 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --LZXkpUdvpWGjuMdklzWDpCX07UHw6frMz Content-Type: multipart/mixed; boundary="QmybEsV62TKI9AojVqn4pAhaNTclfMKfA"; protected-headers="v1" From: Allan Jude To: freebsd-current@freebsd.org Message-ID: Subject: Re: The future of ZFS in FreeBSD References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> In-Reply-To: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> --QmybEsV62TKI9AojVqn4pAhaNTclfMKfA Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2018-12-19 11:30, Shawn Webb wrote: > On Tue, Dec 18, 2018 at 10:49:48PM -0800, Matthew Macy wrote: >> The sources for FreeBSD's ZFS support are currently taken directly >> from Illumos with local ifdefs to support the peculiarities of FreeBSD= >> where the Solaris Portability Layer (SPL) shims fall short. FreeBSD >> has regularly pulled changes from Illumos and tried to push back any >> bug fixes and new features done in the context of FreeBSD. In the past= >> few years the vast majority of new development in ZFS has taken place >> in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced= >> that they will be moving to ZoL >> https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means >> that there will be little to no net new development of Illumos. While >> working through the git history of ZoL I have also discovered that >> many races and locking bugs have been fixed in ZoL and never made it >> back to Illumos and thus FreeBSD. This state of affairs has led to a >> general agreement among the stakeholders that I have spoken to that it= >> makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf >> has graciously encouraged me to add FreeBSD support directly to ZoL >> https://github.com/zfsonfreebsd/ZoF so that we might all have a single= >> shared code base. >> >> A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port >> Before it can be committed some additional functionality needs to be >> added to the FreeBSD opencrypto framework. These can be found at >> https://reviews.freebsd.org/D18520 >> >> This port will provide FreeBSD users with multi modifier protection, >> project quotas, encrypted datasets, allocation classes, vectorized >> raidz, vectorized checksums, and various command line improvements. >> >> Before ZoF can be merged back in to ZoL several steps need to be taken= : >> - Integrate FreeBSD support into ZoL CI >> - Have most of the ZFS test suite passing >> - Complete additional QA testing at iX >> >> We at iX Systems need to port ZoL's EC2 CI scripts to work with >> FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. >> Being integrated in to their CI will mean that, among other things, >> most integration issues will be caught before a PR is merged upstream >> rather than many months later when it is MFVed into FreeBSD. I???m >> hoping to submit the PR to ZoL some time in January. >> >> This port will make it easy for end users on a range of releases to >> run the latest version of ZFS. Nonetheless, transitioning away from an= >> Illumos based ZFS is not likely to be entirely seamless. The >> stakeholders I???ve spoken to all agree that this is the best path >> forward but some degree of effort needs to be made to accommodate >> downstream consumers. The current plan is to import ZoF and unhook the= >> older Illumos based sources from the build on April 15th or two months= >> after iX systems QA deems ZoF stable - which ever comes later. The >> Illumos based sources will be removed some time later - but well >> before 13. This will give users a 3 month period during which both the= >> port and legacy Illumos based ZFS will be available to users. Pools >> should interoperate between ZoF and legacy provided the user does not >> enable any features available only in ZoF. We will try to accommodate >> any downstream consumers in the event that they need that date pushed >> back. We ask that any downstream consumers who are particularly >> sensitive to changes start testing the port when it is formally >> announced and report back any issues they have. I will do my best to >> ensure that this message is communicated to all those who it may >> concern. However, I can???t ensure that everyone reads these lists. Th= at >> is the responsibility of -CURRENT users. >=20 > Hey Matt, >=20 > Thank you for your detailed and informative post. It really helps > downstream consumers of FreeBSD. >=20 > I'm curious what this means for OpenZFS. I was under the impression > that OpenZFS was the upstream for all the ZFS implementations (sans > Oracle). >=20 > Thanks, >=20 The original goal of the OpenZFS project was to have a single OS agnostic repo where all of the common code lives, to try to make it easier to have all of the implementations be relatively in sync with each other, and have feature parity and import compatibility. For the last 5 years, this goal is been out of reach, because no one could justify the effort and expense of maintaining the 'one true repo' when no one would actually be using or benefiting from that repo directly= =2E Today, the OpenZFS repo is just a fork of the illumos-gate repo, but where pull requests are accepted, and where previous Delphix employees would deal with the process of trying to upstream patches to illumos. This process has not worked well recently, as things have gotten stuck waiting for 'merge advocates' in illumos. The ZoF effort will move us closer to the goal of a common repo. The general idea will be to have 'OS Dependent' and 'OS Independent' code, similar to the MI/MD split we do in other kernel code. So the upstream repo will contain OpenZFS, and directories for linux and freebsd. We will leverage the CI work that has already been done, and this will mean that all proposed changes will have to pass CI on FreeBSD as well as Linux before they are merged. Even illumos will begin pulling changes from the ZoL repo, but their timelines are much longer, and more vague than will be acceptable for FreeBSD. There is a monthly ZFS call with leaders from all of the projects (FreeBSD, illumos, ZoL, ZFS on OSX, ZFS on Windows, various vendors), where the need for this change, and some other parts of the plan are discussed: https://www.youtube.com/channel/UC0IK6Y4Go2KtRueHDiQcxow/videos The way that things have evolved over the last few years means it would be much more difficult to just import changes from ZoL. ZoL was originally far behind the OpenZFS repo, but as they were catching up, they were also fixing bugs and adding features. So there is not really a common point in the source we could start from to import ZoL commit by commit. My recent attempts to import a single ZoL feature were also fraught with issues, as the original feature was imported before the zpool import rewrite, but many improvements and bug fixes were done after the rewrite. So the code just doesn't apply cleanly to FreeBSD, since it already has the zpool import rewrite applied. Of paramount importance will be the stability and reliability of the FreeBSD implementation of ZFS. However, for the future, we are going to need to make this switch, so it is better to start sooner rather than later. The biggest thing to remember is that this is still OpenZFS, and still run by the same developers as it has been. We are just commonizing on the repo that has the most features integrated into it. --=20 Allan Jude --QmybEsV62TKI9AojVqn4pAhaNTclfMKfA-- --LZXkpUdvpWGjuMdklzWDpCX07UHw6frMz 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.0.22 (MingW32) iQIcBAEBAgAGBQJcGo7NAAoJEBmVNT4SmAt+PcwP/07O/M31ku52rnTNzPL0La7d QqkvegszPXE5vbmZq7ObKEgd6vyXjTj8zUjfe7QAmx5RiXB3A52O4Uqy/TwOU2XW QSYE6/3X+Pa4Qj7XlqmIackYAnP88mTQjDMu8bCK+SDuEwVBT+pUbpEhgdqDIBO6 fgJD7v5uZXWztfjEKzdZslDyWqm1vYvfekVxhynNbfap212QIeDzOsqp817XO41f 6rR6Ou17jnQq0rqK0mcJPxC/msAgjr6yuqqt/4di4ov9vIMU8EHF84vCXPNWzOm4 Nwa7VguehsSEqAYtHhS60jii73uIgXDfsmKXJYe8y2JurP4lBaVfY9HN7R2q/ahi baGvsQ1gbec6xNIOzVaPryeLhRmhMBmhl9VmpKERXb+P0fR4ZRe2oxOXufJKI05i MJwN3V4bR1N5RgGb3ejj6Kmp6UostQocwU2wpSEVb4zypGsjLea73SxeXddcKNsP C5hN0+anPNnaTGb+vQVNthFttPPPLrRecwAYbiTkiYZMLY9R+wKZv3rv6r+q2kdH HWBm1TctmRQuhAFMhfBvpt0NRUClCh4iTVWwhW5mXNR7Nke/AYnpjM4GvtvqCFsD h44zJCy1p9kqgkNzHq53jJneB5i6mrBC5JpCYPmTycus7B11Qw75wA6O4kuLdgsP c97QnhC3zwdl3UXEugun =UsHM -----END PGP SIGNATURE----- --LZXkpUdvpWGjuMdklzWDpCX07UHw6frMz-- From owner-freebsd-current@freebsd.org Wed Dec 19 18:11:47 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B49B2133F1A0 for ; Wed, 19 Dec 2018 18:11:47 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 614628CED1 for ; Wed, 19 Dec 2018 18:11:46 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: by mail-ua1-x931.google.com with SMTP id j3so7282327uap.3 for ; Wed, 19 Dec 2018 10:11:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphix.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hOzIIq2vNzJWteRgLorlAboeBmU/3kELJ8R/3Rt+0nE=; b=FqSMie6OnvCIQZmLoa2UC2ejz1MKrWEyoq7TQGr/MjnLwRX6N0kCH0DsW/i37hE4zd FVPkCEywLyiiNxbcsCakPehMu6vGdeX5yiHyWC/GRgMNPo3pvk0BP+L6SFWx9nMpF/a/ J39Aw6Am+7ynYKbDpL39Ik+79HrxpyH6zXgvs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hOzIIq2vNzJWteRgLorlAboeBmU/3kELJ8R/3Rt+0nE=; b=WRp6l0HwHFbf3NKdVFxJ+97V7S5/NgU4LH076jJvgBcbbuo6rizdrbcQWf3EI48/no qSWpQU1pwKClM13nJF8IeqJLJn7BXDzXv18m5MbeQ0D0DByzZ5QNb0/u++tJueqmb65+ nPIa0uDw6k0A+y7MAIVDLCh+91VX7Zm5zKQrd6yOD2uku2KX997NzIWiKrCUUsnjA8PZ Iqt8o4xVhvfQeBDIQX83uh1/t5lFijD7tkkuGSam52kJnS/6AnfGDSMuaAPcWfS5Qa0H 953PL5/LBKjylwuYo+aFxjZor1c9+NjgVF+IGNv7HSoLnZuRZfD0oeSYrEFRosfCeJ5F 287A== X-Gm-Message-State: AA+aEWY7fTNRlBXFMTEGWaBNCjmfe36W6Rmurqo1SphnkY9vqYWLUPon eeIIDSofTiZpDjWzbc1GADh2eUH1wRhemDwidRgZmQ== X-Google-Smtp-Source: AFSGD/UdGkh2X9fm0/b9FmZz0MVGS6rHngE9l9h4oLagdoqh8SN93eQ/YwxuC837w/49ok6d08m3pECV7zCpw2w5pqE= X-Received: by 2002:ab0:73c4:: with SMTP id m4mr10762504uaq.101.1545243105000; Wed, 19 Dec 2018 10:11:45 -0800 (PST) MIME-Version: 1.0 References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> In-Reply-To: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> From: Matthew Ahrens Date: Wed, 19 Dec 2018 10:11:32 -0800 Message-ID: Subject: Re: The future of ZFS in FreeBSD To: shawn.webb@hardenedbsd.org Cc: mmacy@freebsd.org, freebsd-fs , freebsd-current@freebsd.org X-Rspamd-Queue-Id: 614628CED1 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=delphix.com header.s=google header.b=FqSMie6O; dmarc=pass (policy=none) header.from=delphix.com; spf=pass (mx1.freebsd.org: domain of matthew.ahrens@delphix.com designates 2607:f8b0:4864:20::931 as permitted sender) smtp.mailfrom=matthew.ahrens@delphix.com X-Spamd-Result: default: False [-3.82 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[delphix.com:s=google]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[delphix.com:+]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com,aspmx.l.google.com,aspmx2.googlemail.com,alt2.aspmx.l.google.com,aspmx3.googlemail.com]; RCVD_IN_DNSWL_NONE(0.00)[1.3.9.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.47)[-0.468,0]; DMARC_POLICY_ALLOW(-0.50)[delphix.com,none]; IP_SCORE(-0.64)[ipnet: 2607:f8b0::/32(-1.75), asn: 15169(-1.39), country: US(-0.08)]; FORGED_SENDER(0.30)[mahrens@delphix.com,matthew.ahrens@delphix.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[mahrens@delphix.com,matthew.ahrens@delphix.com]; RCVD_COUNT_TWO(0.00)[2] X-Mailman-Approved-At: Wed, 19 Dec 2018 18:39:20 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 18:11:48 -0000 On Wed, Dec 19, 2018 at 8:35 AM Shawn Webb wrote: > I'm curious what this means for OpenZFS. > OpenZFS will continue to be an umbrella project for coordinating all work on open-source ZFS. The primary activities of OpenZFS are the annual OpenZFS Developer Summit and the monthly OpenZFS Leadership Meetings . There is also an OpenZFS GitHub repo, which has identical code to illumos. This is used to streamline the process of getting changes into illumos (removing some of the burden of testing and the illumos RTI process). This repo will continue to exist as long as there's need for it and folks able to keep the automation running. The naming of this GitHub project was perhaps unfortunate, since it is specific to illumos and not platform-agnostic. I was under the impression that OpenZFS was the upstream for all the ZFS > implementations (sans > Oracle). Being "upstream" is more a matter of degree than an absolute ordering. In the past, most ZFS features have originated in illumos, and those changes have been ported to the other platforms (notably FreeBSD and ZoL). Looking forward, we see more features originating in ZoL. The OpenZFS community (including FreeBSD) is working to put in place technical processes to ensure that new ZFS features are available on all platforms. The original post in this thread was a proposal for how to do that. --matt From owner-freebsd-current@freebsd.org Wed Dec 19 18:55:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26B621340A2D for ; Wed, 19 Dec 2018 18:55:18 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [140.82.23.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5DF188F27E; Wed, 19 Dec 2018 18:55:17 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from duke.gem.co (cpe-76-175-75-27.socal.res.rr.com [76.175.75.27]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 89b7bda2 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 19 Dec 2018 10:55:15 -0800 (PST) Subject: Re: The future of ZFS in FreeBSD To: Allan Jude , freebsd-current@freebsd.org References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> From: Pete Wright Message-ID: <2f62c721-843b-7e2e-d877-e780243f5d2e@nomadlogic.org> Date: Wed, 19 Dec 2018 10:55:14 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 5DF188F27E X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 140.82.23.70 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-5.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[27.75.175.76.zen.spamhaus.org : 127.0.0.10]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-2.42)[ip: (-8.93), ipnet: 140.82.16.0/21(-4.47), asn: 20473(1.36), country: US(-0.08)]; MX_GOOD(-0.01)[cached: mail.nomadlogic.org]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.87)[-0.866,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20473, ipnet:140.82.16.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 18:55:18 -0000 On 12/19/18 10:32 AM, Allan Jude wrote: > > The biggest thing to remember is that this is still OpenZFS, and still > run by the same developers as it has been. We are just commonizing on > the repo that has the most features integrated into it. > thanks for the clarification on this, as i was a bit confused as well. :) One question - is there a plan to rename things to not be linux specific, especially since it seems that this effort will result in the original goal of the OpenZFS repro (if I am reading things correctly)?  Or is that not going to happen because ZoL has the most commercial backing? It's probably a mute point - but I do take pride in the fact that FreeBSD has had support ZFS for so long and has allowed me to do things for my customers that I can't do on Linux...so I guess what I'm saying is I hope we don't loose credit for the hard work we've put into getting ZFS mainstream over the years :) Thanks! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed Dec 19 19:35:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30FA21341D19 for ; Wed, 19 Dec 2018 19:35:28 +0000 (UTC) (envelope-from Scoobi_doo@yahoo.com) Received: from sonic314-14.consmr.mail.bf2.yahoo.com (sonic314-14.consmr.mail.bf2.yahoo.com [74.6.132.124]) (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 D3FF16A16C for ; Wed, 19 Dec 2018 19:35:26 +0000 (UTC) (envelope-from Scoobi_doo@yahoo.com) X-YMail-OSG: VaIQJY0VM1mMiIyD.zXxpSp.5jnrZx.7x0RnDQgCR4EDY8_M_zG2W.ABRAd13JV Gj7vn6T0eorAwdynFrAskTSif93owu__KE5Ev7h.tSsBPwSwnZ7p9VD8KlMJ0y1hOzc4ui2lsce6 eJtv1NLiWTOq_mvcQ44qW3s2JCtMHtkUk2tSVA9ATRrO3FpHKoyQ6HnHHMhSB7u4_4y3G2EZ5isR Ebvj0WklH6800kDClsH5CdzmGUL1eUsN073X0Fe2jfk7DIa9ON56Su3SlSOsl6MPzT5emH1C7nSy NvYIx4lyILuSESmxcela6bpDFXr5mOReuez8OE2moUZjRDDecYSXfFTPEm0D8grXmwekfS4VLVZS msP3B_GRQE1RM..tt4YCupyVfPzihdHzmkx78kkRFZkVbzoC98yXZP6iXcntcBjXBf4_OzXheS03 3R6q9YYCZ8AsO16eHq7sk_.ZfQZxdbKeDmocW2i82aAwM3FiLEJvNKcCNOsKi3LJipYZW_luvzVT JpSpoShL5PuRTBGvb1SE_0E3RV8qAXA9SP1DWVjBs36d0IzR31J1pAtBplfk4d48aAnLHRh29Kkn ImSejYHnse0x91hDd7o7HM.gysCc6uqjBKJCvhRRHPeN.4cehv_GmeTiMo1krWBVpJYrk7FUbUNl _IsJz17zAmzBwDMGeDF0JjSZpLqt2uPGAYRZraosnW2NWfEPl5mx9nNcBL6w.krzHZ3wfllrBAu8 mr6Yex2WlXhIkHWjI.8Asqj.cXL2YACSJxMum5yPMkdtgRNPUuMOc_sAQ8nFK5RCwQ5W4m0r_1_5 VoiOtmJbEMXDZG.HrC1b1MxAH2G2fEwp2rKtILdMLlej8Sns4xdRMo5qY7XUp_Cxugr94l9pzmgx uq8NNxIwjka2.i4EfMYx.8_HQlPDliuraXvtE7ca1q.IJS2gsC_Jq.UKM3CzFtSrN6LrhU0e9bJX GvGECYrl5Mobe5af1_TWl8wpxKdjcNP6AebdgVlSltQgLUGgCKRx2LghlWOTgQWgovoEpfbIwTby 3HtAFzOH_bcDWqQWu1PWCtI4B8CdLGmlyxtKamaS1MM9cI4VcewgWmKvgr4yen6jdmXECga.XvJb 12hSLl1V4Dy65pYVZSHAS5o0tQ8Q9aw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.bf2.yahoo.com with HTTP; Wed, 19 Dec 2018 19:35:20 +0000 Received: from 192.34.49.8 (EHLO [10.228.144.28]) ([192.34.49.8]) by smtp402.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 8b75c1e5c0adb277ea85742e68ef4d78; Wed, 19 Dec 2018 19:35:15 +0000 (UTC) Subject: Re: Composite PCI devices in FreeBSD (mfd in Linux) From: Anthony Jenkins To: John Baldwin , Ian Lepore Cc: FreeBSD CURRENT , Gleb Popov <6yearold@gmail.com> References: <1544473194.1860.340.camel@freebsd.org> <05b1183c-6117-267b-42f9-19e750adfa07@FreeBSD.org> <02e30a11-4adf-3efb-d2ce-89c598bda9cf@yahoo.com> Message-ID: <1c3e555d-7289-1219-8c66-07f75a335dc0@yahoo.com> Date: Wed, 19 Dec 2018 14:35:14 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: <02e30a11-4adf-3efb-d2ce-89c598bda9cf@yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: D3FF16A16C X-Spamd-Bar: / X-Spamd-Result: default: False [-0.34 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.78)[-0.782,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:26101, ipnet:74.6.128.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.67)[-0.667,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(1.64)[ip: (5.29), ipnet: 74.6.128.0/21(1.67), asn: 26101(1.33), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.48)[0.479,0]; RCVD_IN_DNSWL_NONE(0.00)[124.132.6.74.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 19:35:28 -0000 On 12/19/18 10:41 AM, Anthony Jenkins wrote: > [snip] > > I'm not feeling too confident about the condition of the FreeBSD ig4 > driver; the PCI attach code was calling pci_alloc_msi() wrong, passing > a pointer to the rid (0) instead of a pointer to a count variable, and > not passing bus_alloc_resource_any() an IRQ rid > 0 if it has an MSI.  > I'd be happy(er) if ig4 created a /dev/iic0 node - I figured iicbus(4) > took care of all that... > > https://github.com/ScoobiFreeBSD/freebsd-intel-lpss > Found it!  I didn't declare ig4_iic to include the ig4_lpss as a sub-device.  Now it at least /looks/ like I'm getting I2C devices found on both my DesignWare I2C busses. diff --git a/sys/dev/ichiic/ig4_iic.c b/sys/dev/ichiic/ig4_iic.c index 6bbe417..34c1adb 100644 --- a/sys/dev/ichiic/ig4_iic.c +++ b/sys/dev/ichiic/ig4_iic.c @@ -802,3 +802,4 @@ ig4iic_dump(ig4iic_softc_t *sc)  DRIVER_MODULE(iicbus, ig4iic_acpi, iicbus_driver, iicbus_devclass, NULL, NULL);  DRIVER_MODULE(iicbus, ig4iic_pci, iicbus_driver, iicbus_devclass, NULL, NULL); +DRIVER_MODULE(iicbus, ig4iic_lpss, iicbus_driver, iicbus_devclass, NULL, NULL); ajenkins@ajenkins-delllaptop ~/Projects/freebsd-intel-lpss (master) $ ls /dev/ii* /dev/iic0  /dev/iic1 ajenkins@ajenkins-delllaptop ~/Projects/freebsd-intel-lpss (master) $ for i2cbus in iic0 iic1; do sudo i2c -s -f "/dev/${i2cbus}"; done Hardware may not support START/STOP scanning; trying less-reliable read method. Scanning I2C devices on /dev/iic0: 0a Hardware may not support START/STOP scanning; trying less-reliable read method. Scanning I2C devices on /dev/iic1: 2c Anthony From owner-freebsd-current@freebsd.org Wed Dec 19 20:01:47 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8E20134290A for ; Wed, 19 Dec 2018 20:01:47 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (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 0F42B6B172 for ; Wed, 19 Dec 2018 20:01:46 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1545249668; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=oyRzwZdAUtCcYRp8u92G0uKzUpyQABMX+fBUWKUJInsY09w2cJgXTZGod2atPRVzkwA8HXzR/LE/Z 29iA08xmVUQVIxqwDAv2NRh/xQGRTPlIovQV4WthGmbJxjyboP3OVzdAvtK5aThcP5ZotGhk3EBF2L xV0vRzaKL+NpRWdJweRegB+8eqb1NLT0CVWIpgaXvLBUHs7Nz7x9UKDEtq32IneXq0JEuQT9zfY+Nm onwSlMG8zsSfaAX+lfb8iQxFG2nVy9ERIXaGM46ajAjBYUkwrJ7uAmt5lACgZggMjqvqcbu5smiT15 o24uEf9E105gmeB1TIzEJEyN+U6nPVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=JOYJ06taVcvo7lkh53LM4DKiwj8s8qjlt9+HZc4Ado0=; b=IRXO9DgY59zgfLYCT40Dev5kpiRclrnFV1txqos8TxJe0To+oVOCUIyfS1pwL/a+lKaA3i6Q95Ew5 2mp5vrXnTv1a+H7X5Z+t5g48WOI1SU8/zyI/lkAglKD8MYCvvwDTXOrSE/xpYJj1RIunsPA+rR8UuQ R0Jz/tirzeIl02TNMdDRy++WE+MnwsO+SukspwZ1PVIZ6cQFXlHWgwCoaoS/cnmm9tybzEX3mOLZVb 7nzSI6YCjtu2E2ZdVPc/8SAIOUpSvoTIN7nQH/sYhzGHAv0HetJvo+cIuca2xGl9Aii/98PmSohOpU Zyh2TNEBAJ/6QNdT2vfx9VdxtpjC4WA== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=JOYJ06taVcvo7lkh53LM4DKiwj8s8qjlt9+HZc4Ado0=; b=ih1qCyBU9X/gf+bVr9sviGb4IsPcOhrYZBKIDwscKDtxoX6K69EMoAeCtot+VOgvfkYpBcepeNwfZ lC1rgejXdeZrH2ogrcF8p60rKW1kb/eRb/2ywV/gc+sa0ymXsgnJqQzOvMhhlIfTDCp81AHxYdHXE/ LlCMGToeihdl+WMM/gm2nV91DIxtFdkSmGoLC42wVen5NRubgTSEmBBZxpl0kn+uHK2+DGBcIA7PzQ 29pKKb+3TdPQoM/8AyQM/oevx9ElpVqwH9JqGJ+kVIfGXvZDtnK2UVsOHD1NtOHmVsvUlq1BUszORx o+yCYKyemiDZXBSTD48ksxEeLho25Ag== X-MHO-RoutePath: aGlwcGll X-MHO-User: d1dced10-03c8-11e9-befd-af03bedce89f X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id d1dced10-03c8-11e9-befd-af03bedce89f; Wed, 19 Dec 2018 20:01:06 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id wBJK1bDf097637; Wed, 19 Dec 2018 13:01:37 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1545249697.76088.176.camel@freebsd.org> Subject: Re: Composite PCI devices in FreeBSD (mfd in Linux) From: Ian Lepore To: Anthony Jenkins , John Baldwin Cc: FreeBSD CURRENT , Gleb Popov <6yearold@gmail.com> Date: Wed, 19 Dec 2018 13:01:37 -0700 In-Reply-To: <1c3e555d-7289-1219-8c66-07f75a335dc0@yahoo.com> References: <1544473194.1860.340.camel@freebsd.org> <05b1183c-6117-267b-42f9-19e750adfa07@FreeBSD.org> <02e30a11-4adf-3efb-d2ce-89c598bda9cf@yahoo.com> <1c3e555d-7289-1219-8c66-07f75a335dc0@yahoo.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 0F42B6B172 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 20:01:48 -0000 On Wed, 2018-12-19 at 14:35 -0500, Anthony Jenkins wrote: > On 12/19/18 10:41 AM, Anthony Jenkins wrote: > > > > [snip] > > > > I'm not feeling too confident about the condition of the FreeBSD > > ig4  > > driver; the PCI attach code was calling pci_alloc_msi() wrong, > > passing  > > a pointer to the rid (0) instead of a pointer to a count variable, > > and  > > not passing bus_alloc_resource_any() an IRQ rid > 0 if it has an > > MSI.   > > I'd be happy(er) if ig4 created a /dev/iic0 node - I figured > > iicbus(4)  > > took care of all that... > > > > https://github.com/ScoobiFreeBSD/freebsd-intel-lpss > > > Found it!  I didn't declare ig4_iic to include the ig4_lpss as a  > sub-device.  Now it at least /looks/ like I'm getting I2C devices > found  > on both my DesignWare I2C busses. > > diff --git a/sys/dev/ichiic/ig4_iic.c b/sys/dev/ichiic/ig4_iic.c > index 6bbe417..34c1adb 100644 > --- a/sys/dev/ichiic/ig4_iic.c > +++ b/sys/dev/ichiic/ig4_iic.c > @@ -802,3 +802,4 @@ ig4iic_dump(ig4iic_softc_t *sc) > >   DRIVER_MODULE(iicbus, ig4iic_acpi, iicbus_driver, iicbus_devclass,  > NULL, NULL); >   DRIVER_MODULE(iicbus, ig4iic_pci, iicbus_driver, iicbus_devclass,  > NULL, NULL); > +DRIVER_MODULE(iicbus, ig4iic_lpss, iicbus_driver, iicbus_devclass,  > NULL, NULL); That new DRIVER_MODULE() statement should be in your new driver, not in ig4_iic.c. Those other two statements should also be moved into their corresponding source code files. At least, that's the precedent followed by all the i2c controller drivers except ig4_iic: the DRIVER_MODULE() statement that establishes the connection between iicbus and the controller lives right alongside the DRIVER_MODULE() statement that establishes the connection between the controller and the bus it sits on. See, for example:  sys/dev/glxiic/glxiic.c  sys/dev/iicbus/iicoc.c -- Ian From owner-freebsd-current@freebsd.org Wed Dec 19 20:30:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CAC1134332C for ; Wed, 19 Dec 2018 20:30:41 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic311-22.consmr.mail.gq1.yahoo.com (sonic311-22.consmr.mail.gq1.yahoo.com [98.137.65.203]) (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 34BC16C293 for ; Wed, 19 Dec 2018 20:30:40 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: IDhYi.8VM1n87Iq1zKQn7nCLYlTGsJ_NApZPc7CQY9.tY2RTMyzriKIiinNau6V HNElefSeGM74gbZsAvhh9PKw63G0slF8MDDwYF7M3K5ALyvhIpLaDzQ7M3Qv8zIF0hrHO9D7kcSU BfR94ClAwROea_X2k3xEU7mCUBTnxHooSPGD7ZEXroDNkqhEAh3.EAJ4N4rb01YPVmfUwiTzeK5f 5Dm.0oMoNr0coVowCTDQbG.cqovP8KOUcMU1IkP6imAazuyktel7GoTR0KFGBj2qbYOgkzkCPndh YReQgVnw5Dhq1ID.Yqqr4haugVNkkSSgvTm.J8tZGHXBQ99tPORt5ZEtkUy3Ni0mmzaXde45y08X uVhKmLA7xkzDFuUFbsvl3QI42n.zFyU6hn5l1UnuRJsBiOV4VnqhMrf3MHqc3.xNQ6fXwjR4w6Fs _A4UQ7M7QR3x08foD.QWE_65XBGfojHQebNWQAiG8fV1ZAVoYegn7kT0xohpJ.vHmo3nCnJ6Rvr0 zbLPfQOyBhRSflHB3E9dUR6Pz318hYIWI8Yz5Y5LFcyDA5R9x2Soqlj8X5ZKPT6pZGzLphf0esER mNtXmadwCXJtG6PhDKZTLEzDzq1boRZhWWOjg4qxXrHEIuoDV5jtNFxnPkdHpb3KrT33jbhAulfU WfRgc2l2siUfiKzHzCADEvk_cWAEsP5ZOAzXaHsCHwk4ebcNeIpy4z8_.F1E1hycnKwsN7viqs3. HJcyJEExrDlyS7fHHR9EOOoPIRLBOFxRb_DTr4yZQh440f2dsIA6wYRYPTji7SOSQSPbfzmkCVYq Ais_zfQB4IagZZWTHCH_Pf88vlWpccuQoXRF2wTfCGDF1_T6qyLGp4mjYxkPK2HDKjJj5XHehv7C 4ew1avYD8fPpohnwfyP1tnfWTfxxvM_pg4nRvu2eVYy18r.7h2h8tJ0HV5gnv86VCi64MfLWNbM1 jPmAdm0k6aoUeE0bnOx.L296aM9Zsp7iTSMQjaRiPHXyKw9SJAM1Deom47esY3cA_fWWxBUz0tOt _zB8nG2ZxNbl.EVqTtwZok2D5JnUaaJiDPdq4HvgClQHUKpnn_BaF5Eq0CejfJNmnfg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Wed, 19 Dec 2018 20:30:32 +0000 Received: from c-67-170-167-181.hsd1.or.comcast.net (EHLO [192.168.1.109]) ([67.170.167.181]) by smtp419.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID bed290c5268af183ea9e1fc7776a6e5a; Wed, 19 Dec 2018 20:20:20 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: FreeBSD head -r341836 amd64->aarch64 cross-build of -r484783 ports via poudriere: devel/qt5-testlib hung-up during "Checking for POSIX monotonic clock" Message-Id: <190D54A2-D29A-4B62-B8FF-99514DBE92A0@yahoo.com> Date: Wed, 19 Dec 2018 12:20:19 -0800 To: freebsd-arm , FreeBSD Current , ports-list freebsd X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: 34BC16C293 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.76 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MV_CASE(0.50)[]; FREEMAIL_FROM(0.00)[yahoo.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.77)[-0.771,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.86)[-0.858,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-0.28)[-0.281,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.66)[ip: (2.17), ipnet: 98.137.64.0/21(0.66), asn: 36647(0.53), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[203.65.137.98.list.dnswl.org : 127.0.5.0]; RWL_MAILSPIKE_POSSIBLE(0.00)[203.65.137.98.rep.mailspike.net : 127.0.0.17] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 20:30:41 -0000 FYI: Based on FreeBSD head -r341836 (host and target) and ports -r484783 = . This was a rebuild based on going from perl5.26 to perl5.28 without updating = the ports tree and from system clang 6 for the prior FreeBSD-head context used to = clang 7 this time. (I'm not attributing causes here.) poudriere was using = amd64-native tools for speeding up the cross-build. # grep -r =3Dperl5=3D /etc/ ~/src.configs/ /usr/local/etc/ /etc/make.conf:DEFAULT_VERSIONS+=3Dperl5=3D5.28 gcc=3D8 /usr/local/etc/poudriere.d/make.conf:DEFAULT_VERSIONS+=3Dperl5=3D5.28 = gcc=3D8 There was also a "print/texinfo:configure/runaway" but I've not looked = into it at all yet and it may be a while before I do. The other ports = attempted built fine as far as I can tell so far. The devel/qt5-testlib failure looks like: [00:00:13] Building 123 packages using 28 builders . . . [00:49:30] [10] [00:00:00] Building devel/qt5-testlib | = qt5-testlib-5.11.2 . . . [07:31:31] [10] [06:42:01] Saved devel/qt5-testlib | qt5-testlib-5.11.2 = wrkdir to: = /usr/local/poudriere/data/wrkdirs/FBSDFSSDjailCortexA57-default/default/qt= 5-testlib-5.11.2.tar [07:31:32] [10] [06:42:02] Finished devel/qt5-testlib | = qt5-testlib-5.11.2: Failed: configure/runaway With logs/errors/qt5-testlib-5.11.2.log showing: Checking for POSIX monotonic clock...=20 + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin= /qmake "CONFIG -=3D qt debug_and_release app_bundle lib_bundle" "CONFIG = +=3D shared warn_off console single_arch" = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && MAKEFLAGS=3D make =3D>> Killing runaway build after 21600 seconds with no output =3D>> Cleaning up wrkdir =3D=3D=3D> Cleaning for qt5-testlib-5.11.2 Killed build of devel/qt5-testlib | qt5-testlib-5.11.2 ended at Wed Dec 19 = 06:45:42 PST 2018 build time: 06:41:46 !!! build failure encountered !!! # less = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.log . . . test config.qtbase_corelib.libraries.librt succeeded executing config test clock-monotonic + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin= /qmake "CONFIG -=3D qt debug_and_release app_bundle lib_bundle" "CONFIG = +=3D shared warn_off console single_arch" = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && MAKEFLAGS=3D make Some supporting details of context: # uname -apKU FreeBSD FBSDFSSD 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r341836M: Tue Dec = 11 16:37:42 PST 2018 = markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/G= ENERIC-NODBG amd64 amd64 1300005 1300005 # svnlite info /usr/ports/ | grep "Re[plv]" Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 484783 Last Changed Rev: 484783 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Wed Dec 19 22:18:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9911134ADFC for ; Wed, 19 Dec 2018 22:18:53 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic305-21.consmr.mail.gq1.yahoo.com (sonic305-21.consmr.mail.gq1.yahoo.com [98.137.64.84]) (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 BA5897290A for ; Wed, 19 Dec 2018 22:18:52 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: u_vPeJkVM1kVqmF5WTWaXTxxjKnLJT8MaYvOdabQwf_Tct.Do8KhqDa6UgqYgiw hRt_Ay1685U4.ZmRnNXPr9SZgaAPLmrmEzFgAl_RPDc9K0RCRDrRFrkobhama8xDigLLTRUEmnbv X18L47SvVwugha0mZNFqwtkR1SJgWjZgshTFw4v3jTdqWHwh_MaJ8YkbO0mo_0cdr2kVeO6dZj5E V0lOUNYDMiS0Yp1HywRB.GYBlYAySUZtuuW721BgJQuFxAkL9k1cUPPm7k7DBGG61FNqCXOBlGox tX_SinBcvNHcWEMuqUNn8EuRA6C9LEuy9fLZDurMCVWtLU8DOn.b8cnV2CuZhCTdqQ2WiSM89fMq oe1hEuHaYr3SOZoVigwGQzpmxanTecrlfuzCMhCyxGCH_ROK2mtrUKeRwrCOlI2mhBrtjvo8gwyJ _PFgUaSdAWr3BQCLgdP_sOI_CyXEU63p2SG9fIqdljriw_GWZ0EF2QASVscXX1bhwV.nZTDeOFyk GGgbnXVTNsnHJwut8csV5EPbwJ2Z4gtVy0kgt4anM82ThvuI3QLoc85.L8_CnSTeZjwin.CPSkiB jMCLV6DZqK39U1bL41ehjInzbuHJh7ymYIOQc._x1biXrLu22GJOWUwM7vrlMMGZPeivt7RWDOtk 5MsRy3iY5jTGsGXj5CHjMSBg8TvT0pyH3qn4vPw1SGd1jKInOn9xYerk8AFdRjsLOA_0E7l0L.wm sNxKj.caGkKcp9PNfhqJZcKvSgV0xmK9WRu5Ls.FpPhZvjgMcJpXQEXSXkh0yiSiItBbhbnyAAoA aDm7qc80ggaTCJ.aNvWMjvGH6ICBlmcLqU4B0MJEw2spCFXhi5eoD7dWfT1AO0bGNNRzIRxMTb_c iZhB4cTtUXu_.kEd2IaTqegwMZIzuevv1n7JpTD376PJm45m0dYZcJmEJmarhiDD_vtCxe9SXWcS XOhVx5OJQDHpMgQQ4zZJG3u9BkvtcIEez2bqQcQfq30Bx7UIVzWJrjvkuwGtnILiB0VqO0IWxNKa CW5qEwI8qatakNSM5OkYfseiYtlfO_MYqxklMwPDJGkuUsDQDv5sCo8tNbn9Rs_nn1p8- Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.gq1.yahoo.com with HTTP; Wed, 19 Dec 2018 22:18:50 +0000 Received: from c-67-170-167-181.hsd1.or.comcast.net (EHLO [192.168.1.109]) ([67.170.167.181]) by smtp427.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4876b6bf4f0e77ae3ec4837f0456e7b9; Wed, 19 Dec 2018 21:58:31 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: FreeBSD head -r341836 amd64->aarch64 cross-build of -r484783 ports via poudriere: devel/qt5-testlib hung-up during "Checking for POSIX monotonic clock" Date: Wed, 19 Dec 2018 13:58:30 -0800 References: <190D54A2-D29A-4B62-B8FF-99514DBE92A0@yahoo.com> To: freebsd-arm , FreeBSD Current , ports-list freebsd In-Reply-To: <190D54A2-D29A-4B62-B8FF-99514DBE92A0@yahoo.com> Message-Id: X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: BA5897290A X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.04 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MV_CASE(0.50)[]; FREEMAIL_FROM(0.00)[yahoo.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.80)[-0.800,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.991,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-0.95)[-0.953,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.22)[ipnet: 98.137.64.0/21(0.65), asn: 36647(0.52), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[84.64.137.98.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 22:18:54 -0000 [Looks like a race or some such for devel/qt5-testlib: retry of = poudreire-devel did not hang. The other hang-up seems to be repeating and I give some = details.] On 2018-Dec-19, at 12:20, Mark Millard wrote: > FYI: Based on FreeBSD head -r341836 (host and target) and ports = -r484783 . This > was a rebuild based on going from perl5.26 to perl5.28 without = updating the ports > tree and from system clang 6 for the prior FreeBSD-head context used = to clang 7 > this time. (I'm not attributing causes here.) poudriere was using = amd64-native > tools for speeding up the cross-build. >=20 > # grep -r =3Dperl5=3D /etc/ ~/src.configs/ /usr/local/etc/ > /etc/make.conf:DEFAULT_VERSIONS+=3Dperl5=3D5.28 gcc=3D8 > /usr/local/etc/poudriere.d/make.conf:DEFAULT_VERSIONS+=3Dperl5=3D5.28 = gcc=3D8 >=20 > There was also a "print/texinfo:configure/runaway" but I've not looked = into > it at all yet and it may be a while before I do. The other ports = attempted > built fine as far as I can tell so far. >=20 >=20 > The devel/qt5-testlib failure looks like: >=20 > [00:00:13] Building 123 packages using 28 builders > . . . > [00:49:30] [10] [00:00:00] Building devel/qt5-testlib | = qt5-testlib-5.11.2 > . . . > [07:31:31] [10] [06:42:01] Saved devel/qt5-testlib | = qt5-testlib-5.11.2 wrkdir to: = /usr/local/poudriere/data/wrkdirs/FBSDFSSDjailCortexA57-default/default/qt= 5-testlib-5.11.2.tar > [07:31:32] [10] [06:42:02] Finished devel/qt5-testlib | = qt5-testlib-5.11.2: Failed: configure/runaway >=20 > With logs/errors/qt5-testlib-5.11.2.log showing: >=20 > Checking for POSIX monotonic clock...=20 > + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin= /qmake "CONFIG -=3D qt debug_and_release app_bundle lib_bundle" "CONFIG = +=3D shared warn_off console single_arch" = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic > + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && MAKEFLAGS=3D make > =3D>> Killing runaway build after 21600 seconds with no output > =3D>> Cleaning up wrkdir > =3D=3D=3D> Cleaning for qt5-testlib-5.11.2 > Killed > build of devel/qt5-testlib | qt5-testlib-5.11.2 ended at Wed Dec 19 = 06:45:42 PST 2018 > build time: 06:41:46 > !!! build failure encountered !!! >=20 >=20 > # less = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.log > . . . > test config.qtbase_corelib.libraries.librt succeeded > executing config test clock-monotonic > + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin= /qmake "CONFIG -=3D qt debug_and_release app_bundle lib_bundle" "CONFIG = +=3D shared warn_off console single_arch" = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic > + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && MAKEFLAGS=3D make >=20 >=20 > Some supporting details of context: >=20 > # uname -apKU > FreeBSD FBSDFSSD 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r341836M: Tue = Dec 11 16:37:42 PST 2018 = markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/G= ENERIC-NODBG amd64 amd64 1300005 1300005 >=20 > # svnlite info /usr/ports/ | grep "Re[plv]" > Relative URL: ^/head > Repository Root: svn://svn.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 484783 > Last Changed Rev: 484783 >=20 I started poudriere up again with just the 2 needing to be rebuilt (plus what depends on the 2). devel/qt5-testlib quickly completed just fine: [00:02:16] [02] [00:00:00] Building devel/qt5-testlib | = qt5-testlib-5.11.2 [00:04:54] [02] [00:02:38] Finished devel/qt5-testlib | = qt5-testlib-5.11.2: Success In the prior build that had the hang-ups I looked and dor print/texinfo = : /wrkdirs/usr/ports/print/texinfo/work/texinfo-6.5/config.log shows for = its hang-up: . . . configure:6639: checking for alloca configure:6676: /nxb-bin/usr/bin/cc -o conftest -O2 -pipe = -mcpu=3Dcortex-a57 -DLIBICONV_PLUG -g -fno-strict-aliasing = -mcpu=3Dcortex-a57 -DLIBICONV_PLUG -D_THREAD_SAFE conftest.c >&5 configure:6676: $? =3D 0 configure:6684: result: yes configure:6794: checking for C/C++ restrict keyword configure:6821: /nxb-bin/usr/bin/cc -c -O2 -pipe -mcpu=3Dcortex-a57 = -DLIBICONV_PLUG -g -fno-strict-aliasing -mcpu=3Dcortex-a57 = -DLIBICONV_PLUG -D_THREAD_SAFE conftest.c >&5 configure:6821: $? =3D 0 configure:6829: result: __restrict configure:6844: checking whether // is distinct from / In the poudriere re-run print/texinfo seems to be not progressing: root 87913 0.0 0.0 12920 3668 0 I 13:29 0:00.06 | = | `-- sh: poudriere[FBSDFSSDjailCortexA57-default][01]: = build_pkg (texinfo-6.5_1,1) (sh) root 88869 0.0 0.0 12920 3660 0 I 13:29 0:00.00 | = | `-- sh: poudriere[FBSDFSSDjailCortexA57-default][01]: = build_pkg (texinfo-6.5_1,1) (sh) root 88870 0.0 0.0 10412 1848 0 IJ 13:29 0:00.01 | = | `-- /usr/bin/make -C /usr/ports/print/texinfo configure root 88974 0.0 0.0 10272 1812 0 IJ 13:30 0:00.00 | = | `-- /bin/sh -e -c (cd = /wrkdirs/usr/ports/print/texinfo/work/texinfo-6.5 && = _LATE_CONFIGURE_ARGS=3D"" ; if [=20 root 89283 0.0 0.0 11160 2108 0 IJ 13:30 0:00.10 | = | `-- /bin/sh ./configure --enable-nls = --prefix=3D/usr/local --localstatedir=3D/var --mandir=3D/usr/local/man = --di root 89692 0.0 0.0 227368 14504 0 IJ 13:30 0:00.03 | = | `-- /usr/local/bin/qemu-aarch64-static wc = //dev/null root 89694 0.0 0.0 227424 14596 0 IJ 13:30 0:00.01 | = | `-- /usr/local/bin/qemu-aarch64-static wc = //dev/null root 89695 0.0 0.0 227584 14720 0 IJ 13:30 0:00.01 | = | `-- wc: zygote (qemu-aarch64-static) So it appears that: /usr/local/bin/qemu-aarch64-static wc //dev/null is hanging-up (again). Given that these are hangups I'll note that this is a Ryzen Threadripper 1950X context and is running under Hyper-V from Windows 10's 1809 update. I gave it 28 logical processors and have it to have the virtual NUMA topology match the topology of the physical hardware: "Use Hardware Topology". (Processors 28, NUMA nodes 2, Sockets 1, Hardware threads per core 2.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Wed Dec 19 22:46:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 933F0134B9EB for ; Wed, 19 Dec 2018 22:46:59 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABAD8742DB for ; Wed, 19 Dec 2018 22:46:57 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: by mail-lf1-x136.google.com with SMTP id i26so16288308lfc.0 for ; Wed, 19 Dec 2018 14:46:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j4JVyF3Ru+/bxAAy2sknhbV8VkaTEa8gvgJAlGIhRL8=; b=q7/EAzxt6gSGQzz0WsX3SXkmyEoRUFGQdq0d2NJvlwA3ZSFUYKDQC2eB4OGdonIuEW 1YJs7SKbQOiSkMRrIHyS+oAazfqM7kmiMoD64vutd0o3M9Ou9+b6SXxlc5Ssd7HZBgmr sXUiReTlaT2qtZblSelPRq0Ec01mw0XukI0Ho7/FjYmr2im+ZGePkFzDUbJHjH7xzgv/ KSQ9PNkJYU0eJObhNQaFDAn/EdIhE6JsSdF6JQa3zzk8xquqyaVF6do2Jv10RJv5EhLp NWIggirYie97EEFTjtrSphUcolnSazw0Dj9qV6P8xDiw9NZXWfYzFOaIj68MEAzmUF86 Czig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j4JVyF3Ru+/bxAAy2sknhbV8VkaTEa8gvgJAlGIhRL8=; b=Zekv3BbQ/Mvn+A73bpbJbSZZQQXeEgGYh/blXN/B1JasBOqyY8GWSMtYP3wYy24GHT fu3LVSK9/vD2tK3AEm//CCM3fuGsvM3DCSeap//NGPM9IPt3KpZgVmUgyDxnOW6j5rYw xO9wbJL6VZAIGd6Ay0QxirQHGQ9gey54e5kAcogkjQ56CQI0u1HXoOcgE26wp9zqTROc WIsj4uoschukC8FVmhmd88r39/BN59c3H6AdUeK8XqzIly1N0UxMyLrzc8tkFQAq7VS/ +3YSM64P2RSoYn4IxFNYD/01mWQgb9s0cVBwKlp199Bjoke0XJPAflSVGmQt4pVeG6Xl V+IQ== X-Gm-Message-State: AA+aEWYu74z4DsaAOtDtZ//tNBwdll+WtDpw0P+TV2kwFB7zOeqC+VD3 JrEKOXgjhXTVU+ASBticodVaRDGwqF1k5GQUG8hVZA== X-Google-Smtp-Source: AFSGD/WQD/RE+5tEzWyD025ciYbkObwvlK2dicWiBxl6Xcxv07Pb0jIn/BVxO9WqgLe2tXKCJLdb5c2CAiCdMjKnitI= X-Received: by 2002:a19:2755:: with SMTP id n82mr12762571lfn.94.1545259615325; Wed, 19 Dec 2018 14:46:55 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Steven Hartland Date: Wed, 19 Dec 2018 22:46:44 +0000 Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Matthew Macy Cc: freebsd-current , freebsd-fs X-Rspamd-Queue-Id: ABAD8742DB X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=multiplay-co-uk.20150623.gappssmtp.com header.s=20150623 header.b=q7/EAzxt; spf=pass (mx1.freebsd.org: domain of steven@multiplay.co.uk designates 2a00:1450:4864:20::136 as permitted sender) smtp.mailfrom=steven@multiplay.co.uk X-Spamd-Result: default: False [-3.72 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; R_DKIM_ALLOW(-0.20)[multiplay-co-uk.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; NEURAL_HAM_LONG(-0.99)[-0.992,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[multiplay.co.uk]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[multiplay-co-uk.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[ASPMX.L.GOOGLE.COM,ALT2.ASPMX.L.GOOGLE.COM,ALT1.ASPMX.L.GOOGLE.COM,ASPMX2.GOOGLEMAIL.COM,ASPMX3.GOOGLEMAIL.COM]; RCVD_IN_DNSWL_NONE(0.00)[6.3.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.90)[-0.904,0]; IP_SCORE(-0.62)[ipnet: 2a00:1450::/32(-1.60), asn: 15169(-1.40), country: US(-0.08)]; FORGED_SENDER(0.30)[killing@multiplay.co.uk,steven@multiplay.co.uk]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[killing@multiplay.co.uk,steven@multiplay.co.uk]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 22:46:59 -0000 Thanks for the write up most appreciated. One of the more meaty differences is that FreeBSD ZFS still has the only merged and production ready TRIM support so my question would be are their any plans to address this before creating the new port as going back to a world without TRIM support wouldn=E2=80=99t be something I=E2=80=99d look forward to. On Wed, 19 Dec 2018 at 06:51, Matthew Macy wrote: > The sources for FreeBSD's ZFS support are currently taken directly > from Illumos with local ifdefs to support the peculiarities of FreeBSD > where the Solaris Portability Layer (SPL) shims fall short. FreeBSD > has regularly pulled changes from Illumos and tried to push back any > bug fixes and new features done in the context of FreeBSD. In the past > few years the vast majority of new development in ZFS has taken place > in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced > that they will be moving to ZoL > https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means > that there will be little to no net new development of Illumos. While > working through the git history of ZoL I have also discovered that > many races and locking bugs have been fixed in ZoL and never made it > back to Illumos and thus FreeBSD. This state of affairs has led to a > general agreement among the stakeholders that I have spoken to that it > makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf > has graciously encouraged me to add FreeBSD support directly to ZoL > https://github.com/zfsonfreebsd/ZoF so that we might all have a single > shared code base. > > A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port > Before it can be committed some additional functionality needs to be > added to the FreeBSD opencrypto framework. These can be found at > https://reviews.freebsd.org/D18520 > > This port will provide FreeBSD users with multi modifier protection, > project quotas, encrypted datasets, allocation classes, vectorized > raidz, vectorized checksums, and various command line improvements. > > Before ZoF can be merged back in to ZoL several steps need to be taken: > - Integrate FreeBSD support into ZoL CI > - Have most of the ZFS test suite passing > - Complete additional QA testing at iX > > We at iX Systems need to port ZoL's EC2 CI scripts to work with > FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. > Being integrated in to their CI will mean that, among other things, > most integration issues will be caught before a PR is merged upstream > rather than many months later when it is MFVed into FreeBSD. I=E2=80=99m > hoping to submit the PR to ZoL some time in January. > > This port will make it easy for end users on a range of releases to > run the latest version of ZFS. Nonetheless, transitioning away from an > Illumos based ZFS is not likely to be entirely seamless. The > stakeholders I=E2=80=99ve spoken to all agree that this is the best path > forward but some degree of effort needs to be made to accommodate > downstream consumers. The current plan is to import ZoF and unhook the > older Illumos based sources from the build on April 15th or two months > after iX systems QA deems ZoF stable - which ever comes later. The > Illumos based sources will be removed some time later - but well > before 13. This will give users a 3 month period during which both the > port and legacy Illumos based ZFS will be available to users. Pools > should interoperate between ZoF and legacy provided the user does not > enable any features available only in ZoF. We will try to accommodate > any downstream consumers in the event that they need that date pushed > back. We ask that any downstream consumers who are particularly > sensitive to changes start testing the port when it is formally > announced and report back any issues they have. I will do my best to > ensure that this message is communicated to all those who it may > concern. However, I can=E2=80=99t ensure that everyone reads these lists.= That > is the responsibility of -CURRENT users. > > -M > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Wed Dec 19 22:52:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49E50134C10C; Wed, 19 Dec 2018 22:52:30 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E199A74C53; Wed, 19 Dec 2018 22:52:29 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-io1-f43.google.com (mail-io1-f43.google.com [209.85.166.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id AB4795E3C; Wed, 19 Dec 2018 22:52:29 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-io1-f43.google.com with SMTP id l14so16928294ioj.5; Wed, 19 Dec 2018 14:52:29 -0800 (PST) X-Gm-Message-State: AA+aEWYcclioekmN1H96Whvq+gldXirvD0Sa+KZic86Te1jc4/tSbJwF f38HRUv2hUzT9G1fYOGysXoeeynHNyDm2acWnCc= X-Google-Smtp-Source: AFSGD/VstMykI/2JblKobGbwAbThi/E5wXJtdfND8/+aJ+XCT4RFjTq3poqgS9+ZTP6DefoC+JlTovszjnU/ji8jXcw= X-Received: by 2002:a6b:8f8d:: with SMTP id r135mr19621676iod.5.1545259949011; Wed, 19 Dec 2018 14:52:29 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Matthew Macy Date: Wed, 19 Dec 2018 14:52:17 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Steven Hartland Cc: freebsd-current , freebsd-fs X-Rspamd-Queue-Id: E199A74C53 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.985,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 22:52:30 -0000 On Wed, Dec 19, 2018 at 14:47 Steven Hartland wrote: > Thanks for the write up most appreciated. One of the more meaty > differences is that FreeBSD ZFS still has the only merged and production > ready TRIM support so my question would be are their any plans to address > this before creating the new port as going back to a world without TRIM > support wouldn=E2=80=99t be something I=E2=80=99d look forward to. > Well, then please follow up on the request I CC'd you on a week ago asking that you engage on the deadlist based TRIM PR. That's a better forum for discussing these details than lamenting in public lists. Thanks. -M > On Wed, 19 Dec 2018 at 06:51, Matthew Macy wrote: > >> The sources for FreeBSD's ZFS support are currently taken directly >> from Illumos with local ifdefs to support the peculiarities of FreeBSD >> where the Solaris Portability Layer (SPL) shims fall short. FreeBSD >> has regularly pulled changes from Illumos and tried to push back any >> bug fixes and new features done in the context of FreeBSD. In the past >> few years the vast majority of new development in ZFS has taken place >> in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced >> that they will be moving to ZoL >> https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means >> that there will be little to no net new development of Illumos. While >> working through the git history of ZoL I have also discovered that >> many races and locking bugs have been fixed in ZoL and never made it >> back to Illumos and thus FreeBSD. This state of affairs has led to a >> general agreement among the stakeholders that I have spoken to that it >> makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf >> has graciously encouraged me to add FreeBSD support directly to ZoL >> https://github.com/zfsonfreebsd/ZoF so that we might all have a single >> shared code base. >> >> A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port >> Before it can be committed some additional functionality needs to be >> added to the FreeBSD opencrypto framework. These can be found at >> https://reviews.freebsd.org/D18520 >> >> This port will provide FreeBSD users with multi modifier protection, >> project quotas, encrypted datasets, allocation classes, vectorized >> raidz, vectorized checksums, and various command line improvements. >> >> Before ZoF can be merged back in to ZoL several steps need to be taken: >> - Integrate FreeBSD support into ZoL CI >> - Have most of the ZFS test suite passing >> - Complete additional QA testing at iX >> >> We at iX Systems need to port ZoL's EC2 CI scripts to work with >> FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. >> Being integrated in to their CI will mean that, among other things, >> most integration issues will be caught before a PR is merged upstream >> rather than many months later when it is MFVed into FreeBSD. I=E2=80=99m >> hoping to submit the PR to ZoL some time in January. >> >> This port will make it easy for end users on a range of releases to >> run the latest version of ZFS. Nonetheless, transitioning away from an >> Illumos based ZFS is not likely to be entirely seamless. The >> stakeholders I=E2=80=99ve spoken to all agree that this is the best path >> forward but some degree of effort needs to be made to accommodate >> downstream consumers. The current plan is to import ZoF and unhook the >> older Illumos based sources from the build on April 15th or two months >> after iX systems QA deems ZoF stable - which ever comes later. The >> Illumos based sources will be removed some time later - but well >> before 13. This will give users a 3 month period during which both the >> port and legacy Illumos based ZFS will be available to users. Pools >> should interoperate between ZoF and legacy provided the user does not >> enable any features available only in ZoF. We will try to accommodate >> any downstream consumers in the event that they need that date pushed >> back. We ask that any downstream consumers who are particularly >> sensitive to changes start testing the port when it is formally >> announced and report back any issues they have. I will do my best to >> ensure that this message is communicated to all those who it may >> concern. However, I can=E2=80=99t ensure that everyone reads these lists= . That >> is the responsibility of -CURRENT users. >> >> -M >> > _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> > From owner-freebsd-current@freebsd.org Wed Dec 19 23:11:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB78A134CC12 for ; Wed, 19 Dec 2018 23:11:12 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 851D276091 for ; Wed, 19 Dec 2018 23:11:11 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: by mail-lf1-x136.google.com with SMTP id v5so16329285lfe.7 for ; Wed, 19 Dec 2018 15:11:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c7Dea6s43TH+P3wVxfgVcN5wbIs+u84XhTeMRL6khbk=; b=e/9uaC1pKHXURuDsd1YoFWsJFUey3ACuiUKWQTjm7MTLY7Kgz/fWv9R4w1dTZJbX+R yE1yypRgT7LZJRMjI727z7BP6Z/o6tgcTD9iW+chMro/RdbyHnKvAHAdCuGEJzdx+RrX zoBWRU+q2KnRrqSe/BK7u8+Wk4C+QGrxN9Hdfzy9GfbjGYxFSQPd3Uz/Ng8P4MIbE4ye qOClWbvD4ATzalCQcBJMVkr5i20e7kQ5xC04KBGRyF5RblaClEGkN4VQxYZ/YTNpQ9/6 zgWgOEIyKsa2YffQz6vWPq8p3AD/uBl07vak7MdR3lWtFymfsahv4n5iZdEhpilU5PZf EQ3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c7Dea6s43TH+P3wVxfgVcN5wbIs+u84XhTeMRL6khbk=; b=Q38tpYSmRm+N8HorxD0HTevKM4DPEtcggx2/6yWm3gBmMs+Z5lo0DlhF4Bwdaz7agw 6/NIMc3j6KK7F5MEnirJcjOmBald4Kk9EfZFSOOscI3r1OfYbUNHQ4owHTkFxlQNZ32r iG0OtVOt+kBTxSkXM1aNDEGWxzcKJbcJIFOuXOWUvBRfMiF9KVZ0knapEsVgd0B/wDd6 hwne+FO72GHT8co3+4c4jjTfyewKb9PS6GUbd2FZBo3L3gXuhJlRGdxdVr4NQxhUbSKS mMdW37SuSUWWQQlpevtJp3Sc9DgoWEB53fzn5zJMifHHuPmKbFNxlHUkHgD/HTSatnIt Shhw== X-Gm-Message-State: AA+aEWZ6kAVsl+FLz0QlVAOShVQt7tketItqcVpajceTCcxyLiE8c/GA joMmRbJUn3etWkTso+dAa0YZo3FxFa253B7wsWSF9g== X-Google-Smtp-Source: AFSGD/WkshJRYak8k9UVXV6nUDeBUZ3JSbUNY1YYEeLf17YgUK1L0LvsyKxuOo59khaRovJCBD3z71RJB1Adc2syZ/w= X-Received: by 2002:a19:5154:: with SMTP id f81mr14370165lfb.96.1545261070008; Wed, 19 Dec 2018 15:11:10 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Steven Hartland Date: Wed, 19 Dec 2018 23:10:58 +0000 Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Matthew Macy Cc: freebsd-current , freebsd-fs X-Rspamd-Queue-Id: 851D276091 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=multiplay-co-uk.20150623.gappssmtp.com header.s=20150623 header.b=e/9uaC1p; spf=pass (mx1.freebsd.org: domain of steven@multiplay.co.uk designates 2a00:1450:4864:20::136 as permitted sender) smtp.mailfrom=steven@multiplay.co.uk X-Spamd-Result: default: False [-3.33 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; R_DKIM_ALLOW(-0.20)[multiplay-co-uk.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; NEURAL_HAM_LONG(-0.99)[-0.992,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[multiplay.co.uk]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[multiplay-co-uk.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ASPMX.L.GOOGLE.COM]; RCVD_IN_DNSWL_NONE(0.00)[6.3.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.52)[-0.516,0]; IP_SCORE(-0.62)[ipnet: 2a00:1450::/32(-1.60), asn: 15169(-1.40), country: US(-0.08)]; FORGED_SENDER(0.30)[killing@multiplay.co.uk,steven@multiplay.co.uk]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[killing@multiplay.co.uk,steven@multiplay.co.uk]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 23:11:13 -0000 Sorry been off for a few weeks so must have missed that, please do prod me on again if you don=E2=80=99t see any response to anything not just this. L= ike many others I get so may emails across so many lists it=E2=80=99s more than like= ly I just missed it. That said would you say that with the right support we can make progress on the this prior to the port? I have to ask as the alternative version has been on the cusp for many years now so it=E2=80=99s feels more like a dista= nt memory than something that may happen, no disrespect to anyone involved, as I know all too well how hard it can be to get something like this over the line, especially when people have competing priorities. On Wed, 19 Dec 2018 at 22:52, Matthew Macy wrote: > > > On Wed, Dec 19, 2018 at 14:47 Steven Hartland > wrote: > >> Thanks for the write up most appreciated. One of the more meaty >> differences is that FreeBSD ZFS still has the only merged and production >> ready TRIM support so my question would be are their any plans to addres= s >> this before creating the new port as going back to a world without TRIM >> support wouldn=E2=80=99t be something I=E2=80=99d look forward to. >> > > Well, then please follow up on the request I CC'd you on a week ago askin= g > that you engage on the deadlist based TRIM PR. That's a better forum for > discussing these details than lamenting in public lists. > > Thanks. > > -M > > > > >> On Wed, 19 Dec 2018 at 06:51, Matthew Macy wrote: >> >>> The sources for FreeBSD's ZFS support are currently taken directly >>> from Illumos with local ifdefs to support the peculiarities of FreeBSD >>> where the Solaris Portability Layer (SPL) shims fall short. FreeBSD >>> has regularly pulled changes from Illumos and tried to push back any >>> bug fixes and new features done in the context of FreeBSD. In the past >>> few years the vast majority of new development in ZFS has taken place >>> in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced >>> that they will be moving to ZoL >>> https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means >>> that there will be little to no net new development of Illumos. While >>> working through the git history of ZoL I have also discovered that >>> many races and locking bugs have been fixed in ZoL and never made it >>> back to Illumos and thus FreeBSD. This state of affairs has led to a >>> general agreement among the stakeholders that I have spoken to that it >>> makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf >>> has graciously encouraged me to add FreeBSD support directly to ZoL >>> https://github.com/zfsonfreebsd/ZoF so that we might all have a single >>> shared code base. >>> >>> A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port >>> Before it can be committed some additional functionality needs to be >>> added to the FreeBSD opencrypto framework. These can be found at >>> https://reviews.freebsd.org/D18520 >>> >>> This port will provide FreeBSD users with multi modifier protection, >>> project quotas, encrypted datasets, allocation classes, vectorized >>> raidz, vectorized checksums, and various command line improvements. >>> >>> Before ZoF can be merged back in to ZoL several steps need to be taken: >>> - Integrate FreeBSD support into ZoL CI >>> - Have most of the ZFS test suite passing >>> - Complete additional QA testing at iX >>> >>> We at iX Systems need to port ZoL's EC2 CI scripts to work with >>> FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. >>> Being integrated in to their CI will mean that, among other things, >>> most integration issues will be caught before a PR is merged upstream >>> rather than many months later when it is MFVed into FreeBSD. I=E2=80=99= m >>> hoping to submit the PR to ZoL some time in January. >>> >>> This port will make it easy for end users on a range of releases to >>> run the latest version of ZFS. Nonetheless, transitioning away from an >>> Illumos based ZFS is not likely to be entirely seamless. The >>> stakeholders I=E2=80=99ve spoken to all agree that this is the best pat= h >>> forward but some degree of effort needs to be made to accommodate >>> downstream consumers. The current plan is to import ZoF and unhook the >>> older Illumos based sources from the build on April 15th or two months >>> after iX systems QA deems ZoF stable - which ever comes later. The >>> Illumos based sources will be removed some time later - but well >>> before 13. This will give users a 3 month period during which both the >>> port and legacy Illumos based ZFS will be available to users. Pools >>> should interoperate between ZoF and legacy provided the user does not >>> enable any features available only in ZoF. We will try to accommodate >>> any downstream consumers in the event that they need that date pushed >>> back. We ask that any downstream consumers who are particularly >>> sensitive to changes start testing the port when it is formally >>> announced and report back any issues they have. I will do my best to >>> ensure that this message is communicated to all those who it may >>> concern. However, I can=E2=80=99t ensure that everyone reads these list= s. That >>> is the responsibility of -CURRENT users. >>> >>> -M >>> >> _______________________________________________ >>> freebsd-fs@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >>> >> From owner-freebsd-current@freebsd.org Wed Dec 19 23:17:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92A2D134D050; Wed, 19 Dec 2018 23:17:05 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 098AE76645; Wed, 19 Dec 2018 23:17:05 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-io1-f43.google.com (mail-io1-f43.google.com [209.85.166.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id CA0DD6073; Wed, 19 Dec 2018 23:17:04 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-io1-f43.google.com with SMTP id p7so9335175iog.12; Wed, 19 Dec 2018 15:17:04 -0800 (PST) X-Gm-Message-State: AJcUukdtrOziwIgjDi250OnYQgqszR9CrLwDlSV4yc1vnyrGibLU4vMQ HFUYsrr3TjfX8MyF2p6dzK3mtK+eu3omhB7rvls= X-Google-Smtp-Source: ALg8bN46ZS+RqLXvrnex9vobP5Mrft7kW8Uzh/eHSZZcBAeWcp1BipVqM8aBGLPVOUqk9mUnTbHfPQQD5+7JIp635dY= X-Received: by 2002:a6b:e014:: with SMTP id z20mr4910iog.237.1545261424604; Wed, 19 Dec 2018 15:17:04 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Matthew Macy Date: Wed, 19 Dec 2018 15:16:53 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Steven Hartland Cc: freebsd-current , freebsd-fs X-Rspamd-Queue-Id: 098AE76645 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.96)[-0.964,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 23:17:05 -0000 On Wed, Dec 19, 2018 at 15:11 Steven Hartland wrote: > Sorry been off for a few weeks so must have missed that, please do prod m= e > on again if you don=E2=80=99t see any response to anything not just this.= Like many > others I get so may emails across so many lists it=E2=80=99s more than li= kely I > just missed it. > > That said would you say that with the right support we can make progress > on the this prior to the port? I have to ask as the alternative version h= as > been on the cusp for many years now so it=E2=80=99s feels more like a dis= tant > memory than something that may happen, no disrespect to anyone involved, = as > I know all too well how hard it can be to get something like this over th= e > line, especially when people have competing priorities. > I am hoping that it's sufficiently important to FreeBSD ZFS developers that they'll give the PR the attention it needs so that it can be merged before summer. My understanding is that it's mostly suffered from neglect. TRIM is most important to FreeBSD and it already had its own implementation. https://github.com/zfsonlinux/zfs/pull/5925 I forwarded you the private communication again as well. -M > > On Wed, 19 Dec 2018 at 22:52, Matthew Macy wrote: > >> >> >> On Wed, Dec 19, 2018 at 14:47 Steven Hartland >> wrote: >> >>> Thanks for the write up most appreciated. One of the more meaty >>> differences is that FreeBSD ZFS still has the only merged and productio= n >>> ready TRIM support so my question would be are their any plans to addre= ss >>> this before creating the new port as going back to a world without TRIM >>> support wouldn=E2=80=99t be something I=E2=80=99d look forward to. >>> >> >> Well, then please follow up on the request I CC'd you on a week ago >> asking that you engage on the deadlist based TRIM PR. That's a better >> forum for discussing these details than lamenting in public lists. >> >> Thanks. >> >> -M >> >> >> >> >>> On Wed, 19 Dec 2018 at 06:51, Matthew Macy wrote: >>> >>>> The sources for FreeBSD's ZFS support are currently taken directly >>>> from Illumos with local ifdefs to support the peculiarities of FreeBSD >>>> where the Solaris Portability Layer (SPL) shims fall short. FreeBSD >>>> has regularly pulled changes from Illumos and tried to push back any >>>> bug fixes and new features done in the context of FreeBSD. In the past >>>> few years the vast majority of new development in ZFS has taken place >>>> in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced >>>> that they will be moving to ZoL >>>> https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means >>>> that there will be little to no net new development of Illumos. While >>>> working through the git history of ZoL I have also discovered that >>>> many races and locking bugs have been fixed in ZoL and never made it >>>> back to Illumos and thus FreeBSD. This state of affairs has led to a >>>> general agreement among the stakeholders that I have spoken to that it >>>> makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf >>>> has graciously encouraged me to add FreeBSD support directly to ZoL >>>> https://github.com/zfsonfreebsd/ZoF so that we might all have a single >>>> shared code base. >>>> >>>> A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port >>>> Before it can be committed some additional functionality needs to be >>>> added to the FreeBSD opencrypto framework. These can be found at >>>> https://reviews.freebsd.org/D18520 >>>> >>>> This port will provide FreeBSD users with multi modifier protection, >>>> project quotas, encrypted datasets, allocation classes, vectorized >>>> raidz, vectorized checksums, and various command line improvements. >>>> >>>> Before ZoF can be merged back in to ZoL several steps need to be taken= : >>>> - Integrate FreeBSD support into ZoL CI >>>> - Have most of the ZFS test suite passing >>>> - Complete additional QA testing at iX >>>> >>>> We at iX Systems need to port ZoL's EC2 CI scripts to work with >>>> FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. >>>> Being integrated in to their CI will mean that, among other things, >>>> most integration issues will be caught before a PR is merged upstream >>>> rather than many months later when it is MFVed into FreeBSD. I=E2=80= =99m >>>> hoping to submit the PR to ZoL some time in January. >>>> >>>> This port will make it easy for end users on a range of releases to >>>> run the latest version of ZFS. Nonetheless, transitioning away from an >>>> Illumos based ZFS is not likely to be entirely seamless. The >>>> stakeholders I=E2=80=99ve spoken to all agree that this is the best pa= th >>>> forward but some degree of effort needs to be made to accommodate >>>> downstream consumers. The current plan is to import ZoF and unhook the >>>> older Illumos based sources from the build on April 15th or two months >>>> after iX systems QA deems ZoF stable - which ever comes later. The >>>> Illumos based sources will be removed some time later - but well >>>> before 13. This will give users a 3 month period during which both the >>>> port and legacy Illumos based ZFS will be available to users. Pools >>>> should interoperate between ZoF and legacy provided the user does not >>>> enable any features available only in ZoF. We will try to accommodate >>>> any downstream consumers in the event that they need that date pushed >>>> back. We ask that any downstream consumers who are particularly >>>> sensitive to changes start testing the port when it is formally >>>> announced and report back any issues they have. I will do my best to >>>> ensure that this message is communicated to all those who it may >>>> concern. However, I can=E2=80=99t ensure that everyone reads these lis= ts. That >>>> is the responsibility of -CURRENT users. >>>> >>>> -M >>>> >>> _______________________________________________ >>>> freebsd-fs@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >>>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >>>> >>> From owner-freebsd-current@freebsd.org Thu Dec 20 00:21:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D27FE134F231 for ; Thu, 20 Dec 2018 00:21:51 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-9.consmr.mail.gq1.yahoo.com (sonic315-9.consmr.mail.gq1.yahoo.com [98.137.65.33]) (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 F32A68130F for ; Thu, 20 Dec 2018 00:21:49 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: I3KdwRkVM1mM2acaFyvT1QHpEk2EmAVZlcHv9TLlT7oDF0Q8YzNiYfMJMzofCTe mKbEDfEHTR8mY9tYoxARpQhZDhy8xBkyHkfwWTRfnVKAmXuCeEUpRp5hFLNlNnDOxZJQiWqZ7D48 28pxxs6Jvy4BVsuinz6uRvCcLg_cn_5pTEUQ2Uny6uMJ_xiL3Wa2i6GtQKsCfUhyqETK5e5n0miT zL0X5JPrpBq5v4YvKGGMRn6v9RcmzM4sTuJaWeyzL2XbziLazMJ71OW86I5mizEUsaAXCsQtrrfV vHWPMPfUyfGep0BKjH7f7s.BdQ7qf8N6zRh46T8uNTdywn4oskOtCZD9ZKqAqBUln1b3wgqhSmZg Nu1KMe.ojY9.Y5_rWqIV5rLYGl6gxr48fhDkO3ZIX.xSYxH282m7LvlKbSr4tH5uxUvISKAoTfzh LqjwPjh7RJI8AkwBMIEpaKIhbY0KLovDN_i.D5tUpM08yIuMJ6z3tBM0.52EPCgU9J5P5jqBYWXa 0cM3swQgxUOykMTexjCnueURsX2y3e5GGRj7I1GhMw7OUp5.3K31Fmu2ICPPIoeOQkbDOm5lvV6m DutifmkwKVh.xReTcdN4vUa7hnI4Cpq9l2fCvPsI8V4J7Ozk9RNE7O.9mEzTKh_ldv4OEHOu2SB7 tzNVApvtwPh24F27ev8loSbuRZYvnL0V.LkjflCEK1xDfy20WK06ZJ3pwGJY.qf5zCqvOBlRFbZY wjRdYed1NF2n9sohIO1uPCK89n4qXMvz5lqNxI1ZrKt6hqLP4K4xHmkM5gsKLVk7HF0yaViT.H54 3ypZqKkdN5vI42SEAi6ZZyI1i5dEg1IQIZPSVnlY..te4ZQ40_t95.R08MozGHS1TaSIIN5DXKmT nRYWxSDgDvBaonCnXDDPtIKV5q6M38XXIglwDKx1C2n3bl8.ZleCVgvpjrhEgXQ9oIXO3YuQmFeS XydcxOD9XExcdjknNPTKKrlEgZ7mpTMEe5D0PhCPezS_eaJiIFP4mmiFFtSnXwE.9ep0KGYNEE3g zsyp.8PfGqJZRvPThmYGRoWM4wGcTihpgUW9KTHoAUh2uYA9NUj0.cg3bieIhodJxSQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Thu, 20 Dec 2018 00:21:48 +0000 Received: from c-67-170-167-181.hsd1.or.comcast.net (EHLO [192.168.1.109]) ([67.170.167.181]) by smtp413.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4455f6c70c5b45e5ff84e81aa1b6e7de; Thu, 20 Dec 2018 00:21:43 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: FreeBSD head -r341836 amd64->aarch64 cross-build of -r484783 ports via poudriere: devel/qt5-testlib hung-up during "Checking for POSIX monotonic clock" Date: Wed, 19 Dec 2018 16:21:42 -0800 References: <190D54A2-D29A-4B62-B8FF-99514DBE92A0@yahoo.com> To: freebsd-arm , FreeBSD Current , ports-list freebsd In-Reply-To: Message-Id: <8A63BA63-FBCB-40DA-B031-4C7F4B1F5118@yahoo.com> X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: F32A68130F X-Spamd-Bar: - X-Spamd-Result: default: False [-1.88 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MV_CASE(0.50)[]; FREEMAIL_FROM(0.00)[yahoo.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.994,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.38)[0.383,0]; NEURAL_HAM_LONG(-0.97)[-0.971,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.22)[ipnet: 98.137.64.0/21(0.65), asn: 36647(0.52), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[33.65.137.98.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 00:21:52 -0000 [I attached to the hung-up process with gdb and looked around a little.] On 2018-Dec-19, at 13:58, Mark Millard wrote: > [Looks like a race or some such for devel/qt5-testlib: retry of = poudreire-devel > did not hang. The other hang-up seems to be repeating and I give some = details.] >=20 > On 2018-Dec-19, at 12:20, Mark Millard wrote: >=20 >> FYI: Based on FreeBSD head -r341836 (host and target) and ports = -r484783 . This >> was a rebuild based on going from perl5.26 to perl5.28 without = updating the ports >> tree and from system clang 6 for the prior FreeBSD-head context used = to clang 7 >> this time. (I'm not attributing causes here.) poudriere was using = amd64-native >> tools for speeding up the cross-build. >>=20 >> # grep -r =3Dperl5=3D /etc/ ~/src.configs/ /usr/local/etc/ >> /etc/make.conf:DEFAULT_VERSIONS+=3Dperl5=3D5.28 gcc=3D8 >> /usr/local/etc/poudriere.d/make.conf:DEFAULT_VERSIONS+=3Dperl5=3D5.28 = gcc=3D8 >>=20 >> There was also a "print/texinfo:configure/runaway" but I've not = looked into >> it at all yet and it may be a while before I do. The other ports = attempted >> built fine as far as I can tell so far. >>=20 >>=20 >> The devel/qt5-testlib failure looks like: >>=20 >> [00:00:13] Building 123 packages using 28 builders >> . . . >> [00:49:30] [10] [00:00:00] Building devel/qt5-testlib | = qt5-testlib-5.11.2 >> . . . >> [07:31:31] [10] [06:42:01] Saved devel/qt5-testlib | = qt5-testlib-5.11.2 wrkdir to: = /usr/local/poudriere/data/wrkdirs/FBSDFSSDjailCortexA57-default/default/qt= 5-testlib-5.11.2.tar >> [07:31:32] [10] [06:42:02] Finished devel/qt5-testlib | = qt5-testlib-5.11.2: Failed: configure/runaway >>=20 >> With logs/errors/qt5-testlib-5.11.2.log showing: >>=20 >> Checking for POSIX monotonic clock...=20 >> + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin= /qmake "CONFIG -=3D qt debug_and_release app_bundle lib_bundle" "CONFIG = +=3D shared warn_off console single_arch" = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic >> + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && MAKEFLAGS=3D make >> =3D>> Killing runaway build after 21600 seconds with no output >> =3D>> Cleaning up wrkdir >> =3D=3D=3D> Cleaning for qt5-testlib-5.11.2 >> Killed >> build of devel/qt5-testlib | qt5-testlib-5.11.2 ended at Wed Dec 19 = 06:45:42 PST 2018 >> build time: 06:41:46 >> !!! build failure encountered !!! >>=20 >>=20 >> # less = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.log >> . . . >> test config.qtbase_corelib.libraries.librt succeeded >> executing config test clock-monotonic >> + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin= /qmake "CONFIG -=3D qt debug_and_release app_bundle lib_bundle" "CONFIG = +=3D shared warn_off console single_arch" = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic >> + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && MAKEFLAGS=3D make >>=20 >>=20 >> Some supporting details of context: >>=20 >> # uname -apKU >> FreeBSD FBSDFSSD 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r341836M: Tue = Dec 11 16:37:42 PST 2018 = markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/G= ENERIC-NODBG amd64 amd64 1300005 1300005 >>=20 >> # svnlite info /usr/ports/ | grep "Re[plv]" >> Relative URL: ^/head >> Repository Root: svn://svn.freebsd.org/ports >> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 >> Revision: 484783 >> Last Changed Rev: 484783 >>=20 >=20 > I started poudriere up again with just the 2 needing to be rebuilt = (plus > what depends on the 2). devel/qt5-testlib quickly completed just fine: >=20 > [00:02:16] [02] [00:00:00] Building devel/qt5-testlib | = qt5-testlib-5.11.2 > [00:04:54] [02] [00:02:38] Finished devel/qt5-testlib | = qt5-testlib-5.11.2: Success >=20 >=20 > In the prior build that had the hang-ups I looked and dor = print/texinfo : >=20 > /wrkdirs/usr/ports/print/texinfo/work/texinfo-6.5/config.log shows for = its > hang-up: >=20 > . . . > configure:6639: checking for alloca > configure:6676: /nxb-bin/usr/bin/cc -o conftest -O2 -pipe = -mcpu=3Dcortex-a57 -DLIBICONV_PLUG -g -fno-strict-aliasing = -mcpu=3Dcortex-a57 -DLIBICONV_PLUG -D_THREAD_SAFE conftest.c >&5 > configure:6676: $? =3D 0 > configure:6684: result: yes > configure:6794: checking for C/C++ restrict keyword > configure:6821: /nxb-bin/usr/bin/cc -c -O2 -pipe -mcpu=3Dcortex-a57 = -DLIBICONV_PLUG -g -fno-strict-aliasing -mcpu=3Dcortex-a57 = -DLIBICONV_PLUG -D_THREAD_SAFE conftest.c >&5 > configure:6821: $? =3D 0 > configure:6829: result: __restrict > configure:6844: checking whether // is distinct from / >=20 >=20 > In the poudriere re-run print/texinfo seems to be not progressing: >=20 > root 87913 0.0 0.0 12920 3668 0 I 13:29 0:00.06 = | | `-- sh: poudriere[FBSDFSSDjailCortexA57-default][01]: = build_pkg (texinfo-6.5_1,1) (sh) > root 88869 0.0 0.0 12920 3660 0 I 13:29 0:00.00 = | | `-- sh: poudriere[FBSDFSSDjailCortexA57-default][01]: = build_pkg (texinfo-6.5_1,1) (sh) > root 88870 0.0 0.0 10412 1848 0 IJ 13:29 0:00.01 = | | `-- /usr/bin/make -C /usr/ports/print/texinfo = configure > root 88974 0.0 0.0 10272 1812 0 IJ 13:30 0:00.00 = | | `-- /bin/sh -e -c (cd = /wrkdirs/usr/ports/print/texinfo/work/texinfo-6.5 && = _LATE_CONFIGURE_ARGS=3D"" ; if [=20 > root 89283 0.0 0.0 11160 2108 0 IJ 13:30 0:00.10 = | | `-- /bin/sh ./configure --enable-nls = --prefix=3D/usr/local --localstatedir=3D/var --mandir=3D/usr/local/man = --di > root 89692 0.0 0.0 227368 14504 0 IJ 13:30 0:00.03 = | | `-- /usr/local/bin/qemu-aarch64-static wc = //dev/null > root 89694 0.0 0.0 227424 14596 0 IJ 13:30 0:00.01 = | | `-- /usr/local/bin/qemu-aarch64-static wc = //dev/null > root 89695 0.0 0.0 227584 14720 0 IJ 13:30 0:00.01 = | | `-- wc: zygote (qemu-aarch64-static) >=20 >=20 > So it appears that: >=20 > /usr/local/bin/qemu-aarch64-static wc //dev/null >=20 > is hanging-up (again). >=20 >=20 > Given that these are hangups I'll note that this is a Ryzen > Threadripper 1950X context and is running under Hyper-V from > Windows 10's 1809 update. I gave it 28 logical processors and > have it to have the virtual NUMA topology match the topology of > the physical hardware: "Use Hardware Topology". (Processors > 28, NUMA nodes 2, Sockets 1, Hardware threads per core 2.) Attaching to the stuck process via gdb and looking at the backtrace shows: (gdb) attach 89695 Attaching to program: /usr/local/bin/qemu-aarch64-static, process 89695 [New LWP 101548 of process 89695] [Switching to LWP 100804 of process 89695] _pselect () at _pselect.S:3 3 PSEUDO(pselect) (gdb) bt #0 _pselect () at _pselect.S:3 #1 0x00000000601da57f in __thr_pselect (count=3D12, = rfds=3D0x7ffffffe3650, wfds=3D0x0, efds=3D0x0, timo=3D0x0, = mask=3D0x7ffffffe3600) at /usr/src/lib/libthr/thread/thr_syscalls.c:378 #2 0x000000006004928d in do_freebsd_select (env=3D0x860edfb18, = n=3D, rfd_addr=3D140736934698744, wfd_addr=3D, efd_addr=3D0, target_tv_addr=3D0) at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/freebsd/os-time.h:468 #3 do_freebsd_syscall (cpu_env=3D0x860edfb18, num=3D93, arg1=3D12, = arg2=3D140736934698744, arg3=3D0, arg4=3D0, arg5=3D0, arg6=3D274914043516,= arg7=3D274913946564, arg8=3D6579811) at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/syscall.c:1106 #4 0x000000006003903c in target_cpu_loop (env=3D0x860edfb18) at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/aarch64/target_arch_cpu.h:100 #5 0x0000000060038e09 in cpu_loop (env=3D0xc) at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/main.c:121 #6 0x0000000060039ecb in main (argc=3D, = argv=3D0x7fffffffd360) at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/main.c:513 (gdb) up #1 0x00000000601da57f in __thr_pselect (count=3D12, = rfds=3D0x7ffffffe3650, wfds=3D0x0, efds=3D0x0, timo=3D0x0, = mask=3D0x7ffffffe3600) at /usr/src/lib/libthr/thread/thr_syscalls.c:378 378 ret =3D __sys_pselect(count, rfds, wfds, efds, timo, = mask); (gdb) print *rfds $1 =3D {__fds_bits =3D {2048, 0 }} (gdb) info threads Id Target Id Frame=20 * 1 LWP 100804 of process 89695 _pselect () at _pselect.S:3 2 LWP 101548 of process 89695 _umtx_op_err () at = /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 (gdb) thread 2=20 [Switching to thread 2 (LWP 101548 of process 89695)] #0 _umtx_op_err () at = /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 37 RSYSCALL_ERR(_umtx_op) (gdb) bt #0 _umtx_op_err () at = /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 #1 0x00000000601d2ec0 in _thr_umtx_timedwait_uint (mtx=3D0x861027008, = id=3D, clockid=3D, abstime=3D, shared=3D) at /usr/src/lib/libthr/thread/thr_umtx.c:236 #2 0x00000000601dc6f8 in cond_wait_user (cvp=3D, = mp=3D0x860515b00, abstime=3D0x0, cancel=3D1) at = /usr/src/lib/libthr/thread/thr_cond.c:307 #3 cond_wait_common (cond=3D, mutex=3D, = abstime=3D0x0, cancel=3D1) at /usr/src/lib/libthr/thread/thr_cond.c:367 #4 0x00000000601438bc in qemu_futex_wait (ev=3D, = val=3D4294967295) at util/qemu-thread-posix.c:350 #5 qemu_event_wait (ev=3D0x62735d10 ) at = util/qemu-thread-posix.c:445 #6 0x000000006014a92a in call_rcu_thread (opaque=3D) at = util/rcu.c:255 #7 0x00000000601dc376 in thread_start (curthread=3D0x860518e00) at = /usr/src/lib/libthr/thread/thr_create.c:291 #8 0x0000000000000000 in ?? () Backtrace stopped: Cannot access memory at address 0x7fffdfdfc000 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Thu Dec 20 11:04:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63E3B1340F3C; Thu, 20 Dec 2018 11:04:20 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) (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 9BD3172E3E; Thu, 20 Dec 2018 11:04:09 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from [194.32.164.27] ([194.32.164.27]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id wBKB40so076885; Thu, 20 Dec 2018 11:04:00 GMT (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: The future of ZFS in FreeBSD From: Bob Bishop In-Reply-To: Date: Thu, 20 Dec 2018 11:03:59 +0000 Cc: Steven Hartland , freebsd-current , freebsd-fs Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Matthew Macy X-Mailer: Apple Mail (2.3273) X-Rspamd-Queue-Id: 9BD3172E3E X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of rb@gid.co.uk designates 194.32.164.250 as permitted sender) smtp.mailfrom=rb@gid.co.uk X-Spamd-Result: default: False [0.17 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.35)[-0.354,0]; MX_INVALID(0.50)[greylisted]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[gid.co.uk]; NEURAL_SPAM_SHORT(0.28)[0.282,0]; NEURAL_HAM_LONG(-0.12)[-0.121,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[250.164.32.194.list.dnswl.org : 127.0.10.0]; IP_SCORE(-0.34)[asn: 42831(-1.58), country: GB(-0.10)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42831, ipnet:194.32.164.0/24, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 11:04:20 -0000 Hi, > On 19 Dec 2018, at 23:16, Matthew Macy wrote: >=20 > On Wed, Dec 19, 2018 at 15:11 Steven Hartland = > wrote: >=20 >> Sorry been off for a few weeks so must have missed that, please do = prod me >> on again if you don=E2=80=99t see any response to anything not just = this. Like many >> others I get so may emails across so many lists it=E2=80=99s more = than likely I >> just missed it. >>=20 >> That said would you say that with the right support we can make = progress >> on the this prior to the port? I have to ask as the alternative = version has >> been on the cusp for many years now so it=E2=80=99s feels more like a = distant >> memory than something that may happen, no disrespect to anyone = involved, as >> I know all too well how hard it can be to get something like this = over the >> line, especially when people have competing priorities. >>=20 >=20 > I am hoping that it's sufficiently important to FreeBSD ZFS developers = that > they'll give the PR the attention it needs so that it can be merged = before > summer. My understanding is that it's mostly suffered from neglect. = TRIM is > most important to FreeBSD and it already had its own implementation. >=20 > https://github.com/zfsonlinux/zfs/pull/5925 Please correct me if I=E2=80=99m wrong but this looks a lot less mature = than FreeBSD=E2=80=99s existing TRIM support for ZFS which we=E2=80=99ve = had in production for six years. What is the rationale here? I=E2=80=99m concerned that it looks like an = opportunity for mighty regressions. > I forwarded you the private communication again as well. >=20 > -M >=20 >=20 >>=20 >> On Wed, 19 Dec 2018 at 22:52, Matthew Macy wrote: >>=20 >>>=20 >>>=20 >>> On Wed, Dec 19, 2018 at 14:47 Steven Hartland = >>> wrote: >>>=20 >>>> Thanks for the write up most appreciated. One of the more meaty >>>> differences is that FreeBSD ZFS still has the only merged and = production >>>> ready TRIM support so my question would be are their any plans to = address >>>> this before creating the new port as going back to a world without = TRIM >>>> support wouldn=E2=80=99t be something I=E2=80=99d look forward to. >>>>=20 >>>=20 >>> Well, then please follow up on the request I CC'd you on a week ago >>> asking that you engage on the deadlist based TRIM PR. That's a = better >>> forum for discussing these details than lamenting in public lists. >>>=20 >>> Thanks. >>>=20 >>> -M >>>=20 >>>=20 >>>=20 >>>=20 >>>> On Wed, 19 Dec 2018 at 06:51, Matthew Macy = wrote: >>>>=20 >>>>> The sources for FreeBSD's ZFS support are currently taken directly >>>>> from Illumos with local ifdefs to support the peculiarities of = FreeBSD >>>>> where the Solaris Portability Layer (SPL) shims fall short. = FreeBSD >>>>> has regularly pulled changes from Illumos and tried to push back = any >>>>> bug fixes and new features done in the context of FreeBSD. In the = past >>>>> few years the vast majority of new development in ZFS has taken = place >>>>> in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix = announced >>>>> that they will be moving to ZoL >>>>> https://www.delphix.com/blog/kickoff-future-eko-2018 This shift = means >>>>> that there will be little to no net new development of Illumos. = While >>>>> working through the git history of ZoL I have also discovered that >>>>> many races and locking bugs have been fixed in ZoL and never made = it >>>>> back to Illumos and thus FreeBSD. This state of affairs has led to = a >>>>> general agreement among the stakeholders that I have spoken to = that it >>>>> makes sense to rebase FreeBSD's ZFS on ZoL. Brian Behlendorf >>>>> has graciously encouraged me to add FreeBSD support directly to = ZoL >>>>> https://github.com/zfsonfreebsd/ZoF so that we might all have a = single >>>>> shared code base. >>>>>=20 >>>>> A port for ZoF can be found at = https://github.com/miwi-fbsd/zof-port >>>>> Before it can be committed some additional functionality needs to = be >>>>> added to the FreeBSD opencrypto framework. These can be found at >>>>> https://reviews.freebsd.org/D18520 >>>>>=20 >>>>> This port will provide FreeBSD users with multi modifier = protection, >>>>> project quotas, encrypted datasets, allocation classes, vectorized >>>>> raidz, vectorized checksums, and various command line = improvements. >>>>>=20 >>>>> Before ZoF can be merged back in to ZoL several steps need to be = taken: >>>>> - Integrate FreeBSD support into ZoL CI >>>>> - Have most of the ZFS test suite passing >>>>> - Complete additional QA testing at iX >>>>>=20 >>>>> We at iX Systems need to port ZoL's EC2 CI scripts to work with >>>>> FreeBSD and make sure that most of the ZFS Test Suite (ZTS) = passes. >>>>> Being integrated in to their CI will mean that, among other = things, >>>>> most integration issues will be caught before a PR is merged = upstream >>>>> rather than many months later when it is MFVed into FreeBSD. I=E2=80= =99m >>>>> hoping to submit the PR to ZoL some time in January. >>>>>=20 >>>>> This port will make it easy for end users on a range of releases = to >>>>> run the latest version of ZFS. Nonetheless, transitioning away = from an >>>>> Illumos based ZFS is not likely to be entirely seamless. The >>>>> stakeholders I=E2=80=99ve spoken to all agree that this is the = best path >>>>> forward but some degree of effort needs to be made to accommodate >>>>> downstream consumers. The current plan is to import ZoF and unhook = the >>>>> older Illumos based sources from the build on April 15th or two = months >>>>> after iX systems QA deems ZoF stable - which ever comes later. The >>>>> Illumos based sources will be removed some time later - but well >>>>> before 13. This will give users a 3 month period during which both = the >>>>> port and legacy Illumos based ZFS will be available to users. = Pools >>>>> should interoperate between ZoF and legacy provided the user does = not >>>>> enable any features available only in ZoF. We will try to = accommodate >>>>> any downstream consumers in the event that they need that date = pushed >>>>> back. We ask that any downstream consumers who are particularly >>>>> sensitive to changes start testing the port when it is formally >>>>> announced and report back any issues they have. I will do my best = to >>>>> ensure that this message is communicated to all those who it may >>>>> concern. However, I can=E2=80=99t ensure that everyone reads these = lists. That >>>>> is the responsibility of -CURRENT users. >>>>>=20 >>>>> -M >>>>>=20 >>>> _______________________________________________ >>>>> freebsd-fs@freebsd.org mailing list >>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >>>>> To unsubscribe, send any mail to = "freebsd-fs-unsubscribe@freebsd.org" >>>>>=20 >>>>=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" -- Bob Bishop rb@gid.co.uk From owner-freebsd-current@freebsd.org Thu Dec 20 08:46:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 497C9133C792 for ; Thu, 20 Dec 2018 08:46:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D7B526DC1F for ; Thu, 20 Dec 2018 08:46:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 991C9133C78B; Thu, 20 Dec 2018 08:46:44 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87B82133C788 for ; Thu, 20 Dec 2018 08:46:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1FC6A6DC16 for ; Thu, 20 Dec 2018 08:46:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3A29349F3 for ; Thu, 20 Dec 2018 08:46:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id wBK8khe6087101 for ; Thu, 20 Dec 2018 08:46:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wBK8khRR087100 for current@FreeBSD.org; Thu, 20 Dec 2018 08:46:43 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed) Date: Thu, 20 Dec 2018 08:46:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa, patch, regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: mfc-stable12? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 20 Dec 2018 11:10:17 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 08:46:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227191 --- Comment #21 from commit-hook@freebsd.org --- A commit references this bug: Author: avg Date: Thu Dec 20 08:45:41 UTC 2018 New revision: 342278 URL: https://svnweb.freebsd.org/changeset/base/342278 Log: MFC r341632: acpi_{Device,Battery}IsPresent: restore pre-r330957 behaviour Specifically, assume that the device is present if evaluation of _STA method fails. PR: 227191 Changes: _U stable/12/ stable/12/sys/dev/acpica/acpi.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Thu Dec 20 08:48:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46444133C904 for ; Thu, 20 Dec 2018 08:48:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D38756DE63 for ; Thu, 20 Dec 2018 08:48:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 97D10133C8F9; Thu, 20 Dec 2018 08:48:05 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8677D133C8F6 for ; Thu, 20 Dec 2018 08:48:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 21E8C6DE56 for ; Thu, 20 Dec 2018 08:48:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2171B4A02 for ; Thu, 20 Dec 2018 08:48:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id wBK8m4gK088450 for ; Thu, 20 Dec 2018 08:48:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wBK8m3PR088449 for current@FreeBSD.org; Thu, 20 Dec 2018 08:48:03 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed) Date: Thu, 20 Dec 2018 08:48:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa, patch, regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: mfc-stable12? X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 20 Dec 2018 11:10:25 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 08:48:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227191 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Thu Dec 20 10:49:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 481681340A4D for ; Thu, 20 Dec 2018 10:49:54 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DAE2F72749 for ; Thu, 20 Dec 2018 10:49:45 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from bsdrookie.norma.com. (asterisk.enaza.ru [91.237.76.254] (may be forged)) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id wBKAncpb034031 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 20 Dec 2018 15:49:38 +0500 (+05) (envelope-from eugene@zhegan.in) Subject: Re: The future of ZFS in FreeBSD To: freebsd-current@freebsd.org References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> From: "Eugene M. Zheganin" Message-ID: <4481f3cb-4535-bed3-c09f-429553f8f88b@zhegan.in> Date: Thu, 20 Dec 2018 15:49:38 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Server: localhost X-Rspamd-Scan-Time: 0.49 X-Rspamd-Queue-Id: DAE2F72749 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of eugene@zhegan.in designates 2a00:7540:1::5 as permitted sender) smtp.mailfrom=eugene@zhegan.in X-Spamd-Result: default: False [-6.40 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.989,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.996,0]; DMARC_NA(0.00)[zhegan.in]; MX_GOOD(-0.01)[mail-backup.zhegan.in,mx.zhegan.in]; NEURAL_HAM_SHORT(-0.52)[-0.524,0]; IP_SCORE(-3.58)[ip: (-9.43), ipnet: 2a00:7540:1::/48(-4.71), asn: 57401(-3.77), country: RU(0.00)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:57401, ipnet:2a00:7540:1::/48, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Mailman-Approved-At: Thu, 20 Dec 2018 11:10:47 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 10:49:54 -0000 Hello, On 19.12.2018 23:32, Allan Jude wrote: > The biggest thing to remember is that this is still OpenZFS, and still > run by the same developers as it has been. We are just commonizing on > the repo that has the most features integrated into it. Does it mean that ZoF and thus FreeBSD will lose NFSv4 ACLs because there is no such thing in ZoL ? Eugene. From owner-freebsd-current@freebsd.org Thu Dec 20 11:57:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A957C13431C7 for ; Thu, 20 Dec 2018 11:57:56 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-ed1-x541.google.com (mail-ed1-x541.google.com [IPv6:2a00:1450:4864:20::541]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D652753A5 for ; Thu, 20 Dec 2018 11:57:55 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-ed1-x541.google.com with SMTP id o10so1463039edt.13 for ; Thu, 20 Dec 2018 03:57:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=q/IVkfXVjGSGbH41787peBsjZ0SwQ15XqaAT+t9Yxyk=; b=CDKdmYIleCmOl0Bw7gqat9RtOTmJN1p34fnU86dIpC4cd1c/QMzNj+faDWKoms98AM EwUif9SWBooEyuzH5ZAoQhyWnLYnXWDpD+lEnkAnD9/UyuKp9ngRKrO7XPVhILG3ZOXM FOpEgo+iQlKQvOeZjqAf87vIacEQoIbJOMVOAzeDq62PDAv3HYD0/IFY4kCOnzZQU7PS ssjnm//Pi2/xr9i/pp8r+ktrA0qP3RFLQ0uiK+EBxBHYCQqHhJOSBR5DsO5AgEYk/C8F 3Yhwt+BfsOSsHnCChCKxTsM1FojjhPNpiCasRI7c6MzG+0WYULaD6BSMJEcS6DnsxiX2 Lasg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=q/IVkfXVjGSGbH41787peBsjZ0SwQ15XqaAT+t9Yxyk=; b=kcHcOR0X4us4dIx29B9c+X0ES/wLdatbgy8YvIxEygSoqVOir5ewCyn7DFtjJapGXu 8LyHb4hF6pvcQKxKaqzaU+hQuDJQ59x4Adx1WM37/smQu/n/t36V63jfVCF930kdtjJj AeuQXKuiFXMSCySimBV8qFtl5irsJO1RFum7sY/G8JDYOPOH9sytKkav1GtcyfIZhiFc 4dBWhgytTw3uGRSicLfZiPmi9i9rWBu87OV1lH6tc/CmzfgTDJAtODV1ieyWAxtshCuT y05AKd8Ccsb4E+vRqwBHnEgo/AlMBhuoyxduQwWvdPzJtWZy/K8tfQwBUBB0uWuNGu/Z DV6A== X-Gm-Message-State: AA+aEWZKJoemsS1QFLi/34u2Re8NH+B71ncexiC8PEFXqFkKUsV1uktA tVCIe1Kd/hTSbEDG8zdvk/405Q== X-Google-Smtp-Source: AFSGD/XJEKnHDAwbrVuDFaUHxuDtptT/+HjSRsGJIgzXvcBPLoL8SsMEIWsZ1ktbqy6QcfrMDDSWcQ== X-Received: by 2002:a17:906:55a:: with SMTP id k26-v6mr19490110eja.218.1545307074354; Thu, 20 Dec 2018 03:57:54 -0800 (PST) Received: from [10.44.128.75] ([161.12.40.153]) by smtp.gmail.com with ESMTPSA id e35sm6191762eda.13.2018.12.20.03.57.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Dec 2018 03:57:53 -0800 (PST) Subject: Re: The future of ZFS in FreeBSD To: Bob Bishop , Matthew Macy Cc: freebsd-current , freebsd-fs References: From: Steven Hartland Message-ID: Date: Thu, 20 Dec 2018 11:58:03 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 7D652753A5 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=multiplay-co-uk.20150623.gappssmtp.com header.s=20150623 header.b=CDKdmYIl; spf=pass (mx1.freebsd.org: domain of killing@multiplay.co.uk designates 2a00:1450:4864:20::541 as permitted sender) smtp.mailfrom=killing@multiplay.co.uk X-Spamd-Result: default: False [-4.06 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[multiplay-co-uk.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[multiplay.co.uk]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[multiplay-co-uk.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ASPMX.L.GOOGLE.COM]; RCVD_IN_DNSWL_NONE(0.00)[1.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.98)[-0.975,0]; IP_SCORE(-0.58)[ip: (0.23), ipnet: 2a00:1450::/32(-1.61), asn: 15169(-1.41), country: US(-0.08)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 11:57:56 -0000 On 20/12/2018 11:03, Bob Bishop wrote: > Hi, > >> On 19 Dec 2018, at 23:16, Matthew Macy wrote: >> >> On Wed, Dec 19, 2018 at 15:11 Steven Hartland >> wrote: >> >>> Sorry been off for a few weeks so must have missed that, please do prod me >>> on again if you don’t see any response to anything not just this. Like many >>> others I get so may emails across so many lists it’s more than likely I >>> just missed it. >>> >>> That said would you say that with the right support we can make progress >>> on the this prior to the port? I have to ask as the alternative version has >>> been on the cusp for many years now so it’s feels more like a distant >>> memory than something that may happen, no disrespect to anyone involved, as >>> I know all too well how hard it can be to get something like this over the >>> line, especially when people have competing priorities. >>> >> I am hoping that it's sufficiently important to FreeBSD ZFS developers that >> they'll give the PR the attention it needs so that it can be merged before >> summer. My understanding is that it's mostly suffered from neglect. TRIM is >> most important to FreeBSD and it already had its own implementation. >> >> https://github.com/zfsonlinux/zfs/pull/5925 > Please correct me if I’m wrong but this looks a lot less mature than FreeBSD’s existing TRIM support for ZFS which we’ve had in production for six years. > > What is the rationale here? I’m concerned that it looks like an opportunity for mighty regressions. > This is the case, but overall this solution is thought to be a better approach. With anything like this there is always a risk, so we all need a concerted effort to get to one solution.     Regards     Steve From owner-freebsd-current@freebsd.org Thu Dec 20 13:04:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B52513466D4; Thu, 20 Dec 2018 13:04:58 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) (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 A0DC577E65; Thu, 20 Dec 2018 13:04:47 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from [194.32.164.27] ([194.32.164.27]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id wBKD4jLj093718; Thu, 20 Dec 2018 13:04:45 GMT (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: The future of ZFS in FreeBSD From: rb@gid.co.uk In-Reply-To: Date: Thu, 20 Dec 2018 13:04:45 +0000 Cc: Matthew Macy , freebsd-current , freebsd-fs Content-Transfer-Encoding: quoted-printable Message-Id: <2A394CBF-7739-4F64-B559-BBF513EC141B@gid.co.uk> References: To: Steven Hartland X-Mailer: Apple Mail (2.3273) X-Rspamd-Queue-Id: A0DC577E65 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of rb@gid.co.uk designates 194.32.164.250 as permitted sender) smtp.mailfrom=rb@gid.co.uk X-Spamd-Result: default: False [0.56 / 15.00]; ARC_NA(0.00)[]; MX_INVALID(0.50)[greylisted]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[gid.co.uk]; NEURAL_SPAM_MEDIUM(0.07)[0.073,0]; NEURAL_SPAM_SHORT(0.17)[0.174,0]; NEURAL_HAM_LONG(-0.07)[-0.072,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; FROM_NO_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[250.164.32.194.list.dnswl.org : 127.0.10.0]; IP_SCORE(-0.31)[asn: 42831(-1.48), country: GB(-0.10)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42831, ipnet:194.32.164.0/24, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 13:04:58 -0000 > On 20 Dec 2018, at 11:58, Steven Hartland = wrote: >=20 >=20 >=20 > On 20/12/2018 11:03, Bob Bishop wrote: >> Hi, >>=20 >>> On 19 Dec 2018, at 23:16, Matthew Macy wrote: >>>=20 >>> On Wed, Dec 19, 2018 at 15:11 Steven Hartland = >>> wrote: >>>=20 >>>> Sorry been off for a few weeks so must have missed that, please do = prod me >>>> on again if you don=E2=80=99t see any response to anything not just = this. Like many >>>> others I get so may emails across so many lists it=E2=80=99s more = than likely I >>>> just missed it. >>>>=20 >>>> That said would you say that with the right support we can make = progress >>>> on the this prior to the port? I have to ask as the alternative = version has >>>> been on the cusp for many years now so it=E2=80=99s feels more like = a distant >>>> memory than something that may happen, no disrespect to anyone = involved, as >>>> I know all too well how hard it can be to get something like this = over the >>>> line, especially when people have competing priorities. >>>>=20 >>> I am hoping that it's sufficiently important to FreeBSD ZFS = developers that >>> they'll give the PR the attention it needs so that it can be merged = before >>> summer. My understanding is that it's mostly suffered from neglect. = TRIM is >>> most important to FreeBSD and it already had its own implementation. >>>=20 >>> https://github.com/zfsonlinux/zfs/pull/5925 >> Please correct me if I=E2=80=99m wrong but this looks a lot less = mature than FreeBSD=E2=80=99s existing TRIM support for ZFS which = we=E2=80=99ve had in production for six years. >>=20 >> What is the rationale here? I=E2=80=99m concerned that it looks like = an opportunity for mighty regressions. >>=20 > This is the case, but overall this solution is thought to be a better = approach. >=20 > With anything like this there is always a risk, so we all need a = concerted effort to get to one solution. Not sure what I can contribute, but I can certainly put a box up for = testing when there=E2=80=99s something to test. > Regards > Steve >=20 -- Bob Bishop rb@gid.co.uk From owner-freebsd-current@freebsd.org Thu Dec 20 13:12:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24D8D1346B68 for ; Thu, 20 Dec 2018 13:12:52 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7813980744 for ; Thu, 20 Dec 2018 13:12:50 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.183.168.129]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LsCAp-1hXby117SJ-013uLX for ; Thu, 20 Dec 2018 14:12:42 +0100 Date: Thu, 20 Dec 2018 14:12:02 +0100 From: "O. Hartmann" To: FreeBSD CURRENT Subject: bind 9.12.3-P1 dies after change of IP on outbound interface Message-ID: <20181220140433.451d23c5@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:rJfelYIMDZniY5KuX/RWoKVi01cbt9SUxgYTkWAgIMnYRLdYxz6 vywHF8QmZ3Ellgjyym1wwZ6aB5xPzrcR/2cNJCESUSTun+FICTOlBdEEttxrnIoDugjZKBq htku0UXt7Gm1hjh5hzJglSheQW84wZeBuPZArrGPpdSAaFscPL2Uze697T6BjDINuSDtdKB pIJOk1SAL1kXQtgHSeaAg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:r7kxSqEgTWM=:1KIwZkUUH0qxAwUof+gHgc G9dKLb00m1aGOTDhm4d6pIJzzG040UvpI0Hwx+rDS9lSqBbLtcT/Uc02FjTjwC7v0l979MBTc qn3+NXrEwWnU2OSceC8RbxJJIbMmkeWKiue0s7n24JuYCJGhXyO4nBkB4A9a9CjBbWmC37lzo jTi31ZL93pkoWURcnNGC62tIBg268cCOaaEBESg2Gmk3O3IHS6DjsVBCl9imhMzPF/RNE1+mc i4SCjPVP0e6c7oR4fILgfmkQnI4p/T2sK7Gq4o2OhLIQLnTp0KO2ADbkOlqp59KIOMKJh8hti WtYaNsMdb1ZfDWWPhV2RmDROXMYIzXy+GZ2f7oMIwkN0u0Z4WvMbAjwsN/VdXjmEPaEUPlqvk A6V5PqPuakk1Y+U4VlKDSL7JsmjWgdlnmvQmr1ZBgozn1HN+vht1aylXN6S1ei58IlkS4nYwt Vj0WVVQP2NoZ4w9AOSiKbhtiGvMPtcl2TimtmskE0EWABBICu09ukMZX9z+sweXBRcVU7yqN7 HBUjfgutcYnnP9u++MCu54mxAumCZV+BtTv2RYytf7VkKnYmS47y/0YQlPJFWS2ErwvhnnBBO A3oQkNi6FyPvnZNOeFh1bmhKoBN1XHRReK/jQoV2ktpHX6OEfhn3rVOn0p5P7kqvU0x+S2ao2 /e1nGha0Vcp+2MMFIC1Wnu0LFGDZ4dtkA9i4tGsBwDvX9rSTVHMsRAlY3EWrvDawlrLbVNrRJ gg3iJi0kmI0RI98oGKwihrogMnsyo9OQvt89PJ+naLhLbSFH+WMnT3ZF1Pb7MHFxnHcn64UAc 2ZfEQad8aZ4pmmuInzZFFvSHxwB4O7GoB0pCXfMYklC6iX/OwPW4tr6qVzQdrXZJowxoq5gRw /8Xi12r0dcBZMXh002uSTUFxAuV4DBA4Buul3ru/Id/E5tNdf1fDqPRiYEm7d6SdVNiuNX87N gDGQeyyUZtQ== X-Rspamd-Queue-Id: 7813980744 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-1.02 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[mx00.gmx.net,mx01.gmx.net]; MIME_BASE64_TEXT(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[18.15.227.212.list.dnswl.org : 127.0.3.1]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[129.168.183.77.zen.spamhaus.org : 127.0.0.10]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.968,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.93)[-0.930,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[walstatt.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.57)[ip: (-3.06), ipnet: 212.227.0.0/16(-0.30), asn: 8560(0.53), country: DE(-0.01)]; NEURAL_SPAM_SHORT(0.55)[0.552,0]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 13:12:52 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMjU2DQoNCkxhdGVs ZXkgSSByZWFsaXNlIHNvbWUgc3RyYW5nZSBiZWhhdmlvdXIgb2YgdGhlIHJlY2VudCBkbnMvYmlu ZDkxMiBwb3J0Lg0KDQpSdW5uaW5nIG5hbWVkICg5LjEyLjMtUDEpIG9uIGEgMTItU1RBQkxFIGdh dGV3YXkvcm91dGVyL2ZpcmV3YWxsIHdpdGggb3V0Ym91bmQgaW50ZXJmYWNlDQp0dW4wIHRvIG91 ciBwcml2aWRlciwgbmFtZWQgc2VlbXMgdG8gY3Jhc2ggc2luY2UgdGhlIGxhc3QgcG9ydCB1cGdy YWRlIHdoZW52ZXIgdGhlIElTUCBpcw0KY2hhbmdpbmcgdGhlIElQICh1c2luZyBwcHAgd2l0aCBz b21lIGxpbmt1cC9saW5rZG93biBzY3JpcHRzIGR1ZSB0byBJUHY2LCBub3RoaW5nIGZhbmN5KS4N Cg0KVGhlIGxhc3Qgc2lnbiBvZiBsaXZlIG5hbWVkIHByb3ZpZGVzIGlzIHNob3duIGJlbG93Og0K DQpbLi4uXQ0KRGVjIDIwIDEzOjIyOjQ2IDwzLjI+IGdhdGUgbmFtZWRbMTEyMF06IHNvY2tldC5j OjMyNTE6IFJFUVVJUkUoc29jay0+cmVmZXJlbmNlcyA9PSAxKQ0KZmFpbGVkLCBiYWNrIHRyYWNl IERlYyAyMCAxMzoyMjo0NiA8My4yPiBnYXRlIG5hbWVkWzExMjBdOiAjMCAweDJjODg4MCBpbiA/ Pw0KRGVjIDIwIDEzOjIyOjQ2IDwzLjI+IGdhdGUgbmFtZWRbMTEyMF06ICMxIDB4NGIxMTFhIGlu ID8/DQpEZWMgMjAgMTM6MjI6NDYgPDMuMj4gZ2F0ZSBuYW1lZFsxMTIwXTogIzIgMHg0ZTM1ZmMg aW4gPz8NCkRlYyAyMCAxMzoyMjo0NiA8My4yPiBnYXRlIG5hbWVkWzExMjBdOiAjMyAweDRlOWU3 OSBpbiA/Pw0KRGVjIDIwIDEzOjIyOjQ2IDwzLjI+IGdhdGUgbmFtZWRbMTEyMF06ICM0IDB4MzU1 NTRkIGluID8/DQpEZWMgMjAgMTM6MjI6NDYgPDMuMj4gZ2F0ZSBuYW1lZFsxMTIwXTogIzUgMHgz NTRhMmYgaW4gPz8NCkRlYyAyMCAxMzoyMjo0NiA8My4yPiBnYXRlIG5hbWVkWzExMjBdOiAjNiAw eDRkNDlmYSBpbiA/Pw0KRGVjIDIwIDEzOjIyOjQ2IDwzLjI+IGdhdGUgbmFtZWRbMTEyMF06ICM3 IDB4ODAwZGMzN2M2IGluID8/DQpEZWMgMjAgMTM6MjI6NDYgPDMuMj4gZ2F0ZSBuYW1lZFsxMTIw XTogZXhpdGluZyAoZHVlIHRvIGFzc2VydGlvbiBmYWlsdXJlKQ0KRGVjIDIwIDEzOjQ2OjU5IDwz LjU+IGdhdGUgbmFtZWRbMzE5NV06IHN0YXJ0aW5nIEJJTkQgOS4xMi4zLVAxIDxpZDpjZmRkMzVm Pg0KDQpQcmlvciB0byB0aGUgbGFzdCB1cGRhdGUgb2YgZG5zL2JpbmQ5MTIsIHRoaXMgcm91dGVy L2ZpcmV3YWxsIGFwcGxpYW5jZSB3YXMgcnVubmluZyBtb3JlDQp0aGFuIGEgbW9udGggd2l0aG91 dCBoYXZpbmcgc3VjaCB0cm91YmxlLCBldmVuIHRoZSBJU1AgaXMgcmFuZG9tbHkgY2hhbmdpbmcg dGhlIElQdjQvSVB2Ng0KYWRkcmVzc2VzIHNwcmVhZCBvdmVyIHRoZSBkYXkuDQoNCldoYXQgaXMg d3Jvbmc/DQoNCktpbmQgcmVnYXJkcywNCg0KTy4gSGFydG1hbm4NCg0KDQotIC0tIA0KTy4gSGFy dG1hbm4NCg0KSWNoIHdpZGVyc3ByZWNoZSBkZXIgTnV0enVuZyBvZGVyIMOcYmVybWl0dGx1bmcg bWVpbmVyIERhdGVuIGbDvHINCldlcmJlendlY2tlIG9kZXIgZsO8ciBkaWUgTWFya3QtIG9kZXIg TWVpbnVuZ3Nmb3JzY2h1bmcgKMKnIDI4IEFicy4gNCBCRFNHKS4NCi0tLS0tQkVHSU4gUEdQIFNJ R05BVFVSRS0tLS0tDQoNCmlIVUVBUllJQUIwV0lRU3k4SUJ4QVBEa3FWQmFUSjQ0TjFaWlBiYTVS d1VDWEJ1VlBnQUtDUkE0TjFaWlBiYTUNClJ4QjhBUUR3WG03aFZpZmhEUDg0MWFHY2tYTENDaW5v OTVsU0F0SE5Mb096Mm5CY293RDlGNGxVeWZsQi9JbXENCk92RVJ1U05LZWl4YUREYXpLajZLSmZO dGlFOC8wZ1U9DQo9SDZyMg0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQo= From owner-freebsd-current@freebsd.org Thu Dec 20 14:37:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B2AE1348FBB for ; Thu, 20 Dec 2018 14:37:42 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 10765834D2; Thu, 20 Dec 2018 14:37:42 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id CE0BEBA38; Thu, 20 Dec 2018 14:37:41 +0000 (UTC) Date: Thu, 20 Dec 2018 14:37:41 +0000 From: Alexey Dokuchaev To: "Eugene M. Zheganin" Cc: freebsd-current@freebsd.org Subject: Re: The future of ZFS in FreeBSD Message-ID: <20181220143741.GA40569@FreeBSD.org> References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> <4481f3cb-4535-bed3-c09f-429553f8f88b@zhegan.in> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4481f3cb-4535-bed3-c09f-429553f8f88b@zhegan.in> User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 10765834D2 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.86 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; NEURAL_HAM_SHORT(-0.87)[-0.869,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]; NEURAL_HAM_LONG(-0.99)[-0.993,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 14:37:42 -0000 On Thu, Dec 20, 2018 at 03:49:38PM +0500, Eugene M. Zheganin wrote: > On 19.12.2018 23:32, Allan Jude wrote: > > The biggest thing to remember is that this is still OpenZFS, and still > > run by the same developers as it has been. We are just commonizing on > > the repo that has the most features integrated into it. > > Does it mean that ZoF and thus FreeBSD will lose NFSv4 ACLs because > there is no such thing in ZoL? +1. I'm also worried if this would bring more Linuxish bits into our kernel (cf. LinuxKPI). Also, I thought that ZFS was never really native to Linux but implemented through SPL (Solaris Porting Layer), and Linux' VFS is not ARC-aware unlike Solaris and FreeBSD. It would be quite upsetting to see ZFS as we know it in FreeBSD become pessimized because of those things. :-( ./danfe From owner-freebsd-current@freebsd.org Thu Dec 20 14:39:46 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B00E134914B for ; Thu, 20 Dec 2018 14:39:46 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 96A6383664 for ; Thu, 20 Dec 2018 14:39:45 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id ZzU7gUYra82YcZzU9ghHeA; Thu, 20 Dec 2018 07:39:43 -0700 X-Authority-Analysis: v=2.3 cv=NNSrBHyg c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=2ur7OfE09M0A:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=txGzlZnE3aLDzfR-6lEA:9 a=oAt05iW_-okG4RBV:21 a=Cv7cBpeUSF0v7Pkz:21 a=CjuIK1q_8ugA:10 a=zRTLgjrOLjvyahApcuIA:9 a=Ps5RpZy1YY3MRcQz:21 a=VlyLWuwqHLrscYjW:21 a=NUutSRSvanKpjmmb:21 a=_W_S_7VecoQA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from [25.81.116.22] (unknown [72.143.224.194]) by spqr.komquats.com (Postfix) with ESMTPSA id B86241508; Thu, 20 Dec 2018 06:39:34 -0800 (PST) MIME-Version: 1.0 From: Cy Schubert Subject: RE: The future of ZFS in FreeBSD Date: Thu, 20 Dec 2018 06:39:37 -0800 To: "Eugene M. Zheganin" , "freebsd-current@freebsd.org" Message-Id: <20181220143934.B86241508@spqr.komquats.com> X-CMAE-Envelope: MS4wfOSxwdNKxdrdkG+S96wEO8ARp5hQFRs3q46p7/p9jVDWCvs+oytfVnXasEcLcfjgSXtRtR5O3GA1EHCed7WcyefZHnX5opEiHtL6waHfYC+g6EN7DVQL K5JqT4lQoZU8durATJ6uIjRYzlKxId12eGHFcVNDXmr2HQYnBOPPoS2pRIcLRdkboZ+M3LMoOUAYASL+ts2c6rXyoHmcxETGVz5E48L/zHTtHxmxxKcf8lel X-Rspamd-Queue-Id: 96A6383664 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.95 / 15.00]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-1.74)[ip: (-3.98), ipnet: 64.59.128.0/20(-2.58), asn: 6327(-2.07), country: CA(-0.09)]; RCVD_VIA_SMTP_AUTH(0.00)[]; URI_COUNT_ODD(1.00)[1]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.99)[-0.993,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[139.136.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; RCVD_TLS_LAST(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 14:39:46 -0000 We would port the feature ourselves and push the code upstream. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -----Original Message----- From: Eugene M. Zheganin Sent: 20/12/2018 03:12 To: freebsd-current@freebsd.org Subject: Re: The future of ZFS in FreeBSD Hello, On 19.12.2018 23:32, Allan Jude wrote: > The biggest thing to remember is that this is still OpenZFS, and still > run by the same developers as it has been. We are just commonizing on > the repo that has the most features integrated into it. Does it mean that ZoF and thus FreeBSD will lose NFSv4 ACLs because=20 there is no such thing in ZoL ? Eugene. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu Dec 20 16:15:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BC98134BDC3 for ; Thu, 20 Dec 2018 16:15:10 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 231F587255; Thu, 20 Dec 2018 16:15:08 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id a0yRgV1H882Yca0ySghfNY; Thu, 20 Dec 2018 09:15:02 -0700 X-Authority-Analysis: v=2.3 cv=NNSrBHyg c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=2ur7OfE09M0A:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=p4XUK5SDVfPnt27tRYcA:9 a=FSGolYVeKPdIFara:21 a=h9UTF4u5UCuVk_Hc:21 a=CjuIK1q_8ugA:10 a=wvNN6SPy67tmOg9sxBAA:9 a=weGfD7nXmgxa--RW:21 a=JR-hFisgLNLeIg_q:21 a=hA-yDGspqyyArEbn:21 a=_W_S_7VecoQA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from [25.81.116.22] (S0106788a207e2972.gv.shawcable.net [70.66.154.233]) by spqr.komquats.com (Postfix) with ESMTPSA id 84CC2177E; Thu, 20 Dec 2018 08:14:58 -0800 (PST) MIME-Version: 1.0 From: Cy Schubert Subject: RE: The future of ZFS in FreeBSD Date: Thu, 20 Dec 2018 08:15:01 -0800 To: Alexey Dokuchaev , "Eugene M. Zheganin" CC: "freebsd-current@freebsd.org" Message-Id: <20181220161458.84CC2177E@spqr.komquats.com> X-CMAE-Envelope: MS4wfJr2T2NCLp2Wj7KeRSA3gGQe/J53C2nLBUyQQGnoWrCg/uwiHVwY+E1Q1V3BkmJOQbA6lhzqI8bMDDXHP1BOPsSs+l07OrCCDT74o+9ACFLUXSEMAYXM LV7eLHjopdJffJFj886s6ZNKs1IivJJqkn85poz0nSPlR43QtxWHYckr7kCx44Wn1g1YXG3d60LJDZNB9/PBpyHxy4HJhtCLRiCY2slWs3ESYE2aQu/VZfCg DEATRcT0SQ/sKQLj3jd5mQ== X-Rspamd-Queue-Id: 231F587255 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.83 / 15.00]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-1.70)[ip: (-3.81), ipnet: 64.59.128.0/20(-2.57), asn: 6327(-2.05), country: CA(-0.09)]; TO_DN_EQ_ADDR_SOME(0.00)[]; URI_COUNT_ODD(1.00)[1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.92)[-0.918,0]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[139.136.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; RCVD_TLS_LAST(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 16:15:10 -0000 I suspect the idea is to contribute the FreeBSD bits back to ZoL. My question is, how much of a base does ZoL really have? The enterprise pla= yers with any significant market share won't touch it -- Ubuntu has but IMO= they're a niche player (who has violated GPL by including CDDL in their ke= rnel. The next step should be throwing up a wiki page with a features todo list. = Also, this is a large enough project to have its own project branch, with t= he goal of having it in head before 13 goes GA. I also think people will no= t accept regressions or other POLA violations. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -----Original Message----- From: Alexey Dokuchaev Sent: 20/12/2018 06:40 To: Eugene M. Zheganin Cc: freebsd-current@freebsd.org Subject: Re: The future of ZFS in FreeBSD On Thu, Dec 20, 2018 at 03:49:38PM +0500, Eugene M. Zheganin wrote: > On 19.12.2018 23:32, Allan Jude wrote: > > The biggest thing to remember is that this is still OpenZFS, and still > > run by the same developers as it has been. We are just commonizing on > > the repo that has the most features integrated into it. >=20 > Does it mean that ZoF and thus FreeBSD will lose NFSv4 ACLs because > there is no such thing in ZoL? +1. I'm also worried if this would bring more Linuxish bits into our kernel (cf. LinuxKPI). Also, I thought that ZFS was never really native to Linux but implemented through SPL (Solaris Porting Layer), and Linux' VFS is not ARC-aware unlike Solaris and FreeBSD. It would be quite upsetting to see ZFS as we know it in FreeBSD become pessimized because of those things. :-( ./danfe _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu Dec 20 17:06:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C3CB134D31F for ; Thu, 20 Dec 2018 17:06:04 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EC77289128 for ; Thu, 20 Dec 2018 17:06:03 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: by mailman.ysv.freebsd.org (Postfix) id A9CFF134D31A; Thu, 20 Dec 2018 17:06:03 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85888134D319 for ; Thu, 20 Dec 2018 17:06:03 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 45C718911D for ; Thu, 20 Dec 2018 17:05:58 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from [84.237.50.47] (helo=regency.nsu.ru) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1ga1lb-0004A0-Nz for current@freebsd.org; Fri, 21 Dec 2018 00:05:47 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id wBKHZeFh099806 for ; Thu, 20 Dec 2018 23:35:41 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id wBKHZZje099796 for current@freebsd.org; Fri, 21 Dec 2018 00:35:35 +0700 (+07) (envelope-from danfe) Date: Fri, 21 Dec 2018 00:35:35 +0700 From: Alexey Dokuchaev To: current@freebsd.org Subject: AESNI, /dev/crypto, and new OpenSSL Message-ID: <20181220173535.GA2505@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 3 X-KLMS-Message-Action: skipped X-KLMS-AntiSpam-Status: not scanned, whitelist X-KLMS-AntiPhishing: not scanned, whitelist X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, whitelist X-Rspamd-Queue-Id: 45C718911D X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of danfe@regency.nsu.ru designates 84.237.50.39 as permitted sender) smtp.mailfrom=danfe@regency.nsu.ru X-Spamd-Result: default: False [-0.40 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.22)[-0.223,0]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a:mx.nsu.ru]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.39)[-0.389,0]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MX_GOOD(-0.01)[mx.nsu.ru]; NEURAL_HAM_SHORT(-0.28)[-0.280,0]; DMARC_NA(0.00)[nsu.ru]; IP_SCORE(0.00)[country: RU(0.00)]; FORGED_SENDER(0.30)[danfe@nsu.ru,danfe@regency.nsu.ru]; RWL_MAILSPIKE_POSSIBLE(0.00)[39.50.237.84.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:3335, ipnet:84.237.48.0/21, country:RU]; FROM_NEQ_ENVFROM(0.00)[danfe@nsu.ru,danfe@regency.nsu.ru] X-Mailman-Approved-At: Thu, 20 Dec 2018 17:20:14 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 17:06:04 -0000 Hi there, For many years, OpenSSL was quite vocal about which hw-accelerated algos it can use: $ uname -UK 1200058 1200058 $ openssl version OpenSSL 1.0.2n-freebsd 7 Dec 2017 $ openssl engine -c -t (cryptodev) BSD cryptodev engine [RSA, DSA, DH] <<< word count = 3 [ available ] (dynamic) Dynamic engine loading support [ unavailable ] # kldload aesni <<< loading AESNI(4) $ openssl engine -c -t (cryptodev) BSD cryptodev engine [RSA, DSA, DH, AES-128-CBC, AES-192-CBC, AES-256-CBC] <<< word count = 6 [ available ] (dynamic) Dynamic engine loading support [ unavailable ] Since recently[*], OpenSSL had switched to some new engine. Now, the output is less verbose and seemingly unaffected by the presence of the aesni.ko module (or lack thereof): $ uname -UK 1300005 1300005 $ openssl version OpenSSL 1.1.1a-freebsd 20 Nov 2018 $ openssl engine -c -t (devcrypto) /dev/crypto engine [ available ] <<< which ones??? (dynamic) Dynamic engine loading support [ unavailable ] This does not look right. Also, now the popular "openssl speed -elapsed" benchmark apparently does not use kernel AESNI support even when it is loaded, because `system' CPU load is nearly zero (previously, in presence of aesni.ko, user load would drop to zero while system load would show that it's the kernel who's doing the job). Had something got broken here, or I'm misunderstanding how this machinery now works? ./danfe [*] http://freshbsd.org/commit/freebsd/src/342009 From owner-freebsd-current@freebsd.org Thu Dec 20 17:25:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B128E134DC30 for ; Thu, 20 Dec 2018 17:25:16 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from btw.pki2.com (static-50-125-237-106.rdmd.wa.frontiernet.net [50.125.237.106]) (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 A170189E5D; Thu, 20 Dec 2018 17:25:14 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from localhost (localhost [127.0.0.1]) by btw.pki2.com (8.15.2/8.15.2) with ESMTP id wBKHOt54013158; Thu, 20 Dec 2018 09:24:55 -0800 (PST) (envelope-from freebsd@pki2.com) Message-ID: <439ad3d4e40f0f9ec92c07126167913b9608ba62.camel@pki2.com> Subject: Re: The future of ZFS in FreeBSD From: Dennis Glatting To: Cy Schubert , Alexey Dokuchaev , "Eugene M. Zheganin" Cc: "freebsd-current@freebsd.org" Date: Thu, 20 Dec 2018 09:24:55 -0800 In-Reply-To: <20181220161458.84CC2177E@spqr.komquats.com> References: <20181220161458.84CC2177E@spqr.komquats.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner-ID: wBKHOt54013158 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: freebsd@pki2.com X-Spam-Status: No X-Rspamd-Queue-Id: A170189E5D X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dmarc=fail reason="" header.from=pki2.com (policy=none) X-Spamd-Result: default: False [1.46 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[pki2.com : No valid SPF, No valid DKIM,none]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MV_CASE(0.50)[]; NEURAL_SPAM_SHORT(0.13)[0.132,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(0.21)[0.210,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[btw.pki2.com]; NEURAL_SPAM_LONG(0.65)[0.654,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:5650, ipnet:50.120.0.0/13, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.02)[asn: 5650(-0.02), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 17:25:16 -0000 On Thu, 2018-12-20 at 08:15 -0800, Cy Schubert wrote: > I also think people will not accept regressions or other POLA > violations. +1 From owner-freebsd-current@freebsd.org Thu Dec 20 17:33:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59617134DFC8 for ; Thu, 20 Dec 2018 17:33:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 618638A53C for ; Thu, 20 Dec 2018 17:33:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x734.google.com with SMTP id r71so1455596qkr.10 for ; Thu, 20 Dec 2018 09:33:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fdLQinfKSdDl0dO1eawoSHXN+APGk5nRCkgu6oZ/3Lw=; b=GJYPs4+E3uZoMJ3KToT4vAfSAukXNV/7UUnpPceZ65XYWqYYn645cTFe6ZfnXoEROS ikL86MJlgDh/UmwDmJqItZEVG7C+uPDjQTKQFORGZgfpXCAoi1J0+49/fwDZfcGLDNE1 Mw9Ji/rTILeLLHL6/NLovcXKSOCquQ+JOxWl8CtPaBEtwuTZSJTKQY6H+gO0fS/pL47V 2bX0FvG5JlK5SSWRyHhN+LXZHcm/9BDxlrMQKSKNmK/JAMmLKPInX/DZvrlR6r1Wlspk PBxyfwjO+GmF66muH9DqFZhJjj7ZHdD0c4P1IDg0bc+/z3err+Y/eAT8LchASGyCARuO DYwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fdLQinfKSdDl0dO1eawoSHXN+APGk5nRCkgu6oZ/3Lw=; b=chTiQi7Up6jJZsxS9oY7dxIG4cuPR4JzmpCHfnk0dZC3YTGbNn5SuDjxhekb3QT6Wn fEoPYPsYGe0ltQ6orUqG+pDi843X8lM+bm6Si5G4SC7LZA3L/I9sLJG031OjcaVvNacY umdFYCMvxkhwFvG/N0ie5mZuEUdmzKKbw/2rrEhDnmTdJoncEZ/Pq/LZLgbV/DW2Luk5 Zti5wpksPBPjTsycaFBvLElLoKUr8O18UsbI/wnQTH+inKdZtIaf+Zdd3qfProQmMaqm UlFM0wj5Gbl1CAgfzS8qgPw6gm1ZhhVx48vND2677PNhOBruNV72V4wq0qaBL2lIhwwg 22kg== X-Gm-Message-State: AA+aEWYpeOVawo/lSAakFV26SQN4tZe6G9n19sOIv+bnPkCymHyULvHH 2z9zAkyt146I9lzRGx3g5U+H4JRzs9/DWYGdPOKjXQ== X-Google-Smtp-Source: AFSGD/W4U/MVTuvRUh6HwJWMwJ3gk455a6nC1OzIGJetLH1qPhDG4KNiILTouM3HqiWBsxQnKSZp9H4+WLOxuMnnSrk= X-Received: by 2002:a37:6e86:: with SMTP id j128mr26410675qkc.46.1545327183717; Thu, 20 Dec 2018 09:33:03 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Thu, 20 Dec 2018 10:32:52 -0700 Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Matthew Macy Cc: freebsd-fs , freebsd-current X-Rspamd-Queue-Id: 618638A53C X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=GJYPs4+E X-Spamd-Result: default: False [-5.38 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[4.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.95)[-0.947,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; IP_SCORE(-2.42)[ip: (-8.81), ipnet: 2607:f8b0::/32(-1.78), asn: 15169(-1.41), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 17:33:05 -0000 Matt, This is a fairly comprehensive plan. Kudos for putting it together. The big question here is do you have a complete list of FreeBSD-specific changes that will be lost in the cut-over? We've heard about TRIM support and maybe NFSv4, but are there others that can be identified? Once you have that list, it wouldn't be hard to throw the initial email with some tweaks from the replies into a FCP so everybody knows the plan, and we have it ratified in case people come along later and 'forget'. Warner From owner-freebsd-current@freebsd.org Thu Dec 20 17:33:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72ADA134E001 for ; Thu, 20 Dec 2018 17:33:29 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 17F328A5B3 for ; Thu, 20 Dec 2018 17:33:27 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 103EC30950 for ; Thu, 20 Dec 2018 10:34:14 -0700 (MST) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2l5_DXuT5H5f for ; Thu, 20 Dec 2018 10:34:13 -0700 (MST) Received: from photon.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA for ; Thu, 20 Dec 2018 10:34:13 -0700 (MST) From: Rebecca Cran To: "freebsd-current@FreeBSD.org" Subject: Panic in getblkx() booting from disc1.iso in Qemu VM Date: Thu, 20 Dec 2018 10:33:20 -0700 Message-ID: <4628942.YNO7O01DYZ@photon.int.bluestop.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 17F328A5B3 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.49 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(-3.10)[ip: (-9.79), ipnet: 96.64.0.0/11(-4.79), asn: 7922(-0.85), country: US(-0.08)]; DKIM_TRACE(0.00)[bluestop.org:+]; DMARC_POLICY_ALLOW(-0.50)[bluestop.org,quarantine]; MX_GOOD(-0.01)[mail.bluestop.org]; TO_DN_EQ_ADDR_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.88)[-0.881,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; CTE_CASE(0.50)[]; ASN(0.00)[asn:7922, ipnet:96.64.0.0/11, country:US]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 17:33:29 -0000 I know booting from the cd/dvd iso worked fairly recently, but today booting a new build of -CURRENT in a Qemu VM resulted in a panic: FreeBSD 13.0-CURRENT 19a6ceb89db(HEAD) GENERIC amd64 FreeBSD clang version 7.0.1 (tags/RELEASE_701/final 349250) (based on LLVM 7.0.1) WARNING: WITNESS option enabled, expect reduced performance. VT(efifb): resolution 800x600 CPU: QEMU Virtual CPU version 2.5+ (2994.86-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x663 Family=0x6 Model=0x6 Stepping=3 Features=0x783fbfd Features2=0x80002001 AMD Features=0x20100800 AMD Features2=0x5 SVM: NAsids=16 Hypervisor: Origin = "TCGTCGTCGTCG" real memory = 8589934592 (8192 MB) avail memory = 8227643392 (7846 MB) ... WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from cd9660:/dev/iso9660/13_0_CURRENT_AMD64_DVD [ro]... panic: bsize == 0, check bo->bo_bsize cpuid = 0 time = 2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0041189270 vpanic() at vpanic+0x1b4/frame 0xfffffe00411892d0 panic() at panic+0x43/frame 0xfffffe0041189330 getblkx() at getblkx+0x807/frame 0xfffffe00411893f0 breadn_flags() at breadn_flags+0x3d/frame 0xfffffe0041189460 cd9660_blkatoff() at cd9660_blkatoff+0x53/frame 0xfffffe00411894d0 cd9660_vget_internal() at cd9660_vget_internal+0x26b/frame 0xfffffe0041189550 vfs_domount() at vfs_domount+0x7d3/frame 0xfffffe0041189770 vfs_donmount() at vfs_donmount+0x7b9/frame 0xfffffe0041189810 kernel_mount() at kernel_mount+0x58/frame 0xfffffe0041189860 parse_mount() at parse_mount+0x469/frame 0xfffffe00411899a0 vfs_mountroot() at vfs_mountroot+0x67f/frame 0xfffffe0041189b10 start_init() at start_init+0x28/frame 0xfffffe0041189bb0 fork_exit() at fork_exit+0x84/frame 0xfffffe0041189bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0041189bf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter: panic [ thread pid 1 tid 100002 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> -- Rebecca From owner-freebsd-current@freebsd.org Thu Dec 20 17:33:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 478BC134E053 for ; Thu, 20 Dec 2018 17:33:56 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4416D8A678 for ; Thu, 20 Dec 2018 17:33:55 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 03DFC134E050; Thu, 20 Dec 2018 17:33:55 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2E7F134E04F for ; Thu, 20 Dec 2018 17:33:54 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F8E78A669 for ; Thu, 20 Dec 2018 17:33:54 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lj1-x235.google.com with SMTP id v1-v6so2319933ljd.0 for ; Thu, 20 Dec 2018 09:33:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EXaoagWVpqNvJ7eUNlE0Mxi7AcAXMNSKHzK/0TCLuPE=; b=uXoJOK6uEw/e7lvB4vbRHUvP9DUFKHQm81OPqXsgbWuLNqc/Goaq+adsD8l/Ke7Mrm 9wgZrPaBrNreVojS8BrNjQMx7Wz3ZBNkvwWVdEZFF80hhK6qpNJ1TNJHaYUPqpvgzLaH W1VPV+K92DUMeX1YPEHSPFHKDoVCFEQtNmIatNSwYXZf9/WueLzyn5ANZIgLk4u3/jrA f9m8hLU07nnnYnSiYXwYUsR/16uArxb0Gdhimjy3iTRNNBJ7xyoBTSGLpkmcmxXOoV8/ ybv0plfIANRlFpz8ngcNc61sulZ1p1LUTBW2FXqUmiDFMI6dI8bNS4TVzf8om9Ek11bE atxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EXaoagWVpqNvJ7eUNlE0Mxi7AcAXMNSKHzK/0TCLuPE=; b=frKt6NbIiMe6dm6CSko7lBl9cZNiHeCNugj2vZD0/xL8Fb8wA6YLNqS1klQ/TYFAyN TLhntWqQDRngC9W+DZQ5FMA82OtVkVd7Z3l59ZRPtCOdIlcPBxJ41m5hRF+WdW/QHp8/ Gev0qa54j3tGGIyuF3Ay/PBz8tZqIMf5llP50uh4++6RUIRn4VcZfKtic0FZ7+kiRqE2 19U/afMPW+jnlHi9wiEcd+YXSDEYBubDQyzb9x4PO3f7e7UVyEkyRybZ6crAHL/dVC6g SeY1Umvk5tDucHNQ1IHXLR66D7D6RAy9EGPcQtmHrzNdUkOZZolCydrI4m/3cuXO6irI Aa3g== X-Gm-Message-State: AA+aEWb/FTkSEZ9muTlY/2nATcJ82J6ybxDtBnMgCzDQYHHgnvu3/if3 9NaShmZrgMIKoyyFU8Oyj2DJtDGYyV76CKQ3mbxV12lc X-Google-Smtp-Source: AFSGD/W4AbQ70qUEYOttAqn/6Cn49tAMYVio8uJDz61cfy5SiQr3DUGiuKzxKuQPKcst64aMNwQvGHRMwq82hbBIZw4= X-Received: by 2002:a2e:914b:: with SMTP id q11-v6mr15391324ljg.164.1545327232655; Thu, 20 Dec 2018 09:33:52 -0800 (PST) MIME-Version: 1.0 References: <20181220173535.GA2505@regency.nsu.ru> In-Reply-To: <20181220173535.GA2505@regency.nsu.ru> From: Freddie Cash Date: Thu, 20 Dec 2018 09:33:41 -0800 Message-ID: Subject: Re: AESNI, /dev/crypto, and new OpenSSL To: Alexey Dokuchaev Cc: FreeBSD Current X-Rspamd-Queue-Id: 3F8E78A669 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.987,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 17:33:56 -0000 On Thu, Dec 20, 2018 at 9:21 AM Alexey Dokuchaev wrote: > Had something got broken here, or I'm misunderstanding how this machinery > now works? > Start reading here: https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090195.html That thread covers this issue. :) Along with the "fix" for it. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@freebsd.org Thu Dec 20 17:40:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00AE9134E464 for ; Thu, 20 Dec 2018 17:40:25 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7DDF58AB15 for ; Thu, 20 Dec 2018 17:40:24 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 4128E134E45E; Thu, 20 Dec 2018 17:40:24 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F9E5134E45D for ; Thu, 20 Dec 2018 17:40:24 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AD0B88AB11 for ; Thu, 20 Dec 2018 17:40:23 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from Debian-exim by mx.nsu.ru with local (Exim 4.72) (envelope-from ) id 1ga2J1-0000BX-9c for current@freebsd.org; Fri, 21 Dec 2018 00:40:19 +0700 Received: from [84.237.50.47] (helo=regency.nsu.ru) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1ga2J1-0000BK-8V; Fri, 21 Dec 2018 00:40:19 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id wBKIACWt003392; Fri, 21 Dec 2018 00:10:12 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id wBKIA7Si003368; Fri, 21 Dec 2018 01:10:07 +0700 (+07) (envelope-from danfe) Date: Fri, 21 Dec 2018 01:10:07 +0700 From: Alexey Dokuchaev To: Freddie Cash Cc: FreeBSD Current Subject: Re: AESNI, /dev/crypto, and new OpenSSL Message-ID: <20181220181007.GA2374@regency.nsu.ru> References: <20181220173535.GA2505@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 3 X-KLMS-Message-Action: skipped X-KLMS-AntiSpam-Status: not scanned, whitelist X-KLMS-AntiPhishing: not scanned, whitelist X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, whitelist X-Rspamd-Queue-Id: AD0B88AB11 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.991,0] X-Mailman-Approved-At: Thu, 20 Dec 2018 18:00:38 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 17:40:25 -0000 On Thu, Dec 20, 2018 at 09:33:41AM -0800, Freddie Cash wrote: > On Thu, Dec 20, 2018 at 9:21 AM Alexey Dokuchaev wrote: > > Had something got broken here, or I'm misunderstanding how this machinery > > now works? > > Start reading here: > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090195.html > > That thread covers this issue. :) Along with the "fix" for it. Thanks for the pointer. I've checked both -current and -hackers MLs prior to posting, but didn't expect this would show up on -stable first. :) ./danfe From owner-freebsd-current@freebsd.org Thu Dec 20 18:04:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FFBF134F14B for ; Thu, 20 Dec 2018 18:04:53 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-it1-x132.google.com (mail-it1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE2BC8C031; Thu, 20 Dec 2018 18:04:52 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-it1-x132.google.com with SMTP id a6so3025704itl.4; Thu, 20 Dec 2018 10:04:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=qEq3pU9Tr4VZ9aHDSlnTh49JqFiOtoLe0vG55DQogZw=; b=fz+iS35zzNpa1LZUGhy4hkFxY1g97KEOJQA7ofoaNlfXOhjotJK5ykPvfMJSgpu/2O Dk8MPasslP+eiDalfW872Ry5ji1VESWuQHIn+HS1WSWq74ZYaxoDOM3fywKZ28vlEWqv ykgxR6ZBDhzRMH9yMesTClGWyBysyrVHDb5V5eCXGzM+QcP5pPP3sjhrApsRrlV1Msh6 sGC6TBMpTRrawbfKH9eS9no1vw9cruoMA37R4xKuF5wZc+EwBX45IYcux/eQcrxgvw2Y N+m1ZLUXPGOw8woaU3DRyekSsg1fQwC7NSMVuXRqi7tvMYdwQYVpCmd6j2UDVybjoi9e LXnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=qEq3pU9Tr4VZ9aHDSlnTh49JqFiOtoLe0vG55DQogZw=; b=gguDj89UxrxRsOSqmcTUJjb7gvb9YFwwz2mfvvuaH4ZE6L3a2kFW163lMwuj5PbpzJ Tmc8A+K7PBXvq9P35GBvkccfcNhhSU6NpTLwtdsbSJfD5K4c8hbe86Q41WBOyGEA+oRD lReRafVHH6vylBNKc+CKGCLFrKkf6PgmFDWsK7VI/FH3L6gFUoCbgqQYssJIh0kQzvCw p8U7RX4zI3XQFdxTTUufazYZsFkaYWgmp9hwTUtxFIKpR3zBfHJ1GfDypC3NjaOenbKl sQ8vMdWsuwaJz5ZenVXCeVaD4aRuOq0UbaoHLw3tASIZihmR2tXdFmAJK3OvE46+izSl 2O3Q== X-Gm-Message-State: AA+aEWafoKkX9MBFP1fzWfc1vcCid5Im7sGifF0Malj02neajFRGTlJR vkhkx8QoUsy1Wo12+7NevnHhil5m X-Google-Smtp-Source: AFSGD/Xh0zElfKUgYLPJVokbX7SWo+jSLlZdjjf+4mtGRC5bs7jt0Z8aztErS/o8K2syOJh0wkW+QA== X-Received: by 2002:a24:7fce:: with SMTP id r197mr10142688itc.4.1545329091907; Thu, 20 Dec 2018 10:04:51 -0800 (PST) Received: from raichu (toroon0560w-lp130-07-64-229-95-98.dsl.bell.ca. [64.229.95.98]) by smtp.gmail.com with ESMTPSA id 85sm10033782iou.8.2018.12.20.10.04.50 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 20 Dec 2018 10:04:51 -0800 (PST) Sender: Mark Johnston Date: Thu, 20 Dec 2018 13:04:49 -0500 From: Mark Johnston To: Rebecca Cran Cc: "freebsd-current@FreeBSD.org" , pho@freebsd.org, mckusick@freebsd.org Subject: Re: Panic in getblkx() booting from disc1.iso in Qemu VM Message-ID: <20181220180449.GD98252@raichu> References: <4628942.YNO7O01DYZ@photon.int.bluestop.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4628942.YNO7O01DYZ@photon.int.bluestop.org> User-Agent: Mutt/1.11.1 (2018-12-01) X-Rspamd-Queue-Id: AE2BC8C031 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=fz+iS35z; spf=pass (mx1.freebsd.org: domain of markjdb@gmail.com designates 2607:f8b0:4864:20::132 as permitted sender) smtp.mailfrom=markjdb@gmail.com X-Spamd-Result: default: False [-4.81 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.81)[-0.812,0]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2.3.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.29)[ip: (-8.18), ipnet: 2607:f8b0::/32(-1.78), asn: 15169(-1.41), country: US(-0.08)]; MID_RHS_NOT_FQDN(0.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 18:04:53 -0000 On Thu, Dec 20, 2018 at 10:33:20AM -0700, Rebecca Cran wrote: > I know booting from the cd/dvd iso worked fairly recently, but today booting a > new build of -CURRENT in a Qemu VM resulted in a panic: > > FreeBSD 13.0-CURRENT 19a6ceb89db(HEAD) GENERIC amd64 > FreeBSD clang version 7.0.1 (tags/RELEASE_701/final 349250) (based on LLVM > 7.0.1) > WARNING: WITNESS option enabled, expect reduced performance. > VT(efifb): resolution 800x600 > CPU: QEMU Virtual CPU version 2.5+ (2994.86-MHz K8-class CPU) > Origin="AuthenticAMD" Id=0x663 Family=0x6 Model=0x6 Stepping=3 > Features=0x783fbfd > Features2=0x80002001 > AMD Features=0x20100800 > AMD Features2=0x5 > SVM: NAsids=16 > Hypervisor: Origin = "TCGTCGTCGTCG" > real memory = 8589934592 (8192 MB) > avail memory = 8227643392 (7846 MB) > > ... > > WARNING: WITNESS option enabled, expect reduced performance. > Trying to mount root from cd9660:/dev/iso9660/13_0_CURRENT_AMD64_DVD [ro]... > panic: bsize == 0, check bo->bo_bsize > cpuid = 0 > time = 2 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0041189270 > vpanic() at vpanic+0x1b4/frame 0xfffffe00411892d0 > panic() at panic+0x43/frame 0xfffffe0041189330 > getblkx() at getblkx+0x807/frame 0xfffffe00411893f0 > breadn_flags() at breadn_flags+0x3d/frame 0xfffffe0041189460 > cd9660_blkatoff() at cd9660_blkatoff+0x53/frame 0xfffffe00411894d0 > cd9660_vget_internal() at cd9660_vget_internal+0x26b/frame 0xfffffe0041189550 > vfs_domount() at vfs_domount+0x7d3/frame 0xfffffe0041189770 > vfs_donmount() at vfs_donmount+0x7b9/frame 0xfffffe0041189810 > kernel_mount() at kernel_mount+0x58/frame 0xfffffe0041189860 > parse_mount() at parse_mount+0x469/frame 0xfffffe00411899a0 > vfs_mountroot() at vfs_mountroot+0x67f/frame 0xfffffe0041189b10 > start_init() at start_init+0x28/frame 0xfffffe0041189bb0 > fork_exit() at fork_exit+0x84/frame 0xfffffe0041189bf0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0041189bf0 Peter reported the same problem with ext2. I believe this is a regression from r342135, which moved a VFS_ROOT call before VFS_STATFS. For most filesystems, VFS_STATFS is the place where mp->mnt_stat is initialized, so the problem arises because mnt_stat.f_iosize is still 0 when the root vnode is initialized. UFS initializes mnt_stat.f_iosize in its VFS_MOUNT implementation, so it is immune to this problem. From owner-freebsd-current@freebsd.org Thu Dec 20 19:58:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1295E13524E2; Thu, 20 Dec 2018 19:58:56 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABECB6ADC6; Thu, 20 Dec 2018 19:58:55 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-it1-f176.google.com (mail-it1-f176.google.com [209.85.166.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 80C94E799; Thu, 20 Dec 2018 19:58:55 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-it1-f176.google.com with SMTP id g85so3807078ita.3; Thu, 20 Dec 2018 11:58:55 -0800 (PST) X-Gm-Message-State: AA+aEWZryGy8f7KjeQhhQgVskCY9ywn6Hcb0uBwcZREoc6U2nf15BO9O FR1rd5eT95gKg8Go4bNd01POe9gwrLdcJz6Efgs= X-Google-Smtp-Source: ALg8bN4O7b0j6vR1+AkhII0UFSXDVmhFTywoC06WTavp+8HhZ7fr4ThuoFHI04anvt+Qm2vcH8Uehi/NTDmTA5JDIf4= X-Received: by 2002:a24:9005:: with SMTP id x5mr45809itd.102.1545335934972; Thu, 20 Dec 2018 11:58:54 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Matthew Macy Date: Thu, 20 Dec 2018 11:58:43 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Warner Losh Cc: freebsd-fs , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: ABECB6ADC6 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.97)[-0.965,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 19:58:56 -0000 On Thu, Dec 20, 2018 at 9:33 AM Warner Losh wrote: > > > Matt, > > This is a fairly comprehensive plan. Kudos for putting it together. > > The big question here is do you have a complete list of FreeBSD-specific changes that will be lost in the cut-over? We've heard about TRIM support and maybe NFSv4, but are there others that can be identified? > > Once you have that list, it wouldn't be hard to throw the initial email with some tweaks from the replies into a FCP so everybody knows the plan, and we have it ratified in case people come along later and 'forget'. The general intent is that we not lose anything. TRIM is the only piece of code that really needs resolution upstream causing us to lose it temporarily. Failure to upstream FreeBSD's TRIM support has been a recurring source of bugs when integrating new features. As for NFSv4 I've forked the ACL bits in to the OS dependent code - I'll make a note to make sure that nothing regresses there. This is yet another example of why there will be a 3 month period for users to try the port before we cut over. -M From owner-freebsd-current@freebsd.org Thu Dec 20 20:29:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BEE71353037 for ; Thu, 20 Dec 2018 20:29:00 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic306-3.consmr.mail.bf2.yahoo.com (sonic306-3.consmr.mail.bf2.yahoo.com [74.6.132.42]) (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 4EC786BFE8 for ; Thu, 20 Dec 2018 20:28:59 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 2JFnqj0VM1kJS.8j46j4nt211ocIG31sDXNqAFsvSSEh.j3dRZRf_t7pwSOimSO 73emricSDphZ2IjDSaNhuaoO9M_w6FO4rUZ6XVO2R.onw5IfFqbtItn3whk8pLcJYTqhsXaBhRRe 4s5MKiGD2u1zTkH.XDWjl4lGDPc7Y4vDW4Z5a.9XtneDu16Pw3fQl_HGnBRRVDZdfDsjOWGuRZuT HXEAwx11SeLiPYoK0LHXfPym.901YVT86O67xAKS2sDl_g410FGwG4tb2J5EjUUQr42PxS6b6UZi sa.SZnwDSilh5W0ezB.QKwBF0sbNoxmfTGcySuuEewRxp8yLWMN19Oe4bM2d5DKdD6.Jx6zx7sRH 6LGI8fW1oedbbnTz35Xl9aDPWV8nGScSsmRBylPLmighLuUPp1pE32C308wLzq5pAxAFjuoIQhNn DFlNqu4DYeqMn4w1VtK9s4rpE5I8krKKJzwjyXX5Gxf4jDp7SwNErvjIYaUYHgg2ZIG3lDA2LHVn ObNuq8_57zB9afW_6lauaSTOaey4zkOdSQf.FlOft6ZCVgVzQ7WQ.vHTZf7fyH.kBkKHJcM68e1Q eLM2NohoO7wXL7dfpsXCHHjoVwSRWflWLSFRe.uZH1t09P4qjsXjkVO0tFSgWDNlUvrUZAgAeavD FcPYreQVl_4Oxx7_IG9ERmXgCKt6Nla3YIrUHwOWSO_u7fI4gkFs4oRgxQ9wSw6EzHViFCgIrt27 wqN.2zUztHtw9wHhqI4q_wzACiyVpCQJT.5xx5N39eRWJn4wrtnHDz7mdcBgwojy3VTnLVSf93kg lBoKkH9E.V.XBiBCCZXR6flNRGjjW6wRaD_kNkw0uwie8FZGEPzVXRE9GBhIIoXOIApJiPkRQmPG HAl46JKZsZawkWH2X7HRb51jKIZSoah5iiO.OPiYwmD4UVT4ChmK.nDBskbHi4DWvfHx9NzSOezE OF_Bs8S52fA8jUL5SZWnSmDDk5fALfrAzbtMBpNy0lWy0KE_tk_RFojM59gtugyTRyeRJio4wq2Q uGGZKX1zVeAa8Emg2YauBL1m72VaKMbqh6XehaBDDD2zHZl52wL0hw3yQS2tF_1OjmA_Htw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.bf2.yahoo.com with HTTP; Thu, 20 Dec 2018 20:28:57 +0000 Received: from c-67-170-167-181.hsd1.or.comcast.net (EHLO [192.168.1.109]) ([67.170.167.181]) by smtp408.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 0d16d82eec8ee89c06abd20fccc717bb; Thu, 20 Dec 2018 20:28:54 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: FreeBSD head -r341836 amd64->aarch64 cross-build of -r484783 ports via poudriere: devel/qt5-testlib hung-up during "Checking for POSIX monotonic clock" Date: Thu, 20 Dec 2018 12:28:51 -0800 References: <190D54A2-D29A-4B62-B8FF-99514DBE92A0@yahoo.com> <8A63BA63-FBCB-40DA-B031-4C7F4B1F5118@yahoo.com> To: freebsd-arm , FreeBSD Current , ports-list freebsd In-Reply-To: <8A63BA63-FBCB-40DA-B031-4C7F4B1F5118@yahoo.com> Message-Id: X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: 4EC786BFE8 X-Spamd-Bar: / X-Spamd-Result: default: False [0.95 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MV_CASE(0.50)[]; FREEMAIL_FROM(0.00)[yahoo.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.00)[-0.002,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:26101, ipnet:74.6.128.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.01)[-0.008,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-0.17)[-0.171,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(1.64)[ip: (5.27), ipnet: 74.6.128.0/21(1.67), asn: 26101(1.34), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[42.132.6.74.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 20:29:00 -0000 [A amd64->armv7 cross build shows interesting hang-up behavior as well, apparently highly repeatable for my current context.] On 2018-Dec-19, at 16:21, Mark Millard wrote: > [I attached to the hung-up process with gdb and looked around a = little.] >=20 > On 2018-Dec-19, at 13:58, Mark Millard wrote: >=20 >> [Looks like a race or some such for devel/qt5-testlib: retry of = poudreire-devel >> did not hang. The other hang-up seems to be repeating and I give some = details.] >>=20 >> On 2018-Dec-19, at 12:20, Mark Millard wrote: >>=20 >>> FYI: Based on FreeBSD head -r341836 (host and target) and ports = -r484783 . This >>> was a rebuild based on going from perl5.26 to perl5.28 without = updating the ports >>> tree and from system clang 6 for the prior FreeBSD-head context used = to clang 7 >>> this time. (I'm not attributing causes here.) poudriere was using = amd64-native >>> tools for speeding up the cross-build. >>>=20 >>> # grep -r =3Dperl5=3D /etc/ ~/src.configs/ /usr/local/etc/ >>> /etc/make.conf:DEFAULT_VERSIONS+=3Dperl5=3D5.28 gcc=3D8 >>> /usr/local/etc/poudriere.d/make.conf:DEFAULT_VERSIONS+=3Dperl5=3D5.28 = gcc=3D8 >>>=20 >>> There was also a "print/texinfo:configure/runaway" but I've not = looked into >>> it at all yet and it may be a while before I do. The other ports = attempted >>> built fine as far as I can tell so far. >>>=20 >>>=20 >>> The devel/qt5-testlib failure looks like: >>>=20 >>> [00:00:13] Building 123 packages using 28 builders >>> . . . >>> [00:49:30] [10] [00:00:00] Building devel/qt5-testlib | = qt5-testlib-5.11.2 >>> . . . >>> [07:31:31] [10] [06:42:01] Saved devel/qt5-testlib | = qt5-testlib-5.11.2 wrkdir to: = /usr/local/poudriere/data/wrkdirs/FBSDFSSDjailCortexA57-default/default/qt= 5-testlib-5.11.2.tar >>> [07:31:32] [10] [06:42:02] Finished devel/qt5-testlib | = qt5-testlib-5.11.2: Failed: configure/runaway >>>=20 >>> With logs/errors/qt5-testlib-5.11.2.log showing: >>>=20 >>> Checking for POSIX monotonic clock...=20 >>> + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin= /qmake "CONFIG -=3D qt debug_and_release app_bundle lib_bundle" "CONFIG = +=3D shared warn_off console single_arch" = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic >>> + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && MAKEFLAGS=3D make >>> =3D>> Killing runaway build after 21600 seconds with no output >>> =3D>> Cleaning up wrkdir >>> =3D=3D=3D> Cleaning for qt5-testlib-5.11.2 >>> Killed >>> build of devel/qt5-testlib | qt5-testlib-5.11.2 ended at Wed Dec 19 = 06:45:42 PST 2018 >>> build time: 06:41:46 >>> !!! build failure encountered !!! >>>=20 >>>=20 >>> # less = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.log >>> . . . >>> test config.qtbase_corelib.libraries.librt succeeded >>> executing config test clock-monotonic >>> + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin= /qmake "CONFIG -=3D qt debug_and_release app_bundle lib_bundle" "CONFIG = +=3D shared warn_off console single_arch" = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic >>> + cd = /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/con= fig.tests/clock-monotonic && MAKEFLAGS=3D make >>>=20 >>>=20 >>> Some supporting details of context: >>>=20 >>> # uname -apKU >>> FreeBSD FBSDFSSD 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r341836M: Tue = Dec 11 16:37:42 PST 2018 = markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/G= ENERIC-NODBG amd64 amd64 1300005 1300005 >>>=20 >>> # svnlite info /usr/ports/ | grep "Re[plv]" >>> Relative URL: ^/head >>> Repository Root: svn://svn.freebsd.org/ports >>> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 >>> Revision: 484783 >>> Last Changed Rev: 484783 >>>=20 >>=20 >> I started poudriere up again with just the 2 needing to be rebuilt = (plus >> what depends on the 2). devel/qt5-testlib quickly completed just = fine: >>=20 >> [00:02:16] [02] [00:00:00] Building devel/qt5-testlib | = qt5-testlib-5.11.2 >> [00:04:54] [02] [00:02:38] Finished devel/qt5-testlib | = qt5-testlib-5.11.2: Success >>=20 >>=20 >> In the prior build that had the hang-ups I looked and dor = print/texinfo : >>=20 >> /wrkdirs/usr/ports/print/texinfo/work/texinfo-6.5/config.log shows = for its >> hang-up: >>=20 >> . . . >> configure:6639: checking for alloca >> configure:6676: /nxb-bin/usr/bin/cc -o conftest -O2 -pipe = -mcpu=3Dcortex-a57 -DLIBICONV_PLUG -g -fno-strict-aliasing = -mcpu=3Dcortex-a57 -DLIBICONV_PLUG -D_THREAD_SAFE conftest.c >&5 >> configure:6676: $? =3D 0 >> configure:6684: result: yes >> configure:6794: checking for C/C++ restrict keyword >> configure:6821: /nxb-bin/usr/bin/cc -c -O2 -pipe -mcpu=3Dcortex-a57 = -DLIBICONV_PLUG -g -fno-strict-aliasing -mcpu=3Dcortex-a57 = -DLIBICONV_PLUG -D_THREAD_SAFE conftest.c >&5 >> configure:6821: $? =3D 0 >> configure:6829: result: __restrict >> configure:6844: checking whether // is distinct from / >>=20 >>=20 >> In the poudriere re-run print/texinfo seems to be not progressing: >>=20 >> root 87913 0.0 0.0 12920 3668 0 I 13:29 = 0:00.06 | | `-- sh: = poudriere[FBSDFSSDjailCortexA57-default][01]: build_pkg = (texinfo-6.5_1,1) (sh) >> root 88869 0.0 0.0 12920 3660 0 I 13:29 = 0:00.00 | | `-- sh: = poudriere[FBSDFSSDjailCortexA57-default][01]: build_pkg = (texinfo-6.5_1,1) (sh) >> root 88870 0.0 0.0 10412 1848 0 IJ 13:29 = 0:00.01 | | `-- /usr/bin/make -C /usr/ports/print/texinfo = configure >> root 88974 0.0 0.0 10272 1812 0 IJ 13:30 = 0:00.00 | | `-- /bin/sh -e -c (cd = /wrkdirs/usr/ports/print/texinfo/work/texinfo-6.5 && = _LATE_CONFIGURE_ARGS=3D"" ; if [=20 >> root 89283 0.0 0.0 11160 2108 0 IJ 13:30 = 0:00.10 | | `-- /bin/sh ./configure --enable-nls = --prefix=3D/usr/local --localstatedir=3D/var --mandir=3D/usr/local/man = --di >> root 89692 0.0 0.0 227368 14504 0 IJ 13:30 = 0:00.03 | | `-- /usr/local/bin/qemu-aarch64-static = wc //dev/null >> root 89694 0.0 0.0 227424 14596 0 IJ 13:30 = 0:00.01 | | `-- /usr/local/bin/qemu-aarch64-static = wc //dev/null >> root 89695 0.0 0.0 227584 14720 0 IJ 13:30 = 0:00.01 | | `-- wc: zygote (qemu-aarch64-static) >>=20 >>=20 >> So it appears that: >>=20 >> /usr/local/bin/qemu-aarch64-static wc //dev/null >>=20 >> is hanging-up (again). >>=20 >>=20 >> Given that these are hangups I'll note that this is a Ryzen >> Threadripper 1950X context and is running under Hyper-V from >> Windows 10's 1809 update. I gave it 28 logical processors and >> have it to have the virtual NUMA topology match the topology of >> the physical hardware: "Use Hardware Topology". (Processors >> 28, NUMA nodes 2, Sockets 1, Hardware threads per core 2.) >=20 > Attaching to the stuck process via gdb and looking at the backtrace > shows: >=20 > (gdb) attach 89695 > Attaching to program: /usr/local/bin/qemu-aarch64-static, process = 89695 > [New LWP 101548 of process 89695] > [Switching to LWP 100804 of process 89695] > _pselect () at _pselect.S:3 > 3 PSEUDO(pselect) >=20 > (gdb) bt > #0 _pselect () at _pselect.S:3 > #1 0x00000000601da57f in __thr_pselect (count=3D12, = rfds=3D0x7ffffffe3650, wfds=3D0x0, efds=3D0x0, timo=3D0x0, = mask=3D0x7ffffffe3600) at /usr/src/lib/libthr/thread/thr_syscalls.c:378 > #2 0x000000006004928d in do_freebsd_select (env=3D0x860edfb18, = n=3D, rfd_addr=3D140736934698744, wfd_addr=3D, efd_addr=3D0, target_tv_addr=3D0) > at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/freebsd/os-time.h:468 > #3 do_freebsd_syscall (cpu_env=3D0x860edfb18, num=3D93, arg1=3D12, = arg2=3D140736934698744, arg3=3D0, arg4=3D0, arg5=3D0, arg6=3D274914043516,= arg7=3D274913946564, arg8=3D6579811) > at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/syscall.c:1106 > #4 0x000000006003903c in target_cpu_loop (env=3D0x860edfb18) at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/aarch64/target_arch_cpu.h:100 > #5 0x0000000060038e09 in cpu_loop (env=3D0xc) at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/main.c:121 > #6 0x0000000060039ecb in main (argc=3D, = argv=3D0x7fffffffd360) at = /wrkdirs/usr/ports/emulators/qemu-user-static/work/qemu-bsd-user-4ef7d07/b= sd-user/main.c:513 >=20 > (gdb) up > #1 0x00000000601da57f in __thr_pselect (count=3D12, = rfds=3D0x7ffffffe3650, wfds=3D0x0, efds=3D0x0, timo=3D0x0, = mask=3D0x7ffffffe3600) at /usr/src/lib/libthr/thread/thr_syscalls.c:378 > 378 ret =3D __sys_pselect(count, rfds, wfds, efds, timo, = mask); > (gdb) print *rfds > $1 =3D {__fds_bits =3D {2048, 0 }} >=20 > (gdb) info threads > Id Target Id Frame=20 > * 1 LWP 100804 of process 89695 _pselect () at _pselect.S:3 > 2 LWP 101548 of process 89695 _umtx_op_err () at = /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 >=20 > (gdb) thread 2=20 > [Switching to thread 2 (LWP 101548 of process 89695)] > #0 _umtx_op_err () at = /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 > 37 RSYSCALL_ERR(_umtx_op) >=20 > (gdb) bt > #0 _umtx_op_err () at = /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 > #1 0x00000000601d2ec0 in _thr_umtx_timedwait_uint (mtx=3D0x861027008, = id=3D, clockid=3D, abstime=3D, shared=3D) > at /usr/src/lib/libthr/thread/thr_umtx.c:236 > #2 0x00000000601dc6f8 in cond_wait_user (cvp=3D, = mp=3D0x860515b00, abstime=3D0x0, cancel=3D1) at = /usr/src/lib/libthr/thread/thr_cond.c:307 > #3 cond_wait_common (cond=3D, mutex=3D, = abstime=3D0x0, cancel=3D1) at /usr/src/lib/libthr/thread/thr_cond.c:367 > #4 0x00000000601438bc in qemu_futex_wait (ev=3D, = val=3D4294967295) at util/qemu-thread-posix.c:350 > #5 qemu_event_wait (ev=3D0x62735d10 ) at = util/qemu-thread-posix.c:445 > #6 0x000000006014a92a in call_rcu_thread (opaque=3D) = at util/rcu.c:255 > #7 0x00000000601dc376 in thread_start (curthread=3D0x860518e00) at = /usr/src/lib/libthr/thread/thr_create.c:291 > #8 0x0000000000000000 in ?? () > Backtrace stopped: Cannot access memory at address 0x7fffdfdfc000 >=20 In a separate rebuild of 124 ports print/texinfo repeated its problem. In a rebuild targeting armv7, multimedia/gstreamer1-qt hung-up and timed out. Another poudriere run also hung-up: root 33719 0.0 0.0 12920 3528 0 I 11:40 0:00.03 | = | `-- sh: poudriere[FBSDFSSDjailArmV7-default][02]: build_pkg = (gstreamer1-qt5-1.2.0_14) (sh) root 41551 0.0 0.0 12920 3520 0 I 11:43 0:00.00 | = | `-- sh: poudriere[FBSDFSSDjailArmV7-default][02]: = build_pkg (gstreamer1-qt5-1.2.0_14) (sh) root 41552 0.0 0.0 10340 1744 0 IJ 11:43 0:00.01 | = | `-- /usr/bin/make -C /usr/ports/multimedia/gstreamer1-qt = FLAVOR=3Dqt5 build root 41566 0.0 0.0 10236 1796 0 IJ 11:43 0:00.00 | = | `-- /bin/sh -e -c (cd = /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build; if ! = /usr/bin/env QT_SELE root 41567 0.0 0.0 89976 12896 0 IJ 11:43 0:00.07 | = | `-- /usr/local/bin/qemu-arm-static ninja -j28 -v all root 41585 0.0 0.0 102848 25056 0 IJ 11:43 0:00.10 | = | |-- /usr/local/bin/qemu-arm-static = /usr/local/bin/cmake -E cmake_autogen /wrkdirs/usr/ports/multimedia/g root 41586 0.0 0.0 102852 25072 0 IJ 11:43 0:00.11 | = | `-- /usr/local/bin/qemu-arm-static = /usr/local/bin/cmake -E cmake_autogen /wrkdirs/usr/ports/multimedia/g or as top showed it: 41552 root 1 52 0 10M 1744K 0 wait 15 0:00 = 0.00% /usr/bin/make -C /usr/ports/multimedia/gstreamer1-qt FLAVOR=3Dqt5 = build 41566 root 1 52 0 10M 1796K 0 wait 1 0:00 = 0.00% /bin/sh -e -c (cd = /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build; if ! = /usr/bin/env QT_SELECT=3Dqt5 QMAKEMODULES 41567 root 2 52 0 88M 13M 0 select 4 0:00 = 0.00% /usr/local/bin/qemu-arm-static ninja -j28 -v all 41585 root 2 52 0 100M 24M 0 kqread 8 0:00 = 0.00% /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E = cmake_autogen /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/. 41586 root 2 52 0 100M 24M 0 kqread 22 0:00 = 0.00% /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E = cmake_autogen /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/. So: waiting in kqread. Repeated tries have gotten the same result so far. If this keeps up, later I may be able to try a native FreeBSD boot instead of Hyper-V use on the same machine. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Thu Dec 20 20:47:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 182A11353947 for ; Thu, 20 Dec 2018 20:47:51 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC3846D183 for ; Thu, 20 Dec 2018 20:47:50 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from Ticonderoga.HML3.ScaleEngine.net (senat1-01.HML3.ScaleEngine.net [209.51.186.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: allanjude) by smtp.freebsd.org (Postfix) with ESMTPSA id 7AE4AECFE for ; Thu, 20 Dec 2018 20:47:50 +0000 (UTC) (envelope-from allanjude@freebsd.org) Subject: Re: The future of ZFS in FreeBSD To: freebsd-current@freebsd.org References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> From: Allan Jude Message-ID: Date: Thu, 20 Dec 2018 15:47:49 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: AC3846D183 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.99)[-0.985,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 20:47:51 -0000 On 12/19/2018 13:32, Allan Jude wrote: > Today, the OpenZFS repo is just a fork of the illumos-gate repo, but > where pull requests are accepted, and where previous Delphix employees This should say 'previously', Prakash Surya and Matt Ahrens still work at Delphix. > would deal with the process of trying to upstream patches to illumos. > This process has not worked well recently, as things have gotten stuck > waiting for 'merge advocates' in illumos. > The major stumbling block was the lack of modern test infrastructure. Obviously depending on one or two people to merge stuff was a bottleneck as those people inevitably get busy. Anyway, the point is that this doesn't make FreeBSD any more dependent on Linux. The goal is this project is to continue to make it easier and easier to port OpenZFS and its new features to all platforms (illumos, FreeBSD, Linux, OS X, Windows, NetBSD, etc), and to ensure that new features arrive in a timely fashion in all of the platforms. Unifying on a single CI setup saves duplication of effort, and ensures that changes can easily be tested on all of the platforms. This is a project is a good thing, it ensures that FreeBSD will keep current on OpenZFS going forward, and helps improve the entire OpenZFS ecosystem. I am to give a big thanks to Matt Ahrens for organizing the monthly OpenZFS Leadership meeting, and the OpenZFS developer summit, and to Brian Behlendorf for being so helpful, and willing to work to make OpenZFS better for everyone. -- Allan Jude From owner-freebsd-current@freebsd.org Thu Dec 20 21:18:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A441213547DB for ; Thu, 20 Dec 2018 21:18:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B3E4B6E6CC for ; Thu, 20 Dec 2018 21:18:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x82a.google.com with SMTP id t33so3475916qtt.4 for ; Thu, 20 Dec 2018 13:18:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hwXryhLjSdCY1W7fBhmwrBoudRTx3lw6nq++oUodY9g=; b=lD5GosJPhRY9WSBweKVBDBnA8C3FYzocsXbHkEHYGObCwN10Lb5+UuYvRXX20bAbF5 /AtcI9/MB/ZGRFw8W9TDVNO9k1HfKFNI8IiZ3twPVSM4RbYzLHluCsya0ZGPxKNuc9iG a1uhgHnaGTv56Pdiczv3E+IlKtJRB9rHTuYC1BbZleItu3KouheZyneb5wA1zEa63HLU gbI+CBvV8fOX/25hRX2IeQFCXTCO8q+CWaxiNRUv9hnyjDs+/h4wuuopLBRN+gtunSQu LLjVHp1LWilDPUKRKZaHrPYPXyZGDWFz0sLTwNio6nX2J+Mna/XVAIa352d5g2iTkp8/ f+Sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hwXryhLjSdCY1W7fBhmwrBoudRTx3lw6nq++oUodY9g=; b=qXPJne1+xzjU3es/GRQ91iz3u/WbWgH7vihYBpgyaR6rjtCDIstH8gFk+I2WgiK/C1 vtIXAZdApVzbxNa1ria1XzO4juhwvjdol+HVxxSXZC6umzzlfvC+QRYLrblTF6tu6mo8 yCI1VVm0FoalP5FMPJXRGcD2IG5EQP1qtS8Zfm7SYl8ivaKh9bG6kuXf++EeyjkNHQS4 nhwkQHqpkS6Esgkh/lHC5wj3aI3RqU3KdTZRspXJsgYd54Q8xX26qmjfM+t4zcy0CMZ3 UMsQQsfRx0VY8xcb87/CX/xKUWOBCfYqg0Hs5nxmlE7q7q/HPxuOZnLPnaS2xHlFhAtk qNQg== X-Gm-Message-State: AA+aEWbskaO2Sl1+r0F/NtndOq6Gmu7xPU//i/LQfukjWzXXgCyRKTZH 5GHQYH8bKj6kEnq+fl8gMm1URA7nlH7SQOv7x2qlk4tV X-Google-Smtp-Source: AFSGD/XVQ0JaiLCfaEzAAOddJi1Bs8Y4Cg5sHAokaQoTQC4wU62PU4wqYDVPzxDRlQRKoCi8/CmgY1a8aZrlnRobCjU= X-Received: by 2002:a0c:f143:: with SMTP id y3mr28124469qvl.21.1545340683028; Thu, 20 Dec 2018 13:18:03 -0800 (PST) MIME-Version: 1.0 References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> In-Reply-To: From: Warner Losh Date: Thu, 20 Dec 2018 14:17:52 -0700 Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Allan Jude Cc: FreeBSD Current X-Rspamd-Queue-Id: B3E4B6E6CC X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=lD5GosJP X-Spamd-Result: default: False [-5.08 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.976,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[a.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; IP_SCORE(-2.09)[ip: (-7.14), ipnet: 2607:f8b0::/32(-1.81), asn: 15169(-1.42), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 21:18:04 -0000 On Thu, Dec 20, 2018 at 1:49 PM Allan Jude wrote: > I am to give a big thanks to Matt Ahrens for organizing the monthly > OpenZFS Leadership meeting, and the OpenZFS developer summit, and to > Brian Behlendorf for being so helpful, and willing to work to make > OpenZFS better for everyone. > I'd recommend the monthly leadership meetings. They dispelled any doubt that I had that there were overly powerful factions present that would disadvantage FreeBSD. The calls were worthwhile to understand the context of a number of other things being discussed. It seems much healthier in this context than things I've seen in the Illumos context because of a lack of burdensome process that provided no benefit and actually got in the way (which honestly, was my expectations going into the meeting). There's good reason to trust OpenZFS, it's leadership and decision making process. If ZoL is the best upstream source, then I trust their judgement on that, regardless of the hassles it will cause us in the coming months. >From the discussions I've seen, there is no pain-free choice that doesn't relegate FreeBSD to a backwater of what we have today. Warner From owner-freebsd-current@freebsd.org Thu Dec 20 21:58:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4823A13556F0 for ; Thu, 20 Dec 2018 21:58:45 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-io1-xd44.google.com (mail-io1-xd44.google.com [IPv6:2607:f8b0:4864:20::d44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 265596FCB2; Thu, 20 Dec 2018 21:58:44 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by mail-io1-xd44.google.com with SMTP id m19so2092132ioh.3; Thu, 20 Dec 2018 13:58:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4A5fW5LG8M9fQlTP623f/I0w2zAwM65eV3y7qSZy53c=; b=hsqelCHHBxZDba0Kew3iMrcvrUT/67yYzSBtw0CFgMSB+mhrFgNnlMm94W7Q86VG0A 0CbbOtBXSGmwIMVm82EtqBFQab+4mRlxNSgHgtpDbwKvPFoq38d6pWlMxq8MxRPAM1FB n0dw863PDaBUKEaciFO7R5qgZ7kVuemxBc0LC6muM/EY8qNS9Mjbw9GVdbdPoBVYvFJl 9wBNnTqCg51QnV4tjaRdayRW09W1h0LsB1IzrcH7/WrYqaRan/QrxAJheyZf64CZrfpW NZg08gSIOpvhyU2IY+bSKZuE7Na/TvS2TZXTL7FEcTKpmqLEorIFwJnAfM5Mrd9C7lmK CqVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4A5fW5LG8M9fQlTP623f/I0w2zAwM65eV3y7qSZy53c=; b=XOpcAIby0F9Wve+djY4ofCjaKfUDuV34oZ5e+ybRjlO2xmltx73x/VlzMhwCdArOqz SVVbnRic+N7cHgMBGHbEsDc03O+b2JcGSl4Ga+KjjABM2Q0qwY65leISSrN4PdPu2146 YwP3YA5nWoHBfMAfWp9LLtr0LnKkP+BCvdAY4WSorT9gdNg0lpilv4zy9xqOLUo3xsMq NHhCTyxBo3PCPfhOJJlakfSKfYb2uLBcd3BkXtzG8+f33r5Toud5rWK1fnPPw/dtx4Cz OdqR2HvUeYtMNCjPMXq2sILEolKxthsxBjIqesFlhODoawqz3m/ordIE5d4kTVpjPSSz 0X1A== X-Gm-Message-State: AA+aEWYl4reUrmGidG7C8mrmUcpK6VFpqF1SOci1lU7jcG58Sy06M5rI N9A7ttEsiDCsgRJNm5MsmkNWUYosYqVU2TGidaD7VSH+cfo= X-Google-Smtp-Source: AFSGD/XPB/oaIJCIfIfaRfBL7fm2RqKE07CfD8AVJiUH3OYftUkQTGxiq8mHEUGscnlZCJw028ni+uUhJrU0zYJN7kE= X-Received: by 2002:a6b:e919:: with SMTP id u25mr22833758iof.132.1545343122652; Thu, 20 Dec 2018 13:58:42 -0800 (PST) MIME-Version: 1.0 References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> <4481f3cb-4535-bed3-c09f-429553f8f88b@zhegan.in> <20181220143741.GA40569@FreeBSD.org> In-Reply-To: <20181220143741.GA40569@FreeBSD.org> From: Matthew Macy Date: Thu, 20 Dec 2018 13:58:31 -0800 Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Alexey Dokuchaev Cc: "Eugene M. Zheganin" , freebsd-current@freebsd.org X-Rspamd-Queue-Id: 265596FCB2 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=hsqelCHH; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of matmacy@gmail.com designates 2607:f8b0:4864:20::d44 as permitted sender) smtp.mailfrom=matmacy@gmail.com X-Spamd-Result: default: False [-2.94 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.985,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_LONG(-0.98)[-0.975,0]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.07)[0.068,0]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[4.4.d.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; IP_SCORE(-0.04)[ip: (3.14), ipnet: 2607:f8b0::/32(-1.81), asn: 15169(-1.42), country: US(-0.08)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Mailman-Approved-At: Thu, 20 Dec 2018 22:57:06 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 21:58:45 -0000 On Thu, Dec 20, 2018 at 06:39 Alexey Dokuchaev wrote: > On Thu, Dec 20, 2018 at 03:49:38PM +0500, Eugene M. Zheganin wrote: > > On 19.12.2018 23:32, Allan Jude wrote: > > > The biggest thing to remember is that this is still OpenZFS, and stil= l > > > run by the same developers as it has been. We are just commonizing on > > > the repo that has the most features integrated into it. > > > > Does it mean that ZoF and thus FreeBSD will lose NFSv4 ACLs because > > there is no such thing in ZoL? > +1. I'm also worried if this would bring more Linuxish bits into our > kernel (cf. LinuxKPI). Also, I thought that ZFS was never really native > to Linux but implemented through SPL (Solaris Porting Layer), and Linux' > VFS is not ARC-aware unlike Solaris and FreeBSD. > There is no LinuxKPI involved here. Please re-read Allan=E2=80=99s comments= on directory structuring. No open source OS supporting ZFS has a VM subsystem that is integrated with the ARC. The limited feedback that the ARC has from FreeBSD=E2=80=99s VM will remain unchanged. > It would be quite upsetting to see ZFS as we know it in FreeBSD become > pessimized because of those things. :-( > ZFS will be no more pessimized than it currently is. Talk to mjg some time about ZFS some time, there are ... scaling issues in its locking strategies. Apart from that FreeBSD=E2=80=99s VFS itself has serious scalin= g. None of this will get better or worse when we change the vendor repo we use for integrating changes. -M From owner-freebsd-current@freebsd.org Thu Dec 20 22:00:14 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED4B71355788 for ; Thu, 20 Dec 2018 22:00:13 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 06F016FD16 for ; Thu, 20 Dec 2018 22:00:13 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by mail-it1-x130.google.com with SMTP id g76so4255580itg.2 for ; Thu, 20 Dec 2018 14:00:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rOZS4NoIc/PBiHguNriLQdZ9qM3wfUtd0glDujSMb4w=; b=sfMU34GIQ5odrYiPiAg4lDER9GzSt9Jr5Ldl13Upxd1sKkG7BKfmQKvff50t3FXoO9 0oamh6NE5RSBHMMAfN0hmzwVY9Qej1CnrJR2dD1SlaQHx5LZMFuWvE3V+GoFTzAfRVvQ zQ+hlMcaXghccCgTVFBD0iQJ+2zpb5meMmfYI/b4h1E877/ujUgrFfjeQrkxPXpmegJy hrSvWQ98QFDYMR1OFOInh/N9YZz2RUXSwEzswTmJvURCTziv7OAKg8+qLTlGILHpExIz VeExDi33hVhmg0bEG3nXPMwlE3QpKoje56Cajsl+ocxH09g6HSP4lnqAzcynuaGHHACF DcIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rOZS4NoIc/PBiHguNriLQdZ9qM3wfUtd0glDujSMb4w=; b=ihrFgpORKIOw7BhKyN/l+v7fM/gqJv47r/MYB2ExccNl53xdlxfIduJgZzLi73aBon tOqfIcK9u0MbsquuUkxzsPaYq2y1JyD7pxh3fRqBaJdrSnHWeONO3HtPRz0ThSkrckct tqjOFn8Q7T5TeFlBYeO+pIb4VF2W2tVVbY07s6/uKuzxZT6F/5SgO9mSeM7Wq6R0TnhM nRNtzAm+ZaFzxH3chaTuGBbrQQwQxSQAUkuchJSaaFGQrEHdziGl36TAMkPpXGpoJeIg u1U/NCtFuO/77hm7+oc5Py5+UWxzH6Hdi0ap6ZAt/7ngFD/4q/esnRhJu8ZTTGZkiRu8 ZDCw== X-Gm-Message-State: AA+aEWZk09xP92Hcoq5ilL2OPyrWrmDYUa4HURCzL1UynbKP2o8TooTt dJJlOspPUFTJ8djj4CEBhS3CgygNavxBf9MOd49BdMP7m/Q= X-Google-Smtp-Source: AFSGD/VhW5NbSSXcaNp4lwt54Nw3iJWD1nY1egl0ecrjBksBVaJ/glTfDJZpj3sIIC2VzRhagaZRC7j6pld9Q/47IIo= X-Received: by 2002:a24:9087:: with SMTP id x129mr397468itd.20.1545343212131; Thu, 20 Dec 2018 14:00:12 -0800 (PST) MIME-Version: 1.0 References: <20181219163033.jwm7opiwmdhbk6p3@mutt-hbsd> <4481f3cb-4535-bed3-c09f-429553f8f88b@zhegan.in> In-Reply-To: <4481f3cb-4535-bed3-c09f-429553f8f88b@zhegan.in> From: Matthew Macy Date: Thu, 20 Dec 2018 14:00:00 -0800 Message-ID: Subject: Re: The future of ZFS in FreeBSD To: "Eugene M. Zheganin" Cc: freebsd-current@freebsd.org X-Rspamd-Queue-Id: 06F016FD16 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=sfMU34GI; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of matmacy@gmail.com designates 2607:f8b0:4864:20::130 as permitted sender) smtp.mailfrom=matmacy@gmail.com X-Spamd-Result: default: False [-6.26 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.97)[-0.970,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[0.3.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.28)[ip: (-8.06), ipnet: 2607:f8b0::/32(-1.81), asn: 15169(-1.43), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2] X-Mailman-Approved-At: Thu, 20 Dec 2018 22:57:21 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 22:00:14 -0000 On Thu, Dec 20, 2018 at 03:11 Eugene M. Zheganin wrote: > Hello, > > On 19.12.2018 23:32, Allan Jude wrote: > > The biggest thing to remember is that this is still OpenZFS, and still > > run by the same developers as it has been. We are just commonizing on > > the repo that has the most features integrated into it. > > Does it mean that ZoF and thus FreeBSD will lose NFSv4 ACLs because > there is no such thing in ZoL ? No, but the ZTS will need to have ACL tests re-added. Please help out by aiding in getting this merged: https://github.com/zfsonlinux/zfs/pull/7728 Thanks. -M From owner-freebsd-current@freebsd.org Fri Dec 21 01:20:15 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A36EB1337717 for ; Fri, 21 Dec 2018 01:20:15 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [70.36.157.235]) (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 8B06877129; Fri, 21 Dec 2018 01:20:14 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (localhost [IPv6:::1]) by chez.mckusick.com (8.15.2/8.15.2) with ESMTP id wBL1SjfA041538; Thu, 20 Dec 2018 17:28:45 -0800 (PST) (envelope-from mckusick@mckusick.com) Message-Id: <201812210128.wBL1SjfA041538@chez.mckusick.com> From: Kirk McKusick To: Rebecca Cran , Mark Johnston Subject: Re: Panic in getblkx() booting from disc1.iso in Qemu VM cc: pho@freebsd.org, "freebsd-current@FreeBSD.org" X-URL: http://WWW.McKusick.COM/ Reply-To: Kirk McKusick In-reply-to: <20181220180449.GD98252@raichu> Comments: In-reply-to Mark Johnston message dated "Thu, 20 Dec 2018 13:04:49 -0500." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <41536.1545355725.1@chez.mckusick.com> Date: Thu, 20 Dec 2018 17:28:45 -0800 X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,MISSING_MID, UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on chez.mckusick.com X-Rspamd-Queue-Id: 8B06877129 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.84 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[mckusick@mckusick.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.70)[0.705,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[mckusick.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.25)[0.246,0]; REPLYTO_EQ_FROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: chez.mckusick.com]; NEURAL_SPAM_LONG(0.34)[0.339,0]; RCVD_IN_DNSWL_NONE(0.00)[235.157.36.70.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:46375, ipnet:70.36.128.0/19, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-0.34)[ip: (-0.58), ipnet: 70.36.128.0/19(-0.29), asn: 46375(-0.74), country: US(-0.08)] X-Mailman-Approved-At: Fri, 21 Dec 2018 01:24:20 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2018 01:20:15 -0000 Thanks Rebecca for the report and Mark for the analysis of the problem. This should be fixed in -r342290. Kirk McKusick =-=-= From: Kirk McKusick Date: Fri, 21 Dec 2018 01:09:25 +0000 (UTC) To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r342290 - head/sys/kern Author: mckusick Date: Fri Dec 21 01:09:25 2018 New Revision: 342290 URL: https://svnweb.freebsd.org/changeset/base/342290 Log: Some filesystems (like cd9660 and ext3) require that VFS_STATFS() be called before VFS_ROOT() is called. Move the call for VFS_STATFS() so that it is done after VFS_MOUNT(), but before VFS_ROOT(). This change actually improves the robustness of the mount system call because it returns an error rather than failing silently when VFS_STATFS() returns failure. Reported by: Rebecca Cran Sponsored by: Netflix Modified: head/sys/kern/vfs_mount.c Modified: head/sys/kern/vfs_mount.c ============================================================================== --- head/sys/kern/vfs_mount.c Thu Dec 20 22:39:58 2018 (r342289) +++ head/sys/kern/vfs_mount.c Fri Dec 21 01:09:25 2018 (r342290) @@ -895,6 +895,7 @@ vfs_domount_first( */ error1 = 0; if ((error = VFS_MOUNT(mp)) != 0 || + (error1 = VFS_STATFS(mp, &mp->mnt_stat)) != 0 || (error1 = VFS_ROOT(mp, LK_EXCLUSIVE, &newdp)) != 0) { if (error1 != 0) { error = error1; @@ -916,7 +917,6 @@ vfs_domount_first( vfs_freeopts(mp->mnt_opt); mp->mnt_opt = mp->mnt_optnew; *optlist = NULL; - (void)VFS_STATFS(mp, &mp->mnt_stat); /* * Prevent external consumers of mount options from reading mnt_optnew. From owner-freebsd-current@freebsd.org Fri Dec 21 08:46:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEBAB134202A for ; Fri, 21 Dec 2018 08:46:55 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 17E368CD80 for ; Fri, 21 Dec 2018 08:46:55 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: by mailman.ysv.freebsd.org (Postfix) id C09631342029; Fri, 21 Dec 2018 08:46:54 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96E361342027 for ; Fri, 21 Dec 2018 08:46:54 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 18BA08CD7F for ; Fri, 21 Dec 2018 08:46:53 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from [84.237.50.47] (helo=regency.nsu.ru) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1gaGSH-0008WI-GD for current@freebsd.org; Fri, 21 Dec 2018 15:46:49 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id wBL9Gijb056885 for ; Fri, 21 Dec 2018 15:16:44 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id wBL9Gdll056846 for current@freebsd.org; Fri, 21 Dec 2018 16:16:39 +0700 (+07) (envelope-from danfe) Date: Fri, 21 Dec 2018 16:16:39 +0700 From: Alexey Dokuchaev Cc: FreeBSD Current Subject: Re: AESNI, /dev/crypto, and new OpenSSL Message-ID: <20181221091639.GA53513@regency.nsu.ru> References: <20181220173535.GA2505@regency.nsu.ru> <20181220181007.GA2374@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181220181007.GA2374@regency.nsu.ru> User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 3 X-KLMS-Message-Action: skipped X-KLMS-AntiSpam-Status: not scanned, whitelist X-KLMS-AntiPhishing: not scanned, whitelist X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, whitelist X-Rspamd-Queue-Id: 18BA08CD7F X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.96)[-0.961,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-Mailman-Approved-At: Fri, 21 Dec 2018 11:25:16 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2018 08:46:56 -0000 On Fri, Dec 21, 2018 at 01:10:07AM +0700, Alexey Dokuchaev wrote: > On Thu, Dec 20, 2018 at 09:33:41AM -0800, Freddie Cash wrote: > > On Thu, Dec 20, 2018 at 9:21 AM Alexey Dokuchaev wrote: > > > Had something got broken here, or I'm misunderstanding how this machinery > > > now works? > > > > Start reading here: > > > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090195.html > > > > That thread covers this issue. :) Along with the "fix" for it. > > Thanks for the pointer. I've checked both -current and -hackers MLs prior > to posting, but didn't expect this would show up on -stable first. :) In case people find this thread and want quick answers without having to deviate to -stable, here's a quick summary and my speed test results, with some quotes from delphij@, jhb@, et al.: 1) aesni(4) and crypto[dev](4) modules are not required now for OpenSSL, and userland acceleration in general, to work; 2) On capable systems, AES-NI would be used automatically. In fact, it's much faster to use the AES-NI instructions in userland than to use a system call that copies the data into a kernel buffer, uses the same AES-NI instructions, then copies the data back out again along with the overhead of a pair of user <--> kernel transitions. (Note from me: if you've observed very strange results when using -evp with aesni(4) + BSD cryptodev engine on OpenSSL 1.0.2, it was probably because of that user <--> kernel multicopying.) Some quick naive benchmarks on AMD A8-5550M APU (results were trimmed for brevity): baseline: openssl speed -elapsed aes-128-cbc: 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes 35922.35k 39346.28k 40492.29k 94625.81k 95194.36k 95619.24k hardware extensions: openssl speed -elapsed -evp aes-128-cbc 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes 133823.08k 186960.39k 226363.05k 238189.15k 241782.56k 241646.38k AES-NI disabled: env OPENSSL_ia32cap="~0x200000000000000" openssl speed -elapsed -evp aes-128-cbc: 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes 54820.92k 64884.98k 69229.02k 70424.31k 70731.22k 70714.02k It's interesting how -evp run w/o AES-NI got capped at ~67 GB/s, while the baseline had sustained at ~91 GB/s. AES-NI run had reached pretty solid ~230 GB/s. ./danfe From owner-freebsd-current@freebsd.org Fri Dec 21 23:55:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AF5613379F3 for ; Fri, 21 Dec 2018 23:55:21 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 961A689CB7 for ; Fri, 21 Dec 2018 23:55:20 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: by mailman.ysv.freebsd.org (Postfix) id 597B013379F2; Fri, 21 Dec 2018 23:55:20 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36EA213379F1 for ; Fri, 21 Dec 2018 23:55:20 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 07C3289CB5; Fri, 21 Dec 2018 23:55:17 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2407622101; Fri, 21 Dec 2018 18:55:17 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 21 Dec 2018 18:55:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h=to :cc:from:subject:message-id:date:mime-version:content-type; s= fm3; bh=aQkQ+qQixvRIGu3E9eHd+kgRDOI67y5JANvujBT1WL0=; b=vZ91Eij7 xSXPylHlI5H6t4YPZ/MMdmNJSktsLK8rFP1Az5lqo9+Ola1ajLNMBR03B/bq6kou cgfZmKqkdEBvmlSTl/ZffXmG8Hags8QBhGHzV/1MgWBFYG/2Av/yidziRlhD0PXo LwUfM7TAtgfDCQgGPeJ77uzcGWPGpKDDnTpnJ5eZJVQUo/22n5V0HjsuVMnJ0yeE DFzYcTOvy/z+0ejreUplrg+Ma5jQvE8u3Tw4Ktk5/JGu6Y5lpBhWY0Y3tFInHCet Hz3bCDWgxqHzJgiGSospOIMkm5+++AzooQ4T6A7GwRW+2wp3lXA0XarkD4n2Qx4c Al6resoHghL0IA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=aQkQ+qQixvRIGu3E9eHd+kgRDOI67 y5JANvujBT1WL0=; b=xo5+DzSmCcLB0KEc46AZghh1UNxhiJlKkaIvhLzttMMGO R5biXmtgA+qeOYJ7oz605efQpHgylK4PHmPa1jsE4P+WuGDnxzw4Okm3wrLEKxhl g/U22YoSJlSpFwaFFO+VC32FpFBJbIY2f3kvwrIErRnHZuWe1FZgpABMnCZ4m9Rg zJNgyBKUwKsWsMZTEPem8YHNuujb9Uyhq6woYnjhJim/8XpgBQ/gYMak4/cDSX/c mbv2ypRfmf1ke63/uKigx2wud2naNo6Eu/w6RXqCxo2G70LlxVcFbwYLHOCyv7zm F8PX6I5uVWrQKVIvnRVKZp+ORNp7uV6YktlMV5peQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudejiedgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefvhffukffffg ggtgesghdtrefotdefjeenucfhrhhomhepjghurhhiucfrrghnkhhovhcuoeihuhhrihhp vheshihurhhiphhvrdhnvghtqeenucffohhmrghinheprhgvughhrghtrdgtohhmpdhvmh ifrghrvgdrtghomhdpohhpvghnsghsugdrohhrghenucfkphepleegrddvfeefrddvfedu rdduleehnecurfgrrhgrmhepmhgrihhlfhhrohhmpeihuhhrihhpvheshihurhhiphhvrd hnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from [192.168.1.2] (unknown [94.233.231.195]) by mail.messagingengine.com (Postfix) with ESMTPA id 49EEDE40A1; Fri, 21 Dec 2018 18:55:15 -0500 (EST) To: =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= Cc: freebsd-current From: Yuri Pankov Subject: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes Openpgp: preference=signencrypt Autocrypt: addr=yuripv@yuripv.net; keydata= mQENBFu8u6IBCADB11gP0QwnorrHjqAtKLHKHNHskhy0s7jqJKfx0YqXgVBKGLJ9/mjLAz0F CBNvemHSDDTs0mEZ9cBKKi6cmsav6+UQgr//yai6hvXLBJqKchSFO4MhmdvBtsGFq1yKz5Zi uhjmimKyIpgBgvMdbgGbGq6cnSB2uEPmZuJr419SVRODOkXukU+F5WHgaHzDdHAIu1asCt2B +6msxqIqlFWcXyZyTGicTGGvC/PFIsVRUtD1dIJANTC876g7DTb7LZXWiWwJpSJ4GKMXMHVX Ct9BoQ4i3nhKbOxb6Io1wsy+NFyWsTJ9KYrxKKPJP3oG8BWb/cqlFqnE4eNSsiq2q7krABEB AAG0H1l1cmkgUGFua292IDx5dXJpcHZAeXVyaXB2Lm5ldD6JAVQEEwEKAD4WIQT4arc+w94t Pi0v/3CTi+B/sSrhbAUCW7y7ogIbAwUJBaOagAULCQgHAwUVCgkICwUWAwIBAAIeAQIXgAAK CRCTi+B/sSrhbJ+ACACqOlkjZ+iP8K8hcwz/G6+c1lVkhuMWL+hxFeE149QuJAXQvkOj/UXO 7jY9HSqFbOYYY44/hujpQCu+/u2dsJ5MAA7TJspWK2zUxtFAzgDp1fRXmCvMlFLdI0yVkKOB JaK+HQP8rBT6yHzGw1KJ6VyOXuuD0Kx02Ou61qjG9/vPRR0jtaxog0rKxpf+yf0UvSM4vb7+ LdY2GQxgfcLcJ8hThR4ElWJAkDsG4CiXixGJuFJ+9dpMK6LHmP6M+NxV4NkzpNddn3Eii8XQ y5spxcLszp8csFBDtAC6BI9sHLhJ9Va1VKpuvSlDsBv4ZtsjnUCIaOiF5MDTYkddSPGGMBck uQENBFu8u6IBCADKih3Q933rDNj4ZA8FhBQ2RlmBgvwOLcDPIL3h0V7h38y3+HisgFScXACD sdrTlYZ1bRXkD9FHENynBcv0l/3uGJDk8jaGIDE0TP8OQBRp+IaU9/BHnAqrKxTJGIolDahy 2m+yx2yhdc6B4ujWMDqCF1rWOD+ymOWw+VLllOkrHcZa5PJtX9UOGbApZl8ZTM8El4CANN8F 1bg9MWzUi+8LYoGWGc+BwsFS1OUB1c4SPgMu5fD4Wfsr9yRl06fdpEA2YT7B/j5/5RSC0sE2 Zs/tmJ/JRflHJ12ycj59ma2xQMfEJF40hZDpMFQmZvbVqgEg3ocQcltjbxlIKZ/mjC4zABEB AAGJATwEGAEKACYWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW7y7ogIbDAUJBaOagAAKCRCT i+B/sSrhbIDcCACqAZMcoxUBLZa40a5b24j5i1jplvCYYb3h+Q5lt5+BFJ87kCb4dJuUD3kh 2i29BrxWQWa9WNue9ozxeYkbkfXubQYXexVolRsnh64OdGsE8KvorBFBB3zdK/GRt2Jy+jsn TfUWuQllbzMP0MfhCDMk1Mo8WvDH2/cOEP/yLKf20a+cd6nLs7bidjmGXo9pyuBKAtV6Kv+V Ru54AL+A/UBYu/eB3Dtvzcnut+1Zq6KaP++kUwPwINLIk04OBDwN0zRNTiqMAFYYyz2vZHBB 6E1th/l//ZC5b9Dk0ZpFI1bYdL9ymnrZe1MqbGPnDCToQxu00T/pZCm6Z92YrZQYuNwl Message-ID: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> Date: Sat, 22 Dec 2018 02:55:00 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TqPqiUNwPUb4a2XM8oPk8mDB5mLAFV03B" X-Rspamd-Queue-Id: 07C3289CB5 X-Spamd-Bar: --------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yuripv.net header.s=fm3 header.b=vZ91Eij7; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=xo5+DzSm; spf=pass (mx1.freebsd.org: domain of yuripv@yuripv.net designates 66.111.4.25 as permitted sender) smtp.mailfrom=yuripv@yuripv.net X-Spamd-Result: default: False [-9.19 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25]; HAS_ATTACHMENT(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yuripv.net:+,messagingengine.com:+]; RCPT_COUNT_TWO(0.00)[2]; MIME_BASE64_TEXT(0.10)[]; MX_GOOD(-0.01)[in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.980,0]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-3.60)[ip: (-9.50), ipnet: 66.111.4.0/24(-4.66), asn: 11403(-3.78), country: US(-0.08)]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:+,4:+]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[25.4.111.66.list.dnswl.org : 127.0.5.1]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[yuripv.net:s=fm3,messagingengine.com:s=fm1]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; DMARC_NA(0.00)[yuripv.net] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2018 23:55:21 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TqPqiUNwPUb4a2XM8oPk8mDB5mLAFV03B Content-Type: multipart/mixed; boundary="U4ybSsOLfMyrv5BMcnAylgrTt8f3Jn1iC"; protected-headers="v1" From: Yuri Pankov To: =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= Cc: freebsd-current Message-ID: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> Subject: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes --U4ybSsOLfMyrv5BMcnAylgrTt8f3Jn1iC Content-Type: multipart/mixed; boundary="------------B62CC6903F713B5198EED8DA" Content-Language: en-US This is a multi-part message in MIME format. --------------B62CC6903F713B5198EED8DA Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, There's apparently a bug in VMware Workstation NAT implementation, made visible by the change to default values of IPQoS in OpenSSH 7.8p1, making all ssh connections from the guest behind the NAT to fail with obscure "Fssh_packet_write_wait: Connection to 192.168.1.53 port 22: Broken pipe". I wonder if we could integrate the attached patch (or some smarter version of it) for the time being as the bug affects several major WS releases, and it's not immediately clear where the problem is. The change itself: https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/readconf.c#rev1= =2E284 The bug reports (some of them): https://bugzilla.redhat.com/show_bug.cgi?id=3D1624437 https://communities.vmware.com/message/2803219#2803219 The patch itself is attached. --------------B62CC6903F713B5198EED8DA Content-Type: text/plain; charset=UTF-8; name="vmwssh.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="vmwssh.diff" ZGlmZiAtLWdpdCBhL2NyeXB0by9vcGVuc3NoL3JlYWRjb25mLmMgYi9jcnlwdG8vb3BlbnNz aC9yZWFkY29uZi5jCmluZGV4IGY5N2E2YWM3MmE5NS4uOWVkNjkwMmEwZjQ2IDEwMDY0NAot LS0gYS9jcnlwdG8vb3BlbnNzaC9yZWFkY29uZi5jCisrKyBiL2NyeXB0by9vcGVuc3NoL3Jl YWRjb25mLmMKQEAgLTE2LDYgKzE2LDkgQEAKIF9fUkNTSUQoIiRGcmVlQlNEJCIpOwogCiAj aW5jbHVkZSA8c3lzL3R5cGVzLmg+CisjaWZkZWYgVk1XQVJFX0dVRVNUX1dPUktBUk9VTkQK KyNpbmNsdWRlIDxzeXMvc3lzY3RsLmg+CisjZW5kaWYKICNpbmNsdWRlIDxzeXMvc3RhdC5o PgogI2luY2x1ZGUgPHN5cy9zb2NrZXQuaD4KICNpbmNsdWRlIDxzeXMvd2FpdC5oPgpAQCAt MTk1NCw2ICsxOTU3LDE1IEBAIGZpbGxfZGVmYXVsdF9vcHRpb25zKE9wdGlvbnMgKiBvcHRp b25zKQogewogCWNoYXIgKmFsbF9jaXBoZXIsICphbGxfbWFjLCAqYWxsX2tleCwgKmFsbF9r ZXk7CiAJaW50IHI7CisjaWZkZWYgVk1XQVJFX0dVRVNUX1dPUktBUk9VTkQKKwljaGFyIHNj dmFsWzddOwkvKiAidm13YXJlXDAiICovCisJc2l6ZV90IHNjc2l6ID0gc2l6ZW9mKHNjdmFs KTsKKwlpbnQgdm13Z3Vlc3QgPSAwOworCisJaWYgKHN5c2N0bGJ5bmFtZSgia2Vybi52bV9n dWVzdCIsIHNjdmFsLCAmc2NzaXosIE5VTEwsIDApID09IDAgJiYKKwkgICAgc3RyY21wKHNj dmFsLCAidm13YXJlIikgPT0gMCkKKwkJdm13Z3Vlc3QgPSAxOworI2VuZGlmCiAKIAlpZiAo b3B0aW9ucy0+Zm9yd2FyZF9hZ2VudCA9PSAtMSkKIAkJb3B0aW9ucy0+Zm9yd2FyZF9hZ2Vu dCA9IDA7CkBAIC0yMDg4LDggKzIxMDAsMTggQEAgZmlsbF9kZWZhdWx0X29wdGlvbnMoT3B0 aW9ucyAqIG9wdGlvbnMpCiAJaWYgKG9wdGlvbnMtPnZpc3VhbF9ob3N0X2tleSA9PSAtMSkK IAkJb3B0aW9ucy0+dmlzdWFsX2hvc3Rfa2V5ID0gMDsKIAlpZiAob3B0aW9ucy0+aXBfcW9z X2ludGVyYWN0aXZlID09IC0xKQorI2lmZGVmIFZNV0FSRV9HVUVTVF9XT1JLQVJPVU5ECisJ CWlmICh2bXdndWVzdCkKKwkJCW9wdGlvbnMtPmlwX3Fvc19pbnRlcmFjdGl2ZSA9IElQVE9T X0xPV0RFTEFZOworCQllbHNlCisjZW5kaWYKIAkJb3B0aW9ucy0+aXBfcW9zX2ludGVyYWN0 aXZlID0gSVBUT1NfRFNDUF9BRjIxOwogCWlmIChvcHRpb25zLT5pcF9xb3NfYnVsayA9PSAt MSkKKyNpZmRlZiBWTVdBUkVfR1VFU1RfV09SS0FST1VORAorCQlpZiAodm13Z3Vlc3QpCisJ CQlvcHRpb25zLT5pcF9xb3NfYnVsayA9IElQVE9TX1RIUk9VR0hQVVQ7CisJCWVsc2UKKyNl bmRpZgogCQlvcHRpb25zLT5pcF9xb3NfYnVsayA9IElQVE9TX0RTQ1BfQ1MxOwogCWlmIChv cHRpb25zLT5yZXF1ZXN0X3R0eSA9PSAtMSkKIAkJb3B0aW9ucy0+cmVxdWVzdF90dHkgPSBS RVFVRVNUX1RUWV9BVVRPOwpkaWZmIC0tZ2l0IGEvc2VjdXJlL3Vzci5iaW4vc3NoL01ha2Vm aWxlIGIvc2VjdXJlL3Vzci5iaW4vc3NoL01ha2VmaWxlCmluZGV4IDYxNGNjNzYyN2ZjNS4u MDIzZmE0YTU1YmU5IDEwMDY0NAotLS0gYS9zZWN1cmUvdXNyLmJpbi9zc2gvTWFrZWZpbGUK KysrIGIvc2VjdXJlL3Vzci5iaW4vc3NoL01ha2VmaWxlCkBAIC0zNyw2ICszNyw5IEBAIExJ QkFERCs9CWNyeXB0bwogQ0ZMQUdTKz0gLURYQVVUSF9QQVRIPVwiJHtMT0NBTEJBU0V9L2Jp bi94YXV0aFwiCiAuZW5kaWYKIAorIyBXb3JrYXJvdW5kIFZNd2FyZSBXb3Jrc3RhdGlvbiBO QVQgYnVnCitDRkxBR1MrPS1EVk1XQVJFX0dVRVNUX1dPUktBUk9VTkQKKwogLmluY2x1ZGUg PGJzZC5wcm9nLm1rPgogCiAuUEFUSDoJJHtTU0hESVJ9Cg== --------------B62CC6903F713B5198EED8DA-- --U4ybSsOLfMyrv5BMcnAylgrTt8f3Jn1iC-- --TqPqiUNwPUb4a2XM8oPk8mDB5mLAFV03B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlwdfVQACgkQk4vgf7Eq 4WwxUQf/cXDPiKQH/XMwnusDJ4QVJ8lN0Yzlz+oEmST55yOaCo+fgmS5orfVhpCS V0f00O/4QDcQV7Dci2/oVSlWpbk8JOKOfucJZy/G4u5tQZexd8XS1sfvZvjbKPeX 0+Xb5/AeZLAmaZsqq+TElEvM/j8CUgd8ERqKTZJdsOLgnOu6rVhmjlw/IVkwyBUK GPe8F0CqEFoQlCpF1KX2Viuo/Nrmnt1lizQZDrNK7KeML664SxEpk3Y4tW4HaEg+ Bo6OHBrnA1sO68bruOTNXWxp7CuGetLS8aj24BYXPh2ADCdvcLC7jRPSbhWSS/9X biaBChL01Mpu+RlWJiBsHqan7w2rRg== =M0Di -----END PGP SIGNATURE----- --TqPqiUNwPUb4a2XM8oPk8mDB5mLAFV03B-- From owner-freebsd-current@freebsd.org Sat Dec 22 00:09:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 802261338952 for ; Sat, 22 Dec 2018 00:09:01 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C19858A5AB for ; Sat, 22 Dec 2018 00:09:00 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 850F11338947; Sat, 22 Dec 2018 00:09:00 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62AA21338946 for ; Sat, 22 Dec 2018 00:09:00 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D45028A5A7; Sat, 22 Dec 2018 00:08:59 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pg1-x533.google.com with SMTP id v28so3166954pgk.10; Fri, 21 Dec 2018 16:08:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=0Kzl8BSfv1IJxTXQgRP7KQTE7mRW7HKGs/fbdZbMmDQ=; b=BVvj4M/pG2pWjWieC5stbf8V7aB6w+21D9PF860J26vF21sb2pF453HEhc3aiaKGFM RAc3GB5X7wu5DKcFHl5wrmOVXrWF+mTIC3n1gV0oChTrCN9VPJ7jJrmnfboyyPn05xsd 2qqAZyhwlfl9pd1e/NJZbb7bV4Ok7vjKv9azUJQOQSIHUl0URj8DNDFioY8AqsElP8a2 LA+hnW4PuA2JHObSmj60N8TBQH9swXamCT5I/RhMOFN+WjBkmDeW1VrJSbpusMmApBvB hPnLQmRLzC+7rhm0zWLA5rElaQQCXVSzie/5QgAiyGcj2ckWOlOq4gpKH66wMvnw0XYT q9+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=0Kzl8BSfv1IJxTXQgRP7KQTE7mRW7HKGs/fbdZbMmDQ=; b=feF/ZcqYupycR+LEAwxkhHHoyDhIziFwhu6TI8WOeE8h98isWjltpqfIF7PaoThmxP D02NH9DgtEmIYSMpjAKnkdEmQ0IvjUYMD33BaBAl/e9PwSVLPHo/2XZW83Usrltuil2+ VPWZyYiAE/hsOmO+lxZICmy+KlrToFlRMrgVs7Qy60qZ6hJwu+X+UJoeCB1ZNVkt4nbi SQSdlG0HI7RweoW9gr9QkY0o2HcmFXeu6yqF5RN9S8xrQPLfKk0lGt8wXBcDmhhK23jU 3lh0AgTtwoPbKcclcIBd/6oKqTcy5I/H9qMbARGc3taWnunzeRJVbqYqMNqeEADQrGNc VW+A== X-Gm-Message-State: AA+aEWa4DpxLnCJVF0hdTsjdzNjyMrQzGB/LO8MjDK6wKUsy+/einwpH IEz/ZHGoR3gtLlkmKM/u1Xl/J28N X-Google-Smtp-Source: AFSGD/WPLwgoKAiqI7ER4CSY5yHSgQcxQTWsCzK8Ovk+X17KDUNfhzL32jB1NGJCJRtuizDMZECFPA== X-Received: by 2002:a62:5793:: with SMTP id i19mr4595806pfj.49.1545437338623; Fri, 21 Dec 2018 16:08:58 -0800 (PST) Received: from [192.168.20.7] (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id q1sm39802138pgs.14.2018.12.21.16.08.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Dec 2018 16:08:57 -0800 (PST) From: Enji Cooper Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_42AD2EBD-6602-4ECA-BDC0-657B6AEBD7F4"; protocol="application/pgp-signature"; micalg=pgp-sha256 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes Date: Fri, 21 Dec 2018 16:08:56 -0800 In-Reply-To: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> Cc: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= , freebsd-current , mp@FreeBSD.org To: Yuri Pankov References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> X-Mailer: Apple Mail (2.3445.9.1) X-Rspamd-Queue-Id: D45028A5A7 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.980,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 00:09:01 -0000 --Apple-Mail=_42AD2EBD-6602-4ECA-BDC0-657B6AEBD7F4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: >=20 > Hi, >=20 > There's apparently a bug in VMware Workstation NAT implementation, = made > visible by the change to default values of IPQoS in OpenSSH 7.8p1, > making all ssh connections from the guest behind the NAT to fail with > obscure "Fssh_packet_write_wait: Connection to 192.168.1.53 port 22: > Broken pipe". >=20 > I wonder if we could integrate the attached patch (or some smarter > version of it) for the time being as the bug affects several major WS > releases, and it's not immediately clear where the problem is. >=20 > The change itself: >=20 > = https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/readconf.c#rev1.= 284 >=20 > The bug reports (some of them): >=20 > https://bugzilla.redhat.com/show_bug.cgi?id=3D1624437 > https://communities.vmware.com/message/2803219#2803219 >=20 > The patch itself is attached. > Cool=E2=80=A6 yeah=E2=80=A6 I=E2=80=99ve been running into this = issue for a while with VMware Fusion 11.0.1. I CCed mp@ for visibility. Thanks! -Enji --Apple-Mail=_42AD2EBD-6602-4ECA-BDC0-657B6AEBD7F4 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE5bk3FaGcY5rvqmb79YOpJmkwhhUFAlwdgJgACgkQ9YOpJmkw hhV/jBAAxEc0gyJsEFGNyyWA1mcCLVP+VFmQbHSq8OmrRzkd5hIY3sgq2nH2Bc5Z W4JO2JYe3yVREixLz5NIpDr0q0K7udo+uBnhGnY/9ZTKaI6h2sUZgSEaQbJu3jZz QGqdW/XV8as8dFKibe/LO1UnECLpW7wnI3zALO3AW8hMMQfKvO8BabEvXmOUQUys 2w7u232HIknSyq8qfs+m9e6kTvuTQPjts7KIMfolYF4LV176e5XIi/wMfHzYgtyf RdZEsp9+veq/FSgNS0Gn8yl2biiragF3XfIVV5+orHZK0jt9x7eQBSAWJeXaxN6U IJEM0TvIhNHeDND+J3gJax+MBLSuWW0frygz+uLC19Omur4/WcIisbyDe5CplShC da3n/EyC0rt7uXRwLT3JHn86wJosExOZ36Q/V4IHtqf64YjslW6YuREM5QsWDMLd TVM95ob5RPio7gaMwdABxNiU1nHjo/cAnAAKFWPN7HRZYJHOPsUpeFIUEVD6CeCW upUqvuV9M1KbZzhHxcLGulo7y057nxCc6CITUErMSPbHMKaBldYnhk9Ax2A+z6SV YWaWv03kSqa3hG7CB6DLX0DNy06HnxvODdEaYpT4bpQPJB/vZHkaRS8bRtaDUrk+ gkMPpWoRefXMit6XQPXA8daHc3lIK6KP5nCAq9IH9hCJl5AKA70= =9U6K -----END PGP SIGNATURE----- --Apple-Mail=_42AD2EBD-6602-4ECA-BDC0-657B6AEBD7F4-- From owner-freebsd-current@freebsd.org Sat Dec 22 00:19:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A87841339098 for ; Sat, 22 Dec 2018 00:19:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E03D68AC20 for ; Sat, 22 Dec 2018 00:19:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id A34041339097; Sat, 22 Dec 2018 00:19:18 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DE2B1339095 for ; Sat, 22 Dec 2018 00:19:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 13FD08AC1F for ; Sat, 22 Dec 2018 00:19:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x733.google.com with SMTP id q8so4181669qke.1 for ; Fri, 21 Dec 2018 16:19:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=85ZSFGYHhc7uaQFBfGYtHximzt6PCm48c/tJKulun/g=; b=gxwspBfEAPpwJmafO1yycIjVnLoAQRGnocKKeyepRaYiJyi7evBMybn26r7TTb2DKr FozGZxZugwjrKuPWQUIxRNu74D+GK3JW74x8zRwZPT6Th2KDb0T1s9qX+AuH1Z9GHbMv gzTJ9zB+0FhkYcBkTAYTakhIEaNEJvTb6d5+Z/5tu904czqmiKW5btMCRoQ9k/3MvoVl emEoA+390ZMD0ZN6YtdJcVifC5iRSq0HFSzpDe8I5oKPHzVT+DJOLhh3bof1jCFfpBBh gWMWzl+RoIHTmb9SyQ8yyIJzIqPjbSXhwwZHRH642TYe7uZ1hotZYKyOYgiI73PyiCzp K3YQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=85ZSFGYHhc7uaQFBfGYtHximzt6PCm48c/tJKulun/g=; b=DtC8snKvAMMD3vb2rLzV2cVszqwgvLCKJpl6OTmMy+RgAwKtZwYS2NvfMD0KU4VKcF MOVYJ+VimECqvrs/qdFFXo7C9+E9hgZTmax9PLHZOQKLru/1HcxMX17mFBF9cUXk5zEg nu/9/lLM7RwJtfojOfdz5BhNLgb2RLQCJf4xLj+e13+R8ImuE40tiBeWydw4DXvBX42K ug+0JCsEmKzTYIWrHhOIrti1xpkTSTFlAAwyGe98kXiImi2kvQcrxvFIM1Eni3dLqFRo 6dWpv6AF+J4V6VkviWritxLtF3jocz0m5Cf1SfJ6rQb2dtDaMwIkJHXEdLBx/aMJc2Of 3rJg== X-Gm-Message-State: AJcUukdCE1YjXSqQY3Uvu8PF7jo3inKTq5W+2Fcue6J3S3eo6E+pohKo SQucRoo5rSrTLsSRC/prp8nNCsxZWn1Wmd33tb5abQ== X-Google-Smtp-Source: ALg8bN6w9nnlHMDOj2NdpCbRFYKCOJVjxjOj1K6HbY0Yme5I1XA7rkXpm2gBPMgI+7NLnDV8gtiqoJPkzalfp3fjxlo= X-Received: by 2002:a37:c653:: with SMTP id b80mr4440752qkj.245.1545437957398; Fri, 21 Dec 2018 16:19:17 -0800 (PST) MIME-Version: 1.0 References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> In-Reply-To: From: Warner Losh Date: Fri, 21 Dec 2018 17:19:06 -0700 Message-ID: Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes To: Enji Cooper Cc: Yuri Pankov , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , freebsd-current , Mark Peek X-Rspamd-Queue-Id: 13FD08AC1F X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.95 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.95)[-0.953,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 00:19:20 -0000 I've been hit by this as well. At least two others on IRC have had the same issue. Warner On Fri, Dec 21, 2018 at 5:10 PM Enji Cooper wrote: > > > On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: > > > > Hi, > > > > There's apparently a bug in VMware Workstation NAT implementation, made > > visible by the change to default values of IPQoS in OpenSSH 7.8p1, > > making all ssh connections from the guest behind the NAT to fail with > > obscure "Fssh_packet_write_wait: Connection to 192.168.1.53 port 22: > > Broken pipe". > > > > I wonder if we could integrate the attached patch (or some smarter > > version of it) for the time being as the bug affects several major WS > > releases, and it's not immediately clear where the problem is. > > > > The change itself: > > > > > https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/readconf.c#rev1= .284 > > > > The bug reports (some of them): > > > > https://bugzilla.redhat.com/show_bug.cgi?id=3D1624437 > > https://communities.vmware.com/message/2803219#2803219 > > > > The patch itself is attached. > > > > Cool=E2=80=A6 yeah=E2=80=A6 I=E2=80=99ve been running into this i= ssue for a while with > VMware Fusion 11.0.1. > I CCed mp@ for visibility. > Thanks! > -Enji > From owner-freebsd-current@freebsd.org Sat Dec 22 01:47:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA48C133CF26 for ; Sat, 22 Dec 2018 01:47:15 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8299C8EC6B for ; Sat, 22 Dec 2018 01:47:15 +0000 (UTC) (envelope-from mp@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 46329133CF25; Sat, 22 Dec 2018 01:47:15 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21205133CF23 for ; Sat, 22 Dec 2018 01:47:15 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B74178EC64 for ; Sat, 22 Dec 2018 01:47:14 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from mail-yb1-f170.google.com (mail-yb1-f170.google.com [209.85.219.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mp) by smtp.freebsd.org (Postfix) with ESMTPSA id 8FDE51AA10 for ; Sat, 22 Dec 2018 01:47:14 +0000 (UTC) (envelope-from mp@freebsd.org) Received: by mail-yb1-f170.google.com with SMTP id d187so2877458ybb.5 for ; Fri, 21 Dec 2018 17:47:14 -0800 (PST) X-Gm-Message-State: AJcUukfIKCSvS7xbaLG4Go/oTshet1lpFlElEXwO4P/YwAQSG3vZiHl+ CySsgDrpqcMgp/lrFdS7dDCPT4A1aIb2wIiDShjAQg== X-Google-Smtp-Source: AFSGD/XqUw2KbWeKsGTiXiXJoBxZmZ7gq+j1VCYmtpjcFnkEuBOlNLvFR7Aq4B0+WXKpQ55uWg4heLKnK75OWk7IPTU= X-Received: by 2002:a25:1e44:: with SMTP id e65mr5016148ybe.429.1545443233784; Fri, 21 Dec 2018 17:47:13 -0800 (PST) MIME-Version: 1.0 References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> In-Reply-To: From: Mark Peek Date: Fri, 21 Dec 2018 17:47:02 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes To: Warner Losh Cc: Enji Cooper , Yuri Pankov , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , freebsd-current , Mark Peek X-Rspamd-Queue-Id: B74178EC64 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.994,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 01:47:16 -0000 Thanks for the cc:. I forwarded the original report on to an internal VMware desktop product contact. What version of Workstation or Fusion is this occurring on? I saw Workstation 14 mentioned but curious if it occurs on Workstation 15 (latest). Mark On Fri, Dec 21, 2018 at 4:19 PM Warner Losh wrote: > I've been hit by this as well. At least two others on IRC have had the > same issue. > > Warner > > On Fri, Dec 21, 2018 at 5:10 PM Enji Cooper wrote= : > >> >> > On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: >> > >> > Hi, >> > >> > There's apparently a bug in VMware Workstation NAT implementation, mad= e >> > visible by the change to default values of IPQoS in OpenSSH 7.8p1, >> > making all ssh connections from the guest behind the NAT to fail with >> > obscure "Fssh_packet_write_wait: Connection to 192.168.1.53 port 22: >> > Broken pipe". >> > >> > I wonder if we could integrate the attached patch (or some smarter >> > version of it) for the time being as the bug affects several major WS >> > releases, and it's not immediately clear where the problem is. >> > >> > The change itself: >> > >> > >> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/readconf.c#rev= 1.284 >> > >> > The bug reports (some of them): >> > >> > https://bugzilla.redhat.com/show_bug.cgi?id=3D1624437 >> > https://communities.vmware.com/message/2803219#2803219 >> > >> > The patch itself is attached. >> > >> >> Cool=E2=80=A6 yeah=E2=80=A6 I=E2=80=99ve been running into this = issue for a while with >> VMware Fusion 11.0.1. >> I CCed mp@ for visibility. >> Thanks! >> -Enji >> > From owner-freebsd-current@freebsd.org Sat Dec 22 01:48:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4866133D062 for ; Sat, 22 Dec 2018 01:48:58 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 05C268EE96 for ; Sat, 22 Dec 2018 01:48:58 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: by mailman.ysv.freebsd.org (Postfix) id BD5CE133D05D; Sat, 22 Dec 2018 01:48:57 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82709133D05B for ; Sat, 22 Dec 2018 01:48:57 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 166618EE91; Sat, 22 Dec 2018 01:48:57 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 617F420DE4; Fri, 21 Dec 2018 20:48:56 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 21 Dec 2018 20:48:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm3; bh=su2RQIYRY6GsgC4drMsqp3Pui2O Qil5r7mV9Z/5p4Hw=; b=jm7ZXEQJWjN9KvylevpxpzfEqaS9Q8RKaEGHQABD82a e0CnUChOYl6wbxYnp/hbUWUHnIdJ5ZC7QJvyjKzL7uc8kXvXUvfWvouz0qtszu5N 8j40cJLay1YQNAFJDo13kyOY2txcgobrIH/2CkfjQvVV4QrlrEcuWcItS2PwOies OzKmooePxJsykCVkbZTX0JEv0WJTxsbbwXhMiBawSdQMxHKTks77qxwYUEuqoZUf Rw4Or6eGaCMQxwJFbsSJ4ZQFg4M73Djybl7jL/ABTWpOBYHI7WL0DK5HBX/MkfcT zi2s6rP/ROVe+XSTAldGPAxViMHkDKCHXw9jk83gtrQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=su2RQI YRY6GsgC4drMsqp3Pui2OQil5r7mV9Z/5p4Hw=; b=cdtSK//KBbkRJhFZUYFnv6 hDq8KiU0OMzghxexWuN7IGOnYerWnYMchxC6CxJRM05aI089EmALT3N8qlJGCLwo ZFI/W1PWxPEireXiRLQjB8Jm2Z73sDWlJIrDaHMlDt2DefYcN6QUmhztBKJ2djR0 AE72eFx4EL/3RUUEvPDBefwAfnpAOLStwNGSimeOWveGO2O5lhJ5eHVA9Xgi9LEW AJXNoL0Iy0Ori6CgxBOlIiO8bbUMZZ31QfFxrhLoj7zyBXWOslgrB0E0ZWRaYR1v lvXTOQFfrGOPwJ1KPwq8FxfmjU/uHTTs8THSZuAMFxV5Kkb87ob4+4EP30qIdMyQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudejiedgfeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefuvfhfhffkff gfgggjtgesghdtrefotdefjeenucfhrhhomhepjghurhhiucfrrghnkhhovhcuoeihuhhr ihhpvheshihurhhiphhvrdhnvghtqeenucffohhmrghinheprhgvughhrghtrdgtohhmpd hfrhgvvggsshgurdhorhhgpdhvmhifrghrvgdrtghomhdpohhpvghnsghsugdrohhrghen ucfkphepleegrddvfeefrddvfedurdduleehnecurfgrrhgrmhepmhgrihhlfhhrohhmpe ihuhhrihhpvheshihurhhiphhvrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from [192.168.1.2] (unknown [94.233.231.195]) by mail.messagingengine.com (Postfix) with ESMTPA id 9EF5FE40E1; Fri, 21 Dec 2018 20:48:54 -0500 (EST) Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes To: Mark Peek , Warner Losh Cc: Enji Cooper , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> From: Yuri Pankov Openpgp: preference=signencrypt Autocrypt: addr=yuripv@yuripv.net; keydata= mQENBFu8u6IBCADB11gP0QwnorrHjqAtKLHKHNHskhy0s7jqJKfx0YqXgVBKGLJ9/mjLAz0F CBNvemHSDDTs0mEZ9cBKKi6cmsav6+UQgr//yai6hvXLBJqKchSFO4MhmdvBtsGFq1yKz5Zi uhjmimKyIpgBgvMdbgGbGq6cnSB2uEPmZuJr419SVRODOkXukU+F5WHgaHzDdHAIu1asCt2B +6msxqIqlFWcXyZyTGicTGGvC/PFIsVRUtD1dIJANTC876g7DTb7LZXWiWwJpSJ4GKMXMHVX Ct9BoQ4i3nhKbOxb6Io1wsy+NFyWsTJ9KYrxKKPJP3oG8BWb/cqlFqnE4eNSsiq2q7krABEB AAG0H1l1cmkgUGFua292IDx5dXJpcHZAeXVyaXB2Lm5ldD6JAVQEEwEKAD4WIQT4arc+w94t Pi0v/3CTi+B/sSrhbAUCW7y7ogIbAwUJBaOagAULCQgHAwUVCgkICwUWAwIBAAIeAQIXgAAK CRCTi+B/sSrhbJ+ACACqOlkjZ+iP8K8hcwz/G6+c1lVkhuMWL+hxFeE149QuJAXQvkOj/UXO 7jY9HSqFbOYYY44/hujpQCu+/u2dsJ5MAA7TJspWK2zUxtFAzgDp1fRXmCvMlFLdI0yVkKOB JaK+HQP8rBT6yHzGw1KJ6VyOXuuD0Kx02Ou61qjG9/vPRR0jtaxog0rKxpf+yf0UvSM4vb7+ LdY2GQxgfcLcJ8hThR4ElWJAkDsG4CiXixGJuFJ+9dpMK6LHmP6M+NxV4NkzpNddn3Eii8XQ y5spxcLszp8csFBDtAC6BI9sHLhJ9Va1VKpuvSlDsBv4ZtsjnUCIaOiF5MDTYkddSPGGMBck uQENBFu8u6IBCADKih3Q933rDNj4ZA8FhBQ2RlmBgvwOLcDPIL3h0V7h38y3+HisgFScXACD sdrTlYZ1bRXkD9FHENynBcv0l/3uGJDk8jaGIDE0TP8OQBRp+IaU9/BHnAqrKxTJGIolDahy 2m+yx2yhdc6B4ujWMDqCF1rWOD+ymOWw+VLllOkrHcZa5PJtX9UOGbApZl8ZTM8El4CANN8F 1bg9MWzUi+8LYoGWGc+BwsFS1OUB1c4SPgMu5fD4Wfsr9yRl06fdpEA2YT7B/j5/5RSC0sE2 Zs/tmJ/JRflHJ12ycj59ma2xQMfEJF40hZDpMFQmZvbVqgEg3ocQcltjbxlIKZ/mjC4zABEB AAGJATwEGAEKACYWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW7y7ogIbDAUJBaOagAAKCRCT i+B/sSrhbIDcCACqAZMcoxUBLZa40a5b24j5i1jplvCYYb3h+Q5lt5+BFJ87kCb4dJuUD3kh 2i29BrxWQWa9WNue9ozxeYkbkfXubQYXexVolRsnh64OdGsE8KvorBFBB3zdK/GRt2Jy+jsn TfUWuQllbzMP0MfhCDMk1Mo8WvDH2/cOEP/yLKf20a+cd6nLs7bidjmGXo9pyuBKAtV6Kv+V Ru54AL+A/UBYu/eB3Dtvzcnut+1Zq6KaP++kUwPwINLIk04OBDwN0zRNTiqMAFYYyz2vZHBB 6E1th/l//ZC5b9Dk0ZpFI1bYdL9ymnrZe1MqbGPnDCToQxu00T/pZCm6Z92YrZQYuNwl Message-ID: <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> Date: Sat, 22 Dec 2018 04:48:52 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="QYp3HdA8zinltL3bHmIcwg20icgjpwHRF" X-Rspamd-Queue-Id: 166618EE91 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.987,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 01:48:59 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QYp3HdA8zinltL3bHmIcwg20icgjpwHRF Content-Type: multipart/mixed; boundary="NfZ2hlmNftE9B5ygJDqb0sdLbZFyWHUFW"; protected-headers="v1" From: Yuri Pankov To: Mark Peek , Warner Losh Cc: Enji Cooper , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current Message-ID: <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> In-Reply-To: --NfZ2hlmNftE9B5ygJDqb0sdLbZFyWHUFW Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Mark Peek wrote: > Thanks for the cc:. I forwarded the original report on to an internal > VMware desktop product contact. Thank you. > What version of Workstation or Fusion is this occurring on? I saw > Workstation 14 mentioned but curious if it occurs on Workstation 15 > (latest). Running the latest available for download: 15.0.2 build-10952284. > On Fri, Dec 21, 2018 at 4:19 PM Warner Losh wrote: >=20 >> I've been hit by this as well. At least two others on IRC have had the= >> same issue. >> >> Warner >> >> On Fri, Dec 21, 2018 at 5:10 PM Enji Cooper wr= ote: >> >>> >>>> On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: >>>> >>>> Hi, >>>> >>>> There's apparently a bug in VMware Workstation NAT implementation, m= ade >>>> visible by the change to default values of IPQoS in OpenSSH 7.8p1, >>>> making all ssh connections from the guest behind the NAT to fail wit= h >>>> obscure "Fssh_packet_write_wait: Connection to 192.168.1.53 port 22:= >>>> Broken pipe". >>>> >>>> I wonder if we could integrate the attached patch (or some smarter >>>> version of it) for the time being as the bug affects several major W= S >>>> releases, and it's not immediately clear where the problem is. >>>> >>>> The change itself: >>>> >>>> >>> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/readconf.c#= rev1.284 >>>> >>>> The bug reports (some of them): >>>> >>>> https://bugzilla.redhat.com/show_bug.cgi?id=3D1624437 >>>> https://communities.vmware.com/message/2803219#2803219 >>>> >>>> The patch itself is attached. >>>> >>> >>> Cool=E2=80=A6 yeah=E2=80=A6 I=E2=80=99ve been running into th= is issue for a while with >>> VMware Fusion 11.0.1. >>> I CCed mp@ for visibility. >>> Thanks! >>> -Enji >>> >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 --NfZ2hlmNftE9B5ygJDqb0sdLbZFyWHUFW-- --QYp3HdA8zinltL3bHmIcwg20icgjpwHRF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlwdmAQACgkQk4vgf7Eq 4WyXRQf9EMyyfVPi+62HBu/mz7PKaBouwlIz0pfQ5NCKv7NO5pLKFi4JENCa/eEx w3flNQ9DrAny3YJgsh0NyYlsQVWoslGIvi06m3cGK9rlj+F/cylu7HyUEmgvnVTU tIJ+LcDoSZezc/VzaFGp6PqvHtAjJYoAUNe3NJCwHUYa7m8SxlEk89A7qL+aqLaM zx3mV9eEsK6MPkqvihwnC0YiuFmwuogY0lW3H1bO7kggDLjXN5ERuS74LcqwGsgO Gf11mx20bqqQ4Z9I2yikyJv3omr2TD6jP+eNSbmiIQX1HKxC1POOFhxUFac25yTm s4JplkIz5vQeResRCSuDQ028g6b4Cg== =OHwd -----END PGP SIGNATURE----- --QYp3HdA8zinltL3bHmIcwg20icgjpwHRF-- From owner-freebsd-current@freebsd.org Sat Dec 22 03:14:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E59A5134113B for ; Sat, 22 Dec 2018 03:14:29 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic305-21.consmr.mail.gq1.yahoo.com (sonic305-21.consmr.mail.gq1.yahoo.com [98.137.64.84]) (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 5D4EC6C1E7 for ; Sat, 22 Dec 2018 03:14:28 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: OIu1edAVM1l2EmHwh_uwzwndmyvn96Hbw7uWDV4oxltWebE8TVh.iJVfRXiuzNn yBTW1ZtAyuPze7uBDHMLYWWT8iz6Owhy3jNUOgx22LQAZuoKLGa9UNQGG1u8b.FUTdYBfXfG8iAm uGbeZq7Xwl35Ygih3AwCIWJPnHnR5FLcVZZxd9c3PlhnfkDWm5Oddh9HxYr9ICSRHk0tYm8_J0IX ZVTP5CoNQ.j8IhEH.7NOAz7SqbNtZzoM4.OBcs6fsqiteh7JaA41qF26oW0dydvMkggO2wpcyF5T 6LxTPWXLPVVkrubA0NkTQxnobXjSq_n0f3y0yOLy9S1nZDtlk..3l8WvB6lcScnZYn_0nQfcWUOz jhFtAV4YqSQ6tqkDYWZ_A0B2TJKqn0xeRNXVa2Np.lq_Pqu2favs.sk2RblfeSX42ttJJa_baI8u Fb1SOI7iTA4ZiDGNjAzhARGkq757JwBJo7CyiN_iYaF_WEmobjqZGRK6FxCqwJpBjUXOu6sETLQT B4IXT_qdbX_7XT7gWVkLddz2WYndRz8e4JGuGFAo9vICYTRGHcAp4Y_LImqK3qfbDd_H9M0lD0fb WyuMXEIIzZrNrjg8_uhL6caYyU79VcJ3g4Luy_OnQVHDpzWf_2rWV0NhyEWH7r6LwuNW4u2W5f63 CLV8Hqog5gZx6g0YyauH9rOWimn5Sm1sydGOk16ntTc6Alg19.e7l5_5_P2pTCgZKB8Y22wP_En6 .DIZq6jgmfouarno15bh5sP3_rFILxLcOt4Q2GbrS25x2cgnE_kJcRgeCMh3rxmsx0CXbOJa5Ofe CNEOSHhHAbLSRuls9XLX19ByAjdY3uVJ5lx0k5Uclifbh_34VAvE5GoznLr3p35jY14w41DVfzNI SmRg4eL0YzaNokMuyOzCqwqMZN3ypS9BqQNEI_FFPBKT0YUO81JYaDpC1b7Hx1JY2jPkc6f50wrg qeh6vIBDDH3o.gDyKhPGNYokqXAUxKm2NS7fdo2HE33l_sE9NJPO6a14k9ZHGc9epiiwZ9kpjGTt _70R4sHME8VfYn4ZmUIbZTDwBW7FY2w_DGb2fz71eIYBDuh4LQfXJ_0u4Z3zyVD5ng7MqR2w9YF_ J Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.gq1.yahoo.com with HTTP; Sat, 22 Dec 2018 03:14:20 +0000 Received: from c-67-170-167-181.hsd1.or.comcast.net (EHLO [192.168.1.109]) ([67.170.167.181]) by smtp426.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID e0306e394260faa24df3cb8b88a66439; Sat, 22 Dec 2018 03:14:16 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: A reliable port cross-build failure (hangup) in my context (amd64->armv7 cross build, with native-tool speedup involved) Message-Id: Date: Fri, 21 Dec 2018 19:14:15 -0800 Cc: freebsd-arm , FreeBSD Toolchain , ports-list freebsd To: freebsd-emulation@freebsd.or, FreeBSD Current X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: 5D4EC6C1E7 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.76 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MV_CASE(0.50)[]; FREEMAIL_FROM(0.00)[yahoo.com]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[yahoo.com:+]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.47)[-0.471,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.997,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.21)[ipnet: 98.137.64.0/21(0.64), asn: 36647(0.51), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[84.64.137.98.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 03:14:30 -0000 I had been reporting intermittent hang-ups for my amd64->{aarch64,armv7} = port cross builds in another message sequence. But it turns out that one thing I = ran into has hung-up every time, the same way, for amd64->armv7 cross builds: multimedia/gstreamer1-qt@qt5 . So I extract the material here into a = separate report with some updated notes. A little context: I had built from ports head -r484783 before under = FreeBSD head -r340287 (as I remember the version). Back then it did not have this = problem that it now has under FreeBSD head -r341836 . One ports-specific change was to = force perl5.28 as the default instead of perl5.26 originally. In fact this is what = drives what is being rebuilt for my experiment that caught this. But I doubt the perl = version is important to the problem. The context has a Ryzen Threadripper 1950X and = has been tested both for FreeBSD under Hyper-V and for the same media = native-booted. Both hang-up at the same point as seen via ps or top. The native tools for = cross-build speedup were in use. Cross-builds targeting aarch64 did not get this = problem but targeting armv7 did. 121 of 129 armv7 ports built before the hang-up for = the first armv7 try. The hang-up: In the port rebuilds targeting armv7, multimedia/gstreamer1-qt@qt5 = hung-up and timed out. Looking during the wait in later tries shows something much like = (from one of the examples): root 33719 0.0 0.0 12920 3528 0 I 11:40 0:00.03 | = | `-- sh: poudriere[FBSDFSSDjailArmV7-default][02]: build_pkg = (gstreamer1-qt5-1.2.0_14) (sh) root 41551 0.0 0.0 12920 3520 0 I 11:43 0:00.00 | = | `-- sh: poudriere[FBSDFSSDjailArmV7-default][02]: = build_pkg (gstreamer1-qt5-1.2.0_14) (sh) root 41552 0.0 0.0 10340 1744 0 IJ 11:43 0:00.01 | = | `-- /usr/bin/make -C /usr/ports/multimedia/gstreamer1-qt = FLAVOR=3Dqt5 build root 41566 0.0 0.0 10236 1796 0 IJ 11:43 0:00.00 | = | `-- /bin/sh -e -c (cd = /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build; if ! = /usr/bin/env QT_SELE root 41567 0.0 0.0 89976 12896 0 IJ 11:43 0:00.07 | = | `-- /usr/local/bin/qemu-arm-static ninja -j28 -v all root 41585 0.0 0.0 102848 25056 0 IJ 11:43 0:00.10 | = | |-- /usr/local/bin/qemu-arm-static = /usr/local/bin/cmake -E cmake_autogen /wrkdirs/usr/ports/multimedia/g root 41586 0.0 0.0 102852 25072 0 IJ 11:43 0:00.11 | = | `-- /usr/local/bin/qemu-arm-static = /usr/local/bin/cmake -E cmake_autogen /wrkdirs/usr/ports/multimedia/g or as top showed it: 41552 root 1 52 0 10M 1744K 0 wait 15 0:00 = 0.00% /usr/bin/make -C /usr/ports/multimedia/gstreamer1-qt FLAVOR=3Dqt5 = build 41566 root 1 52 0 10M 1796K 0 wait 1 0:00 = 0.00% /bin/sh -e -c (cd = /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build; if ! = /usr/bin/env QT_SELECT=3Dqt5 QMAKEMODULES 41567 root 2 52 0 88M 13M 0 select 4 0:00 = 0.00% /usr/local/bin/qemu-arm-static ninja -j28 -v all 41585 root 2 52 0 100M 24M 0 kqread 8 0:00 = 0.00% /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E = cmake_autogen /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/. 41586 root 2 52 0 100M 24M 0 kqread 22 0:00 = 0.00% /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E = cmake_autogen /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/. So: waiting in kqread trying to run cmake. Unlike some intermittent hang-ups, attaching-then-detaching via gdb does = not resume the hung-up processes. Kills of the processes waiting on kqread = stop the build. Given the prior ports have been built already, building just multimedia/gstreamer1-qt@qt5 still gets the hang-up at the same point. Building anything that requires multimedia/gstreamer1-qt@qt5 seems to be solidly blocked in my environment. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sat Dec 22 04:03:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99CBF134304E; Sat, 22 Dec 2018 04:03:53 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 652A36E2E7; Sat, 22 Dec 2018 04:03:50 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52C0CB.dip0.t-ipconnect.de [46.82.192.203]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id wBM43ZjW066184 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 22 Dec 2018 04:03:40 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id wBM43VkO077937; Sat, 22 Dec 2018 05:03:31 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id wBM430Oa099167; Sat, 22 Dec 2018 05:03:12 +0100 (CET) (envelope-from jhs@berklix.com) Message-Id: <201812220403.wBM430Oa099167@fire.js.berklix.net> To: Stefan Esser cc: Warner Losh , Ed Maste , Poul-Henning Kamp , FreeBSD Current , "Rodney W. Grimes" , ctm-users@freebsd.org Subject: Re: ctm(1) deprecation in the FreeBSD base system? From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Aachen Kent User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Tue, 23 Oct 2018 20:18:01 +0200." Date: Sat, 22 Dec 2018 05:03:00 +0100 X-Rspamd-Queue-Id: 652A36E2E7 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.13 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.22)[-0.224,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.82)[0.818,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[land.berklix.com,slim.berklix.com]; NEURAL_SPAM_LONG(0.56)[0.563,0]; RCPT_COUNT_SEVEN(0.00)[7]; R_SPF_NA(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[203.192.82.46.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:24940, ipnet:144.76.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.08)[ipnet: 144.76.0.0/16(2.91), asn: 24940(-2.49), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 04:03:53 -0000 > The port Makefile that I have prepared is attached below for reference. > Regards, STefan Thanks Stefan, I took current /usr/ports/misc/ctm/ & converted Stephen's & my diffs to be automatic ports patches: http://berklix.com/~jhs/src/bsd/fixes/freebsd/ports/gen/misc/ctm/files/ http://berklix.com/~jhs/src/bsd/fixes/freebsd/ports/gen/misc/ctm/README.JHS Stephens diffs are essential, without them CTM broke long ago, (5 digit numeric names maybe ?) I haven't checked all execution as my ctm_rmail scripts run automaticaly on an older release, not my current box, but this is running OK so far: ctm -q /pub/FreeBSD/development/CTM/svn-cur/svn-cur.07000xEmpty.xz ; ctm -q /pub/FreeBSD/development/CTM/svn-cur/svn-cur.07[0-9][0-9][0-9].xz Stephen may be best person to test delta builds, as hes the delta originator. Soonish I'll set up a [freebsd-]ctm-src-12 on http://mailman.berklix.org/mailman/listinfo if Stephens' & my requests to postmaster @ & mailman @ freebsd.org continues to get no response. Cheers, Julian -- Julian Stacey, Computer Consultant Sys.Eng. BSD Linux Unix, Munich Aachen Kent First referendum stole 700,000 votes from Brits in EU; 3,700,000 globaly. Lies criminal funded; jobs pound & markets down. 1.9M new voters 1.3M dead. Email MP: "A new referendum will buy UK & EU more time (Art 50.3), to avoid a hard crash, & consider all options." http://berklix.org/brexit/#mp From owner-freebsd-current@freebsd.org Sat Dec 22 05:30:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0D5113457F9 for ; Sat, 22 Dec 2018 05:30:42 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1F8A170D02 for ; Sat, 22 Dec 2018 05:30:42 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id D715713456CC; Sat, 22 Dec 2018 05:30:41 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4A0F13456CB for ; Sat, 22 Dec 2018 05:30:41 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E24970CFE; Sat, 22 Dec 2018 05:30:41 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pf1-x435.google.com with SMTP id b85so3539410pfc.3; Fri, 21 Dec 2018 21:30:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MNPs8L9afKYvv9ohmqVAdFvk2w56GG8a3nvGjqjXErQ=; b=XKlX8fIl4h8jS37Yz8ai1Ysp28WqFg2whm5VLje1fpwYCE03TyKCx/l7GDnxy59QD5 Yg6ncJbAHFfalkB+OCEm6ujf3YigPjbCPMhqD+JRKesSQ2C+N9H8NJapp7rYDtrpruFM 8c5m/F3d0ii4NGBWFuworxYL+UwU/tyjxwGa0OGDElwoDhCQ6FlvzKIefzOJpeRhhZjN EVqENv6OFU6GWLoLKVbpP43AmbjG7v90ch7BNqtigfrjaEbbcHLQ/9k1IWpRGtnD1O2t oGuDHKSk5R5n4FqGZpL2MCvzd1mtbI+0yfMhYjm1Nx2jaOrUYgvE+EwSmPShnNc0KQll WEPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MNPs8L9afKYvv9ohmqVAdFvk2w56GG8a3nvGjqjXErQ=; b=FMjlR2psoUrQ8p1KgzkInEaFFtTiJ2N/EbTLYU1AXZi9kg6/2Ww4s1k3wiNbxkU9qo q7hcCEts7HAc7cd7cblpBtH3bf87foffYEuZ/Bsk8wT9zQQbijjiIRWunl4r3W6rGFYR ulKa6jj1R/LUDiLmEJhpRlHk1VRzYlEg6VRWOPyq57aoRkDpV9QhZCX7CH2JLb62yk7V t8PYaPsHuAUf1KNksdoS8Gii5Gry3CNwgJUX6i32YeCgVkGPBmNGFwcem6iXXwGxU/N1 n11K1UJbfzGaIy/BzSBLal/LlElne+9TJr7AB0dTJKw+vpU0gn47oVNYu47PdY7/wBMI MEww== X-Gm-Message-State: AJcUukeMEKajP7v/YSvc22oimmAA3fiEuUK1wG7Bf5fghXzGAE+Mq2NV hzNX9nXZKwKr/OJvA03EgT3GTCFL X-Google-Smtp-Source: ALg8bN6fUQHYFz/bB89ZyifIcJyRS09OqtFEJ+RDwsz5eiV9wHb/WaoEfuwJ1FLu1ogIP1Cb70l30g== X-Received: by 2002:a63:314d:: with SMTP id x74mr5048109pgx.10.1545456639774; Fri, 21 Dec 2018 21:30:39 -0800 (PST) Received: from ?IPv6:2607:fb90:8165:4611:bd73:feec:ae0c:66a7? ([2607:fb90:8165:4611:bd73:feec:ae0c:66a7]) by smtp.gmail.com with ESMTPSA id v9sm36012888pfg.144.2018.12.21.21.30.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Dec 2018 21:30:39 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes From: Enji Cooper X-Mailer: iPhone Mail (16C101) In-Reply-To: <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> Date: Fri, 21 Dec 2018 21:30:37 -0800 Cc: Mark Peek , Warner Losh , =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= , freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: <980AA7F3-A447-45DC-A538-8EA89515F7DF@gmail.com> References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> To: Yuri Pankov X-Rspamd-Queue-Id: 2E24970CFE X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.87 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.87)[-0.871,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 05:30:43 -0000 > On Dec 21, 2018, at 17:48, Yuri Pankov wrote: >=20 > Mark Peek wrote: >> Thanks for the cc:. I forwarded the original report on to an internal >> VMware desktop product contact. >=20 > Thank you. >=20 >> What version of Workstation or Fusion is this occurring on? I saw >> Workstation 14 mentioned but curious if it occurs on Workstation 15 >> (latest). >=20 > Running the latest available for download: 15.0.2 build-10952284. This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it wasn=E2=80=99= t affecting me on 10.x. I didn=E2=80=99t install 11.0.0, so I don=E2=80=99t k= now if it affects that version... Thanks so much! -Enji= From owner-freebsd-current@freebsd.org Sat Dec 22 08:10:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FF26134A13A for ; Sat, 22 Dec 2018 08:10:25 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic311-13.consmr.mail.bf2.yahoo.com (sonic311-13.consmr.mail.bf2.yahoo.com [74.6.131.123]) (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 98B7D7600B for ; Sat, 22 Dec 2018 08:10:23 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 00_AYygVM1n.r2zTFDBgo6Qzlb4DEIcbm8wNIaXGaa6wIEMnhhdRmLY4F3kS2OV qucmF_2nks3QmCbDQwCUZrJl3ox3uFLsjAUf3O4_KwUsDFFL94eytyvrHlsHbZApWxlTDOWzw5ad wxSn9mTIpZgLTd5NutDqnrPaI.PYiRQmorshO.CMUdSkS3CU0h_axUIQ47mTEWCE8uLx6M0FeG6W hyC4nCG5YuIgPTvyWN30qygMZexqb7ph8eljqjUk4vNAvAr1_BQiZDMZbWVzbUAzJZfizu52t423 DekEJ3fUaA3ixYlvKbyy2FvCrKH0wQbODk6y8yJTYg1LajCnOa3FUuxPx_5wMG2xkUsBc5qOyFVc hJUUQs9Z8NH_UqBFABGqmkGwCdDGVV_S5Rw08xg1Dfi287XstrKq2dROUJLLDtPNAgXjz1GO8.G_ 0fegxANvPS6hUCd3NrBvrJhD3ArH5lI5OC2TLBimEeBdfLPHZ0OiXoZ.LxhR.dUx67H5SUrtKsBj hCFWc5WaPX53NaKkVRnUEULs5FzXu57RWLQxPykjfF24SHjDvqYI4oiTvnP6MXLM9udO7PJTpR6R p0hw4LeM40A0GzlO7xMgJF5ZMj_EiKe3rM2BRpff6zJYHFRaD8et7a0o1W2doKQTc5pAqxj0nAv0 VBcNQ59ZRMJxdVbug23O_vYk7FC6eWehie9S5wERNS7Qi2AJ5ri4FHtnMMSTikYSsk3smWh3Iv8_ ljWJ9OZGal74mFFcBeh8XbV4AAxlhZKI2VvhIX_THdwWgqDOn.ZP8gyKCHs8_1Gawlc6SZl7pYSx ecWFpKDpY1G5dH3nsz5_Rmh20MKfso6Vbco.MZBc4I_E3ZIrfqWo0A8xvPhbECAtkD8MrYzbTjSw CjP55jwJ_l7J.kAFdzB_.FZwpUhuktWTkYLQVu3wLr1UwC43ZJWqpo2fDr5sF06st1fqoCAN5Cmy gCynnEA5rwTer6mWI3osko1R2ERotO9K_g3T.J.ztHLKsyj8wIjfYz8C7qYi4J6dEQesHd76SiSr CBfKRhcDnHeSCffcUMyLkqjL.7rSpIFlkqzX7YfbkKq4VKqmXuorJYP350E75hEZzntLupdNXOtL Mv5MWjw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.bf2.yahoo.com with HTTP; Sat, 22 Dec 2018 08:10:16 +0000 Received: from c-67-170-167-181.hsd1.or.comcast.net (EHLO [192.168.1.109]) ([67.170.167.181]) by smtp403.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID bdc0811dc73c0818dc840b939212d3b0; Sat, 22 Dec 2018 08:10:13 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: A reliable port cross-build failure (hangup) in my context (amd64->armv7 cross build, with native-tool speedup involved) From: Mark Millard In-Reply-To: Date: Sat, 22 Dec 2018 00:10:11 -0800 Cc: freebsd-arm , FreeBSD Toolchain Content-Transfer-Encoding: quoted-printable Message-Id: <865A13C8-9749-486E-9F79-5EEDDECBE621@yahoo.com> References: To: freebsd-emulation@freebsd.org, FreeBSD Current , ports-list freebsd X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: 98B7D7600B X-Spamd-Bar: + X-Spamd-Result: default: False [1.47 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MV_CASE(0.50)[]; FREEMAIL_FROM(0.00)[yahoo.com]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[yahoo.com:+]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:26101, ipnet:74.6.128.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.22)[-0.220,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.99)[0.993,0]; NEURAL_HAM_LONG(-0.38)[-0.382,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(1.59)[ip: (5.08), ipnet: 74.6.128.0/21(1.64), asn: 26101(1.31), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[123.131.6.74.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 08:10:25 -0000 [I messed up the freebsd-emulation email address the first time I sent this. I also forgot to indicate the qemu-user-static vintage = relationship.] I had been reporting intermittent hang-ups for my amd64->{aarch64,armv7} = port cross builds in another message sequence. But it turns out that one thing I = ran into has hung-up every time, the same way, for amd64->armv7 cross builds: multimedia/gstreamer1-qt@qt5 . So I extract the material here into a = separate report with some updated notes. A little context: I had built from ports head -r484783 before under = FreeBSD head -r340287 (as I remember the version). Back then it did not have this = problem that it now has under FreeBSD head -r341836 . One ports-specific change was to = force perl5.28 as the default instead of perl5.26 originally. In fact this is what = drives what is being rebuilt for my experiment that caught this. But I doubt the perl = version is important to the problem. The context has a Ryzen Threadripper 1950X and = has been tested both for FreeBSD under Hyper-V and for the same media = native-booted. Both hang-up at the same point as seen via ps or top. The native tools for = cross-build speedup were in use. Cross-builds targeting aarch64 did not get this = problem but targeting armv7 did. 121 of 129 armv7 ports built before the hang-up for = the first armv7 try. ADDED: The qemu-user-static back with head -r340287 before installing = the updated ports would likely be different than the -r484783 vintage. So = both FreeBSD and qemu-user-static may have changed over the comparison. The hang-up: In the port rebuilds targeting armv7, multimedia/gstreamer1-qt@qt5 = hung-up and timed out. Looking during the wait in later tries shows something much like = (from one of the examples): root 33719 0.0 0.0 12920 3528 0 I 11:40 0:00.03 | = | `-- sh: poudriere[FBSDFSSDjailArmV7-default][02]: build_pkg = (gstreamer1-qt5-1.2.0_14) (sh) root 41551 0.0 0.0 12920 3520 0 I 11:43 0:00.00 | = | `-- sh: poudriere[FBSDFSSDjailArmV7-default][02]: = build_pkg (gstreamer1-qt5-1.2.0_14) (sh) root 41552 0.0 0.0 10340 1744 0 IJ 11:43 0:00.01 | = | `-- /usr/bin/make -C /usr/ports/multimedia/gstreamer1-qt = FLAVOR=3Dqt5 build root 41566 0.0 0.0 10236 1796 0 IJ 11:43 0:00.00 | = | `-- /bin/sh -e -c (cd = /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build; if ! = /usr/bin/env QT_SELE root 41567 0.0 0.0 89976 12896 0 IJ 11:43 0:00.07 | = | `-- /usr/local/bin/qemu-arm-static ninja -j28 -v all root 41585 0.0 0.0 102848 25056 0 IJ 11:43 0:00.10 | = | |-- /usr/local/bin/qemu-arm-static = /usr/local/bin/cmake -E cmake_autogen /wrkdirs/usr/ports/multimedia/g root 41586 0.0 0.0 102852 25072 0 IJ 11:43 0:00.11 | = | `-- /usr/local/bin/qemu-arm-static = /usr/local/bin/cmake -E cmake_autogen /wrkdirs/usr/ports/multimedia/g or as top showed it: 41552 root 1 52 0 10M 1744K 0 wait 15 0:00 = 0.00% /usr/bin/make -C /usr/ports/multimedia/gstreamer1-qt FLAVOR=3Dqt5 = build 41566 root 1 52 0 10M 1796K 0 wait 1 0:00 = 0.00% /bin/sh -e -c (cd = /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build; if ! = /usr/bin/env QT_SELECT=3Dqt5 QMAKEMODULES 41567 root 2 52 0 88M 13M 0 select 4 0:00 = 0.00% /usr/local/bin/qemu-arm-static ninja -j28 -v all 41585 root 2 52 0 100M 24M 0 kqread 8 0:00 = 0.00% /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E = cmake_autogen /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/. 41586 root 2 52 0 100M 24M 0 kqread 22 0:00 = 0.00% /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E = cmake_autogen /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/. So: waiting in kqread trying to run cmake. Unlike some intermittent hang-ups, attaching-then-detaching via gdb does = not resume the hung-up processes. Kills of the processes waiting on kqread = stop the build. Given the prior ports have been built already, building just multimedia/gstreamer1-qt@qt5 still gets the hang-up at the same point. Building anything that requires multimedia/gstreamer1-qt@qt5 seems to be solidly blocked in my environment. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sat Dec 22 17:50:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A91061359A95 for ; Sat, 22 Dec 2018 17:50:58 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4056C6A88F for ; Sat, 22 Dec 2018 17:50:58 +0000 (UTC) (envelope-from mp@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 03D321359A94; Sat, 22 Dec 2018 17:50:58 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D56351359A93 for ; Sat, 22 Dec 2018 17:50:57 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D7FC6A886 for ; Sat, 22 Dec 2018 17:50:57 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com [209.85.219.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mp) by smtp.freebsd.org (Postfix) with ESMTPSA id 408231522 for ; Sat, 22 Dec 2018 17:50:57 +0000 (UTC) (envelope-from mp@freebsd.org) Received: by mail-yb1-f176.google.com with SMTP id t16so1701214ybk.10 for ; Sat, 22 Dec 2018 09:50:57 -0800 (PST) X-Gm-Message-State: AA+aEWbC0AsREXBcn9lAJgGFMm23j+8mDeD45hJYI0huZShTOCQSVwrr Nfi8tzL5gRwa3IeMaiwGNRx7xKokpM7r2pRFVT5uGA== X-Google-Smtp-Source: AFSGD/Ub3hRLJslif0XzgUbVRR9xTvsyrtCggKid6VsWsLIW6OO4I+U0x3HghOKbaR7f+NoPz/Zj5NCuF5AwVVutvYk= X-Received: by 2002:a25:4b02:: with SMTP id y2mr7046342yba.387.1545501056748; Sat, 22 Dec 2018 09:50:56 -0800 (PST) MIME-Version: 1.0 References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> <980AA7F3-A447-45DC-A538-8EA89515F7DF@gmail.com> In-Reply-To: <980AA7F3-A447-45DC-A538-8EA89515F7DF@gmail.com> From: Mark Peek Date: Sat, 22 Dec 2018 09:50:45 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes To: Enji Cooper Cc: Yuri Pankov , Mark Peek , Warner Losh , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , freebsd-current X-Rspamd-Queue-Id: 7D7FC6A886 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.989,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 17:50:59 -0000 On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wrote: > > > On Dec 21, 2018, at 17:48, Yuri Pankov wrote: > > > > Mark Peek wrote: > >> Thanks for the cc:. I forwarded the original report on to an internal > >> VMware desktop product contact. > > > > Thank you. > > > >> What version of Workstation or Fusion is this occurring on? I saw > >> Workstation 14 mentioned but curious if it occurs on Workstation 15 > >> (latest). > > > > Running the latest available for download: 15.0.2 build-10952284. > > This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it wasn=E2=80= =99t > affecting me on 10.x. I didn=E2=80=99t install 11.0.0, so I don=E2=80=99t= know if it > affects that version... > > Thanks so much! > > -Enji BTW, there appears to be a workaround here using -o 'IPQoS=3Dthroughput' (untested by me). I've seen the issue forwarded internally but no further discussions yet. https://communities.vmware.com/thread/590825 Mark From owner-freebsd-current@freebsd.org Sat Dec 22 18:03:47 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAB2213350E1 for ; Sat, 22 Dec 2018 18:03:46 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 64E926B19D for ; Sat, 22 Dec 2018 18:03:45 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: by mailman.ysv.freebsd.org (Postfix) id 2296013350DE; Sat, 22 Dec 2018 18:03:45 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F420913350DC for ; Sat, 22 Dec 2018 18:03:44 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 7402E6B19A; Sat, 22 Dec 2018 18:03:44 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 1FA251181; Sat, 22 Dec 2018 13:03:42 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 22 Dec 2018 13:03:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm3; bh=NXUFQInvv1H4xTZb7bF89iMvv8x X6driEXNpKlOVVyA=; b=LQ4r/AwS9mVETIdYuIPHAG085vGlll76x9921c5sP2d b9yTmSgi3QD9ju/KWgnashG7xfhChYOoQaf/IhH6uL4euyBxOrhgX+utX9a6Yn+S toXo+qg9ZUWimpxzk2h5011D7t43xoKU+wfr1Fzv3uIK8xfCAX6Ihx4dNgqH/j8F 4tbRcx0dRcTKvQNm/7qkXINaexM1IxyA1PfleWMWM1W34XL6/jQbTT8oKZVAlNVv AUh24fS4+xJsb3LobO3zvk8QsCeHwbPs2QuhUvDDnWVr40eHfIaJmQ+2lkYdmbXg AVtyqCz29c4Fb9O/w1lnthgkULEVRMAXq3Z4iuVXAgA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=NXUFQI nvv1H4xTZb7bF89iMvv8xX6driEXNpKlOVVyA=; b=WJOy9KkUwzuaSAHpotdL7b tXu1wWGG9XVhn93DaQG7UCPelyhBJyBL7+y6TQgYANfVvcPC3W3gfAKjJVuglilc O/Dmu2NpncHQOQ+nYUW4eA62EfCzJW7PiesTu8KarWs8BtJYMov6BeLdDqTkW/+o aak6CC93/dodzmUo+tcO53teh0dXj5fDrNUcV+fBV+VQcV93R7+KpKDMy8hTJf0p CWRROH8g86QFp6n/RVW9zQVVbMy1LhGv0PJuucOv1QBGq7RIddAkJeF1cASS4aqu hkmznK8ZzHNFa0X5wyoAGGuz8jYjp29ylVY2nWcIfN9s6yjy/wk0CcPxXC93KvUQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudejjedguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecu fedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhkf fffgggjggtsehgtderofdtfeejnecuhfhrohhmpegjuhhrihcurfgrnhhkohhvuceohihu rhhiphhvseihuhhrihhpvhdrnhgvtheqnecuffhomhgrihhnpehvmhifrghrvgdrtghomh enucfkphepleegrddvfeefrddvfedurdduleehnecurfgrrhgrmhepmhgrihhlfhhrohhm peihuhhrihhpvheshihurhhiphhvrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from [192.168.1.2] (unknown [94.233.231.195]) by mail.messagingengine.com (Postfix) with ESMTPA id BE52510087; Sat, 22 Dec 2018 13:03:38 -0500 (EST) Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes To: Mark Peek , Enji Cooper Cc: Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> <980AA7F3-A447-45DC-A538-8EA89515F7DF@gmail.com> From: Yuri Pankov Openpgp: preference=signencrypt Autocrypt: addr=yuripv@yuripv.net; keydata= mQENBFu8u6IBCADB11gP0QwnorrHjqAtKLHKHNHskhy0s7jqJKfx0YqXgVBKGLJ9/mjLAz0F CBNvemHSDDTs0mEZ9cBKKi6cmsav6+UQgr//yai6hvXLBJqKchSFO4MhmdvBtsGFq1yKz5Zi uhjmimKyIpgBgvMdbgGbGq6cnSB2uEPmZuJr419SVRODOkXukU+F5WHgaHzDdHAIu1asCt2B +6msxqIqlFWcXyZyTGicTGGvC/PFIsVRUtD1dIJANTC876g7DTb7LZXWiWwJpSJ4GKMXMHVX Ct9BoQ4i3nhKbOxb6Io1wsy+NFyWsTJ9KYrxKKPJP3oG8BWb/cqlFqnE4eNSsiq2q7krABEB AAG0H1l1cmkgUGFua292IDx5dXJpcHZAeXVyaXB2Lm5ldD6JAVQEEwEKAD4WIQT4arc+w94t Pi0v/3CTi+B/sSrhbAUCW7y7ogIbAwUJBaOagAULCQgHAwUVCgkICwUWAwIBAAIeAQIXgAAK CRCTi+B/sSrhbJ+ACACqOlkjZ+iP8K8hcwz/G6+c1lVkhuMWL+hxFeE149QuJAXQvkOj/UXO 7jY9HSqFbOYYY44/hujpQCu+/u2dsJ5MAA7TJspWK2zUxtFAzgDp1fRXmCvMlFLdI0yVkKOB JaK+HQP8rBT6yHzGw1KJ6VyOXuuD0Kx02Ou61qjG9/vPRR0jtaxog0rKxpf+yf0UvSM4vb7+ LdY2GQxgfcLcJ8hThR4ElWJAkDsG4CiXixGJuFJ+9dpMK6LHmP6M+NxV4NkzpNddn3Eii8XQ y5spxcLszp8csFBDtAC6BI9sHLhJ9Va1VKpuvSlDsBv4ZtsjnUCIaOiF5MDTYkddSPGGMBck uQENBFu8u6IBCADKih3Q933rDNj4ZA8FhBQ2RlmBgvwOLcDPIL3h0V7h38y3+HisgFScXACD sdrTlYZ1bRXkD9FHENynBcv0l/3uGJDk8jaGIDE0TP8OQBRp+IaU9/BHnAqrKxTJGIolDahy 2m+yx2yhdc6B4ujWMDqCF1rWOD+ymOWw+VLllOkrHcZa5PJtX9UOGbApZl8ZTM8El4CANN8F 1bg9MWzUi+8LYoGWGc+BwsFS1OUB1c4SPgMu5fD4Wfsr9yRl06fdpEA2YT7B/j5/5RSC0sE2 Zs/tmJ/JRflHJ12ycj59ma2xQMfEJF40hZDpMFQmZvbVqgEg3ocQcltjbxlIKZ/mjC4zABEB AAGJATwEGAEKACYWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW7y7ogIbDAUJBaOagAAKCRCT i+B/sSrhbIDcCACqAZMcoxUBLZa40a5b24j5i1jplvCYYb3h+Q5lt5+BFJ87kCb4dJuUD3kh 2i29BrxWQWa9WNue9ozxeYkbkfXubQYXexVolRsnh64OdGsE8KvorBFBB3zdK/GRt2Jy+jsn TfUWuQllbzMP0MfhCDMk1Mo8WvDH2/cOEP/yLKf20a+cd6nLs7bidjmGXo9pyuBKAtV6Kv+V Ru54AL+A/UBYu/eB3Dtvzcnut+1Zq6KaP++kUwPwINLIk04OBDwN0zRNTiqMAFYYyz2vZHBB 6E1th/l//ZC5b9Dk0ZpFI1bYdL9ymnrZe1MqbGPnDCToQxu00T/pZCm6Z92YrZQYuNwl Message-ID: <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net> Date: Sat, 22 Dec 2018 21:03:26 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="C9tYzLa4TFdnD3GavtP4j4bVdhI51xkqa" X-Rspamd-Queue-Id: 7402E6B19A X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.975,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 18:03:47 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --C9tYzLa4TFdnD3GavtP4j4bVdhI51xkqa Content-Type: multipart/mixed; boundary="dqdUviaZ1EgHR5FbTSaJiV6v1uEsJLO2f"; protected-headers="v1" From: Yuri Pankov To: Mark Peek , Enji Cooper Cc: Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current Message-ID: <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net> Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> <980AA7F3-A447-45DC-A538-8EA89515F7DF@gmail.com> In-Reply-To: --dqdUviaZ1EgHR5FbTSaJiV6v1uEsJLO2f Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Mark Peek wrote: > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wro= te: >=20 >> >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: >>> >>> Mark Peek wrote: >>>> Thanks for the cc:. I forwarded the original report on to an interna= l >>>> VMware desktop product contact. >>> >>> Thank you. >>> >>>> What version of Workstation or Fusion is this occurring on? I saw >>>> Workstation 14 mentioned but curious if it occurs on Workstation 15 >>>> (latest). >>> >>> Running the latest available for download: 15.0.2 build-10952284. >> >> This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it wasn=E2= =80=99t >> affecting me on 10.x. I didn=E2=80=99t install 11.0.0, so I don=E2=80=99= t know if it >> affects that version... >> >> Thanks so much! >> >> -Enji >=20 >=20 > BTW, there appears to be a workaround here using -o 'IPQoS=3Dthroughput= ' > (untested by me). I've seen the issue forwarded internally but no furth= er > discussions yet. >=20 > https://communities.vmware.com/thread/590825 Yes, that's exactly what the patch attached to original message does if we are running as a VMware guest. The workaround is known and it works, but it's not immediately clear and I just wanted it to be the default for the time being. --dqdUviaZ1EgHR5FbTSaJiV6v1uEsJLO2f-- --C9tYzLa4TFdnD3GavtP4j4bVdhI51xkqa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlwefG4ACgkQk4vgf7Eq 4WwWygf+OobN3ufb1YCSnCO8LjYSecUmm1wogpvXTRq+1vwNQQGw52VcHSx4lZYU 3yTcoxtjDCwyIoLjX48wcRRKn4IerLv7ZF2jOLw+WhSoxqgzUqUXgHp2PCqSBCYF Yor5LljQUMjECaAuNBUHQiHo3Z+SDyxg36ZLWU7tvYlVTlaSYl0tmT/MQXAYQsd1 9rHj9KSDjQFaUhihTI9yYuUS2S3bK3GdW7INYXhS+JzkGndZuVNkvNUkJ4e6wRzy KYcJhHPyUrPhx6bVtQfadMz5Pr4JG6euZK4442p/I9RxyGIVu9A/mlrgJqVVeGwy YHf2yUw98CwLyqKq1LUOngwjw+Mk/Q== =VqrW -----END PGP SIGNATURE----- --C9tYzLa4TFdnD3GavtP4j4bVdhI51xkqa-- From owner-freebsd-current@freebsd.org Sat Dec 22 18:16:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99CB81335ABB for ; Sat, 22 Dec 2018 18:16:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D93FA6BA0C for ; Sat, 22 Dec 2018 18:16:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9CCF11335AB6; Sat, 22 Dec 2018 18:16:52 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A2AC1335AB5 for ; Sat, 22 Dec 2018 18:16:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1167D6BA06 for ; Sat, 22 Dec 2018 18:16:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x82a.google.com with SMTP id p17so9456037qtl.5 for ; Sat, 22 Dec 2018 10:16:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nlSiA+CebNCCGc5BOccON0SySOoOPALhGf6bN6wD/y0=; b=gByPS7UipPVOUjzl6A4urk2A+cjSTatVQUa3xSkSRVITMqCJG/WaGdTGTyWjP//YSR Dm+ZNTqPUptvXCj1uk80dFrkzcNW9LJnXjStY/+CiTWWGuiokr1KD0f2uVGuUfgq9y6C mExbmaO8Qr7cNVFoizq+zXTGbYD4TKlRqh1+4I6yWN7B0gRRLwBPzm1fIxNMbRETGjXs d/Kjt1z9OYaDOqLaQD4wJZIIIoBHdwwe+TEcC9icA8/YcPB7oCJWYvbGDR76Sw0TtsyK PDKW8Yx9m1xJzgOa3aP9L+tnAx069cJhUhkZ/6DxJ/sI1TKE81ypDxY5kSk11Eg2qNXg G71g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nlSiA+CebNCCGc5BOccON0SySOoOPALhGf6bN6wD/y0=; b=cBddSx4xWsPtUi9jNl0a+fhpvY2bCdet+FCql6/ljgr1GWxc+/KGfhqvdW9JKkWVIT DUGq4wPrH819XLn0FMY97FwXlqr8UsUV/j0SChI8zghXwjXORucvwr3wk5vaHPgCMK6q f8Ag8w+EJHL3LDk7rachUPcYS1Sns6FjriXQSnP96hPIEit39ti+1Esxsg29eHT+0LAv A3o34IZ0qtTCwwi22uqI68IR4y/T7lQkjPzvcKwDZx+uw3ZKgYV2CEkzS8NccUFHDNze jdo4+8TyiHJG8ciYObP2kAVaaBlyeSncjfgdlHOzyulLK1ze8wv5e6acNlTT68EUTL0T AZkw== X-Gm-Message-State: AJcUukfB6uO/xSkTaYge5cPYEERaj40knh/BlnwRzhE2lsZ09Cob7wI5 xVFYhEWAOIxS3iia1f5YQtqhDASz/Dy1A+0JKw2UxHQS X-Google-Smtp-Source: ALg8bN5y8nue6EgPKqacPwIbEcfb+IwDPujroDALnxQi2H4NXl6qWo8zjmC2bKCIYnLSXfIyGb2IFSuVEx2Cjq51oRs= X-Received: by 2002:ac8:548a:: with SMTP id h10mr6991370qtq.15.1545502611341; Sat, 22 Dec 2018 10:16:51 -0800 (PST) MIME-Version: 1.0 References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> <980AA7F3-A447-45DC-A538-8EA89515F7DF@gmail.com> <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net> In-Reply-To: <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net> From: Warner Losh Date: Sat, 22 Dec 2018 11:16:39 -0700 Message-ID: Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes To: Yuri Pankov Cc: Mark Peek , Garrett Cooper , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , freebsd-current X-Rspamd-Queue-Id: 1167D6BA06 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.96)[-0.960,0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 18:16:53 -0000 On Sat, Dec 22, 2018, 11:03 AM Yuri Pankov Mark Peek wrote: > > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper > wrote: > > > >> > >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: > >>> > >>> Mark Peek wrote: > >>>> Thanks for the cc:. I forwarded the original report on to an interna= l > >>>> VMware desktop product contact. > >>> > >>> Thank you. > >>> > >>>> What version of Workstation or Fusion is this occurring on? I saw > >>>> Workstation 14 mentioned but curious if it occurs on Workstation 15 > >>>> (latest). > >>> > >>> Running the latest available for download: 15.0.2 build-10952284. > >> > >> This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it wasn=E2= =80=99t > >> affecting me on 10.x. I didn=E2=80=99t install 11.0.0, so I don=E2=80= =99t know if it > >> affects that version... > >> > >> Thanks so much! > >> > >> -Enji > > > > > > BTW, there appears to be a workaround here using -o 'IPQoS=3Dthroughput= ' > > (untested by me). I've seen the issue forwarded internally but no furth= er > > discussions yet. > > > > https://communities.vmware.com/thread/590825 > > Yes, that's exactly what the patch attached to original message does if > we are running as a VMware guest. The workaround is known and it works, > but it's not immediately clear and I just wanted it to be the default > for the time being. > Fixes my world... Warner > From owner-freebsd-current@freebsd.org Sat Dec 22 20:09:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9BC571339AF6 for ; Sat, 22 Dec 2018 20:09:25 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 16A836F1CA for ; Sat, 22 Dec 2018 20:09:25 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: by mailman.ysv.freebsd.org (Postfix) id CB3C71339AF5; Sat, 22 Dec 2018 20:09:24 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8E2C1339AF4 for ; Sat, 22 Dec 2018 20:09:24 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 491DC6F1C7; Sat, 22 Dec 2018 20:09:22 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id anaIg2ZB8MRX3anaKgPzNF; Sat, 22 Dec 2018 13:09:21 -0700 X-Authority-Analysis: v=2.3 cv=TL87tGta c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=2ur7OfE09M0A:10 a=L0TlzgiqAAAA:8 a=pGLkceISAAAA:8 a=eh1Yez-EAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=FK5bYJiJP2447jQKtJoA:9 a=CjuIK1q_8ugA:10 a=h1pxpgV1WlEA:10 a=IAVDLmJhbIOVeWgv0OxI:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 83B5F2B4; Sat, 22 Dec 2018 12:09:18 -0800 (PST) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id wBMK9ISa050106; Sat, 22 Dec 2018 12:09:18 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id wBMK9H5T050103; Sat, 22 Dec 2018 12:09:18 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201812222009.wBMK9H5T050103@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Yuri Pankov cc: Mark Peek , Enji Cooper , Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes In-Reply-To: Message from Yuri Pankov of "Sat, 22 Dec 2018 21:03:26 +0300." <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Dec 2018 12:09:17 -0800 X-CMAE-Envelope: MS4wfO4xzWeow5AL16JIU7n9XLRXxc8swd3BuFOCzIw1ymnALAt9g5katCAVgb3yMfUBz4npRLjyRV5nISD9VTsts5LLMBX5FHcR7KZgGUnzq78VFXOPSSqF Zcu7qHN3/NcAT56WCbS/N2XlDa/upKRmgLyoCfnT03ZYl6+gAMv1dO+N1BK9EOgSmZYNYN0cvPPTjAQP9vCsUAm/QAtVk6egunO+UcQce+8cYn61ZqicOwpg KXOSOxSoFYF8aLPiSyQPxo1sWzneOpJDG+DZUolnBfD/8ql0DkSjQkKFrjxyeg4sE1jJzD02BjNBF8Bkmg39/g== X-Rspamd-Queue-Id: 491DC6F1C7 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-4.37 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; RCPT_COUNT_FIVE(0.00)[6]; REPLYTO_EQ_FROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.94)[-0.943,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[9.134.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-1.71)[ip: (-3.98), ipnet: 64.59.128.0/20(-2.50), asn: 6327(-2.00), country: CA(-0.09)]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 20:09:25 -0000 In message <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net>, Yuri Pankov write s: > Yuri Pankov wrote: >> In-Reply-To: > com> >> Mark Peek wrote: >> > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wro= >> te: >> >=20 >> >> >> >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: >> >>> >> >>> Mark Peek wrote: >> >>>> Thanks for the cc:. I forwarded the original report on to an interna= >> l >> >>>> VMware desktop product contact. >> >>> >> >>> Thank you. >> >>> >> >>>> What version of Workstation or Fusion is this occurring on? I saw >> >>>> Workstation 14 mentioned but curious if it occurs on Workstation 15 >> >>>> (latest). >> >>> >> >>> Running the latest available for download: 15.0.2 build-10952284. >> >> >> >> This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it wasn=E2= >> =80=99t >> >> affecting me on 10.x. I didn=E2=80=99t install 11.0.0, so I don=E2=80=99= >> t know if it >> >> affects that version... >> >> >> >> Thanks so much! >> >> >> >> -Enji >> >=20 >> >=20 >> > BTW, there appears to be a workaround here using -o 'IPQoS=3Dthroughput= >> ' >> > (untested by me). I've seen the issue forwarded internally but no furth= >> er >> > discussions yet. >> >=20 >> > https://communities.vmware.com/thread/590825 > > Yes, that's exactly what the patch attached to original message does if > we are running as a VMware guest. The workaround is known and it works, > but it's not immediately clear and I just wanted it to be the default > for the time being. The patch assumes VMWARE_GUEST_WORKAROUND unconditionally. Is this intended? Juxtaposed to this, at $JOB where our VMware guests (mostly Linux and Windows) running on VMware clusters with NSX network (with plans to totally virtualize the network), we've noticed other network quirkiness, most notably with NFS between unlike O/S's, i.e. Solaris <--> Linux. I'm not surprised that this regression also exists. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Sat Dec 22 20:14:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13F661339EE6 for ; Sat, 22 Dec 2018 20:14:06 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 020056F6D7 for ; Sat, 22 Dec 2018 20:14:05 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: by mailman.ysv.freebsd.org (Postfix) id B95AD1339EE3; Sat, 22 Dec 2018 20:14:04 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96CB31339EE2 for ; Sat, 22 Dec 2018 20:14:04 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 1F1A46F6D3; Sat, 22 Dec 2018 20:14:03 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 0707EEC0; Sat, 22 Dec 2018 15:14:01 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 22 Dec 2018 15:14:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm3; bh=4si6Ol0TV/X8nZ/PEFwPEenSfja /TYffkTjQ8Re3ngo=; b=cMV/LWoLVjaJY8532WHyVrHRGlbeqEs4dCqkPU92vpG Axagoo71z+ylEh7pgpu8Z3Fv3h/e9EfHZfjtP9pqKmhb5B4I9SN+pnLfdaW1IKh/ 4yTzU+QTzjiILdHHk5C6G5lcz2Iv4S2GizIJFkyjeXGguUUmZu+CQIvNokKlDo90 bl42CbuIMAYtRu4P0+AKHIOz07y1vgJ+DdZj0AKeW9q5+e8f2wDRjDSWb7ylRFtO Wt+iW/tADm0LZNKWC6xT0Ad3+QHfGKEVOPs6kgtf1Bgq9U+9nSSnuvb16S8b6BqJ VQZwiwgvApQk+6q1fp1r+tb2pgoQCrZ/xmB8yY/4U1w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=4si6Ol 0TV/X8nZ/PEFwPEenSfja/TYffkTjQ8Re3ngo=; b=BVRPY19ltUZkKQejzN6o/0 yYlmFzVD+keuTMQI6VvJA3SGFZ5myFQ6XW0I0WsHc+Vl+VGyHyx7zo/eEg+hCD3F 6zklU9DVP+Ci32ZcitxPI0CipwP8rfPvQyM+YeisFTZj6BKuGoNDYulPpBRc+9Xk CWzbaCjKmWUKT2EiuR17wriX/3qeCZW93gAwGFAPUuPd6k1v1LJbKjmQYJll+Pzs s118TYM6OqCkIHYLqa0d64yDnX9+2I31jYuar0kVdvF8YAeuK8EF85ils3OLXrLD Ro7nZUwAdZxf3k92gjd/ucqwsR4PbnEAHTXFapkQGSA521GYeyu6LJmp6Fb0aC/A == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudejjedgudefgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecu fedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhkf fffgggjggtsehgtderofdtfeejnecuhfhrohhmpegjuhhrihcurfgrnhhkohhvuceohihu rhhiphhvseihuhhrihhpvhdrnhgvtheqnecuffhomhgrihhnpehvmhifrghrvgdrtghomh enucfkphepleegrddvfeefrddvfedurdduleehnecurfgrrhgrmhepmhgrihhlfhhrohhm peihuhhrihhpvheshihurhhiphhvrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from [192.168.1.2] (unknown [94.233.231.195]) by mail.messagingengine.com (Postfix) with ESMTPA id E3E5B10084; Sat, 22 Dec 2018 15:13:58 -0500 (EST) Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes To: Cy Schubert Cc: Mark Peek , Enji Cooper , Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current References: <201812222009.wBMK9H5T050103@slippy.cwsent.com> From: Yuri Pankov Openpgp: preference=signencrypt Autocrypt: addr=yuripv@yuripv.net; keydata= mQENBFu8u6IBCADB11gP0QwnorrHjqAtKLHKHNHskhy0s7jqJKfx0YqXgVBKGLJ9/mjLAz0F CBNvemHSDDTs0mEZ9cBKKi6cmsav6+UQgr//yai6hvXLBJqKchSFO4MhmdvBtsGFq1yKz5Zi uhjmimKyIpgBgvMdbgGbGq6cnSB2uEPmZuJr419SVRODOkXukU+F5WHgaHzDdHAIu1asCt2B +6msxqIqlFWcXyZyTGicTGGvC/PFIsVRUtD1dIJANTC876g7DTb7LZXWiWwJpSJ4GKMXMHVX Ct9BoQ4i3nhKbOxb6Io1wsy+NFyWsTJ9KYrxKKPJP3oG8BWb/cqlFqnE4eNSsiq2q7krABEB AAG0H1l1cmkgUGFua292IDx5dXJpcHZAeXVyaXB2Lm5ldD6JAVQEEwEKAD4WIQT4arc+w94t Pi0v/3CTi+B/sSrhbAUCW7y7ogIbAwUJBaOagAULCQgHAwUVCgkICwUWAwIBAAIeAQIXgAAK CRCTi+B/sSrhbJ+ACACqOlkjZ+iP8K8hcwz/G6+c1lVkhuMWL+hxFeE149QuJAXQvkOj/UXO 7jY9HSqFbOYYY44/hujpQCu+/u2dsJ5MAA7TJspWK2zUxtFAzgDp1fRXmCvMlFLdI0yVkKOB JaK+HQP8rBT6yHzGw1KJ6VyOXuuD0Kx02Ou61qjG9/vPRR0jtaxog0rKxpf+yf0UvSM4vb7+ LdY2GQxgfcLcJ8hThR4ElWJAkDsG4CiXixGJuFJ+9dpMK6LHmP6M+NxV4NkzpNddn3Eii8XQ y5spxcLszp8csFBDtAC6BI9sHLhJ9Va1VKpuvSlDsBv4ZtsjnUCIaOiF5MDTYkddSPGGMBck uQENBFu8u6IBCADKih3Q933rDNj4ZA8FhBQ2RlmBgvwOLcDPIL3h0V7h38y3+HisgFScXACD sdrTlYZ1bRXkD9FHENynBcv0l/3uGJDk8jaGIDE0TP8OQBRp+IaU9/BHnAqrKxTJGIolDahy 2m+yx2yhdc6B4ujWMDqCF1rWOD+ymOWw+VLllOkrHcZa5PJtX9UOGbApZl8ZTM8El4CANN8F 1bg9MWzUi+8LYoGWGc+BwsFS1OUB1c4SPgMu5fD4Wfsr9yRl06fdpEA2YT7B/j5/5RSC0sE2 Zs/tmJ/JRflHJ12ycj59ma2xQMfEJF40hZDpMFQmZvbVqgEg3ocQcltjbxlIKZ/mjC4zABEB AAGJATwEGAEKACYWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW7y7ogIbDAUJBaOagAAKCRCT i+B/sSrhbIDcCACqAZMcoxUBLZa40a5b24j5i1jplvCYYb3h+Q5lt5+BFJ87kCb4dJuUD3kh 2i29BrxWQWa9WNue9ozxeYkbkfXubQYXexVolRsnh64OdGsE8KvorBFBB3zdK/GRt2Jy+jsn TfUWuQllbzMP0MfhCDMk1Mo8WvDH2/cOEP/yLKf20a+cd6nLs7bidjmGXo9pyuBKAtV6Kv+V Ru54AL+A/UBYu/eB3Dtvzcnut+1Zq6KaP++kUwPwINLIk04OBDwN0zRNTiqMAFYYyz2vZHBB 6E1th/l//ZC5b9Dk0ZpFI1bYdL9ymnrZe1MqbGPnDCToQxu00T/pZCm6Z92YrZQYuNwl Message-ID: Date: Sat, 22 Dec 2018 23:13:49 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <201812222009.wBMK9H5T050103@slippy.cwsent.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH" X-Rspamd-Queue-Id: 1F1A46F6D3 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.973,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 20:14:06 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH Content-Type: multipart/mixed; boundary="c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi"; protected-headers="v1" From: Yuri Pankov To: Cy Schubert Cc: Mark Peek , Enji Cooper , Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current Message-ID: Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes References: <201812222009.wBMK9H5T050103@slippy.cwsent.com> In-Reply-To: <201812222009.wBMK9H5T050103@slippy.cwsent.com> --c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Cy Schubert wrote: > In message <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net>, Yuri=20 > Pankov write > s: >> Yuri Pankov wrote: >>> In-Reply-To: l.gmail. >>> com> >>> Mark Peek wrote: >>>> On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper > wro=3D >>> te: >>>> =3D20 >>>>> >>>>>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: >>>>>> >>>>>> Mark Peek wrote: >>>>>>> Thanks for the cc:. I forwarded the original report on to an=20 > interna=3D >>> l >>>>>>> VMware desktop product contact. >>>>>> >>>>>> Thank you. >>>>>> >>>>>>> What version of Workstation or Fusion is this occurring on? I=20 > saw >>>>>>> Workstation 14 mentioned but curious if it occurs on=20 > Workstation 15 >>>>>>> (latest). >>>>>> >>>>>> Running the latest available for download: 15.0.2 build-10952284. >>>>> >>>>> This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it=20 > wasn=3DE2=3D >>> =3D80=3D99t >>>>> affecting me on 10.x. I didn=3DE2=3D80=3D99t install 11.0.0, so I=20 > don=3DE2=3D80=3D99=3D >>> t know if it >>>>> affects that version... >>>>> >>>>> Thanks so much! >>>>> >>>>> -Enji >>>> =3D20 >>>> =3D20 >>>> BTW, there appears to be a workaround here using -o=20 > 'IPQoS=3D3Dthroughput=3D >>> ' >>>> (untested by me). I've seen the issue forwarded internally but no=20 > furth=3D >>> er >>>> discussions yet. >>>> =3D20 >>>> https://communities.vmware.com/thread/590825 >> >> Yes, that's exactly what the patch attached to original message does i= f >> we are running as a VMware guest. The workaround is known and it work= s, >> but it's not immediately clear and I just wanted it to be the default >> for the time being. >=20 > The patch assumes VMWARE_GUEST_WORKAROUND unconditionally. Is this=20 > intended? It's the added code that is ifdef'ed VMWARE_GUEST_WORKAROUND, so it can be ripped out easily when no longer needed, and yes, it's enabled unconditionally for now. And the check itself is if 'kern.vm_guest' reports 'vmware'. > Juxtaposed to this, at $JOB where our VMware guests (mostly Linux and=20 > Windows) running on VMware clusters with NSX network (with plans to=20 > totally virtualize the network), we've noticed other network=20 > quirkiness, most notably with NFS between unlike O/S's, i.e. Solaris=20 > <--> Linux. I'm not surprised that this regression also exists. >=20 >=20 --c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi-- --NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlwemv0ACgkQk4vgf7Eq 4WzRYQgAkYY2fb3KicgVMkTSVjP+g3mEz0xqAQIVnOKaRDfXOqAG3sgSqp5FkEiz OqQYlFfgeg6hOIIKUpsJc0DU7TTZUNtVw1XNihb3JlHIufe3XU2p6zER2jBqPObW xAltGgZfd3cKeR+bKV2jKTEFmuUjRyTu8X1heWK0RZ09Wa+mBeEgcoSOJJDuEHRY vs5QeqduyhoxN7GAIlkgsUCCEDzeoAW4x+6OqYC3QFgw/VwD8EUJpMD2A1s8OUTw GrFYvuWiH0k/YbIQyhY04vUIVNR4VqQFrL7d+eiIAhA5Q0vpDrf8KDgev+NDYRiY cOg0wABTh/vkYW+B3p4Ef5jL3HrT/Q== =l+NN -----END PGP SIGNATURE----- --NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH-- From owner-freebsd-current@freebsd.org Sat Dec 22 20:27:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 702BC133A32E for ; Sat, 22 Dec 2018 20:27:30 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C044D6FBFF for ; Sat, 22 Dec 2018 20:27:29 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7E313133A32D; Sat, 22 Dec 2018 20:27:29 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58F8F133A32C for ; Sat, 22 Dec 2018 20:27:29 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 42A276FBFC; Sat, 22 Dec 2018 20:27:28 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id anrhghqye82YcanrigpVUm; Sat, 22 Dec 2018 13:27:20 -0700 X-Authority-Analysis: v=2.3 cv=NNSrBHyg c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=2ur7OfE09M0A:10 a=L0TlzgiqAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=pGLkceISAAAA:8 a=7Qk2ozbKAAAA:8 a=VxmjJ2MpAAAA:8 a=eh1Yez-EAAAA:8 a=Xe7PpyctmunpBpIkOdIA:9 a=CjuIK1q_8ugA:10 a=-RtknO9RM1QA:10 a=h1pxpgV1WlEA:10 a=IAVDLmJhbIOVeWgv0OxI:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=1lyxoWkJIXJV6VJUPhuM:22 a=7gXAzLPJhVmCkEl4_tsf:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id AEB272E2; Sat, 22 Dec 2018 12:27:16 -0800 (PST) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id wBMKRGY8050856; Sat, 22 Dec 2018 12:27:16 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id wBMKRGWJ050853; Sat, 22 Dec 2018 12:27:16 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201812222027.wBMKRGWJ050853@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Yuri Pankov cc: Cy Schubert , Mark Peek , Enji Cooper , Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes In-Reply-To: Message from Yuri Pankov of "Sat, 22 Dec 2018 23:13:49 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Dec 2018 12:27:16 -0800 X-CMAE-Envelope: MS4wfNsy9Ihz3qfvbL4KuZKGwp1dcDh9gBngW8m01E7liMOZMYO2WUNtHMBE13G8ix985WJSwxVwcBsfmj0gUNPINpDC8QWHQ1v6vFtVkXDYCAILJ3W7MTmx AaA0SuHPYKBYXMKmHlzXiVzfOW9yvE5PUQgcvT9mkt39tNatj3OFL4a1vCm6p7f4ZcvhghcE3edEPdvi1xsK00JJOLbBo35RLrvP2xU+nmPMvOy9G+/SgGzO tu5ElgsgsvLJkx8/tqPC0/89Nz3Jpa9wupQpB75P766B3NqoOdQC1bRNG/RiXTMM0k2FmTDY/2/NVovll4/QJg== X-Rspamd-Queue-Id: 42A276FBFC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-4.26 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; REPLYTO_EQ_FROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.94)[-0.936,0]; RCPT_COUNT_SEVEN(0.00)[7]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-1.62)[ip: (-3.50), ipnet: 64.59.128.0/20(-2.49), asn: 6327(-1.99), country: CA(-0.09)]; RCVD_IN_DNSWL_LOW(-0.10)[139.136.59.64.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 20:27:30 -0000 In message , Yuri Pankov write s: > This is an OpenPGP/MIME signed message (RFC 4880 and 3156) > --NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH > Content-Type: multipart/mixed; boundary="c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi"; > protected-headers="v1" > From: Yuri Pankov > To: Cy Schubert > Cc: Mark Peek , Enji Cooper , > Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= > , freebsd-current > Message-ID: > Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 > changes > References: <201812222009.wBMK9H5T050103@slippy.cwsent.com> > In-Reply-To: <201812222009.wBMK9H5T050103@slippy.cwsent.com> > > --c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi > Content-Type: text/plain; charset=utf-8 > Content-Language: en-US > Content-Transfer-Encoding: quoted-printable > > Cy Schubert wrote: > > In message <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net>, Yuri=20 > > Pankov write > > s: > >> Yuri Pankov wrote: > >>> In-Reply-To: > > l.gmail. > >>> com> > >>> Mark Peek wrote: > >>>> On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper > > wro=3D > >>> te: > >>>> =3D20 > >>>>> > >>>>>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: > >>>>>> > >>>>>> Mark Peek wrote: > >>>>>>> Thanks for the cc:. I forwarded the original report on to an=20 > > interna=3D > >>> l > >>>>>>> VMware desktop product contact. > >>>>>> > >>>>>> Thank you. > >>>>>> > >>>>>>> What version of Workstation or Fusion is this occurring on? I=20 > > saw > >>>>>>> Workstation 14 mentioned but curious if it occurs on=20 > > Workstation 15 > >>>>>>> (latest). > >>>>>> > >>>>>> Running the latest available for download: 15.0.2 build-10952284. > >>>>> > >>>>> This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it=20 > > wasn=3DE2=3D > >>> =3D80=3D99t > >>>>> affecting me on 10.x. I didn=3DE2=3D80=3D99t install 11.0.0, so I=20 > > don=3DE2=3D80=3D99=3D > >>> t know if it > >>>>> affects that version... > >>>>> > >>>>> Thanks so much! > >>>>> > >>>>> -Enji > >>>> =3D20 > >>>> =3D20 > >>>> BTW, there appears to be a workaround here using -o=20 > > 'IPQoS=3D3Dthroughput=3D > >>> ' > >>>> (untested by me). I've seen the issue forwarded internally but no=20 > > furth=3D > >>> er > >>>> discussions yet. > >>>> =3D20 > >>>> https://communities.vmware.com/thread/590825 > >> > >> Yes, that's exactly what the patch attached to original message does i= > f > >> we are running as a VMware guest. The workaround is known and it work= > s, > >> but it's not immediately clear and I just wanted it to be the default > >> for the time being. > >=20 > > The patch assumes VMWARE_GUEST_WORKAROUND unconditionally. Is this=20 > > intended? > > It's the added code that is ifdef'ed VMWARE_GUEST_WORKAROUND, so it can > be ripped out easily when no longer needed, and yes, it's enabled > unconditionally for now. And the check itself is if 'kern.vm_guest' > reports 'vmware'. It doesn't look that conditional to me. diff --git a/secure/usr.bin/ssh/Makefile b/secure/usr.bin/ssh/Makefile index 614cc7627fc5..023fa4a55be9 100644 --- a/secure/usr.bin/ssh/Makefile +++ b/secure/usr.bin/ssh/Makefile @@ -37,6 +37,9 @@ LIBADD+= crypto CFLAGS+= -DXAUTH_PATH=\"${LOCALBASE}/bin/xauth\" .endif +# Workaround VMware Workstation NAT bug +CFLAGS+=-DVMWARE_GUEST_WORKAROUND + .include .PATH: ${SSHDIR} -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Sat Dec 22 20:31:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2332E133A653 for ; Sat, 22 Dec 2018 20:31:24 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 751F66FF37 for ; Sat, 22 Dec 2018 20:31:23 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: by mailman.ysv.freebsd.org (Postfix) id 325EB133A64A; Sat, 22 Dec 2018 20:31:23 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2884133A645 for ; Sat, 22 Dec 2018 20:31:22 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 48C476FF2D; Sat, 22 Dec 2018 20:31:22 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 49AEA93A; Sat, 22 Dec 2018 15:31:20 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 22 Dec 2018 15:31:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm3; bh=XLuK+PMF3xbGXjUx+wVgPQs8GW+ 3o+PwpLhcUSA2I7Q=; b=DEXRDgjGzlol6XXf3IrigznsXILshzBl6Inwt07Tbcs bPqAzcP1j/MM0Y5N87B9OVaWAHgWm8CQ+a0cgyJBq7RUvRtxHJybgj8EUUKgBnl/ RP/TVrkgWctX2zaAdYVBmJFYZFUzrqVOLWw+uLC5bKTV8ShvNVPckk28OR6+mKOZ 92tcTEqPBp+vGgwMsi1kN1LWzzsRvw0Ku2/DCMMe0A0fSPGlify/VXsTlmV0ivIK D6l/RCBFZQyY0MU8JM6BFFb6zS7dkn85Qm3DEDhWHI/jVkmMZ0cmlS05ZHrhSm40 aLcFj0WndB8OmLaqnjcQBNrNX3JttOgsIMeK5vXLGSg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=XLuK+P MF3xbGXjUx+wVgPQs8GW+3o+PwpLhcUSA2I7Q=; b=mql4MbynYjanEoJvE//38D mRpCL0w+pWbK5fN9mLWrkU6Zvl5pkNl0+OWF8KkrSg47HYEiATPYLqEkkb7gB8y9 kebX+ugSFpcDKCImV4a2/nPZyzrgKudRCmHIoe6x1YXRsofDAQ4+y5Vzd/8D/8f+ exO3PXsqOi7sMdfjgwLYlpAiyqtin+o05TwMSk2Ss+OXMIcsvmHxd7eDfU562zlG 6npNj5sbOEpUhwHCIKK+gLtQyu+g7BNFkA6/uHajDCxsBwmlZ03Gf33IWlKG43Cj HmHIa1c9MW4uumiOsWlupBN1eK6bCyb5WWyhW1W5TT+5L/K9q25d8IhYv/vCKJCw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudejjedgudefkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecu fedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhkf fffgggjggtsehgtderofdtfeejnecuhfhrohhmpegjuhhrihcurfgrnhhkohhvuceohihu rhhiphhvseihuhhrihhpvhdrnhgvtheqnecuffhomhgrihhnpehvmhifrghrvgdrtghomh enucfkphepleegrddvfeefrddvfedurdduleehnecurfgrrhgrmhepmhgrihhlfhhrohhm peihuhhrihhpvheshihurhhiphhvrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from [192.168.1.2] (unknown [94.233.231.195]) by mail.messagingengine.com (Postfix) with ESMTPA id 57F3910087; Sat, 22 Dec 2018 15:31:17 -0500 (EST) Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes To: Cy Schubert Cc: Mark Peek , Enji Cooper , Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current References: <201812222027.wBMKRGWJ050853@slippy.cwsent.com> From: Yuri Pankov Openpgp: preference=signencrypt Autocrypt: addr=yuripv@yuripv.net; keydata= mQENBFu8u6IBCADB11gP0QwnorrHjqAtKLHKHNHskhy0s7jqJKfx0YqXgVBKGLJ9/mjLAz0F CBNvemHSDDTs0mEZ9cBKKi6cmsav6+UQgr//yai6hvXLBJqKchSFO4MhmdvBtsGFq1yKz5Zi uhjmimKyIpgBgvMdbgGbGq6cnSB2uEPmZuJr419SVRODOkXukU+F5WHgaHzDdHAIu1asCt2B +6msxqIqlFWcXyZyTGicTGGvC/PFIsVRUtD1dIJANTC876g7DTb7LZXWiWwJpSJ4GKMXMHVX Ct9BoQ4i3nhKbOxb6Io1wsy+NFyWsTJ9KYrxKKPJP3oG8BWb/cqlFqnE4eNSsiq2q7krABEB AAG0H1l1cmkgUGFua292IDx5dXJpcHZAeXVyaXB2Lm5ldD6JAVQEEwEKAD4WIQT4arc+w94t Pi0v/3CTi+B/sSrhbAUCW7y7ogIbAwUJBaOagAULCQgHAwUVCgkICwUWAwIBAAIeAQIXgAAK CRCTi+B/sSrhbJ+ACACqOlkjZ+iP8K8hcwz/G6+c1lVkhuMWL+hxFeE149QuJAXQvkOj/UXO 7jY9HSqFbOYYY44/hujpQCu+/u2dsJ5MAA7TJspWK2zUxtFAzgDp1fRXmCvMlFLdI0yVkKOB JaK+HQP8rBT6yHzGw1KJ6VyOXuuD0Kx02Ou61qjG9/vPRR0jtaxog0rKxpf+yf0UvSM4vb7+ LdY2GQxgfcLcJ8hThR4ElWJAkDsG4CiXixGJuFJ+9dpMK6LHmP6M+NxV4NkzpNddn3Eii8XQ y5spxcLszp8csFBDtAC6BI9sHLhJ9Va1VKpuvSlDsBv4ZtsjnUCIaOiF5MDTYkddSPGGMBck uQENBFu8u6IBCADKih3Q933rDNj4ZA8FhBQ2RlmBgvwOLcDPIL3h0V7h38y3+HisgFScXACD sdrTlYZ1bRXkD9FHENynBcv0l/3uGJDk8jaGIDE0TP8OQBRp+IaU9/BHnAqrKxTJGIolDahy 2m+yx2yhdc6B4ujWMDqCF1rWOD+ymOWw+VLllOkrHcZa5PJtX9UOGbApZl8ZTM8El4CANN8F 1bg9MWzUi+8LYoGWGc+BwsFS1OUB1c4SPgMu5fD4Wfsr9yRl06fdpEA2YT7B/j5/5RSC0sE2 Zs/tmJ/JRflHJ12ycj59ma2xQMfEJF40hZDpMFQmZvbVqgEg3ocQcltjbxlIKZ/mjC4zABEB AAGJATwEGAEKACYWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW7y7ogIbDAUJBaOagAAKCRCT i+B/sSrhbIDcCACqAZMcoxUBLZa40a5b24j5i1jplvCYYb3h+Q5lt5+BFJ87kCb4dJuUD3kh 2i29BrxWQWa9WNue9ozxeYkbkfXubQYXexVolRsnh64OdGsE8KvorBFBB3zdK/GRt2Jy+jsn TfUWuQllbzMP0MfhCDMk1Mo8WvDH2/cOEP/yLKf20a+cd6nLs7bidjmGXo9pyuBKAtV6Kv+V Ru54AL+A/UBYu/eB3Dtvzcnut+1Zq6KaP++kUwPwINLIk04OBDwN0zRNTiqMAFYYyz2vZHBB 6E1th/l//ZC5b9Dk0ZpFI1bYdL9ymnrZe1MqbGPnDCToQxu00T/pZCm6Z92YrZQYuNwl Message-ID: <0503b382-d886-39a4-d265-b43d8adc15c9@yuripv.net> Date: Sat, 22 Dec 2018 23:31:09 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <201812222027.wBMKRGWJ050853@slippy.cwsent.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="e7sW91Qf9WxzTaujtGEdAimN5k2EtpJ6Q" X-Rspamd-Queue-Id: 48C476FF2D X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.974,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 20:31:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --e7sW91Qf9WxzTaujtGEdAimN5k2EtpJ6Q Content-Type: multipart/mixed; boundary="3a9zlXDI7Z2P48EdQkgwMdVOMQOEfR5Wm"; protected-headers="v1" From: Yuri Pankov To: Cy Schubert Cc: Mark Peek , Enji Cooper , Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current Message-ID: <0503b382-d886-39a4-d265-b43d8adc15c9@yuripv.net> Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes References: <201812222027.wBMKRGWJ050853@slippy.cwsent.com> In-Reply-To: <201812222027.wBMKRGWJ050853@slippy.cwsent.com> --3a9zlXDI7Z2P48EdQkgwMdVOMQOEfR5Wm Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Cy Schubert wrote: > In message , Yuri=20 > Pankov write > s: >> This is an OpenPGP/MIME signed message (RFC 4880 and 3156) >> --NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH >> Content-Type: multipart/mixed; boundary=3D"c7yUHUJpZYpJqOrOWLAb4sE3Rmh= 2alrdi"; >> protected-headers=3D"v1" >> From: Yuri Pankov >> To: Cy Schubert >> Cc: Mark Peek , Enji Cooper , >> Warner Losh , =3D?UTF-8?Q?Dag-Erling_Sm=3Dc3=3Db8rgra= v?=3D >> , freebsd-current >> Message-ID: >> Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8= p1 >> changes >> References: <201812222009.wBMK9H5T050103@slippy.cwsent.com> >> In-Reply-To: <201812222009.wBMK9H5T050103@slippy.cwsent.com> >> >> --c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi >> Content-Type: text/plain; charset=3Dutf-8 >> Content-Language: en-US >> Content-Transfer-Encoding: quoted-printable >> >> Cy Schubert wrote: >>> In message <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net>, Yuri=3D= 20 >>> Pankov write >>> s: >>>> Yuri Pankov wrote: >>>>> In-Reply-To: > >>> l.gmail. >>>>> com> >>>>> Mark Peek wrote: >>>>>> On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper >>> wro=3D3D >>>>> te: >>>>>> =3D3D20 >>>>>>> >>>>>>>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote= : >>>>>>>> >>>>>>>> Mark Peek wrote: >>>>>>>>> Thanks for the cc:. I forwarded the original report on to an=3D= 20 >>> interna=3D3D >>>>> l >>>>>>>>> VMware desktop product contact. >>>>>>>> >>>>>>>> Thank you. >>>>>>>> >>>>>>>>> What version of Workstation or Fusion is this occurring on? I=3D= 20 >>> saw >>>>>>>>> Workstation 14 mentioned but curious if it occurs on=3D20 >>> Workstation 15 >>>>>>>>> (latest). >>>>>>>> >>>>>>>> Running the latest available for download: 15.0.2 build-10952284= =2E >>>>>>> >>>>>>> This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it=3D= 20 >>> wasn=3D3DE2=3D3D >>>>> =3D3D80=3D3D99t >>>>>>> affecting me on 10.x. I didn=3D3DE2=3D3D80=3D3D99t install 11.0.0= , so I=3D20 >>> don=3D3DE2=3D3D80=3D3D99=3D3D >>>>> t know if it >>>>>>> affects that version... >>>>>>> >>>>>>> Thanks so much! >>>>>>> >>>>>>> -Enji >>>>>> =3D3D20 >>>>>> =3D3D20 >>>>>> BTW, there appears to be a workaround here using -o=3D20 >>> 'IPQoS=3D3D3Dthroughput=3D3D >>>>> ' >>>>>> (untested by me). I've seen the issue forwarded internally but no=3D= 20 >>> furth=3D3D >>>>> er >>>>>> discussions yet. >>>>>> =3D3D20 >>>>>> https://communities.vmware.com/thread/590825 >>>> >>>> Yes, that's exactly what the patch attached to original message does= i=3D >> f >>>> we are running as a VMware guest. The workaround is known and it wo= rk=3D >> s, >>>> but it's not immediately clear and I just wanted it to be the defaul= t >>>> for the time being. >>> =3D20 >>> The patch assumes VMWARE_GUEST_WORKAROUND unconditionally. Is this=3D= 20 >>> intended? >> >> It's the added code that is ifdef'ed VMWARE_GUEST_WORKAROUND, so it ca= n >> be ripped out easily when no longer needed, and yes, it's enabled >> unconditionally for now. And the check itself is if 'kern.vm_guest' >> reports 'vmware'. >=20 > It doesn't look that conditional to me. Indeed, and that's what I said exactly :-) The added code is enabled unconditionally, and the added code also has a check for vmware guest. The ifdefs are there only to show that this is local addition, nothing el= se. I'm not saying it needs to be done this way, this is just something I did quickly after installing yet another VM and forgetting to modify my ~/.ssh/config to include the workaround. --3a9zlXDI7Z2P48EdQkgwMdVOMQOEfR5Wm-- --e7sW91Qf9WxzTaujtGEdAimN5k2EtpJ6Q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlwenw0ACgkQk4vgf7Eq 4WyIegf6A9GzStMWvJJm8rBz16USfMCQcfaFy7d78R6GpJJ8C6RCBnhEctznx9og atxstLlr0ar0qKUHWRVSKUGtAGp8599MJHJWNUR8DcHZxOhfyempASUhZq0usGLe /uav9JDc2n4sPcLckHVI/No5UUSnV3sdYGHmrBniNStlwxv0raeeRMUd1p5SYt45 XG41OuEGfih+fiDR+ITsooxEvQCBF1emPoYB0eHw2hnlfNzeQrnCMyRAduB/uw6+ 9WrHI9dDaPeZiSOhUBjXOtdyahW4fd9hclfIEDs40YTbnTh3jOm/g07lSUf2SEDK zWujMO+S0IG4H7giriVd9wYvmn/+/A== =p+yW -----END PGP SIGNATURE----- --e7sW91Qf9WxzTaujtGEdAimN5k2EtpJ6Q-- From owner-freebsd-current@freebsd.org Sat Dec 22 20:55:15 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7CDA5133B540 for ; Sat, 22 Dec 2018 20:55:15 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic302-4.consmr.mail.bf2.yahoo.com (sonic302-4.consmr.mail.bf2.yahoo.com [74.6.135.43]) (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 B054370EE4 for ; Sat, 22 Dec 2018 20:55:13 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: mjQfKEYVM1lsrsdyiMPPDCkli3aEH.Yuf7qioAg3skUY.gCb2Nm1DVGEWO56t7c iGeEt8l0DfoYmqIpUfwn4OEN7I60FOQ8yqqIIqdhKBG3zXtbp71ofmJtc0P9GBTsvxgliAzPQq.p e87cWjEhif1hrQ8hqII1oVQLCR2Y_MZfDqmpCdNI8oeGbidGVCj1ha0SHBFhPDN5v.6V1egfJVi6 8xhB.1UZQCeU9N4w.dmSBAKjmJuZ5p1tUaUDTEENll8bHjdj3N9DCsHg6UdBFiOKHs80XXDuZhGQ 2uPooOdlI3HcUoz9O1SfylyS_X2Yj5NfShYCmx9vYRxQN0clEdifgIqKj30X5b47xCrLs6inrWaA pMc_GSqnYkSzGI9el5xB1DuH0YUlLB2zAj7WHb4Q6Wot7cw3DMl0cMS3m.I4s9bbaqNBhfE76guh bg9VqbkZueo4.VEnA5i55RBkl1UtlCsyerqEmcIpjLI.6PgtldGwC0KxAvOhieXCn_Xe11jE31n0 uvu0KAxzwAeFAWiyP4I9lEA6aVIE30Ej8W8PFApp4ui_DjoS.7JdJrHqYNDiVPodPxRX2rNW1Fon y15X1jSCYBKoHMMNClnSugJ8vIzKaQSKM2czmNjbITfcO4a3w5owQSW3swVOSdHtV4OoHfsVJNiE O13k7unOMHBsVKvexX92o9LWV4VrhVX5BohQAvYLODpz3VRfQGTxeWb364sI5ArOx9q9Yt3POnWJ bOV5GNUVfGhfPUf53xTtMh393UxQdGHALw8UwmlMRKBN7q6.y6r.Xh14VWSUPp3uKWKRrAkN.Kf4 q5rx4_SLYgqC.6mi4Z4KFBO8DnDdGJovMvlItS1b0QsAXO042PwcaAGHL3TxVz9tQhpG6_nwwaJo qLNxPDwKRVBiu3Eg.sLo7x8ZpE48HfeeofUafDF8EEFeGxy5KqEAKbvKYh5bYQXeajpLACOxClTK QZS.2vYR0c0PFBhEH3orZe9gJRYu4Z2aHm1EUGWIPsACLnRuqsnp0ZS.x3hv2jG.3QFGcIpyDQGJ jyTD0sCq6xeaIdeITDaemPC_5w1_HNTso4OgkkrAYpSq9hm9fn.ivRJiHVsNtaKPdlqSXTgl80RC cOmRjvQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.bf2.yahoo.com with HTTP; Sat, 22 Dec 2018 20:55:12 +0000 Received: from c-67-170-167-181.hsd1.or.comcast.net (EHLO [192.168.1.109]) ([67.170.167.181]) by smtp410.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID e33a5e5a027923209050fbcb65b80ac5; Sat, 22 Dec 2018 20:55:10 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: A reliable port cross-build failure (hangup) in my context (amd64->armv7 cross build, with native-tool speedup involved) From: Mark Millard In-Reply-To: <865A13C8-9749-486E-9F79-5EEDDECBE621@yahoo.com> Date: Sat, 22 Dec 2018 12:55:07 -0800 Cc: freebsd-arm , FreeBSD Toolchain Content-Transfer-Encoding: quoted-printable Message-Id: <0154C3AC-D85B-4FCF-BA63-454BC26BC1A2@yahoo.com> References: <865A13C8-9749-486E-9F79-5EEDDECBE621@yahoo.com> To: freebsd-emulation@freebsd.org, FreeBSD Current , ports-list freebsd X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: B054370EE4 X-Spamd-Bar: / X-Spamd-Result: default: False [0.69 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MV_CASE(0.50)[]; FREEMAIL_FROM(0.00)[yahoo.com]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:26101, ipnet:74.6.128.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.35)[-0.347,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.69)[0.686,0]; NEURAL_HAM_LONG(-0.71)[-0.706,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(1.57)[ip: (5.00), ipnet: 74.6.128.0/21(1.62), asn: 26101(1.30), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[43.135.6.74.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 20:55:15 -0000 [I found my E-mail records reporting successful builds using qemu-user-static from ports head -r484783 under FreeBSD head -r340287.] On 2018-Dec-22, at 00:10, Mark Millard wrote: > [I messed up the freebsd-emulation email address the first time I sent > this. I also forgot to indicate the qemu-user-static vintage = relationship.] >=20 > I had been reporting intermittent hang-ups for my = amd64->{aarch64,armv7} port cross > builds in another message sequence. But it turns out that one thing I = ran into > has hung-up every time, the same way, for amd64->armv7 cross builds: > multimedia/gstreamer1-qt@qt5 . So I extract the material here into a = separate report > with some updated notes. >=20 > A little context: I had built from ports head -r484783 before under = FreeBSD head > -r340287 (as I remember the version). Back then it did not have this = problem that it > now has under FreeBSD head -r341836 . One ports-specific change was to = force perl5.28 > as the default instead of perl5.26 originally. In fact this is what = drives what is > being rebuilt for my experiment that caught this. But I doubt the perl = version is > important to the problem. The context has a Ryzen Threadripper 1950X = and has been > tested both for FreeBSD under Hyper-V and for the same media = native-booted. Both > hang-up at the same point as seen via ps or top. The native tools for = cross-build > speedup were in use. Cross-builds targeting aarch64 did not get this = problem but > targeting armv7 did. 121 of 129 armv7 ports built before the hang-up = for the first > armv7 try. >=20 > ADDED: The qemu-user-static back with head -r340287 before installing = the > updated ports would likely be different than the -r484783 vintage. So = both > FreeBSD and qemu-user-static may have changed over the comparison. CORRECTION to ADDED: Back on 2018-Nov-11 I reported successful = cross-builds based on qemu-user-static from ports head -484783 --all built under = FreeBSD head -r340287 . So the use of the perl5.28 as the forced-default and the newer FreeBSD head version -r341836 as the context are the differences = here. > The hang-up: >=20 > In the port rebuilds targeting armv7, multimedia/gstreamer1-qt@qt5 = hung-up and timed > out. Looking during the wait in later tries shows something much like = (from one of the > examples): >=20 > root 33719 0.0 0.0 12920 3528 0 I 11:40 0:00.03 = | | `-- sh: poudriere[FBSDFSSDjailArmV7-default][02]: = build_pkg (gstreamer1-qt5-1.2.0_14) (sh) > root 41551 0.0 0.0 12920 3520 0 I 11:43 0:00.00 = | | `-- sh: poudriere[FBSDFSSDjailArmV7-default][02]: = build_pkg (gstreamer1-qt5-1.2.0_14) (sh) > root 41552 0.0 0.0 10340 1744 0 IJ 11:43 0:00.01 = | | `-- /usr/bin/make -C = /usr/ports/multimedia/gstreamer1-qt FLAVOR=3Dqt5 build > root 41566 0.0 0.0 10236 1796 0 IJ 11:43 0:00.00 = | | `-- /bin/sh -e -c (cd = /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build; if ! = /usr/bin/env QT_SELE > root 41567 0.0 0.0 89976 12896 0 IJ 11:43 0:00.07 = | | `-- /usr/local/bin/qemu-arm-static ninja -j28 -v = all > root 41585 0.0 0.0 102848 25056 0 IJ 11:43 0:00.10 = | | |-- /usr/local/bin/qemu-arm-static = /usr/local/bin/cmake -E cmake_autogen /wrkdirs/usr/ports/multimedia/g > root 41586 0.0 0.0 102852 25072 0 IJ 11:43 0:00.11 = | | `-- /usr/local/bin/qemu-arm-static = /usr/local/bin/cmake -E cmake_autogen /wrkdirs/usr/ports/multimedia/g >=20 > or as top showed it: >=20 > 41552 root 1 52 0 10M 1744K 0 wait 15 0:00 = 0.00% /usr/bin/make -C /usr/ports/multimedia/gstreamer1-qt FLAVOR=3Dqt5 = build > 41566 root 1 52 0 10M 1796K 0 wait 1 0:00 = 0.00% /bin/sh -e -c (cd = /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build; if ! = /usr/bin/env QT_SELECT=3Dqt5 QMAKEMODULES > 41567 root 2 52 0 88M 13M 0 select 4 0:00 = 0.00% /usr/local/bin/qemu-arm-static ninja -j28 -v all > 41585 root 2 52 0 100M 24M 0 kqread 8 0:00 = 0.00% /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E = cmake_autogen /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/. > 41586 root 2 52 0 100M 24M 0 kqread 22 0:00 = 0.00% /usr/local/bin/qemu-arm-static /usr/local/bin/cmake -E = cmake_autogen /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/. >=20 > So: waiting in kqread trying to run cmake. >=20 > Unlike some intermittent hang-ups, attaching-then-detaching via gdb = does not > resume the hung-up processes. Kills of the processes waiting on kqread = stop > the build. >=20 > Given the prior ports have been built already, building just > multimedia/gstreamer1-qt@qt5 still gets the hang-up at the same point. >=20 > Building anything that requires multimedia/gstreamer1-qt@qt5 seems to = be > solidly blocked in my environment. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sat Dec 22 21:03:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68795133BBB5 for ; Sat, 22 Dec 2018 21:03:24 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D301171787 for ; Sat, 22 Dec 2018 21:03:23 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9675D133BBB4; Sat, 22 Dec 2018 21:03:23 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73E12133BBB3 for ; Sat, 22 Dec 2018 21:03:23 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE9BF71784; Sat, 22 Dec 2018 21:03:21 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id aoQSghzaS82YcaoQUgpawX; Sat, 22 Dec 2018 14:03:14 -0700 X-Authority-Analysis: v=2.3 cv=NNSrBHyg c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=2ur7OfE09M0A:10 a=L0TlzgiqAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=pGLkceISAAAA:8 a=7Qk2ozbKAAAA:8 a=VxmjJ2MpAAAA:8 a=eh1Yez-EAAAA:8 a=A-AosRLH1ePmieniaj8A:9 a=CjuIK1q_8ugA:10 a=fspyDsK2fjUA:10 a=-RtknO9RM1QA:10 a=h1pxpgV1WlEA:10 a=IAVDLmJhbIOVeWgv0OxI:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=1lyxoWkJIXJV6VJUPhuM:22 a=7gXAzLPJhVmCkEl4_tsf:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id B739437E; Sat, 22 Dec 2018 13:03:12 -0800 (PST) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id wBML3CMZ053165; Sat, 22 Dec 2018 13:03:12 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id wBML3C8G053162; Sat, 22 Dec 2018 13:03:12 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201812222103.wBML3C8G053162@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Yuri Pankov cc: Cy Schubert , Mark Peek , Enji Cooper , Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , freebsd-current Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes In-Reply-To: Message from Yuri Pankov of "Sat, 22 Dec 2018 23:31:09 +0300." <0503b382-d886-39a4-d265-b43d8adc15c9@yuripv.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Dec 2018 13:03:12 -0800 X-CMAE-Envelope: MS4wfINTTBj6Uq5kaeXnHS2iNAgJf7q8vzLbOT58l9IpX1OqET8xDyN1kevTT3BQGnfUBAsN8wUNklpALh1MRVgGE2JeKViiUw1qWVq44B14WD7hxRJPS+Lp WaCgqEL0FDMvHdNK15E5KXfTEAir/7FsqFpqjudYv55uclZ/V8HBaaNynfBI6dpu01ycWFXTT8HZkxbW4upzgxCSqunOXqYeCgECTuk7EmQbB8aLUlPrbP+v e0MVD1Tbn4P/LT0ev2/su6vTJwu61W7x3h6zht+WlKSUAS2dYXzxwiJHHg+UlfDfM5TimzuvcCrnwXPPEpqTng== X-Rspamd-Queue-Id: EE9BF71784 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-4.46 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; REPLYTO_EQ_FROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.97)[-0.969,0]; RCPT_COUNT_SEVEN(0.00)[7]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-1.78)[ip: (-4.36), ipnet: 64.59.128.0/20(-2.47), asn: 6327(-1.98), country: CA(-0.09)]; RCVD_IN_DNSWL_LOW(-0.10)[137.136.59.64.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 21:03:24 -0000 In message <0503b382-d886-39a4-d265-b43d8adc15c9@yuripv.net>, Yuri Pankov write s: > This is an OpenPGP/MIME signed message (RFC 4880 and 3156) > --e7sW91Qf9WxzTaujtGEdAimN5k2EtpJ6Q > Content-Type: multipart/mixed; boundary="3a9zlXDI7Z2P48EdQkgwMdVOMQOEfR5Wm"; > protected-headers="v1" > From: Yuri Pankov > To: Cy Schubert > Cc: Mark Peek , Enji Cooper , > Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= > , freebsd-current > Message-ID: <0503b382-d886-39a4-d265-b43d8adc15c9@yuripv.net> > Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 > changes > References: <201812222027.wBMKRGWJ050853@slippy.cwsent.com> > In-Reply-To: <201812222027.wBMKRGWJ050853@slippy.cwsent.com> > > --3a9zlXDI7Z2P48EdQkgwMdVOMQOEfR5Wm > Content-Type: text/plain; charset=utf-8 > Content-Language: en-US > Content-Transfer-Encoding: quoted-printable > > Cy Schubert wrote: > > In message , Yuri=20 > > Pankov write > > s: > >> This is an OpenPGP/MIME signed message (RFC 4880 and 3156) > >> --NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH > >> Content-Type: multipart/mixed; boundary=3D"c7yUHUJpZYpJqOrOWLAb4sE3Rmh= > 2alrdi"; > >> protected-headers=3D"v1" > >> From: Yuri Pankov > >> To: Cy Schubert > >> Cc: Mark Peek , Enji Cooper , > >> Warner Losh , =3D?UTF-8?Q?Dag-Erling_Sm=3Dc3=3Db8rgra= > v?=3D > >> , freebsd-current > >> Message-ID: > >> Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8= > p1 > >> changes > >> References: <201812222009.wBMK9H5T050103@slippy.cwsent.com> > >> In-Reply-To: <201812222009.wBMK9H5T050103@slippy.cwsent.com> > >> > >> --c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi > >> Content-Type: text/plain; charset=3Dutf-8 > >> Content-Language: en-US > >> Content-Transfer-Encoding: quoted-printable > >> > >> Cy Schubert wrote: > >>> In message <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net>, Yuri=3D= > 20 > >>> Pankov write > >>> s: > >>>> Yuri Pankov wrote: > >>>>> In-Reply-To: ai=3D > >> > >>> l.gmail. > >>>>> com> > >>>>> Mark Peek wrote: > >>>>>> On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper > > >>> wro=3D3D > >>>>> te: > >>>>>> =3D3D20 > >>>>>>> > >>>>>>>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote= > : > >>>>>>>> > >>>>>>>> Mark Peek wrote: > >>>>>>>>> Thanks for the cc:. I forwarded the original report on to an=3D= > 20 > >>> interna=3D3D > >>>>> l > >>>>>>>>> VMware desktop product contact. > >>>>>>>> > >>>>>>>> Thank you. > >>>>>>>> > >>>>>>>>> What version of Workstation or Fusion is this occurring on? I=3D= > 20 > >>> saw > >>>>>>>>> Workstation 14 mentioned but curious if it occurs on=3D20 > >>> Workstation 15 > >>>>>>>>> (latest). > >>>>>>>> > >>>>>>>> Running the latest available for download: 15.0.2 build-10952284= > =2E > >>>>>>> > >>>>>>> This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it=3D= > 20 > >>> wasn=3D3DE2=3D3D > >>>>> =3D3D80=3D3D99t > >>>>>>> affecting me on 10.x. I didn=3D3DE2=3D3D80=3D3D99t install 11.0.0= > , so I=3D20 > >>> don=3D3DE2=3D3D80=3D3D99=3D3D > >>>>> t know if it > >>>>>>> affects that version... > >>>>>>> > >>>>>>> Thanks so much! > >>>>>>> > >>>>>>> -Enji > >>>>>> =3D3D20 > >>>>>> =3D3D20 > >>>>>> BTW, there appears to be a workaround here using -o=3D20 > >>> 'IPQoS=3D3D3Dthroughput=3D3D > >>>>> ' > >>>>>> (untested by me). I've seen the issue forwarded internally but no=3D= > 20 > >>> furth=3D3D > >>>>> er > >>>>>> discussions yet. > >>>>>> =3D3D20 > >>>>>> https://communities.vmware.com/thread/590825 > >>>> > >>>> Yes, that's exactly what the patch attached to original message does= > i=3D > >> f > >>>> we are running as a VMware guest. The workaround is known and it wo= > rk=3D > >> s, > >>>> but it's not immediately clear and I just wanted it to be the defaul= > t > >>>> for the time being. > >>> =3D20 > >>> The patch assumes VMWARE_GUEST_WORKAROUND unconditionally. Is this=3D= > 20 > >>> intended? > >> > >> It's the added code that is ifdef'ed VMWARE_GUEST_WORKAROUND, so it ca= > n > >> be ripped out easily when no longer needed, and yes, it's enabled > >> unconditionally for now. And the check itself is if 'kern.vm_guest' > >> reports 'vmware'. > >=20 > > It doesn't look that conditional to me. > > Indeed, and that's what I said exactly :-) The added code is enabled > unconditionally, and the added code also has a check for vmware guest. > The ifdefs are there only to show that this is local addition, nothing el= > se. > > I'm not saying it needs to be done this way, this is just something I > did quickly after installing yet another VM and forgetting to modify my > ~/.ssh/config to include the workaround. First and foremost a ticket with VMware should be opened. They really need to fix yet another regression. Regarding the Red Hat bugzilla bug, looks like they're doing the right thing by reaching out to VMware. This should be our position as well. Add it to ssh_config or sshd_config if one must but have VMware fix their bugs. Putting workarounds in our O/S to work around a bug in some other vendor's virtualization is something I don't support. If we must add the #ifdefs to our ssh, then add an UPDATING entry to say that to enable it put VMWARE_GUEST_WORKAROUND or however we choose to enable it in src.conf. This reminds me of an issue we had on Red Hat Linux last year (or was it the year before -- time just flies) which between VMware and HPE was causing serious performance impact. And before that a vmxnet3 issue that caused the Linux kernel to panic. In both cases RH did not change their distribution but offered workarounds until the other vendors had resolved the issues. RH is taking the same stance here. I think we should not patch our ssh but instead offer a workaround just as RH has. We, FreeBSD, should try to open a ticket or reach out to VMware to add a +1 to the issue that RH has already opened. This is the right thing to do. In this case we should consider ourselves an O/S vendor too, which BTW we are. BTW the 2018-11-08 entry in the RH bug talks about adding the workaround to sshd_config. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.