All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzkaller@googlegroups.com, glider@google.com,
	vinicius.gomes@intel.com
Subject: Re: [PATCH net] net/sched: sch_taprio: fix possible use-after-free
Date: Mon, 16 Jan 2023 13:30:16 +0000	[thread overview]
Message-ID: <167387581653.2747.13878941339893288655.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230113164849.4004848-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 13 Jan 2023 16:48:49 +0000 you wrote:
> syzbot reported a nasty crash [1] in net_tx_action() which
> made little sense until we got a repro.
> 
> This repro installs a taprio qdisc, but providing an
> invalid TCA_RATE attribute.
> 
> qdisc_create() has to destroy the just initialized
> taprio qdisc, and taprio_destroy() is called.
> 
> [...]

Here is the summary with links:
  - [net] net/sched: sch_taprio: fix possible use-after-free
    https://git.kernel.org/netdev/net/c/3a415d59c1db

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



      parent reply	other threads:[~2023-01-16 13:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 16:48 [PATCH net] net/sched: sch_taprio: fix possible use-after-free Eric Dumazet
2023-01-13 23:41 ` Vinicius Costa Gomes
2023-01-16 10:03   ` Eric Dumazet
2023-01-18 11:43   ` Eric Dumazet
2023-01-16  0:35 ` Cong Wang
2023-01-16  2:07   ` shaozhengchao
2023-01-16  9:03     ` Alexander Potapenko
2023-01-16  9:36   ` Eric Dumazet
2023-01-16 13: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=167387581653.2747.13878941339893288655.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=glider@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzkaller@googlegroups.com \
    --cc=vinicius.gomes@intel.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.