Re: Syzkaller on NetBSD broken for a long time

2025-07-08 Thread Martin Husemann
On Mon, Jul 07, 2025 at 08:04:36PM +0200, Martin Husemann wrote: > On Mon, Jul 07, 2025 at 02:31:59PM +0200, Benny Siegert wrote: > > I filed https://github.com/google/syzkaller/issues/6163 for the > > investigation and added some more details there. > > I created a standalone reproducer and am in

Re: Syzkaller on NetBSD broken for a long time

2025-07-07 Thread Martin Husemann
On Mon, Jul 07, 2025 at 02:31:59PM +0200, Benny Siegert wrote: > I filed https://github.com/google/syzkaller/issues/6163 for the > investigation and added some more details there. I created a standalone reproducer and am investigating... Martin

Re: Syzkaller on NetBSD broken for a long time

2025-07-07 Thread Benny Siegert
On Mon, Jul 7, 2025 at 1:17 PM Martin Husemann wrote: > > On Mon, Jul 07, 2025 at 11:42:26AM +0200, Benny Siegert wrote: > > Warning: Permanently added '10.128.0.147' (ED25519) to the list of known > > hosts. > > SYZFAIL: posix_spawnp failed > > (errno 22: Invalid argument) > > > > Is anyone awa

Re: Syzkaller on NetBSD broken for a long time

2025-07-07 Thread Martin Husemann
On Mon, Jul 07, 2025 at 11:42:26AM +0200, Benny Siegert wrote: > Warning: Permanently added '10.128.0.147' (ED25519) to the list of known > hosts. > SYZFAIL: posix_spawnp failed > (errno 22: Invalid argument) > > Is anyone aware of this and investigating this? I bet not :-/ The posix_spwan* fu