From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sparse@vger.kernel.org
Subject: updated variadic printf/scanf checking
Date: Fri, 19 Jun 2026 08:05:28 +0100 [thread overview]
Message-ID: <20260619070532.11664-1-ben.dooks@codethink.co.uk> (raw)
I'm reposting this as an RFC as there has been quite a bit of work on
this to get scanf in and to try and simplify the code, fix a few bugs
found when checking the kernel. Depending on the reviews I will post
this for inclusion.
I am also looking at some work to try and make printf and scanf extensible
with the interesting types the kernel adds to printk, either by a new flag
or by some sort of attribute. This is not included in this set.
I think the tests need some more work on scanf, otherwise it seems to work
well with the kernel, and not really found any further issues other than
the odd signed/unsigned and type.
next reply other threads:[~2026-06-19 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 7:05 Ben Dooks [this message]
2026-06-19 7:05 ` [RFC v4 1/4] parse: initial parsing of __attribute__((format)) Ben Dooks
2026-06-19 7:05 ` [RFC v4 2/4] add -Wformat Ben Dooks
2026-06-19 7:05 ` [RFC v4 3/4] evaluate: check variadic argument types against formatting info Ben Dooks
2026-06-19 7:05 ` [RFC v4 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=20260619070532.11664-1-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-sparse@vger.kernel.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