Re: Move solock() down to sosetopt()

2023-07-28 Thread Alexander Bluhm
On Sat, Jul 22, 2023 at 05:42:49PM +0300, Vitaliy Makkoveev wrote: > Thanks for testing. There is updated diff below. OK bluhm@ > Index: sys/kern/uipc_socket.c > === > RCS file: /cvs/src/sys/kern/uipc_socket.c,v > retrieving

Re: Move solock() down to sosetopt()

2023-07-22 Thread Vitaliy Makkoveev
On Fri, Jul 21, 2023 at 07:38:17PM +0200, Alexander Bluhm wrote: > On Thu, Jul 13, 2023 at 02:22:17AM +0300, Vitaliy Makkoveev wrote: > > This is a part of my standalone sblock() work. I need this movement > > because buffers related SO_SND* and SO_RCV* socket options modification > > should be

Re: Move solock() down to sosetopt()

2023-07-21 Thread Alexander Bluhm
On Thu, Jul 13, 2023 at 02:22:17AM +0300, Vitaliy Makkoveev wrote: > This is a part of my standalone sblock() work. I need this movement > because buffers related SO_SND* and SO_RCV* socket options modification > should be protected with sblock(). However, standalone sblock() has > different lock

Move solock() down to sosetopt()

2023-07-12 Thread Vitaliy Makkoveev
This is a part of my standalone sblock() work. I need this movement because buffers related SO_SND* and SO_RCV* socket options modification should be protected with sblock(). However, standalone sblock() has different lock orders with solock() for receive and send buffers. At least sblock() for