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 0CB02C05027 for ; Fri, 10 Feb 2023 00:16:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229960AbjBJAQL (ORCPT ); Thu, 9 Feb 2023 19:16:11 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45250 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229953AbjBJAQK (ORCPT ); Thu, 9 Feb 2023 19:16:10 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5F9565DC3F for ; Thu, 9 Feb 2023 16:16:08 -0800 (PST) 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 dfw.source.kernel.org (Postfix) with ESMTPS id EF3CA61C11 for ; Fri, 10 Feb 2023 00:16:07 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id ED9B4C433EF; Fri, 10 Feb 2023 00:16:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1675988167; bh=kBUfv1e2Y5mGsh7sGrvr1JPQtJufLYGEc7xCRzO9Wmw=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=UuU4SPATQCjbwZDXtDJfOFsx4jffwj36GIfHgeKfU24XtTAIp7+E7bkDRoUVxa6JM Nrx0wdbfdlTjKTD5cYPFzfPFiRnbeoAg1lfMEFIe+H/3f38Z6XtM05gMwGd8mIue9K bOX+4LV5exdyl/toUhLhapXIG2hPB+Zmi4hN56wEU8KPAV23bMImlCr0cIV/tY7XOF YRYoa2o3GWStue4Me+EBteYC4J/LzjYPg+cDgDHUrF3Ogj5s69Uix+pDejb4MHHAlo KGraZBWP9UhDYWBaMDJXV82ktnGnujieKwBSzDGHWWNnO9wQ9au1SuUqU/Ijlpi9uE bkkm/am4v4E1A== Date: Thu, 9 Feb 2023 16:16:06 -0800 From: Jakub Kicinski To: Kim Phillips Cc: Jiri Pirko , , , , , , , , , Subject: Re: [patch net-next 0/7] devlink: params cleanups and devl_param_driverinit_value_get() fix Message-ID: <20230209161606.79f064ae@kernel.org> In-Reply-To: <34be65a9-a741-7e4e-c7f3-a80d3e660528@amd.com> References: <20230209154308.2984602-1-jiri@resnulli.us> <81b9453b-87e4-c4d4-f083-bab9d7a85cbe@amd.com> <20230209133144.3e699727@kernel.org> <34be65a9-a741-7e4e-c7f3-a80d3e660528@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, 9 Feb 2023 16:37:13 -0600 Kim Phillips wrote: > On 2/9/23 3:31 PM, Jakub Kicinski wrote: > > On Thu, 9 Feb 2023 15:05:46 -0600 Kim Phillips wrote: > >> Is there a different tree the series can be rebased on, until net-next > >> gets fixed? > > > > merge in net-next, the fix should be there but was merged a couple of > > hours ago so probably not yet in linux-next > > I=Ok, I took next-20230209, git merged net-next/master, fixed a merge > conflict to use the latter net-next/master version: > ...and unfortunately still get a splat on that same Rome system: Alright, so that's the splat I'm guessing the patch set was supposed to address. Can you confirm that you're testing next-20230209 + net-next/master + this patches from the list ? The previous crash (which I called "fixed in net-next") was an unrelated bug in the socket layer. You still have to apply the patches from the list to fix the devlink warning.