diff options
| author | Jakob Unterwurzacher | 2023-09-15 23:11:58 +0200 |
|---|---|---|
| committer | Jakob Unterwurzacher | 2023-09-15 23:19:02 +0200 |
| commit | 3a65627316cb4d1c360ece87ec9a33e4c330d1aa (patch) | |
| tree | 6a35d9b9d2b7fa6cf3f97ba28b9785e3eca00838 /fsck.go | |
| parent | 7fff33a1e2560c8f4eb1f477c1e220eeb14291ab (diff) | |
gocryptfs -speed: call testing.Init() to not panic
Looks like I should have been calling testing.Init()
all along. From https://pkg.go.dev/testing#Init :
> Init is only needed when calling functions such as
> Benchmark without using "go test".
Panic only affected without_openssl builds and looks
like this:
$ ./gocryptfs -speed
gocryptfs v2.4.0-2-g8b1c4b0-dirty without_openssl; go-fuse v2.3.0; 2023-09-15 go1.21.1 linux/amd64
cpu: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz; with AES acceleration
AES-GCM-256-OpenSSL panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x5a5d20]
goroutine 7 [running]:
testing.(*common).decorate(0x40d625?, {0xc00001c150, 0x2a}, 0x830601?)
testing/testing.go:772 +0xa0
[...]
Fixes: https://github.com/rfjakob/gocryptfs/issues/789
Relates-to: https://github.com/golang/go/issues/62666
Diffstat (limited to 'fsck.go')
0 files changed, 0 insertions, 0 deletions