From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org, tglx@linutronix.de,
Len Brown <lenb@kernel.org>
Subject: Re: [patch 3/3] acpi: check for pxm_to_node_map overflow
Date: Fri, 2 Jan 2009 13:25:22 +0300 [thread overview]
Message-ID: <20090102102522.GA13629@localhost> (raw)
In-Reply-To: <20090102092330.GB1975@elte.hu>
[Ingo Molnar - Fri, Jan 02, 2009 at 10:23:30AM +0100]
|
| * Cyrill Gorcunov <gorcunov@gmail.com> wrote:
|
| > It is hardly (if ever) possible but in case of broken _PXM
| > entry we could reach out of pxm_to_node_map array
| > bounds in acpi_map_pxm_to_node() call. Lets check it
| > (it's not that expensive and safe).
| >
| > Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
| > CC: Len Brown <lenb@kernel.org>
| > ---
| > drivers/acpi/numa.c | 2 +-
| > 1 file changed, 1 insertion(+), 1 deletion(-)
|
| just curious - how did you find this - code review or some tool help like
| Sparse output or a compiler warning?
|
| Ingo
|
Unfortunately -- by reading the code :( I would prefer
if gcc or sparse complain about it but we have indirect
referring which is that hard to trace by any tool I believe
(until say some emulator but even if we have such kind of
tool we would need to tell it that 'there we have boundries
we shouldn't cross)'. But to be fair -- I didn't try sparse
here maybe it does complain :)
- Cyrill -
next prev parent reply other threads:[~2009-01-02 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090102082717.810810508@gmail.com>
2009-01-02 8:27 ` [patch 1/3] early_printk - use sizeof instead of hardcoded number Cyrill Gorcunov
2009-01-02 8:27 ` [patch 2/3] mm: hugetlb -- get rid of redundant if operation Cyrill Gorcunov
2009-01-02 9:22 ` Ingo Molnar
2009-01-02 8:27 ` [patch 3/3] acpi: check for pxm_to_node_map overflow Cyrill Gorcunov
2009-01-02 9:23 ` Ingo Molnar
2009-01-02 10:25 ` Cyrill Gorcunov [this message]
2009-01-02 10:30 ` Cyrill Gorcunov
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=20090102102522.GA13629@localhost \
--to=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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