From: Ingo Molnar <mingo@kernel.org>
To: Chris Metcalf <cmetcalf@ezchip.com>
Cc: Michael Cree <mcree@orcon.net.nz>,
Matt Turner <mattst88@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Alexey Dobriyan <adobriyan@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
linux-alpha@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] strscpy: zero any trailing garbage bytes in the destination
Date: Wed, 7 Oct 2015 09:31:52 +0200 [thread overview]
Message-ID: <20151007073152.GA8974@gmail.com> (raw)
In-Reply-To: <1444159429-4788-4-git-send-email-cmetcalf@ezchip.com>
* Chris Metcalf <cmetcalf@ezchip.com> wrote:
> It's possible that the destination can be shadowed in userspace
> (as, for example, the perf buffers are now). So we should take
> care not to leak data that could be inspected by userspace.
>
> Signed-off-by: Chris Metcalf <cmetcalf@ezchip.com>
Please always preserve credits for who found the bug:
Reported-by: Alexey Dobriyan <adobriyan@gmail.com>
Also, you should credit the kbuild-bot for the cross-arch build breakages that
your other patches address:
Reported-by: kbuild test robot <fengguang.wu@intel.com>
Thanks,
Ingo
prev parent reply other threads:[~2015-10-07 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 19:23 [PATCH v2 0/3] various strscpy fixes Chris Metcalf
2015-10-06 19:23 ` [PATCH v2 1/3] word-at-a-time.h: fix some Kbuild files Chris Metcalf
2015-10-06 19:23 ` [PATCH v2 2/3] word-at-a-time.h: support zero_bytemask() on alpha and tile Chris Metcalf
2015-10-07 5:53 ` Ingo Molnar
2015-10-07 13:58 ` Chris Metcalf
2015-10-06 19:23 ` [PATCH v2 3/3] strscpy: zero any trailing garbage bytes in the destination Chris Metcalf
2015-10-07 7:31 ` Ingo Molnar [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=20151007073152.GA8974@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adobriyan@gmail.com \
--cc=bp@alien8.de \
--cc=cmetcalf@ezchip.com \
--cc=hpa@zytor.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=mpe@ellerman.id.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=ysato@users.sourceforge.jp \
/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;
as well as URLs for NNTP newsgroup(s).