From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Adrian Ambrozewicz <aambrozewicz@nvidia.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Kent Gibson <warthog618@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Herve Codina <herve.codina@bootlin.com>,
Jia Jia <physicalmtea@gmail.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 5/6] gpiolib: cdev: don't leak the IRQ name when the chip is removed
Date: Tue, 13 Oct 2026 18:59:53 +0300 [thread overview]
Message-ID: <as5VeTfADRr9nwRN@ashevche-desk.local> (raw)
In-Reply-To: <20261012-gpiolib-chip-removal-v1-5-aambrozewicz@nvidia.com>
On Mon, Oct 12, 2026 at 04:49:59PM +0300, Adrian Ambrozewicz wrote:
> The character device requests line IRQs with a copy of the consumer
> label as the name and frees that copy with the name free_irq() returns.
> Since commit ec8b6f55b981 ("gpio: free irqs that are still requested
> when the chip is being removed"), gpiochip_remove() may free the IRQ
> first and drops the name it gets back. The character device then does
> not get it from its own free_irq() call, which since the previous patch
> it does not even make, so the copy leaks:
> unreferenced object 0xff1100000435b080 (size 8):
> comm "gpio-hold", pid 108, jiffies 4294695819
> hex dump (first 8 bytes):
> 72 65 70 72 6f 00 00 00 repro...
> backtrace (crc dc8eac94):
> __kmalloc_node_track_caller_noprof+0x50f/0x6a0
> kstrdup+0x35/0x90
> kstrdup_and_replace+0x19/0xe0
> edge_detector_setup+0x5d8/0x940
> linereq_create+0x9ec/0xce0
> gpio_ioctl+0x49c/0xc80
> __x64_sys_ioctl+0x134/0x1c0
> do_syscall_64+0x109/0x5d0
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
For all patches, please, act in accordance with the Submitting Patches
documentation on backtraces in the commit messages.
> Keep the name with the line, or with the v1 line event, and free it
> there whoever freed the IRQ.
>
> Reproduced with gpio-sim and a line requested with edge detection and
> a consumer label, the chip being removed while the request is open:
> kmemleak reports between 17 and 23 such objects after 30 cycles; with
> this change, none after 100.
...
> -static void free_line_irq(unsigned int irq, void *dev_id)
> +static void free_line_irq(unsigned int irq, void *dev_id, char **label)
> {
> if (irq_has_action(irq))
> - free_irq_label(free_irq(irq, dev_id));
> + free_irq(irq, dev_id);
> + free_irq_label(*label);
> + *label = NULL;
> }
This can be modified a bit to prepare for this with the suggestion to check
an irq here. So, in the previous patch you may have it as
char *name = NULL;
if (irq && irq_has_action(irq))
name = free_irq(irq, dev_id);
free_irq_label(name);
After this patch
char *name = *label;
if (irq && irq_has_action(irq))
free_irq(irq, dev_id);
free_irq_label(name);
*label = NULL;
...
While it might be more verbose I think it makes the point clearer.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-13 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 13:49 [PATCH 0/6] gpiolib: fix chip removal with lines still requested from user space Adrian Ambrozewicz
2026-10-12 13:49 ` [PATCH 1/6] gpiolib: wait for pending label frees before cleaning up desc_srcu Adrian Ambrozewicz
2026-10-12 15:46 ` Paul E. McKenney
2026-10-12 20:42 ` Andy Shevchenko
2026-10-12 13:49 ` [PATCH 2/6] gpiolib: free the label of lines released after their chip was removed Adrian Ambrozewicz
2026-10-13 15:38 ` Andy Shevchenko
2026-10-12 13:49 ` [PATCH 3/6] gpiolib: cdev: do not free line IRQs again after the chip is removed Adrian Ambrozewicz
2026-10-13 15:44 ` Andy Shevchenko
2026-10-12 13:49 ` [PATCH 4/6] gpiolib: cdev: don't sleep in the SRCU read section in read() Adrian Ambrozewicz
2026-10-13 15:48 ` Andy Shevchenko
2026-10-12 13:49 ` [PATCH 5/6] gpiolib: cdev: don't leak the IRQ name when the chip is removed Adrian Ambrozewicz
2026-10-13 15:59 ` Andy Shevchenko [this message]
2026-10-12 13:50 ` [PATCH 6/6] gpiolib: let the character device free its IRQs first on chip removal Adrian Ambrozewicz
2026-10-13 16:05 ` Andy Shevchenko
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=as5VeTfADRr9nwRN@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=aambrozewicz@nvidia.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=herve.codina@bootlin.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=physicalmtea@gmail.com \
--cc=stable@vger.kernel.org \
--cc=warthog618@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
all inboxes | Powered by JetHome®