From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757525AbaFTUcp (ORCPT ); Fri, 20 Jun 2014 16:32:45 -0400 Received: from qmta04.emeryville.ca.mail.comcast.net ([76.96.30.40]:50648 "EHLO qmta04.emeryville.ca.mail.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751349AbaFTUcn (ORCPT ); Fri, 20 Jun 2014 16:32:43 -0400 Date: Fri, 20 Jun 2014 15:32:40 -0500 (CDT) From: Christoph Lameter To: Hugh Dickins cc: Naoya Horiguchi , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , KOSAKI Motohiro , Naoya Horiguchi Subject: Re: kernel BUG at /src/linux-dev/mm/mempolicy.c:1738! on v3.16-rc1 In-Reply-To: Message-ID: References: <20140619215641.GA9792@nhori.bos.redhat.com> <20140620194639.GA30729@nhori.bos.redhat.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 20 Jun 2014, Hugh Dickins wrote: > [PATCH] mm: fix crashes from mbind() merging vmas > > v2.6.34's 9d8cebd4bcd7 ("mm: fix mbind vma merge problem") introduced > vma merging to mbind(), but it should have also changed the convention > of passing start vma from queue_pages_range() (formerly check_range()) > to new_vma_page(): vma merging may have already freed that structure, > resulting in BUG at mm/mempolicy.c:1738 and probably worse crashes. Good catch. Cannot find fault with what I see. Acked-by: Christoph Lameter