From nobody Tue Aug 22 00:28:54 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RV9G21rswz4rTmS for ; Tue, 22 Aug 2023 00:29:30 +0000 (UTC) (envelope-from lain@fair.moe) Received: from mail.076.ne.jp (mail.076.ne.jp [45.76.218.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RV9G02Ym9z3QwK for ; Tue, 22 Aug 2023 00:29:27 +0000 (UTC) (envelope-from lain@fair.moe) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=076.ne.jp header.s=dkim header.b=h3RXKmYP; spf=none (mx1.freebsd.org: domain of lain@fair.moe has no SPF policy when checking 45.76.218.69) smtp.mailfrom=lain@fair.moe; dmarc=none Received: from mail.076.ne.jp (localhost [127.0.0.1]) by mail.076.ne.jp (Postfix) with ESMTP id 4RV9Fr1DgGzW0pZ for ; Tue, 22 Aug 2023 09:29:20 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=076.ne.jp; h= user-agent:in-reply-to:content-disposition:content-type :mime-version:references:message-id:subject:to:from:date; s= dkim; t=1692664159; x=1695256160; bh=kkEVJKbPnl+xAW0qcrxZ9B9oti4 9YJdEpUAv0KhwzAI=; b=h3RXKmYPPJL1HgticH7nABYjKyN1Avi9rVB0v0e5BV7 JIJOsHWnPOiQl0vuqCavaTKEnp4krJUAHC+fKEZJM322UFHb+IqgLikQYw6bvRjn fZu1GTo0lYNRAvOn1b8V9Ha/OZivuH9me5DvYUsOFA5Visr7pnxuOW2soyqivHaX F54Dj6iUxWTWe57E8VsYUR/K7s1/WGRaMjxx6v8yqTRzpQJt2U0PQ8plJKTFZifT qC2XAb7kINPZDTGlHNF8dQgnsfufCvzbU19So2JZR8Dk0HX8M1sZlw2AThh6jUlW kRz/oBD8fpCabfiWMB4cm3/4cz9Ycc0wOy0Biw4+JrQ== X-Virus-Scanned: Debian amavisd-new at guest.guest Received: from mail.076.ne.jp ([127.0.0.1]) by mail.076.ne.jp (mail.076.ne.jp [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3FoBO4FDxJh4 for ; Tue, 22 Aug 2023 09:29:19 +0900 (JST) Received: from mail.fair.moe (KD106137200105.ppp-bb.dion.ne.jp [106.137.200.105]) by mail.076.ne.jp (Postfix) with ESMTPSA id 4RV9Fq1cHmzW0pS for ; Tue, 22 Aug 2023 09:29:19 +0900 (JST) Date: Tue, 22 Aug 2023 09:28:54 +0900 From: "lain." To: questions@freebsd.org Subject: Re: ZFS Root size keeps going down after upgrade to 13.2-release Message-ID: X-Location: =?utf-8?B?IkVhcnRoL+WcsOeQgyI=?= X-Operating-System: "GNU/Linux" References: <8f3b445d-3f55-f359-ce5e-0d86c57755fe@optiplex-networks.com> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="kt7frapioq5v6lha" Content-Disposition: inline In-Reply-To: <8f3b445d-3f55-f359-ce5e-0d86c57755fe@optiplex-networks.com> User-Agent: NeoMutt/20230517 X-Spamd-Result: default: False [-4.90 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[076.ne.jp:s=dkim]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; MLMMJ_DEST(0.00)[questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[076.ne.jp:+]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DMARC_NA(0.00)[fair.moe]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:20473, ipnet:45.76.192.0/19, country:US]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; R_SPF_NA(0.00)[no SPF record]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4RV9G02Ym9z3QwK --kt7frapioq5v6lha Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable (Man, I keep fucking this up...) On 2023=E5=B9=B408=E6=9C=8821=E6=97=A5 11:06, Christos Chatzaras wrote: > There are security vulnerabilities in Intel and AMD processors. When do Intel and AMD processors not have security vulnerabilities? > It appears that changes are required both in the operating system code an= d microcode/bios updates. This is why Intel IME and AMD PSP were a mistake from the very beginning. > If I remember correctly, when Spectre and Meltdown vulnerabilities were d= isclosed in early 2018, there was significant controversy surrounding the n= otification process. Several entities, including certain Linux distribution= s and the +FreeBSD project, were not informed as early as some major tech companies. As usual. > I am aware that work is currently being done for upcoming FreeBSD 14 rele= ase and there may not be available human resources, but is there anyone wor= king on this? Seeing the lists AMD and Intel have provided, it seems like I've dodged the bullet pretty epically, but I'm sure far from everyone can claim the same. -- lain. --kt7frapioq5v6lha Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCAAdFiEEozVhUpXECiNYIKIXtWNzC1Y29b0FAmTkAUYACgkQtWNzC1Y2 9b3nzAwAs9HBe+kvsWj9NWSZ5tXMv4eLI4/e4K3fxJvzqmnH3l9IiLVizwUQe4bT nv3Q0WQ1W3Xs7W2hJrUTud1a8pyCoB9AqwhkVWE232BDeLg0+Y6xzKDAhGH4lPRf bY+N6KKk8QJn6D/10F0Z5QZpcyxEPgIwlqjfVti2Ef6fjaogojUay0o6hZrxm44p GwfKg3MGtq95+BeucEZKsgoMSsL52cX7DGnbncFWx4tnSU/vKmzAvwFN/sT4Oxmq tCAQXRvrE7NdXlk+kngpNB7I5g6uH0J4xPnb1FnXTJMVkiTvMlndJr28jf6aKLJO JgORfeV82Cgoj+uMfhSTwNx5AnoJg6g1QximYCxkmAiT77qD3Vh2/0JYlwlx6SKw aunCSyEvs5DCZsDLqLVyv3y0BbyEtXdmpdbWHW8kyc4l13xCE5yjwQMm5JfAEd9r JdWsl+QXE8cGpgy30eIuFQRMj6+9V32UMekVMdiDkGWlf5aG+y77e5gszat8nGOb sBBY2Nvv =htLM -----END PGP SIGNATURE----- --kt7frapioq5v6lha--