Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp149476pxb; Tue, 10 Nov 2020 23:21:26 -0800 (PST) X-Google-Smtp-Source: ABdhPJwcen3BpkqgC+4orWoc2BNtzVM7aiX4PBjhA4dLX5NGBu7nYDv35oUe+MV8hheDqb2B0kCC X-Received: by 2002:a05:6402:b28:: with SMTP id bo8mr25520468edb.57.1605079286410; Tue, 10 Nov 2020 23:21:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605079286; cv=none; d=google.com; s=arc-20160816; b=AtMnunwuTaG+9uteHtlrdghrI3rHVxrLk4NHODfYb8NPGp/JOk0n5hwW9EswaEWdz5 ek5FRhK3hbIYmBVqmHDp964yWl7CR7oUOCJT1Woxq3KuILEJ0cFufpFtDkGT2IPBckaN /LMvVzTZGNDbVMlSPYJMUgkHxNFWjo83yWaefQaoFH9IAPp1F8e3pRmR9wTQbJ2mUxW9 ImkFrjfbh5S+mISKL3zkIKfzD41ZMx7fZWXmQgcMIwDlKdi2yK0QfImunCI8OXoDiuZr 2QTYkCsHVct6iuMfi9aAhCAV86lpoSdYXVBRxy8QP0H4wHFsCn3K/5rv93f7Wp+ZW3Wv jCZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=CAQVZqtxtSOwUyW8EqmnyD/K8yMmd2zuMQylnTG3pAg=; b=W28w3EgLhwHhPF00jO5Nyt6EtF2ODfUF36y2zMaCKExgtSzX9JAa0gzOWfSA7cpi/p ifY/DEO+C2jrpd+Wz94f0oXkCWRD8payYBXDm2PW3xpMCdXElZYV/nC4EoI/9HXz8KBr IkDnGSoTtVhTN+8rlXr7dAvhA74DoJx50j+f+TWgD1DfqR9tusCz82O8OTbsFDNdt3FD z30qosrQLaoCUtAVFlpgC8gllUDf+wYUx+jCKqzqekkSH7+mM94UDNAfW8eaiPYE1GQQ DP3V8g14DstwHZI6vH+DpmbjoWLOgv4KGuplAyUR1lSZTQqkrkvbgq2YKoR/yVswynHD wXUA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=guq6CmAi; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cc10si934249edb.156.2020.11.10.23.20.50; Tue, 10 Nov 2020 23:21:26 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=guq6CmAi; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726151AbgKKHT1 (ORCPT + 99 others); Wed, 11 Nov 2020 02:19:27 -0500 Received: from mail.kernel.org ([198.145.29.99]:39160 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726038AbgKKHT1 (ORCPT ); Wed, 11 Nov 2020 02:19:27 -0500 Received: from mail-ot1-f43.google.com (mail-ot1-f43.google.com [209.85.210.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 573D721D7F; Wed, 11 Nov 2020 07:19:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605079166; bh=CAQVZqtxtSOwUyW8EqmnyD/K8yMmd2zuMQylnTG3pAg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=guq6CmAiRLq4R57MddTf3q6FwEUAeGMSddkiHps3KcyrTTkyZgtGjcSmcOIsYZj0M RIXnQSaNESRz5bdvVKxisfCpa82vtPflR7f31OGH6AfHdtg9UUX+aLE+fkQkqYSZm9 ibIc3iuUQl0WCalegb6OGnkKiHD0ZFDeAI5/tccU= Received: by mail-ot1-f43.google.com with SMTP id i18so1301416ots.0; Tue, 10 Nov 2020 23:19:26 -0800 (PST) X-Gm-Message-State: AOAM531102nF+TmYgHnqKLijp4Ay8DngYbSXrdz5bO/NrSJ9+SJv0zhU Q32FXfif3rTNKqT927zHMOBOHCbDykmPTOvtOQQ= X-Received: by 2002:a05:6830:214c:: with SMTP id r12mr7308063otd.90.1605079165545; Tue, 10 Nov 2020 23:19:25 -0800 (PST) MIME-Version: 1.0 References: <20201022073307.GP2628@hirez.programming.kicks-ass.net> <133aa0c8c5e2cbc862df109200b982e89046dbc0.camel@perches.com> In-Reply-To: <133aa0c8c5e2cbc862df109200b982e89046dbc0.camel@perches.com> From: Ard Biesheuvel Date: Wed, 11 Nov 2020 08:19:13 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH -next] treewide: Remove stringification from __alias macro definition To: Joe Perches , Russell King Cc: Peter Zijlstra , Thomas Gleixner , Borislav Petkov , X86 ML , "H. Peter Anvin" , Miguel Ojeda , Marco Elver , Dmitry Vyukov , Herbert Xu , "David S. Miller" , Andrey Ryabinin , Alexander Potapenko , Andrew Morton , Nick Desaulniers , Linux Kernel Mailing List , linux-efi , kasan-dev , Linux Crypto Mailing List , linux-mm Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org (+ Russell) On Thu, 22 Oct 2020 at 18:20, Joe Perches wrote: > > On Thu, 2020-10-22 at 09:33 +0200, Peter Zijlstra wrote: > > On Wed, Oct 21, 2020 at 11:58:25AM -0700, Joe Perches wrote: > > > Like the __section macro, the __alias macro uses > > > macro # stringification to create quotes around > > > the section name used in the __attribute__. > > > > > > Remove the stringification and add quotes or a > > > stringification to the uses instead. > > > > There's a complete lack of rationale for this change. > > I'll eventually post V2. > I'm waiting to see if there are more comments. > > As I wrote in reply to Ard: > > https://lore.kernel.org/lkml/1cecfbfc853b2e71a96ab58661037c28a2f9280e.camel@perches.com/ > > Using quotes in __section caused/causes differences > between clang and gcc. > > https://lkml.org/lkml/2020/9/29/2187 > > Using common styles for details like this is good. > This patch is now causing problems in the ARM tree, because some new uses of __alias() have been queued (for KASAN), and since this is a non-backwards compatible change, we have to choose between breaking the maintainer's tree or breaking -next (given that the change has been pulled in there now) I am still not convinced we need this change, as I don't see how the concerns regarding __section apply to __alias. But if we do, can we please use the same approach, i.e., revert the current patch, and queue it again after v5.11-rc1 with all new occurrences covered as well?