public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Mike Beaton" <mjsbeaton@gmail.com>
To: devel@edk2.groups.io
Cc: Eric Dong <eric.dong@intel.com>, Dandan Bi <dandan.bi@intel.com>,
	 Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [edk2-devel] [PATCH v3] MdeModulePkg/HiiDatabase: Fix incorrect AllocateCopyPool size
Date: Wed, 6 Sep 2023 13:05:12 +0100	[thread overview]
Message-ID: <CAHzAAWQh_LCtQ3FTMFq=5agc0b2xEec3KVbuwSQ-ZwU4HZNu+g@mail.gmail.com> (raw)
In-Reply-To: <CAHzAAWQ9m-QPAEhmrnie9TgGAAaMejxJg5o06keTNQ0KmEiHYA@mail.gmail.com>

On Wed, 6 Sept 2023 at 12:55, Mike Beaton <mjsbeaton@gmail.com> wrote:
>
> On Wed, 6 Sept 2023 at 11:34, Mike Beaton <mjsbeaton@gmail.com> wrote:
> >
> > AsciiStrLen was one byte too short (though with alignment up from an odd size
> > would probably always have had the required space in practice). AsciiStrSize
> > matches usage elsewhere in this file and in the codebase.

Have just realised that the severity is worse than implied in my
current commit message,
since not only are (potentially - though almost certainly not, in practice) too
few bytes allocated, but definitely too few bytes are then copied, so
the resulting string is
only null terminated by the grace of the specific implementation, too.
Could update to a v4
of this (small) patch with a commit message mentioning this?


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108329): https://edk2.groups.io/g/devel/message/108329
Mute This Topic: https://groups.io/mt/101189764/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2023-09-06 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 10:33 [edk2-devel] [PATCH v3] MdeModulePkg/HiiDatabase: Fix incorrect AllocateCopyPool size Mike Beaton
2023-09-06 11:55 ` Mike Beaton
2023-09-06 12:05   ` Mike Beaton [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-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='CAHzAAWQh_LCtQ3FTMFq=5agc0b2xEec3KVbuwSQ-ZwU4HZNu+g@mail.gmail.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