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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EF65CC433EF for ; Tue, 25 Jan 2022 15:49:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1350022AbiAYPtV (ORCPT ); Tue, 25 Jan 2022 10:49:21 -0500 Received: from ams.source.kernel.org ([145.40.68.75]:33970 "EHLO ams.source.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1582332AbiAYPq4 (ORCPT ); Tue, 25 Jan 2022 10:46:56 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id E71A0B8189A; Tue, 25 Jan 2022 15:46:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DAF88C340E0; Tue, 25 Jan 2022 15:46:49 +0000 (UTC) Date: Tue, 25 Jan 2022 10:46:48 -0500 From: Steven Rostedt To: Chuck Lever III Cc: Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List , Anna Schumaker , Trond Myklebust , Linux NFS Mailing List Subject: Re: linux-next: runtime warning in next-20220125 Message-ID: <20220125104648.7ecce604@gandalf.local.home> In-Reply-To: References: <20220125160505.068dbb52@canb.auug.org.au> <20220125162146.13872bdb@canb.auug.org.au> <20220125100138.0d19c8ca@gandalf.local.home> <20220125103607.2dc307e2@gandalf.local.home> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Tue, 25 Jan 2022 15:38:22 +0000 Chuck Lever III wrote: > > This should fix it: > > > > I'll make it a real patch and start running it through my tests. > > Should this be squashed into the patch that adds __get_sockaddr() ? > > I have an updated version of that patch that applies on kernels > that have __rel_dynamic_array. Heh, I thought the patch was already in mainline. I just posted the fix. Just add it to your queue. No need to squash it. You can remove the Fixes: tag, as it may not reference the right commit. -- Steve