All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Thinh Tran <thinhtr@linux.ibm.com>
Cc: jacob.e.keller@intel.com, kuba@kernel.org,
	netdev@vger.kernel.org, VENKATA.SAI.DUGGI@ibm.com,
	abdhalee@in.ibm.com, aelior@marvell.com, davem@davemloft.net,
	drc@linux.vnet.ibm.com, edumazet@google.com, manishc@marvell.com,
	pabeni@redhat.com, simon.horman@corigine.com,
	skalluru@marvell.com
Subject: Re: [PATCH v11] net/bnx2x: Prevent access to a freed page in page_pool
Date: Wed, 20 Mar 2024 03:10:28 +0000	[thread overview]
Message-ID: <171090422871.19504.16129773459568231603.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240315205535.1321-1-thinhtr@linux.ibm.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 15 Mar 2024 15:55:35 -0500 you wrote:
> Fix race condition leading to system crash during EEH error handling
> 
> During EEH error recovery, the bnx2x driver's transmit timeout logic
> could cause a race condition when handling reset tasks. The
> bnx2x_tx_timeout() schedules reset tasks via bnx2x_sp_rtnl_task(),
> which ultimately leads to bnx2x_nic_unload(). In bnx2x_nic_unload()
> SGEs are freed using bnx2x_free_rx_sge_range(). However, this could
> overlap with the EEH driver's attempt to reset the device using
> bnx2x_io_slot_reset(), which also tries to free SGEs. This race
> condition can result in system crashes due to accessing freed memory
> locations in bnx2x_free_rx_sge()
> 
> [...]

Here is the summary with links:
  - [v11] net/bnx2x: Prevent access to a freed page in page_pool
    https://git.kernel.org/netdev/net/c/d27e2da94a42

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



      parent reply	other threads:[~2024-03-20  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 20:55 [PATCH v11] net/bnx2x: Prevent access to a freed page in page_pool Thinh Tran
2024-03-18 11:46 ` Jiri Pirko
2024-03-20  3:10 ` 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=171090422871.19504.16129773459568231603.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=VENKATA.SAI.DUGGI@ibm.com \
    --cc=abdhalee@in.ibm.com \
    --cc=aelior@marvell.com \
    --cc=davem@davemloft.net \
    --cc=drc@linux.vnet.ibm.com \
    --cc=edumazet@google.com \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=manishc@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.com \
    --cc=skalluru@marvell.com \
    --cc=thinhtr@linux.ibm.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.