Received: by 2002:a05:6359:6284:b0:131:369:b2a3 with SMTP id se4csp1053269rwb; Sat, 5 Aug 2023 06:31:03 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFjxjp6LR1ga2EdWB/7iQdaW9myk4O79KdzRgN6Y+L1ascpUHnhpGztti9zSxRpsBhwVJQW X-Received: by 2002:a17:907:2ccc:b0:994:1eb4:6896 with SMTP id hg12-20020a1709072ccc00b009941eb46896mr2703887ejc.25.1691242263573; Sat, 05 Aug 2023 06:31:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1691242263; cv=none; d=google.com; s=arc-20160816; b=UZQpfdmWZukmDpUF+7rdEPrnv192qVI/tkdcmBrHUUXQ3FSkWsgDkTCxRjlgXU4aY3 M6pmRRFzuqLw8X1dYMmXgHwhqyowXWyUeGnUzAXd9B7zQmwrBOPJ2y8CED2DSoWdq0oM SgrV86AHj+i7aD97B35qyNFBwGbaZ8JiqWW+cSqVw4frOPQtTDV/vppz0RcUl0KAraSE mel30We8CgW2onh6FNmkdUGMAG4oaFKXlavVO5PsvKmI3BMyqM5lXcweuFFTR0RGZG3z ynTdNoYpmHFePw7oq1n9ZABIWB437yKVaKyrE8AFzy8dXpF9WT+jO6y0fmYYD3Y/9XTy Kk9Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:references :reply-to:to:from:content-language:subject:user-agent:mime-version :date:message-id; bh=n+r4AYfQhljemcZAw04NJCRyviXPZutWpxsLtnomc8s=; fh=h460o/SFw13E3WeE09lFOLUyXuoNfyETrb6kqjgenV8=; b=1J1bSw8SdHwOYeAjnqf9EAbETaEu8QIZ1hNUY7en8xmBO1qIhhj/XNhjQu1dbRbaWH I2FlfZiVAKbI0jg9gWPdA/yjdqV/ObV1Z0i+G2g5XFolCJR1ptFpOkHvXgbqx7CIW9OF 52UAc4ygreowIMkheHtOoHvObw1+uDb1czG7J8Jji7eZtiBOP+BJ20Q8t9Wv9wqgtZGO EugRO7odWakeRnV+uOMFmcGY41OTNDygkunGoFWVu6jf35LMI7emOHj5z9EF+kYepD1P VGMDFb9mIK/rPYpG9ODLXvIjwy0YMVttKLM+vLIXtAQlT2mA334uBjsxuf/b7S9Ug0uJ 0r+Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id si26-20020a170906ceda00b0099bd53a0d3csi1743849ejb.178.2023.08.05.06.30.30; Sat, 05 Aug 2023 06:31:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229992AbjHEMQh (ORCPT + 99 others); Sat, 5 Aug 2023 08:16:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58852 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229741AbjHEMQg (ORCPT ); Sat, 5 Aug 2023 08:16:36 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F23794237; Sat, 5 Aug 2023 05:16:33 -0700 (PDT) Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1qSGCt-0000Dd-FE; Sat, 05 Aug 2023 14:16:31 +0200 Message-ID: <7d4707fa-4161-865f-2445-675be6d70ddb@leemhuis.info> Date: Sat, 5 Aug 2023 14:16:30 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: XFS metadata CRC errors on zram block device on ppc64le architecture Content-Language: en-US, de-DE From: "Linux regression tracking #update (Thorsten Leemhuis)" To: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Linux kernel regressions list Reply-To: Linux regressions mailing list , Linux regressions mailing list References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1691237794;5d1a7720; X-HE-SMSGID: 1qSGCt-0000Dd-FE X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [TLDR: This mail in primarily relevant for Linux regression tracking. A change or fix related to the regression discussed in this thread was posted or applied, but it did not use a Closes: tag to point to the report, as Linus and the documentation call for. Things happen, no worries -- but now the regression tracking bot needs to be told manually about the fix. See link in footer if these mails annoy you.] On 04.08.23 18:22, Linux regression tracking #adding (Thorsten Leemhuis) wrote: > On 02.08.23 05:31, Dusty Mabe wrote: >> In Fedora CoreOS we found an issue with an interaction of an XFS filesystem on a zram block device on ppc64le: >> >> - https://github.com/coreos/fedora-coreos-tracker/issues/1489 >> - https://bugzilla.redhat.com/show_bug.cgi?id=2221314 #regzbot monitor: https://lore.kernel.org/all/20230805055537.147835-1-hch@lst.de/ #regzbot fix: zram: take device and not only bvec offset into account #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.