Re: KMSAN: uninit-value in __crypto_memneq (2)

2021-02-21 Thread Dmitry Vyukov
On Sat, Jan 9, 2021 at 6:33 PM Dmitry Vyukov wrote: > > On Sat, Jan 9, 2021 at 6:14 PM Eric Biggers wrote: > > > > +Jason, since this looks WireGuard-related. > > I suspect that the uninit was created by geneve or batadv and then > just handed off to wireguard, which couldn't deal with it at

Re: KMSAN: uninit-value in __crypto_memneq (2)

2021-01-09 Thread Dmitry Vyukov
On Sat, Jan 9, 2021 at 6:14 PM Eric Biggers wrote: > > +Jason, since this looks WireGuard-related. I suspect that the uninit was created by geneve or batadv and then just handed off to wireguard, which couldn't deal with it at that point. > On Sat, Jan 09, 2021 at 05:05:24AM -0800, syzbot

Re: KMSAN: uninit-value in __crypto_memneq (2)

2021-01-09 Thread Eric Biggers
+Jason, since this looks WireGuard-related. On Sat, Jan 09, 2021 at 05:05:24AM -0800, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit:73d62e81 kmsan: random: prevent boot-time reports in _mix_.. > git tree: https://github.com/google/kmsan.git master >

KMSAN: uninit-value in __crypto_memneq (2)

2021-01-09 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:73d62e81 kmsan: random: prevent boot-time reports in _mix_.. git tree: https://github.com/google/kmsan.git master console output: https://syzkaller.appspot.com/x/log.txt?x=142ab9c0d0 kernel config: