From: Michael Ellerman <mpe@ellerman.id.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "stable\@vger.kernel.org" <stable@vger.kernel.org>,
"linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH backport pre-4.9] powerpc/slb: Force a full SLB flush when we insert for a bad EA
Date: Wed, 28 Jun 2017 11:40:55 +1000 [thread overview]
Message-ID: <87fuekdh3s.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170627105958.GA10609@kroah.com>
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Thu, Jun 22, 2017 at 04:52:51PM +1000, Michael Ellerman wrote:
>> The SLB miss handler calls slb_allocate_realmode() in order to create an
>> SLB entry for the faulting address. At the very start of that function
>> we check that the faulting Effective Address (EA) is less than
>> PGTABLE_RANGE (ignoring the region), ie. is it an address which could
>> possibly fit in the virtual address space.
...
>> ---
>> arch/powerpc/mm/slb_low.S | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> Note this patch is not upstream. The bug fix was fixed differently in
>> upstream prior to the bug being identified.
>
> Now applied to 4.4 and 3.18-stable kernels, thanks,
Thanks.
cheers
next prev parent reply other threads:[~2017-06-28 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k244sed8.fsf@concordia.ellerman.id.au>
2017-06-27 10:59 ` Patch "powerpc/slb: Force a full SLB flush when we insert for a bad EA" has been added to the 3.18-stable tree gregkh
2017-06-27 10:59 ` [PATCH backport pre-4.9] powerpc/slb: Force a full SLB flush when we insert for a bad EA Greg Kroah-Hartman
2017-06-28 1:40 ` Michael Ellerman [this message]
2017-06-27 11:00 ` Patch "powerpc/slb: Force a full SLB flush when we insert for a bad EA" has been added to the 4.4-stable tree gregkh
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=87fuekdh3s.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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
Powered by JetHome