linux-kernel - Re: kernel/module: Delete an error message for a failed memory allocation in add_module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 19 Oct 2017 13:30:34 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     Jessica Yu <jeyu@...nel.org>
Cc:     SF Markus Elfring <elfring@...rs.sourceforge.net>,
        kernel-janitors@...r.kernel.org,
        Rusty Russell <rusty@...tcorp.com.au>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: kernel/module: Delete an error message for a failed memory
 allocation in add_module_usage()

On Thu, Oct 19, 2017 at 11:29:43AM +0200, Jessica Yu wrote:
> +++ SF Markus Elfring [06/10/17 17:12 +0200]:
> > From: Markus Elfring <elfring@...rs.sourceforge.net>
> > Date: Fri, 6 Oct 2017 16:27:26 +0200
> > 
> > Omit an extra message for a memory allocation failure in this function.
> > 
> > This issue was detected by using the Coccinelle software.
> > 
> > Signed-off-by: Markus Elfring <elfring@...rs.sourceforge.net>
> > ---
> > kernel/module.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
> > 
> > diff --git a/kernel/module.c b/kernel/module.c
> > index de66ec825992..07ef44767245 100644
> > --- a/kernel/module.c
> > +++ b/kernel/module.c
> > @@ -837,10 +837,8 @@ static int add_module_usage(struct module *a, struct module *b)
> > 
> > 	pr_debug("Allocating new usage for %s.\n", a->name);
> > 	use = kmalloc(sizeof(*use), GFP_ATOMIC);
> > -	if (!use) {
> > -		pr_warn("%s: out of memory loading\n", a->name);
> > +	if (!use)
> > 		return -ENOMEM;
> > -	}
> 
> IMO this is removing useful information. Although stack traces are
> generated on alloc failures, the extra print also tells us which
> module we were trying to load at the time the memory allocation
> failed.

This is a small allocation so it can't fail in current kernels.  I can't
imagine a situation where this could fail and it wasn't dead easy to
debug.  Most modules are loaded at boot so it's not likely to fail, but
if it did, it would be easy to reproduce.  If it's not loaded at boot
it's probably really easy to tell which module we're loading.

regards,
dan carpenter