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 68A52315793; Tue, 24 Mar 2026 08:20:24 +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=1774340424; cv=none; b=Z6co55xkIGbECr1psVpbJnPY8mjcaoIZT5VN+lBQZtKCFdQLkxNkRRGZ3o75ibxj/JoeCfEDvgDxsfQj1BM7Lzlo7JL+v6eJKqoiKvEj7+n1IiJUcd6himwvros9MKpRJjWKbdCrj1WypBC3AQ1RbqdoB1E7bx7f77iNLHmlZA0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774340424; c=relaxed/simple; bh=B3kyXlmEq13caqQrNaU86Hb/JRfeTL9rcrJV9xcXokw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=VJwaWyVqZC672tvCH3uemDPcM87mzbxavSfeuYNAPqq6mjNvmF/4PwincQyvp1KNuOoGBqrZXmPVHKSkyISPrFQWa42CwpHwPg86d6LAWKVW47RsHH6mRONlLmy5M5cQZf1wJtGF/hFaarzGRAnxbItE2A9b+XdRjwtKNtvc6ZU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=SVnjhA/S; 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="SVnjhA/S" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2A48AC19424; Tue, 24 Mar 2026 08:20:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1774340423; bh=B3kyXlmEq13caqQrNaU86Hb/JRfeTL9rcrJV9xcXokw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=SVnjhA/S24RkfOLk24Js6bYFNLDZ/CMgcY5Xu5WUp5rIEAjvRgyhnm7NmM0nX41Ey +CyJoTys0eXf7tVjeN9Ef8dqfiUb1eN26U5K5zj8OeEF1lghIsu/GtZtn0h2CnCLS1 5YADBioRSmBZTvTjzz5f6tqRT1mgHix4a6QZLveM= Date: Tue, 24 Mar 2026 09:20:01 +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: <2026032411-paramount-lapdog-41e6@gregkh> References: <20260322121026.869758-1-sashal@kernel.org> <20260322121026.869758-4-sashal@kernel.org> <2026032309-jargon-stalling-28c2@gregkh> Precedence: bulk X-Mailing-List: linux-fsdevel@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: On Mon, Mar 23, 2026 at 07:58:50PM -0400, Sasha Levin wrote: > > 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? > > That is correct, for now. > > I'm only trying to tackle syscalls to begin with, and since no syscalls live in > modules, we have no need for module support. We used to support syscalls in modules, but thankfully that is now gone. But, how will this work for stuff like usbfs ioctls? That is a module, and our uapi is, by far, in drivers through ioctl "hell" and that would be great to be able to document through all of this. Will that just not be in the debugfs api? thanks, greg k-h