From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] board/arcturus/ppc-ucp1020 new gcc-6.x Linux kernel build fix
Date: Thu, 13 Jul 2017 19:30:59 +0200 [thread overview]
Message-ID: <20170713193059.08c08974@windsurf> (raw)
In-Reply-To: <20170713163817.7114-1-oleks@arcturusnetworks.com>
Hello,
On Thu, 13 Jul 2017 12:38:17 -0400, Oleksandr Zhadan wrote:
> Add the Linux-3.18 patch "powerpc/ptrace: Fix out of bounds array access warning" to the board/arcturus/ppc-ucp1020 BSP
>
> " gcc-6 correctly warns about a out of bounds access
>
> arch/powerpc/kernel/ptrace.c:407:24: warning: index 32 denotes an offset greater than size of 'u64[32][1] {aka long long unsigned int[32][1]}' [-Warray-bounds]
> offsetof(struct thread_fp_state, fpr[32][0]));
> ^
>
> check the end of array instead of beginning of next element to fix this"
>
> Signed-off-by: Oleksandr Zhadan <oleks@arcturusnetworks.com>
Do you have a good reason to stick with the 4.1 Linux kernel in this
defconfig, instead of upgrading to a newer kernel version that has
commit 1e407ee3b21f981140491d5b8a36422979ca246f ? For example, using
Linux 4.9 would solve this.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-13 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 16:38 [Buildroot] [PATCH 1/1] board/arcturus/ppc-ucp1020 new gcc-6.x Linux kernel build fix Oleksandr Zhadan
2017-07-13 17:30 ` Thomas Petazzoni [this message]
2017-07-13 19:21 ` Oleksandr G Zhadan
2017-07-14 7:22 ` Thomas Petazzoni
2017-07-14 12:59 ` Oleksandr G Zhadan
2017-07-15 8:16 ` Thomas Petazzoni
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=20170713193059.08c08974@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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