Re: Call sysctl_source() with shared netlock

2023-04-20 Thread Alexander Bluhm
On Thu, Apr 20, 2023 at 03:11:15PM +0300, Vitaliy Makkoveev wrote: > Now rtable_*source() are polished, so we could push this diff to tree. > > ok? OK bluhm@ > On Mon, Apr 17, 2023 at 02:36:57AM +0300, Vitaliy Makkoveev wrote: > > It seems rt_setsource() needs some attention, but sysctl_source()

Re: Call sysctl_source() with shared netlock

2023-04-20 Thread Vitaliy Makkoveev
Now rtable_*source() are polished, so we could push this diff to tree. ok? On Mon, Apr 17, 2023 at 02:36:57AM +0300, Vitaliy Makkoveev wrote: > It seems rt_setsource() needs some attention, but sysctl_source() could > be called with shared netlock just now. > > Index: sys/net/rtsock.c >

Re: Call sysctl_source() with shared netlock

2023-04-18 Thread Vitaliy Makkoveev
On Tue, Apr 18, 2023 at 03:36:09PM +0200, Alexander Bluhm wrote: > On Mon, Apr 17, 2023 at 05:53:28PM +0200, Alexander Bluhm wrote: > > On Mon, Apr 17, 2023 at 04:32:13PM +0200, Alexander Bluhm wrote: > > > On Mon, Apr 17, 2023 at 02:36:57AM +0300, Vitaliy Makkoveev wrote: > > > > It seems rt_setso

Re: Call sysctl_source() with shared netlock

2023-04-18 Thread Alexander Bluhm
On Mon, Apr 17, 2023 at 05:53:28PM +0200, Alexander Bluhm wrote: > On Mon, Apr 17, 2023 at 04:32:13PM +0200, Alexander Bluhm wrote: > > On Mon, Apr 17, 2023 at 02:36:57AM +0300, Vitaliy Makkoveev wrote: > > > It seems rt_setsource() needs some attention, but sysctl_source() could > > > be called wi

Re: Call sysctl_source() with shared netlock

2023-04-17 Thread Alexander Bluhm
On Mon, Apr 17, 2023 at 06:33:50PM +0300, Vitaliy Makkoveev wrote: > However, the renaming of `source' to `ar_source' diff is pretty small. > We use 'art_root' structure in regress/sys/net/rtable/delete and in > usr.bin/netstat/ but we don't touch `source'. OK bluhm@ > Index: sys/net/art.h >

Re: Call sysctl_source() with shared netlock

2023-04-17 Thread Alexander Bluhm
On Mon, Apr 17, 2023 at 04:32:13PM +0200, Alexander Bluhm wrote: > On Mon, Apr 17, 2023 at 02:36:57AM +0300, Vitaliy Makkoveev wrote: > > It seems rt_setsource() needs some attention, but sysctl_source() could > > be called with shared netlock just now. > > I think rtable_setsource() is not MP saf

Re: Call sysctl_source() with shared netlock

2023-04-17 Thread Vitaliy Makkoveev
On Mon, Apr 17, 2023 at 04:32:13PM +0200, Alexander Bluhm wrote: > On Mon, Apr 17, 2023 at 02:36:57AM +0300, Vitaliy Makkoveev wrote: > > It seems rt_setsource() needs some attention, but sysctl_source() could > > be called with shared netlock just now. > > I think rtable_setsource() is not MP saf

Re: Call sysctl_source() with shared netlock

2023-04-17 Thread Alexander Bluhm
On Mon, Apr 17, 2023 at 02:36:57AM +0300, Vitaliy Makkoveev wrote: > It seems rt_setsource() needs some attention, but sysctl_source() could > be called with shared netlock just now. I think rtable_setsource() is not MP safe. It is documented as [K] kernel lock. But that is not true and makes no

Call sysctl_source() with shared netlock

2023-04-16 Thread Vitaliy Makkoveev
It seems rt_setsource() needs some attention, but sysctl_source() could be called with shared netlock just now. Index: sys/net/rtsock.c === RCS file: /cvs/src/sys/net/rtsock.c,v retrieving revision 1.359 diff -u -p -r1.359 rtsock.c --