From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B1F00C5517A for ; Tue, 3 Nov 2020 18:12:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 60F9820780 for ; Tue, 3 Nov 2020 18:12:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604427145; bh=r1Gq9OQ/Y9ZaxyS3xFLYB8+pOy7r+3M+D+op3/q0gyg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=Mh+n/NhZNvRvt2jLbGvUh06cby440Gs55sRgs4RT7KXuVfe/MZsI3A39vvIGHAkpi Urj73U/chDZt81CL8Vh6q+qpqwQpjQiBZlRtBOJk9pJ8NZSy7lhvX9Uxyi7oWMTo0f 0LXwPnJyr1p6cog6b5Tei5SZSokK/juHWcyMSpn8= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729089AbgKCSMD (ORCPT ); Tue, 3 Nov 2020 13:12:03 -0500 Received: from mail-lj1-f195.google.com ([209.85.208.195]:33663 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728855AbgKCSMD (ORCPT ); Tue, 3 Nov 2020 13:12:03 -0500 Received: by mail-lj1-f195.google.com with SMTP id m8so14034523ljj.0 for ; Tue, 03 Nov 2020 10:12:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=76fujNvmaDU5izlocC2iDYMlwXY99PLp9hN2X9PjG0k=; b=o+woJuU6uxbpyJXKPP+YLgClWOcEiD4sxf0m+B2MJm5dL16dSWj3A2s4ImgR4on5B9 pZP2WetuEaxF4loSh9hz6kLMwOBkizbvsAqlljrzx4VEMIiUFWxRPFwlUs+cBBPWzmes cgD0rbSD7uOVpsbVh6Qllr3FFN5AA/RNCcL1Dj9CtDvnS7z1zkMqHSQY/Wt/UG12lKhu kyGP2ede5zTWNPvC0ZUNAJliVkoE0QFpbe693xyQKHRdYt0VQvv8Kg2zSuH2PDc7fu0B ev6yyUHneT1GeYviC5yzBCli0oleTW3ilwGIihxQ0ZWlRddd0GT+rNMovwQNBNa35FXa xDDw== X-Gm-Message-State: AOAM532PWrtiIPghH5SFw2T2roZGTPQt9c3WnysRPEWPJKGC8/+2v+Fv 7xf8XyobCvOKMdGIO8BL1zs= X-Google-Smtp-Source: ABdhPJw6rQq0Fh3kcxIva7KSE+qsd1+5egDz952MKuJgRAuL68zhNMHWuZwjaNwDpdN2HgxJoFCTxQ== X-Received: by 2002:a2e:7617:: with SMTP id r23mr9525714ljc.0.1604427120842; Tue, 03 Nov 2020 10:12:00 -0800 (PST) Received: from xi.terra (c-beaee455.07-184-6d6c6d4.bbcust.telenor.se. [85.228.174.190]) by smtp.gmail.com with ESMTPSA id a25sm3688646lfo.141.2020.11.03.10.11.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 Nov 2020 10:11:59 -0800 (PST) Received: from johan by xi.terra with local (Exim 4.93.0.4) (envelope-from ) id 1ka0mn-0002rR-Jv; Tue, 03 Nov 2020 19:12:01 +0100 From: Johan Hovold To: linux-kernel@vger.kernel.org Cc: Linus Torvalds , Rob Herring , Frank Rowand , Greg Kroah-Hartman , Jessica Yu , Nick Desaulniers , Arnd Bergmann , Geert Uytterhoeven , Dmitry Torokhov , David Miller , Jakub Jelinek , Peter Zijlstra , Thomas Gleixner , Steven Rostedt , Daniel Kurtz , linux-arch@vger.kernel.org, linux-m68k@lists.linux-m68k.org, Johan Hovold , stable Subject: [PATCH 1/8] of: fix linker-section match-table corruption Date: Tue, 3 Nov 2020 18:57:04 +0100 Message-Id: <20201103175711.10731-2-johan@kernel.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20201103175711.10731-1-johan@kernel.org> References: <20201103175711.10731-1-johan@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-m68k@vger.kernel.org Specify type alignment when declaring linker-section match-table entries to prevent gcc from increasing alignment and corrupting the various tables with padding (e.g. timers, irqchips, clocks, reserved memory). This is specifically needed on x86 where gcc (typically) aligns larger objects like struct of_device_id with static extent on 32-byte boundaries which at best prevents matching on anything but the first entry. Here's a 64-bit example where all entries are corrupt as 16 bytes of padding has been inserted before the first entry: ffffffff8266b4b0 D __clk_of_table ffffffff8266b4c0 d __of_table_fixed_factor_clk ffffffff8266b5a0 d __of_table_fixed_clk ffffffff8266b680 d __clk_of_table_sentinel And here's a 32-bit example where the 8-byte-aligned table happens to be placed on a 32-byte boundary so that all but the first entry are corrupt due to the 28 bytes of padding inserted between entries: 812b3ec0 D __irqchip_of_table 812b3ec0 d __of_table_irqchip1 812b3fa0 d __of_table_irqchip2 812b4080 d __of_table_irqchip3 812b4160 d irqchip_of_match_end Verified on x86 using gcc-9.3 and gcc-4.9 (which uses 64-byte alignment), and on arm using gcc-7.2. Note that there are no in-tree users of these tables on x86 currently (even if they are included in the image). Fixes: 54196ccbe0ba ("of: consolidate linker section OF match table declarations") Fixes: f6e916b82022 ("irqchip: add basic infrastructure") Cc: stable # 3.9 Signed-off-by: Johan Hovold --- include/linux/of.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/linux/of.h b/include/linux/of.h index 5d51891cbf1a..af655d264f10 100644 --- a/include/linux/of.h +++ b/include/linux/of.h @@ -1300,6 +1300,7 @@ static inline int of_get_available_child_count(const struct device_node *np) #define _OF_DECLARE(table, name, compat, fn, fn_type) \ static const struct of_device_id __of_table_##name \ __used __section("__" #table "_of_table") \ + __aligned(__alignof__(struct of_device_id)) \ = { .compatible = compat, \ .data = (fn == (fn_type)NULL) ? fn : fn } #else -- 2.26.2