Breakage in recent linux

[queenp]

Hi there, thanks for writing this awesome wrapper package.

I've just recently started having an issue, where I get the following output running the demo candump app

$ go run cmd/candump.go -if vcan0
2018/09/19 03:37:16 invalid argument
exit status 1

I traced the error down to the call to syscall.Bind() in NewReadWriteCloserForInterface, but I'm not familiar enough with the relationship between the golang syscall package and the C end to take that gap any further. It's possible that this is actually a lower level issue in the go stack, but I figured I'd come here first just in case.

The kernel version on the vm it broke for:

$ uname -a
Linux kali 4.17.0-kali3-amd64 #1 SMP Debian 4.17.17-1kali1 (2018-08-21) x86_64 GNU/Linux

(Just for reference, I've confirmed multiple times including with the socketcan C based canplayer/candump executables that my vcan socket is definitely present and up and functional).

[brutella]

Which version of Go are using?

[brutella]

Maybe we have to change the binding to this.
(Currently I don't have time to look into it.)

[queenp]

I'll spend some more time looking into it and fire over a PR if I get it sorted, thanks for responding.

…

On Fri, 28 Sep 2018, 11:54 Matthias, ***@***.***> wrote: Maybe we have to change the binding to this <https://github.com/golang/sys/blob/master/unix/syscall_linux.go#L541-L546> . (Currently I don't have time to look into it.) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2KuZZ_68eOeer3EsHaFn3S3MXkkvPEks5uff_dgaJpZM4WvTyB> .

[brutella]

I've added a possible fix in the fix-linux branch.