From: Paolo Abeni <pabeni@redhat.com>
To: chia-yu.chang@nokia-bell-labs.com, horms@kernel.org,
donald.hunter@gmail.com, xandfury@gmail.com,
netdev@vger.kernel.org, dave.taht@gmail.com, jhs@mojatatu.com,
kuba@kernel.org, stephen@networkplumber.org,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, andrew+netdev@lunn.ch, ast@fiberby.net,
liuhangbin@gmail.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, ij@kernel.org,
ncardwell@google.com, koen.de_schepper@nokia-bell-labs.com,
g.white@cablelabs.com, ingemar.s.johansson@ericsson.com,
mirja.kuehlewind@ericsson.com, cheshire@apple.com,
rs.ietf@gmx.at, Jason_Livingood@comcast.com,
vidhi_goel@apple.com
Subject: Re: [PATCH v15 net-next 1/5] sched: Struct definition and parsing of dualpi2 qdisc
Date: Thu, 15 May 2025 10:51:20 +0200 [thread overview]
Message-ID: <44cd376a-8fee-4d82-a465-a0e80e67135c@redhat.com> (raw)
In-Reply-To: <20250509214801.37306-2-chia-yu.chang@nokia-bell-labs.com>
On 5/9/25 11:47 PM, chia-yu.chang@nokia-bell-labs.com wrote:
> +struct dualpi2_sched_data {
> + struct Qdisc *l_queue; /* The L4S Low latency queue (L-queue) */
> + struct Qdisc *sch; /* The Classic queue (C-queue) */
> +
> + /* Registered tc filters */
> + struct tcf_proto __rcu *tcf_filters;
> + struct tcf_block *tcf_block;
> +
> + /* PI2 parameters */
> + u64 pi2_target; /* Target delay in nanoseconds */
> + u32 pi2_tupdate; /* Timer frequency in nanoseconds */
AFAICS this can be written from user-space, without any upper bound,
causing an integer overflow after converting the frequency from seconds
to nsec.
> +static enum hrtimer_restart dualpi2_timer(struct hrtimer *timer)
> +{
> + struct dualpi2_sched_data *q = from_timer(q, timer, pi2_timer);
> +
> + WRITE_ONCE(q->pi2_prob, calculate_probability(q->sch));
This runs without acquiring the qdisc_lock(). The state accessed by
calculate_probability() could be inconsistent. You likely need to
acquire the qdisc_lock here.
/P
next prev parent reply other threads:[~2025-05-15 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 21:47 [PATCH v15 net-next 0/5] DUALPI2 patch chia-yu.chang
2025-05-09 21:47 ` [PATCH v15 net-next 1/5] sched: Struct definition and parsing of dualpi2 qdisc chia-yu.chang
2025-05-15 8:51 ` Paolo Abeni [this message]
2025-05-15 9:07 ` Paolo Abeni
2025-05-09 21:47 ` [PATCH v15 net-next 2/5] sched: Dump configuration and statistics " chia-yu.chang
2025-05-15 9:12 ` Paolo Abeni
2025-05-09 21:47 ` [PATCH v15 net-next 3/5] sched: Add enqueue/dequeue " chia-yu.chang
2025-05-09 21:48 ` [PATCH v15 net-next 4/5] selftests/tc-testing: Add selftests for qdisc DualPI2 chia-yu.chang
2025-05-09 21:48 ` [PATCH v15 net-next 5/5] Documentation: netlink: specs: tc: Add DualPI2 specification chia-yu.chang
2025-05-15 8:04 ` [PATCH v15 net-next 0/5] DUALPI2 patch Paolo Abeni
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=44cd376a-8fee-4d82-a465-a0e80e67135c@redhat.com \
--to=pabeni@redhat.com \
--cc=Jason_Livingood@comcast.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@fiberby.net \
--cc=cheshire@apple.com \
--cc=chia-yu.chang@nokia-bell-labs.com \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=g.white@cablelabs.com \
--cc=horms@kernel.org \
--cc=ij@kernel.org \
--cc=ingemar.s.johansson@ericsson.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=koen.de_schepper@nokia-bell-labs.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=mirja.kuehlewind@ericsson.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=rs.ietf@gmx.at \
--cc=shuah@kernel.org \
--cc=stephen@networkplumber.org \
--cc=vidhi_goel@apple.com \
--cc=xandfury@gmail.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).