All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 2/2] hvmloader: cast to 64bit before multiplication in get_module_entry
Date: Mon, 22 Aug 2016 12:37:40 +0100	[thread overview]
Message-ID: <20160822113740.GV20641@citrix.com> (raw)
In-Reply-To: <57B710EC020000780010760E@prv-mh.provo.novell.com>

On Fri, Aug 19, 2016 at 06:00:12AM -0600, Jan Beulich wrote:
> >>> On 19.08.16 at 12:09, <andrew.cooper3@citrix.com> wrote:
> > On 19/08/16 09:31, Jan Beulich wrote:
> >>>>> On 19.08.16 at 10:06, <wei.liu2@citrix.com> wrote:
> >>> --- a/tools/firmware/hvmloader/hvmloader.c
> >>> +++ b/tools/firmware/hvmloader/hvmloader.c
> >>> @@ -272,8 +272,8 @@ const struct hvm_modlist_entry *get_module_entry(
> >>>  
> >>>      if ( !modlist ||
> >>>           info->modlist_paddr > UINTPTR_MAX ||
> >>> -         (info->modlist_paddr + info->nr_modules * sizeof(*modlist) - 1)
> >>> -            > UINTPTR_MAX )
> >>> +         (info->modlist_paddr +
> >>> +          (uint64_t)info->nr_modules * sizeof(*modlist) - 1) > UINTPTR_MAX )
> >>>          return NULL;
> >> This can be had without resorting to 64-bit multiplication, by bounds
> >> checking
> >>
> >>          (UINTPTR_MAX - (uintptr_t)info->modlist_paddr) / sizeof(*modlist)
> >>
> >> instead. While we would certainly hope that compilers don't resort
> >> to a libgcc helper for 64-bit multiplication, I think we'd better avoid
> >> that risk altogether.
> > 
> > In this case, using libgcc would cause a link error because of
> > -fno-builtin, so I don't think it is too bad.
> 
> And it's this link error which I want to avoid.
> 

What approach should I use? I would like to clear this minor issue as
quick as possible.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-08-22 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  8:06 [PATCH 0/2] hvmloader: fix two issues spotted by Coverity Wei Liu
2016-08-19  8:06 ` [PATCH 1/2] hvmloader: correctly copy signature to info structures Wei Liu
2016-08-19  8:25   ` Jan Beulich
2016-08-19  9:42     ` Andrew Cooper
2016-08-19 11:58       ` Jan Beulich
2016-08-19  8:06 ` [PATCH 2/2] hvmloader: cast to 64bit before multiplication in get_module_entry Wei Liu
2016-08-19  8:31   ` Jan Beulich
2016-08-19 10:09     ` Andrew Cooper
2016-08-19 12:00       ` Jan Beulich
2016-08-22 11:37         ` Wei Liu [this message]
2016-08-22 11:55           ` Jan Beulich

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=20160822113740.GV20641@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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.