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;
Feedback-ID: i56a14606:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-624-g7714e4406d-fm-20230801.001-g7714e440
Mime-Version: 1.0
Message-Id: <eeeef65a-fbf9-403f-8541-5169b06976d7@app.fastmail.com>
In-Reply-To: <66ca8677-6a8d-c2f6-f215-a49ae7248458@csgroup.eu>
References: <20230809131024.2039647-1-arnd@kernel.org>
 <66ca8677-6a8d-c2f6-f215-a49ae7248458@csgroup.eu>
Date:   Wed, 09 Aug 2023 15:35:46 +0200
From:   "Arnd Bergmann" <arnd@arndb.de>
To:     "Christophe Leroy" <christophe.leroy@csgroup.eu>,
        "Arnd Bergmann" <arnd@kernel.org>,
        "Michael Ellerman" <mpe@ellerman.id.au>
Cc:     "Nicholas Piggin" <npiggin@gmail.com>,
        "Andrew Morton" <akpm@linux-foundation.org>,
        "Jiri Slaby" <jirislaby@kernel.org>,
        "Maninder Singh" <maninder1.s@samsung.com>,
        "Hugh Dickins" <hughd@google.com>,
        "Gustavo A. R. Silva" <gustavoars@kernel.org>,
        "Nathan Lynch" <nathanl@linux.ibm.com>,
        "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] powerpc: mark more local variables as volatile
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Wed, Aug 9, 2023, at 15:17, Christophe Leroy wrote:
> Le 09/08/2023 =C3=A0 15:10, Arnd Bergmann a =C3=A9crit=C2=A0:
>> From: Arnd Bergmann <arnd@arndb.de>
>>=20
>> A while ago I created a2305e3de8193 ("powerpc: mark local variables
>> around longjmp as volatile") in order to allow building powerpc with
>> -Wextra enabled on gcc-11.
>
> Should this be explained in=20
> https://docs.kernel.org/process/volatile-considered-harmful.html ?
>

My feeling is that these two files are special enough that we
don't have to worry about it in general, there is only one other
caller of setjmp in the kernel, and the setjmp() man page
explicitly mentions this problem and the workaround.

     Arnd