Re: Call sysctl_ifnames() with shared netlock

2023-04-18 Thread Alexander Bluhm
On Mon, Apr 17, 2023 at 05:43:05PM +0300, Vitaliy Makkoveev wrote: > On Mon, Apr 17, 2023 at 02:58:59PM +0200, Alexander Bluhm wrote: > > On Mon, Apr 17, 2023 at 01:20:28AM +0300, Vitaliy Makkoveev wrote: > > > It performs read-only access to netlock protected data. > > > > OK bluhm@ > > > > Coul

Re: Call sysctl_ifnames() with shared netlock

2023-04-17 Thread Vitaliy Makkoveev
On Mon, Apr 17, 2023 at 02:58:59PM +0200, Alexander Bluhm wrote: > On Mon, Apr 17, 2023 at 01:20:28AM +0300, Vitaliy Makkoveev wrote: > > It performs read-only access to netlock protected data. > > OK bluhm@ > > Could you somewhere document that ifnetlist is protected by netlock? > We use both k

Re: Call sysctl_ifnames() with shared netlock

2023-04-17 Thread Alexander Bluhm
On Mon, Apr 17, 2023 at 01:20:28AM +0300, Vitaliy Makkoveev wrote: > It performs read-only access to netlock protected data. OK bluhm@ Could you somewhere document that ifnetlist is protected by netlock? > Index: sys/net/rtsock.c >

Call sysctl_ifnames() with shared netlock

2023-04-16 Thread Vitaliy Makkoveev
It performs read-only access to netlock protected data. 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 --- sys/net/rtsock.c22 Jan 2023 12:05:44 - 1.