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 583523D9DDE; Wed, 18 Mar 2026 14:14:14 +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=1773843254; cv=none; b=WwhB3ZJuumMzyfQglF1UOr1UkQaBQScY1DaW34pax17cyUAHU82RjRiFEZ0UEo92tzxSHtEZMvOGb5kdgVPSE7HkJc1Y+Vvh4AXrnJVJasFM6p/Vr7IAvPWUMfo6abj+SVG3otAUBQG//h8J2ioG8biFPlMLVrwPK9AQnw5J+xQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773843254; c=relaxed/simple; bh=HPOd8av0zkvPB5Jq+2D8kTe1uRlAAJQLKHhW1me+kbA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=QQF9VAqs4fjArXftBzY+gvBxLjajfU5ato015n/YEwyGRuBxNQHnZWLl1cQuYOwRmYLDmkwfNuIbTGazXsuP22/P1KL6SukHNDYsVzunpspKW/XKaCM9iva0QarfYaSryc9Q1dra2k4Q0nz2HeQdmyF/TZmn4wAYUOy93oWpa+U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=NzdkQVwb; 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="NzdkQVwb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id F2A4AC19421; Wed, 18 Mar 2026 14:14:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773843254; bh=HPOd8av0zkvPB5Jq+2D8kTe1uRlAAJQLKHhW1me+kbA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=NzdkQVwb82dEzBbXvF70Z1p9D3TneAvmkgYsv9NacC23G0MVhbN9Rx4jWwAjcE5Oh 57DAm4TOA6HEUMNqjgyv6l5dHRi+tCUlSm4xGnfP2AVOcjje97jxMW7DeCOA4EbU5t k61o5rlp6u/6m/EwndDElJndj887uX3ri786McXpoN9ITA+Za5BQiZ+iCyzO3Pf743 AAMKfn7HrJiYmWXFF8tH6b43Giq4oxvLCd44QsRPacsKIxFddyCKTtEbsfjnNWT2iD 6On1YlVkQMCGJlS3bpB04OlZRh9tUnqxymZfzlF6ccEcl9dblkGxOb8G4krSF/+KZ3 9OnFWRUhNV0nQ== Date: Wed, 18 Mar 2026 10:14:12 -0400 From: Sasha Levin To: Mauro Carvalho Chehab Cc: Jakub Kicinski , 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" , Greg Kroah-Hartman , 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 0/9] Kernel API Specification Framework Message-ID: References: <20260313150928.2637368-1-sashal@kernel.org> <20260314111822.63a2ba4a@kernel.org> <20260318072410.72618011@foz.lan> 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; format=flowed Content-Disposition: inline In-Reply-To: <20260318072410.72618011@foz.lan> On Wed, Mar 18, 2026 at 07:24:10AM +0100, Mauro Carvalho Chehab wrote: >On Sun, 15 Mar 2026 02:36:51 -0400 >Sasha Levin wrote: > >> On Sat, Mar 14, 2026 at 11:18:22AM -0700, Jakub Kicinski wrote: >> >On Fri, 13 Mar 2026 11:09:10 -0400 Sasha Levin wrote: >> >> This enables static analysis tools to verify userspace API usage at compile >> >> time, test generation based on formal specifications, consistent error handling >> >> validation, automated documentation generation, and formal verification of >> >> kernel interfaces. >> > >> >Could you give some examples? We have machine readable descriptions for >> >Netlink interfaces, we approached syzbot folks and they did not really >> >seem to care for those. >> >> Once the API is in a machine-readable format, we can write formatters to >> output whatever downstream tools need. > >Kernel-doc already does that. The way it works is that it handles >kernel-doc markups on two steps: Cool, I'll take a look. We could throw away the source parser in the kapi tool and just use the kerneldoc parse. -- Thanks, Sasha