I saw some changes to wg recently, so I wanted to report the issue in
case recent commit changed something in time for release. I understand
the issue is probably a year old by now. I guess I hadn't destroyed wg
for a while, although I do believe I have...
• Alexander Bluhm [2023-10-04 16:31]:
On Wed, Oct 04, 2023 at 10:08:01AM -0400, Sonic wrote:
See the post:
"Uninterruptible D State after ifconfig wg0 destroy" Oct. 31, 2022 in the
Bugs archive.
I have a test regress/sys/net/wg that configures a wg(4), sends
some traffic, and destroys it. I have never seen this bug. There
must be something special to trigger it.
If it happns again, could you send an 'ps axlww | grep ifconifg'
output? Then we see the wait channel where it hangs in the kernel.
$ ps axlww
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
Here it happened again:
0 75339 23922 0 10 0 360 296 wg_ifq D+U p0 0:00.00
ifconfig wg1 destroy
The WCHAN string can be found in the kernel sources and gives hints.
More sophisticated would be to break into ddb and show the kernel
stack trace of the ifconfig process. If you want to do that, I can
give some advice. But I recommend a serial console for that.
Any idea what you did specially to trigger the problem?
I did a down, delete and destroy sequence on a newly booted system.
OpenBSD 7.4 (GENERIC) #1332: Wed Oct 4 01:00:54 MDT 2023
bluhm
