stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Deutschmann <whissi@gentoo.org>
To: stable@vger.kernel.org
Cc: seth.forshee@canonical.com, mpe@ellerman.id.au
Subject: stable request: 186b8f15 ("powerpc: Always initialize input array when calling epapr_hypercall()")
Date: Sat, 2 Mar 2019 21:24:21 +0100	[thread overview]
Message-ID: <dc0ba1c6-89cb-90ff-f336-e7a5108f02ac@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1107 bytes --]

Hi,

please backport

> powerpc: Always initialize input array when calling epapr_hypercall()
> Several callers to epapr_hypercall() pass an uninitialized stack
> allocated array for the input arguments, presumably because they
> have no input arguments. However this can produce errors like
> this one
> 
>  arch/powerpc/include/asm/epapr_hcalls.h:470:42: error: 'in' may be used uninitialized in this function [-Werror=maybe-uninitialized]
>   unsigned long register r3 asm("r3") = in[0];
>                                         ~~^~~
> 
> Fix callers to this function to always zero-initialize the input
> arguments array to prevent this.
> 
> Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=186b8f1587c79c2fa04bfa392fdf084443e398c1

to

- 4.14.x
- 4.9.x
- 4.4.x


Downstream-Bug: https://bugs.gentoo.org/675334


-- 
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

             reply	other threads:[~2019-03-02 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 20:24 Thomas Deutschmann [this message]
2019-03-02 21:21 ` stable request: 186b8f15 ("powerpc: Always initialize input array when calling epapr_hypercall()") Greg KH

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=dc0ba1c6-89cb-90ff-f336-e7a5108f02ac@gentoo.org \
    --to=whissi@gentoo.org \
    --cc=mpe@ellerman.id.au \
    --cc=seth.forshee@canonical.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).