Re: sincosl() segmentation fault

2024-04-30 Thread Jonathan Gray
On Tue, Apr 30, 2024 at 06:18:23PM +0100, colin.i.k...@gmail.com wrote: > >Synopsis:sincosl() segmentation fault > >Category:library > >Environment: > System : OpenBSD 7.5 > Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024 >

Re: Fwd: Assertion !cold failed in drm during sys_reboot

2024-04-30 Thread Jonathan Gray
On Tue, Apr 30, 2024 at 09:31:47AM -0500, Nathaniel Griswold wrote: > > >Synopsis: Assertion !cold failed in drm after console ctrl-alt-del > >Category: system > >Environment: > System : OpenBSD 7.5 > Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024 >

sincosl() segmentation fault

2024-04-30 Thread colin . i . king
>Synopsis: sincosl() segmentation fault >Category: library >Environment: System : OpenBSD 7.5 Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Re: kernel panics on NODEV in ioctl create RAID call

2024-04-30 Thread Klemens Nanni
On Tue, Apr 30, 2024 at 12:03:04PM GMT, Alexander Klimov wrote: > Hello everyone! > > Actually I was working on a way to create a degraded RAID. > As the ioctl create RAID syscall takes a list of dev_t, > I tried NODEV for Not yet Online DEVice. ;-) > I expected the kernel to complain. But

Re: lock order reversal in soreceive and NFS

2024-04-30 Thread Alexander Bluhm
On Tue, Apr 30, 2024 at 05:26:15PM +0300, Vitaliy Makkoveev wrote: > On Tue, Apr 30, 2024 at 04:06:29PM +0200, Mark Kettenis wrote: > > > Date: Tue, 30 Apr 2024 16:18:31 +0300 > > > From: Vitaliy Makkoveev > > > > > > On Tue, Apr 30, 2024 at 11:08:13AM +0200, Martin Pieuchot wrote: > > > > > >

Re: lock order reversal in soreceive and NFS

2024-04-30 Thread Vitaliy Makkoveev
On Tue, Apr 30, 2024 at 04:06:29PM +0200, Mark Kettenis wrote: > > Date: Tue, 30 Apr 2024 16:18:31 +0300 > > From: Vitaliy Makkoveev > > > > On Tue, Apr 30, 2024 at 11:08:13AM +0200, Martin Pieuchot wrote: > > > > > > On the other side, would that make sense to have a NET_LOCK()-free > > >

Re: lock order reversal in soreceive and NFS

2024-04-30 Thread Mark Kettenis
> Date: Tue, 30 Apr 2024 16:18:31 +0300 > From: Vitaliy Makkoveev > > On Tue, Apr 30, 2024 at 11:08:13AM +0200, Martin Pieuchot wrote: > > > > On the other side, would that make sense to have a NET_LOCK()-free > > sysctl path? > > > > To me it's better to remove uvm_vslock() from network

Re: lock order reversal in soreceive and NFS

2024-04-30 Thread Vitaliy Makkoveev
On Tue, Apr 30, 2024 at 11:08:13AM +0200, Martin Pieuchot wrote: > > On the other side, would that make sense to have a NET_LOCK()-free > sysctl path? > To me it's better to remove uvm_vslock() from network related sysctl paths. uvm_vslock() used to avoid context switch in the uiomove() call to

Re: lock order reversal in soreceive and NFS

2024-04-30 Thread Vitaliy Makkoveev
On Tue, Apr 30, 2024 at 11:08:13AM +0200, Martin Pieuchot wrote: > > So the issue here is due to NFS entering the network stack after the > VFS. Alexander, Vitaly are we far from a NET_LOCK()-free sosend()? > Is something we should consider? > We are close enough, but I want to unlock raw and

kernel panics on NODEV in ioctl create RAID call

2024-04-30 Thread Alexander Klimov
Hello everyone! Actually I was working on a way to create a degraded RAID. As the ioctl create RAID syscall takes a list of dev_t, I tried NODEV for Not yet Online DEVice. ;-) I expected the kernel to complain. But instead it crashed. How to reproduce: 1) Apply the diff below. 2) Build (just)

Re: lock order reversal in soreceive and NFS

2024-04-30 Thread Mark Kettenis
> Date: Tue, 30 Apr 2024 11:08:13 +0200 > From: Martin Pieuchot > > On 27/04/24(Sat) 13:44, Visa Hankala wrote: > > On Tue, Apr 23, 2024 at 02:48:32PM +0200, Martin Pieuchot wrote: > > > [...] > > > I agree. Now I'd be very grateful if someone could dig into WITNESS to > > > figure out why we

Re: lock order reversal in soreceive and NFS

2024-04-30 Thread Alexander Bluhm
On Tue, Apr 30, 2024 at 11:08:13AM +0200, Martin Pieuchot wrote: > > With the patch, the nfsnode-vmmaplk reversal looks like this: > > So the issue here is due to NFS entering the network stack after the > VFS. Alexander, Vitaly are we far from a NET_LOCK()-free sosend()? > Is something we

Re: lock order reversal in soreceive and NFS

2024-04-30 Thread Martin Pieuchot
On 27/04/24(Sat) 13:44, Visa Hankala wrote: > On Tue, Apr 23, 2024 at 02:48:32PM +0200, Martin Pieuchot wrote: > > [...] > > I agree. Now I'd be very grateful if someone could dig into WITNESS to > > figure out why we see such reports. Are these false positive or are we > > missing data from the