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.
- Re: KASAN: use-after-free Read in tcf_block_find Eric Dumazet
- Re: KASAN: use-after-free Read in tcf_block_find Dmitry Vyukov
- Re: KASAN: use-after-free Read in tcf_block_find Eric Dumazet
- Re: KASAN: use-after-free Read in tcf_block_fin... Dmitry Vyukov
- Re: KASAN: use-after-free Read in tcf_block_find Cong Wang
- Re: KASAN: use-after-free Read in tcf_block_find Dmitry Vyukov