From: Stafford Horne <shorne@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
arnd@arndb.de, Eric Biggers <ebiggers3@gmail.com>,
linux-crypto@vger.kernel.org, Stafford Horne <shorne@gmail.com>
Subject: [PATCH v2 0/2] Fix GCC -Wstringop-truncation warnings
Date: Mon, 25 Jun 2018 21:45:36 +0900 [thread overview]
Message-ID: <20180625124538.21051-1-shorne@gmail.com> (raw)
Hello,
When compiling OpenRISC kernels with our new toolchain based on GCC 9.0.0 I am
seeing various -Wstringop-truncation warnings. There might be more as I am not
compiling all drivers/modules yet, if someone thinks thats helpful let me know.
I discussed this with Greg KH at the OSS Summit Japan 2018 and it seems no
one has pointed these out yet, so here are the patches... Actually, the crypto
issue was reported before, but the patch was discarded as it introduced a data
leakage bug pointed out by Erix.
As for merging, I think the maintainers should pick these up separately. Let me
know if you want something else.
Changes since v1:
- Fix paper-bag bug in kobject patch, using memcpy() now
- Fix data leakage issue crypto patch pointed out by Eric Biggers
-Stafford
Stafford Horne (2):
crypto: Fix -Wstringop-truncation warnings
kobject: Fix -Wstringop-truncation warning
crypto/ablkcipher.c | 2 ++
crypto/blkcipher.c | 1 +
lib/kobject.c | 2 +-
3 files changed, 4 insertions(+), 1 deletion(-)
--
2.17.0
next reply other threads:[~2018-06-25 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 12:45 Stafford Horne [this message]
2018-06-25 12:45 ` [PATCH v2 1/2] crypto: Fix -Wstringop-truncation warnings Stafford Horne
2018-06-25 12:59 ` Christophe LEROY
2018-06-25 13:40 ` Stafford Horne
2018-07-08 16:43 ` Herbert Xu
2018-06-25 12:45 ` [PATCH v2 2/2] kobject: Fix -Wstringop-truncation warning Stafford Horne
2018-06-25 12:57 ` Christophe LEROY
2018-06-25 13:24 ` Stafford Horne
2018-06-25 13:32 ` Christophe LEROY
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=20180625124538.21051-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=arnd@arndb.de \
--cc=ebiggers3@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@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