From nobody Sat Mar 19 14:03:54 2022 X-Original-To: dev-commits-ports-main@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 AC7811A16EF5; Sat, 19 Mar 2022 14:04:03 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KLN0M3rgBz3H0Q; Sat, 19 Mar 2022 14:04:03 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-oi1-x232.google.com with SMTP id z8so11766974oix.3; Sat, 19 Mar 2022 07:04:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=qB4oFhSyWfKd75zyR6gY7doJjyuvAx4iTbZRMpxr43g=; b=Kuh3QBMoYDpQ17rN4Rtdm5jNAIj0phU99jyK38x3sc5FdUIkWIxwDPz7JrAdup66W7 UvP9OOLBt3FhN/L4Zt6jNhQdWyUGORR08DU3CObBy86YwiB6wtULxqAAA61LwZ+7YBIN bZmzpSzlOECyPnH96PonQK9dFlrbPIF4RYHoIEcD4J6hziepIZu6pHBnmK/XYmquMgzf 0KqFCiEjM4aCBpMVhRH+T8Oe7g8S6nyBCQ2L0h8NyVDQYjDsgmeqsxtmkzPHlTGo6ZU1 BCi+h1JGU0QmQ231uBBB6c8vAxnYqy48WbCiFi+tm9+jyNX47gkozPJyHVejcCBQsjTU 8Uhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=qB4oFhSyWfKd75zyR6gY7doJjyuvAx4iTbZRMpxr43g=; b=KS1npU+kQy4gVXbsglt1nSW/VmMmguzvIrfzrH8zRIv3pAmG3sQ45RY8W6HTCvODRV jHaBo9SpLJCohJnXotMVIP1vEcQejApnzoGP3uIU+eL3AxDcpGOmwboob1MSOMH1DLV8 5evaVJ5Lkbf9cGgbrVXUYgNesL4WluZsMqVB/0OqvbBEwScHW0opigxuIXPQCzuBwzwF XwDayZUVi9TW23Y6QIKa8o4j6fsq0TCMauFfkTiiMw83yOc8uYuqgpfwMKjuhpwftiCM jHrAntmk0hNB1eJX+D+OLqXVXTFBt0qKNAw4BH5LfUd4u0OuAPKuA9jStYfYcK+05DWh iPcw== X-Gm-Message-State: AOAM531VywtohRis4Be84yJauUYkHBeHhkoHPpv5tbX0d/eyJ6sy2aqk CpdG9de4VcD4KR7LvMuJoOmyNN+ybmoAVQ2S X-Google-Smtp-Source: ABdhPJzaVBh6gLRwbMCwptb2exO2doTlvv9XOC8AGXStvgbDtWUdXdHpeFXFKnXZtNYYApBztbnWrw== X-Received: by 2002:aca:36c3:0:b0:2ec:cf67:b8fe with SMTP id d186-20020aca36c3000000b002eccf67b8femr6188126oia.141.1647698636526; Sat, 19 Mar 2022 07:03:56 -0700 (PDT) Received: from framework ([187.144.106.84]) by smtp.gmail.com with ESMTPSA id t21-20020a9d7495000000b005c933cbc964sm5075110otk.5.2022.03.19.07.03.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 19 Mar 2022 07:03:55 -0700 (PDT) Date: Sat, 19 Mar 2022 10:03:54 -0400 From: Mark Johnston To: Thomas Zander Cc: Rene Ladan , Matthias Fechner , Christoph Moench-Tegeder , Bernard Spil , "ports-committers@FreeBSD.org" , dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org, secteam@freebsd.org Subject: Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n Message-ID: References: <579f562b-8add-d3f7-77c9-1a6126bd282b@FreeBSD.org> List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-main@freebsd.org X-BeenThere: dev-commits-ports-main@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4KLN0M3rgBz3H0Q X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sat, Mar 19, 2022 at 12:40:45PM +0100, Thomas Zander wrote: > On Sat, 19 Mar 2022 at 12:11, Rene Ladan wrote: > > > > On Sat, Mar 19, 2022 at 11:04:58AM +0100, Thomas Zander wrote: > > > On Sat, 19 Mar 2022 at 09:00, Matthias Fechner wrote: > > > > > > > I can confirm now, the problem is definitely related to the -p8 update. > > > > I rolled back now to -p7 using `freebsd-update rollback`. > > > > [...] > > > > System is now up and running again. > > > > This all works even if poudriere jail is using -p8. No need to downgrade the jail/base version poudriere is using. > > > > It is caused by the kernel so the ZFS patch seems to be broken and -p8 should maybe not rolled out to not break more systems of users. > > > > > > On top of "stop rollout", there is the question how to identify the > > > broken files for the users who have already upgraded to -p8. A `zpool > > > scrub` presumably won't help. > > > > I think it also applies to 13.1-BETA2 ? > > > > Should we involve/CC some src committers? > > I have just rolled back to -p7 and run a number of test builds in > poudriere (the jails still have the -p8 user land). I see the same as > Matthias and Christoph, the rollback to the -p7 kernel/zfs resolved > the build problems, there are no NUL byte files generated anymore. > Adding markj@ to the discussion. Mark, the TLDR so far: > - One of the zfs patches in -p8 seems to cause erroneous writes. > - We noticed because of many build failures with poudriere (presumably > highly io-loaded during build). > - Symptom: Production of files with large runs of NUL-bytes. Looking at it now. Does the problem appear on systems updated with freebsd-update, or built from source, or both?