From: Filipe Brandenburger <filbranden@google.com>
To: Daniel J Blueman <daniel@numascale.com>
Cc: linux-numa@vger.kernel.org, Steffen Persvold <sp@numascale.com>,
Cliff Wickman <cpw@sgi.com>
Subject: Re: [PATCH] Fix a SEGV due to uninitialised mask
Date: Wed, 18 Feb 2015 13:39:09 -0800 [thread overview]
Message-ID: <CADU+-uAkabE80TjG1T-20G9xCZZyMRqu89gOQtqcyFZ9vpatPg@mail.gmail.com> (raw)
In-Reply-To: <1424146011-28317-1-git-send-email-daniel@numascale.com>
Hi,
On Mon, Feb 16, 2015 at 8:06 PM, Daniel J Blueman <daniel@numascale.com> wrote:
> As node_cpu_mask_v2 is not defined as local to the compilation unit with
> 'static', it is not guaranteed to be initialised to zero (ie in the .bss).
> This was leading to some SEGVs we've seen.
>
> Also mark another internal function local to the compilation unit.
>
> Signed-off-by: Daniel J Blueman <daniel@numascale.com>
Pushed. Thanks for the contribution!
Cheers,
Filipe
prev parent reply other threads:[~2015-02-18 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 4:06 [PATCH] Fix a SEGV due to uninitialised mask Daniel J Blueman
2015-02-18 21:39 ` Filipe Brandenburger [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=CADU+-uAkabE80TjG1T-20G9xCZZyMRqu89gOQtqcyFZ9vpatPg@mail.gmail.com \
--to=filbranden@google.com \
--cc=cpw@sgi.com \
--cc=daniel@numascale.com \
--cc=linux-numa@vger.kernel.org \
--cc=sp@numascale.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).