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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 4C73DECE57A for ; Mon, 9 Sep 2024 14:37:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=IpKVy58ntyJ6Lpje5QwEamUSamP66DJ9hkBokMsPrwU=; b=VCmHmpnHz4VBG4uHrYLb2oxgnL V14ZJ0QRIBte9gU43coqMBEyAwq9VGM0P82Er2/o3XGIPXdSj7dgzLyM2uGedZQtu6QV5osv1WaBs OsvyUWESGUkT6rP2863+1MIy2DF6rUHckDSF30B9mLlHmUpBEPOSpogzuJZpTJ0fqg9Bj5Em1ocw0 LeMBUCXC/KuwxkKzPYqzXCrhWEAxQVNOm30QLa29CH9x7N6M6O/SUsGfiO0dqlr9iTuZFLScx3Oyf ScZLe5F/h7tnXDzGkMepd560s3IXdZP2JrtQZfGN+SO0EpAKJ4M1LxhvmGFDkSQiA9w+GGBZv0OpR JCPo1YZw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1snfVo-00000002JRi-3Qzh; Mon, 09 Sep 2024 14:37:04 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1snfUf-00000002JBJ-3Z4d; Mon, 09 Sep 2024 14:35:58 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id A05215C01A0; Mon, 9 Sep 2024 14:35:48 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A70D5C4CEC5; Mon, 9 Sep 2024 14:35:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1725892551; bh=FZKxzFRyz9Op8EvuEP3cZ3bXtDG2HWdMHdwMe2g59vw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=s1v7sjN3LNrEZl6o3gbfDHJL/srLbCjmQhFTT9iKdRjFei0qYil6a8RA/j709kphV 5dt/5lLGlU4JUEf9HDqXDA13POjv3B1tsyQkm6HxD+ogSgqSlk2+fiDnRPWYcae0le E2/MgNhSOdJxBj5n/kowlKW1eAEzlfAhR66Qb+Qjalo8Nh1XuS01FvByl1Gv6CVO+b cBcNQMbEgp5Am40Xxh57lCui4kSPYtYgztxxydnF+MrtWp6rmQZM8HRjdAeoJKeyWz xkIwGRbL4dHCn0baIOZLiV4oILm1sVaSbi3zL6AqG79UPOnkNp2EDRKThVLbpQr2Bf I2TFUukUj/OqQ== Date: Mon, 9 Sep 2024 15:35:46 +0100 From: Simon Horman To: Marc Kleine-Budde Cc: Nathan Chancellor , kernel@pengutronix.de, Vincent Mailhol , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Heiko Stuebner , linux-can@vger.kernel.org, netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, llvm@lists.linux.dev, patches@lists.linux.dev Subject: Re: [PATCH] can: rockchip_canfd: fix return type of rkcanfd_start_xmit() Message-ID: <20240909143546.GX2097826@kernel.org> References: <20240906-rockchip-canfd-wifpts-v1-1-b1398da865b7@kernel.org> <20240909084448.GU2097826@kernel.org> <20240909-arcane-practical-petrel-015d24-mkl@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240909-arcane-practical-petrel-015d24-mkl@pengutronix.de> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240909_073554_042827_D534F26C X-CRM114-Status: GOOD ( 22.15 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Sep 09, 2024 at 10:57:06AM +0200, Marc Kleine-Budde wrote: > On 09.09.2024 09:44:48, Simon Horman wrote: > > On Fri, Sep 06, 2024 at 01:26:41PM -0700, Nathan Chancellor wrote: > > > With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), > > > indirect call targets are validated against the expected function > > > pointer prototype to make sure the call target is valid to help mitigate > > > ROP attacks. If they are not identical, there is a failure at run time, > > > which manifests as either a kernel panic or thread getting killed. A > > > warning in clang aims to catch these at compile time, which reveals: > > > > > > drivers/net/can/rockchip/rockchip_canfd-core.c:770:20: error: incompatible function pointer types initializing 'netdev_tx_t (*)(struct sk_buff *, struct net_device *)' (aka 'enum netdev_tx (*)(struct sk_buff *, struct net_device *)') with an expression of type 'int (struct sk_buff *, struct net_device *)' [-Werror,-Wincompatible-function-pointer-types-strict] > > > 770 | .ndo_start_xmit = rkcanfd_start_xmit, > > > | ^~~~~~~~~~~~~~~~~~ > > > > > > ->ndo_start_xmit() in 'struct net_device_ops' expects a return type of > > > 'netdev_tx_t', not 'int' (although the types are ABI compatible). Adjust > > > the return type of rkcanfd_start_xmit() to match the prototype's to > > > resolve the warning. > > > > > > Fixes: ff60bfbaf67f ("can: rockchip_canfd: add driver for Rockchip CAN-FD controller") > > > Signed-off-by: Nathan Chancellor > > > > Thanks, I was able to reproduce this problem at build time > > and that your patch addresses it. > > FTR: the default clang in Debian unstable, clang-16.0.6 doesn't support > this. With clang-20 from experimental it works, haven't checked older > versions, though. FTR: I checked using 18.1.8 from here [1][2]. [1] https://mirrors.edge.kernel.org/pub/tools/llvm/ [2] https://mirrors.edge.kernel.org/pub/tools/llvm/files/