From: Jacob Keller <jacob.e.keller@intel.com>
To: Myeonghun Pak <mhun512@gmail.com>,
Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Simon Horman <horms@kernel.org>, Ijae Kim <ae878000@gmail.com>
Subject: Re: [PATCH net-next v3] net: 8390: pcnet_cs: release PCMCIA window on setup_shmem_window() error
Date: Tue, 15 Sep 2026 16:45:22 -0700 [thread overview]
Message-ID: <706e0153-f2a9-4103-8529-2f706f9e998c@intel.com> (raw)
In-Reply-To: <20260913204104.53408-1-mhun512@gmail.com>
On 9/13/2026 1:41 PM, Myeonghun Pak wrote:
> setup_shmem_window() acquires a PCMCIA memory window using
> pcmcia_request_window(). If pcmcia_map_mem_page() or the subsequent
> ioremap() fails, the function returns without releasing the requested
> window.
>
> pcnet_config() treats shared-memory setup failure as non-fatal and falls
> back to setup_dma_config(). Probe can therefore continue while socket
> window 3 and its reserved iomem range remain unnecessarily held for the
> rest of the bound lifetime of the device. pcmcia_disable_device()
> eventually releases the window during teardown.
>
> Route error paths after a successful request through a new release label
> that calls pcmcia_release_window(). Fold the existing buffer-verification
> cleanup into the same path, keeping iounmap() before the window release
> when a mapping exists. Leave the request failure path unchanged.
>
> This issue was identified during our ongoing static-analysis research while
> reviewing kernel code.
>
> Assisted-by: OpenAI:GPT-5.6
> Co-developed-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
> Reviewed-by: Simon Horman <horms@kernel.org>
> ---
> Changes in v3:
> - Drop Fixes and stable Cc as suggested by Simon Horman.
> - Add Simon Horman's Reviewed-by tag.
>
> Link: https://lore.kernel.org/netdev/20260910231400.31919-1-mhun512@gmail.com/
>
> Changes in v2:
> - Clarify that the window remains reserved only until device teardown.
> - Make the DMA fallback and continued probe description conditional.
> - Avoid claiming that every request failure leaves no resource held.
> - Restore the surrounding indentation for the new goto statements.
>
> Link: https://lore.kernel.org/netdev/20260731161740.44955-1-mhun512@gmail.com/
> ---
Seems reasonable to me. No reason to hold that memory indefinitely.
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> drivers/net/ethernet/8390/pcnet_cs.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/8390/pcnet_cs.c b/drivers/net/ethernet/8390/pcnet_cs.c
> index 19f9c5db3..0cf3c0f3c 100644
> --- a/drivers/net/ethernet/8390/pcnet_cs.c
> +++ b/drivers/net/ethernet/8390/pcnet_cs.c
> @@ -1434,14 +1434,14 @@ static int setup_shmem_window(struct pcmcia_device *link, int start_pg,
> offset -= offset % window_size;
> ret = pcmcia_map_mem_page(link, link->resource[3], offset);
> if (ret)
> - goto failed;
> + goto release;
>
> /* Try scribbling on the buffer */
> info->base = ioremap(link->resource[3]->start,
> resource_size(link->resource[3]));
> if (unlikely(!info->base)) {
> ret = -ENOMEM;
> - goto failed;
> + goto release;
> }
>
> for (i = 0; i < (TX_PAGES<<8); i += 2)
> @@ -1452,9 +1452,8 @@ static int setup_shmem_window(struct pcmcia_device *link, int start_pg,
> pcnet_reset_8390(dev);
> if (i != (TX_PAGES<<8)) {
> iounmap(info->base);
> - pcmcia_release_window(link, link->resource[3]);
> info->base = NULL;
> - goto failed;
> + goto release;
> }
>
> ei_status.mem = info->base + offset;
> @@ -1475,6 +1474,8 @@ static int setup_shmem_window(struct pcmcia_device *link, int start_pg,
> info->flags |= USE_SHMEM;
> return 0;
>
> +release:
> + pcmcia_release_window(link, link->resource[3]);
> failed:
> return 1;
> }
next prev parent reply other threads:[~2026-09-15 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 20:41 Myeonghun Pak
2026-09-15 23:45 ` Jacob Keller [this message]
2026-09-16 0:10 ` 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=706e0153-f2a9-4103-8529-2f706f9e998c@intel.com \
--to=jacob.e.keller@intel.com \
--cc=ae878000@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mhun512@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®