Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) client-ip=23.128.96.32;
Date:   Sat, 4 Nov 2023 14:56:34 +0100
From:   Willy Tarreau <w@1wt.eu>
To:     Thomas =?iso-8859-1?Q?Wei=DFschuh?= <linux@weissschuh.net>
Cc:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org,
        Zhangjin Wu <falcon@tinylab.org>,
        Yuan Tan <tanyuan@tinylab.org>
Subject: Re: [PATCH RFC] misc/pvpanic: add support for normal shutdowns
Message-ID: <ZUZNkpEiHHWsmZhT@1wt.eu>
References: <20231104-pvpanic-shutdown-v1-1-5ee7c9b3e301@weissschuh.net>
 <2023110407-unselect-uptight-b96d@gregkh>
 <365bbe1f-5ee8-40fe-bec0-53d9e7395c18@t-8ch.de>
 <2023110431-pacemaker-pruning-0e4c@gregkh>
 <59ed7f70-2953-443e-9fa5-d46c566e4a08@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: <59ed7f70-2953-443e-9fa5-d46c566e4a08@t-8ch.de>
Precedence: bulk

On Sat, Nov 04, 2023 at 02:53:37PM +0100, Thomas Wei?schuh wrote:
> > > The real reason probably doesn't matter today as the header propably
> > > can't be dropped from Linux anyways for compatibility reasons.
> > > 
> > > > And if they need to be here, why not use the proper BIT() macro for it?
> > > 
> > > This was for uniformity with the existing code.
> > > I can send a (standalone?) patch to fix it up.
> > 
> > If we keep it, sure, that would be nice.  But let's try to drop it if
> > possible :)
> 
> It will break the mentioned scripts/update-linux-headers.sh from qemu.
> 
> 
> Note:
> 
> BIT() is part of include/vdso/bits.h which is not part of the
> uapi. How is it supposed to work?
> Some other uapi header also use BIT() but that seems to work by accident
> as the users have the macro defined themselves.

Be careful here, we don't want to expose this kernel macro to userland,
it would break programs that define their own (possibly different) BIT
macro. BIT() is used in kernel headers but we should not presume that
it is available from userland.

Willy