netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: syzbot+f0bbb2287b8993d4fa74@syzkaller.appspotmail.com,
	jhs@mojatatu.com, jiri@resnulli.us, kuba@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, xiyou.wangcong@gmail.com
Subject: Re: memory leak in tcindex_set_parms
Date: Tue, 04 Feb 2020 22:22:45 +0100 (CET)	[thread overview]
Message-ID: <20200204.222245.1920371518669295397.davem@davemloft.net> (raw)
In-Reply-To: <a1673e4f-6382-d7df-6942-6e4ffd2b81ce@gmail.com>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 4 Feb 2020 10:03:16 -0800

> 
> 
> On 2/4/20 9:58 AM, syzbot wrote:
>> Hello,
>> 
>> syzbot found the following crash on:
>> 
>> HEAD commit:    322bf2d3 Merge branch 'for-5.6' of git://git.kernel.org/pu..
>> git tree:       upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=1111f8e6e00000
>> kernel config:  https://syzkaller.appspot.com/x/.config?x=8d0490614a000a37
>> dashboard link: https://syzkaller.appspot.com/bug?extid=f0bbb2287b8993d4fa74
>> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
>> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17db90f6e00000
>> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13a94511e00000
>> 
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by: syzbot+f0bbb2287b8993d4fa74@syzkaller.appspotmail.com
>> 
>>
> 
> Might have been fixed already ?
> 
> commit 599be01ee567b61f4471ee8078870847d0a11e8e    net_sched: fix an OOB access in cls_tcindex

My reaction was actually that this bug is caused by this commit :)

  reply	other threads:[~2020-02-04 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 17:58 memory leak in tcindex_set_parms syzbot
2020-02-04 18:03 ` Eric Dumazet
2020-02-04 21:22   ` David Miller [this message]
2020-02-04 22:26     ` Cong Wang
2020-02-04 23:40       ` Eric Dumazet
2020-02-05  0:41         ` Cong Wang

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=20200204.222245.1920371518669295397.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+f0bbb2287b8993d4fa74@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).