Re: PF_UNIX sockets unlocking

2021-02-09 Thread Alexander Bluhm
On Tue, Feb 09, 2021 at 09:14:44PM +0300, Vitaliy Makkoveev wrote: > On Tue, Feb 09, 2021 at 05:20:33PM +0100, Alexander Bluhm wrote: > > > +extern struct rwlock unp_lock; > > > > Could you put this declaration into a header file? > > I see no such sense to do this. `unp_lock' is not system wide

Re: PF_UNIX sockets unlocking

2021-02-09 Thread Vitaliy Makkoveev
On Tue, Feb 09, 2021 at 05:20:33PM +0100, Alexander Bluhm wrote: > On Thu, Feb 04, 2021 at 03:07:44PM +0300, Vitaliy Makkoveev wrote: > > I hope someone else will try it and gives positive feedback which allow > > to push it forward. > > OK bluhm@ > Thanks. > > +extern struct rwlock unp_lock; >

Re: PF_UNIX sockets unlocking

2021-02-09 Thread Alexander Bluhm
On Thu, Feb 04, 2021 at 03:07:44PM +0300, Vitaliy Makkoveev wrote: > I hope someone else will try it and gives positive feedback which allow > to push it forward. OK bluhm@ > +extern struct rwlock unp_lock; Could you put this declaration into a header file?

PF_UNIX sockets unlocking

2021-02-04 Thread Vitaliy Makkoveev
The latest version of the PF_UNIX sockets unlocking diff. The new `unp_lock' rwlock(9) was used as solock()'s backend to protect the whole layer. We release solock() while we perform all vnode(9) related operations. Since fifo subsystem uses unix sockets as backend this is required