linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	arcml <linux-snps-arc@lists.infradead.org>
Subject: 4.2+ stable inclusion request: ARCv2: save r30 on kernel entry as gcc uses it for code-gen
Date: Fri, 28 Apr 2017 11:57:36 -0700	[thread overview]
Message-ID: <bd36bc24-831f-a5ea-2b24-f4984a9b91cf@synopsys.com> (raw)

Hi,

Can we please backport upstream ecd43afdbe72017aefe48080631eb625e177ef4d ("ARCv2:
save r30 on kernel entry as gcc uses it for code-gen") to 4.2 to 4.9 kernels.

While the issue cites gcc, it is general deficiency of kernel as userspace
programs can modify r30 register in hand/inline assembly and those will not be
preserved without this change.

Thx,
-Vineet

             reply	other threads:[~2017-04-28 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 18:57 Vineet Gupta [this message]
2017-04-30 14:08 ` 4.2+ stable inclusion request: ARCv2: save r30 on kernel entry as gcc uses it for code-gen 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=bd36bc24-831f-a5ea-2b24-f4984a9b91cf@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --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).