[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7d4707fa-4161-865f-2445-675be6d70ddb@leemhuis.info>
Date: Sat, 5 Aug 2023 14:16:30 +0200
From: "Linux regression tracking #update (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: XFS metadata CRC errors on zram block device on ppc64le
architecture
[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.
Powered by blists - more mailing lists