On Thu, 06 Feb 2025 10:46:57 +0100, Jan Kara wrote:
> filesystem fuzzing of ocfs2 has revealed some issues in jbd2 where suitably
> corrupted fs can trigger issues in jbd2 - most notably a complaint about
> sb->s_sequence being 0 (which is actually correct after recent changes) and
> also attempt to replay the journal after it has been wiped. Fix them.
>
> Honza
>
> [...]
Applied, thanks!
[1/2] jbd2: Remove wrong sb->s_sequence check
commit: e6eff39dd0fe4190c6146069cc16d160e71d1148
[2/2] jbd2: Do not try to recover wiped journal
commit: a662f3c03b754e1f97a2781fa242e95bdb139798
Best regards,
--
Theodore Ts'o <tytso@xxxxxxx>
