linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
	Quentin Lambert <lambert.quentin@gmail.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	kernel-janitors@vger.kernel.org, linux-wireless@vger.kernel.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] staging: rtl8723au: Remove unnecessary OOM message
Date: Fri, 06 Mar 2015 09:35:02 -0800	[thread overview]
Message-ID: <1425663302.12017.32.camel@perches.com> (raw)
In-Reply-To: <wrfj61aeyup1.fsf@ultrasam.lan.trained-monkey.org>

On Fri, 2015-03-06 at 11:08 -0500, Jes Sorensen wrote:
> Julia Lawall <julia.lawall@lip6.fr> writes:
> > On Fri, 6 Mar 2015, Jes Sorensen wrote:
> >> Quentin Lambert <lambert.quentin@gmail.com> writes:
> >> > This patch reduces the kernel size by removing error messages that duplicate
> >> > the normal OOM message.
> >> > A simplified version of the semantic patch that finds this problem is as
> >> > follows: (http://coccinelle.lip6.fr)
> >> This patch removes useful warnings about what allocation failed. The
> >> messages removed are NOT duplicate!
> > Is it really the case that the information can't be reconstructed from the
> > information generated by kmalloc on failure?  To my understanding there is
> > a stack trace, and from scanning through the changes I see only one change
> > per function, so perhaps the stack trace already makes it clear where the
> > problem occurred?
> It may be possible to backtrack, but this change just makes it harder.
> There are tons of real issues to fix in this driver, this patch just
> increases the risk of patch conflicts for no real gain.

Making the allocation less likely to fail for
low memory systems is a gain.

The allocation failures themselves are low
likelihood events.  Determining which specific
memory allocation failure occurred has near
nil value.



  reply	other threads:[~2015-03-06 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06  8:21 [PATCH 1/1] staging: rtl8723au: Remove unnecessary OOM message Quentin Lambert
2015-03-06 15:27 ` Jes Sorensen
2015-03-06 15:33   ` Julia Lawall
2015-03-06 16:08     ` Jes Sorensen
2015-03-06 17:35       ` Joe Perches [this message]
2015-03-06 19:43         ` Jes Sorensen
2015-03-06 20:21           ` Joe Perches

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=1425663302.12017.32.camel@perches.com \
    --to=joe@perches.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lambert.quentin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).