From nobody Sat Mar 19 16:42:59 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 6DECE1A1684D; Sat, 19 Mar 2022 16:43:10 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (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 4KLRWx5cwhz4Qr5; Sat, 19 Mar 2022 16:43:09 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-oi1-x234.google.com with SMTP id 12so12006106oix.12; Sat, 19 Mar 2022 09:43:09 -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=tAooG/CExBWkXs20TI7/21VgYrtbYO97TuJjTdzFA2s=; b=IA9yn7DuwNYAN3m9rN9DgflNyPnCksBPu3HDyK+pCMiHu6h/LedOkKKdFCN6SRn7b+ vA8pLeeIm9BmhdHf0EHOkF7KRGCPJIb06dncUfECMJzI2MRLy0niPiZpJQ23bAQ07f+u CsxOJ3DQgQJEgrYTxeeDKUQdLORUCO2YWo4ymYIN5vcQ8VWFR3OaMUV0Gvyq6LQ8fhwt mwVoqDNT4FH3IeNU7ydzUZMX0P0Rfjg526EfVzqfFR2NdMVMmDrXF4vbUyjWbVhcu/s4 SN8VoE3GNhx4icXVDaVJtpUXwPgmpIsLZy0g2CmpNwbYliISuSC7bn7p3/4EqpIi+jYO OyAQ== 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=tAooG/CExBWkXs20TI7/21VgYrtbYO97TuJjTdzFA2s=; b=g+yOecyX9kYtDGlDOlCvBpxZfQ6jzVSBsRjJOEusH4iHUFcETnLqNQpvOVBRvZUQ5t 0r1TTG0YU9a2ltU82FHed25wBtTf9Of2N4G0GNOMXU+jvfvrt+zq9ZQ2MtpaHFMKtkfF ECyh/Q8PDOaYJPl20Pojne2s0du88vBCCF6J13ExgxZSw+nLwaYzoGkXjSCTq7ZCVhKG x6gbl94zFzUw4qtIIpKShmADyzF7zd0gLzWzs3wUBjcjrodxYmxL3xYx9FKRmNrjBbwh nQ8md33gGtHjNnluN7Nl6PqU9JY3OY9trvkG4p1BJ2W0TqgLAwfdndWD9ML4aOt0+MaS 1fbg== X-Gm-Message-State: AOAM531A8hFzGisqnT8ppqmmX1AqlQ/2Rp1hndB+EIfEsHJuvXQMh5QH kSEclIOryPS2RLUhlEMwzz8pa9rUZ6ycUWDj X-Google-Smtp-Source: ABdhPJzaDZLRodFa7UNxsg2eegziaOcx0N0z6PSiGbwIhzXCglh7B5BtkBDf1EE7vzJvDFNnm0nOpw== X-Received: by 2002:a05:6808:1883:b0:2da:3ed2:68cf with SMTP id bi3-20020a056808188300b002da3ed268cfmr6796414oib.204.1647708182229; Sat, 19 Mar 2022 09:43:02 -0700 (PDT) Received: from framework ([187.144.106.84]) by smtp.gmail.com with ESMTPSA id 96-20020a9d0469000000b005c959dd643csm5269025otc.3.2022.03.19.09.43.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 19 Mar 2022 09:43:01 -0700 (PDT) Date: Sat, 19 Mar 2022 12:42:59 -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: 4KLRWx5cwhz4Qr5 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. I've had zero luck reproducing this locally. I built several hundred ports, including textproc/py-pystemmer mentioned elsewhere in the thread, without any failures or instances of zero-filled files. Another member of secteam also hasn't been able to trigger any build failures on -p8. Any hints on a reproducer would be useful. We can simply push a -p9 which reverts EN-22:10 and :11, but of course it would be preferable to precisely identify the problem.