From: patchwork-bot+netdevbpf@kernel.org
To: Takamitsu Iwai <takamitz@amazon.co.jp>
Cc: vinicius.gomes@intel.com, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us,
netdev@vger.kernel.org, kuniyu@google.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, olteanv@gmail.com, takamitz@amazon.com,
syzbot+398e1ee4ca2cac05fddb@syzkaller.appspotmail.com
Subject: Re: [PATCH v3 net] net/sched: taprio: enforce minimum value for picos_per_byte
Date: Sat, 02 Aug 2025 00:30:10 +0000 [thread overview]
Message-ID: <175409461025.4171186.11925448552311801964.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250728173149.45585-1-takamitz@amazon.co.jp>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 29 Jul 2025 02:31:49 +0900 you wrote:
> Syzbot reported a WARNING in taprio_get_start_time().
>
> When link speed is 470,589 or greater, q->picos_per_byte becomes too
> small, causing length_to_duration(q, ETH_ZLEN) to return zero.
>
> This zero value leads to validation failures in fill_sched_entry() and
> parse_taprio_schedule(), allowing arbitrary values to be assigned to
> entry->interval and cycle_time. As a result, sched->cycle can become zero.
>
> [...]
Here is the summary with links:
- [v3,net] net/sched: taprio: enforce minimum value for picos_per_byte
https://git.kernel.org/netdev/net/c/ae8508b25def
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:[~2025-08-02 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 17:31 [PATCH v3 net] net/sched: taprio: enforce minimum value for picos_per_byte Takamitsu Iwai
2025-07-30 17:49 ` Cong Wang
2025-07-31 19:27 ` Vinicius Costa Gomes
2025-08-02 0:30 ` 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=175409461025.4171186.11925448552311801964.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=syzbot+398e1ee4ca2cac05fddb@syzkaller.appspotmail.com \
--cc=takamitz@amazon.co.jp \
--cc=takamitz@amazon.com \
--cc=vinicius.gomes@intel.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