From: Joe Perches <joe@perches.com> To: Lukas Bulwahn <lukas.bulwahn@gmail.com>, Aditya Srivastava <yashsri421@gmail.com>, Dwaipayan Ray <dwaipayanray1@gmail.com> Cc: Nick Desaulniers <ndesaulniers@google.com>, Pablo Neira Ayuso <pablo@netfilter.org>, Jozsef Kadlecsik <kadlec@netfilter.org>, Florian Westphal <fw@strlen.de>, "David S. Miller" <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>, Nathan Chancellor <natechancellor@gmail.com>, netfilter-devel@vger.kernel.org, coreteam@netfilter.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com Subject: Re: [PATCH] netfilter: conntrack: fix -Wformat Date: Sun, 08 Nov 2020 02:10:24 -0800 Message-ID: <5e3265c241602bb54286fbaae9222070daa4768e.camel@perches.com> (raw) In-Reply-To: <alpine.DEB.2.21.2011080829080.4909@felia> On Sun, 2020-11-08 at 08:34 +0100, Lukas Bulwahn wrote: > On Sat, 7 Nov 2020, Joe Perches wrote: > > On Fri, 2020-11-06 at 23:55 -0800, Nick Desaulniers wrote: > > > Clang is more aggressive about -Wformat warnings when the format flag > > > specifies a type smaller than the parameter. Fixes 8 instances of: > > > > > > warning: format specifies type 'unsigned short' but the argument has > > > type 'int' [-Wformat] > > > > Likely clang's -Wformat message is still bogus. > > Wasn't that going to be fixed? > > > > Integer promotions are already done on these types to int anyway. > > Didn't we have this discussion last year? > > > > https://lore.kernel.org/lkml/CAKwvOd=mqzj2pAZEUsW-M_62xn4pijpCJmP=B1h_-wEb0NeZsA@mail.gmail.com/ > > https://lore.kernel.org/lkml/CAHk-=wgoxnmsj8GEVFJSvTwdnWm8wVJthefNk2n6+4TC=20e0Q@mail.gmail.com/ > > https://lore.kernel.org/lkml/a68114afb134b8633905f5a25ae7c4e6799ce8f1.camel@perches.com/ > > > > Look at commit cbacb5ab0aa0 ("docs: printk-formats: Stop encouraging use > > of unnecessary %h[xudi] and %hh[xudi]") > > > > The "h" and "hh" things should never be used. The only reason for them > > being used if if you have an "int", but you want to print it out as a > > "char" (and honestly, that is a really bad reason, you'd be better off > > just using a proper cast to make the code more obvious). > > > Joe, would this be a good rule to check for in checkpatch? > > Can Dwaipayan or Aditya give it a try to create a suitable patch to add > such a rule? $ git grep -P '"[^"]*%[\d\.\*\-]*h+[idux].*"' I suppose so. Please avoid warning on scanf and its variants and the asm bits though. > Dwaipayan, Aditya, if Joe thinks it is worth a rule, it is "first come, > first serve" for you to take that task.
next prev parent reply index Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-07 7:55 Nick Desaulniers 2020-11-07 10:32 ` Joe Perches 2020-11-08 7:34 ` Lukas Bulwahn 2020-11-08 10:10 ` Joe Perches [this message] 2020-11-10 22:00 ` Nick Desaulniers 2020-11-10 22:04 ` Joe Perches 2020-11-10 22:06 ` Nick Desaulniers 2020-12-02 22:34 ` Nick Desaulniers 2020-12-03 0:46 ` Tom Rix 2020-12-03 7:26 ` Lukas Bulwahn 2020-12-03 13:43 ` Miguel Ojeda 2020-12-03 14:40 ` Lukas Bulwahn 2020-12-03 14:39 ` Tom Rix 2020-12-03 16:45 ` Joe Perches 2020-12-13 19:21 ` Tom Rix 2020-12-13 23:25 ` Joe Perches 2020-12-13 23:29 ` Tom Rix 2020-11-07 17:52 ` Jakub Kicinski 2020-11-09 15:43 ` kernel test robot
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=5e3265c241602bb54286fbaae9222070daa4768e.camel@perches.com \ --to=joe@perches.com \ --cc=clang-built-linux@googlegroups.com \ --cc=coreteam@netfilter.org \ --cc=davem@davemloft.net \ --cc=dwaipayanray1@gmail.com \ --cc=fw@strlen.de \ --cc=kadlec@netfilter.org \ --cc=kuba@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lukas.bulwahn@gmail.com \ --cc=natechancellor@gmail.com \ --cc=ndesaulniers@google.com \ --cc=netdev@vger.kernel.org \ --cc=netfilter-devel@vger.kernel.org \ --cc=pablo@netfilter.org \ --cc=yashsri421@gmail.com \ /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
LKML Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \ linux-kernel@vger.kernel.org public-inbox-index lkml Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git