Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 24 May 2023 18:30:12 +0200
From:   Willy Tarreau <w@1wt.eu>
To:     Thomas =?iso-8859-1?Q?Wei=DFschuh?= <linux@weissschuh.net>
Cc:     linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: s390: disable stackprotector in _start
Message-ID: <ZG47lJR+mRwtTfeQ@1wt.eu>
References: <20230524-nolibc-stackprotector-s390-v1-1-5044d42230cc@weissschuh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20230524-nolibc-stackprotector-s390-v1-1-5044d42230cc@weissschuh.net>
Precedence: bulk

On Wed, May 24, 2023 at 06:27:06PM +0200, Thomas Wei?schuh wrote:
> s390 does not support the "global" stack protector mode that is
> implemented in nolibc.
> 
> Now that nolibc detects if stack protectors are enabled at runtime it
> could happen that a future compiler does indeed use global mode on
> and nolibc would compile but segfault at runtime.
> 
> To avoid this hypothetic case and to align s390 with the other
> architectures disable stack protectors when compiling _start().
(...)

Queued, same branch. Thanks Thomas!
Willy