From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sparse@vger.kernel.org, sparse@chrisli.org
Subject: add variadic format checking
Date: Fri, 16 Jan 2026 17:58:05 +0000 [thread overview]
Message-ID: <20260116175809.6849-1-ben.dooks@codethink.co.uk> (raw)
Third version with a few minor fixes, the only issues seem to be
with the complexities of the linux-kernel which has some printk
fun locally defined.
This series (which was initially sent back in 2020) adds the
ability to deal with __attribute__((format) and checking the
arguments to formatted variadic functions.
I have been considering adding a -Wformat-linux to this as
the kernel now has a number of extra formatting options and
checking the type of these would be useful. An even nicer
extension would be some way of informing the compiler/sparse
of these at compile time (but would need to get agreement on
how to do this with the compilers too)
next reply other threads:[~2026-01-16 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 17:58 Ben Dooks [this message]
2026-01-16 17:58 ` [PATCH v3 1/4] parse: initial parsing of __attribute__((format)) Ben Dooks
2026-01-16 17:58 ` [PATCH v3 2/4] add -Wformat Ben Dooks
2026-01-16 17:58 ` [PATCH v3 3/4] evaluate: check variadic argument types against formatting info Ben Dooks
2026-01-16 17:58 ` [PATCH v3 4/4] tests: add varargs printf format tests Ben Dooks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260116175809.6849-1-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox