[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+Z1G_QMG_PQu_ZwHsyhwyh_DBOG4mX9n=va08w3Z7j02Q@mail.gmail.com>
Date: Sun, 23 Sep 2018 18:22:36 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Vladis Dronov <vdronov@...hat.com>
Cc: syzbot <syzbot+d3402c47f680ff24b29c@...kaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
David Miller <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
sunlianwen <sunlw.fnst@...fujitsu.com>
Subject: Re: KMSAN: uninit-value in memcmp (2)
On Sun, Sep 23, 2018 at 6:02 PM, Vladis Dronov <vdronov@...hat.com> wrote:
> #syz fix: net: fix uninit-value in __hw_addr_add_ex()
Hi Vladis,
This can be fixed with "net: fix uninit-value in __hw_addr_add_ex()".
That commit landed in April, syzbot waited till the commit reached all
tested trees, and then closed the bug.
But the similar bug continued to happen, so syzbot created second
version of this bug (2). You can see on dashboard that the last crash
for the second version (2) happened just few days ago. So this is a
different bug.
Powered by blists - more mailing lists