[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAeHK+xwrXTsgKpXKbJJXeneXeh2eLhYegdPbJYEJH3sD6Ld5A@mail.gmail.com>
Date: Thu, 1 Feb 2018 15:34:56 +0100
From: Andrey Konovalov <andreyknvl@...gle.com>
To: Eric Biggers <ebiggers3@...il.com>
Cc: syzbot
<bot+944a064dbc165044476317df06ebfb218415e951@...kaller.appspotmail.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>,
Deepa Dinamani <deepa.kernel@...il.com>, gscrivan@...hat.com,
Herbert Xu <herbert@...dor.apana.org.au>,
LKML <linux-kernel@...r.kernel.org>, luc.vanoostenryck@...il.com,
Ingo Molnar <mingo@...nel.org>,
netdev <netdev@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Steffen Klassert <steffen.klassert@...unet.com>,
syzkaller-bugs@...glegroups.com,
Alexander Viro <viro@...iv.linux.org.uk>,
Cong Wang <xiyou.wangcong@...il.com>
Subject: Re: WARNING in refcount_inc (2)
On Wed, Jan 31, 2018 at 8:27 AM, Eric Biggers <ebiggers3@...il.com> wrote:
>
> Also Dmitry, syzbot seems to be grouping together unrelated bugs under the
> refcount_t WARNINGs; maybe those should be on a blacklist?
Not a blacklist, we need a proper way of extracting the offending
caller like it's done for reports from __this_cpu_* [1].
[1] https://github.com/google/syzkaller/blob/master/pkg/report/linux.go#L579
Powered by blists - more mailing lists