From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>,
Liming Gao <liming.gao@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>
Subject: [PATCH 0/4] MdePkg/BaseSafeIntLib: fix undefined behavior in INT64 Sub/Add/Mult
Date: Thu, 15 Feb 2018 19:36:34 +0100 [thread overview]
Message-ID: <20180215183638.18578-1-lersek@redhat.com> (raw)
Repo: https://github.com/lersek/edk2.git
Branch: signed_range_checks
Based on the discussion starting at
<https://lists.01.org/pipermail/edk2-devel/2018-February/021178.html>.
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>
Laszlo Ersek (4):
MdePkg/BaseSafeIntLib: fix undefined behavior in SafeInt64Sub()
MdePkg/BaseSafeIntLib: fix undefined behavior in SafeInt64Add()
MdePkg/BaseSafeIntLib: clean up parentheses in MIN_INT64_MAGNITUDE
MdePkg/BaseSafeIntLib: fix undefined behavior in SafeInt64Mult()
MdePkg/Library/BaseSafeIntLib/SafeIntLib.c | 110 ++++++++++++++++----
1 file changed, 88 insertions(+), 22 deletions(-)
--
2.14.1.3.gb7cf6e02401b
next reply other threads:[~2018-02-15 18:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 18:36 Laszlo Ersek [this message]
2018-02-15 18:36 ` [PATCH 1/4] MdePkg/BaseSafeIntLib: fix undefined behavior in SafeInt64Sub() Laszlo Ersek
2018-02-15 18:36 ` [PATCH 2/4] MdePkg/BaseSafeIntLib: fix undefined behavior in SafeInt64Add() Laszlo Ersek
2018-02-15 18:36 ` [PATCH 3/4] MdePkg/BaseSafeIntLib: clean up parentheses in MIN_INT64_MAGNITUDE Laszlo Ersek
2018-02-15 18:36 ` [PATCH 4/4] MdePkg/BaseSafeIntLib: fix undefined behavior in SafeInt64Mult() Laszlo Ersek
2018-02-16 11:28 ` [PATCH 0/4] MdePkg/BaseSafeIntLib: fix undefined behavior in INT64 Sub/Add/Mult Ard Biesheuvel
2018-02-16 20:44 ` Laszlo Ersek
2018-02-16 18:11 ` Kinney, Michael D
2018-02-16 20:49 ` Laszlo Ersek
2018-02-17 3:07 ` Kinney, Michael D
2018-02-21 11:00 ` Laszlo Ersek
2018-02-21 18:10 ` Ard Biesheuvel
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-list 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=20180215183638.18578-1-lersek@redhat.com \
--to=devel@edk2.groups.io \
/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