Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From:   William Kucharski <william.kucharski@oracle.com>
Mime-Version: 1.0 (1.0)
Subject: Re:   [PATCH] mm/vmalloc: Sanitize __get_vm_area() arguments
Message-Id: <D25C4027-6EF9-44C2-AD4D-DDC785288B9A@oracle.com>
Date:   Sat, 4 Apr 2020 09:35:02 -0600
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        linux-kernel@vger.kernel.org, linux-mm@kvack.org, jroedel@suse.de,
        vbabka@suse.cz, urezki@gmail.com,
        Thomas Gleixner <tglx@linutronix.de>
To:     Peter Zijlstra <peterz@infradead.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

=EF=BB=BFIs there any need to similarly sanitize =E2=80=9Csize=E2=80=9D to a=
ssure start + size doesn=E2=80=99t go past =E2=80=9Cend?=E2=80=9D

> On Apr 3, 2020, at 10:33, Peter Zijlstra <peterz@infradead.org> wrote:
>=20
> =EF=BB=BF
> __get_vm_area() is an exported symbol, make sure the callers stay in
> the expected memory range. When calling this function with memory
> ranges outside of the VMALLOC range *bad* things can happen.