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 Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A4A73EB64DC for ; Mon, 26 Jun 2023 03:21:37 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=Lgqx4Tr0; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4QqCmw0Srbz30XZ for ; Mon, 26 Jun 2023 13:21:36 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=Lgqx4Tr0; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=2604:1380:4641:c500::1; helo=dfw.source.kernel.org; envelope-from=jpoimboe@kernel.org; receiver=lists.ozlabs.org) Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4QqClv16NHz2ykB for ; Mon, 26 Jun 2023 13:20:43 +1000 (AEST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 7863360C6D; Mon, 26 Jun 2023 03:20:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A60E1C433C8; Mon, 26 Jun 2023 03:20:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1687749638; bh=0j42pFaHzOUI6swjUOLjkgy+NNh2RUt8s6H5ez2k5IM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Lgqx4Tr02Iw9n2yo+uU0QlSokM0TVEq9+ArAqcY9hQEFnVFq4ks++nrhAS3lR2TA5 uu8czI9zAZg8kicW5bE+OlAFIaJWeudWIOR358LrAYgfnP/irTMaL2gn8aGxjV5jw8 M3LXLctJ024YN17riX4Z9Chx+B7cg+0AtR7pqZKrLusTldNVnQwQinz+ZvE0qCYUyz hdSgm3sqlug63AAFT+bTkfnJPK2UFj3ut75xqqNnGaJiZnlrH474nw5PPkyc+O9pYU LdIsZOw4wDJZEnVWvVRmO22MWwH7oUfdg5/phrjwIDRCxdCUuApOfEA9WJwCWnyaFM i7bIbbup2JaxA== Date: Sun, 25 Jun 2023 20:20:36 -0700 From: Josh Poimboeuf To: Christophe Leroy Subject: Re: [PATCH] objtool: Make 'sec-address' always on Message-ID: <20230626032036.m7vdthsguezm52wa@treble> References: <202306241520.4jIgEhK4-lkp@intel.com> <2bd6c377-51ac-e2e2-6fcf-9c9b0f96f9cf@csgroup.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <2bd6c377-51ac-e2e2-6fcf-9c9b0f96f9cf@csgroup.eu> X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Peter Zijlstra , "oe-kbuild-all@lists.linux.dev" , "linuxppc-dev@lists.ozlabs.org" , kernel test robot , "linux-kernel@vger.kernel.org" Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Sat, Jun 24, 2023 at 08:30:48AM +0000, Christophe Leroy wrote: > >>> vmlinux.o: warning: objtool: ibt_selftest+0x14 (.text+0x92b54): sibling call from callable instruction with modified stack frame > > vmlinux.o: warning: objtool: .altinstr_replacement+0x19a4: redundant UACCESS disable > > vmlinux.o: warning: objtool: iovec_from_user.part.0+0xb1 (.text+0x1c47761): call to copy_iovec_from_user.part.0() with UACCESS enabled > > vmlinux.o: warning: objtool: ibt_selftest+0x1e (.text+0x92b5e): return with modified stack frame > > > > I can't really see any link between that warning and the changes in the > patch. I suspect it's a pre-existing warning, but because the patch made a change to the default formatting (adding .text+off), it looks like a new warning to the bots. -- Josh