From: Marc Zyngier <maz@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup()
Date: Thu, 02 Feb 2023 16:56:50 +0000 [thread overview]
Message-ID: <867cx00zvx.wl-maz@kernel.org> (raw)
In-Reply-To: <Y9vqJhCj5w/+b6SV@kroah.com>
On Thu, 02 Feb 2023 16:51:50 +0000,
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> On Thu, Feb 02, 2023 at 04:48:30PM +0000, Marc Zyngier wrote:
> > On Thu, 02 Feb 2023 15:15:54 +0000,
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > >
> > > When calling debugfs_lookup() the result must have dput() called on it,
> > > otherwise the memory will leak over time. To make things simpler, just
> > > call debugfs_lookup_and_remove() instead which handles all of the logic
> > > at once.
> > >
> > > Cc: Marc Zyngier <maz@kernel.org>
> > > Cc: Thomas Gleixner <tglx@linutronix.de>
> > > Cc: linux-kernel@vger.kernel.org
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > ---
> > > kernel/irq/irqdomain.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> > > index 8fe1da9614ee..e2096b51c004 100644
> > > --- a/kernel/irq/irqdomain.c
> > > +++ b/kernel/irq/irqdomain.c
> > > @@ -1915,7 +1915,7 @@ static void debugfs_add_domain_dir(struct irq_domain *d)
> > >
> > > static void debugfs_remove_domain_dir(struct irq_domain *d)
> > > {
> > > - debugfs_remove(debugfs_lookup(d->name, domain_dir));
> > > + debugfs_lookup_and_remove(d->name, domain_dir);
> > > }
> > >
> > > void __init irq_domain_debugfs_init(struct dentry *root)
> >
> > Reviewed-by: Marc Zyngier <maz@kernel.org>
> >
> > Maybe add a Cc stable to get this in 6.1?
>
> Sure, I can, but how often are irq domains removed from the system under
> a normal operation?
As many time as you want if you're doing virtualisation and have the
right sort of HW (anything GICv4.x, for example, which will create
per-VM irqdomains).
> Or you can take it through your tree and add that? I too can take
> it through mine, which ever is easier for you.
Sure, I can queue that, although that will probably be next week.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-02-02 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 15:15 [PATCH] kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup() Greg Kroah-Hartman
2023-02-02 16:48 ` Marc Zyngier
2023-02-02 16:51 ` Greg Kroah-Hartman
2023-02-02 16:56 ` Marc Zyngier [this message]
2023-02-03 6:04 ` Greg Kroah-Hartman
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=867cx00zvx.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.