Possible memory leak in function (reserve_range) not freeing pointer (regionid)

[Greg KH]

On Sun, Nov 30, 2014 at 09:49:23PM -0600, Ahmed Tamrawi wrote:
> On Sun, Nov 30, 2014 at 8:51 PM, Greg KH <gregkh at linuxfoundation.org> wrote:
> > On Sun, Nov 30, 2014 at 02:00:45PM -0600, Ahmed Tamrawi wrote:
> >> Bug Report: https://bugzilla.kernel.org/show_bug.cgi?id=89101
> >> Linux Version [3.17-rc1]
> >
> > That's a very old kernel version.
> It does exist on the latest version (v3.18-rc7)

Good to know.

> >> Configuration: Default configuration for x86
> >>
> >>
> >> Function (reserve_range) in file (drivers/pnp/system.c) allocates
> >> pointer (regionid) on line (32) and passes it to function
> >> (__request_region) through the macros: (request_region) at line (38)
> >> or (request_mem_region) at line (40). However, if the resource (res)
> >> is allocated through (__request_region) function, then the pointer
> >> (res->name) points to the allocated pointer (regionid). Then, there is
> >> no way in function (free_resource) or function (release_resource) to
> >> free the pointer (regionid) or (res->name). Thus, causing a potential
> >> memory leak!
> >
> > How does this relate to the mailing list you sent this to?
> The bug occurs in the drivers side code in pnp/system.c. I thought
> this is the list to target. I have already posted the bug into
> linux-kernel mailing list, does that suffice?

Use the tool, scripts/get_maintainer.pl to determine what people and
mailing lists to send issues to for specific files.  Just sending them
to random mailing lists without cc: developers is a sure way to get them
ignored.

thanks,

greg k-h