public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Jessica Yu <jeyu@kernel.org>, kernel-janitors@vger.kernel.org
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel/module: Delete an error message for a failed memory allocation in add_module_usage()
Date: Thu, 19 Oct 2017 12:42:12 +0200	[thread overview]
Message-ID: <b4f1f555-4e54-8258-cd0c-764c6b314fee@users.sourceforge.net> (raw)
In-Reply-To: <20171019092943.hbghcaifwkcdsgd3@redbean>

>> @@ -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.

How do you think about to clarify the circumstances any further?


> Although stack traces are generated on alloc failures,

Do you ever want to switch them off for special use cases?


> the extra print also tells us which module we were trying to load
> at the time the memory allocation failed.

Can a default allocation failure report provide the same information already?

Regards,
Markus

  parent reply	other threads:[~2017-10-19 10:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 15:12 [PATCH] kernel/module: Delete an error message for a failed memory allocation in add_module_usage() SF Markus Elfring
2017-10-19  9:29 ` Jessica Yu
2017-10-19 10:30   ` Dan Carpenter
2017-10-19 11:02     ` Jessica Yu
2017-10-19 11:12       ` SF Markus Elfring
2017-10-19 10:42   ` SF Markus Elfring [this message]
2017-10-19 11:08 ` Jessica Yu
2017-10-19 11:18   ` SF Markus Elfring
2017-10-19 11:29     ` Joe Perches
2017-10-19 11:35       ` SF Markus Elfring
2017-10-19 11:45         ` Joe Perches
2017-10-19 18:56           ` SF Markus Elfring

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=b4f1f555-4e54-8258-cd0c-764c6b314fee@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=jeyu@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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