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 1C58A3B2FEF; Mon, 23 Mar 2026 15:18:49 +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=1774279129; cv=none; b=rne/jwOse9HAPD/4Q7ZEzh/GIUdAN7Z9DmAfgpUcOEO2WmSyd90K4kW0vV+6rR3Y6yEstCzfySu3/AUQ8LvVnfcyWyKRRdenuh+tb+32Ak1SpoSvTFWQjlqg1TKqRstFRqlyS49cWDFOpPQJD9Mxbxy4oJ0Cs+rxATIov4vPiQc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774279129; c=relaxed/simple; bh=pbXYxhzMz1CXELl5GAMQGqn3VS0cXr+c3mpboLxq4hA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=VmSXXN8c2WtH3wQQynNMPQ/4OJ1Uiby0h0yibazGqP0nyC08VKPKrqEkc2mYo/CrLemmjYefUxJhEgk+j+9xtLRyyydgJDuY1dBsKpzwQVR5QpZnJ8ozea5zTzisYi+u0qHwyFw4HtTHUCBw2oZbBuStV0Gh2a7JNJHtZkfRpFc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=CJ5hRoCK; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="CJ5hRoCK" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 72CCBC4CEF7; Mon, 23 Mar 2026 15:18:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1774279129; bh=pbXYxhzMz1CXELl5GAMQGqn3VS0cXr+c3mpboLxq4hA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CJ5hRoCKajUHc8KKiBAP2gYu1mVfUOfWRR6xc1nDC/KmFM8FTX4OS4y9Nfd8vhfAi J23Pc2XVcANhfXnjGTAo+urvXkyrzow5gFm2OspORm1S/DdOvkBQZXlQYlKUBUvn28 tpGOuXncYvNz+HkAvROWP9p1b6eqV6ah8hy5xkd8= Date: Mon, 23 Mar 2026 14:52:58 +0100 From: Greg Kroah-Hartman To: Sasha Levin Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kbuild@vger.kernel.org, linux-kselftest@vger.kernel.org, workflows@vger.kernel.org, tools@kernel.org, x86@kernel.org, Thomas Gleixner , "Paul E . McKenney" , Jonathan Corbet , Dmitry Vyukov , Randy Dunlap , Cyril Hrubis , Kees Cook , Jake Edge , David Laight , Askar Safin , Gabriele Paoloni , Mauro Carvalho Chehab , Christian Brauner , Alexander Viro , Andrew Morton , Masahiro Yamada , Shuah Khan , Ingo Molnar , Arnd Bergmann Subject: Re: [PATCH v2 3/9] kernel/api: add debugfs interface for kernel API specifications Message-ID: <2026032309-jargon-stalling-28c2@gregkh> References: <20260322121026.869758-1-sashal@kernel.org> <20260322121026.869758-4-sashal@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260322121026.869758-4-sashal@kernel.org> On Sun, Mar 22, 2026 at 08:10:17AM -0400, Sasha Levin wrote: > Add a debugfs interface to expose kernel API specifications at runtime. > This allows tools and users to query the complete API specifications > through the debugfs filesystem. > > The interface provides: > - /sys/kernel/debug/kapi/list - lists all available API specifications > - /sys/kernel/debug/kapi/specs/ - detailed info for each API > > Each specification file includes: > - Function name, version, and descriptions > - Execution context requirements and flags > - Parameter details with types, flags, and constraints > - Return value specifications and success conditions > - Error codes with descriptions and conditions > - Locking requirements and constraints > - Signal handling specifications > - Examples, notes, and deprecation status > > This enables runtime introspection of kernel APIs for documentation > tools, static analyzers, and debugging purposes. > > Signed-off-by: Sasha Levin Debugfs logic looks sane, nice. But this only works if the kabi stuff is built into the kernel image, right? This doesn't work if any of these abi sections are in a module or am I missing that logic here? thanks, greg k-h