From: "Michal Suchánek" <msuchanek@suse.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Marcelo Henrique Cerri <marcelo.cerri@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/decompressor: add fortify_panic as x86 has.
Date: Wed, 20 Dec 2017 15:09:29 +0100 [thread overview]
Message-ID: <20171220150929.38ab6771@kitsune.suse.cz> (raw)
In-Reply-To: <20171213083317.GA6931@osiris>
On Wed, 13 Dec 2017 09:33:17 +0100
Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> From 4ec2a3fd66bb5b1da35807bc2e382f9b8d9eebb8 Mon Sep 17 00:00:00 2001
> From: Heiko Carstens <heiko.carstens@de.ibm.com>
> Date: Wed, 13 Dec 2017 09:21:59 +0100
> Subject: [PATCH] s390/sclp: disable FORTIFY_SOURCE for early sclp code
>
> Michal Suchanek reported the following compile error with
> FORTIFY_SOURCE enabled:
>
> drivers/s390/char/sclp_early_core.o: In function `memcpy':
> include/linux/string.h:340: undefined reference to `fortify_panic'
>
> To fix this simply disable FORTIFY_SOURCE on the early sclp code as
> well, which I forgot on the initial commit.
>
> Fixes: 79962038dffa ("s390: add support for FORTIFY_SOURCE")
> Reported-by: Michal Suchanek <msuchanek@suse.de>
> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
> ---
> drivers/s390/char/Makefile | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/s390/char/Makefile b/drivers/s390/char/Makefile
> index 05ac6ba15a53..614b44e70a28 100644
> --- a/drivers/s390/char/Makefile
> +++ b/drivers/s390/char/Makefile
> @@ -17,6 +17,8 @@ CFLAGS_REMOVE_sclp_early_core.o +=
> $(CC_FLAGS_MARCH) CFLAGS_sclp_early_core.o +=
> -march=z900 endif
>
> +CFLAGS_sclp_early_core.o += -D__NO_FORTIFY
> +
> obj-y += ctrlchar.o keyboard.o defkeymap.o sclp.o sclp_rw.o
> sclp_quiesce.o \ sclp_cmd.o sclp_config.o sclp_cpi_sys.o sclp_ocf.o
> sclp_ctl.o \ sclp_early.o sclp_early_core.o
That works for me as well.
Tested-by: Michal Suchanek <msuchanek@suse.de>
Thanks
Michal
prev parent reply other threads:[~2017-12-20 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 10:37 [PATCH] s390/decompressor: add fortify_panic as x86 has Michal Suchanek
2017-12-07 12:55 ` Martin Schwidefsky
2017-12-11 13:09 ` Michal Suchánek
2017-12-13 8:33 ` Heiko Carstens
2017-12-20 14:09 ` Michal Suchánek [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=20171220150929.38ab6771@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=schwidefsky@de.ibm.com \
/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