From: James Bottomley <jejb@linux.ibm.com> To: Denis Kenzior <denkenz@gmail.com>, ndesaulniers@google.com, dhowells@redhat.com Cc: natechancellor@gmail.com, ebiggers@google.com, Mimi Zohar <zohar@linux.vnet.ibm.com>, James Morris <jmorris@namei.org>, "Serge E. Hallyn" <serge@hallyn.com>, linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] KEYS: trusted: fix -Wvarags warning Date: Fri, 12 Oct 2018 16:01:15 +0000 [thread overview] Message-ID: <1539360075.2656.18.camel@linux.ibm.com> (raw) In-Reply-To: <da2a675f-bd2d-a1f3-6a67-5579e75bdb76@gmail.com> On Fri, 2018-10-12 at 10:53 -0500, Denis Kenzior wrote: > Hi James, > > > > From the links provided in the patch it seems that one cannot > > > pass char/float/short to va_start(). Fair enough. So if we make > > > h3 an unsigned int, the issue goes away, no? > > > > For the current version of clang, yes. However, if we're fixing > > this for good a char * pointer is the only guaranteed thing because > > it mirrors current use in printf. > > > > All right. I guess I wasn't aware that non-printf like variadic > functions are now considered harmful or of the impending crusade > against them :) It's not, it's just a maintainer issue: The original problem is because we coded for gcc specifically; it doesn't complain and does the right thing, so everyone was happy. Now Clang comes along and is unhappy with this, so the question a good maintainer should ask is "how do I fix this so it never comes back again?", not "what's the easiest bandaid to get both Clang and gcc to work?" because the latter is how we got here in the first place. James > But in the context of this patch, can we please use something less > invasive than changing all the arguments around? Promoting h3 to a > bool (if possible) or int/unsigned int would get my vote. > > Regards, > -Denis >
WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <jejb@linux.ibm.com> To: Denis Kenzior <denkenz@gmail.com>, ndesaulniers@google.com, dhowells@redhat.com Cc: natechancellor@gmail.com, ebiggers@google.com, Mimi Zohar <zohar@linux.vnet.ibm.com>, James Morris <jmorris@namei.org>, "Serge E. Hallyn" <serge@hallyn.com>, linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] KEYS: trusted: fix -Wvarags warning Date: Fri, 12 Oct 2018 09:01:15 -0700 [thread overview] Message-ID: <1539360075.2656.18.camel@linux.ibm.com> (raw) In-Reply-To: <da2a675f-bd2d-a1f3-6a67-5579e75bdb76@gmail.com> On Fri, 2018-10-12 at 10:53 -0500, Denis Kenzior wrote: > Hi James, > > > > From the links provided in the patch it seems that one cannot > > > pass char/float/short to va_start(). Fair enough. So if we make > > > h3 an unsigned int, the issue goes away, no? > > > > For the current version of clang, yes. However, if we're fixing > > this for good a char * pointer is the only guaranteed thing because > > it mirrors current use in printf. > > > > All right. I guess I wasn't aware that non-printf like variadic > functions are now considered harmful or of the impending crusade > against them :) It's not, it's just a maintainer issue: The original problem is because we coded for gcc specifically; it doesn't complain and does the right thing, so everyone was happy. Now Clang comes along and is unhappy with this, so the question a good maintainer should ask is "how do I fix this so it never comes back again?", not "what's the easiest bandaid to get both Clang and gcc to work?" because the latter is how we got here in the first place. James > But in the context of this patch, can we please use something less > invasive than changing all the arguments around? Promoting h3 to a > bool (if possible) or int/unsigned int would get my vote. > > Regards, > -Denis >
next prev parent reply other threads:[~2018-10-12 16:01 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-09 22:11 undefined behavior (-Wvarargs) in security/keys/trusted.c#TSS_authhmac() Nick Desaulniers 2018-10-09 22:11 ` Nick Desaulniers 2018-10-11 16:02 ` Arnd Bergmann 2018-10-11 16:02 ` Arnd Bergmann 2018-10-11 16:10 ` James Bottomley 2018-10-11 16:10 ` James Bottomley 2018-10-11 20:31 ` [PATCH] KEYS: trusted: fix -Wvarags warning ndesaulniers 2018-10-11 20:31 ` ndesaulniers 2018-10-12 1:50 ` Nathan Chancellor 2018-10-12 1:50 ` Nathan Chancellor 2018-10-12 16:55 ` Nick Desaulniers 2018-10-12 16:55 ` Nick Desaulniers 2018-10-12 17:03 ` Nathan Chancellor 2018-10-12 17:03 ` Nathan Chancellor 2018-10-12 12:29 ` Denis Kenzior 2018-10-12 12:29 ` Denis Kenzior 2018-10-12 15:05 ` James Bottomley 2018-10-12 15:05 ` James Bottomley 2018-10-12 15:13 ` Denis Kenzior 2018-10-12 15:13 ` Denis Kenzior 2018-10-12 15:22 ` James Bottomley 2018-10-12 15:22 ` James Bottomley 2018-10-12 15:44 ` Denis Kenzior 2018-10-12 15:44 ` Denis Kenzior 2018-10-12 15:46 ` James Bottomley 2018-10-12 15:46 ` James Bottomley 2018-10-12 15:53 ` Denis Kenzior 2018-10-12 15:53 ` Denis Kenzior 2018-10-12 16:01 ` James Bottomley [this message] 2018-10-12 16:01 ` James Bottomley 2018-10-12 17:14 ` Nick Desaulniers 2018-10-12 17:14 ` Nick Desaulniers 2018-10-12 15:25 ` James Bottomley 2018-10-12 15:25 ` James Bottomley 2018-10-12 17:05 ` Nick Desaulniers 2018-10-12 17:05 ` Nick Desaulniers 2018-10-12 17:17 ` Nick Desaulniers 2018-10-12 17:17 ` Nick Desaulniers 2018-10-12 17:27 ` Denis Kenzior 2018-10-12 17:27 ` Denis Kenzior 2018-10-12 18:39 ` Nick Desaulniers 2018-10-12 18:39 ` Nick Desaulniers 2018-10-12 17:02 ` Nick Desaulniers 2018-10-12 17:02 ` Nick Desaulniers 2018-10-12 17:15 ` Denis Kenzior 2018-10-12 17:15 ` Denis Kenzior 2018-10-15 9:26 ` David Laight 2018-10-15 9:26 ` David Laight 2018-10-15 9:26 ` David Laight 2018-10-15 21:53 ` Nick Desaulniers 2018-10-15 21:53 ` Nick Desaulniers 2018-10-16 8:13 ` David Laight 2018-10-16 8:13 ` David Laight 2018-10-16 8:13 ` David Laight 2018-10-22 23:43 ` [PATCH v2] " ndesaulniers 2018-10-22 23:43 ` ndesaulniers 2018-10-23 0:00 ` Nathan Chancellor 2018-10-23 0:00 ` Nathan Chancellor 2018-10-24 8:36 ` Jarkko Sakkinen 2018-10-24 8:36 ` Jarkko Sakkinen 2018-10-29 17:54 ` Nick Desaulniers 2018-10-29 17:54 ` Nick Desaulniers 2019-02-11 18:36 ` Nick Desaulniers 2019-02-11 18:36 ` Nick Desaulniers 2019-02-12 23:12 ` Jarkko Sakkinen 2019-02-12 23:12 ` Jarkko Sakkinen 2019-02-14 10:52 ` Jarkko Sakkinen 2019-02-14 10:52 ` Jarkko Sakkinen
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=1539360075.2656.18.camel@linux.ibm.com \ --to=jejb@linux.ibm.com \ --cc=denkenz@gmail.com \ --cc=dhowells@redhat.com \ --cc=ebiggers@google.com \ --cc=jmorris@namei.org \ --cc=keyrings@vger.kernel.org \ --cc=linux-integrity@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=natechancellor@gmail.com \ --cc=ndesaulniers@google.com \ --cc=serge@hallyn.com \ --cc=zohar@linux.vnet.ibm.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.