From: Guenter Roeck <linux@roeck-us.net>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390: Add WARN_DYNAMIC_STACK dependencies
Date: Wed, 15 Sep 2021 07:08:21 -0700 [thread overview]
Message-ID: <84949d48-435a-e76b-9977-d072f7359d91@roeck-us.net> (raw)
In-Reply-To: <80b7dbc9-0c09-197f-0f40-ab92d2e3fe3c@de.ibm.com>
On 9/15/21 2:02 AM, Christian Borntraeger wrote:
>
>
> On 15.09.21 06:40, Guenter Roeck wrote:
>> s390:allmodconfig fails to build with the following errors.
>>
>> arch/s390/kernel/syscall.c: In function '__do_syscall':
>> arch/s390/kernel/syscall.c:168:1: error:
>> '__do_syscall' uses dynamic stack allocation
>>
>> lib/test_kasan.c: In function 'kasan_alloca_oob_right':
>> lib/test_kasan.c:782:1: error:
>> 'kasan_alloca_oob_right' uses dynamic stack allocation
>>
>> lib/test_kasan.c: In function 'kasan_alloca_oob_left':
>> lib/test_kasan.c:767:1: error:
>> 'kasan_alloca_oob_left' uses dynamic stack allocation
>>
>> The first error is seen if RANDOMIZE_KSTACK_OFFSET_DEFAULT,
>> WARN_DYNAMIC_STACK, and WERROR are enabled. The other problems
>> are seen if KASAN_KUNIT_TEST, WARN_DYNAMIC_STACK, and WERROR
>> are enabled.
>>
>> It does not make sense to abort a build in that situation.
>> If either RANDOMIZE_KSTACK_OFFSET_DEFAULT or KASAN_KUNIT_TEST
>> is enabled, dynamic stack allocation is on purpose and should
>> not fail the build. Add dependencies to reflect that situation.
>>
>
> Thanks for the patch. I think Heiko (on vacation) has a patch to
> get rid of this config alltogether, which is probably the better
> solution.
>
I did consider that, but concluded that this would be something a maintainer
should do and went with what I thought was the least invasive method.
I did check the various mailing lists for other patches, but I did not
find anything there. Sorry if I missed it.
Guenter
next prev parent reply other threads:[~2021-09-15 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 4:40 [PATCH] s390: Add WARN_DYNAMIC_STACK dependencies Guenter Roeck
2021-09-15 9:02 ` Christian Borntraeger
2021-09-15 14:08 ` Guenter Roeck [this message]
2021-09-15 15:13 ` Vasily Gorbik
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=84949d48-435a-e76b-9977-d072f7359d91@roeck-us.net \
--to=linux@roeck-us.net \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox