From nobody Sun Dec 3 00:11:48 2023 X-Original-To: freebsd-stable@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 4SjS0C1vfyz53G53 for ; Sun, 3 Dec 2023 00:11:55 +0000 (UTC) (envelope-from mem@schmem.com) Received: from shell.qozzy.net (schorl.qozzy.net [209.104.225.37]) by mx1.freebsd.org (Postfix) with SMTP id 4SjS0B3jghz3PN2 for ; Sun, 3 Dec 2023 00:11:54 +0000 (UTC) (envelope-from mem@schmem.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of mem@schmem.com designates 209.104.225.37 as permitted sender) smtp.mailfrom=mem@schmem.com; dmarc=none Received: (qmail 8886 invoked by uid 101); 2 Dec 2023 19:11:48 -0500 From: "Mark E. Mallett" Date: Sat, 2 Dec 2023 19:11:48 -0500 To: freebsd-stable@freebsd.org Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs Message-ID: References: <20231201031737.DF0231B942@freefall.freebsd.org> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.10 (2023-03-25) X-Spamd-Result: default: False [-0.24 / 15.00]; NEURAL_HAM_LONG(-0.97)[-0.967]; NEURAL_SPAM_SHORT(0.96)[0.958]; R_SPF_ALLOW(-0.20)[+ip4:209.104.225.32/27]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_MEDIUM(0.07)[0.073]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[schmem.com]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; ASN(0.00)[asn:14265, ipnet:209.104.224.0/20, country:US] X-Rspamd-Queue-Id: 4SjS0B3jghz3PN2 X-Spamd-Bar: / Might I also ask (or say): I find some of the notice and actions confusing, at least in minor ways. I'm mainly only remarking since the subject has been opened. First, "Background" talks about FreeBSD 12 ZFS being based on Illumos ZFS, and 13 and on being based on OpenZFS. I kinda wish the notice would say why it tells me that, because the implication in the text is that both are affected. It would be nice if it said "both are affected" right out in the open. I realize it's implied. Second, it gives workaround of "vfs.zfs.dmu_offset_next_sync sysctl to 0" But on my 12.4 systems there is no such sysctl variable. Third, it says the binary upgrade will result in 12.4-RELEASE-p8. When I do the freebsd-update, the result according to uname is 12.4-RELEASE-p6. Thinking that perhaps I have to do it again, I am told No updates needed to update system to 12.4-RELEASE-p8 and yet uname -a still says 12.4-RELEASE-p6. Somebody might ask if I did a reboot, and yes. (and there's still no vfs.zfs.dum_offset variable) Like I said, all pretty minor except maybe the sysctl variable one. I'm mostly bothered because I'm overly literal and/or anal. I was starting from p1. I hadn't seen anything urging me to step up to a different patch level, hopefully I hadn't overlooked anything. -mm- (long time no post)