From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, jiri@resnulli.us,
xiyou.wangcong@gmail.com, syzkaller-bugs@googlegroups.com,
linux-kernel@vger.kernel.org, shaozhengchao@huawei.com,
syzbot+a3618a167af2021433cd@syzkaller.appspotmail.com,
vladimir.oltean@nxp.com, victor@mojatatu.com,
pctammela@mojatatu.com
Subject: Re: [PATCH net v2 1/1] net/sched: fix a qdisc modification with ambiguous command request
Date: Wed, 23 Aug 2023 08:50:21 +0000 [thread overview]
Message-ID: <169278062189.13745.3034926060241116473.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230822101231.74388-1-jhs@mojatatu.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 22 Aug 2023 06:12:31 -0400 you wrote:
> When replacing an existing root qdisc, with one that is of the same kind, the
> request boils down to essentially a parameterization change i.e not one that
> requires allocation and grafting of a new qdisc. syzbot was able to create a
> scenario which resulted in a taprio qdisc replacing an existing taprio qdisc
> with a combination of NLM_F_CREATE, NLM_F_REPLACE and NLM_F_EXCL leading to
> create and graft scenario.
> The fix ensures that only when the qdisc kinds are different that we should
> allow a create and graft, otherwise it goes into the "change" codepath.
>
> [...]
Here is the summary with links:
- [net,v2,1/1] net/sched: fix a qdisc modification with ambiguous command request
https://git.kernel.org/netdev/net/c/da71714e359b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-08-23 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 10:12 [PATCH net v2 1/1] net/sched: fix a qdisc modification with ambiguous command request Jamal Hadi Salim
2023-08-23 8:50 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-21 19:13 Jamal Hadi Salim
2023-08-22 7:48 ` Simon Horman
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=169278062189.13745.3034926060241116473.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=shaozhengchao@huawei.com \
--cc=syzbot+a3618a167af2021433cd@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=victor@mojatatu.com \
--cc=vladimir.oltean@nxp.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