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:   Tue, 6 Jun 2023 06:48:44 +0200
From:   Willy Tarreau <w@1wt.eu>
To:     Thomas =?iso-8859-1?Q?Wei=DFschuh?= <thomas@t-8ch.de>
Cc:     "Paul E. McKenney" <paulmck@kernel.org>,
        Zhangjin Wu <falcon@tinylab.org>, linux-kernel@vger.kernel.org,
        linux-kselftest@vger.kernel.org
Subject: Re: nolibc patches, still possible for 6.5 ?
Message-ID: <ZH66rI847lA1q3gq@1wt.eu>
References: <ZHyPi29q3MKiNAQZ@1wt.eu>
 <1fc53bcf-f7ec-4d74-a984-da4ee38e938f@t-8ch.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1fc53bcf-f7ec-4d74-a984-da4ee38e938f@t-8ch.de>
Precedence: bulk

On Mon, Jun 05, 2023 at 12:44:03PM +0200, Thomas Wei?schuh wrote:
> (Talking about 20230605-nolibc-rv32+stkp7,
> but the same issue is in stkp6)
> 
> I noticed that the commit introducing prctl() comes *after* the one
> making use of it.
> 
> 8389cb4b55ae ("selftests/nolibc: prevent coredumps during test execution")
> 033c01b5a8f4 ("tools/nolibc: add support for prctl()")
> 
> This can lead to compiler errors and break bisectability.
> 
> They just need to be swapped.

just done in 20230606-nolibc-rv32+stkp7a, thank you!

Willy