From: Joe Perches <joe@perches.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: General kernel misuse of vsnprintf SPECIAL %#<foo> (was: Re: [PATCH v2 0/4] iio: Drop use of %hhx and %hx format strings)
Date: Thu, 03 Jun 2021 12:34:28 -0700 [thread overview]
Message-ID: <7a7e5cf61177b168f465f2502fde7a1e04293063.camel@perches.com> (raw)
In-Reply-To: <20210603202546.0d12e7ad@jic23-huawei>
On Thu, 2021-06-03 at 20:25 +0100, Jonathan Cameron wrote:
> On Thu, 03 Jun 2021 11:58:15 -0700 Joe Perches <joe@perches.com> wrote:
> > It looks to me as though %#<foo> is relatively commonly misused in the kernel.
> >
> > Pehaps for the decimal portion of the format, checkpatch could have some
> > test for use of non-standard lengths.
> >
> > Given the use is generally meant for a u8, u16, u32, or u64, perhaps
> > checkpatch should emit a warning whenever the length is not 4, 6, 10, or 18.
>
> Would have saved me some trouble, so I'm definitely in favour of checkpatch
> catching this.
>
> I wonder if a better option is to match on 1, 2, 4, 8, 16 as likely to be
> caused by people getting the usage wrong rather than a deliberate attempt
> to pretty print something a little unusual?
Dunno. %#0x and %x[123] seems pretty silly as it'll always emit the number
of digits in the value.
There aren't too many other odd uses other than those.
> > $ git grep -P -h -o '%#\d+\w+' | sort | uniq -c | sort -rn
8 and 16 are perhaps commonly misused.
> > 392 %#08x
> > 17 %#08lx
> > 9 %#08zx
> > 6 %#8x
> > 4 %#08llx
> > 1 %#8lx
> > 1 %#08
> > 7 %#16llx
> > 5 %#16
> > 4 %#016Lx
> > 1 %#16x
> > 1 %#16lx
These are the odd ones:
> > 144 %#02x
> > 27 %#0x
> > 23 %#2x
> > 17 %#3lx
> > 15 %#3x
> > 14 %#03x
> > 6 %#012llx
> > 4 %#05x
> > 4 %#02X
> > 3 %#01x
> > 2 %#09x
> > 2 %#05lx
> > 1 %#5x
> > 1 %#5lx
> > 1 %#2Lx
> > 1 %#2llx
> > 1 %#12x
> > 1 %#0lx
> > 1 %#05llx
> > 1 %#03X
next prev parent reply other threads:[~2021-06-03 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210603180612.3635250-1-jic23@kernel.org>
2021-06-03 18:58 ` Joe Perches
2021-06-03 19:25 ` Jonathan Cameron
2021-06-03 19:34 ` Joe Perches [this message]
2021-06-04 8:27 ` Jonathan Cameron
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=7a7e5cf61177b168f465f2502fde7a1e04293063.camel@perches.com \
--to=joe@perches.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®