Re: pflow(4): make `so' dereference safe

2022-11-10 Thread Vitaliy Makkoveev
ping... On Fri, Nov 04, 2022 at 10:04:35PM +0300, Vitaliy Makkoveev wrote: > Each pflow(4) interface has associated socket, referenced as sc->so. We > set this socket in pflowioctl() which is called with both kernel and net > locks held. In the pflow_output_process() task we do sc->so

pflow(4): make `so' dereference safe

2022-11-04 Thread Vitaliy Makkoveev
Each pflow(4) interface has associated socket, referenced as sc->so. We set this socket in pflowioctl() which is called with both kernel and net locks held. In the pflow_output_process() task we do sc->so dereference, which is protected by kernel lock. But the sosend(), called deeper by