All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Davide Caratti <dcaratti@redhat.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
	davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] two fixes for the fq_pie scheduler
Date: Mon, 24 May 2021 00:20:09 +0000	[thread overview]
Message-ID: <162181560979.26786.13116118895081737886.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1621687869.git.dcaratti@redhat.com>

Hello:

This series was applied to netdev/net.git (refs/heads/master):

On Sat, 22 May 2021 15:14:33 +0200 you wrote:
> - patch 1/2 restores the possibility to use 65536 flows with fq_pie,
>   preserving the fix for an endless loop in the control plane
> - patch 2/2 fixes an OOB access that can be observed in the traffic
>   path of fq_pie scheduler, when the classification selects a flow
>   beyond the allocated space.
> 
> 
> [...]

Here is the summary with links:
  - [net,1/2] net/sched: fq_pie: re-factor fix for fq_pie endless loop
    https://git.kernel.org/netdev/net/c/3a62fed2fd7b
  - [net,2/2] net/sched: fq_pie: fix OOB access in the traffic path
    https://git.kernel.org/netdev/net/c/e70f7a11876a

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-05-24  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 13:14 [PATCH net 0/2] two fixes for the fq_pie scheduler Davide Caratti
2021-05-22 13:14 ` [PATCH net 1/2] net/sched: fq_pie: re-factor fix for fq_pie endless loop Davide Caratti
2021-05-22 13:15 ` [PATCH net 2/2] net/sched: fq_pie: fix OOB access in the traffic path Davide Caratti
2021-05-24  0:20 ` 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=162181560979.26786.13116118895081737886.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --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.