Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751590AbdFUF7L (ORCPT ); Wed, 21 Jun 2017 01:59:11 -0400 Received: from wtarreau.pck.nerim.net ([62.212.114.60]:52989 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751140AbdFUF7K (ORCPT ); Wed, 21 Jun 2017 01:59:10 -0400 Date: Wed, 21 Jun 2017 07:59:02 +0200 From: Willy Tarreau To: Hugh Dickins Cc: Greg Kroah-Hartman , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Michal Hocko , Linus Torvalds Subject: Re: [PATCH 3.18 32/32] mm: larger stack guard gap, between vmas Message-ID: <20170621055902.GF8079@1wt.eu> References: <20170619152035.750974520@linuxfoundation.org> <20170619152037.416644984@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1371 Lines: 37 On Tue, Jun 20, 2017 at 10:49:16PM -0700, Hugh Dickins wrote: > On Mon, 19 Jun 2017, Greg Kroah-Hartman wrote: > > > 3.18-stable review patch. If anyone has any objections, please let me know. > > > > ------------------ > > > > From: Hugh Dickins > > > > commit 1be7107fbe18eed3e319a6c3e83c78254b693acb upstream. > > Here's a few adjustments to the 3.18 patch: no doubt you'll have > already sorted out any build errors (and I have to confess that > I haven't even tried to build this); and the VM_WARN_ON line (as > in 4.4) only fixes a highly unlikely error; but those FOLL_MLOCK > lines in mm/gup.c were mistaken, and do need to be deleted. Are you sure ? The test on the FOLL_MLOCK flag remains present in 4.11 and mainline : /* mlock all present pages, but do not fault in new pages */ if ((*flags & (FOLL_POPULATE | FOLL_MLOCK)) == FOLL_MLOCK) return -ENOENT; And this test was present although different in 3.18 as well : /* For mlock, just skip the stack guard page. */ if ((*flags & FOLL_MLOCK) && (stack_guard_page_start(vma, address) || stack_guard_page_end(vma, address + PAGE_SIZE))) So by removing it we're totally removing any test on FOLL_MLOCK. That might be the correct fix, but I'm just a bit surprized since the mainline patch doesn't remove it, and only removes the test on FOLL_POPULATE. Thanks, Willy