"wireguard" implementation improperly merged and needs revert

2020-08-22 Thread Jason A. Donenfeld
Hi Taylor/Ozaki-san/NetBSD developers, I'm very excited that NetBSD is enthusiastic about WireGuard. Having more deployment of WireGuard is always great to hear. And NetBSD is really a terrific project. I've been enthusiastic about using it for rump kernels for many years, and adding WireGuard cap

Re: "wireguard" implementation improperly merged and needs revert

2020-08-22 Thread Taylor R Campbell
[followups to tech-net to reduce cross-posting noise] Hi, Jason! Sorry about not reaching out. The history is that the code has been kicking around the NetBSD world since Ozaki-san first wrote it in 2018, without getting merged into src. It felt a shame to let it wallow in that state indefinite

Re: "wireguard" implementation improperly merged and needs revert

2020-08-22 Thread Jason Thorpe
> On Aug 22, 2020, at 11:35 AM, Jason A. Donenfeld wrote: > > it needs to be done right, Can you be specific about what is wrong? -- thorpej

Re: wait(2) and SIGCHLD

2020-08-22 Thread Rhialto
On Sat 15 Aug 2020 at 19:57:26 -0400, Terry Moore wrote: > David Holland wrote: > >> I would say so, especially since that would mean the child's parent is > > > no longer the process that forked it (which could break other use > >> cases). > > > > That depends on how you implement detaching, but