On 18.03.25 09:35, Anand Jain wrote: > On 17/3/25 23:04, Johannes Thumshirn wrote: >> From: Johannes Thumshirn <johannes.thumshirn@xxxxxxx> >> >> Recently we had a bug report about a kernel crash that happened when the >> user was converting a filesystem to use RAID1 for metadata, but for some >> reason the device's write pointers got out of sync. >> >> Test this scenario by manually injecting de-synchronized write pointer >> positions and then running conversion to a metadata RAID1 filesystem. >> >> In the testcase also repair the broken filesystem and check if both system >> and metadata block groups are back to the default 'DUP' profile >> afterwards. >> >> Link: https://lore.kernel.org/linux-btrfs/CAB_b4sBhDe3tscz=duVyhc9hNE+gu=B8CrgLO152uMyanR8BEA@xxxxxxxxxxxxxx/ >> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@xxxxxxx> > > > looks good. > > Reviewed-by: Anand Jain <anand.jain@xxxxxxxxxx> > > added to for-next. Thanks, but the kernel fix for this isn't merged yet. So running this testcase will crash kernel's with zoned btrfs.
