linux-kernel - Re: [GIT PULL] bcachefs fixes for 6.9

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <gqtaouixd7pmxyzttmyexwqzrziujo7ncqoc54vqhjqdnr326u@t5eolb2vdihp>
Date: Tue, 7 May 2024 11:27:52 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-bcachefs@...r.kernel.org, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.9

On Tue, May 07, 2024 at 11:10:44AM -0400, Kent Overstreet wrote:
> On Tue, May 07, 2024 at 10:43:11AM -0400, Kent Overstreet wrote:
> > Hi Linus, another stack of fixes for you.
> 
> I have a report from a user that the sb-downgrade validation has an
> issue, so that's been yanked.

As a followup: the sb-downgrade patch was good, the user had at some
point been running an unreleased version (which adds new accounting for
amount of unstriped data in stripe buckets); and that version generated
a faulty downgrade entry (because it has custom logic for generating the
downgrade entry based on whether erasure coding is in use).

But I'm still holding that patch for now while I come up with something
for that user's filesystem - I'll probably add a flags parameter to that
validation code so that we only fail to validate if we're writing out
something new, like we already can for bkeys.