Message ID | 20220411114119.e8c4e465da8e.I47453169065a52e80433b529073726a3c5855194@changeid |
---|---|
State | Accepted |
Headers | show |
Series | tests: vm: pretend the RNG is initialized | expand |
On Mon, Apr 11, 2022 at 11:41:20AM +0200, Johannes Berg wrote: > We don't particularly care about the quality of random numbers > during the test. So far, there hasn't been an issue with the > RNG not being initialized completely, we only get a few prints > about uninitialized reads from urandom. However, if some tool > were to actually use /dev/random, it might get stuck. Call the > RNDADDTOENTCNT ioctl to unblock this. Thanks, applied.
diff --git a/tests/hwsim/vm/inside.sh b/tests/hwsim/vm/inside.sh index bfcbda631e4f..f0a0d9bf3b9f 100755 --- a/tests/hwsim/vm/inside.sh +++ b/tests/hwsim/vm/inside.sh @@ -53,6 +53,11 @@ ln -s /proc/self/fd/0 /dev/stdin ln -s /proc/self/fd/1 /dev/stdout ln -s /proc/self/fd/2 /dev/stderr +# pretend we've initialized the RNG, we don't care here +# about the actual quality of the randomness. The ioctl +# is RNDADDTOENTCNT (at least on x86). +PYTHONHASHSEED=0 python3 -c 'import fcntl; fd=open("/dev/random", "w"); fcntl.ioctl(fd.fileno(), 0x40045201, b"\x00\x01\x00\x00")' + echo "VM has started up" > /dev/ttyS0 # create stub sudo - everything runs as uid 0