From: Andrew Donnellan <andrew.donnellan@au1•ibm.com>
To: Daniel Axtens <dja@axtens•net>, linuxppc-dev@ozlabs•org
Cc: akpm@linux-foundation•org,
Andrey Ryabinin <aryabinin@virtuozzo•com>,
linux-kernel@vger•kernel.org
Subject: Re: [RFC] powerpc: Enable UBSAN support
Date: Tue, 15 Dec 2015 13:40:26 +1100 [thread overview]
Message-ID: <566F7D9A.4050806@au1.ibm.com> (raw)
In-Reply-To: <1449708123-7340-1-git-send-email-dja@axtens.net>
On 10/12/15 11:42, Daniel Axtens wrote:
> This hooks up UBSAN support for PowerPC.
>
> So far it's found some interesting cases where we don't properly sanitise
> input to shifts, including one in our futex handling. Nothing critical,
> but interesting and worth fixing.
>
> CC: Andrey Ryabinin <aryabinin@virtuozzo•com>
> ---
>
> This to be applied on top of next with Andrey's patches:
> 1) https://patchwork.kernel.org/patch/7761341/
> 2) https://patchwork.kernel.org/patch/7761351/
> 3) https://patchwork.kernel.org/patch/7761361/
> 4) https://patchwork.kernel.org/patch/7785791/
>
> This is RFC for a couple of reasons:
>
> - I'd like the original patches to
> s/ARCH_HAS_UBSAN_SANTIZE_ALL/ARCH_HAS_UBSAN_SAN*I*TIZE_ALL/
> (I'm about to send an email about that)
>
> - I've only tested on LE pseries so far - I want to test on powernv,
> and on BE.
>
> Signed-off-by: Daniel Axtens <dja@axtens•net>
I tested this patch as found in linux-next, along with the SANITIZE_ALL
typo fix, on a big-endian BML system, with gcc 5.2.1. It successfully
picked up one of the shift input issues that Daniel found, so therefore...
Tested-by: Andrew Donnellan <andrew.donnellan@au1•ibm.com>
--
Andrew Donnellan Software Engineer, OzLabs
andrew.donnellan@au1•ibm.com Australia Development Lab, Canberra
+61 2 6201 8874 (work) IBM Australia Limited
prev parent reply other threads:[~2015-12-15 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 0:42 [RFC] powerpc: Enable UBSAN support Daniel Axtens
2015-12-15 2:40 ` Andrew Donnellan [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-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=566F7D9A.4050806@au1.ibm.com \
--to=andrew.donnellan@au1$(echo .)ibm.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=aryabinin@virtuozzo$(echo .)com \
--cc=dja@axtens$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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