All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: x86@kernel.org, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: warning: ‘memset’ offset [197, 448] from the object at ‘boot_params’ is out of the bounds of referenced subobject ‘ext_ramdisk_image’ with type, ‘unsigned int’ at offset 192 [-Warray-bounds]
Date: Thu, 15 Aug 2019 14:43:06 +0200	[thread overview]
Message-ID: <20190815124306.GA17581@kroah.com> (raw)
In-Reply-To: <7e44d224-ce7e-909d-e91e-9a643b5fcd71@molgen.mpg.de>

On Tue, Aug 13, 2019 at 06:15:51PM +0200, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> No idea, if you are interested in these reports. Building Linux 5.3-rc4,
> GCC 9.2.0 shows the warning below.
> 
> ```
> In file included from arch/x86/kernel/head64.c:35:
> In function ‘sanitize_boot_params’,
>     inlined from ‘copy_bootdata’ at arch/x86/kernel/head64.c:391:2:
> ./arch/x86/include/asm/bootparam_utils.h:40:3: warning: ‘memset’ offset [197, 448] from the object at ‘boot_params’ is out of the bounds of referenced subobject ‘ext_ramdisk_image’ with type
>  ‘unsigned int’ at offset 192 [-Warray-bounds]
>    40 |   memset(&boot_params->ext_ramdisk_image, 0,
>       |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    41 |          (char *)&boot_params->efi_info -
>       |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    42 |    (char *)&boot_params->ext_ramdisk_image);
>       |    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ./arch/x86/include/asm/bootparam_utils.h:43:3: warning: ‘memset’ offset [493, 497] from the object at ‘boot_params’ is out of the bounds of referenced subobject ‘kbd_status’ with type ‘unsig
> ned char’ at offset 491 [-Warray-bounds]
>    43 |   memset(&boot_params->kbd_status, 0,
>       |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    44 |          (char *)&boot_params->hdr -
>       |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    45 |          (char *)&boot_params->kbd_status);
>       |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ```

Yeah, it shows up on my builds as well :(

Any chance you can make a fix for this?

thanks,

greg k-h

  reply	other threads:[~2019-08-15 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 16:15 warning: ‘memset’ offset [197, 448] from the object at ‘boot_params’ is out of the bounds of referenced subobject ‘ext_ramdisk_image’ with type, ‘unsigned int’ at offset 192 [-Warray-bounds] Paul Menzel
2019-08-15 12:43 ` Greg KH [this message]
2019-08-15 12:54   ` Thomas Gleixner
2019-08-15 13:19     ` Greg KH

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=20190815124306.GA17581@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=x86@kernel.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.