Re: kern/56438: panic when trying to use gpioiic in -current 9.99.90

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

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

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/56438: panic when trying to use gpioiic in -current 9.99.90
Date: Mon, 4 Oct 2021 05:42:14 -0000 (UTC)

 brad%anduin.eldar.org@localhost writes:
 
 >[  13.2358565] panic: kernel diagnostic assertion "KERNEL_LOCKED_P()" failed: file "../../../../kern/subr_autoconf.c", line 1053
 >[  13.2487462] cpu0: Begin traceback...
 >[  13.2487462] 0xd1cf1b5c: netbsd:db_panic+0x14
 >[  13.2562360] 0xd1cf1b74: netbsd:vpanic+0x148
 >[  13.2562360] 0xd1cf1b8c: netbsd:__aeabi_uldivmod
 >[  13.2562360] 0xd1cf1bc4: netbsd:config_match+0x88
 >[  13.2680444] 0xd1cf1be4: netbsd:mapply+0x4c
 >[  13.2680444] 0xd1cf1c34: netbsd:config_search_internal+0x1a8
 >[  13.2771142] 0xd1cf1c5c: netbsd:config_search+0x90
 >[  13.2771142] 0xd1cf1cf4: netbsd:gpioioctl+0x3b0
 
 The attachment framework nowadays enforces that it is called with
 the kernel lock held. Since gpio(4) is tagged as 'mpsafe' it has
 to care itself about taking the kernel lock.