From: patchwork-bot+netdevbpf@kernel.org
To: Du Cheng <ducheng2@gmail.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
netdev@vger.kernel.org, skhan@linuxfoundation.org,
gregkh@linuxfoundation.org, eric.dumazet@gmail.com,
syzbot+d50710fd0873a9c6b40c@syzkaller.appspotmail.com
Subject: Re: [PATCH v4] net: sched: tapr: prevent cycle_time == 0 in parse_taprio_schedule
Date: Mon, 19 Apr 2021 22:40:09 +0000 [thread overview]
Message-ID: <161887200958.19818.10568820283791492526.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210416233046.12399-1-ducheng2@gmail.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Sat, 17 Apr 2021 07:30:46 +0800 you wrote:
> There is a reproducible sequence from the userland that will trigger a WARN_ON()
> condition in taprio_get_start_time, which causes kernel to panic if configured
> as "panic_on_warn". Catch this condition in parse_taprio_schedule to
> prevent this condition.
>
> Reported as bug on syzkaller:
> https://syzkaller.appspot.com/bug?extid=d50710fd0873a9c6b40c
>
> [...]
Here is the summary with links:
- [v4] net: sched: tapr: prevent cycle_time == 0 in parse_taprio_schedule
https://git.kernel.org/netdev/net/c/ed8157f1ebf1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-04-19 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 23:30 [PATCH v4] net: sched: tapr: prevent cycle_time == 0 in parse_taprio_schedule Du Cheng
2021-04-19 19:19 ` Cong Wang
2021-04-19 22:40 ` patchwork-bot+netdevbpf [this message]
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=161887200958.19818.10568820283791492526.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ducheng2@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+d50710fd0873a9c6b40c@syzkaller.appspotmail.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).