Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2343540pxb; Tue, 23 Feb 2021 05:00:12 -0800 (PST) X-Google-Smtp-Source: ABdhPJzSXhgSLzsg/HJ5Msbygmq8yEc3kkiJ5t+vIelewyr5O4ysbCfm+fNZ0H/IT0HLO+ZwDnnA X-Received: by 2002:a17:906:4442:: with SMTP id i2mr26374914ejp.41.1614085212177; Tue, 23 Feb 2021 05:00:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614085212; cv=none; d=google.com; s=arc-20160816; b=aAWu4t2ZAsvvl6PzWTQMK+FRtyuYqY47GL376aEmJmWjpOv01/1dk2c27S1ZgwW8C3 9HAHXvOfF4JjCeoD4getlx7j2cAivE9FQeeDo0MCdf02IAc+QgepOybRtcogesKK7Jd8 XNa+3Q5vCbYjzraIOKK2aSSy8sFTcOqOpEWoC/92o0PxMv1DZRNrQzVPpPtiNBchRKmL 1d3PjpL3vAhwdzP0v5AkMFWk70mFw/BhswaJecPktBLqqyED+javtHQqEBGzHUc3pwra Hv28o3QXnwmyjCsYyO4WklRGb7bY2Zq0mWy0zDwZVvcpvaZTYcnxEO9cE4Wbuggxj7wZ M2+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=K2Z+2VSPg7+sHFh8HFFj48DBY6HY3D0m21RTVvIi500=; b=U0PQpmQJRKlFW8rXUSHE1wbvDnVD6j2pKmjtl73ZM/BSNoNbP6ZHRUUswJtN90Z7hH CIFd+vlbbZzgRsyqEQvzvEG44IznPZjU3iCAJCJ6+yLAc1yLqqcfSjLNZ8wvuZVcb/xg EZCc9NpSfG0U9kjKofRq82P1XlAzY4jUMsuK8FF9C936r0lETQzOOZBAcfBt4AE0ZmBo ZYCbeBLmdFhIo6Ncvmd2CV8LXuajtyWSTQ2ZuWvcyu5mY5NK1vKhGKl+QeAAly0l9BoE BoX5xUjLGHkk8EhAoYnBx0S1vSHbmDjkyjiMr2ruL3o4sL4PtQZZqTbSdwhMXnw2gJkf RvHg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id lw11si22861ejb.42.2021.02.23.04.59.46; Tue, 23 Feb 2021 05:00:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232689AbhBWM6L (ORCPT + 99 others); Tue, 23 Feb 2021 07:58:11 -0500 Received: from elvis.franken.de ([193.175.24.41]:49459 "EHLO elvis.franken.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232611AbhBWM5v (ORCPT ); Tue, 23 Feb 2021 07:57:51 -0500 Received: from uucp (helo=alpha) by elvis.franken.de with local-bsmtp (Exim 3.36 #1) id 1lEXFU-0002LK-00; Tue, 23 Feb 2021 13:57:08 +0100 Received: by alpha.franken.de (Postfix, from userid 1000) id 986DDC07AD; Tue, 23 Feb 2021 13:21:44 +0100 (CET) Date: Tue, 23 Feb 2021 13:21:44 +0100 From: Thomas Bogendoerfer To: Alexander Lobakin Cc: Arnd Bergmann , Nathan Chancellor , Nick Desaulniers , Sami Tolvanen , Huacai Chen , Pei Huang , Kees Cook , Fangrui Song , Jiaxun Yang , Corey Minyard , kernel test robot , linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org Subject: Re: [PATCH mips-fixes] vmlinux.lds.h: catch even more instrumentation symbols into .data Message-ID: <20210223122144.GA7765@alpha.franken.de> References: <20210223113600.7009-1-alobakin@pm.me> <20210223113600.7009-2-alobakin@pm.me> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210223113600.7009-2-alobakin@pm.me> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 23, 2021 at 11:36:41AM +0000, Alexander Lobakin wrote: > > LKP caught another bunch of orphaned instrumentation symbols [0]: > > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > `init/main.o' being placed in section `.data.$LPBX1' > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > `init/main.o' being placed in section `.data.$LPBX0' > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > `init/do_mounts.o' being placed in section `.data.$LPBX1' > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > `init/do_mounts.o' being placed in section `.data.$LPBX0' > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > `init/do_mounts_initrd.o' being placed in section `.data.$LPBX1' > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > `init/do_mounts_initrd.o' being placed in section `.data.$LPBX0' > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > `init/initramfs.o' being placed in section `.data.$LPBX1' > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > `init/initramfs.o' being placed in section `.data.$LPBX0' > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > `init/calibrate.o' being placed in section `.data.$LPBX1' > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > `init/calibrate.o' being placed in section `.data.$LPBX0' > > > > [...] > > > > Soften the wildcard to .data.$L* to grab these ones into .data too. > > > > [0] https://lore.kernel.org/lkml/202102231519.lWPLPveV-lkp@intel.com > > > > Reported-by: kernel test robot > > Signed-off-by: Alexander Lobakin > > --- > > include/asm-generic/vmlinux.lds.h | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > Hi Thomas, > > This applies on top of mips-next or Linus' tree, so you may need to > rebase mips-fixes before taking it. > It's not for mips-next as it should go into this cycle as a [hot]fix. > I haven't added any "Fixes:" tag since these warnings is a result > of merging several sets and of certain build configurations that > almost couldn't be tested separately. no worries, mips-fixes is defunct during merge windows. I'll send another pull request to Linus and will add this patch to it. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]