From: patchwork-bot+netdevbpf@kernel.org
To: Ruoyu Wang <ruoyuw560@gmail.com>
Cc: khc@pm.waw.pl, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] wan: wanxl: Only reset hardware after BAR mapping
Date: Tue, 21 Jul 2026 11:20:06 +0000 [thread overview]
Message-ID: <178463280640.237147.335286475786801784.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260708143415.3169358-1-ruoyuw560@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 8 Jul 2026 22:34:15 +0800 you wrote:
> wanxl_pci_init_one() stores the freshly allocated card in driver data
> before the PLX BAR is mapped. Several early probe failures then unwind
> through wanxl_pci_remove_one(), including failure to allocate the coherent
> status area or to restore the DMA mask.
>
> wanxl_pci_remove_one() unconditionally calls wanxl_reset(), and
> wanxl_reset() dereferences card->plx. On those early failures card->plx
> is still NULL, so the error path can dereference a NULL MMIO pointer.
>
> [...]
Here is the summary with links:
- [net] wan: wanxl: Only reset hardware after BAR mapping
https://git.kernel.org/netdev/net/c/91957b89da99
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-21 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 14:34 [PATCH net] wan: wanxl: Only reset hardware after BAR mapping Ruoyu Wang
2026-07-21 11:20 ` 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=178463280640.237147.335286475786801784.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=khc@pm.waw.pl \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ruoyuw560@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox