[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+Z24_ak+42mUGxMWBcBdXFYXFGKomPe0QzFUX+YSSkV+Q@mail.gmail.com>
Date: Thu, 27 Sep 2018 15:42:45 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Cong Wang <xiyou.wangcong@...il.com>,
syzbot+37b8770e6d5a8220a039@...kaller.appspotmail.com,
David Miller <davem@...emloft.net>,
Jamal Hadi Salim <jhs@...atatu.com>,
Jiri Pirko <jiri@...nulli.us>,
LKML <linux-kernel@...r.kernel.org>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: KASAN: use-after-free Read in tcf_block_find
On Thu, Sep 27, 2018 at 3:24 PM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> On 09/27/2018 06:02 AM, Dmitry Vyukov wrote:
>
>> I am not suggesting to commit this. This is just a hack for debugging.
>> It in fact lead to some warnings, but still allowed me to reproduce
>> the bug reliably.
>>
>
> Had you got more meaningful stack traces ?
>
> (Showing which context was actually doing the dst_release())
nope... I just handed off the instructions to Wei since she said she
can't reproduce it.
>>>> + dst_destroy_rcu(&dst->rcu_head);
>>>> + }
>>>> + }
>>>> }
>>>> }
>
> Thanks.
Powered by blists - more mailing lists