All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, andrew+netdev@lunn.ch,
	netdev@vger.kernel.org
Subject: Re: [PATCH net 0/8][pull request] Intel Wired LAN Driver Updates 2025-09-02 (ice, idpf, i40e, ixgbe, e1000e)
Date: Wed, 03 Sep 2025 23:40:13 +0000	[thread overview]
Message-ID: <175694281353.1237656.2000761863886349636.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250902232131.2739555-1-anthony.l.nguyen@intel.com>

Hello:

This series was applied to netdev/net.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:

On Tue,  2 Sep 2025 16:21:20 -0700 you wrote:
> For ice:
> Jake adds checks for initialization of Tx timestamp tracking structure
> to prevent NULL pointer dereferences.
> 
> For idpf:
> Josh moves freeing of auxiliary device id to prevent use-after-free issue.
> 
> [...]

Here is the summary with links:
  - [net,1/8] ice: fix NULL access of tx->in_use in ice_ptp_ts_irq
    https://git.kernel.org/netdev/net/c/403bf043d934
  - [net,2/8] ice: fix NULL access of tx->in_use in ice_ll_ts_intr
    https://git.kernel.org/netdev/net/c/f6486338fde3
  - [net,3/8] idpf: fix UAF in RDMA core aux dev deinitialization
    https://git.kernel.org/netdev/net/c/65637c3a1811
  - [net,4/8] idpf: set mac type when adding and removing MAC filters
    https://git.kernel.org/netdev/net/c/acf3a5c8be80
  - [net,5/8] i40e: remove read access to debugfs files
    https://git.kernel.org/netdev/net/c/9fcdb1c3c4ba
  - [net,6/8] i40e: Fix potential invalid access when MAC list is empty
    https://git.kernel.org/netdev/net/c/a556f06338e1
  - [net,7/8] ixgbe: fix incorrect map used in eee linkmode
    https://git.kernel.org/netdev/net/c/b7e5c3e3bfa9
  - [net,8/8] e1000e: fix heap overflow in e1000_set_eeprom
    https://git.kernel.org/netdev/net/c/90fb7db49c6d

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



      parent reply	other threads:[~2025-09-03 23:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 23:21 [PATCH net 0/8][pull request] Intel Wired LAN Driver Updates 2025-09-02 (ice, idpf, i40e, ixgbe, e1000e) Tony Nguyen
2025-09-02 23:21 ` [PATCH net 1/8] ice: fix NULL access of tx->in_use in ice_ptp_ts_irq Tony Nguyen
2025-09-02 23:21 ` [PATCH net 2/8] ice: fix NULL access of tx->in_use in ice_ll_ts_intr Tony Nguyen
2025-09-02 23:21 ` [PATCH net 3/8] idpf: fix UAF in RDMA core aux dev deinitialization Tony Nguyen
2025-09-02 23:21 ` [PATCH net 4/8] idpf: set mac type when adding and removing MAC filters Tony Nguyen
2025-09-02 23:21 ` [PATCH net 5/8] i40e: remove read access to debugfs files Tony Nguyen
2025-09-02 23:21 ` [PATCH net 6/8] i40e: Fix potential invalid access when MAC list is empty Tony Nguyen
2025-09-02 23:21 ` [PATCH net 7/8] ixgbe: fix incorrect map used in eee linkmode Tony Nguyen
2025-09-02 23:21 ` [PATCH net 8/8] e1000e: fix heap overflow in e1000_set_eeprom Tony Nguyen
2025-09-03 23:40 ` 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=175694281353.1237656.2000761863886349636.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --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.