From: Andi Kleen <andi@firstfloor.org>
To: Petr Oros <poros@redhat.com>
Cc: linux-numa@vger.kernel.org
Subject: Re: [PATCH] numastat: fix bad column calculation in show_process_info
Date: Thu, 25 May 2017 11:30:27 -0700 [thread overview]
Message-ID: <20170525183026.GD8096@two.firstfloor.org> (raw)
In-Reply-To: <20170525113632.11638-1-poros@redhat.com>
On Thu, May 25, 2017 at 01:36:32PM +0200, Petr Oros wrote:
> When system has non contiguous numa node number, double_add writing in bad area in table struct.
Should be already covered in
commit b608687037d873ad82d6318f231b3d6612e8601d
Author: Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
Date: Wed Dec 21 12:48:11 2016 +0530
Segment fault when numa nodes not sequential or contiguous
in https://github.com/numactl/numactl
Please check.
-Andi
prev parent reply other threads:[~2017-05-25 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 11:36 [PATCH] numastat: fix bad column calculation in show_process_info Petr Oros
2017-05-25 18:30 ` Andi Kleen [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=20170525183026.GD8096@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-numa@vger.kernel.org \
--cc=poros@redhat.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 NNTP newsgroup(s).