please ignore the above, it was meant to be sent to #1069310 instead On Mon, May 6, 2024 at 6:34 AM Reinhard Tartler <siret...@gmail.com> wrote:
> I spent about half an hour looking at this, and wanted to share my > thoughts: > > - the build / tests succeed on all architectures but mips64el > - the panic in question appears to come from here: > https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13 > -- a map[int64]string is being set with the key "syscall.O_DIRECT" to the > value "DIRECT". > - that map is pre-initialized here: > https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L64-L80 > - on most architectures, such as amd64, the constant `syscall.O_DIRECT` is > set to the value 0x4000, cf. > https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_amd64.go;l=627;bpv=0;bpt=1 > - on mipsel64, the value is set to 0x8000, cf. > https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_mips64.go;l=774?q=O_DIRECT&ss=go%2Fgo&start=11 > - this value conflicts with > https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L77 > so we now get conflicting values for the same key. This explains the > message "panic: DIRECT (8000) overlaps with LARGEFILE (8000). > > > -- > regards, > Reinhard > -- regards, Reinhard
