From owner-freebsd-stable@freebsd.org Mon May 13 00:18:20 2019 Return-Path: Delivered-To: freebsd-stable@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 D768D15A6445 for ; Mon, 13 May 2019 00:18:19 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660056.outbound.protection.outlook.com [40.107.66.56]) (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 7874E901B0 for ; Mon, 13 May 2019 00:18:18 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YQBPR0101MB2260.CANPRD01.PROD.OUTLOOK.COM (52.132.70.13) by YQBPR0101MB0707.CANPRD01.PROD.OUTLOOK.COM (52.132.73.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1878.22; Mon, 13 May 2019 00:18:16 +0000 Received: from YQBPR0101MB2260.CANPRD01.PROD.OUTLOOK.COM ([fe80::e92e:7851:66e9:3967]) by YQBPR0101MB2260.CANPRD01.PROD.OUTLOOK.COM ([fe80::e92e:7851:66e9:3967%7]) with mapi id 15.20.1878.024; Mon, 13 May 2019 00:18:16 +0000 From: Rick Macklem To: FreeBSD-STABLE Mailing List Subject: Patch to improve mountd performance for reload of exports Thread-Topic: Patch to improve mountd performance for reload of exports Thread-Index: AQHVCSCpzJASEVnoS0qc8B+A1Xp9Eg== Date: Mon, 13 May 2019 00:18:16 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 7741c85e-340e-4991-dc4f-08d6d7387ec1 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:YQBPR0101MB0707; x-ms-traffictypediagnostic: YQBPR0101MB0707: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 0036736630 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(366004)(346002)(376002)(136003)(39850400004)(199004)(189003)(52544003)(14454004)(99286004)(4744005)(7696005)(5660300002)(6916009)(316002)(25786009)(305945005)(786003)(46003)(76116006)(73956011)(186003)(66476007)(66946007)(478600001)(33656002)(64756008)(66556008)(66446008)(8676002)(486006)(102836004)(6506007)(476003)(8936002)(71200400001)(9686003)(74316002)(71190400001)(52536014)(74482002)(5024004)(2906002)(68736007)(55016002)(256004)(53936002)(81156014)(6436002)(86362001)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:YQBPR0101MB0707; H:YQBPR0101MB2260.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: xpGZsYQgeSwhfMnJqDlhxQQNdGUqrWw63I73EPuUhChwF4CTsCt5+UxHuWAOvnzZOfM8JT2OfaQr7M/cID3w6BVX0+2Q152I04DqxEu4as6xR62sx/gUZ9/rqlSKqMD+JIphuSnr9Y+uMtbR/uNCZ9psGYV2Q0J4NPETGviMmvxY4fD8NzIw2ZriNnlCH7lL53RUUAFJmzxQTPOXzMh+M2yoI3rvgTLGWbRViGkNsmoDq28vtAM1eGaFOSuuEVHWM/7LkqtSAq4nbOxSND9dWw+pER9/wxFvce9i0HJfifdwewyksKf8YB3Dm3JFt+p4wvclzLkaEXMWB2ZH258SSA0e3im+8o2RBnZlIqDHs8+5PsJj0xXsJzX5zjhtg13ZWlrM6rB+8wpPvQJheO6FtXMPKaC/5LkesMRsS/ldfKA= 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: 7741c85e-340e-4991-dc4f-08d6d7387ec1 X-MS-Exchange-CrossTenant-originalarrivaltime: 13 May 2019 00:18:16.3278 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: YQBPR0101MB0707 X-Rspamd-Queue-Id: 7874E901B0 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of rmacklem@uoguelph.ca designates 40.107.66.56 as permitted sender) smtp.mailfrom=rmacklem@uoguelph.ca X-Spamd-Result: default: False [-4.20 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[uoguelph.ca]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-0.99)[ipnet: 40.64.0.0/10(-2.70), asn: 8075(-2.22), country: US(-0.06)]; TO_DN_ALL(0.00)[]; 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]; NEURAL_HAM_SHORT(-0.90)[-0.896,0]; RCVD_IN_DNSWL_NONE(0.00)[56.66.107.40.list.dnswl.org : 127.0.3.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)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 May 2019 00:18:20 -0000 Hi, I have created PR#237860 to keep track of a patch I have to try and improve the performance of mountd when reloading exports for an NFS server with a lot of file systems. Peter reported that the nfsd threads would be stalled = for 16sec when exports were reloaded (via SIGHUP) for his file server with 7200= 0+ file systems on it. Peter will be testing this patch, but I would appreciate it if anyone else = can test it as well. It doesn't matter if your NFS file server only exports a few fi= le systems, because I would like to find out if the patch results in any regressions. (The new capability of incrementally updating the exports in the kernel upo= n a reload is only enabled if mountd is started with the new "-I" option the = patch adds.) If anyone can test the patch (it is the attachment in the PR), please let m= e know how it goes. Thanks, rick From owner-freebsd-stable@freebsd.org Wed May 15 01:13:33 2019 Return-Path: Delivered-To: freebsd-stable@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 05D5315A367F for ; Wed, 15 May 2019 01:13:33 +0000 (UTC) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.sub.de [IPv6:2001:1440:5001:1::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "uucp.dinoex.sub.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0989C69E43 for ; Wed, 15 May 2019 01:13:28 +0000 (UTC) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.sub.de [194.45.71.2]) by uucp.dinoex.org (8.16.0.41/8.16.0.41) with ESMTPS id x4F1D6p6060222 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Wed, 15 May 2019 03:13:07 +0200 (CEST) (envelope-from li-fbsd@citylink.dinoex.sub.org) X-MDaemon-Deliver-To: Received: from citylink.dinoex.sub.org (uucp@localhost) by uucp.dinoex.sub.de (8.16.0.41/8.16.0.41/Submit) with UUCP id x4F1D6Wo060221 for freebsd-stable@FreeBSD.ORG; Wed, 15 May 2019 03:13:06 +0200 (CEST) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from gate.oper.dinoex.org (gate-e [192.168.98.2]) by citylink.dinoex.sub.de (8.15.2/8.15.2) with ESMTP id x4F0OMnM069912 for ; Wed, 15 May 2019 02:24:22 +0200 (CEST) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from gate.oper.dinoex.org (gate-e [192.168.98.2]) by gate.oper.dinoex.org (8.15.2/8.15.2) with ESMTP id x4F0O2Fb069738 for ; Wed, 15 May 2019 02:24:03 +0200 (CEST) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: (from news@localhost) by gate.oper.dinoex.org (8.15.2/8.15.2/Submit) id x4F0O2vg069737 for freebsd-stable@FreeBSD.ORG; Wed, 15 May 2019 02:24:02 +0200 (CEST) (envelope-from li-fbsd@citylink.dinoex.sub.org) X-Authentication-Warning: gate.oper.dinoex.org: news set sender to li-fbsd@citylink.dinoex.sub.org using -f From: Peter Subject: kernel crash from adjacent partitions (gpart, zfs) Date: Wed, 15 May 2019 02:10:16 +0200 Organization: even some more stinky socks Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 15 May 2019 00:10:57 -0000 (UTC) Injection-Info: oper.dinoex.de; logging-data="67354"; mail-complaints-to="usenet@citylink.dinoex.sub.org" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 X-Mozilla-News-Host: news://localhost:119 Sender: li-fbsd@citylink.dinoex.sub.org To: freebsd-stable@FreeBSD.ORG X-Milter: Spamilter (Reciever: uucp.dinoex.sub.de; Sender-ip: 194.45.71.2; Sender-helo: uucp.dinoex.sub.de; ) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (uucp.dinoex.org [194.45.71.2]); Wed, 15 May 2019 03:13:10 +0200 (CEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 01:13:33 -0000 Hi, when creating partitions directly adjacent without a safety free space between them, the kernel may crash. Does anybody know how big that free space needs to be? How I found out (and how to reproduce the crash): https://forums.freebsd.org/threads/create-degraded-raid-5-with-2-disks-on-freebsd.70750/post-426756 OS concerned: 11.2, amd64 and i386. Or, does anybody know if this is fixed in 12? From owner-freebsd-stable@freebsd.org Wed May 15 07:24:26 2019 Return-Path: Delivered-To: freebsd-stable@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 26CE815AD6CB for ; Wed, 15 May 2019 07:24:26 +0000 (UTC) (envelope-from support@marmac.nl) Received: from mx5.mijnspamfilter.nl (mx5.mijnspamfilter.nl [37.48.83.136]) (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 6829C76E6A; Wed, 15 May 2019 07:24:21 +0000 (UTC) (envelope-from support@marmac.nl) Received: from [94.124.95.194] (helo=[127.0.0.1]) by mx5.mijnspamfilter.nl with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1hQoGq-0008Ng-NC; Wed, 15 May 2019 09:24:13 +0200 Message-ID: <83b0faf45215018532d82894acd72060@swift.generated> Date: Wed, 15 May 2019 07:23:15 +0000 Subject: (#2572022) Ticket gesloten door support From: =?UTF-8?B?TWFyTWFj?= To: freebsd-stable@freebsd.org Cc: errata-notices@freebsd.org MIME-Version: 1.0 X-Originating-IP: 94.124.95.194 X-SpamExperts-Domain: prima-it.nl X-SpamExperts-Username: supportpal X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: SB/global_tokens (0.00176852475451) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0XJZQFAmqAilMiozUWhfaCSpSDasLI4SayDByyq9LIhVKatYhaRFhmgI Ur4feUK1S0TNWdUk1Ol2OGx3IfrIJKyP9eGNFz9TW9u+Jt8z2T3KIvQHr/Y4gcPcWtzctnXaDqhl XavMTkgitliU64dEUA9G+uYQsJRIbwAAqBDad5pV3ACwUsyiPQ0SpaggCqkBziJet/5v+ZsXWr4e ZJvd2SfJjWZKm5jqM5KAKYJUkIEJv1OZq1WygSVBSKfkP8jtyxFqVaqdS+jxzMo65Uql0DXLnFFp slzlZw8qdBf2jEI7zSFLtj3wfjHGaq2zCfOe0FdWi9Yv/bCV/ZLLarbYl45OKOhu19vnHnkFxfR5 z2sYf0cnVwbwxyMyZnCDJmCieRLZ8URFrivgdwjOQrRU+1H7Jnb9qYX5S1ajQI9O+NabgqLpwMb+ 1rKXpdIT0eB0YNm18OiGlc6NtWUdUWp/E6MHPCNOxUxXI6XX1/yXK/O3fin0GiibdwQ1hqZVJgbL dpBC037EDRYhhWtZien7t7pIF0PsjArDxhLBlNmLk9GM28m6JjUulA4T7VAQQPKyrHCOfte63+Vd qCyh13mqo4NMWLBylTh/LPvmPGlT3xE8aIfVaCHpEB6cFH6WJxE4ZnLC6kUG6rJ4BrkP8X8PSfkt /pyZT/33ANB502EwqmCtzWaM70rplmEFD6EoY9t2vTCtF4dhFijZbOx5jK6xbsj1GsrUqsMGNQPH SwoUEuVLyk18GjosFe+UErw+G9g2RLPbaivpcR8bupDyqIGJuyIsWwQrwZ4hEN0TRsk7naqZQXyL 2rEpatDmglOGdUKLUSG7X+t1TW39Ja77LGPpOwBgAyxzfG4UOHK3SD7PXT7ZX4SWKZb/sjmEqY4E J/fJxjVSkTL6JlcnGcSy5rPt7Aj3LLIYpmFyKlJO1faZMzIsqF+3vNCO90DVE8LxbiRFFFtMe2XI zAzAGpYFdcl8M0XbsOhkH12sY/x7N04LPZqYsSuNxAAlTncZJIQ9WAM/xjEvuGslKTrRIXcXpFg5 ivY= X-Report-Abuse-To: spam@mx1.mijnspamfilter.nl X-Rspamd-Queue-Id: 6829C76E6A X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; spf=softfail (mx1.freebsd.org: 37.48.83.136 is neither permitted nor denied by domain of support@marmac.nl) smtp.mailfrom=support@marmac.nl X-Spamd-Result: default: False [2.31 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_XOIP(0.00)[]; FROM_EXCESS_BASE64(1.50)[]; TO_DN_NONE(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; MX_GOOD(-0.01)[marmac-nl.mail.protection.outlook.com,marmac-nl.mail.protection.outlook.com]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:60781, ipnet:37.48.64.0/18, country:NL]; IP_SCORE(0.11)[asn: 60781(0.55), country: NL(0.01)]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.11)[0.110,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[marmac.nl]; NEURAL_SPAM_MEDIUM(0.62)[0.617,0]; NEURAL_SPAM_LONG(0.08)[0.084,0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 07:24:26 -0000 -#-#- Antwoord u boven deze lijn alstublieft -#-#- Beste freebsd-stabl= e@freebsd.org, Uw ticket is gesloten door een supportmedewerker. Indie= n u van mening bent dat het probleem niet volledig is opgelost, dan kunt u = antwoorden op deze e-mail. Your ticket has been marked as resolved by a m= ember of our staff. If you do not believe that this issue has been adequate= ly resolved, you may still reply to this ticket and an operator will respon= d shortly. You can review the ticket by going to: https://support.marmac.= nl/nl/tickets/view/2572022?token=3Dbbc117f8dea7bbe09d749a28bcddea263cefce3b= --------------------------------------------------------------- fre= ebsd-stable@freebsd.org User - 15/05/2019 02:45 -----BEGIN PGP SIGNED M= ESSAGE----- Hash: SHA512 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D FreeBSD-EN-19:10.scp Errata Notic= e The FreeBSD Project Topic: Insufficient filename validation in scp= (1) client Category: contrib Module: scp Announced: 2019-05-14 A= ffects: All supported versions of FreeBSD. Corrected: 2019-05-07 19:48:39= UTC (stable/12, 12.0-STABLE) 2019-05-14 22:54:17 UTC (releng/12.0, 12.0-= RELEASE-p10) CVE Name: CVE-2019-6111 For general information regardi= ng FreeBSD Errata Notices and Security Advisories, including descriptions= of the fields above, security branches, and the following sections, plea= se visit . I. Background scp= (1) is a file transfer protocol running over an SSH session. II. Probl= em Description The scp(1) client implementation fails to verify if the= objects returned by the server match what was requested. III. Impac= t A malicious scp server can write arbitrary files to the client. = IV. Workaround Switch to using the sftp(1) client, if possible. = V. Solution Note: While stable/11 and its release branches are curr= ently affected by this errata, due to the lack of patches, no fix is curr= ently available for stable/11. We are currently evaluating a backport for= these fixes to stable/11. Perform one of the following: 1) Upg= rade your system to a supported FreeBSD stable or release / security bran= ch (releng) dated after the correction date. 2) To update your system = via a binary patch: Systems running a RELEASE version of FreeBSD on th= e i386 or amd64 platforms can be updated via the freebsd-update(8) utilit= y: # freebsd-update fetch # freebsd-update install 3) To update= your system via a source code patch: The following patches have been = verified to apply to the applicable FreeBSD release branches. a) Dow= nload the relevant patch from the location below, and verify the detached= PGP signature using your PGP utility. [FreeBSD 12.0] # fetch https:= //security.FreeBSD.org/patches/EN-19:10/scp.patch # fetch https://securit= y.FreeBSD.org/patches/EN-19:10/scp.patch.asc # gpg --verify scp.patch.asc= b) Apply the patch. Execute the following commands as root: # cd= /usr/src # patch < /path/to/patch c) Recompile the operating system= using buildworld and installworld as described in . VI. Correction details The follo= wing list contains the correction revision numbers for each affected bran= ch. Branch/path Revision - -----------------------------------------= -------------------------------- stable/12/ r347232 releng/12.0/ r34758= 6 - ---------------------------------------------------------------------= ---- To see which files were modified by a particular revision, run th= e following command, replacing NNNNNN with the revision number, on a ma= chine with Subversion installed: # svn diff -cNNNNNN --summarize svn:/= /svn.freebsd.org/base Or visit the following URL, replacing NNNNNN wit= h the revision number: VII. References The latest revision of th= is advisory is available at -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9= FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAlzbTq1fFIAAAAAALgAo aXNzdWVyLWZwckBub3Rh= dGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD MEU4NzhBRTVBRkU3ODgwMjhENjM1= NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n 5cJXGQ/+Ii19QUq6MdSeNPPOHVTtW8G/FIls= aYYlCFooIvzxYxvcqDcCyabVlX/a Lt815YY7+EbKcSbA0Gh/YFm9S05rwUg4Dnj8nIQwMVp9= OEtziIdY6TVU0JhRoUpe +YVG9e5eh8wK7FFJ/jIaZbAcr2MfMYV2KPouA1HZdqsMBkAkr8xu= S3HrmkeE0nxo 6QHTWaaD7qvr8foUSHS1hJsAX3+1eIsdytGUTJIGeL6g7DWsLYYiX7v2k+eZ= uSe1 dkt7/3J+RqpyJAv+LfGh3QnILC52fO7jOVlnOBt5H/HefX+xRdb8lwHfoBeyxIFc N= 4v4Ecypewci6Hv4moTeZF+FtIETHj3EfPIe04eiikiGhrpGQ4cCveK6+kk49x4m RR7TE+y7k= lGIfoSuxoooaJ1/UyFJ9T0eICmBUh1B5rcrnwbbhgpXVPpbbee7IFL2 HYiEuDECPN45zek+b= L0M5D0wHZc823e7p1Ioxl1NNzawdts7hWwIpNmFTlfWNczQ KZ9y0bDFffK3nuUkMHORLagCM= 6ou/wAPunsnWXY3Xg3X61svYIvZThDIeeOi9SbF d1ve8/H/t5yHRQBpqWk51FfO4RdPmQAo6= Y9w9WzhnkETsNXeTruQq7D8SnOaWgXG JUh9PAVQKcJRWPXVwDTPEsqRgaDVB0gpaPCt5IS2j= 2tyB8UuAd4=3D =3D2h+W -----END PGP SIGNATURE----- ___________________= ____________________________ freebsd-announce@freebsd.org mailing list = https://lists.freebsd.org/mailman/listinfo/freebsd-announce To unsubscrib= e, send any mail to "freebsd-announce-unsubscribe@freebsd.org" ----------= ----------------------------------------------------- Ticket Details= Ticket #: 2572022 Subject: [FreeBSD-Announce] FreeBSD Errata Notice Fr= eeBSD-EN-19:10.scp Department: Support | Marmac Status: Gesloten Prio= rity: Laag You can review the ticket by going to: https://support.ma= rmac.nl/nl/tickets/view/2572022?token=3Dbbc117f8dea7bbe09d749a28bcddea263ce= fce3b Kind Regards, MarMac From owner-freebsd-stable@freebsd.org Wed May 15 07:24:25 2019 Return-Path: Delivered-To: freebsd-stable@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 ECB4215AD6C9 for ; Wed, 15 May 2019 07:24:24 +0000 (UTC) (envelope-from support@marmac.nl) Received: from mx5.mijnspamfilter.nl (mx5.mijnspamfilter.nl [37.48.83.136]) (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 6837F76E6C; Wed, 15 May 2019 07:24:21 +0000 (UTC) (envelope-from support@marmac.nl) Received: from [94.124.95.194] (helo=[127.0.0.1]) by mx5.mijnspamfilter.nl with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1hQoGx-0008P1-IY; Wed, 15 May 2019 09:24:20 +0200 Message-ID: <9d54d4addd4e59e979635e60d17430a5@swift.generated> Date: Wed, 15 May 2019 07:23:22 +0000 Subject: (#3759419) Ticket gesloten door support From: =?UTF-8?B?TWFyTWFj?= To: freebsd-stable@freebsd.org Cc: errata-notices@freebsd.org MIME-Version: 1.0 X-Originating-IP: 94.124.95.194 X-SpamExperts-Domain: prima-it.nl X-SpamExperts-Username: supportpal X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: Combined (0.03) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0XJZQFAmqAilMiozUWhfaCSpSDasLI4SayDByyq9LIhVYx18WN9zSM2z sLYkPlRIukTNWdUk1Ol2OGx3IfrIJKyP9eGNFz9TW9u+Jt8z2T3KIvQHr/Y4gcPcWtzctnXaDqhl XavMTkgitliU64dEUA9G+uYQsJRIbwAAqBDad5pV3ACwUsyiPQ0SpaggCqkBzvJsKKVsPKcsg2aw sGkatqApTT0JjnHmua2Cz26Um1dPv1OZq1WygSVBSKfkP8jtyxFqVaqdS+jxzMo65Uql0DXLnFFp slzlZw8qdBf2jEI7zSFLtj3wfjHGaq2zCfOe0FdWi9Yv/bCV/ZLLarbYl45OKOhu19vnHnkFxfR5 z2sYf0cnVwbwxyMyZnCDJmCieRLZ8URFrivgdwjOQrRU+1H7Jnb9qYX5S1ajQI9O+NabgqLpwMb+ 1rKXpdIT0eB0YG6GQ+bzxXvOKSUBpOXX2xT3X3F4C87GN5ARwvmU2Zd0uOLGGtTgzgmcyvxTMr8Q 80bRt/qZvKOlFNKeGzAR+rBWh1LsvgIaWHmdiqF4hbi2BC83BsQ4JD3u3keqrKTTUBoy4RjAUqxX X/HQWz77aicBIkUL/j1Y48GvmeURQjjETFoZE11keg7DwlClMBp6X6AaXVo/EC2K+bDeFIM9LXv1 KvdxpQs8Ycs/cbrYsRMBlJfEURT7yTsdTm7VjCIUHPsKx5FZ7eqPslYdTEyF4IosaJ0KCyitWwwW YiOBcFFrKtoc6cymroq21GaEfQcPCzP9IP39YzjAUNiVJKIcaiKaIas3cIYBSUf12qbYTLeytQyc LwV+wK/merQw3ZE+PYH7OIeOHqNHMFs6yqJUpYC/ON3T8omjTopJj826j7plAWG+VxTSKPReY+TB lRwklpdlaFFcJtLwFa1Rsque/NvDcadKmebwzWm14b1KYWJLRXz4VIsOBe5vlLQt1EGcVGt8+4DJ C/0/7SrgpWB1PKPiZxW09RWmsIatSYvwAYGd X-Report-Abuse-To: spam@mx1.mijnspamfilter.nl X-Rspamd-Queue-Id: 6837F76E6C X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; spf=softfail (mx1.freebsd.org: 37.48.83.136 is neither permitted nor denied by domain of support@marmac.nl) smtp.mailfrom=support@marmac.nl X-Spamd-Result: default: False [2.31 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_XOIP(0.00)[]; FROM_EXCESS_BASE64(1.50)[]; TO_DN_NONE(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; MX_GOOD(-0.01)[marmac-nl.mail.protection.outlook.com,marmac-nl.mail.protection.outlook.com]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:60781, ipnet:37.48.64.0/18, country:NL]; IP_SCORE(0.11)[asn: 60781(0.55), country: NL(0.01)]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.11)[0.110,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[marmac.nl]; NEURAL_SPAM_MEDIUM(0.61)[0.615,0]; NEURAL_SPAM_LONG(0.08)[0.085,0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 07:24:25 -0000 -#-#- Antwoord u boven deze lijn alstublieft -#-#- Beste freebsd-stabl= e@freebsd.org, Uw ticket is gesloten door een supportmedewerker. Indie= n u van mening bent dat het probleem niet volledig is opgelost, dan kunt u = antwoorden op deze e-mail. Your ticket has been marked as resolved by a m= ember of our staff. If you do not believe that this issue has been adequate= ly resolved, you may still reply to this ticket and an operator will respon= d shortly. You can review the ticket by going to: https://support.marmac.= nl/nl/tickets/view/3759419?token=3D852ccf79da96df0d5f7bee1d93a70dc9f58f6f14= --------------------------------------------------------------- fre= ebsd-stable@freebsd.org User - 15/05/2019 02:30 -----BEGIN PGP SIGNED M= ESSAGE----- Hash: SHA512 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D FreeBSD-EN-19:09.xinstall Errata = Notice The FreeBSD Project Topic: install(1) broken with partially m= atching relative paths Category: core Module: xinstall Announced: = 2019-05-14 Affects: All supported versions of FreeBSD Corrected: 2019-0= 2-16 04:48:30 UTC (stable/12, 12.0-STABLE) 2019-05-14 22:51:49 UTC (relen= g/12.0, 12.0-RELEASE-p4) 2019-02-16 04:49:10 UTC (stable/11, 11.3-PRERELE= ASE) 2019-05-14 22:51:49 UTC (releng/11.2, 11.2-RELEASE-p10) For gen= eral information regarding FreeBSD Errata Notices and Security Advisories= , including descriptions of the fields above, security branches, and the = following sections, please visit . = I. Background The install(1) utility installs files and links, opti= onally calculating relative paths for an installed symbolic link. II= . Problem Description Due to an issue in the way install(1) determines= common components of the source and target paths, the relative link may = be incorrectly calculated and drop a component of the link because a part= ial match existed on that component. III. Impact The ports tree= and other software very frequently use install(1) to create relative sym= links without checking whether a partial match of the path exists that wo= uld result in such a truncation. IV. Workaround No workaround is = available, but using install(1) to install non-relative links and files i= s unaffected. V. Solution Perform one of the following: 1) U= pgrade your system to a supported FreeBSD stable or release / security br= anch (releng) dated after the correction date. 2) To update your syste= m via a binary patch: Systems running a RELEASE version of FreeBSD on = the i386 or amd64 platforms can be updated via the freebsd-update(8) util= ity: # freebsd-update fetch # freebsd-update install 3) To upda= te your system via a source code patch: The following patches have bee= n verified to apply to the applicable FreeBSD release branches. a) D= ownload the relevant patch from the location below, and verify the detach= ed PGP signature using your PGP utility. # fetch https://security.Free= BSD.org/patches/EN-19:09/xinstall.patch # fetch https://security.FreeBSD.= org/patches/EN-19:09/xinstall.patch.asc # gpg --verify xinstall.patch.asc= b) Apply the patch. Execute the following commands as root: # cd= /usr/src # patch < /path/to/patch c) Recompile the operating system= using buildworld and installworld as described in . VI. Correction details The follo= wing list contains the correction revision numbers for each affected bran= ch. Branch/path Revision - -----------------------------------------= -------------------------------- stable/12/ r344205 releng/12.0/ r34758= 5 stable/11/ r344206 releng/11.2/ r347585 - -------------------------= ------------------------------------------------ To see which files we= re modified by a particular revision, run the following command, replacin= g NNNNNN with the revision number, on a machine with Subversion installed= : # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base Or v= isit the following URL, replacing NNNNNN with the revision number: V= II. References The latest revision of this advisory is available at -= ----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5= cIFAlzbTqhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvc= nNlbWFuLm5ldEZD MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ0= 5eS9J6n 5cJV2RAAjFslsJRGQlL5piJPcAixaQO3gEgmaAp+q79whcsN3O8cqQpApU0BApTA= cT7cNnm3/sMteHFd6wCTLsssBnDsTWYxqccOeUIiCIgpXXkP67XYpLxxjBZqq5Tn egFes= jpZdu2yr+0gdRrpf54msed7ts8E0dDVoGIYeGhU7omIqlYWJGJfsZ4tg1La Mod40JgxXcHMT= ca7Et46LBu/j/cF5MeQhzIepRrj1awiElQY/dMesmJwD9AuYL9m cuS7yTH4eC6A/b7TdhUXB= qBTbNipUCmwUuIWJ6OxpcrKPrtv/qGhUCEDdsNvMxpA i8ciQY4YD06wdmZP+9Ugp/qXMXpLl= xzwHrUYPe/Xn6/NvUgMp+KyMWgfkmtPBuIl YKRTp5S4ZAs6U7RPSOMUWmQ2bWh0yZqEaQXAg= zzNwIpqdghrZj73krr99pCeWc81 1MWv6K9/ZMdm8i31Iur3Mz/4hkv5WQSObU9SdjigtvFGu= 5ldVEJzE5f3Zu9Vr5ja keCB1HVYtU25ekngLYPdFiVf9B/HAWwHugOyeZNV2jPB6VVSeFkye= icm8zZ95G63 Ww0BQbc830AFYlhb6DpciaP1Epokywr+wO4O+I3DRN3K6Zi47ODv7881milM8= KQO jWYn0kemMIgnz0R0ZluU/I5SU1cnXbWZuKvsw9efd++irqEHrBw=3D =3Dt05i --= ---END PGP SIGNATURE----- _______________________________________________= freebsd-announce@freebsd.org mailing list https://lists.freebsd.org/ma= ilman/listinfo/freebsd-announce To unsubscribe, send any mail to "freebsd= -announce-unsubscribe@freebsd.org" --------------------------------------= ------------------------- Ticket Details Ticket #: 3759419 Subject= : [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-19:09.xinstall Depa= rtment: Support | Marmac Status: Gesloten Priority: Laag You can r= eview the ticket by going to: https://support.marmac.nl/nl/tickets/view/3= 759419?token=3D852ccf79da96df0d5f7bee1d93a70dc9f58f6f14 Kind Regards,= MarMac From owner-freebsd-stable@freebsd.org Wed May 15 14:25:52 2019 Return-Path: Delivered-To: freebsd-stable@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 2FA131592B70 for ; Wed, 15 May 2019 14:25:52 +0000 (UTC) (envelope-from jhs@berklix.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 A26648D336 for ; Wed, 15 May 2019 14:25:51 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6092E1592B6D; Wed, 15 May 2019 14:25:51 +0000 (UTC) Delivered-To: stable@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 4EA7B1592B69; Wed, 15 May 2019 14:25:51 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "slim.berklix.org", Issuer "slim.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F3C708D32C; Wed, 15 May 2019 14:25:47 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CF95.dip0.t-ipconnect.de [46.82.207.149]) (authenticated bits=128) by slim.berklix.org (8.15.2/8.15.2) with ESMTPSA id x4FEPaEB019318 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2019 16:25:40 +0200 (CEST) (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 x4FEPZX2071746; Wed, 15 May 2019 16:25:35 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id x4FEPNqk065975; Wed, 15 May 2019 16:25:35 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201905151425.x4FEPNqk065975@fire.js.berklix.net> To: core@freebsd.org cc: hackers@freebsd.org, stable@freebsd.org Subject: FreeBSD flood of 8 breakage announcements in 3 mins. From: "Julian H. Stacey" Organization: http://berklix.com/jhs http://stolenvotes.uk User-agent: EXMH on FreeBSD http://www.berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ Date: Wed, 15 May 2019 16:25:23 +0200 X-Rspamd-Queue-Id: F3C708D32C X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.08 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.88)[0.884,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.38)[0.375,0]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(0.17)[ip: (0.62), ipnet: 94.185.88.0/22(0.31), asn: 33824(-0.08), country: DE(-0.01)]; MX_GOOD(-0.01)[slim.berklix.com]; NEURAL_SPAM_LONG(0.76)[0.759,0]; RCVD_IN_DNSWL_NONE(0.00)[68.90.185.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[149.207.82.46.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:33824, ipnet:94.185.88.0/22, country:DE]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 14:25:52 -0000 Hi core@, cc hackers@ & stable@ PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html Volunteers who contribute actual fixes are very much appreciated; But those styled as 'management' who delay announcements to batch floods damage us. As they've previously refused to stop, it's time to sack them. Just send each announcement out when ready, no delays to batch them. No sys admins can deal with 8 in 3 mins: Especially on multiple systems & releases. Recipients start mitigating, then more flood in, & need review which are most urgent to interrupt to; While also avoiding sudden upgrades to many servers & releases, to minimise disturbing server users, bosses & customers. Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. From owner-freebsd-stable@freebsd.org Wed May 15 14:32:48 2019 Return-Path: Delivered-To: freebsd-stable@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 05DC1159336F for ; Wed, 15 May 2019 14:32:48 +0000 (UTC) (envelope-from asomers@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 37B9C8DBE6 for ; Wed, 15 May 2019 14:32:47 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id ED0F2159336A; Wed, 15 May 2019 14:32:46 +0000 (UTC) Delivered-To: stable@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 DB5AC1593368; Wed, 15 May 2019 14:32:46 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf1-f54.google.com (mail-lf1-f54.google.com [209.85.167.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5543D8DBDE; Wed, 15 May 2019 14:32:46 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf1-f54.google.com with SMTP id y10so9570lfl.3; Wed, 15 May 2019 07:32:46 -0700 (PDT) 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=q2skSffZtfo+RM9AdGna71az9dWIc1aqxTmw/BajE94=; b=g8GcZJNujHfwabbOY5aj5b9G1PC6fByBvmQdc6n5l5ZRUz4ftperKkNeE/C5sdNHib AywNENHKuE5p2bsffqW/MAgPW1QQSpXl7KcbP4xJix6O7zfaIZwOXpM5GBHoz7T+sSz3 4ZIN1rmRiml4B46sIJfRLl9HDJCyIPG5px+nRMJaTEKypeAOvF71xRICQSIoWlJmXqgQ 2cVM+K7EGOvQU/p8MIWmSPVdM3DUaCGOvtWJfES5SaQzvcMICWe0xn6QloQl9q9q4+zS JRP65NBL7FnpdVpnisbRV1or55o9uNmxXNWt7SncifAQDtqSYhDCxR+JTzKrJsqqH3I7 Rm1g== X-Gm-Message-State: APjAAAVSof8wOGgT2KKjYA+pr3n8th76/jfl0pQVJU4/CKCEGtlZknzr 1Kw1gk1vnRUJ2QVz6w/EsoWypiMorqWgwe7jEMFUqpQN X-Google-Smtp-Source: APXvYqzFs9TjC4aLSUKPq6L4seAhBhlqimhnIycqOcE9ojTDQzhPWdKQitz4pj3D51bdhITX+dWhuRd7BBpeJRXAAwE= X-Received: by 2002:a19:5015:: with SMTP id e21mr21251288lfb.62.1557930758725; Wed, 15 May 2019 07:32:38 -0700 (PDT) MIME-Version: 1.0 References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> In-Reply-To: <201905151425.x4FEPNqk065975@fire.js.berklix.net> From: Alan Somers Date: Wed, 15 May 2019 08:32:26 -0600 Message-ID: Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: "Julian H. Stacey" Cc: FreeBSD Core Team , FreeBSD Stable ML , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 5543D8DBDE X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.95 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.95)[-0.947,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 14:32:48 -0000 On Wed, May 15, 2019 at 8:26 AM Julian H. Stacey wrote: > > Hi core@, > cc hackers@ & stable@ > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > Volunteers who contribute actual fixes are very much appreciated; > But those styled as 'management' who delay announcements to batch floods > damage us. As they've previously refused to stop, it's time to sack them. > > Just send each announcement out when ready, no delays to batch them. > No sys admins can deal with 8 in 3 mins: > Especially on multiple systems & releases. Recipients start > mitigating, then more flood in, & need review which are > most urgent to interrupt to; While also avoiding sudden upgrades > to many servers & releases, to minimise disturbing server users, > bosses & customers. > > Cheers, > Julian > -- > Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent > http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. > Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. I disagree, Julian. I think SAs are easier to deal with when they're batched. True, I can't fix the first one in less than 3 minutes. But then I probably wouldn't even notice it that fast. Batching them all together means fewer updates and reboots. -Alan From owner-freebsd-stable@freebsd.org Wed May 15 14:33:21 2019 Return-Path: Delivered-To: freebsd-stable@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 7D1F61593441 for ; Wed, 15 May 2019 14:33:21 +0000 (UTC) (envelope-from pi@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 1E21D8DC8F for ; Wed, 15 May 2019 14:33:21 +0000 (UTC) (envelope-from pi@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D33AF159343C; Wed, 15 May 2019 14:33:20 +0000 (UTC) Delivered-To: stable@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 C1EC9159343A for ; Wed, 15 May 2019 14:33:20 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 551E18DC8C for ; Wed, 15 May 2019 14:33:20 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hQuy9-000ObA-Cg; Wed, 15 May 2019 16:33:21 +0200 Date: Wed, 15 May 2019 16:33:21 +0200 From: Kurt Jaeger To: "Julian H. Stacey" Cc: stable@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <20190515143321.GZ72200@home.opsec.eu> References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201905151425.x4FEPNqk065975@fire.js.berklix.net> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 14:33:21 -0000 Hi! > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > Volunteers who contribute actual fixes are very much appreciated; > But those styled as 'management' who delay announcements to batch floods > damage us. 8 announcements and one freebsd-update is easier on the admin and the re-team than 8 announcements and 8 freebsd-update runs. That's probably why they are batched. Because all of the fixes are bundled in one update. If the re-team-capacity is limited, what would be the alternative? -- pi@opsec.eu +49 171 3101372 One year to go ! From owner-freebsd-stable@freebsd.org Wed May 15 15:32:34 2019 Return-Path: Delivered-To: freebsd-stable@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 D5E0B159592B for ; Wed, 15 May 2019 15:32:33 +0000 (UTC) (envelope-from jhs@berklix.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 58AE3906C8 for ; Wed, 15 May 2019 15:32:33 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1CF3E159592A; Wed, 15 May 2019 15:32:33 +0000 (UTC) Delivered-To: stable@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 0B3CF1595929 for ; Wed, 15 May 2019 15:32:33 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "slim.berklix.org", Issuer "slim.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2603A906B1; Wed, 15 May 2019 15:32:28 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CF95.dip0.t-ipconnect.de [46.82.207.149]) (authenticated bits=128) by slim.berklix.org (8.15.2/8.15.2) with ESMTPSA id x4FFWMRR019861 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2019 17:32:26 +0200 (CEST) (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 x4FFWL1i072177; Wed, 15 May 2019 17:32:21 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id x4FFW9SD066919; Wed, 15 May 2019 17:32:21 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201905151532.x4FFW9SD066919@fire.js.berklix.net> To: Kurt Jaeger cc: stable@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. From: "Julian H. Stacey" Organization: http://berklix.com/jhs http://stolenvotes.uk User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Wed, 15 May 2019 16:33:21 +0200." <20190515143321.GZ72200@home.opsec.eu> Date: Wed, 15 May 2019 17:32:09 +0200 X-Rspamd-Queue-Id: 2603A906B1 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.64 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.64)[0.643,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.26)[0.256,0]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(0.16)[ip: (0.60), ipnet: 94.185.88.0/22(0.30), asn: 33824(-0.07), country: DE(-0.01)]; MX_GOOD(-0.01)[cached: slim.berklix.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[68.90.185.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(0.68)[0.683,0]; R_SPF_NA(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[149.207.82.46.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:33824, ipnet:94.185.88.0/22, country:DE]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 15:32:34 -0000 Kurt Jaeger wrote: > Hi! > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > Volunteers who contribute actual fixes are very much appreciated; > > But those styled as 'management' who delay announcements to batch floods > > damage us. > > 8 announcements and one freebsd-update is easier on the > admin and the re-team than 8 announcements and 8 freebsd-update runs. > > That's probably why they are batched. Because all of the fixes > are bundled in one update. > > If the re-team-capacity is limited, what would be the alternative? Alternative is to for announcers to do Less work: Send each announcement when ready. Do not do extra work delaying, storing, batch announcing. Announcements to recipients not delayed, without flooding. > > -- > pi@opsec.eu +49 171 3101372 One year to go ! > Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. From owner-freebsd-stable@freebsd.org Wed May 15 15:38:41 2019 Return-Path: Delivered-To: freebsd-stable@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 AB96F1595B0A for ; Wed, 15 May 2019 15:38:41 +0000 (UTC) (envelope-from pi@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 4C768908EA for ; Wed, 15 May 2019 15:38:41 +0000 (UTC) (envelope-from pi@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0D0691595B08; Wed, 15 May 2019 15:38:41 +0000 (UTC) Delivered-To: stable@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 EFA4F1595B03 for ; Wed, 15 May 2019 15:38:40 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 802D0908E8 for ; Wed, 15 May 2019 15:38:40 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by fc.opsec.eu with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hQvzI-000H97-Jk; Wed, 15 May 2019 17:38:36 +0200 Date: Wed, 15 May 2019 17:38:36 +0200 From: Kurt Jaeger To: "Julian H. Stacey" Cc: stable@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <20190515153836.GU20962@fc.opsec.eu> References: <20190515143321.GZ72200@home.opsec.eu> <201905151532.x4FFW9SD066919@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201905151532.x4FFW9SD066919@fire.js.berklix.net> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 15:38:41 -0000 Hi! > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > > > Volunteers who contribute actual fixes are very much appreciated; > > > But those styled as 'management' who delay announcements to batch floods > > > damage us. > > > > 8 announcements and one freebsd-update is easier on the > > admin and the re-team than 8 announcements and 8 freebsd-update runs. > > > > That's probably why they are batched. Because all of the fixes > > are bundled in one update. > > > > If the re-team-capacity is limited, what would be the alternative? > Alternative is to for announcers to do Less work: > Send each announcement when ready. The problem is not the announcement, the problem is providing the freebsd-update. If announcements are send when ready, and the freebsd-update is not ready, therefore, the timeframes to attack systems with unpatched problems are much longer. -- pi@FreeBSD.org +49 171 3101372 One year to go ! From owner-freebsd-stable@freebsd.org Wed May 15 15:44:48 2019 Return-Path: Delivered-To: freebsd-stable@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 2176F1595F8C for ; Wed, 15 May 2019 15:44:48 +0000 (UTC) (envelope-from jhs@berklix.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 90F3E90E1E for ; Wed, 15 May 2019 15:44:47 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4EC731595F8A; Wed, 15 May 2019 15:44:47 +0000 (UTC) Delivered-To: stable@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 13E9F1595F88; Wed, 15 May 2019 15:44:47 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "slim.berklix.org", Issuer "slim.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 25E0190E19; Wed, 15 May 2019 15:44:45 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CF95.dip0.t-ipconnect.de [46.82.207.149]) (authenticated bits=128) by slim.berklix.org (8.15.2/8.15.2) with ESMTPSA id x4FFie6a019980 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2019 17:44:44 +0200 (CEST) (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 x4FFidIQ072255; Wed, 15 May 2019 17:44:39 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id x4FFiR0G067138; Wed, 15 May 2019 17:44:39 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201905151544.x4FFiR0G067138@fire.js.berklix.net> To: Alan Somers Cc: FreeBSD Core Team , FreeBSD Stable ML , "freebsd-hackers@freebsd.org" Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. From: "Julian H. Stacey" Organization: http://berklix.com/jhs http://stolenvotes.uk User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Wed, 15 May 2019 08:32:26 -0600." Date: Wed, 15 May 2019 17:44:27 +0200 X-Rspamd-Queue-Id: 25E0190E19 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.99 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.77)[0.773,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.40)[0.401,0]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(0.16)[ip: (0.58), ipnet: 94.185.88.0/22(0.29), asn: 33824(-0.07), country: DE(-0.01)]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: slim.berklix.com]; NEURAL_SPAM_LONG(0.77)[0.772,0]; RCVD_IN_DNSWL_NONE(0.00)[68.90.185.94.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:33824, ipnet:94.185.88.0/22, country:DE]; RCVD_TLS_LAST(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[149.207.82.46.zen.spamhaus.org : 127.0.0.10] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 15:44:48 -0000 Hi, Reference: > From: Alan Somers > Date: Wed, 15 May 2019 08:32:26 -0600 Alan Somers wrote: > On Wed, May 15, 2019 at 8:26 AM Julian H. Stacey wrote: > > > > Hi core@, > > cc hackers@ & stable@ > > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > Volunteers who contribute actual fixes are very much appreciated; > > But those styled as 'management' who delay announcements to batch floods > > damage us. As they've previously refused to stop, it's time to sack them. > > > > Just send each announcement out when ready, no delays to batch them. > > No sys admins can deal with 8 in 3 mins: > > Especially on multiple systems & releases. Recipients start > > mitigating, then more flood in, & need review which are > > most urgent to interrupt to; While also avoiding sudden upgrades > > to many servers & releases, to minimise disturbing server users, > > bosses & customers. > > > > Cheers, > > Julian > > -- > > Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent > > http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. > > Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. > > I disagree, Julian. I think SAs are easier to deal with when they're > batched. True, I can't fix the first one in less than 3 minutes. But > then I probably wouldn't even notice it that fast. Batching them all > together means fewer updates and reboots. Batching also means some of these vulnerabilities could have been fixed earlier & less of a surge of demand on recipient admins time. An admin can find time to ameliorate 1 bug, not 8 suddenly together. Avoidance is called planning ahead. Giving warning of a workload. Like an admin plans ahead & announces an outage schedule for planned upgrade. Suddenly dumping 8 on admins causes overload on admin manpower. 8 reason for users to approach admin in parallel & say "FreeBSD seems riddled, how long will all the sudden unplanned outages take ? Should we just dump it ?" Dont want negative PR & lack of management. Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. From owner-freebsd-stable@freebsd.org Wed May 15 15:51:20 2019 Return-Path: Delivered-To: freebsd-stable@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 80B961596556 for ; Wed, 15 May 2019 15:51:20 +0000 (UTC) (envelope-from jhs@berklix.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 E30F79152B for ; Wed, 15 May 2019 15:51:19 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id A07681596421; Wed, 15 May 2019 15:51:19 +0000 (UTC) Delivered-To: stable@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 7C72E1596420 for ; Wed, 15 May 2019 15:51:19 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "slim.berklix.org", Issuer "slim.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9EC9F91526; Wed, 15 May 2019 15:51:18 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CF95.dip0.t-ipconnect.de [46.82.207.149]) (authenticated bits=128) by slim.berklix.org (8.15.2/8.15.2) with ESMTPSA id x4FFpCGO020019 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2019 17:51:16 +0200 (CEST) (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 x4FFpCAP072297; Wed, 15 May 2019 17:51:12 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id x4FFp0UP067236; Wed, 15 May 2019 17:51:12 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201905151551.x4FFp0UP067236@fire.js.berklix.net> To: Kurt Jaeger cc: stable@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. From: "Julian H. Stacey" Organization: http://berklix.com/jhs http://stolenvotes.uk User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Wed, 15 May 2019 17:38:36 +0200." <20190515153836.GU20962@fc.opsec.eu> Date: Wed, 15 May 2019 17:51:00 +0200 X-Rspamd-Queue-Id: 9EC9F91526 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.73 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.83)[0.834,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.19)[0.189,0]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(0.15)[ip: (0.57), ipnet: 94.185.88.0/22(0.28), asn: 33824(-0.07), country: DE(-0.01)]; MX_GOOD(-0.01)[cached: slim.berklix.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[68.90.185.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(0.66)[0.659,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:33824, ipnet:94.185.88.0/22, country:DE]; RCVD_TLS_LAST(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[149.207.82.46.zen.spamhaus.org : 127.0.0.10] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 15:51:20 -0000 Hi, Reference: > From: Kurt Jaeger > Date: Wed, 15 May 2019 17:38:36 +0200 Kurt Jaeger wrote: > Hi! > > > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > > > > > Volunteers who contribute actual fixes are very much appreciated; > > > > But those styled as 'management' who delay announcements to batch floods > > > > damage us. > > > > > > 8 announcements and one freebsd-update is easier on the > > > admin and the re-team than 8 announcements and 8 freebsd-update runs. > > > > > > That's probably why they are batched. Because all of the fixes > > > are bundled in one update. > > > > > > If the re-team-capacity is limited, what would be the alternative? > > > Alternative is to for announcers to do Less work: > > Send each announcement when ready. > > The problem is not the announcement, the problem is providing > the freebsd-update. > > If announcements are send when ready, and the freebsd-update is > not ready, therefore, the timeframes to attack systems with unpatched > problems are much longer. True as far as that goes for binary users, but often source patches are available faster, which begs the question: when to announce ? When there's diffs ? When diffs are commited to src/ (used to be the norm *) ? When there's some binary update ? Whne a whole bunch of 8 arrive in 3 minutes ? Gasp ! * I happen to use src/ never use freebsd-update. Equally bound to be some who use binary updates & not source Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. From owner-freebsd-stable@freebsd.org Wed May 15 15:58:42 2019 Return-Path: Delivered-To: freebsd-stable@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 246241596ED2 for ; Wed, 15 May 2019 15:58:42 +0000 (UTC) (envelope-from pi@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 B90FC92EEF for ; Wed, 15 May 2019 15:58:41 +0000 (UTC) (envelope-from pi@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 76BD61596ECF; Wed, 15 May 2019 15:58:41 +0000 (UTC) Delivered-To: stable@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 655E11596ECD for ; Wed, 15 May 2019 15:58:41 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CC8A92EEC; Wed, 15 May 2019 15:58:41 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by fc.opsec.eu with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hQwIg-000HD3-9N; Wed, 15 May 2019 17:58:38 +0200 Date: Wed, 15 May 2019 17:58:38 +0200 From: Kurt Jaeger To: "Julian H. Stacey" Cc: stable@freebsd.org, re@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <20190515155838.GV20962@fc.opsec.eu> References: <20190515153836.GU20962@fc.opsec.eu> <201905151551.x4FFp0UP067236@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201905151551.x4FFp0UP067236@fire.js.berklix.net> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 15:58:42 -0000 Hi! > > > Alternative is to for announcers to do Less work: > > > Send each announcement when ready. > > The problem is not the announcement, the problem is providing > > the freebsd-update. > > If announcements are send when ready, and the freebsd-update is > > not ready, therefore, the timeframes to attack systems with unpatched > > problems are much longer. > True as far as that goes for binary users, but often source patches > are available faster, which begs the question: when to announce ? > When there's diffs ? When diffs are commited to src/ (used to be the norm *) ? > When there's some binary update ? > Whne a whole bunch of 8 arrive in 3 minutes ? Gasp ! Now I understand why you bring this up. I guess the majority of users are using the binary update path. Maybe re@ can explain how the process is for these steps ? -- pi@FreeBSD.org +49 171 3101372 One year to go ! From owner-freebsd-stable@freebsd.org Wed May 15 16:02:49 2019 Return-Path: Delivered-To: freebsd-stable@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 EC05815974C9 for ; Wed, 15 May 2019 16:02:48 +0000 (UTC) (envelope-from gjb@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 6BBDA93443 for ; Wed, 15 May 2019 16:02:48 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2CCF615974C7; Wed, 15 May 2019 16:02:48 +0000 (UTC) Delivered-To: stable@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 1B4EE15974C5 for ; Wed, 15 May 2019 16:02:48 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 B386F9343D; Wed, 15 May 2019 16:02:47 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 2425A7CDC; Wed, 15 May 2019 16:02:47 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Wed, 15 May 2019 16:02:44 +0000 From: Glen Barber To: Kurt Jaeger Cc: "Julian H. Stacey" , stable@freebsd.org, re@freebsd.org, FreeBSD Security Officer Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <20190515160244.GU15455@FreeBSD.org> References: <20190515153836.GU20962@fc.opsec.eu> <201905151551.x4FFp0UP067236@fire.js.berklix.net> <20190515155838.GV20962@fc.opsec.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3yk1sSvxP8cRAjBs" Content-Disposition: inline In-Reply-To: <20190515155838.GV20962@fc.opsec.eu> User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: B386F9343D X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.89 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.89)[-0.894,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 16:02:49 -0000 --3yk1sSvxP8cRAjBs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 15, 2019 at 05:58:38PM +0200, Kurt Jaeger wrote: > Hi! >=20 > > > > Alternative is to for announcers to do Less work:=20 > > > > Send each announcement when ready. >=20 > > > The problem is not the announcement, the problem is providing > > > the freebsd-update. >=20 > > > If announcements are send when ready, and the freebsd-update is > > > not ready, therefore, the timeframes to attack systems with unpatched > > > problems are much longer. >=20 > > True as far as that goes for binary users, but often source patches > > are available faster, which begs the question: when to announce ? > > When there's diffs ? When diffs are commited to src/ (used to be the no= rm *) ? > > When there's some binary update ?=20 > > Whne a whole bunch of 8 arrive in 3 minutes ? Gasp ! >=20 > Now I understand why you bring this up. >=20 > I guess the majority of users are using the binary update path. >=20 > Maybe re@ can explain how the process is for these steps ? >=20 This is an so@ thing (CCd). re@ does not have any involvement in this process. Glen --3yk1sSvxP8cRAjBs Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlzcOCQACgkQAxRYpUeP 4pOCaw/+KmuAxkQgN/pBRqZEvq4B0K8OCToE2XBavpugNMUJwEmlG5sPYHEc2tg2 mIPmQVzM47x/SdwARXkqUoUGh+jvOcYoEzfK2rLXNR5nAz7zrA5fcBkGe/wNZ23t N4GsCYym54lwalFWWXzmsUfiUMlLvkhLPW6N97buDftNw5B0RQKNCymVWc2butM7 dBSWQKW0BgKq9vh+X+6T6z0u05nbO7prsM8nWu3DYPwRvgdzxxEmoui2C8cQvda/ 3F5aXi8HrYgQO4JzI0VYbqkCrXkt+r7ZYM4D/UO0u+LRv8vEglM/TRhWxxPLsbaD GCN8C6DFusGwVQB2Kg+81IreHclRkotQw4iosvZrr3ElkRW7Np8eRRWTedg/D5Ui Ne05aJlZzrU1AxUOhInvMrQg+o685CJx1Kz+dNaastuv4/Qnqz5kpb4oNgjvBKPY y0XJpsE6X/lFCkKhVcAbpy1Q5MdCesb4u2Zdv2gcnKtltIOIZPtbqXfV40aFmM85 2YkQAmt/bo0GCo2RNAowgxUx5kcxxLlqSir2+kWlv7xeOCnL4Ayw4FX9uyA/bwHa nBvUFk4Fos2edGgEvWt4ZLWc7nTbAb6312AphzpaShwUxPY56JUlD+aM1vMSHRqL hlhVHVbhB8ipqYh3Csg4f7P5xkseU16iJXR2A+uGosq7XCNnKEk= =FqGO -----END PGP SIGNATURE----- --3yk1sSvxP8cRAjBs-- From owner-freebsd-stable@freebsd.org Wed May 15 16:13:09 2019 Return-Path: Delivered-To: freebsd-stable@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 D44CE15979B7 for ; Wed, 15 May 2019 16:13:08 +0000 (UTC) (envelope-from will@firepipe.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 52BDA93A28 for ; Wed, 15 May 2019 16:13:08 +0000 (UTC) (envelope-from will@firepipe.net) Received: by mailman.ysv.freebsd.org (Postfix) id 141F015979B5; Wed, 15 May 2019 16:13:08 +0000 (UTC) Delivered-To: stable@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 E450C15979B3 for ; Wed, 15 May 2019 16:13:07 +0000 (UTC) (envelope-from will@firepipe.net) Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84AA193A23 for ; Wed, 15 May 2019 16:13:07 +0000 (UTC) (envelope-from will@firepipe.net) Received: by mail-qk1-x734.google.com with SMTP id z128so331670qkb.6 for ; Wed, 15 May 2019 09:13:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=firepipe-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rMEa1zDdJyvwxY45LX6vdxIxMYPAnK8e3fBGKBYQ7lA=; b=kfX9q7RS6r42HasJ3JnTH8BHAG8LRelN/bC9pYaTexA9pzXZH9UrLDCKnH0HEYU3Ng 1GYiAEnHbN48f9WEveXQSLH9/miu84wU4syzBJ3a9GExwxwyqYlI9lGATCLB+1UjI0YZ 7pX8yCu2hL6+iuQHHF/GzQ8yMCH+BTPw37X2PXBqNNrzDbv/OGC1A12Xm18pd820GUgY BeWCmzTP+s2X8eWEEU5ePJf7i+kv+4uEHioIyEKjMQItzSlaq9EXxUVcKzkmNiFQoOZg GwOAHXLHI7A2gCD1vEHclTkyMkp0nNmLMUzPTo644jaPsamgQUTEDdrdEKWOUdR1BxpH I00Q== 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=rMEa1zDdJyvwxY45LX6vdxIxMYPAnK8e3fBGKBYQ7lA=; b=tpPxTF4oEaJgN9El+I3C8OvOYWpiPL82Qtmr8nqAnGHe8YEeAAyRuCCO2aw6tiFq3e nMQOXnmVslgscl1gqfkXQigSusaz+iu2gsQd4IbeEwnREcMYGYQ8qOSfX5fYN5Jc2zVJ EeUsx71ycR/sAz9Fy5YPZT0hp/qyZh/ubK3L0A+p5Op8zKcGO3TYIQWtqOw7dkX2Sw/t 34VpuaBJi/dRhdoOziV3fgKR6zk3378ptvobwfdZewTO4rZsBNuL/w1dSJOPmMboyamf 3PMK/p/Pd5SgwMFcnWPgZYNNus8ONhha+6sMfGdutP7YRnUVBNhpxTJKfm9NlUSJwgmA aWqw== X-Gm-Message-State: APjAAAWqVNa2Qq/C/a6vt2imeiiudifdO65j7pBacPbaGWLE6yVzY9wi IKw5aLOpwJrzBgYhLWdfjgOyO6SgbBdgnOIHay/ObQ== X-Google-Smtp-Source: APXvYqwdxqUIiSAqcuRit/VCgPOwOA/GG8gc9kygbXJ8MZO5W9L+EPMOLMi1D6vJu7Wd5Xhy7HWKc1ucNBnbv4zaf2A= X-Received: by 2002:a37:9103:: with SMTP id t3mr35068514qkd.78.1557936786926; Wed, 15 May 2019 09:13:06 -0700 (PDT) MIME-Version: 1.0 References: <201905151544.x4FFiR0G067138@fire.js.berklix.net> In-Reply-To: <201905151544.x4FFiR0G067138@fire.js.berklix.net> From: Will Andrews Date: Wed, 15 May 2019 11:12:55 -0500 Message-ID: Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: "Julian H. Stacey" Cc: Alan Somers , FreeBSD Stable ML , "freebsd-hackers@freebsd.org" , FreeBSD Core Team X-Rspamd-Queue-Id: 84AA193A23 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_SHORT(-0.97)[-0.973,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 16:13:09 -0000 On Wed, May 15, 2019 at 10:45 AM Julian H. Stacey wrote: > Batching also means some of these vulnerabilities could have been > fixed earlier & less of a surge of demand on recipient admins time. > > An admin can find time to ameliorate 1 bug, not 8 suddenly together. > Avoidance is called planning ahead. Giving warning of a workload. > Like an admin plans ahead & announces an outage schedule for planned > upgrade. > > Suddenly dumping 8 on admins causes overload on admin manpower. > 8 reason for users to approach admin in parallel & say > "FreeBSD seems riddled, how long will all the sudden unplanned > outages take ? Should we just dump it ?" > Dont want negative PR & lack of management. > What admins prefer 8 downtime events instead of 1? --Will. From owner-freebsd-stable@freebsd.org Wed May 15 16:16:41 2019 Return-Path: Delivered-To: freebsd-stable@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 36F7C1597C3D for ; Wed, 15 May 2019 16:16:41 +0000 (UTC) (envelope-from matt.garber@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 8FE6A93D70 for ; Wed, 15 May 2019 16:16:40 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4E0EA1597C37; Wed, 15 May 2019 16:16:40 +0000 (UTC) Delivered-To: stable@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 2B79B1597C35; Wed, 15 May 2019 16:16:40 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 83F2493D69; Wed, 15 May 2019 16:16:39 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: by mail-qt1-x82d.google.com with SMTP id y42so312096qtk.6; Wed, 15 May 2019 09:16:39 -0700 (PDT) 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=BDKCTeHS+/j7SohAx91ExE0xNbRq8raNLmfqada1j6I=; b=Bimpda2lVUDerX6EauT1XIMb0vXrM7QPvOq7KoQS2FJQzQtpPaBvB7ghxizUg99pQS E9Z5cBW3APgaqoy+bDqIEZmu+KfUhg9/NT0/RJCHZh0QE+NEYgHm9cQBGxFiz/SG8nq9 5AeVj0t+TWHBlQpDEv+JpwUkpG65U+D3YSwHEI53a2WHzdQ3MDnm7mMOXq791yFS5esR EoYdNIEgDW4AdgneibmBaRL3Sv5znvRNgq/g35pL5DITXYfKPBS9ChSCNKqWk9fK/cBT KlWcRvaahdaX0kfV2s84k60wMPX2+X4J0kemCYN9Mkpu6652/eYe6SuabgtEKgYZglMK WztA== 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=BDKCTeHS+/j7SohAx91ExE0xNbRq8raNLmfqada1j6I=; b=kAn7uKNjaZcoypXWRCqSM9Y5cnB8BaLiD0L1TgQ5pMJLdeh2AjWXxoFNrBrQZQw7jw iqsVQAu3wx9BbOZyu2geE8Zqa9vlqJtcZ8UpxfjzPyIJP5K/86GILKVNRF6Uguh92zLH gsY6bU9v22jqTTpJ/WaujQ69FDSe4DXugsE9fYOoKgcVtPRMw8YiqPGxTbyJdsGwm2Tg G/zhZ3KMppiD0GBWvuev2a/uW5zBW4hcHFiIDMRwrK3jABM5yPdOIrme410+dwE/BX7+ Gb/yiCjc92RUJK4O3v1jqA8r59dOMpXVUcLUAFl4w3ZdSa6LZ6aEn941gWyaQSyUl0g6 iu5Q== X-Gm-Message-State: APjAAAWqn+EYQTrBVBILmhrTF3jHJd5/HHGcXQ3Hpcncl9DEtq74ULtT 1NwuYTtJEjeYjNp5SglTFxxDvhFyO84= X-Google-Smtp-Source: APXvYqxr3uLHsV9jjdNSZoMxsLsdndRVznyr6voGLKJjWaNLby18/W19fPIxO2l3G+DKhDaKfE5oBw== X-Received: by 2002:ac8:19ab:: with SMTP id u40mr36483770qtj.229.1557936999079; Wed, 15 May 2019 09:16:39 -0700 (PDT) Received: from [10.100.20.3] ([68.183.62.201]) by smtp.gmail.com with ESMTPSA id 139sm1263618qkm.27.2019.05.15.09.16.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 May 2019 09:16:38 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. From: Matt Garber In-Reply-To: Date: Wed, 15 May 2019 12:16:37 -0400 Cc: FreeBSD Stable ML , "freebsd-hackers@freebsd.org" , FreeBSD Core Team , Alan Somers Content-Transfer-Encoding: quoted-printable Message-Id: <6CE35CEB-C2AB-47B1-AA86-BC9C91B2B8A6@gmail.com> References: <201905151544.x4FFiR0G067138@fire.js.berklix.net> To: Will Andrews , "Julian H. Stacey" X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 83F2493D69 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_SHORT(-0.98)[-0.978,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 16:16:41 -0000 > On May 15, 2019, at 12:12 PM, Will Andrews wrote: >=20 > On Wed, May 15, 2019 at 10:45 AM Julian H. Stacey = wrote: >=20 >> Batching also means some of these vulnerabilities could have been >> fixed earlier & less of a surge of demand on recipient admins time. >>=20 >> An admin can find time to ameliorate 1 bug, not 8 suddenly together. >> Avoidance is called planning ahead. Giving warning of a workload. >> Like an admin plans ahead & announces an outage schedule for planned >> upgrade. >>=20 >> Suddenly dumping 8 on admins causes overload on admin manpower. >> 8 reason for users to approach admin in parallel & say >> "FreeBSD seems riddled, how long will all the sudden unplanned >> outages take ? Should we just dump it ?" >> Dont want negative PR & lack of management. >>=20 >=20 > What admins prefer 8 downtime events instead of 1? >=20 > =E2=80=94Will. Exactly. If batching 8 (or more) individual bugs/issues together into = one release is really causing admin/manpower overload and angst, then = maybe it=E2=80=99s time in your situation to use the binary updates = (which would only be a single `freebsd-update` and reboot, so there = would be no =E2=80=98sudden unplanned outages=E2=80=99) rather than = tracking src and remediating each individual bug at a time. I understand = that might be mutually exclusive with other reasons why you don=E2=80=99t = already use binary updates or prefer to track src for the base system, = but there are always compromises and trade-offs to everything, and = batching seems preferable to any alternatives. You=E2=80=99d seriously want to run reboots across a server fleet every = other day for two weeks if there were 8 separate patches staggered out? = That=E2=80=99s insanity, and is way more of a PR problem from a = =E2=80=98should we just dump it=E2=80=99 perspective. You mention = =E2=80=98announces an outage schedule for planned upgrade=E2=80=99, but = that=E2=80=99s really its own form of internal batching =E2=80=93 it = shouldn=E2=80=99t make any difference if you=E2=80=99re technically = pushing 1 or 8 bug/security fixes during that pre-identified period of = time: all of your other internal processes like maintaining a test group = for detecting regressions, using boot environments (or other storage = features) to allow for rollbacks, etc. all continue to work as intended. Any potential negative PR within your company/organization seems like it = would be related to how else you=E2=80=99re handling the upgrade = process(es), not whether the fixes are batched or not. Whatever other = negative things you can say about them, I don=E2=80=99t hear enterprise = admins begging that Microsoft/Oracle/whoever would dribble out patches = one at a time each week instead of combining them like they do; it seems = like it works just fine for everyone else. =C2=AF\_(=E3=83=84)_/=C2=AF Thanks, =E2=80=94 Matt Garber From owner-freebsd-stable@freebsd.org Wed May 15 16:28:31 2019 Return-Path: Delivered-To: freebsd-stable@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 83CE7159821A for ; Wed, 15 May 2019 16:28:31 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (net-2-44-121-52.cust.vodafonedsl.it [2.44.121.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mailserver.netfence.it", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E728294461 for ; Wed, 15 May 2019 16:28:29 +0000 (UTC) (envelope-from ml@netfence.it) Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.15.2/8.15.2) with ESMTPSA id x4FGSNmf092330 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 15 May 2019 18:28:25 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: freebsd-stable@freebsd.org References: <201905151544.x4FFiR0G067138@fire.js.berklix.net> <6CE35CEB-C2AB-47B1-AA86-BC9C91B2B8A6@gmail.com> From: Andrea Venturoli Message-ID: <5d74a839-50ef-d8c0-b541-15d9b875b7e2@netfence.it> Date: Wed, 15 May 2019 18:28:23 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <6CE35CEB-C2AB-47B1-AA86-BC9C91B2B8A6@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: E728294461 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.963,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 16:28:31 -0000 On 5/15/19 6:16 PM, Matt Garber wrote: > Exactly. If batching 8 (or more) individual bugs/issues together into > one release is really causing admin/manpower overload and angst,then > maybe it’s time in your situation to use the binary updates (which > would only be a single `freebsd-update` and reboot, so there would > be no ‘sudden unplanned outages’) rather than tracking src and > remediating each individual bug at a time. Maybe I'm dumb, but I still don't get what "src vs binary" has to do with "8 vs 1"... I ran a single "svn update; make buildworld; make kernel; make installworld; reboot", not 8... bye av. From owner-freebsd-stable@freebsd.org Wed May 15 16:34:32 2019 Return-Path: Delivered-To: freebsd-stable@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 1732615985E6 for ; Wed, 15 May 2019 16:34:32 +0000 (UTC) (envelope-from jhs@berklix.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 7A41E948BF for ; Wed, 15 May 2019 16:34:31 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3EAEF15985DB; Wed, 15 May 2019 16:34:31 +0000 (UTC) Delivered-To: stable@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 1C57215985D9 for ; Wed, 15 May 2019 16:34:31 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "slim.berklix.org", Issuer "slim.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0893F948B9; Wed, 15 May 2019 16:34:27 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CF95.dip0.t-ipconnect.de [46.82.207.149]) (authenticated bits=128) by slim.berklix.org (8.15.2/8.15.2) with ESMTPSA id x4FGYKBJ020414 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2019 18:34:24 +0200 (CEST) (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 x4FGYJxh072582; Wed, 15 May 2019 18:34:19 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id x4FGY7nR067982; Wed, 15 May 2019 18:34:19 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201905151634.x4FGY7nR067982@fire.js.berklix.net> To: Kurt Jaeger cc: stable@freebsd.org, re@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. From: "Julian H. Stacey" Organization: http://berklix.com/jhs http://stolenvotes.uk User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Wed, 15 May 2019 17:58:38 +0200." <20190515155838.GV20962@fc.opsec.eu> Date: Wed, 15 May 2019 18:34:07 +0200 X-Rspamd-Queue-Id: 0893F948B9 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.71 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.52)[0.516,0]; NEURAL_SPAM_SHORT(0.84)[0.841,0]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(0.15)[ip: (0.55), ipnet: 94.185.88.0/22(0.28), asn: 33824(-0.07), country: DE(-0.01)]; MX_GOOD(-0.01)[cached: slim.berklix.com]; NEURAL_SPAM_LONG(0.32)[0.318,0]; RCVD_IN_DNSWL_NONE(0.00)[68.90.185.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[149.207.82.46.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:33824, ipnet:94.185.88.0/22, country:DE]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 16:34:32 -0000 Kurt Jaeger wrote: > Hi! > > > > > Alternative is to for announcers to do Less work: > > > > Send each announcement when ready. > > > > The problem is not the announcement, the problem is providing > > > the freebsd-update. > > > > If announcements are send when ready, and the freebsd-update is > > > not ready, therefore, the timeframes to attack systems with unpatched > > > problems are much longer. > > > True as far as that goes for binary users, but often source patches > > are available faster, which begs the question: when to announce ? > > When there's diffs ? When diffs are commited to src/ (used to be the norm *) ? > > When there's some binary update ? > > Whne a whole bunch of 8 arrive in 3 minutes ? Gasp ! > > Now I understand why you bring this up. > > I guess the majority of users are using the binary update path. Hmm, a distinct possibility, that could be a problem delaying announcements. > Maybe re@ can explain how the process is for these steps ? I assumed re@ (periodicaly overworked team who presumably collapse in appreciated exhaustion after valuable work rolling releases), were [largely] different people? Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. From owner-freebsd-stable@freebsd.org Wed May 15 16:35:03 2019 Return-Path: Delivered-To: freebsd-stable@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 9C4A3159862D for ; Wed, 15 May 2019 16:35:03 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: from mail-qt1-x842.google.com (mail-qt1-x842.google.com [IPv6:2607:f8b0:4864:20::842]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BEE7A94905 for ; Wed, 15 May 2019 16:35:02 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: by mail-qt1-x842.google.com with SMTP id j53so358204qta.9 for ; Wed, 15 May 2019 09:35:02 -0700 (PDT) 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=6ypgbizXont3l6LEO1Lr8tsDd4tPwlNyaVY58odTXdk=; b=nW9NfqKw+ktNb8mp3bh/tI2BimlZPCV85WEfmApu/AjRhFHmZOYWIMF0nc0z3m6few /29NE6TOpeGUfoLZFn3pw4NK8dbT70P0OTdabhn8tuyi6LljVG2t0T8Bj0uhyQid2bfV +ZZmEDL7TEzA13LJTJhGAP6f2BFlFVwH9zLSx2zsJmUqPuF66VMDxXzQktTnTAvJvqtx 1P/fo8UFOJBXbLwctgyCfU1S1gv+A1xnDl0X6qX4iRO04SJhIjZQ0QqjfmkBHnCFfgCx OOwX+pNEg3hcp39h24x2DOfj0XahyRx9+TSicVMcSYmk2vqzEbcRkv8PTRJDyUM8S7EO 64fA== 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=6ypgbizXont3l6LEO1Lr8tsDd4tPwlNyaVY58odTXdk=; b=e7z4JvAuvGc20unZ+bupG7hR80AZS+elS2mL2jVjveB6cvoFkNC50JP9tf3eUW5PoE aKOd5VhS6DGAw7De7MM+cxDK7fPe03/IXbxqolqCIXn0qoqFlsbVR6diB3OJSu4RVlyj MNs+ajL/s+PKKHaSKUj0NaqY2D0XgZTXmeokORDJw/dAdZq68AMgL+1ExktvI52rj9lk n0jqdw7ngVi1V6Y8bq1zeV+YaTwSI+cZahazqXPPi6KYr7yHwxvcFP1S73a7PXM3/9ID /6E/E+IHbXQSoDqczvHoSgSyvjnA05b8TVYX9xrDVFtW0R+r6k5g08wtuUbJ4ZKVplqW KSrA== X-Gm-Message-State: APjAAAXcwjzk8mrpabmPfXNhYxOCpMHay20hfpXLghYYKRYskaPlBSO4 shA65wXHHNN6WP5dBRF1BM9lXfr6 X-Google-Smtp-Source: APXvYqytvLLn3Kurz6xviUemQdnIWhEEmytvTFqwhWhaTOvYS6mM8zxZcRgSlg6iFpznNA9VDLUMRA== X-Received: by 2002:ac8:309d:: with SMTP id v29mr37361928qta.195.1557938102341; Wed, 15 May 2019 09:35:02 -0700 (PDT) Received: from [10.100.20.3] ([68.183.62.201]) by smtp.gmail.com with ESMTPSA id 76sm1189782qkf.20.2019.05.15.09.35.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 May 2019 09:35:01 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. From: Matt Garber In-Reply-To: <5d74a839-50ef-d8c0-b541-15d9b875b7e2@netfence.it> Date: Wed, 15 May 2019 12:35:00 -0400 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <97B1D23D-1A22-4002-8FC3-4ACF6986CD44@gmail.com> References: <201905151544.x4FFiR0G067138@fire.js.berklix.net> <6CE35CEB-C2AB-47B1-AA86-BC9C91B2B8A6@gmail.com> <5d74a839-50ef-d8c0-b541-15d9b875b7e2@netfence.it> To: Andrea Venturoli X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: BEE7A94905 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=nW9NfqKw; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mattgarber@gmail.com designates 2607:f8b0:4864:20::842 as permitted sender) smtp.mailfrom=mattgarber@gmail.com X-Spamd-Result: default: False [-4.29 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; 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.966,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; 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]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2.4.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]; IP_SCORE(-0.82)[ip: (1.48), ipnet: 2607:f8b0::/32(-3.25), asn: 15169(-2.26), country: US(-0.06)] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 16:35:03 -0000 > On May 15, 2019, at 12:28 PM, Andrea Venturoli wrote: >=20 > On 5/15/19 6:16 PM, Matt Garber wrote: >=20 >> Exactly. If batching 8 (or more) individual bugs/issues together into >> one release is really causing admin/manpower overload and angst,then >> maybe it=E2=80=99s time in your situation to use the binary updates = (which >> would only be a single `freebsd-update` and reboot, so there would >> be no =E2=80=98sudden unplanned outages=E2=80=99) rather than = tracking src and >> remediating each individual bug at a time. >=20 > Maybe I'm dumb, but I still don't get what "src vs binary" has to do = with "8 vs 1"... > I ran a single "svn update; make buildworld; make kernel; make = installworld; reboot", not 8... >=20 > bye > av. Agreed. But if, say, you were tracking specific svn revisions rather = than just jumping to the latest, I *guess* it might involve 8 separate = builds? I certainly prefer one, batched downtime event to address across all = affected systems, regardless of binary updates or src, and I imagine = most other individuals/companies/organizations do, too. -- Matt From owner-freebsd-stable@freebsd.org Wed May 15 17:15:44 2019 Return-Path: Delivered-To: freebsd-stable@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 CFA841599D5D for ; Wed, 15 May 2019 17:15:44 +0000 (UTC) (envelope-from jhs@berklix.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 4F2B3962D6 for ; Wed, 15 May 2019 17:15:44 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0C7691599D53; Wed, 15 May 2019 17:15:44 +0000 (UTC) Delivered-To: stable@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 DDCA81599D52; Wed, 15 May 2019 17:15:43 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "slim.berklix.org", Issuer "slim.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 78AA8962D2; Wed, 15 May 2019 17:15:41 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CF95.dip0.t-ipconnect.de [46.82.207.149]) (authenticated bits=128) by slim.berklix.org (8.15.2/8.15.2) with ESMTPSA id x4FHFY5i020724 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2019 19:15:38 +0200 (CEST) (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 x4FHFXlO072830; Wed, 15 May 2019 19:15:34 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id x4FHF4eC068579; Wed, 15 May 2019 19:15:21 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201905151715.x4FHF4eC068579@fire.js.berklix.net> To: Matt Garber cc: Will Andrews , FreeBSD Stable ML , "freebsd-hackers@freebsd.org" , FreeBSD Core Team , Alan Somers Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. From: "Julian H. Stacey" Organization: http://berklix.com/jhs http://stolenvotes.uk User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Wed, 15 May 2019 12:16:37 -0400." <6CE35CEB-C2AB-47B1-AA86-BC9C91B2B8A6@gmail.com> Date: Wed, 15 May 2019 19:15:04 +0200 X-Rspamd-Queue-Id: 78AA8962D2 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.93 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_FIVE(0.00)[6]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: slim.berklix.com]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:33824, ipnet:94.185.88.0/22, country:DE]; RCVD_TLS_LAST(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[149.207.82.46.zen.spamhaus.org : 127.0.0.10]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.88)[0.883,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.37)[0.365,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.65)[0.647,0]; RCVD_IN_DNSWL_NONE(0.00)[68.90.185.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; IP_SCORE(0.15)[ip: (0.54), ipnet: 94.185.88.0/22(0.27), asn: 33824(-0.07), country: DE(-0.01)] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 17:15:45 -0000 Thanks Will, You make some good points, but all depend on variant circustances. I prefer to be informed ASAP, to make my own decisons with max info ASAP, Not delayed. I want freebsd.org to Not Delay fix announcements into batches. If other admins want to delay being told told to do upgrades until there's lots more to consider & upgrade, they can dummy the delay their receive end, just filtering announcements into their own special box they read once per period. As soon as exploits are in the wild, some will exploit, not announcing until binary updates are ready gives black hats more time. > Whatever other negative things you can say about them, I don't hear enterprise admins begging that Microsoft/Oracle/whoever would dribble out patches one at a time each week instead of combining them like they do; it seems like it works just fine for everyone else. MS make lots of money from the addicted cluless, despite MS loosers frequently complain eg that PCs are locked up again in mid auto update & owner can't shut down to catch a plane or train. MS servers I avoid like the plague. PS Here seems (*) an example of something in text config didnt even need to wait for src/ let alone bin. * Not sure, I'll try it later, got to dash off line. https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/001878.html ] IV. Workaround ] Use 'restrict noquery' in the ntpd configuration to limit addresses that ] can send mode 6 queries. Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. From owner-freebsd-stable@freebsd.org Wed May 15 17:53:02 2019 Return-Path: Delivered-To: freebsd-stable@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 CE2BF159ABE0 for ; Wed, 15 May 2019 17:53:02 +0000 (UTC) (envelope-from gordon@tetlows.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 01CF297826 for ; Wed, 15 May 2019 17:53:02 +0000 (UTC) (envelope-from gordon@tetlows.org) Received: by mailman.ysv.freebsd.org (Postfix) id B745C159ABDD; Wed, 15 May 2019 17:53:01 +0000 (UTC) Delivered-To: stable@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 951B0159ABDB for ; Wed, 15 May 2019 17:53:01 +0000 (UTC) (envelope-from gordon@tetlows.org) Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 34AF797822 for ; Wed, 15 May 2019 17:53:01 +0000 (UTC) (envelope-from gordon@tetlows.org) Received: by mail-qt1-x833.google.com with SMTP id t1so643455qtc.12 for ; Wed, 15 May 2019 10:53:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tetlows.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=wB5skITX1hOvjOrnZPFRjv7iNmLLHeJ0DX0MqCw8S+o=; b=glevW5dJjPFk5VrYQxJM2iPgiLjjz2nLONRkGLIn1uLNd03gscqbJQCTOT7Ca80gzk MRMhLZfRi8v9wQKbvfhUbi+/8wDJpzlLv1RXmn/nZMrZirv7OsW3k8C5R/nGKcpwIvtV h0ykMdFH3icBAtE9T9/ToNChPzTmW3KP1HRdQ= 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=wB5skITX1hOvjOrnZPFRjv7iNmLLHeJ0DX0MqCw8S+o=; b=bP3iJnk6/Z30mb6Dqb/ihxxJVG79Lg/rfmub4a0GYCyUImpwQc1MCSTQtxCC88bEZJ QS4dO1U9z/VlOaO8auIXptecrFF0NMueYE1H7O2BnspNd6BFQj2SQtUlP1WukTOV2LBo bRqv0IY9XgwiEquwPaWxRc159fDt1gaLcbaU2RhvgJ/NpD4WJt41lv4jO4YmQqVySgjL xe1Ow5fOh+iuNvopDUP8mwsVErK6N/JBwIZ5vrEJ0S4ZyPzE2utIe9sOLACAyrJu7+4R JnHGCY0jn4f8uUw8pJ3rlgQ2Ve8i472SvV8PPa+F0Jif00n1EIKxsqW2wOTiKHAG54p8 olww== X-Gm-Message-State: APjAAAUrCGuFwzd/h56gl/G9Cu9mMI6SITXtqeHvg6aOWMobphUxJfSE vuSrov5ZBpWyPclr4qu2KwvT X-Google-Smtp-Source: APXvYqyZ37psuRRjWllIjP9thMKolx2echVUr5TLJC9DR4dT13bp7NQAeOY2oYbtnozs97TE//ysdA== X-Received: by 2002:aed:30cf:: with SMTP id 73mr22188770qtf.356.1557942780649; Wed, 15 May 2019 10:53:00 -0700 (PDT) Received: from gmail.com ([2607:fc50:0:7900:0:dead:beef:cafe]) by smtp.gmail.com with ESMTPSA id u5sm1591297qtj.95.2019.05.15.10.52.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 May 2019 10:52:59 -0700 (PDT) Date: Wed, 15 May 2019 10:52:57 -0700 From: Gordon Tetlow To: "Julian H. Stacey" Cc: Matt Garber , Will Andrews , "freebsd-hackers@freebsd.org" , FreeBSD Core Team , FreeBSD Stable ML , Alan Somers Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <20190515175257.GC33157@gmail.com> References: <6CE35CEB-C2AB-47B1-AA86-BC9C91B2B8A6@gmail.com> <201905151715.x4FHF4eC068579@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201905151715.x4FHF4eC068579@fire.js.berklix.net> User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: 34AF797822 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]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 17:53:03 -0000 Hi. Your friendly neighborhood Security Officer here. I published the 5 advisories and 3 errata yesterday. On Wed, May 15, 2019 at 07:15:04PM +0200, Julian H. Stacey wrote: > Thanks Will, > You make some good points, but all depend on variant circustances. > > I prefer to be informed ASAP, to make my own decisons with max info ASAP, > Not delayed. I want freebsd.org to Not Delay fix announcements into batches. All but one of the fixes was already in the STABLE branches. So if you wanted to track something that would get things as immediate as possible, I would recommend looking at the STABLE branches, you just won't get freebsd-update bits there. Just to put a line in the sand here, I will always be batching advisories when it works in my judgement. Granted, this batch was larger than I wanted it to be; I ran out of time over the past couple of months to get everything together (real life and all getting in the way). There are two reasons I will batch: 1. Our users and the industry have a preference for batched updates. 2. There is a large upfront cost for getting the freebsd-update bits built. Meaning the time to do 1 advisory vs the time to do 8 makes it worthwhile to batch. No offense, but I value my time. I only have so much to devote to FreeBSD. > As soon as exploits are in the wild, some will exploit, > not announcing until binary updates are ready gives black hats more time. Welcome to the push/pull of dealing with security. It is a risk based decision, but I have the unenviable position of trying to make the best risk based decision for the entire community. By definition, not everyone will be happy with the decision. > PS Here seems (*) an example of something in text config didnt even > need to wait for src/ let alone bin. * Not sure, I'll try it later, > got to dash off line. > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/001878.html > ] IV. Workaround > ] Use 'restrict noquery' in the ntpd configuration to limit addresses that > ] can send mode 6 queries. I would note this is already the default config. Best regards, Gordon From owner-freebsd-stable@freebsd.org Wed May 15 18:19:23 2019 Return-Path: Delivered-To: freebsd-stable@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 C8815159BE9D for ; Wed, 15 May 2019 18:19:23 +0000 (UTC) (envelope-from freebsd@gregv.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 1C0B36A3B9 for ; Wed, 15 May 2019 18:19:23 +0000 (UTC) (envelope-from freebsd@gregv.net) Received: by mailman.ysv.freebsd.org (Postfix) id CE3BD159BE9A; Wed, 15 May 2019 18:19:22 +0000 (UTC) Delivered-To: stable@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 BBF2C159BE99; Wed, 15 May 2019 18:19:22 +0000 (UTC) (envelope-from freebsd@gregv.net) Received: from aurora.gregv.net (aurora.gregv.net [IPv6:2607:5600:bd::1:1000]) by mx1.freebsd.org (Postfix) with ESMTP id 60E336A3B4; Wed, 15 May 2019 18:19:22 +0000 (UTC) (envelope-from freebsd@gregv.net) Received: by aurora.gregv.net (Postfix, from userid 1001) id 4625D61F92; Wed, 15 May 2019 14:19:15 -0400 (EDT) Date: Wed, 15 May 2019 14:19:15 -0400 From: Greg Veldman To: "Julian H. Stacey" Cc: Matt Garber , Will Andrews , "freebsd-hackers@freebsd.org" , FreeBSD Core Team , FreeBSD Stable ML , Alan Somers Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <20190515181915.GD42338@aurora.gregv.net> References: <6CE35CEB-C2AB-47B1-AA86-BC9C91B2B8A6@gmail.com> <201905151715.x4FHF4eC068579@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201905151715.x4FHF4eC068579@fire.js.berklix.net> User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: 60E336A3B4 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.99)[-0.989,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 18:19:24 -0000 On Wed, May 15, 2019 at 07:15:04PM +0200, Julian H. Stacey wrote: > You make some good points, but all depend on variant circustances. I think there's validity to both points of view, and as you say I think a lot of it depends on circumstance. For example on my personal systems, where I can patch/update/change/whatever on a whim, I agree I'd rather know sooner. But I also do this professionally, and at work it's much more difficult to get a maintenance window. In that setting, where you can't patch and reboot a box every day, batching makes sense. It allows several defects to be fixed at once and actually reduces the time you're sitting with publically known issues on your running systems, waiting for RFC approval. That said, there are perhaps some things that can be done to make the process more predictable, which I'd submit for consideration to the various groups on this thread. First, perhaps there could be some advance notice when a large batch of fixes like this is about to drop. Nothing that gives details, but just something to allow enterprise admins to plan ahead and possibly be ready when the details are released. By way of example, I'm thinking of how the Samba project handled a security release which also dropped this week. [1][2] Second, to ensure things are being fixed in a reasonable manner and not waiting excessively long for a batch to queue up, perhaps secteam@ could share vulnerability timing metrics in (for example) quarterly reports, to include such things as time from initial report to released fix, time under embargo, etc. Again, doesn't have to be bug-specific, but an average would be useful. That would set the stage for a meaningful debate based on actual data, instead of just personal preferences. [1] https://lists.samba.org/archive/samba-announce/2019/000477.html [2] https://lists.samba.org/archive/samba-announce/2019/000478.html -- Greg Veldman freebsd@gregv.net From owner-freebsd-stable@freebsd.org Wed May 15 19:09:18 2019 Return-Path: Delivered-To: freebsd-stable@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 B1134159E4B5 for ; Wed, 15 May 2019 19:09:18 +0000 (UTC) (envelope-from justausern00b@gmail.com) Received: from mail-io1-xd42.google.com (mail-io1-xd42.google.com [IPv6:2607:f8b0:4864:20::d42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD1D06C911 for ; Wed, 15 May 2019 19:09:17 +0000 (UTC) (envelope-from justausern00b@gmail.com) Received: by mail-io1-xd42.google.com with SMTP id s20so483397ioj.7 for ; Wed, 15 May 2019 12:09:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=7DjScGwVNIe+XtrnSpezLp+s9Dob65k1cPBMnbJZ3q0=; b=Rp0LS53ZRnDsyFnBdJ/5eOXXMERUsbSlKLwJYplIUAwh1iHhJYAEVHmZDFsf2RqZzp SlEf0SYW4HQBvFN2iYREBWLcStpk/wkrL49FSCLjLF6WX0yiN7n+PwP85BrQf/fXLdzD wE3DdjqWDtZXBgsBjSqp9POgyvFhXXlN8WV4bwRApHsoXLxrKdCUnWZo24UQUvKyOY7f wbBVb9JdrmrSV1bbK+OJVIgICarUw+Q4llScxKvNe1frZxUvKnhDqFxbuJR4XIemNStU WuzPR9f0TWA5m+tx+aB9Maht3dPSk8810UD/mnNFtWet760gb4kQkGRVdNhBOhgYO8Ty dniw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=7DjScGwVNIe+XtrnSpezLp+s9Dob65k1cPBMnbJZ3q0=; b=rzC93MQn5SIt84K41Xasivbe/TcIN5fey3TDTmcPMDpRdVtC8njujWV/kCWKofx4oE 5jVNR3aIzTwMnNlse0naHpj05hrVsQbFY7cBmvs0e17JjCah4NsW/gFc+EeZKE8dXmKg lM0VqGIkv+ldWtUEVFelze22FSrr7TkmK1QP3uHl57nU+jO4aUmT0NfBNedKhXWeeJcA DgrzwiGP/xb8D8GuL8xYIoGatrs1NC5hmpeLxt5hfik/fp7EFWvyhB9o11bCxbR5oiGj 4Ke2Cj+4FoqZkK9dlOzvSwJ5CfrbHFaMWWZamAZ9iyfgbgmyzMUtE013ldJwrGGItT5F UrNw== X-Gm-Message-State: APjAAAW+qZqoKn7qfYBOpR1eqQUKH2Zw0w7akb+Ksr5gy5ViH0SoTBFO 35qoGI5u7NOeoR5Ezmfp5fpBPSO5gzWsVINEePDWs1y+20znJQ== X-Google-Smtp-Source: APXvYqzWT68accMmyE498suRdfucSUtOqdMoe+5lOlwEKTqna4JDqGYS0I+oHv+eXxDOLkWZWCEYItYqQFwSomJYQ8M= X-Received: by 2002:a6b:f305:: with SMTP id m5mr23381449ioh.271.1557947357037; Wed, 15 May 2019 12:09:17 -0700 (PDT) MIME-Version: 1.0 From: wintellect Auser Date: Wed, 15 May 2019 20:09:05 +0100 Message-ID: Subject: 12.0-RELEASE-p4 kernel panic on i386 boot To: freebsd-stable@freebsd.org X-Rspamd-Queue-Id: AD1D06C911 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Rp0LS53Z; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of justausern00b@gmail.com designates 2607:f8b0:4864:20::d42 as permitted sender) smtp.mailfrom=justausern00b@gmail.com X-Spamd-Result: default: False [-4.74 / 15.00]; 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)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2.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.80)[ip: (1.55), ipnet: 2607:f8b0::/32(-3.25), asn: 15169(-2.26), country: US(-0.06)]; NEURAL_HAM_SHORT(-0.93)[-0.928,0]; 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]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 19:09:18 -0000 Hi all, Wanted to make you aware of an issue I have encountered, sorry if this is the wrong list. I upgraded from FreeBSD 12.0-RELEASE-p3 to p4 using: freebsd-fetch update freebsd-fetch install and use the GENERIC kernel. Upon reboot the system kernel panics when attempting to mount the filesystem read-write. This also happens in single-user mode if selected at boot. Selecting the kernel.old from the boot menu boots the system with 12-p3 and all works fine. I have uploaded a screenshot here: https://imagebin.ca/v/4hCc2Kk5YqCX The computer is an i386 system. Thanks wintellect From owner-freebsd-stable@freebsd.org Wed May 15 18:19:30 2019 Return-Path: Delivered-To: freebsd-stable@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 D220F159BEDF for ; Wed, 15 May 2019 18:19:28 +0000 (UTC) (envelope-from justausern00b@gmail.com) Received: from mail-it1-x144.google.com (mail-it1-x144.google.com [IPv6:2607:f8b0:4864:20::144]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7CBF76A3DA for ; Wed, 15 May 2019 18:19:27 +0000 (UTC) (envelope-from justausern00b@gmail.com) Received: by mail-it1-x144.google.com with SMTP id q65so1716918itg.2 for ; Wed, 15 May 2019 11:19:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=fGh6OPnETRruspP9WZ+r6kltUx9fPY0+96diXOnXI5k=; b=YNJJGvrQy+qeHaXZ9jK4km+6klNxxZc63sajgCZ7rKSrnCoKw4cDIG7jtCCeLAiTu+ XdjPoQMQv/ywSfH0TVaGPSn3eJGwTwbF0VnImmZuABV8lzUQnmVYEsR3lCAf8zUOJusF Lj8KRmkADkxj9vPeGhJFFtH6rZpAQ0HIFL52X05EWSfHn49riUktcO9qvTuLgjyi5LtM MkscyQ9RWa3wJ9bIBphm1UKsnpgs6Y65UqjgraQdtnI+cgLZAnaEEl6RXAZEraehEIjs l14+N0/TMTHYGW/4jNiHCY80ysJ/718TOEnJOmM5WhGaDqiIJPmg7SJmBZmZhl0gouDS y5HA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=fGh6OPnETRruspP9WZ+r6kltUx9fPY0+96diXOnXI5k=; b=Dlp9jV2OABeC3d5vrwb9ExcYk8xcyQf+CZvJkbMvCXqKHrvRdWiIqbbKb41rhe06LW xi8jpTOdLsuKW1aAbJKcT7vOe94DTFDeks37qKGDzkVijSo35znTjJ1cZDf+nroacDBl jLQXDSaHhLYvPQ8blUrs/vWP4O9lQGVGd2VEmnFOBaCmIgK1CBniuYxDrBLRVhZtTdWj LWNBnDVQWk3jlVqecTwIF0cqU+ponHLI8n5irYOi4zML1FAlMR8nEBWPStfU1e5CYmTd MmssjpnnyJ5t6nBcEbATBdaPwddxnOeMwPfQJzXuNz2X4L9v08aq3L68PquJtW1T7ddB n8RA== X-Gm-Message-State: APjAAAW/NnGKTOoUgBpHu9mhdypWVxa9+6/kOuPe5aPWGMy14mSxJDkj eTJBJxvqVi7nVYUWii80jOjlMqt/kqH81gPKpAO5Lg4ik9Qn1w== X-Google-Smtp-Source: APXvYqx36BI/0rbhvq351x2heHfAKx0PtCE9/gWulLKRzQ1OmwqWN8wQmyjlO7IEf8dtEev/WM1KAOOJResjAghktt8= X-Received: by 2002:a24:320c:: with SMTP id j12mr8422611ita.131.1557944366019; Wed, 15 May 2019 11:19:26 -0700 (PDT) MIME-Version: 1.0 From: wintellect Auser Date: Wed, 15 May 2019 19:19:14 +0100 Message-ID: Subject: 12.0-RELEASE-p4 kernel panic on boot To: freebsd-stable@freebsd.org X-Rspamd-Queue-Id: 7CBF76A3DA X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=YNJJGvrQ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of justausern00b@gmail.com designates 2607:f8b0:4864:20::144 as permitted sender) smtp.mailfrom=justausern00b@gmail.com X-Spamd-Result: default: False [-4.75 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; HAS_ATTACHMENT(0.00)[]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.95)[-0.954,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; 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)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/mixed,multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.78)[ip: (1.65), ipnet: 2607:f8b0::/32(-3.25), asn: 15169(-2.26), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[4.4.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]; RCVD_COUNT_TWO(0.00)[2] X-Mailman-Approved-At: Wed, 15 May 2019 19:19:49 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 18:19:30 -0000 Hi all, Wanted to make you aware of an issue I have encountered, sorry if this is the wrong list. I upgraded from FreeBSD 12.0-RELEASE-p3 to p4 using: freebsd-fetch update freebsd-fetch install and use the GENERIC kernel. Upon reboot the system kernel panics when attempting to mount the filesystem read-write. This also happens in single-user mode if selected at boot. Selecting the kernel.old from the boot menu boots the system with 12-p3 and all works fine. I have attached a screenshot. The computer is an i386 system. Thanks wintellect From owner-freebsd-stable@freebsd.org Wed May 15 19:28:29 2019 Return-Path: Delivered-To: freebsd-stable@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 96728159F0DB for ; Wed, 15 May 2019 19:28:29 +0000 (UTC) (envelope-from dan@langille.org) 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 81FD86D615 for ; Wed, 15 May 2019 19:28:28 +0000 (UTC) (envelope-from dan@langille.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A688325A68 for ; Wed, 15 May 2019 15:28:27 -0400 (EDT) Received: from imap36 ([10.202.2.86]) by compute4.internal (MEProxy); Wed, 15 May 2019 15:28:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=langille.org; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=XMvT2b+SLf5ylSZRGzbZvTMGSxCdiky PGAxzYN7jjwQ=; b=aaJpgl6SZnotr+GhCV1uZOEXj8pNd+MIlkDR/R5eKYyokZG UhJ7HDsw029F3xKKo396TiODz7m4kIpQxED6QHwI4ITK3dm44it44wVfRXPyrEEK x4jMeld+9Vm35GkJGAC8fvu3pSbPrJCY29WTKlkf0X0LJWF1A+3Hyg+k9ASpVXJ/ jIH9X7MW9NirR1BsMfL06rPXgbhHZ0OtZzDlw6BQ8HsoDn5cLkyCf09tXh0Ic+1Z 468L6H5AmdZdwFGBhenQbW17S3itayxRSWQ0JAMbC3b0RfTfrHzf1R8YcsbxAeoC AoQW3sX3o7Q8B4lrRTmZ+VOzYpOaIxsvOO9Sa7w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm2; bh=XMvT2b +SLf5ylSZRGzbZvTMGSxCdikyPGAxzYN7jjwQ=; b=MMckKszJXLjqjGD7nVWoLP FvwzhOkPIxrV/0FWbAm4mNUrEZYbxe54dBjUsE8T9fHq/CXtRwZifDWxYhvSUgv0 LbOcToyefnPzqjelNukyjn4cJyr0RkKiB7gXjaj+FqDkEbIW+T+WXc6Aj8gGfcZy LgWc+/ZYRm1nvK873nZa+vpFAVcY6Kk9jHs4XkBYy9BtMjg5bB8+JPcxlP+n1LvQ ynKqjU6FzXU1Z6go5xgEtkbbULRSSdCYLB62x/dFTDqaWvlc8cwJ5Y16HFQvTZf4 1dNS1tRtGwdtOhRKjyG6wQnnpBfTnxm4OpHMgy7IrbFYbqVNVaZhDhxC1Lv6BM+A == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrleekgddufedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfffgrnhcunfgrnhhgihhllhgvfdcuoegurghnsehlrghn ghhilhhlvgdrohhrgheqnecuffhomhgrihhnpehtfihithhtvghrrdgtohhmpdhimhgrgh gvsghinhdrtggrnecurfgrrhgrmhepmhgrihhlfhhrohhmpegurghnsehlrghnghhilhhl vgdrohhrghenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 53ADC8EE84; Wed, 15 May 2019 15:28:27 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-541-gda5ca9a-fmstable-20190515v2 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Wed, 15 May 2019 15:28:26 -0400 From: "Dan Langille" To: freebsd-stable@freebsd.org Subject: Re: 12.0-RELEASE-p4 kernel panic on i386 boot Content-Type: text/plain X-Rspamd-Queue-Id: 81FD86D615 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=langille.org header.s=fm1 header.b=aaJpgl6S; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=MMckKszJ; dmarc=pass (policy=none) header.from=langille.org; spf=pass (mx1.freebsd.org: domain of dan@langille.org designates 66.111.4.25 as permitted sender) smtp.mailfrom=dan@langille.org X-Spamd-Result: default: False [-6.47 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[langille.org:s=fm1,messagingengine.com:s=fm2]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[langille.org:+,messagingengine.com:+]; MX_GOOD(-0.01)[cached: in2-smtp.messagingengine.com]; DMARC_POLICY_ALLOW(-0.50)[langille.org,none]; NEURAL_HAM_SHORT(-0.99)[-0.992,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; IP_SCORE(-3.37)[ip: (-9.11), ipnet: 66.111.4.0/24(-4.48), asn: 11403(-3.22), country: US(-0.06)]; MID_RHS_WWW(0.50)[]; RCVD_IN_DNSWL_LOW(-0.10)[25.4.111.66.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 19:28:29 -0000 > Hi all, > > Wanted to make you aware of an issue I have encountered, sorry if this is > the wrong list. > > I upgraded from FreeBSD 12.0-RELEASE-p3 to p4 using: > > freebsd-fetch update > freebsd-fetch install > > and use the GENERIC kernel. Upon reboot the system kernel panics when > attempting to mount the filesystem read-write. This also happens in > single-user mode if selected at boot. > > Selecting the kernel.old from the boot menu boots the system with 12-p3 and > all works fine. I have uploaded a screenshot here: > > https://imagebin.ca/v/4hCc2Kk5YqCX > > The computer is an i386 system. I also upgraded using "freebsd-update fetch install". I also went from -p3 to -p4 on an i386. My screen shot is here: https://twitter.com/DLangille/status/1128734141569208320 Hope this helps. From owner-freebsd-stable@freebsd.org Wed May 15 19:42:58 2019 Return-Path: Delivered-To: freebsd-stable@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 7846C159FC8B for ; Wed, 15 May 2019 19:42:58 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it1-f179.google.com (mail-it1-f179.google.com [209.85.166.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 83FAD6E3D8 for ; Wed, 15 May 2019 19:42:57 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it1-f179.google.com with SMTP id i63so2133664ita.3 for ; Wed, 15 May 2019 12:42:57 -0700 (PDT) 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=7E0A5OLW1FJK4Kz6vTTbk7iDJ8D/WF8xf0rQdvODC7Y=; b=UrDu4hP89hqPEMltTL3DULDGeX8fnnH9ASQc+hab6V7RKsXGoBIe0uZJxMantZmTfk J6l+Tl8eGYHKS/M7Cp4R57EtBqTmJR5aArO987gFVPTZwuysRaOZlQQPXSBG/oF8TTp7 EOIIpYniAeqrpJ2VyZtu5R3etODnhnuo1lwY6xAhQxNCQTlOjaQQemLE6X/BCBnAioAy 3KSUoLhQEMW2Y+DWntBJzy6bQWXUiII1j8NI+yrmA2Mwbf56v99lbvrNMSOHP4WOObQr putoDeHbDLDC8wLESbzEaAbtoKLn3wpu3KwVO9kjaNrEmDxETp0BxhbUyv9rTNbeW0Jc qZEQ== X-Gm-Message-State: APjAAAUEaF9AJL9zl4eeh9OVzaDJHZPr+Iucf+5hM07+Hp6gcFUDi3l1 T24yr73SOC2yncZ7E2NeyBPLFs1qxu1ntMmp1b0= X-Google-Smtp-Source: APXvYqyvlBgaFEKmmkh7ej9lx+YGGoJt28k6jJrIb3/wRrMrxCxqOYoCeB9vmvILwk0eRIqDuUxrjIAxRGUeO2sqKt0= X-Received: by 2002:a24:2e86:: with SMTP id i128mr9122428ita.87.1557949015204; Wed, 15 May 2019 12:36:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ed Maste Date: Wed, 15 May 2019 00:03:07 -0400 Message-ID: Subject: Re: 12.0-RELEASE-p4 kernel panic on i386 boot To: wintellect Auser Cc: freebsd-stable stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 83FAD6E3D8 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.179 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-5.65 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[179.166.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.99)[-0.992,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; IP_SCORE(-2.64)[ip: (-7.35), ipnet: 209.85.128.0/17(-3.55), asn: 15169(-2.26), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 19:42:58 -0000 On Wed, 15 May 2019 at 15:09, wintellect Auser wrote: > > Hi all, > > Wanted to make you aware of an issue I have encountered, sorry if this is > the wrong list. This is the right place and thank you for reporting. Looking into it. From owner-freebsd-stable@freebsd.org Wed May 15 20:09:02 2019 Return-Path: Delivered-To: freebsd-stable@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 8DED915A092E for ; Wed, 15 May 2019 20:09:02 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it1-f173.google.com (mail-it1-f173.google.com [209.85.166.173]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7509F6F453 for ; Wed, 15 May 2019 20:09:01 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it1-f173.google.com with SMTP id e184so2287192ite.1 for ; Wed, 15 May 2019 13:09:01 -0700 (PDT) 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=aeWhOfEtbqLpXcQnrUuHeozT7bLYY93RljB6YQ2oiM0=; b=cTstbYgbFiDCwDqRhaJU7l7vCd2h/nuRVwyMli/4IJzs8rOvL2Py6OLFcc45YjNrhD UEcNgssbnY57aGfAqUlR5JSUFTxdNqrc32TjEt/XJ9qaeP9HegH6luaqK2cu+FqZW8UC NuKM+bJv1miGxBsVTxtYBXE5C55gDbC+9IIVlS8Im+YEL1BS7SbNxgl078SVP6U6b30j Lu/aBfZpmgGWkp2eWO5sOv5GdXN4XKQzCn2AM5CvDdnxfAKa51HZmNN4+vIPtBBPdYhQ Ax2j9YS4UcKbXkKMZO/vPGaxvA/NDJuAP666Y54gbkJMa/nj5yPr43b94UMSZ/GnoL5E YM6w== X-Gm-Message-State: APjAAAVw0c4wZLuOndVIn9ze/seyfOsVUuePDXHO4mm1FW7a3HD3RfJg LvDv7D8rRISzT6AMmE2lPs3EK3nIiJaR+QgHvR78rQ== X-Google-Smtp-Source: APXvYqwLAAIB0ABwtXYN+RaR6YPHUaKcLV017Gm7dtEQsvwGToJ6q5sB6/le9fbL5z6/1kgni+q7Jhs4T0l4lTLnCPA= X-Received: by 2002:a24:ac49:: with SMTP id m9mr3060229iti.174.1557950934933; Wed, 15 May 2019 13:08:54 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ed Maste Date: Wed, 15 May 2019 00:35:07 -0400 Message-ID: Subject: Re: 12.0-RELEASE-p4 kernel panic on i386 boot To: wintellect Auser Cc: freebsd-stable stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 7509F6F453 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.173 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-5.67 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; 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.99)[-0.992,0]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@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)[173.166.85.209.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.67)[ip: (-7.48), ipnet: 209.85.128.0/17(-3.55), asn: 15169(-2.26), country: US(-0.06)] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 20:09:02 -0000 On Wed, 15 May 2019 at 00:03, Ed Maste wrote: > > On Wed, 15 May 2019 at 15:09, wintellect Auser wrote: > > > > Hi all, > > > > Wanted to make you aware of an issue I have encountered, sorry if this is > > the wrong list. > > This is the right place and thank you for reporting. Looking into it. It looks like a new update for 12.0 i386 will be needed and will be rolled out as soon as possible. From owner-freebsd-stable@freebsd.org Wed May 15 23:45:46 2019 Return-Path: Delivered-To: freebsd-stable@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 E2E4B15A597D for ; Wed, 15 May 2019 23:45:45 +0000 (UTC) (envelope-from steven@multiplay.co.uk) 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 EAE8476730 for ; Wed, 15 May 2019 23:45:44 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id AB82D15A597A; Wed, 15 May 2019 23:45:44 +0000 (UTC) Delivered-To: stable@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 6F26A15A5977 for ; Wed, 15 May 2019 23:45:44 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD34B76729 for ; Wed, 15 May 2019 23:45:43 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: by mail-lf1-x135.google.com with SMTP id v18so1156456lfi.1 for ; Wed, 15 May 2019 16:45:43 -0700 (PDT) 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=WoYWoujmJ9Eb0/yRXHQhV1vbONqyQ2OQiKw/cYojH74=; b=DbfnqZAjF4HUI0XReIT1/HUBvNOYspmcYRn2FX0Zab7pUEyipPGdNQlqwAkB3njMHW aI1ztla8GIOY70WjjSj8rcltshttgM8h85nBwANqUgr1t6A+FtF55TqXWY36Nm3ujZbr L7JHXx8DDKk/JLSBeKH0CJmu+otzFBtBPPtrHMrsVQgNVcASttVLSjUIGFQFWjtWN8JN lr4WinGRuPhUQ8BDMOLTcA5LofW0qHQav+1p/SbYjO6oanmQIRXf42pMpHl7rk8FN96G 95iaS9Niks2xzwNO64ZRAlodJvKkiFBgsj6Agn0vPgEMBUsU3DlPMr6a0uku2huJnyl+ W9PA== 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=WoYWoujmJ9Eb0/yRXHQhV1vbONqyQ2OQiKw/cYojH74=; b=EBd46k+/za+cGAYUFvf0oelqinxxk5RT2VmL3fSeSUTPtpUXgckuEKiKFF/tvOdmrp MfVAvHjVtUXPzdY4x7WwIq785lTGvon1N4hYJDDLSEo4XKjKUlLgSGSgj1GmVMnQyKAT 40FQ4QjqXn1Cx/+ouub2hTKWWmksBISOmIz2DXW97UfgTCikqO5EnebrTsyn0lUSMM6s AwyjEb5BI9XaqI1Ob4BqGMgN9vtEqnUnatQYx6z51ZKgCLYA6U+c7s0VK0MmtQv6hg2Q Wqpocgeb47AjD49PlkqUb0LvBkldramzZ2ChH4nO77qGf9MuOcFiZZZOmmCItUr/M15Y oscA== X-Gm-Message-State: APjAAAX1lNWnSgBx9Uvd6kXlBS9QyHxIyXXdL92hUj9xE3doTJBn4GU7 SncN16X82PpFKRum9PayUmSP1VywOrZchSiJlYQaZrJ6 X-Google-Smtp-Source: APXvYqy/1qqvY8SjK/EMA6HnhqYT/DifwKK4HcD2LbmC0SzbXyVaVy18p/7WHYD8irokCNbfEGQ2BmDA3JUqS3wNIi0= X-Received: by 2002:a19:29c4:: with SMTP id p187mr21870236lfp.69.1557963941705; Wed, 15 May 2019 16:45:41 -0700 (PDT) MIME-Version: 1.0 References: <201905151544.x4FFiR0G067138@fire.js.berklix.net> In-Reply-To: <201905151544.x4FFiR0G067138@fire.js.berklix.net> From: Steven Hartland Date: Thu, 16 May 2019 00:45:29 +0100 Message-ID: Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: "Julian H. Stacey" Cc: Alan Somers , FreeBSD Core Team , FreeBSD Stable ML , "freebsd-hackers@freebsd.org" X-Rspamd-Queue-Id: CD34B76729 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.947,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 23:45:46 -0000 Is disagree, having them hatched causes us less work not more, as others have said one update not many, which result in one outage of systems that need patching not many. Regards Steve On Wed, 15 May 2019 at 16:48, Julian H. Stacey wrote: > Hi, Reference: > > From: Alan Somers > > Date: Wed, 15 May 2019 08:32:26 -0600 > > Alan Somers wrote: > > On Wed, May 15, 2019 at 8:26 AM Julian H. Stacey > wrote: > > > > > > Hi core@, > > > cc hackers@ & stable@ > > > > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > > > Volunteers who contribute actual fixes are very much appreciated; > > > But those styled as 'management' who delay announcements to batch > floods > > > damage us. As they've previously refused to stop, it's time to sack > them. > > > > > > Just send each announcement out when ready, no delays to batch them. > > > No sys admins can deal with 8 in 3 mins: > > > Especially on multiple systems & releases. Recipients start > > > mitigating, then more flood in, & need review which are > > > most urgent to interrupt to; While also avoiding sudden upgrades > > > to many servers & releases, to minimise disturbing server users, > > > bosses & customers. > > > > > > Cheers, > > > Julian > > > -- > > > Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich > Aachen Kent > > > http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in > EU. > > > Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers > died. > > > > I disagree, Julian. I think SAs are easier to deal with when they're > > batched. True, I can't fix the first one in less than 3 minutes. But > > then I probably wouldn't even notice it that fast. Batching them all > > together means fewer updates and reboots. > > Batching also means some of these vulnerabilities could have been > fixed earlier & less of a surge of demand on recipient admins time. > > An admin can find time to ameliorate 1 bug, not 8 suddenly together. > Avoidance is called planning ahead. Giving warning of a workload. > Like an admin plans ahead & announces an outage schedule for planned > upgrade. > > Suddenly dumping 8 on admins causes overload on admin manpower. > 8 reason for users to approach admin in parallel & say > "FreeBSD seems riddled, how long will all the sudden unplanned > outages take ? Should we just dump it ?" > Dont want negative PR & lack of management. > > Cheers, > Julian > -- > Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen > Kent > http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. > Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers > died. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Thu May 16 00:30:34 2019 Return-Path: Delivered-To: freebsd-stable@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 B741E15A733C for ; Thu, 16 May 2019 00:30:34 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.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 08F7C8003B for ; Thu, 16 May 2019 00:30:34 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: by mailman.ysv.freebsd.org (Postfix) id B7DAB15A733A; Thu, 16 May 2019 00:30:33 +0000 (UTC) Delivered-To: stable@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 A57D215A7338; Thu, 16 May 2019 00:30:33 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (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 4839780036; Thu, 16 May 2019 00:30:33 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (chombo [IPv6:2601:1c2:1402:1770:ae1f:6bff:fe6b:9e1c]) by echo.brtsvcs.net (Postfix) with ESMTPS id 9639E38D09; Wed, 15 May 2019 17:30:23 -0700 (PDT) Received: from [IPv6:2601:1c2:1402:1770:5c80:9656:5574:b3a3] (unknown [IPv6:2601:1c2:1402:1770:5c80:9656:5574:b3a3]) by chombo.houseloki.net (Postfix) with ESMTPSA id CBEB02830; Wed, 15 May 2019 17:30:22 -0700 (PDT) Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: "Julian H. Stacey" , core@freebsd.org Cc: stable@freebsd.org, hackers@freebsd.org References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> From: Mel Pilgrim Message-ID: Date: Wed, 15 May 2019 17:30:23 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <201905151425.x4FEPNqk065975@fire.js.berklix.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4839780036 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] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 00:30:35 -0000 On 2019-05-15 7:25, Julian H. Stacey wrote: > Hi core@, > cc hackers@ & stable@ > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > Volunteers who contribute actual fixes are very much appreciated; > But those styled as 'management' who delay announcements to batch floods > damage us. As they've previously refused to stop, it's time to sack them. > > Just send each announcement out when ready, no delays to batch them. > No sys admins can deal with 8 in 3 mins: > Especially on multiple systems & releases. Recipients start > mitigating, then more flood in, & need review which are > most urgent to interrupt to; While also avoiding sudden upgrades > to many servers & releases, to minimise disturbing server users, > bosses & customers. Admins attentive to security issues will already be tracking CVEs for the software they use and mitigating or solving the vulnerability by all means available. By batching updates, FreeBSD is making administrative decisions for other people's systems. Some folks don't need to worry about scheduling downtime and will benefit from faster update availability. Folks who need to worry about scheduling downtime are already going to batch updates and should be allowed to make those decisions for themselves. Batched SAs help in neither case. Example: the ntpd CVE is more than two months old, and was rapidly fixed in ports. I was able to switch my systems to the ports ntpd during a scheduled downtime window in March instead of doing it this weekend. So not only did I benefit from the faster update availability, I was able to make my own decision about my own systems and significantly reduce my exposure. Don't be Microsoft. Don't sit on security updates. From owner-freebsd-stable@freebsd.org Thu May 16 02:22:57 2019 Return-Path: Delivered-To: freebsd-stable@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 5E90415A98E8 for ; Thu, 16 May 2019 02:22:57 +0000 (UTC) (envelope-from instructionset@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 CE0D183DD2 for ; Thu, 16 May 2019 02:22:56 +0000 (UTC) (envelope-from instructionset@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8E74C15A98E6; Thu, 16 May 2019 02:22:56 +0000 (UTC) Delivered-To: stable@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 6B35115A98E4; Thu, 16 May 2019 02:22:56 +0000 (UTC) (envelope-from instructionset@gmail.com) Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0AB783DCF; Thu, 16 May 2019 02:22:55 +0000 (UTC) (envelope-from instructionset@gmail.com) Received: by mail-qt1-x835.google.com with SMTP id a17so2196227qth.3; Wed, 15 May 2019 19:22:55 -0700 (PDT) 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=wBDoL9ETXLKGVdtsjswvUuCbh10DtPWEAWpeD+ykn3I=; b=j8G2OS84+odKhL6VrGkeQUo2HXia/Y2eEb/Kt8Uo4G/bBpBg/MpT0Kv4W8ejBE1h70 9Yo3+A3sqocioAka9Z0mma2CzV3sJ3vybcT7dzYnXMmAGbmdWQHhq8D4FeTm/Z9OVBoU n68FPU+UW/L3UQV/4vDuYj+Ba46IL+aqnl9qVsDKfzHKwgq5vlGz/tNUv7bZlODKF5dV WSlY2gbppHvEzIxwYAEh9maNyJMC87FMdWOO08xtxYPRj2ME7vxPiD8+p6vNLY7zo04W 47K0LtP4Z2TSTxtmR47C3FygLsL+e4tCJTpFP4DjvNdwHUF2QjNRG9blT7CJLRsmPVQz ZrNg== 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=wBDoL9ETXLKGVdtsjswvUuCbh10DtPWEAWpeD+ykn3I=; b=bNGBlynm0Zw524oFKyyXLLzdcFUjWDrHc2uvkCmH4dwEYeyvHlxRqJAI1waYoUsSJU EaMUgAWYuqoSsxDXeNBxxQH9TBRsN6X5VnbeRm2zgoap3Tydgn/XZKfqIc9cTMLcXXPH v3azEthTXGfTlUl1wxlYzaLFf8OGsKwRAwNahESWDExZgjdwUURZJ0cCX8GcKykeSVN5 ItpoXSoJngEUsX16iwCmg0ZDwg6p9ZJbe9KwyUXwViOQuCRG4hN5aHTDYJfQElhTB4RT UxXNu4+V0ydqOTeu6UMtJtwUwfc9WVcplEdY7OY3WMukehysz7M4RCmtNc8QgnFv5L0b zn3w== X-Gm-Message-State: APjAAAWLcwdQuMg2dA4svpwZf/RaNKDLrmNQN+rZzKNvJ/P2GWVqtC2a GUz4VsyrPFjH9Whh09FxqHi9i564QfV3BG52Sd0= X-Google-Smtp-Source: APXvYqxAvCqMMQ2XkzNyP8qBDy18kd7PRu2keHlBRMFh+FqTQXAN5zMKhIE4ZxbxSKX0YnBOV/5YqIhZ6doaOx8waAg= X-Received: by 2002:a0c:d941:: with SMTP id t1mr36664074qvj.204.1557973375152; Wed, 15 May 2019 19:22:55 -0700 (PDT) MIME-Version: 1.0 References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> In-Reply-To: From: Bill Sorenson Date: Wed, 15 May 2019 21:22:45 -0500 Message-ID: Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: Mel Pilgrim Cc: "Julian H. Stacey" , core@freebsd.org, stable@freebsd.org, hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: F0AB783DCF X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.96)[-0.965,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 02:22:57 -0000 > Admins attentive to security issues will already be tracking CVEs for > the software they use and mitigating or solving the vulnerability by all > means available. > > By batching updates, FreeBSD is making administrative decisions for > other people's systems. Some folks don't need to worry about scheduling > downtime and will benefit from faster update availability. Folks who > need to worry about scheduling downtime are already going to batch > updates and should be allowed to make those decisions for themselves. > Batched SAs help in neither case. > > Example: the ntpd CVE is more than two months old, and was rapidly fixed > in ports. I was able to switch my systems to the ports ntpd during a > scheduled downtime window in March instead of doing it this weekend. So > not only did I benefit from the faster update availability, I was able > to make my own decision about my own systems and significantly reduce my > exposure. > > Don't be Microsoft. Don't sit on security updates. I'm inclined to agree with this sentiment. I can sort of understand holding a SA for a week while waiting for another SA's embargo to end but beyond that I think the patches for Security Advisories should be made available as soon as practical. SysAdmins need to be smart enough to plan updating strategies, whether they can get away with patching quarterly, monthly, weekly, immediately, etc. It depends on the systems and the circumstances. I appreciate the SO's work, but in my opinion if a patch to a CVE makes it to STABLE it should be in the patch branch within a week or so unless issues are discovered (and depending on the severity of the issue maybe it should be pushed anyway with caveats.) FreeBSD already makes a distinction between SAs and Errata unlike some other projects, I think that should factor into how they are delivered. Security Advisories should be made available quickly regardless of whether they are known the be exploited in the wild or we might as well just go the Linux route and call everything a 'bug fix' and not bother categorizing things at all. From owner-freebsd-stable@freebsd.org Thu May 16 02:53:00 2019 Return-Path: Delivered-To: freebsd-stable@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 E37AF15AA30E for ; Thu, 16 May 2019 02:52:59 +0000 (UTC) (envelope-from matt.garber@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 4C53E84F2F for ; Thu, 16 May 2019 02:52:59 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 09EB915AA30D; Thu, 16 May 2019 02:52:59 +0000 (UTC) Delivered-To: stable@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 D97E115AA30B; Thu, 16 May 2019 02:52:58 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7BB5E84F23; Thu, 16 May 2019 02:52:58 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: by mail-qt1-x82c.google.com with SMTP id d13so2234490qth.5; Wed, 15 May 2019 19:52:58 -0700 (PDT) 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=O1k/hdGvverXmfo/LcfqRE2On8EaDRUEEDoqpA+503c=; b=fBbWbUs3or66X3yu9LW0m0KF6xYQzXMrm9GkRW/YX3vrEl8sPnKPzmNbon8n1OqxwV GycF5ZJjNg7MEZD4IUfF2H6g069oRxCDRaE/+14xu/5XDe5+6YSVxSCQv3OvTBBp33Qh KtvuIh/ovS2OgqnFdqBQQsHjyXCQKd14gtM+ebg6L+EBqbDWQjAMKmr6Tw0EuYCrQ5D9 BdQKGqd7f/t5pDCwFg8f11+wf1mdhyiOvBain8VmG81cTKsJAwtNvPhC9E4MfeaJxjid hZUCk84V6cvNnueyjt7q5tZNefI+047Ui4u2IO+GsJUx5Yt2wOPiEBhzd6uSHGpGDzI5 IdKQ== 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=O1k/hdGvverXmfo/LcfqRE2On8EaDRUEEDoqpA+503c=; b=tolmfI5afI+l6cppzI9ADeJF4LqFiCzMzhY3PupCgqJuPdUyD2+3XrxGpFcXV0M6cI 0MGML96/rnERn87keqH+pfImWNi90hm2NNZN/CTmpZNXfvEK85zTiJcqIbcMg3lZH0jd uhrYeCXeBM/ZC/eh+Z41t5g8gSvvrIabAqV3yFPViFdqPXE4HPCBzbj9Aoo//89OlFkm eNq9hXPl7QBFq1sOTdce7Abj7P8KJjGjPa+fW00Ox7pCZ+MVv0TDSWlf2DrwuKHtuny4 ZUpIUMfFx1k6+srWkFp02x5D6mrWfwOVaey2qKze7VpGzhfHumSexDhNDSsfvXUjLXGR igeA== X-Gm-Message-State: APjAAAXJWcRxVCpUGD7MCMscpxMKUp0764D5d8XgnKmuhDuzF4EPumOX 90N5nj1VWsibUQEvhmswUsB6keLW9sI/GJfGWn8= X-Google-Smtp-Source: APXvYqxhD43BDwic9gN2kZgMcZb0UWbONCUDXyeCfe7vK27wkuCW6hKV9GXtJ07CeUKvPtHR0keuC25Rw26TVkYiDI8= X-Received: by 2002:a0c:9350:: with SMTP id e16mr35026920qve.119.1557975178032; Wed, 15 May 2019 19:52:58 -0700 (PDT) MIME-Version: 1.0 References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> In-Reply-To: From: Matt Garber Date: Wed, 15 May 2019 22:52:47 -0400 Message-ID: Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: Bill Sorenson Cc: "Julian H. Stacey" , Mel Pilgrim , core@freebsd.org, hackers@freebsd.org, stable@freebsd.org X-Rspamd-Queue-Id: 7BB5E84F23 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.97)[-0.965,0]; REPLY(-4.00)[]; TAGGED_FROM(0.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-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 02:53:00 -0000 On Wed, May 15, 2019 at 10:28 PM Bill Sorenson wrote: > > Admins attentive to security issues will already be tracking CVEs for > > the software they use and mitigating or solving the vulnerability by al= l > > means available. > > > > By batching updates, FreeBSD is making administrative decisions for > > other people's systems. Some folks don't need to worry about schedulin= g > > downtime and will benefit from faster update availability. Folks who > > need to worry about scheduling downtime are already going to batch > > updates and should be allowed to make those decisions for themselves. > > Batched SAs help in neither case. > > > > Example: the ntpd CVE is more than two months old, and was rapidly fixe= d > > in ports. I was able to switch my systems to the ports ntpd during a > > scheduled downtime window in March instead of doing it this weekend. S= o > > not only did I benefit from the faster update availability, I was able > > to make my own decision about my own systems and significantly reduce m= y > > exposure. > > > > Don't be Microsoft. Don't sit on security updates. > > I'm inclined to agree with this sentiment. I can sort of understand > holding a SA > for a week while waiting for another SA's embargo to end but beyond that = I > think > the patches for Security Advisories should be made available as soon as > practical. SysAdmins need to be smart enough to plan updating strategies, > whether they can get away with patching quarterly, monthly, weekly, > immediately, > etc. It depends on the systems and the circumstances. I appreciate the SO= 's > work, but in my opinion if a patch to a CVE makes it to STABLE it should > be in > the patch branch within a week or so unless issues are discovered (and > depending > on the severity of the issue maybe it should be pushed anyway with > caveats.) > > FreeBSD already makes a distinction between SAs and Errata unlike some > other > projects, I think that should factor into how they are delivered. > Security Advisories should be made available quickly regardless of whethe= r > they > are known the be exploited in the wild or we might as well just go the > Linux > route and call everything a 'bug fix' and not bother categorizing things > at all. I=E2=80=99m certainly not advocating holding on to SAs for an extended peri= od of time, either: if something like the ntpd fix takes a long time to roll out on a consistent basis, maybe that=E2=80=99s rationale for the separate disc= ussion of further shrinking the base system (?), since what=E2=80=99s =E2=80=98bes= t=E2=80=99 for the majority of users in that scenario is probably getting that patched via packages/ports in days, not weeks (or months). However, I otherwise don=E2=80=99t find anything objectionable to releasing= several ENs or SAs at once, assuming they were close in time anyway. E.g., I think it=E2=80=99s perfectly sane to publish 4-5 advisories/notices at once on a = Thursday rather than one on Monday, one on Tuesday, two on Wednesday, etc., especially since we don=E2=80=99t yet have pkg base, and it fits the model = of RELEASE-pX to RELEASE-pY bundling those up. I=E2=80=99m not sure what you meant about Linux distros not categorizing fi= xes, though =E2=80=94 with some notable exceptions, most of the big ones certain= ly tag security fixes separately, which is what allows `unattended-upgrades` on Debian/Ubuntu based systems (and `yum-cron` on RHEL) to work so nicely automatically as scheduled on *only* security errata, while leaving all other types of updates alone for admin intervention. =E2=80=94 Matt From owner-freebsd-stable@freebsd.org Thu May 16 02:55:19 2019 Return-Path: Delivered-To: freebsd-stable@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 661B715AA3FD for ; Thu, 16 May 2019 02:55:19 +0000 (UTC) (envelope-from greg.bal4@gmail.com) Received: from mail-it1-x142.google.com (mail-it1-x142.google.com [IPv6:2607:f8b0:4864:20::142]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E70D850D5 for ; Thu, 16 May 2019 02:55:18 +0000 (UTC) (envelope-from greg.bal4@gmail.com) Received: by mail-it1-x142.google.com with SMTP id a190so3664089ite.4 for ; Wed, 15 May 2019 19:55:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=PnHWylnIHfcxfmMkXa9KSbLu1FFeu4p4OoPB9gbbK0U=; b=jPajXbVdsRCjHW0TMRKwIuMRbb7cHi+zA70TVXBWLssKUUjXysulAX7s5jEQB3d/cM lJvMwUbyL40nsfl7l8Bghq2xU6lyggYOzFm+kBnwpywy61EZbjIlAI1OhMq/BOtkSBFh jkfebaCa/eWP7GnZiqFn5aB0mAvyXmbdaduk2JJlj3ZnIvVUfZYztPZTaO/EOplIdWS8 LwbdaF6DrCxPhfunpm7NRrswKceJGTQB3g3689gCxPwgot9KpATpmNjN0k+uwzAPh2au aGN7Mq4g1r8TCNkzNyR0CUibi4Q/IFCqSckmd3hJvWhnmc0QK6D1BGSOyU0WJc5B9qjZ kdLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PnHWylnIHfcxfmMkXa9KSbLu1FFeu4p4OoPB9gbbK0U=; b=iLTFY1rTq6E5CZRGiob/hIE4MWqzLTaZwn5x99Bixt/nRf8lBZSHcgXYU/BlhZlumW Iggy3AH/TnB35Ek71UF4A/2Qns9FavgkpZn9lhitKSWrAZ8nXVAmJJ8vJBTEHJJnrXP2 VcJweSMTpLfheMZpoP4vQQmSL6TtSE4RcgmAFruofGsq/iXcgz7ExHQda7XDKfUJyqZv cVjQtf56vO8onXBCs/ulNe6YoFwgIzWGnF9NCFKWilrx+bARgOVodh8mQrUeS1PUMHhq AAXy199C3tNMC4+/lxjoCWm6EJ/qDK0YnZFpKdoIGviXPVDvCoepWWaWZDNpdvfD7iGZ ahtA== X-Gm-Message-State: APjAAAURbtg8KeH40uC9kHUj3f0P8iOfzVhN14phIrWvm9oVZDKwshRu va+rcuW7rzNwz88G8Rn7uctPSku+3mOsp8Fq2hocte+p X-Google-Smtp-Source: APXvYqwd4DugPCYw6k3VTa0m37nn6C3QInYWhQNhzuwn3U+I3bWX9diGBpXSLMOcv/7gMra2E0ahAjsaH4tgPaB9G6g= X-Received: by 2002:a24:6c13:: with SMTP id w19mr9766217itb.144.1557975317516; Wed, 15 May 2019 19:55:17 -0700 (PDT) MIME-Version: 1.0 From: Greg Balfour Date: Wed, 15 May 2019 21:55:06 -0500 Message-ID: Subject: FreeBSD-SA-19:03 source code patch To: freebsd-stable@freebsd.org X-Rspamd-Queue-Id: 2E70D850D5 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=jPajXbVd; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gregbal4@gmail.com designates 2607:f8b0:4864:20::142 as permitted sender) smtp.mailfrom=gregbal4@gmail.com X-Spamd-Result: default: False [-4.73 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.96)[-0.959,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)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.76)[ip: (1.78), ipnet: 2607:f8b0::/32(-3.25), asn: 15169(-2.26), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[2.4.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]; 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-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 02:55:19 -0000 After applying wpa-11.patch (and the rest of the recent patches) to my 11.2 machine I'm having build problems. Looks like a binder directory and associated files did not get created. Pilot error? # uname -a FreeBSD freebsd.example.com 11.2-RELEASE FreeBSD 11.2-RELEASE #0: Thu Jan 3 19:29:29 CST 2019 root@freebsd.example.com:/usr/obj/usr/src/sys/GENERIC amd64 --- notify.o --- cc -target x86_64-unknown-freebsd11.2 --sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -I/usr/src/usr.sbin/wpa/wpa_supplicant -I/usr/src/contrib/wpa//hostapd -I/usr/src/contrib/wpa//src -I/usr/src/contrib/wpa//src/common -I/usr/src/contrib/wpa//src/crypto -I/usr/src/contrib/wpa//src/drivers -I/usr/src/contrib/wpa//src/l2_packet -I/usr/src/contrib/wpa//src/utils -I/usr/src/contrib/wpa//src/wps -DCONFIG_CTRL_IFACE -DCONFIG_CTRL_IFACE_UNIX -DNEED_AP_MLME -DTLS_DEFAULT_CIPHERS=\"DEFAULT:!EXP:!LOW\" -DCONFIG_BACKEND_FILE -DCONFIG_DEBUG_SYSLOG -DCONFIG_DRIVER_BSD -DCONFIG_DRIVER_NDIS -DCONFIG_DRIVER_WIRED -DCONFIG_GAS -DCONFIG_HS20 -DCONFIG_IEEE80211R -DCONFIG_INTERWORKING -DCONFIG_PEERKEY -DCONFIG_PRIVSEP -DCONFIG_SMARTCARD -DCONFIG_TERMINATE_ONLASTIF -DCONFIG_TLS=openssl -DCONFIG_WPS -DCONFIG_WPS2 -DCONFIG_WPS_UPNP -DPKCS12_FUNCS -DEAP_GTC -DEAP_LEAP -DEAP_MD5 -DEAP_MSCHAPv2 -DEAP_OTP -DEAP_PEAP -DEAP_PSK -DEAP_TLS -DEAP_TTLS -DIEEE8021X_EAPOL -DCONFIG_SHA256 -DEAP_TLS_OPENSSL -I/usr/src/usr.sbin/wpa/wpa_supplicant -I/usr/src/contrib/wpa//hostapd -I/usr/src/contrib/wpa//src -I/usr/src/contrib/wpa//src/common -I/usr/src/contrib/wpa//src/crypto -I/usr/src/contrib/wpa//src/drivers -I/usr/src/contrib/wpa//src/l2_packet -I/usr/src/contrib/wpa//src/utils -I/usr/src/contrib/wpa//src/wps -DCONFIG_CTRL_IFACE -DCONFIG_CTRL_IFACE_UNIX -DNEED_AP_MLME -DTLS_DEFAULT_CIPHERS=\"DEFAULT:!EXP:!LOW\" -g -MD -MF.depend.notify.o -MTnotify.o -std=gnu99 -fstack-protector-strong -Qunused-arguments -c /usr/src/contrib/wpa//wpa_supplicant/notify.c -o notify.o /usr/src/contrib/wpa//wpa_supplicant/notify.c:16:10: fatal error: 'binder/binder.h' file not found #include "binder/binder.h" ^~~~~~~~~~~~~~~~~ 1 error generated. *** [notify.o] Error code 1 make[5]: stopped in /usr/src/usr.sbin/wpa/wpa_supplicant 1 error From owner-freebsd-stable@freebsd.org Thu May 16 03:13:33 2019 Return-Path: Delivered-To: freebsd-stable@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 32EDC15AABE9 for ; Thu, 16 May 2019 03:13:33 +0000 (UTC) (envelope-from SRS0=HRFA=TQ=quip.cz=000.fbsd@elsa.codelab.cz) 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 AFEB685E75 for ; Thu, 16 May 2019 03:13:32 +0000 (UTC) (envelope-from SRS0=HRFA=TQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: by mailman.ysv.freebsd.org (Postfix) id 6C8D315AABE8; Thu, 16 May 2019 03:13:32 +0000 (UTC) Delivered-To: stable@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 5872415AABE7 for ; Thu, 16 May 2019 03:13:32 +0000 (UTC) (envelope-from SRS0=HRFA=TQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 DCC3B85E74 for ; Thu, 16 May 2019 03:13:31 +0000 (UTC) (envelope-from SRS0=HRFA=TQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 836AD28417; Thu, 16 May 2019 05:13:28 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 53DC628411; Thu, 16 May 2019 05:13:27 +0200 (CEST) Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: Mel Pilgrim Cc: stable@freebsd.org References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Thu, 16 May 2019 05:13:30 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: DCC3B85E74 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]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 03:13:33 -0000 Mel Pilgrim wrote on 2019/05/16 02:30: [...] > By batching updates, FreeBSD is making administrative decisions for > other people's systems.  Some folks don't need to worry about scheduling > downtime and will benefit from faster update availability.  Folks who > need to worry about scheduling downtime are already going to batch > updates and should be allowed to make those decisions for themselves. > Batched SAs help in neither case. > > Example: the ntpd CVE is more than two months old, and was rapidly fixed > in ports.  I was able to switch my systems to the ports ntpd during a > scheduled downtime window in March instead of doing it this weekend.  So > not only did I benefit from the faster update availability, I was able > to make my own decision about my own systems and significantly reduce my > exposure. > > Don't be Microsoft. Don't sit on security updates. +1 Delaying / hiding security updates cannot be good. The vulnerability already exists. Delayed updates do favor to "bad persons", not sysadmins. Even information about found vulnerability is more valuable for sysadmins than silence. Some vulnerabilities can be mitigated by configuration changes or some service replacement (eg. ntpd). But if I don't know that there is some vulnerability I cannot do anything. It would also be good if base system vulnerabilities are first published in FreeBSD vuxml. Then it can be reported to sysadmins by package security/base-audit. None of these recent Sec. Advisories are listed in Vuxml yet! It's bad example of not dog fooding there. I am not saying that FreeBSD SO do bad work. I really appreciate it. But there is still something to improve. Kind regards Miroslav Lachman From owner-freebsd-stable@freebsd.org Thu May 16 03:15:21 2019 Return-Path: Delivered-To: freebsd-stable@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 D775615AAC7C for ; Thu, 16 May 2019 03:15:20 +0000 (UTC) (envelope-from instructionset@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 689C585F4B for ; Thu, 16 May 2019 03:15:20 +0000 (UTC) (envelope-from instructionset@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 256C615AAC67; Thu, 16 May 2019 03:15:20 +0000 (UTC) Delivered-To: stable@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 02BC415AAC66; Thu, 16 May 2019 03:15:20 +0000 (UTC) (envelope-from instructionset@gmail.com) Received: from mail-qk1-x742.google.com (mail-qk1-x742.google.com [IPv6:2607:f8b0:4864:20::742]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 77D3E85F44; Thu, 16 May 2019 03:15:19 +0000 (UTC) (envelope-from instructionset@gmail.com) Received: by mail-qk1-x742.google.com with SMTP id a132so1338154qkb.13; Wed, 15 May 2019 20:15:19 -0700 (PDT) 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:content-transfer-encoding; bh=Kk6MKPCZhUgEySkC0hBC92tUyiSFb4lVIMPOQTE2WVE=; b=cQ2lPOX2Mfmel71b8bROf5Y41qQx9y9uSkHXW9Qc4WfYbfTmuzJOM1DwGwULOZt2wZ iE+iyUJUgBbUW1OORsQjojO/u01vpuUFIOLuB0Bp4/qEgKkFo2id22hETN/3QSVSDHmb Dm1eEO1ieEzOAy25PGVKqN8lXJafHvsp/jFw5hzjgIL01CvHT2szqR8LCZP6gNfI9lIB sIMibq97t/Rk/GPoiPUTHWGkhoCJ01hA3vSskTvHUKQvNHwMRg08UUvTkXvATY1QqyHG UAkhl4jsF5yRjkHWdwy3FVUC887NMI+LMFqyKQEHlviBXkWPBLC+4EcwEZ8/kS/GPVMM +u4g== 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:content-transfer-encoding; bh=Kk6MKPCZhUgEySkC0hBC92tUyiSFb4lVIMPOQTE2WVE=; b=A5gDJIcc1wrSHc89ho96RN4Z0XmzR0Gsbnwx/TKRwV6n8X68SYz1ooVwNgF+k4S99e HlVNEesxjI6kBNBH/F1tkoozJD0wf8b5PUnWRitWBKM1NyzGWwUsm2uePFnW693xpN8I O4ZNuV/dg6On0CCdRrpQV0VxK5HnVmR18EvxguPzpQNtax2TZBda2Q0bcF3Tvov87g3y C+Ge+DMMd1GMcVh801eRcXVp1yzMztkImYgqxkTTQvKN3fB1HXBUbKMGsWl1ayCRYIeU Twj39DIbpKifSEUK3QxZkIsuGYwd56z00m8oRhlIpmPDL234Xp48MCMImStouFsrQyuY mQsg== X-Gm-Message-State: APjAAAUrcnsm7KTrkxVEhqm5cwjb5C/Sefvbs+BPds+zgJjW7HbO5Z+H +XVxS+/SeqdnDecXGZ+beFgtK0ZS4jGjo459r4tBlNx6 X-Google-Smtp-Source: APXvYqzVbKH8WeDVT0UVaxRkVNgrqVeHW5pB/M3urrxRF9TEJVl2u7TikfH3I5/xR7T6B09intWCeGA6yNykXx9bRLQ= X-Received: by 2002:a37:b4c6:: with SMTP id d189mr36546789qkf.173.1557976518928; Wed, 15 May 2019 20:15:18 -0700 (PDT) MIME-Version: 1.0 References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> In-Reply-To: From: Bill Sorenson Date: Wed, 15 May 2019 22:15:08 -0500 Message-ID: Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: Matt Garber Cc: "Julian H. Stacey" , Mel Pilgrim , core@freebsd.org, hackers@freebsd.org, stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 77D3E85F44 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; TAGGED_RCPT(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.969,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 03:15:21 -0000 > I=E2=80=99m not sure what you meant about Linux distros not categorizing = fixes, though =E2=80=94 with some notable exceptions, most of the big ones = certainly tag security fixes >separately, which is what allows `unattended-= upgrades` on Debian/Ubuntu based systems (and `yum-cron` on RHEL) to work s= o nicely automatically as scheduled on > *only* security errata, while leav= ing all other types of updates alone for admin intervention. My comment about Linux was not in regards to any particular distro, they al= l have interesting policies of varying effectiveness when it comes to release engineering, but specifically about the Linux kernel team (Torvalds Et al,) which last I checked had a policy of specifically not handling security iss= ues any different from any generic bug. Distros may do their own kernel release engineering and handling that themselves which is fine. From owner-freebsd-stable@freebsd.org Thu May 16 03:17:18 2019 Return-Path: Delivered-To: freebsd-stable@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 AC19315AAE80 for ; Thu, 16 May 2019 03:17:18 +0000 (UTC) (envelope-from asomers@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 313F0860C2 for ; Thu, 16 May 2019 03:17:18 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id E284015AAE7D; Thu, 16 May 2019 03:17:17 +0000 (UTC) Delivered-To: stable@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 A648115AAE7C for ; Thu, 16 May 2019 03:17:17 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F50E860BF for ; Thu, 16 May 2019 03:17:17 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lj1-f174.google.com with SMTP id 14so1670166ljj.5 for ; Wed, 15 May 2019 20:17:17 -0700 (PDT) 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=fL9TD62dCUyxS5K2NG5OKFCTKTfOCcicg+txCg7jcbE=; b=KcJjK/UznsJ6oreS/Iz0NpFd9A7GlIspmF9wHiv9cMwPOTAQtdPBoUPRi5R1HYhmKc XpDpT7azlpHU8DUgUSiELwrphy5f2sbLCfAlGnROjPyQqnxsRPoUmnYm3E4hw/jZZ5Cx 3e5WDRuMPsaEUCoWXlJbRaBZ4NtkvAqHuQuPvkiqLimfmG59I+72neNK65uEjVgLHA2p 6JwerpWgWrwUeD4FMj6OYf3ykMZFpwkFqLUNzq+L7BbPDgh+jzvkhfr5O9LDCCefSvhy E7FWZIeewRzBJ7XDrxx4uSI1mo+GZezjI27pyGJmw6XXPJUOXWbN52habVdwqUFyMarA HwnQ== X-Gm-Message-State: APjAAAXUD2Ayu+n3khmsBttXd1VH7HxYCBnqxdHHkxAdgI/zAMz6B7Ij qOH1Ezw+/xPucJ69dNzRVQI3XLj6UuEKW/mu6YErhLql X-Google-Smtp-Source: APXvYqxDvSe4j+/gJKqdw4A6YBI9GpS4Q4oYp6I3NHhYLDVB8Dp5vZT6UTO4ev03zyjPk8xockcnd6OXkp6YzgJ8EtU= X-Received: by 2002:a2e:121d:: with SMTP id t29mr13414408lje.29.1557976629675; Wed, 15 May 2019 20:17:09 -0700 (PDT) MIME-Version: 1.0 References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> In-Reply-To: From: Alan Somers Date: Wed, 15 May 2019 21:16:57 -0600 Message-ID: Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Mel Pilgrim , FreeBSD Stable ML Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 2F50E860BF 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]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 03:17:18 -0000 On Wed, May 15, 2019 at 9:14 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > > Mel Pilgrim wrote on 2019/05/16 02:30: > > [...] > > > By batching updates, FreeBSD is making administrative decisions for > > other people's systems. Some folks don't need to worry about scheduling > > downtime and will benefit from faster update availability. Folks who > > need to worry about scheduling downtime are already going to batch > > updates and should be allowed to make those decisions for themselves. > > Batched SAs help in neither case. > > > > Example: the ntpd CVE is more than two months old, and was rapidly fixed > > in ports. I was able to switch my systems to the ports ntpd during a > > scheduled downtime window in March instead of doing it this weekend. So > > not only did I benefit from the faster update availability, I was able > > to make my own decision about my own systems and significantly reduce my > > exposure. > > > > Don't be Microsoft. Don't sit on security updates. > > +1 > > Delaying / hiding security updates cannot be good. The vulnerability > already exists. Delayed updates do favor to "bad persons", not > sysadmins. Even information about found vulnerability is more valuable > for sysadmins than silence. Some vulnerabilities can be mitigated by > configuration changes or some service replacement (eg. ntpd). But if I > don't know that there is some vulnerability I cannot do anything. > > It would also be good if base system vulnerabilities are first published > in FreeBSD vuxml. Then it can be reported to sysadmins by package > security/base-audit. +1. Reporting base + ports vulnerabilities in a common way would be great. I assume that this is already part of the pkgbase project being worked on by brd and others. > > None of these recent Sec. Advisories are listed in Vuxml yet! It's bad > example of not dog fooding there. > > I am not saying that FreeBSD SO do bad work. I really appreciate it. But > there is still something to improve. > > Kind regards > Miroslav Lachman From owner-freebsd-stable@freebsd.org Thu May 16 03:23:56 2019 Return-Path: Delivered-To: freebsd-stable@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 331C615AB550 for ; Thu, 16 May 2019 03:23:56 +0000 (UTC) (envelope-from matt.garber@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 A3CC4868BB for ; Thu, 16 May 2019 03:23:55 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6437415AB54D; Thu, 16 May 2019 03:23:55 +0000 (UTC) Delivered-To: stable@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 415B815AB54B; Thu, 16 May 2019 03:23:55 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D87C7868B8; Thu, 16 May 2019 03:23:54 +0000 (UTC) (envelope-from matt.garber@gmail.com) Received: by mail-qt1-x831.google.com with SMTP id o7so2302467qtp.4; Wed, 15 May 2019 20:23:54 -0700 (PDT) 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=eosGjJKUvnWD7Y4dtTPgAVwkCwzhMAQ9n0cCm1YYzio=; b=FOKT7hVAYUBelQEYP2zQpREIpiHIoqj2INWhhiYxRSAPPLQ37X2BouMjx50mlAl1Po uEBaO6pgyJuvsCzOuuADp0nbQMAGH5veF/Ougc81mMMh36kiJcf48jnzk9s4coviZ5vM Ww8ZkyXT7tYNPp/1iYFijOeq+yjv7G6CaAUPxlQhH0P9Iiqey5Ct1Z8xXe0qA+dD5wLJ dXYCLcFmUPpx8BazK2CSxIf2rkRJmIes/HoxwnErPck6Kulw5TjKfQC6icNKp/mTbJdq kI6jXhOPzbgHPxMv2E9g2I3uYLK/k8qVslsLAv6JfK4grlxYSf3YFwjTjx9EHjetq9zr XpHw== 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=eosGjJKUvnWD7Y4dtTPgAVwkCwzhMAQ9n0cCm1YYzio=; b=Ew894k/t0nET1BRaoVVEWK/CR31dR+T2rZJak8nCCvpl/hzy0Q8DCjaFFjeS6m0866 g+y4MECZtA8NsnGZxlMJtNC4F48HPa/4dNtn2GDdBaXhml+t/elc1dp/B6vZpuhP+r+G +j0RhX1/Z+li5g90W088plMG4IDeStqp/qmtU+z+tqRuFfU7BERFRne0o0zAmtqagA3P tXf26NKYOb+4MajMxcsGd33xi+1lexRMVQMbN581+vfd+xFLWhV9CZHlLPqgPao/DzVV GrFNmfzzR4X5x+8quzzND3jhh+BVjCKRUnVbDQ/zGbTCjFHEiZj8no1O/DwG1nMRlrBb IyXw== X-Gm-Message-State: APjAAAXPukhvtXN1v4WyUF1eghdxlpEypVBswxOc8SnvIa77LPzEVt4p YymZRJT/0R+uPCahvP5P2tVVV/ACF1FCBhc1zG4= X-Google-Smtp-Source: APXvYqy4R2UuQaN+6HyLOvZGi2viBg/oQ2062FCIZpiDx0WAk96GobmB5OGkZFcJdBN0cwVxpN0VkLHLbdzXcnKx4jQ= X-Received: by 2002:ac8:4a14:: with SMTP id x20mr39849953qtq.233.1557977034547; Wed, 15 May 2019 20:23:54 -0700 (PDT) MIME-Version: 1.0 References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> In-Reply-To: From: Matt Garber Date: Wed, 15 May 2019 23:23:39 -0400 Message-ID: Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: Bill Sorenson Cc: "Julian H. Stacey" , Mel Pilgrim , core@freebsd.org, hackers@freebsd.org, stable@freebsd.org X-Rspamd-Queue-Id: D87C7868B8 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.971,0]; TAGGED_FROM(0.00)[] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 03:23:56 -0000 On Wed, May 15, 2019 at 11:15 PM Bill Sorenson wrote: > > I=E2=80=99m not sure what you meant about Linux distros not categorizin= g fixes, > though =E2=80=94 with some notable exceptions, most of the big ones certa= inly tag > security fixes >separately, which is what allows `unattended-upgrades` on > Debian/Ubuntu based systems (and `yum-cron` on RHEL) to work so nicely > automatically as scheduled on > *only* security errata, while leaving all > other types of updates alone for admin intervention. > > My comment about Linux was not in regards to any particular distro, they > all > have interesting policies of varying effectiveness when it comes to relea= se > engineering, but specifically about the Linux kernel team (Torvalds Et al= ,) > which last I checked had a policy of specifically not handling security > issues > any different from any generic bug. Distros may do their own kernel relea= se > engineering and handling that themselves which is fine. Understood, yep, that historical stance in the kernel itself has really sucked and does no one any favors with =E2=80=98everything is just a bug.= =E2=80=99 Thankfully the kernel self-protection project has made some significant strides in that area, even if the overall security attitude of maintainers has been slower to positive change than would be ideal. =E2=80=94 Matt From owner-freebsd-stable@freebsd.org Thu May 16 05:15:23 2019 Return-Path: Delivered-To: freebsd-stable@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 2FE3115AD2B0 for ; Thu, 16 May 2019 05:15:23 +0000 (UTC) (envelope-from Public2@xymox1.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 85BA389BA9 for ; Thu, 16 May 2019 05:15:22 +0000 (UTC) (envelope-from Public2@xymox1.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4667E15AD2AF; Thu, 16 May 2019 05:15:22 +0000 (UTC) Delivered-To: stable@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 33F7F15AD2AE for ; Thu, 16 May 2019 05:15:22 +0000 (UTC) (envelope-from Public2@xymox1.com) Received: from smtp83.iad3b.emailsrvr.com (smtp83.iad3b.emailsrvr.com [146.20.161.83]) (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 CC20F89BA8 for ; Thu, 16 May 2019 05:15:21 +0000 (UTC) (envelope-from Public2@xymox1.com) Received: from smtp3.relay.iad3b.emailsrvr.com (localhost [127.0.0.1]) by smtp3.relay.iad3b.emailsrvr.com (SMTP Server) with ESMTP id E86DD4031F for ; Thu, 16 May 2019 01:15:14 -0400 (EDT) X-Auth-ID: cs@xymox1.com Received: by smtp3.relay.iad3b.emailsrvr.com (Authenticated sender: cs-AT-xymox1.com) with ESMTPSA id AE03C4012B for ; Thu, 16 May 2019 01:15:14 -0400 (EDT) X-Sender-Id: cs@xymox1.com Received: from [10.233.0.221] (ip70-162-110-235.ph.ph.cox.net [70.162.110.235]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.7.12); Thu, 16 May 2019 01:15:14 -0400 Subject: P5 bork To: stable@freebsd.org References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> From: Chris Message-ID: <43a0d86f-0169-eaae-c221-b1a9533c19a2@xymox1.com> Date: Wed, 15 May 2019 22:15:14 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:66.0) Gecko/20100101 Thunderbird/66.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: CC20F89BA8 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.995,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 05:15:23 -0000 I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at home doing DoT TLS1.3 Thats all I do on the machine. Its a very clean boring typical install. X86. FreeBSD-update fetch freebsd-update install reboot BORKED. Just loops duing boot. Backed up to kernal.old - works perfect.. If anyone cares I could go grab logs and things, but, I would assume this is already known and I will just wait for P6, hehehe.. Sorry im not deeper on the subject. From owner-freebsd-stable@freebsd.org Thu May 16 06:05:15 2019 Return-Path: Delivered-To: freebsd-stable@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 2BC8215ADEDC for ; Thu, 16 May 2019 06:05:15 +0000 (UTC) (envelope-from pete@nomadlogic.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 630098B14F for ; Thu, 16 May 2019 06:05:14 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: by mailman.ysv.freebsd.org (Postfix) id 23A0415ADEDB; Thu, 16 May 2019 06:05:14 +0000 (UTC) Delivered-To: stable@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 120F615ADEDA for ; Thu, 16 May 2019 06:05:14 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 792328B14E for ; Thu, 16 May 2019 06:05:13 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from duke.gem.co (23.243.162.239 [23.243.162.239]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 5f68da33 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 16 May 2019 05:58:26 +0000 (UTC) Subject: Re: P5 bork To: Chris , stable@freebsd.org References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> <43a0d86f-0169-eaae-c221-b1a9533c19a2@xymox1.com> From: Pete Wright Message-ID: <662f7211-68bb-7577-359b-9154f6da295c@nomadlogic.org> Date: Wed, 15 May 2019 22:58:26 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <43a0d86f-0169-eaae-c221-b1a9533c19a2@xymox1.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 792328B14E 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-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 06:05:15 -0000 On 5/15/19 10:15 PM, Chris wrote: > I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at > home doing DoT TLS1.3 > > Thats all I do on the machine. Its a very clean boring typical > install. X86. > > FreeBSD-update fetch > freebsd-update install > reboot > > BORKED. Just loops duing boot. > > Backed up to kernal.old - works perfect.. > > If anyone cares I could go grab logs and things, but, I would assume > this is already known and I will just wait for P6, hehehe.. > > Sorry im not deeper on the subject. should be fixed now: https://www.freebsd.org/security/advisories/FreeBSD-SA-19:07.mds.asc "v2.0 2019-05-15 Rerelease 12.0-RELEASE patch as -p5 due to i386 panic bug." -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-stable@freebsd.org Thu May 16 06:56:26 2019 Return-Path: Delivered-To: freebsd-stable@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 6651D15AEBE8 for ; Thu, 16 May 2019 06:56:26 +0000 (UTC) (envelope-from C@Xymox1.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 ADEC18C57C for ; Thu, 16 May 2019 06:56:25 +0000 (UTC) (envelope-from C@Xymox1.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6F50015AEBE7; Thu, 16 May 2019 06:56:25 +0000 (UTC) Delivered-To: stable@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 5DE7015AEBE6 for ; Thu, 16 May 2019 06:56:25 +0000 (UTC) (envelope-from C@Xymox1.com) Received: from smtp83.iad3a.emailsrvr.com (smtp83.iad3a.emailsrvr.com [173.203.187.83]) (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 DB3B68C57A for ; Thu, 16 May 2019 06:56:24 +0000 (UTC) (envelope-from C@Xymox1.com) Received: from smtp3.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp3.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 54733239E5; Thu, 16 May 2019 02:56:18 -0400 (EDT) X-Auth-ID: cs@xymox1.com Received: by smtp3.relay.iad3a.emailsrvr.com (Authenticated sender: cs-AT-xymox1.com) with ESMTPSA id DCA1C22F27; Thu, 16 May 2019 02:56:17 -0400 (EDT) X-Sender-Id: cs@xymox1.com Received: from [10.233.0.199] (ip70-162-110-235.ph.ph.cox.net [70.162.110.235]) (using TLSv1.2 with cipher AES128-SHA) by 0.0.0.0:465 (trex/5.7.12); Thu, 16 May 2019 02:56:18 -0400 Subject: Re: P5 bork To: Pete Wright , Chris , stable@freebsd.org References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> <43a0d86f-0169-eaae-c221-b1a9533c19a2@xymox1.com> <662f7211-68bb-7577-359b-9154f6da295c@nomadlogic.org> From: Chris Message-ID: <549fc05d-b356-5ec3-bc71-0aa073d95d13@Xymox1.com> Date: Wed, 15 May 2019 23:56:17 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <662f7211-68bb-7577-359b-9154f6da295c@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: DB3B68C57A 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_SHORT(-0.98)[-0.979,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 06:56:26 -0000 Thank you Pete :) On 5/15/2019 10:58 PM, Pete Wright wrote: > > > On 5/15/19 10:15 PM, Chris wrote: >> I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at >> home doing DoT TLS1.3 >> >> Thats all I do on the machine. Its a very clean boring typical >> install. X86. >> >> FreeBSD-update fetch >> freebsd-update install >> reboot >> >> BORKED. Just loops duing boot. >> >> Backed up to kernal.old - works perfect.. >> >> If anyone cares I could go grab logs and things, but, I would assume >> this is already known and I will just wait for P6, hehehe.. >> >> Sorry im not deeper on the subject. > > should be fixed now: > https://www.freebsd.org/security/advisories/FreeBSD-SA-19:07.mds.asc > > "v2.0 2019-05-15 Rerelease 12.0-RELEASE patch as -p5 due to i386 panic > bug." > > -pete > From owner-freebsd-stable@freebsd.org Thu May 16 07:07:11 2019 Return-Path: Delivered-To: freebsd-stable@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 4A88E15AEF05 for ; Thu, 16 May 2019 07:07:11 +0000 (UTC) (envelope-from C@Xymox1.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 8ECFC8C9E2 for ; Thu, 16 May 2019 07:07:10 +0000 (UTC) (envelope-from C@Xymox1.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4C8E215AEF04; Thu, 16 May 2019 07:07:10 +0000 (UTC) Delivered-To: stable@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 3B16715AEF03 for ; Thu, 16 May 2019 07:07:10 +0000 (UTC) (envelope-from C@Xymox1.com) Received: from smtp91.ord1c.emailsrvr.com (smtp91.ord1c.emailsrvr.com [108.166.43.91]) (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 D50718C9E1 for ; Thu, 16 May 2019 07:07:09 +0000 (UTC) (envelope-from C@Xymox1.com) Received: from smtp4.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id D428EA0243; Thu, 16 May 2019 03:07:02 -0400 (EDT) X-Auth-ID: cs@xymox1.com Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: cs-AT-xymox1.com) with ESMTPSA id 633DFA0206; Thu, 16 May 2019 03:07:02 -0400 (EDT) X-Sender-Id: cs@xymox1.com Received: from [10.233.0.199] (ip70-162-110-235.ph.ph.cox.net [70.162.110.235]) (using TLSv1.2 with cipher AES128-SHA) by 0.0.0.0:465 (trex/5.7.12); Thu, 16 May 2019 03:07:02 -0400 Subject: Re: P5 bork From: Chris To: Chris , stable@freebsd.org References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> <43a0d86f-0169-eaae-c221-b1a9533c19a2@xymox1.com> <662f7211-68bb-7577-359b-9154f6da295c@nomadlogic.org> <549fc05d-b356-5ec3-bc71-0aa073d95d13@Xymox1.com> Message-ID: <6b0e362b-4ad0-cdc9-1332-7c917b8ae495@Xymox1.com> Date: Thu, 16 May 2019 00:07:01 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <549fc05d-b356-5ec3-bc71-0aa073d95d13@Xymox1.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: D50718C9E1 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.981,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 07:07:11 -0000 hahaha.. So I gotta patch the patch with a patch if its patched already.  :) On 5/15/2019 11:56 PM, Chris wrote: > Thank you Pete :) > > On 5/15/2019 10:58 PM, Pete Wright wrote: >> >> >> On 5/15/19 10:15 PM, Chris wrote: >>> I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at >>> home doing DoT TLS1.3 >>> >>> Thats all I do on the machine. Its a very clean boring typical >>> install. X86. >>> >>> FreeBSD-update fetch >>> freebsd-update install >>> reboot >>> >>> BORKED. Just loops duing boot. >>> >>> Backed up to kernal.old - works perfect.. >>> >>> If anyone cares I could go grab logs and things, but, I would assume >>> this is already known and I will just wait for P6, hehehe.. >>> >>> Sorry im not deeper on the subject. >> >> should be fixed now: >> https://www.freebsd.org/security/advisories/FreeBSD-SA-19:07.mds.asc >> >> "v2.0 2019-05-15 Rerelease 12.0-RELEASE patch as -p5 due to i386 >> panic bug." >> >> -pete >> > From owner-freebsd-stable@freebsd.org Thu May 16 09:41:26 2019 Return-Path: Delivered-To: freebsd-stable@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 7793E158F075 for ; Thu, 16 May 2019 09:41:26 +0000 (UTC) (envelope-from SRS0=HRFA=TQ=quip.cz=000.fbsd@elsa.codelab.cz) 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 BD4846D6A2 for ; Thu, 16 May 2019 09:41:25 +0000 (UTC) (envelope-from SRS0=HRFA=TQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: by mailman.ysv.freebsd.org (Postfix) id 7DCA2158F074; Thu, 16 May 2019 09:41:25 +0000 (UTC) Delivered-To: stable@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 6C1FA158F073 for ; Thu, 16 May 2019 09:41:25 +0000 (UTC) (envelope-from SRS0=HRFA=TQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 001876D69C; Thu, 16 May 2019 09:41:24 +0000 (UTC) (envelope-from SRS0=HRFA=TQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 0BDFA28417; Thu, 16 May 2019 11:41:22 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8909528411; Thu, 16 May 2019 11:41:20 +0200 (CEST) Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. To: Alan Somers Cc: FreeBSD Stable ML , Mel Pilgrim References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <8e472993-2d01-003f-acbb-77f9edf512dc@quip.cz> Date: Thu, 16 May 2019 11:41:23 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 001876D69C 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-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 09:41:26 -0000 Alan Somers wrote on 2019/05/16 05:16: > On Wed, May 15, 2019 at 9:14 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: >> It would also be good if base system vulnerabilities are first published >> in FreeBSD vuxml. Then it can be reported to sysadmins by package >> security/base-audit. > > +1. Reporting base + ports vulnerabilities in a common way would be > great. I assume that this is already part of the pkgbase project > being worked on by brd and others. The functionality is already there. The only part missing is Security Office should fill the data in to vuxml at the time of publishing new SA. Thanks to Mark Felder https://blog.feld.me/posts/2016/08/monitoring-freebsd-base-system-vulnerabilities-with-pkg-audit/ Then I provided periodic script https://www.freshports.org/security/base-audit/ Miroslav Lachman From owner-freebsd-stable@freebsd.org Thu May 16 12:19:53 2019 Return-Path: Delivered-To: freebsd-stable@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 776351594379 for ; Thu, 16 May 2019 12:19:53 +0000 (UTC) (envelope-from robbelics@gmail.com) Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C2EC72FCE for ; Thu, 16 May 2019 12:19:52 +0000 (UTC) (envelope-from robbelics@gmail.com) Received: by mail-lj1-x22c.google.com with SMTP id 188so2878238ljf.9 for ; Thu, 16 May 2019 05:19:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=6lP1Y0Z2EvXH5Z5tUKk28ZBee2LVgSvsfuw3PaPdywg=; b=t9b2NW0kE1teXwmB+jRWqWwVKSXgnvxp4lj+FfcYmznbx+pY9110RKiP6CWw47tV6n 0s8fHlhz9FMaSwCVgijYCtGsoOC8N73XRhx2paxhzJp4z3PzLlOde4sO750nUt9sIJT2 /zbND57eTm4ttfm3NT6dhDypQV1xvQefYmw7rxB7pTzEIxHOQkeSZN7zstW7HcjGVCZl ErnGQ9ctNVkqlq7KQX2p0vYFsREUqBFnnsjRm4+x5rFu9XzmtwbtikUNbGTixSZ5tE/9 GrQArVk8Pisb12UYyuYuH/x1U1Kf18OTok7WF5FU0oHntrLw8p0kFmZHap5PMv4FiK2O x6pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6lP1Y0Z2EvXH5Z5tUKk28ZBee2LVgSvsfuw3PaPdywg=; b=Lnx+VucuHj+LlcS+nCP6MhCclRRJXqXLLOhN0nx8ygwpMH/NpONGQbeWVZy27PjzXm bxuPb1cvi+b3vxJ4PKGVkTSc5JlwlaktU7P40AFRMRvcyT9GfuPivYaWV309t7lgFh7W 7JtkmMjCvjlcSLF0b3kwoluFz18GaELgefTgnrHo4qfu4E4e157uQqVylX+0v541mx8R 30gzMAu1RXYbI657LeE/uJ6sI0TzZojNoznR5Xlygwqwm9yQdWbqIZw+TaCjQ7mHJVs2 baTcnR0eK4oqKbKZAZVIjRh1S/yDl2SZ+L6CpYzTbJLAMWH4qTcRJkimSPNp3Z+/8m02 2/9g== X-Gm-Message-State: APjAAAX5vljOVp2A1jgv52p5iTA1+A4LAx7ZchW1HC7QFypJ4WmlCLsE UrWdLYAtUsDgCTIiHFf/Gi5vcnOByHTsmTI9JqydBbU= X-Google-Smtp-Source: APXvYqzNpzOqb/iewwxNmko2DuC+ZBAIM8V4/eU8/jdx8bfvW1DokI7BvYUpSIOTFOzfxc2XYxpRkmgzkXjay8KtnkU= X-Received: by 2002:a2e:8988:: with SMTP id c8mr18201787lji.99.1558009190100; Thu, 16 May 2019 05:19:50 -0700 (PDT) MIME-Version: 1.0 From: Rob Belics Date: Thu, 16 May 2019 07:19:39 -0500 Message-ID: Subject: Re: 12.0-RELEASE-p4 kernel panic on i386 boot To: freebsd-stable@freebsd.org X-Rspamd-Queue-Id: 5C2EC72FCE X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=t9b2NW0k; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of robbelics@gmail.com designates 2a00:1450:4864:20::22c as permitted sender) smtp.mailfrom=robbelics@gmail.com X-Spamd-Result: default: False [-5.77 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.94)[-0.937,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:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-2.82)[ip: (-9.59), ipnet: 2a00:1450::/32(-2.20), asn: 15169(-2.27), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[c.2.2.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]; 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-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 12:19:53 -0000 Possibly same issue on amd64 server in my VPS but my laptop updated just fine. vm_fault_hold: fault on nofault entry, addr: 0 From owner-freebsd-stable@freebsd.org Thu May 16 12:41:59 2019 Return-Path: Delivered-To: freebsd-stable@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 03078159512F for ; Thu, 16 May 2019 12:41:59 +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 8EC4C73CC6 for ; Thu, 16 May 2019 12:41:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4C7F7159512D; Thu, 16 May 2019 12:41:58 +0000 (UTC) Delivered-To: stable@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 3A443159512A for ; Thu, 16 May 2019 12:41:58 +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 C8A1E73CC1 for ; Thu, 16 May 2019 12:41:57 +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 255EEED65 for ; Thu, 16 May 2019 12:41:57 +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 x4GCfvhq010890 for ; Thu, 16 May 2019 12:41:57 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4GCfv9g010884 for stable@FreeBSD.org; Thu, 16 May 2019 12:41:57 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: stable@FreeBSD.org Subject: [Bug 193366] [panic] panic vnlru Date: Thu, 16 May 2019 12:41:57 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: arrowd@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 12:41:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193366 Gleb Popov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arrowd@FreeBSD.org --- Comment #1 from Gleb Popov --- This FreeBSD version is not supported anymore, and the bug report doesn't s= eem to actually contain any useful information. Should we close it? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Thu May 16 13:04:44 2019 Return-Path: Delivered-To: freebsd-stable@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 D2AFB1595E18 for ; Thu, 16 May 2019 13:04:44 +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 6C30B75450 for ; Thu, 16 May 2019 13:04:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 30DEB1595E13; Thu, 16 May 2019 13:04:44 +0000 (UTC) Delivered-To: stable@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 1ECB41595E10 for ; Thu, 16 May 2019 13:04: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 7898975447 for ; Thu, 16 May 2019 13:04:43 +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 667FEF099 for ; Thu, 16 May 2019 13:04:42 +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 x4GD4gDT071897 for ; Thu, 16 May 2019 13:04:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4GD4gnu071896 for stable@FreeBSD.org; Thu, 16 May 2019 13:04:42 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: stable@FreeBSD.org Subject: [Bug 193366] [panic] panic vnlru Date: Thu, 16 May 2019 13:04:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution cc 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-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 13:04:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193366 Konstantin Belousov changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Overcome By Events CC| |kib@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Thu May 16 14:02:19 2019 Return-Path: Delivered-To: freebsd-stable@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 DD72F15978FB for ; Thu, 16 May 2019 14:02:19 +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 6FC2677C64 for ; Thu, 16 May 2019 14:02:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 305D315978F7; Thu, 16 May 2019 14:02:19 +0000 (UTC) Delivered-To: stable@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 1F09A15978F6 for ; Thu, 16 May 2019 14:02:19 +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 AE88177C5E for ; Thu, 16 May 2019 14:02:18 +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 02F7CF93A for ; Thu, 16 May 2019 14:02:18 +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 x4GE2H4H091636 for ; Thu, 16 May 2019 14:02:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4GE2HaU091635 for stable@FreeBSD.org; Thu, 16 May 2019 14:02:17 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: stable@FreeBSD.org Subject: [Bug 193361] [panic] panic pagedaemon Date: Thu, 16 May 2019 14:02:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: arrowd@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 14:02:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193361 Gleb Popov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arrowd@FreeBSD.org Resolution|--- |Overcome By Events Status|New |Closed --- Comment #3 from Gleb Popov --- This FreeBSD version is not supported anymore, and the bug report doesn't s= eem to actually contain any useful information. Closing it. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Thu May 16 18:16:29 2019 Return-Path: Delivered-To: freebsd-stable@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 8E72915A3280 for ; Thu, 16 May 2019 18:16:29 +0000 (UTC) (envelope-from spork@bway.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 B7FE16D6BE for ; Thu, 16 May 2019 18:16:28 +0000 (UTC) (envelope-from spork@bway.net) Received: by mailman.ysv.freebsd.org (Postfix) id 783A315A327F; Thu, 16 May 2019 18:16:28 +0000 (UTC) Delivered-To: stable@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 3D7E215A327E for ; Thu, 16 May 2019 18:16:28 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp1.bway.net (smtp1.v6.bway.net [IPv6:2607:d300:1::27]) (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 D23936D6B5; Thu, 16 May 2019 18:16:27 +0000 (UTC) (envelope-from spork@bway.net) Received: from frankentosh.sporklab.com (pool-173-70-93-30.nwrknj.fios.verizon.net [173.70.93.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp1.bway.net (Postfix) with ESMTPSA id D94FB958BA; Thu, 16 May 2019 14:16:20 -0400 (EDT) From: Charles Sprickman Message-Id: <137C0B51-9644-400C-89A1-81CEA3390C9E@bway.net> Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Date: Thu, 16 May 2019 14:15:41 -0400 In-Reply-To: <8e472993-2d01-003f-acbb-77f9edf512dc@quip.cz> Cc: Alan Somers , FreeBSD Stable ML , Mel Pilgrim To: Miroslav Lachman <000.fbsd@quip.cz> References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> <8e472993-2d01-003f-acbb-77f9edf512dc@quip.cz> X-Mailer: Apple Mail (2.3273) X-Rspamd-Queue-Id: D23936D6B5 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.988,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-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 18:16:29 -0000 > On May 16, 2019, at 5:41 AM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >=20 > Alan Somers wrote on 2019/05/16 05:16: >> On Wed, May 15, 2019 at 9:14 PM Miroslav Lachman <000.fbsd@quip.cz> = wrote: >=20 >>> It would also be good if base system vulnerabilities are first = published >>> in FreeBSD vuxml. Then it can be reported to sysadmins by package >>> security/base-audit. >> +1. Reporting base + ports vulnerabilities in a common way would be >> great. I assume that this is already part of the pkgbase project >> being worked on by brd and others. >=20 > The functionality is already there. The only part missing is Security = Office should fill the data in to vuxml at the time of publishing new = SA. >=20 > Thanks to Mark Felder = https://blog.feld.me/posts/2016/08/monitoring-freebsd-base-system-vulnerab= ilities-with-pkg-audit/ > Then I provided periodic script = https://www.freshports.org/security/base-audit/ = There=E2=80=99s also this as a =E2=80=9Cright now=E2=80=9D solution if = you use nagios: = https://github.com/frlen/nagios-plugins/blob/master/check_freebsd_version = You do have to adjust it to check only once or twice a day and to = provide for a large number of retries, as the remote portion of the = check to find the current version often times out. Thanks, Charles > Miroslav Lachman > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Thu May 16 19:16:15 2019 Return-Path: Delivered-To: freebsd-stable@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 8BA4315A5192 for ; Thu, 16 May 2019 19:16:15 +0000 (UTC) (envelope-from robbelics@gmail.com) Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B661711F4 for ; Thu, 16 May 2019 19:16:14 +0000 (UTC) (envelope-from robbelics@gmail.com) Received: by mail-lj1-x236.google.com with SMTP id z5so4107254lji.10 for ; Thu, 16 May 2019 12:16:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=7CUmFiC5LlBFLUWJaQK10+yIz7hDB7OsGD95Pcc6sIs=; b=B2r2MsD6RkSKWhGlspfDmUE+aGsVvttUFqrJDyzFlrItxJK36K9PGKt7c0g1v3c6sa yLuTXYRR9RLe6o/x7+wEOMz3dtsxyg+KiRLt+BAjx778krrQbM0D5n+SnIj1QjgIt/J9 Lqiq91IT/+Id+CS47nlAS4jhT2bE/rPZz142SBDt63VK+pzLAZ9vmfQrIy8WSQ+Km4jH KoKwJzZdVbksl96VLefooUrQRXAYO7oU6HjhwytjyTmZSGd54Mw02JmX01HARfmswSaP YlDKDILFGO9StkGibKsK/n1xIAC+jNGrK4UEm+RoAZxlY4YbO3aYKqMT9+hoBmO4FrJA BBRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=7CUmFiC5LlBFLUWJaQK10+yIz7hDB7OsGD95Pcc6sIs=; b=kzttYD9cr2ZdpQ/r3FiYipm0q+UDfNFyTo8nnmCcJ9lE9QzeNRU63HoAqp2SLo4foW gQUD8USPOHlgMEPXbV0LOmjhkF0WdY17dpnWnwYr1/DiyNDqc/dktAVjoPKKxannVkWk t6UU+YSrsbv80J/6bXDg+KzhrmZsqEU6P1PTtCXDMzKBunmhIm21s6D7RBEQ0cUDW1a+ 9QqcfJlHQjUdur5t6TD6O40oyYdz3wYbOCUsGPjWe6lPUj6cimQlpaBz+ovfWtlmHief KrVCz7GsfGnER4TV2bLxmCOsL3Ysn2rSS6AYp3n1eIMBjw97AkSYoyKVFssf/iJzC9v/ +k3Q== X-Gm-Message-State: APjAAAW44wE/gomdigVcV1QiVJ4Fbe2NbzRJcz/BMyHGkkYx43FNX0QM Pp5XYmKt844YVGz9AKNq/zW9Oa04xn7WQewVTs6z X-Google-Smtp-Source: APXvYqyJaBV/fRhtRLhH3dJtGjTNP3ERd0WyVKmQiwQpgH8LVhytgTwBrhr3WPSSnGlaj7ITPf8w+r419J6n7VyaFdk= X-Received: by 2002:a2e:9cd5:: with SMTP id g21mr19188987ljj.39.1558034172584; Thu, 16 May 2019 12:16:12 -0700 (PDT) MIME-Version: 1.0 From: Rob Belics Date: Thu, 16 May 2019 14:16:01 -0500 Message-ID: Subject: Re: 12.0-RELEASE-p4 kernel panic on i386 boot To: freebsd-stable@freebsd.org X-Rspamd-Queue-Id: 8B661711F4 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=B2r2MsD6; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of robbelics@gmail.com designates 2a00:1450:4864:20::236 as permitted sender) smtp.mailfrom=robbelics@gmail.com X-Spamd-Result: default: False [-5.74 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(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]; NEURAL_HAM_SHORT(-0.91)[-0.905,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:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-2.83)[ip: (-9.61), ipnet: 2a00:1450::/32(-2.20), asn: 15169(-2.27), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[6.3.2.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]; 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-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2019 19:16:15 -0000 This morning, RELEASE-p5 came about. I did a freebsd-update without issue. However, as I said, I am running amd64 and not i386 on my server. So there must be something more involved here. From owner-freebsd-stable@freebsd.org Fri May 17 07:22:16 2019 Return-Path: Delivered-To: freebsd-stable@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 35E5E15B1DF0 for ; Fri, 17 May 2019 07:22:16 +0000 (UTC) (envelope-from dmitryluhtionov@gmail.com) Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 436CE8E241; Fri, 17 May 2019 07:22:15 +0000 (UTC) (envelope-from dmitryluhtionov@gmail.com) Received: by mail-ot1-x329.google.com with SMTP id r10so5875680otd.4; Fri, 17 May 2019 00:22:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=dVfy4PuXrJFKhEio3JM/bU4qzXKc7vPaaLo/eU/sZ0c=; b=BEEnPHFnN6NQ1w8ltiBHpBHr9UhfovsNGiJt8E8OKpKviBB5c+dFGr4usgn2C375kF fGngUJK/wmLUaTYQv8qu1oRVYKVxTkb+EbgRH19Xk1kzRdsMNCCqg/PXGjGuiWbFiJpB dbKeI3a0LX6A1PvJBr4Bk8j/E5DqWfROuOqp8QlUDFrzxstTJUNYmx8BIofVDnP0OPz4 vCc9KJPcythCvJpfCWrvZcZK0DeiCY3NfYHgbADSS9AuyzuLNnf+kYasjOIDtOogxUi5 5PloQB3aHBCKCV/7fNw48MYQhZIh08EEIYGHypGQf1sFrg1/Tz+JaH+yic07Te9ecEB3 nqzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dVfy4PuXrJFKhEio3JM/bU4qzXKc7vPaaLo/eU/sZ0c=; b=AiinTfgclMn0Q9CTUyIOoZv8DzsziigK7teNp4p/I2XGfuUeSTP3+0e5AnS8n13bF/ 1sutZfz2ZU0f11bubj0VVxNzVGaR0dF1SeAkuXwwBLH3a2DmoQjNb0YYCEE+fHIOUDj+ dZknQudXJmiUANbHuixRKbPwfks7Zpaxk7mrNlWkkpmuVjL4B6BdQrXb5/7T2X/kZbBo lI+gePsPjLDmzJMeZFU00HN7s7fgJwIMzxJ+zUz/awFyfs+04HaXbp/1D6AMFh7CrU9d 6swuLXCphgieT0c6qap2P4CCjvzgkz+r0n+61nSiF4pY+b9JXZngh9OFOzAJktU+Y3KN ZJ7g== X-Gm-Message-State: APjAAAWLlLqc5hIYEzmVwOhglvQp7upNZeEJfelt3Vvg/e8eqnev+BKK 9h6awlMYT5PmuUc+NDZEFTC1lBBE1omT9jtjjOdlKjlA X-Google-Smtp-Source: APXvYqyWAyvNGhZXpobAART6SFqPBhpuVXoPWZlxIdwIOj5E5iBjnt2WVNBD07nSAHuyO6M0d6WpojkShN7OHgO+JUU= X-Received: by 2002:a9d:5f8f:: with SMTP id g15mr3076146oti.196.1558077734150; Fri, 17 May 2019 00:22:14 -0700 (PDT) MIME-Version: 1.0 From: Dmitry Luhtionov Date: Fri, 17 May 2019 10:22:03 +0300 Message-ID: Subject: 12.0-STABLE on PINE64-LTS To: freebsd-stable@freebsd.org, lwhsu@freebsd.org X-Rspamd-Queue-Id: 436CE8E241 X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=BEEnPHFn; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of dmitryluhtionov@gmail.com designates 2607:f8b0:4864:20::329 as permitted sender) smtp.mailfrom=dmitryluhtionov@gmail.com X-Spamd-Result: default: False [-7.01 / 15.00]; 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)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; 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]; RCVD_IN_DNSWL_NONE(0.00)[9.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]; NEURAL_HAM_SHORT(-0.97)[-0.975,0]; 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]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-3.02)[ip: (-9.52), ipnet: 2607:f8b0::/32(-3.26), asn: 15169(-2.27), country: US(-0.06)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 May 2019 07:22:16 -0000 Hi. I download FreeBSD-12.0.STABLE from official website https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/12.0/FreeBSD-12.0-STABLE-arm64-aarch64-PINE64-LTS-20190510-r347397.img.xz When booting them, I see these lines in dmesg: KLD file umodem.ko is missing dependencies mmcsd0: 32GB at mmc0 50.0MHz/4bit/32768-block mmc0: Failed to set VCCQ for card at relative address 1 warning: KLD '/boot/kernel/fdt_slicer.ko' is newer than the linker.hints file Can I fix this ? From owner-freebsd-stable@freebsd.org Sat May 18 04:29:08 2019 Return-Path: Delivered-To: freebsd-stable@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 637F515A781F for ; Sat, 18 May 2019 04:29:08 +0000 (UTC) (envelope-from crahman@gmail.com) Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 21E7E9733B for ; Sat, 18 May 2019 04:29:07 +0000 (UTC) (envelope-from crahman@gmail.com) Received: by mail-oi1-x22b.google.com with SMTP id z65so6582376oia.11 for ; Fri, 17 May 2019 21:29:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=RVhCmIUqZQ3nMVASI0d6RDAnAaF0WbjUUuBXT/+7I4k=; b=EX5N+De3XCCJKVBa5khZMiQDDwlPXbr7NFXXjYVSjwGuQIeRZS+oDkv8tKrANmewTU jWi4g5H8rwNyrJ2pF49HPjJsiYxYkD8GslNmAP3HW9ReVr1uoGWidqIk7ToTqRsR+Oe2 Y60Hjd/MQblyveDWR7IIHhK7s6Z//zxh3NCIC4Sa9ZIi0gqN22fTjuQzKotDpMqDa+O+ lTMA88P8zhXvWlvbsL0Ui5dAHh9xU/tm4HeenEQTC4DtXzPg8jBhXjxDqFycYA/qhjfY DJpFmhVXdwwUynf9cBRI8D6yXyjDFmoc4/bukZXR4ygqeh2SXAzb2GymT48ypSYlZCz1 doUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=RVhCmIUqZQ3nMVASI0d6RDAnAaF0WbjUUuBXT/+7I4k=; b=LtGhexPL6MP+Q0o01FWR7zvNjwM5oSG/2CJoFicd0d7AU4IhyTcX+ee99ml23Ocq8r nxQv0KKeNtPrrHlZHMOQBxeCXw6XQ/lSpwA2sCSAkuMygZ3wieUl9sXhFs7GVsv8O6HI 59riwyzUYuMF42YI6k4QFtub+un+ODlIoYmUqa31aow5lHjSUigR3VDQnkI5ORRRCcHq zNiiCNBbd/DpskhzgwwUBwvQHG0zXUDMKXf1dfUfCI7yFe5t/Z0yZ+o3xLdlq1/LhOV2 a/AXDRiRB4y7oRtYWUZm+AOWx+YxT1+uWtXPWaCJKtp9qmLW2i8mTEO+Lwim3gsUY7ds tZiA== X-Gm-Message-State: APjAAAUY13WIccaBYzPp1TMoHXAi71JUzHuOo3wXsiBy0Rk8ZHWP9jkW wRsmFfSbIoikcbTI0uOA6+JR1s+ZgCd8/4e/ph8/p05X X-Google-Smtp-Source: APXvYqyKrWeAjV4l1kjCs6ifLZtqxuSUuJgEkwQViu+57D8M3nFOBa+ysjVb4sTKmiS172K6xr9qARo8NkDbINjMDxQ= X-Received: by 2002:aca:3905:: with SMTP id g5mr16934266oia.49.1558153745974; Fri, 17 May 2019 21:29:05 -0700 (PDT) MIME-Version: 1.0 From: Cyrus Rahman Date: Fri, 17 May 2019 22:28:29 -0600 Message-ID: Subject: Problem with /boot/loader in 11.3-PRERELEASE r347946 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 21E7E9733B X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=EX5N+De3; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of crahman@gmail.com designates 2607:f8b0:4864:20::22b as permitted sender) smtp.mailfrom=crahman@gmail.com X-Spamd-Result: default: False [-6.87 / 15.00]; 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)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[b.2.2.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.97)[ip: (-9.22), ipnet: 2607:f8b0::/32(-3.27), asn: 15169(-2.27), country: US(-0.06)]; NEURAL_HAM_SHORT(-0.90)[-0.898,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 May 2019 04:29:08 -0000 I've just updated to r347946 from r344695. Upon booting the loader, I get: panic: free: guard2 fail @ 0xcd8de040 + 2061 from unknown:0 I'm using gptzfsboot, and the boot blocks are current. The previous loader works fine - boot loader_lua and loader_4th are ok. But the current loaders, both ula and 4th, fail with the same panic (the message reproduced is from loader_4th). Cyrus Rahman From owner-freebsd-stable@freebsd.org Sat May 18 11:44:56 2019 Return-Path: Delivered-To: freebsd-stable@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 D0E6F15AFDC7; Sat, 18 May 2019 11:44:55 +0000 (UTC) (envelope-from tech-lists@zyxst.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 B6F6B76156; Sat, 18 May 2019 11:44:53 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7216D25C36; Sat, 18 May 2019 07:44:47 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 18 May 2019 07:44:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:cc:subject:message-id:mime-version:content-type; s= fm2; bh=Ezf63hdvo7HL/qkCi9BuH5rpPMcvC/xeRjCNt4HgLRs=; b=r8nVstk4 orKJfAhigh4QnyCVSPmNzInyfUp208uhWEfwVbADN2Id37LBgx2voCWd6VMKQqm6 Dr8miN2n9NiBjyxWODTFL5Jaa3/EuB0ycOcVKf9FfKByuewn7x/fSf4HzgGalSmv vxBxRiYA3TFbeEhUGxur4rgdew6ONOnlN+P/eoWXDalRwvTR5EkuJmFfqRniRpey Q7PEYRFtNAOrIvqJYu1plp2E0mfdxJkJoulDkFyE7b5xN/3xnAaXDJtuQ7OKOyHR k3H9itqa1ZvQWPZsioyWYTn7bWwsspDVRiZAEbkkJHBAfkKFedtKRnCeMsCvi/KU sXDotWjGNTnhBw== 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=fm2; bh=Ezf63hdvo7HL/qkCi9BuH5rpPMcvC /xeRjCNt4HgLRs=; b=GShrHOzyWAl0h1j2TVkXzsX6q3XOasYVZumoI/8fr1NxR UZigQfq/dXb4oORBl0Yavy4c4Uv0tjdEOhZjXSjImyZ0X2NPjYeEdWoM1jW188Bz WUy6UMSNyV/vgAkQNirIB1pwKsbX0mYFSFI7XBVGSPutcIyxJ+U+eP/cSNu3vVcR I1xR/PLc8AwYJSJbJ7IJMmgPkqSE938NymSBPimMg0hKm3Fk8krXjO1ENMWWaAYq HP8LBHHI1Lail4kDjvZHnauk9f+sfDizeVf2HMuQ8K/0isrP9p41IYHDuGAOkUgk ZN5S6FC553V20IaptSfBWgwoHmkgH+xd5GiCYB23g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddruddtgedgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtuggfsehgtderre dtredvnecuhfhrohhmpehtvggthhdqlhhishhtshcuoehtvggthhdqlhhishhtshesiiih gihsthdrnhgvtheqnecukfhppeekvddrjedtrdeluddruddtudenucfrrghrrghmpehmrg hilhhfrhhomhepthgvtghhqdhlihhsthhsseiihiigshhtrdhnvghtnecuvehluhhsthgv rhfuihiivgeptd X-ME-Proxy: Received: from rpi3.zyxst.net (rpi3.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 83AFA1037C; Sat, 18 May 2019 07:44:46 -0400 (EDT) Date: Sat, 18 May 2019 12:44:44 +0100 From: tech-lists To: freebsd-stable@freebsd.org Cc: freebsd-questions@freebsd.org Subject: nextcloud and collabora on freebsd-12-stable host Message-ID: <20190518114443.GG15462@rpi3.zyxst.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oXNgvKVxGWJ0RPMJ" Content-Disposition: inline User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: B6F6B76156 X-Spamd-Bar: --------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm2 header.b=r8nVstk4; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=GShrHOzy; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 66.111.4.25 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-9.08 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm2,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[zyxst.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; RCPT_COUNT_TWO(0.00)[2]; 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,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.995,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; IP_SCORE(-3.38)[ip: (-9.12), ipnet: 66.111.4.0/24(-4.51), asn: 11403(-3.21), country: US(-0.06)]; RCVD_IN_DNSWL_LOW(-0.10)[25.4.111.66.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 May 2019 11:44:56 -0000 --oXNgvKVxGWJ0RPMJ Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hi, Does anyone run nextcloud with collabora on freebsd? If so, please tell how you did it? Reading up on it, instructions are all in linux and use of docker which I'm not keen on as my nextcloud is already a bhyve instance. thanks, --=20 J. --oXNgvKVxGWJ0RPMJ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAlzf8CMACgkQs8o7QhFz NAVyww//YBPxhO/PJyVwr+My7lYSaOFVTOvE6qp/qglA5w+mYKMueTT8xq9Up/ls NQnabki41BZHkBqc6OAl8C0Uqxk6yxfU4aL6agEDS4RSo8Ms4EDCKhUHKjmQjK1F 58g/Jy/NWVAcrHB7Sb/xtk+9NlP0603zmMOpZAVD5Ilz1Wgqd46TIZKQ5ek5BVoR bnnowjlFWUeXKDkg+kg4UpXFarNCFEOAqRhxxTKuW4v7AyoTPfRVRmFZ+Duecd2k plyT8/rfQb3ZfDoX038DmEa4TstEM6IdGnp1CdVuv3jlfKEVsWeY2eX8mJVRnL/Q 0PiCn86qBGZUjLY85QatW99KEwIPd3oaE+6dJBnBidTiQrGDPv5zXiziYTsCvyfW Ks2Yqw2b6n58cNMAMtIxKA6AMeWUkuTJ03VL31Ju0dY6ZiAIdjE+6Q78NImraoRe i8LIjo0C5Y/3GEEd1VZ3BDW1oVzh/uY76WBFklDA13KdQ1atA2gnVeXA3ny7TIEj oj+n7BeO0DSEJ5SHl2/btOGCuco6Ky6Mrms882itSYOCaclvxzaOCzNCfhXBkKIr BtmBWhLqKOwKEp1LlKR6P0yQpKC6c4WDG/Lfq8Wp7m7BvGxA4eOryeMREUQBULCv fVqG7uPE+BCrnnxcG5vccAy2oFT5cSj2vKGnhxw9xvAvk2yOoUQ= =bE89 -----END PGP SIGNATURE----- --oXNgvKVxGWJ0RPMJ-- From owner-freebsd-stable@freebsd.org Sat May 18 13:03:45 2019 Return-Path: Delivered-To: freebsd-stable@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 CAD92158A651 for ; Sat, 18 May 2019 13:03:45 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (mx.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.sdf.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 713F481740 for ; Sat, 18 May 2019 13:03:44 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id x4ID2Kqa028239 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sat, 18 May 2019 13:02:20 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id x4ID2KZZ028026 for freebsd-stable@freebsd.org; Sat, 18 May 2019 08:02:20 -0500 (CDT) From: Scott Bennett Message-Id: <201905181302.x4ID2KZZ028026@sdf.org> Date: Sat, 18 May 2019 08:02:20 -0500 To: freebsd-stable@freebsd.org Subject: 11-STABLE system unbootable after update User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 713F481740 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-1.96 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.967,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[mx.sdf.org]; NEURAL_HAM_SHORT(-0.33)[-0.328,0]; RCVD_IN_DNSWL_NONE(0.00)[20.94.166.205.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; DMARC_NA(0.00)[sdf.org]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14361, ipnet:205.166.94.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.56)[ip: (-1.79), ipnet: 205.166.94.0/24(-0.89), asn: 14361(-0.05), country: US(-0.06)] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 May 2019 13:03:46 -0000 I have been running 11.2-STABLE for a while at r345498. Last weekend it crashed, so I took the opportunity to install the most recent build I had lying around, r347182. I created a new boot environment and installed the r347182 kernel into it, shut the system down, and rebooted. The new kernel came up and appeared to be working okay, so I continued with the mergemaster -p -F, make installworld, and mergemaster -F, then shut it down again, and rebooted. It asked for the GELI key for the boot pool, which I then entered. The spinning slash cursor appeared and may have changed for one frame or so, and then I got a message beginning with "BTX" and followed by several lines of hexadecimal, and then it stopped. I tried it again just to be sure, and the result was exactly the same. Does anyone know whether the PMBR boot block or the loader in the freebsd-boot partition changed between r345498 and r347182? I found no warning in /usr/src/UPDATING about installworld potentially leaving a wasted system, so I don't have a clear idea of what went wrong, much less whether I missed some instruction somewhere about source updates. If anyone can lend me a clue here, I would greatlyappreciate it. I only had one working machine, and now it is only working in a "rescue" mode by booting from a DVD. (Probably needless to say, but I will burn new DVDs with up-to-date stuff as soon as my system is working the way it is supposed to again.) This motherboard is nearly 11 years old and does not boot from USB (in spite of the BIOS menus say), so at the moment I am logged into SDF by running a long out-of-date TrueOS installer DVD, which happens to be a pain to get to boot all the way, but I've figured how to make it do it rather than get stuck with a logo on the screen that never goes away. Unfortunately, it includes no software to burn a CD or DVD, so I cannot make a new bootable disk for the time being. I will check email much later today or this evening. Thanks in advance for any helpful ideas! Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-stable@freebsd.org Sat May 18 13:42:03 2019 Return-Path: Delivered-To: freebsd-stable@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 1D011158B933 for ; Sat, 18 May 2019 13:42:03 +0000 (UTC) (envelope-from markoml@markoturk.info) Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACEE382FFC for ; Sat, 18 May 2019 13:42:01 +0000 (UTC) (envelope-from markoml@markoturk.info) Received: by mail-wr1-x434.google.com with SMTP id b18so9807499wrq.12 for ; Sat, 18 May 2019 06:42:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=markoturk-info.20150623.gappssmtp.com; s=20150623; h=sender:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=0CQnKAGYQH2YbnJc9kMwiJ736BANZ+beVSUfp5/nbAA=; b=BhIOSjMmy47Yyi7nCzHn99DHePM2/hRzsR3Pyu3g/Gu32rvOylEM+ILGfymsiwJ7V+ oSoU21GJ67ze2fo26g38swbp2dfsS57nrbhgiOl8dWsZ173f1v2hEcRiNymJ098J1vMp TqfsuJ5DPJmpF+sdjgIML3GswbUGqGS8atL5822hCs8MsNjUJ5G+UIOmIaZ8ZZ5jSsDb B/15cBIH5rBAtycz1AC+eypwm66Kua8RzPt2K5kqGtjyZDXtEAzl+CzLeDbzOQdhpJPC 1AbLbnQz1LFt+iG89GVFihu9OdFew9kGnQbGhIX1EBUMLYRaSvI1XEfCu0YyYtg0Ip8B v+dQ== 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:subject:message-id :mime-version:content-disposition:user-agent; bh=0CQnKAGYQH2YbnJc9kMwiJ736BANZ+beVSUfp5/nbAA=; b=TtExwosktLV1qPihmJPQBSaP3cOu9+DRzvolHhDlrIf0rpMZngm8MgDU6hMyXjBfEZ l+AIoXl93H8Eci957JSp91dtMRsPvXK8iMyNWrEjQu1mXuVlSoPNHDDO9UBH6f9XjC+M wp76+hCgBturqfmV7w4CmvkxuwR2uC4jOAeGaAXESrZABPE9bdCaf/aotJEPzG3LlZCS 0oTXQYIbDJFYv4ELXGT0QdgYKag7ylsXALVsMP5j0Igf7ltRehK45Dy6nluYuyhXbuXm lGLxryR2A4nt1qsThDr9oVcTWy6LeK7xji8y2wSl8UcIBl4SzK/phBf+do6d/ka4TDKp N4bw== X-Gm-Message-State: APjAAAUhgZVbHqOXxp7lmOnlg2vlw5JapwCALvs5yP/VeUVvEJCwmYbU eEvst14tenp6RuPVKvqxuqCcEZZE2/4= X-Google-Smtp-Source: APXvYqz3DTsNq2K9bfjmbnarZR5uToPnkB2p8QIa/NAbCLXVum4mE/g+jQx/wcD+122y+t4EiPlWBg== X-Received: by 2002:a5d:5544:: with SMTP id g4mr31735293wrw.327.1558186920070; Sat, 18 May 2019 06:42:00 -0700 (PDT) Received: from vps.markoturk.info (cpe-109-60-8-18.st3.cable.xnet.hr. [109.60.8.18]) by smtp.gmail.com with ESMTPSA id m206sm15294165wmf.21.2019.05.18.06.41.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 May 2019 06:41:59 -0700 (PDT) Sender: Marko Turk Date: Sat, 18 May 2019 15:41:57 +0200 From: Marko Turk To: freebsd-stable@freebsd.org Subject: Mount command shows wrong information for nullfs mounts Message-ID: <20190518134157.GA12983@vps.markoturk.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: ACEE382FFC X-Spamd-Bar: -------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=markoturk-info.20150623.gappssmtp.com header.s=20150623 header.b=BhIOSjMm; spf=softfail (mx1.freebsd.org: 2a00:1450:4864:20::434 is neither permitted nor denied by domain of markoml@markoturk.info) smtp.mailfrom=markoml@markoturk.info X-Spamd-Result: default: False [-8.24 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[markoturk-info.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; 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,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_DN_NONE(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[markoturk.info]; MX_GOOD(-0.01)[vps.markoturk.info]; DKIM_TRACE(0.00)[markoturk-info.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[4.3.4.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(-1.00)[-1.000,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:2a00:1450::/32, country:US]; IP_SCORE(-2.83)[ip: (-9.60), ipnet: 2a00:1450::/32(-2.20), asn: 15169(-2.27), country: US(-0.06)] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 May 2019 13:42:03 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I have the following nullfs mount: /data/downloads on /usr/jails/dlna/mnt/data (nullfs, local, read-only) For some reason, the mount command output shows this: zroot/virtuals/bhyve/fbsd3@change-volmode/data/downloads on /usr/jails/dlna/mnt/data (nullfs, local, read-only) This happened for all nullfs mounts, not just this one. It appeared yesterday, after 40 days of uptime. Before that the mount was shown properly. This extra prefix is probably from the zfs volume that I'd created just before the issue started appearing: zroot/virtuals/bhyve/fbsd3 The zfs volume is not related to /data/downloads mountpoint. I haven't rebooted the system since, does anyone know how to debug this? I'm running: FreeBSD shkatula 11.2-STABLE FreeBSD 11.2-STABLE #7 r343828: Wed Feb 6 10:47:56 CET 2019 root@shkatula:/usr/obj/usr/src/sys/SHKATULA amd64 BR/Marko --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhcgjUnLArcQCyVEgeDpsXaaozYgFAlzgC6QACgkQeDpsXaao zYgoYRAAjvlasGOU361S4xRIteGPJ6ZIXHy3l7ISyzMcQ8Ui0nvjW68Y1Z6Rm7bI t1nuDIhQW+wMD2vfS0ByPLd/r5iM1iH81j+OqoWgKKTJ3nb/MepEhdV1f2zqAYT1 L4zvvOC50RtT9X9jPv1GQh4Ps9LGoFho/FzACmNy5gl1pcMkY9q6MMJ/qYy39Pe6 PcnpuzvXcuTiixvWBdwm3CcWxscVZaPUXbQSspCNn7hJqi6vN/wuVCgwnqCoJmaI lCNIGP9G6HaX3SM+nZgwG8v1PiiJtpz6Hjg6YDd30n/Rh36G2ug/sTkzAw/knWXg QYAj9iGwV725D4UKv8GX2RBVqAyqlaR79IFzbUa04fHvqXNYuq69bzeHwb1Z1B39 LZbTreTMnXAw/14zKeVnmoqmcec8JXh/6BMS/FqHpfkVRk+yubfyirHlFS7jtTrD +KCQhjWQgPPQISkChJ3UEPjtYkZrOjA5ltED8N9jJJyWkh5lpGoX2WKm5uWkEm5k TR5CwMOVx+eREV8vQphPUXXV86pR+DTsP7IkHSeDqvfAjhwKkXggn3Rs/XD1mGqg ZblFUXomglk91zl2UQcIhNg+IuuCDzUGwSNOHPeqEFzwwnzoMXnSa3INiSVbLLEf C5xnWxtkwiF/dkEh0YQgHGLwBI7EwfCP/bKKhY1JLfypkbic0RM= =2oe9 -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/--