Re: port-amd64/56844: delete auto-modified network route crash

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

The following reply was made to PR port-amd64/56844; it has been noted by GNATS.

From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, ocb%l25.fi@localhost
Subject: Re: port-amd64/56844: delete auto-modified network route crash
Date: Thu, 19 May 2022 20:49:36 +0000

 > Date: Wed, 18 May 2022 14:00:00 +0000 (UTC)
 > From: ocb@dc.localdomain
 > 
 > Finally if we try to remove this route by executing 'route delete
 > 192.168.88.2 192.168.88.2', machine running KASLR kernel will be
 > very limited, X continues to be visually responsive, already running
 > terminal emulators can run commands but will hang and can not be
 > paused or killed. New terminal emulators can not be started.
 > Changing active virtual console will finally crash X and kernel. I
 > am not experienced with crashes but this appears like memory is
 > slowly getting corrupted. Kernel crash dump successfully gets saved
 > to swap, but upon reboot is unable to retrieve it from swap. Note,
 > crash dump saving and retrieving works fine on non-kaslr kernel, but
 > not in this situation, since..
 
 Do you have a serial console, or a working network interface where you
 can redirect output via netcat?
 
 Can you start crash(8) running before triggering this (with output to
 serial console or netcat), and, when it starts to hang, type `ps' at
 crash(8)?  And, if any threads listed there are in `tstile' or are
 marked with a `>' on the line, can you type `bt/a 0xffff...' at
 crash(8), where 0xffff... is the lwp address shown in ps output?