public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Trent Piepho <tpiepho@impinj.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Todd Kjos <tkjos@google.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] ARM: amba: Fix leak of driver_override attribute value
Date: Thu, 20 Sep 2018 09:09:37 +0200	[thread overview]
Message-ID: <20180920070937.GA9609@kroah.com> (raw)
In-Reply-To: <CAMuHMdVMbjkvEXex_Z8ELPUo8hVZucFBCd2Wy4ENpiqEaLES_w@mail.gmail.com>

On Thu, Sep 20, 2018 at 08:48:36AM +0200, Geert Uytterhoeven wrote:
> On Thu, Sep 20, 2018 at 1:48 AM Trent Piepho <tpiepho@impinj.com> wrote:
> > If driver_override was set when a device was released the string would
> > not be kfree'ed in amba_device_release and thus leaked when the amba
> > device was freed.
> >
> > Cc: Russell King <linux@armlinux.org.uk>
> > Cc: Todd Kjos <tkjos@google.com>
> > Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Trent Piepho <tpiepho@impinj.com>
> 
> Reported-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Fixes: 3cf385713460eb2b ("ARM: 8256/1: driver coamba: add device
> binding path 'driver_override'")

Then it should also have a cc: stable, right?

thanks,

greg k-h

  reply	other threads:[~2018-09-20  7:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 23:47 [PATCH] ARM: amba: Fix leak of driver_override attribute value Trent Piepho
2018-09-20  6:48 ` Geert Uytterhoeven
2018-09-20  7:09   ` Greg KH [this message]
2018-09-20  7:16     ` Geert Uytterhoeven
2018-09-20  7:24       ` Greg KH

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=20180920070937.GA9609@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=tkjos@google.com \
    --cc=tpiepho@impinj.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