Re: kern/54504: -9/-current WAPBL panic: current transaction too big, to flush

[Jaromir Dolecek <jaromir.dolecek%gmail.com@localhost>]

The following reply was made to PR kern/54504; it has been noted by GNATS.

From: Jaromir Dolecek <jaromir.dolecek%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: kardel%netbsd.org@localhost
Subject: Re: kern/54504: -9/-current WAPBL panic: current transaction too big, to flush
Date: Mon, 24 Aug 2020 08:32:04 +0200

 Let me chceck the detail first. It seemms to me the check is inherently not M=
 P safe, and thus not a hood final solution.  I would prefer if it properly b=
 ailed out if unallocation registration fails, as is done elsewhere, rather t=
 hen checking size before operation.=20
 
 Please dont commit this for now.  I should be again available later in the w=
 eek, I am currentlt on move so cant check.=20
 
 Jaromir
 
 > Le 24 ao=C3=BBt 2020 =C3=A0 00:45, Konrad Schroder <perseant%hhhh.org@localhost> a =C3=
 =A9crit :
 >=20
 > =EF=BB=BFThe following reply was made to PR kern/54504; it has been noted b=
 y GNATS.
 >=20
 > From: Konrad Schroder <perseant%hhhh.org@localhost>
 > To: NetBSD bugtracking <gnats-bugs%netbsd.org@localhost>
 > Cc: jdolecek%netbsd.org@localhost
 > Subject: Re: kern/54504: -9/-current WAPBL panic: current transaction too b=
 ig,
 > to flush
 > Date: Sun, 23 Aug 2020 15:41:02 -0700
 >=20
 > An updated patch, so that "build.sh release" succeeds (the definition of=20=
 
 > wapbl_check() should be within "#idfef _KERNEL"):
 >=20
 > http://www.hhhh.org/perseant/ffs-wapbl-check-r2.diff
 >=20
 > Any objections to this before I commit?
 >=20
 > Thanks,
 >=20
 > --=20
 > Konrad Schroder
 > perseant%hhhh.org@localhost
 >=20