From: Bastien Curutchet <bastien.curutchet@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Woojung Huh" <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, "Andrew Lunn" <andrew@lunn.ch>,
"Vladimir Oltean" <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Richard Cochran" <richardcochran@gmail.com>,
"Arun Ramadoss" <arun.ramadoss@microchip.com>,
"Pascal Eberhard" <pascal.eberhard@se.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 3/4] net: dsa: microchip: Ensure a ksz_irq is initialized before freeing it
Date: Wed, 12 Nov 2025 08:44:06 +0100 [thread overview]
Message-ID: <91ee0772-b166-4556-9c9e-e12fa0262088@bootlin.com> (raw)
In-Reply-To: <20251110182839.3dfb68bf@kernel.org>
Hi Jakub,
On 11/11/25 3:28 AM, Jakub Kicinski wrote:
> On Thu, 06 Nov 2025 13:53:10 +0100 Bastien Curutchet (Schneider
> Electric) wrote:
>> diff --git a/drivers/net/dsa/microchip/ksz_common.c b/drivers/net/dsa/microchip/ksz_common.c
>> index 3a4516d32aa5f99109853ed400e64f8f7e2d8016..4f5e2024442692adefc69d47e82381a3c3bda184 100644
>> --- a/drivers/net/dsa/microchip/ksz_common.c
>> +++ b/drivers/net/dsa/microchip/ksz_common.c
>> @@ -2858,14 +2858,16 @@ static void ksz_irq_free(struct ksz_irq *kirq)
>> {
>> int irq, virq;
>>
>> - free_irq(kirq->irq_num, kirq);
>> + if (kirq->irq_num)
>> + free_irq(kirq->irq_num, kirq);
>>
>> for (irq = 0; irq < kirq->nirqs; irq++) {
>
> if the domain may not be registered is it okay to try to find mappings
> in it? From the init path it seems that kirq->nirqs is set to the port
> count before registration so it will not be 0 if domain is NULL.
>
I first thought it was fine because __irq_resolve_mapping() inside
irq_find_mapping() verifies that the domain isn't NULL, then
irq_find_mapping() returns 0 when it doesn't find an IRQ, and finally,
irq_dispose_mapping() returns immediately when virq is 0.
However, after taking a closer look at __irq_resolve_mapping(), I
noticed that there is a global irq_default_domain that is used by some
architectures (mainly MIPS and PowerPC) as a fallback when
__irq_resolve_mapping() is given a NULL domain. In that case, it seems
possible for the function to return a non-zero virq that has nothing to
do with us, and which would then be incorrectly released afterward by
irq_dispose_mapping().
This second case shouldn't occur often but I can move the for loop
behind the `if (kirq->domain)` check to be safe.
>> virq = irq_find_mapping(kirq->domain, irq);
>> irq_dispose_mapping(virq);
>> }
>>
>> - irq_domain_remove(kirq->domain);
>> + if (kirq->domain)
>> + irq_domain_remove(kirq->domain);
Best regards,
Bastien
next prev parent reply other threads:[~2025-11-12 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 12:53 [PATCH net v2 0/4] net: dsa: microchip: Fix resource releases in error path Bastien Curutchet (Schneider Electric)
2025-11-06 12:53 ` [PATCH net v2 1/4] net: dsa: microchip: common: Fix checks on irq_find_mapping() Bastien Curutchet (Schneider Electric)
2025-11-11 2:27 ` Jakub Kicinski
2025-11-12 7:45 ` Bastien Curutchet
2025-11-06 12:53 ` [PATCH net v2 2/4] net: dsa: microchip: ptp: " Bastien Curutchet (Schneider Electric)
2025-11-06 12:53 ` [PATCH net v2 3/4] net: dsa: microchip: Ensure a ksz_irq is initialized before freeing it Bastien Curutchet (Schneider Electric)
2025-11-11 2:28 ` Jakub Kicinski
2025-11-12 7:44 ` Bastien Curutchet [this message]
2025-11-06 12:53 ` [PATCH net v2 4/4] net: dsa: microchip: Immediately assing IRQ numbers Bastien Curutchet (Schneider Electric)
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=91ee0772-b166-4556-9c9e-e12fa0262088@bootlin.com \
--to=bastien.curutchet@bootlin.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pascal.eberhard@se.com \
--cc=richardcochran@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=woojung.huh@microchip.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;
as well as URLs for NNTP newsgroup(s).