From: Christian Borntraeger <borntraeger@de.ibm.com>
To: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Michal Marek <mmarek@suse.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Yang Shi <yang.shi@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [PATCH 0/2] ubsan for s390
Date: Mon, 12 Sep 2016 14:37:18 +0200 [thread overview]
Message-ID: <1473683840-8700-1-git-send-email-borntraeger@de.ibm.com> (raw)
This patch set enables ubsan for s390.
We have to fence some files and can then enable
ARCH_HAS_UBSAN_SANITIZE_ALL. (patch 2)
We have to disable the null pointer sanitizer as
we use the S390_lowcore macro to access several
memory location after address 0 (patch 1)
If patch 1 is ok, is the s390 tree the right place
also for patch1?
Christian Borntraeger (2):
ubsan: allow to disable the null sanitizer
s390/ubsan: enable UBSAN for s390
arch/s390/Kconfig | 2 ++
arch/s390/boot/compressed/Makefile | 1 +
arch/s390/kernel/Makefile | 3 +++
arch/s390/kernel/vdso32/Makefile | 3 ++-
arch/s390/kernel/vdso64/Makefile | 3 ++-
lib/Kconfig.ubsan | 11 +++++++++++
scripts/Makefile.ubsan | 5 ++++-
7 files changed, 25 insertions(+), 3 deletions(-)
--
2.5.5
next reply other threads:[~2016-09-12 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 12:37 Christian Borntraeger [this message]
2016-09-12 12:37 ` [PATCH 1/2] ubsan: allow to disable the null sanitizer Christian Borntraeger
2016-09-13 6:46 ` Heiko Carstens
2016-09-12 12:37 ` [PATCH 2/2] s390/ubsan: enable UBSAN for s390 Christian Borntraeger
2016-09-12 16:38 ` [PATCH 0/2] ubsan " Andrey Ryabinin
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=1473683840-8700-1-git-send-email-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=schwidefsky@de.ibm.com \
--cc=yang.shi@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox