From: Cody P Schafer <cody@linux.vnet.ibm.com>
To: Cody Schafer <cody@linux.vnet.ibm.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@redhat.com>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] perf: prevent overflow in size calculation
Date: Thu, 19 Jul 2012 19:57:14 -0700 [thread overview]
Message-ID: <5008C90A.50705@linux.vnet.ibm.com> (raw)
In-Reply-To: <1342752552-3065-1-git-send-email-cody@linux.vnet.ibm.com>
> struct annotation *notes = symbol__annotation(sym);
> const size_t size = symbol__size(sym);
> - size_t sizeof_sym_hist = (sizeof(struct sym_hist) + size * sizeof(u64));
> + size_t sizeof_sym_hist;
> +
> + /* Check for overflow when calculating sizeof_sym_hist */
> + if (size > (SIZE_MAX / sizeof(u64) - sizeof(struct sym_hist)))
> + return -1;
> +
> + sizeof_sym_hist = (sizeof(struct sym_hist) + size * sizeof(u64));
> +
> + /* Check for overflow in zalloc argument */
> + if (sizeof_sym_hist > (SIZE_MAX / symbol_conf.nr_events
> + - sizeof(*notes->src)))
> + return -1;
>
> notes->src = zalloc(sizeof(*notes->src) + symbol_conf.nr_events * sizeof_sym_hist);
> if (notes->src == NULL)
>
Actually, I don't think this is correct either (subtraction seems to
occur in the wrong spot).
next prev parent reply other threads:[~2012-07-20 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 0:13 [PATCH] perf: prevent overflow in size calculation Cody Schafer
2012-07-20 0:49 ` Namhyung Kim
2012-07-20 2:49 ` [PATCH v2] " Cody Schafer
2012-07-20 2:57 ` Cody P Schafer [this message]
2012-07-20 3:05 ` [PATCH v3] " Cody Schafer
2012-07-25 19:33 ` [tip:perf/core] perf annotate: Prevent " tip-bot for Cody Schafer
2012-07-20 2:51 ` [PATCH] perf: prevent " Cody P Schafer
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=5008C90A.50705@linux.vnet.ibm.com \
--to=cody@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=sukadev@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.