From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
syzbot+37b8770e6d5a8220a039@syzkaller.appspotmail.com,
David Miller <davem@davemloft.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Jiri Pirko <jiri@resnulli.us>,
LKML <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: use-after-free Read in tcf_block_find
Date: Thu, 27 Sep 2018 06:24:06 -0700 [thread overview]
Message-ID: <10a02f06-2e6c-e70b-2766-012a835d3a57@gmail.com> (raw)
In-Reply-To: <CACT4Y+ZvoVsL_BjBWr7QPnXOPGXqkqKfo-NQcox7vaAFPWVUVg@mail.gmail.com>
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())
>>> + dst_destroy_rcu(&dst->rcu_head);
>>> + }
>>> + }
>>> }
>>> }
Thanks.
next prev parent reply other threads:[~2018-09-27 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 15:44 KASAN: use-after-free Read in tcf_block_find syzbot
2018-09-26 21:44 ` Cong Wang
2018-09-26 21:50 ` Eric Dumazet
2018-09-26 21:55 ` Cong Wang
2018-09-27 8:06 ` Dmitry Vyukov
2018-09-27 8:10 ` Dmitry Vyukov
2018-09-27 13:00 ` Eric Dumazet
2018-09-27 13:02 ` Dmitry Vyukov
2018-09-27 13:24 ` Eric Dumazet [this message]
2018-09-27 13:42 ` Dmitry Vyukov
2018-09-27 17:50 ` Cong Wang
2018-09-27 18:04 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10a02f06-2e6c-e70b-2766-012a835d3a57@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+37b8770e6d5a8220a039@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).