From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CFABA3A7831 for ; Thu, 23 Apr 2026 17:26:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776965214; cv=none; b=meaZggH0/xScJmAwId/5hq/cWFNPrNQnQa+qQOLORapJrPUsTMZ4K5UetmlXAmI+YbbFwV63dTv6AOHBkGrlW4TKNFU3m7t5bcHkbOHFGyFwsQgD0nERIXqB1VNO/Ehsqj9ky1HqxUSm3VC+79zgzvjNU8XbRwxmd8iOwwZ5MRU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776965214; c=relaxed/simple; bh=dr+GNM9G7gB9AckXDFpmrjv7oY9xSK9S71BPvvX7yxc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=ZaGOMOg2/aU9Y8iAxOKG38U1n4htQKv9s2mwrqeTe4zV68m0O8Y8gYAaoeHVCykS7To4Qz4wl6XyfjGGBWO1OwRHwGKZPYbmnDOQBR5hGBQvnIqgLawNa70A2VtaDnyqm+d99DRMzOr66B0H0w4/I1cAhaOMXf6WubZvqZNIyLM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=TEPExy6f; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="TEPExy6f" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C6A44C2BCB3; Thu, 23 Apr 2026 17:26:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1776965214; bh=dr+GNM9G7gB9AckXDFpmrjv7oY9xSK9S71BPvvX7yxc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=TEPExy6fCtUjk+WMOQowg/FEdn9EIJ5M/z9pNINSIwmXVNZk+G8muQg22zOE9dJAx PG6rCfBGSYfMbpLdpA4/la9K1vI9KmP7tNm/xWrkh08qZXXev6RF+dMgMXtNmgfEQa eOl4VU1c7I60m4bOKQeKaZw7g0NKD1EamexWRV6MwwJ00J2Pti+/wL3f++BW3GHaaS fYqTFefTqoTWVMn8B9A7k0cIJqFnaGZHaMCBeMb6IyuSeuDlJW2FyBMrb0Onwb+WxC 4UxbrdU4HciZoQtl9VIx6Eu4xPTeJHrOQTWsGIh1sFFXqCHN50/2MVwp/GCQ7Fh0pz l9QSVO+UjcDXg== Message-ID: <13219731-89be-4c49-8842-69935c21eb2f@kernel.org> Date: Thu, 23 Apr 2026 13:26:52 -0400 Precedence: bulk X-Mailing-List: linux-nfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] NFSD: Put cache get-reqs dump attrs under reply To: Thorsten Leemhuis , NeilBrown , Jeff Layton , Olga Kornievskaia , Dai Ngo , Tom Talpey Cc: linux-nfs@vger.kernel.org, Chuck Lever References: <20260423171732.322623-1-cel@kernel.org> Content-Language: en-US From: Chuck Lever Organization: kernel.org In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 4/23/26 10:24 AM, Thorsten Leemhuis wrote: > On 4/23/26 19:17, Chuck Lever wrote: >> From: Chuck Lever >> >> The new get-reqs dump operations added to sunrpc_cache.yaml and >> nfsd.yaml place the "requests" nested attribute under dump.request. >> A netlink dump carries an empty request; its payload travels back >> in the reply. Because the spec names no reply attributes, the YNL >> C code generator synthesizes a forward reference to a >> _rsp struct that is never defined, breaking any consumer of >> these specs. >> >> This first surfaced when Thorsten Leemhuis built tools/net/ynl >> against -next: > > Thx for the quick fix, this makes things work. In case anybody cares: > > Tested-by: Thorsten Leemhuis Thanks! Applied to nfsd-next. -- Chuck Lever