From: Jakub Kicinski <kuba@kernel.org>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Lorenzo Bianconi <lorenzo@kernel.org>
Cc: netdev@vger.kernel.org, edumazet@google.com, brouer@redhat.com,
intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
davem@davemloft.net, magnus.karlsson@intel.com
Subject: Re: [Intel-wired-lan] [PATCH net] igb: fix a use-after-free issue in igb_clean_tx_ring
Date: Fri, 17 Jun 2022 20:30:42 -0700 [thread overview]
Message-ID: <20220617203042.33d3a124@kernel.org> (raw)
In-Reply-To: <20220617201644.368bab1b@kernel.org>
On Fri, 17 Jun 2022 20:16:44 -0700 Jakub Kicinski wrote:
> It got marked as Awaiting Upstream so the bot won't respond.
Ooo, the bot got changed!
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Lorenzo Bianconi <lorenzo@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com,
brouer@redhat.com, anthony.l.nguyen@intel.com,
edumazet@google.com, intel-wired-lan@lists.osuosl.org,
lorenzo.bianconi@redhat.com, magnus.karlsson@intel.com,
sven.auhagen@voleatech.de
Subject: Re: [PATCH net] igb: fix a use-after-free issue in igb_clean_tx_ring
Date: Fri, 17 Jun 2022 20:30:42 -0700 [thread overview]
Message-ID: <20220617203042.33d3a124@kernel.org> (raw)
In-Reply-To: <20220617201644.368bab1b@kernel.org>
On Fri, 17 Jun 2022 20:16:44 -0700 Jakub Kicinski wrote:
> It got marked as Awaiting Upstream so the bot won't respond.
Ooo, the bot got changed!
next prev parent reply other threads:[~2022-06-18 3:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 14:13 [Intel-wired-lan] [PATCH net] igb: fix a use-after-free issue in igb_clean_tx_ring Lorenzo Bianconi
2022-06-16 14:13 ` Lorenzo Bianconi
2022-06-16 18:26 ` [Intel-wired-lan] " Jesse Brandeburg
2022-06-16 18:26 ` Jesse Brandeburg
2022-06-17 14:36 ` [Intel-wired-lan] " Jesper Dangaard Brouer
2022-06-17 14:36 ` Jesper Dangaard Brouer
2022-06-18 3:16 ` [Intel-wired-lan] " Jakub Kicinski
2022-06-18 3:16 ` Jakub Kicinski
2022-06-18 3:30 ` Jakub Kicinski [this message]
2022-06-18 3:30 ` Jakub Kicinski
2022-06-18 3:20 ` [Intel-wired-lan] " patchwork-bot+netdevbpf
2022-06-18 3:20 ` patchwork-bot+netdevbpf
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=20220617203042.33d3a124@kernel.org \
--to=kuba@kernel.org \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jbrouer@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=lorenzo@kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.