From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Greg KH <greg@kroah.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Laura Abbott <labbott@redhat.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [STABLE REQ] mm/vmalloc.c: huge-vmap: fail gracefully on unexpected huge vmap mappings
Date: Mon, 3 Jul 2017 12:14:16 +0100 [thread overview]
Message-ID: <CAKv+Gu-TGm5ghzMQ=bYubnyoi-s7H-L+o73NShoCO3JUHdCxQw@mail.gmail.com> (raw)
In-Reply-To: <20170703084439.GC11757@kroah.com>
On 3 July 2017 at 09:44, Greg KH <greg@kroah.com> wrote:
> On Tue, Jun 27, 2017 at 02:36:46PM +0000, Ard Biesheuvel wrote:
>> Please consider
>>
>> 029c54b09599 mm/vmalloc.c: huge-vmap: fail gracefully on unexpected
>> huge vmap mappings
>>
>> for inclusion into the v4.9 and v4.11 stable trees. It prevents
>> crashes on arm64 that may occur after commit 324420bf91f6 ("arm64: add
>> support for ioremap() block mappings") was merged for v4.6.
>
> Does not apply to the 4.9-stable tree, can you provide a backport for it
> there?
>
Done.
Regards,
Ard.
WARNING: multiple messages have this Message-ID (diff)
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [STABLE REQ] mm/vmalloc.c: huge-vmap: fail gracefully on unexpected huge vmap mappings
Date: Mon, 3 Jul 2017 12:14:16 +0100 [thread overview]
Message-ID: <CAKv+Gu-TGm5ghzMQ=bYubnyoi-s7H-L+o73NShoCO3JUHdCxQw@mail.gmail.com> (raw)
In-Reply-To: <20170703084439.GC11757@kroah.com>
On 3 July 2017 at 09:44, Greg KH <greg@kroah.com> wrote:
> On Tue, Jun 27, 2017 at 02:36:46PM +0000, Ard Biesheuvel wrote:
>> Please consider
>>
>> 029c54b09599 mm/vmalloc.c: huge-vmap: fail gracefully on unexpected
>> huge vmap mappings
>>
>> for inclusion into the v4.9 and v4.11 stable trees. It prevents
>> crashes on arm64 that may occur after commit 324420bf91f6 ("arm64: add
>> support for ioremap() block mappings") was merged for v4.6.
>
> Does not apply to the 4.9-stable tree, can you provide a backport for it
> there?
>
Done.
Regards,
Ard.
next prev parent reply other threads:[~2017-07-03 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 14:36 [STABLE REQ] mm/vmalloc.c: huge-vmap: fail gracefully on unexpected huge vmap mappings Ard Biesheuvel
2017-06-27 14:36 ` Ard Biesheuvel
2017-07-03 8:44 ` Greg KH
2017-07-03 8:44 ` Greg KH
2017-07-03 11:14 ` Ard Biesheuvel [this message]
2017-07-03 11:14 ` Ard Biesheuvel
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='CAKv+Gu-TGm5ghzMQ=bYubnyoi-s7H-L+o73NShoCO3JUHdCxQw@mail.gmail.com' \
--to=ard.biesheuvel@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=greg@kroah.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.