From: David Rientjes <rientjes@google.com>
To: Himangi Saraogi <himangi774@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [PATCH] x86, olpc: Eliminate BUG_ON and memset after alloc_bootmem
Date: Mon, 21 Jul 2014 15:56:48 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1407211553190.29389@chino.kir.corp.google.com> (raw)
In-Reply-To: <20140719113637.GA23621@himangi-Dell>
On Sat, 19 Jul 2014, Himangi Saraogi wrote:
> alloc_bootmem and related functions never return NULL and always return
> a zeroed region of memory. Thus a BUG_ON the NULL test or memset after
> calls to these functions is unnecessary.
>
> The following Coccinelle semantic patch was used for making the change:
>
> @@
> expression E;
> statement S;
> @@
>
> E = \(alloc_bootmem\|alloc_bootmem_low\|alloc_bootmem_pages\|alloc_bootmem_low_pages\)(...)
> ... when != E
> - BUG_ON (E == NULL);
>
> @@
> expression E,E1;
> @@
>
> E = \(alloc_bootmem\|alloc_bootmem_low\|alloc_bootmem_pages\|alloc_bootmem_low_pages\)(...)
> ... when != E
> - memset(E,0,E1);
>
> Signed-off-by: Himangi Saraogi <himangi774@gmail.com>
> Acked-by: Julia Lawall <julia.lawall@lip6.fr>
Acked-by: David Rientjes <rientjes@google.com>
Many callers of alloc_bootmem() do not check for the return value because
of this, there's no fallback available at this part in bootstrap so
there's nothing else that can be done.
prev parent reply other threads:[~2014-07-21 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 11:36 Himangi Saraogi
2014-07-21 22:56 ` David Rientjes [this message]
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=alpine.DEB.2.02.1407211553190.29389@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=himangi774@gmail.com \
--cc=hpa@zytor.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®