[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACT4Y+bjFj6-G_WxetFzmWfppjZLOXHk2G2m_XfEZpC3h4k0Tw@mail.gmail.com>
Date: Fri, 27 Oct 2017 11:43:17 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Xin Long <lucien.xin@...il.com>, ChunYu Wang <chunwang@...hat.com>,
syzbot
<bot+a004c8dcbae7c160bf1bbd6e6af2e9cf4fa54f84@...kaller.appspotmail.com>,
David Miller <davem@...emloft.net>,
LKML <linux-kernel@...r.kernel.org>, linux-sctp@...r.kernel.org,
netdev <netdev@...r.kernel.org>,
Neil Horman <nhorman@...driver.com>,
syzkaller-bugs@...glegroups.com,
Vladislav Yasevich <vyasevich@...il.com>
Subject: Re: WARNING in refcount_sub_and_test
On Fri, Oct 27, 2017 at 11:36 AM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> On Fri, 2017-10-27 at 08:09 +0200, Dmitry Vyukov wrote:
>
>> Yes, I've noticed this one. It seems to happen on a first incoming
>> network connection (ssh/scp). I have not seen it before.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=timers/core&id=52f737c2da40259ac9962170ce608b6fb1b55ee4
>
> ( Google-Bug-Id: 68003409 )
Good!
I've noticed that it does not happen on latest Linus tree, now I know why.
Powered by blists - more mailing lists