From: tip-bot for Mattias Jacobsson <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: bp@suse.de, mingo@kernel.org, 2pi@mok.nu,
linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de, hpa@zytor.com
Subject: [tip:x86/boot] x86/boot: Add missing va_end() to die()
Date: Wed, 28 Nov 2018 11:15:54 -0800 [thread overview]
Message-ID: <tip-69be4efeb959147ff86f22e35aea9526f9b86715@git.kernel.org> (raw)
In-Reply-To: <20181128161607.10973-1-2pi@mok.nu>
Commit-ID: 69be4efeb959147ff86f22e35aea9526f9b86715
Gitweb: https://git.kernel.org/tip/69be4efeb959147ff86f22e35aea9526f9b86715
Author: Mattias Jacobsson <2pi@mok.nu>
AuthorDate: Wed, 28 Nov 2018 17:16:07 +0100
Committer: Borislav Petkov <bp@suse.de>
CommitDate: Wed, 28 Nov 2018 20:06:07 +0100
x86/boot: Add missing va_end() to die()
Each call to va_start() must have a corresponding call to va_end()
before the end of the function. Add the missing va_end().
Found with Coccinelle.
Signed-off-by: Mattias Jacobsson <2pi@mok.nu>
Signed-off-by: Borislav Petkov <bp@suse.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: https://lkml.kernel.org/r/20181128161607.10973-1-2pi@mok.nu
---
arch/x86/boot/tools/build.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/boot/tools/build.c b/arch/x86/boot/tools/build.c
index bf0e82400358..a93d44e58f9c 100644
--- a/arch/x86/boot/tools/build.c
+++ b/arch/x86/boot/tools/build.c
@@ -132,6 +132,7 @@ static void die(const char * str, ...)
va_list args;
va_start(args, str);
vfprintf(stderr, str, args);
+ va_end(args);
fputc('\n', stderr);
exit(1);
}
prev parent reply other threads:[~2018-11-28 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 16:16 [PATCH] x86: boot: add missing va_end to die Mattias Jacobsson
2018-11-28 19:15 ` tip-bot for Mattias Jacobsson [this message]
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=tip-69be4efeb959147ff86f22e35aea9526f9b86715@git.kernel.org \
--to=tipbot@zytor.com \
--cc=2pi@mok.nu \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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 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.