Re: kern/55697: ccd, gpt and, I suppose, kernel panic.

[mlelstv%serpens.de@localhost (Michael van Elst)]

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

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/55697: ccd, gpt and, I suppose, kernel panic.
Date: Tue, 6 Oct 2020 13:01:08 -0000 (UTC)

 joel.bertrand%systella.fr@localhost writes:
 
 >	I have tried to create new wedge on ccd0 with following command :
 >legendre# gpt add -a 4k -l swap_hilbert -s 96g -t swap ccd0
 
 >	Server immediatly reboots. I'm not sure kernel panics (but I suppose)
 >as there is no crashdump and kernel doesn't enter in debugger.
 
 The kernel fails over a recursive lock when gpt issues the DIOCMWEDGES ioctl.
 
 lockdebug_abort() at lockdebug_abort+0xee
 mutex_vector_enter() at mutex_vector_enter+0x364
 ccdopen() at ccdopen+0x52
 spec_open() at spec_open+0x175
 VOP_OPEN() at VOP_OPEN+0x4c
 dkwedge_discover() at dkwedge_discover+0xb4
 disk_ioctl() at disk_ioctl+0xd3
 ccdioctl() at ccdioctl+0x1ea
 VOP_IOCTL() at VOP_IOCTL+0x54
 vn_ioctl() at vn_ioctl+0xa5
 sys_ioctl() at sys_ioctl+0x5ab
 syscall() at syscall+0x157
 
 The error is to call disk_ioctl() with the dvlock held.
 
 -- 
 -- 
                                 Michael van Elst
 Internet: mlelstv%serpens.de@localhost
                                 "A potential Snark may lurk in every tree."