From: syzbot <syzbot+2f9183cb6f89b0e16586@syzkaller.appspotmail.com>
To: chenzhongjin@huawei.com, davem@davemloft.net,
edumazet@google.com, gregkh@linuxfoundation.org,
jhs@mojatatu.com, jiri@resnulli.us, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, stable@vger.kernel.org,
syzkaller-bugs@googlegroups.com, xiyou.wangcong@gmail.com
Subject: Re: [syzbot] memory leak in tcindex_set_parms (3)
Date: Thu, 08 Dec 2022 03:06:17 -0800 [thread overview]
Message-ID: <000000000000afe93f05ef4f063a@google.com> (raw)
In-Reply-To: <20221208032216.63513-1-chenzhongjin@huawei.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+2f9183cb6f89b0e16586@syzkaller.appspotmail.com
Tested on:
commit: 355479c7 Merge tag 'efi-fixes-for-v6.1-4' of git://git..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=175b5b23880000
kernel config: https://syzkaller.appspot.com/x/.config?x=979161df0e247659
dashboard link: https://syzkaller.appspot.com/bug?extid=2f9183cb6f89b0e16586
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=142313f3880000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2022-12-08 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 3:22 [PATCH net] net/sched: Fix memory leak in tcindex_set_parms Chen Zhongjin
2022-12-08 6:35 ` Chen Zhongjin
2022-12-08 11:06 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-06 19:09 [syzbot] memory leak in tcindex_set_parms (3) syzbot
2022-12-07 7:19 ` Wangshaobo (bobo)
2023-04-02 6:07 ` 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=000000000000afe93f05ef4f063a@google.com \
--to=syzbot+2f9183cb6f89b0e16586@syzkaller.appspotmail.com \
--cc=chenzhongjin@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.