From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org,
tariqt@nvidia.com, tglx@linutronix.de, elic@nvidia.com,
jacob.e.keller@intel.com
Subject: Re: [net-next V2 01/15] lib: cpu_rmap: Avoid use after free on rmap->obj array entries
Date: Wed, 29 Mar 2023 07:00:26 +0000 [thread overview]
Message-ID: <168007322637.11543.1690845820853149153.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230324231341.29808-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:
On Fri, 24 Mar 2023 16:13:27 -0700 you wrote:
> From: Eli Cohen <elic@nvidia.com>
>
> When calling irq_set_affinity_notifier() with NULL at the notify
> argument, it will cause freeing of the glue pointer in the
> corresponding array entry but will leave the pointer in the array. A
> subsequent call to free_irq_cpu_rmap() will try to free this entry again
> leading to possible use after free.
>
> [...]
Here is the summary with links:
- [net-next,V2,01/15] lib: cpu_rmap: Avoid use after free on rmap->obj array entries
https://git.kernel.org/netdev/net-next/c/4e0473f1060a
- [net-next,V2,02/15] lib: cpu_rmap: Use allocator for rmap entries
https://git.kernel.org/netdev/net-next/c/9821d8d4628e
- [net-next,V2,03/15] lib: cpu_rmap: Add irq_cpu_rmap_remove to complement irq_cpu_rmap_add
https://git.kernel.org/netdev/net-next/c/71f0a2478605
- [net-next,V2,04/15] net/mlx5e: Coding style fix, add empty line
https://git.kernel.org/netdev/net-next/c/b94616d9c6fd
- [net-next,V2,05/15] net/mlx5: Fix wrong comment
https://git.kernel.org/netdev/net-next/c/40a252c123c7
- [net-next,V2,06/15] net/mlx5: Modify struct mlx5_irq to use struct msi_map
https://git.kernel.org/netdev/net-next/c/235a25fe28de
- [net-next,V2,07/15] net/mlx5: Use newer affinity descriptor
https://git.kernel.org/netdev/net-next/c/bbac70c74183
- [net-next,V2,08/15] net/mlx5: Improve naming of pci function vectors
https://git.kernel.org/netdev/net-next/c/8bebfd767909
- [net-next,V2,09/15] net/mlx5: Refactor completion irq request/release code
https://git.kernel.org/netdev/net-next/c/b48a0f72bc3e
- [net-next,V2,10/15] net/mlx5: Use dynamic msix vectors allocation
https://git.kernel.org/netdev/net-next/c/3354822cde5a
- [net-next,V2,11/15] net/mlx5: Move devlink registration before mlx5_load
https://git.kernel.org/netdev/net-next/c/fe578cbb2f05
- [net-next,V2,12/15] net/mlx5: Refactor calculation of required completion vectors
https://git.kernel.org/netdev/net-next/c/1dc85133c207
- [net-next,V2,13/15] net/mlx5: Use one completion vector if eth is disabled
https://git.kernel.org/netdev/net-next/c/b637ac5db0d0
- [net-next,V2,14/15] net/mlx5: Provide external API for allocating vectors
https://git.kernel.org/netdev/net-next/c/fb0a6a268dcd
- [net-next,V2,15/15] vdpa/mlx5: Support interrupt bypassing
(no matching commit)
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-03-29 7:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 23:13 [pull request][net-next V2 00/15] mlx5 updates 2023-03-20 Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 01/15] lib: cpu_rmap: Avoid use after free on rmap->obj array entries Saeed Mahameed
2023-03-29 7:00 ` patchwork-bot+netdevbpf [this message]
2023-03-24 23:13 ` [net-next V2 02/15] lib: cpu_rmap: Use allocator for rmap entries Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 03/15] lib: cpu_rmap: Add irq_cpu_rmap_remove to complement irq_cpu_rmap_add Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 04/15] net/mlx5e: Coding style fix, add empty line Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 05/15] net/mlx5: Fix wrong comment Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 06/15] net/mlx5: Modify struct mlx5_irq to use struct msi_map Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 07/15] net/mlx5: Use newer affinity descriptor Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 08/15] net/mlx5: Improve naming of pci function vectors Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 09/15] net/mlx5: Refactor completion irq request/release code Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 10/15] net/mlx5: Use dynamic msix vectors allocation Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 11/15] net/mlx5: Move devlink registration before mlx5_load Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 12/15] net/mlx5: Refactor calculation of required completion vectors Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 13/15] net/mlx5: Use one completion vector if eth is disabled Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 14/15] net/mlx5: Provide external API for allocating vectors Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 15/15] vdpa/mlx5: Support interrupt bypassing Saeed Mahameed
2023-03-25 1:26 ` [pull request][net-next V2 00/15] mlx5 updates 2023-03-20 Saeed Mahameed
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=168007322637.11543.1690845820853149153.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elic@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).