Re: Add f_modify and f_process callbacks to socket filterops

2021-05-25 Thread Martin Pieuchot
On 20/05/21(Thu) 14:16, Visa Hankala wrote: > On Thu, May 20, 2021 at 11:35:32AM +0200, Martin Pieuchot wrote: > > On 18/05/21(Tue) 14:22, Visa Hankala wrote: > > > This diff adds f_modify and f_process callbacks to socket event filters. > > > As a result, socket events are handled using the

Re: Add f_modify and f_process callbacks to socket filterops

2021-05-20 Thread Visa Hankala
On Thu, May 20, 2021 at 11:35:32AM +0200, Martin Pieuchot wrote: > On 18/05/21(Tue) 14:22, Visa Hankala wrote: > > This diff adds f_modify and f_process callbacks to socket event filters. > > As a result, socket events are handled using the non-legacy paths in > > filter_modify() and

Re: Add f_modify and f_process callbacks to socket filterops

2021-05-20 Thread Martin Pieuchot
On 18/05/21(Tue) 14:22, Visa Hankala wrote: > This diff adds f_modify and f_process callbacks to socket event filters. > As a result, socket events are handled using the non-legacy paths in > filter_modify() and filter_process() of kern_event.c This a step toward > MP-safety. However, everything

Add f_modify and f_process callbacks to socket filterops

2021-05-18 Thread Visa Hankala
This diff adds f_modify and f_process callbacks to socket event filters. As a result, socket events are handled using the non-legacy paths in filter_modify() and filter_process() of kern_event.c This a step toward MP-safety. However, everything still runs under the kernel lock. The change has