Re: panic - ffs_write - AMD64/7.4 to current

2024-08-24 Thread Martin Pieuchot
Hugh, If you can reproduce this easily, please send a new panic with the outputs of: - show uvm - show bcstats - And the traces of all running processes... In the two reports below we only have the trace of pax(1) which is running on CPU2. The two panics are due to corruptions of two different g

getentropy(2) and arc4random(3) do not reseed on VM fork

2024-08-24 Thread Jonas Böttiger
Hi everyone, While implementing the new default random number generator for the Rust standard library (https://github.com/rust-lang/rust/pull/129201), I’ve noticed that OpenBSD does not appear to reseed its RNGs when a VM fork occurs or multiple VMs are resumed from the same checkpoint. This ca

Re: panic - mutex? - AMD64/7.4 to current

2024-08-24 Thread Hugh Graham
On Sat, Aug 24, 2024 at 12:13:11PM +0200, Martin Pieuchot wrote: > Hugh, > > If you can reproduce this easily, please send a new panic with the > outputs of: > - show uvm > - show bcstats > - And the traces of all running processes... In the two reports below we > only have the trace of pax(1) wh

Re: panic - mutex? - AMD64/7.4 to current

2024-08-24 Thread Hugh Graham
The machine that slowly received the ports tree crashed upon reboot, and I have included the traces. It was running 7.5-stable at the time. I will wait an hour or so, and then restart and repeat against current. /Hugh # reboot dd: /var/db/host.random: No such file or directory chmod: /var/db/host

Re: panic - mutex? - AMD64/7.4 to current

2024-08-24 Thread Martin Pieuchot
On 24/08/24(Sat) 12:09, Hugh Graham wrote: > The machine that slowly received the ports tree crashed upon reboot, > and I have included the traces. It was running 7.5-stable at the > time. I will wait an hour or so, and then restart and repeat > against current. Thanks, could you elaborate how you

Re: panic - mutex? - AMD64/7.4 to current

2024-08-24 Thread Hugh Graham
On Sat, Aug 24, 2024 at 09:31:43PM +0200, Martin Pieuchot wrote: > On 24/08/24(Sat) 12:09, Hugh Graham wrote: > > The machine that slowly received the ports tree crashed upon reboot, > > and I have included the traces. It was running 7.5-stable at the > > time. I will wait an hour or so, and then r

Re: getentropy(2) and arc4random(3) do not reseed on VM fork

2024-08-24 Thread Bryan Stenson
I've not tested this, but I wonder if adding unique entropy to each unique VM (post boot) would address this concern: https://man.openbsd.org/arc4random.9#enqueue_randomness On Saturday, August 24, 2024, Jonas Böttiger wrote: > Hi everyone, > > While implementing the new default random number g