Re: BLAKE3 unstability?

In reply to: Evgeniy Khramtsov : "BLAKE3 unstability?"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Warner Losh <imp_at_bsdimp.com>
Date: Sat, 09 Jul 2022 16:31:50 UTC

Be advised that blake3 went into the bootloader yesterday and has been only
lightly tested.

Don't think this would cause your checksum errors since the boot loader is
read only.

Warner

On Sat, Jul 9, 2022, 10:27 AM Evgeniy Khramtsov <evgeniy@khramtsov.org>
wrote:

> -CURRENT as of:
>
> commit eec3290266bc09b4c4b4d875d2269d611adc0016 (main)
> Author: Ganbold Tsagaankhuu <ganbold@FreeBSD.org>
> Date:   Sat Jul 9 13:06:52 2022 +0000
>
>     Add RK3568 SoC support to pinctrl driver.
>
>     Submitted by:   sos
>     Reviewed by:    manu
>     Differential Revision:
>     https://reviews.freebsd.org/D31330
>
> New boot environment created via bectl, zfs set checksum=blake3 new_be,
> pkg -r /tmp/be_N upgrade, reboot into new BE, login failed after
> sysutils/pam_xdg failed integrity check.
>
> Rebooted into previous BE, did zpool scrub and got 32 checksum errors
> without files specified before getting panic (no trace due to drm-kmod?).
>
> bectl destroy / zfs destroy of new env with blake3 restored pool back to
> 0 checksum error state.
>
> No out-of-tree base modifications present, only a custom kernel config.
>
>