Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5436857ybi; Tue, 4 Jun 2019 06:42:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqy1X+484IG+5Sck5eiMs/Qzz36y1MozhwckBBmTiKk49M4zLk0GFN05OIEkBI8CdMRvQVfC X-Received: by 2002:aa7:864e:: with SMTP id a14mr38862161pfo.132.1559655766608; Tue, 04 Jun 2019 06:42:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559655766; cv=none; d=google.com; s=arc-20160816; b=ktFkWhV00kasXwMVgOAGeZFtBcB+4TLE6hGg7N4xZtwpK9ru2avxfIA95Gejhdrjqb xbuQneRGQacKvQWIInRbgxnhgc9ySHVy218BW9fPnN5twcP4m6pAP4PUQrVXBwszOlJn YadieCh/R1Bj4ZWQ63Pp0LK1TZGHz3Yx7rSPtUi33+nUUo+F4Rhup5oZWhpASpOjvrFj JbgXNQD9IxvoSzWPvUTpFufIAvLLU1xLm0cUEgPlanHusLV6Kl/HUnqj5fQYxuY23bFB zmZr8wAFNQKU+206uFI0/adXRPjMU2MCdkFPX1lzPQFGUy/1F5g9aM+67LWPYfInqDhE /GCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:to:references :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=Y6C19x9dlJzyoCn5bBRafsQdoIZme1n+ZdxRgWhdDek=; b=S6uAZQ05OuI3N4Vh9qI19ac7mxfv0mnU6CmVHHH5x2XgL5+NVCUeslWqEPnH3hJXG/ ketRF//V6wDE8IqYmD0kugKNnEXYsl/rx8a2CFTLIRrtSLYkaME+x/Vqt85G6fkFWkem 3q4ds8fxkHKV7rpCodMFss0ryuhTMYToN000gXsT+Hmz6awFNeKf0Y5et3hsmJMW1fIN 8Vxg84zbfMDQdKQb2achYwL9kUWlNcNYLWeQjm2gP6oE02ZOssLgJMoZNP/ow6zkyIrj HVk7lWjwcjOud8StnyXSuUu8EGK9JNS6phj4YPXzu0KqoULbAZeyWmLYZ++zW23UlO7o JvYw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y62si22268223pgy.362.2019.06.04.06.42.28; Tue, 04 Jun 2019 06:42:46 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727737AbfFDNjo convert rfc822-to-8bit (ORCPT + 99 others); Tue, 4 Jun 2019 09:39:44 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:48322 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727348AbfFDNjn (ORCPT ); Tue, 4 Jun 2019 09:39:43 -0400 Received: from pps.filterd (m0098396.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x54DWu3i093560 for ; Tue, 4 Jun 2019 09:39:42 -0400 Received: from e06smtp01.uk.ibm.com (e06smtp01.uk.ibm.com [195.75.94.97]) by mx0a-001b2d01.pphosted.com with ESMTP id 2swqamq77q-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 04 Jun 2019 09:39:41 -0400 Received: from localhost by e06smtp01.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 4 Jun 2019 14:39:33 +0100 Received: from b06cxnps4075.portsmouth.uk.ibm.com (9.149.109.197) by e06smtp01.uk.ibm.com (192.168.101.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 4 Jun 2019 14:39:29 +0100 Received: from d06av26.portsmouth.uk.ibm.com (d06av26.portsmouth.uk.ibm.com [9.149.105.62]) by b06cxnps4075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x54DdS7J50987256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 4 Jun 2019 13:39:28 GMT Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id AF048AE04D; Tue, 4 Jun 2019 13:39:28 +0000 (GMT) Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 69768AE056; Tue, 4 Jun 2019 13:39:27 +0000 (GMT) Received: from [9.102.21.242] (unknown [9.102.21.242]) by d06av26.portsmouth.uk.ibm.com (Postfix) with ESMTP; Tue, 4 Jun 2019 13:39:27 +0000 (GMT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [POWERPC][next-20190603] Boot failure : Kernel BUG at mm/vmalloc.c:470 From: Sachin Sant In-Reply-To: <20190604202918.17a1e466@canb.auug.org.au> Date: Tue, 4 Jun 2019 19:09:26 +0530 Cc: linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org, linux-mm@kvack.org, "Uladzislau Rezki (Sony)" , linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8BIT References: <9F9C0085-F8A4-4B66-802B-382119E34DF5@linux.vnet.ibm.com> <20190604202918.17a1e466@canb.auug.org.au> To: Stephen Rothwell X-Mailer: Apple Mail (2.3445.104.11) X-TM-AS-GCONF: 00 x-cbid: 19060413-4275-0000-0000-0000033C9377 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19060413-4276-0000-0000-0000384CA27D Message-Id: <88ADCAAE-4F1A-49FE-A454-BBAB12A88C70@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-06-04_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=857 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906040092 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On 04-Jun-2019, at 3:59 PM, Stephen Rothwell wrote: > > Hi Sachin, > > On Tue, 4 Jun 2019 14:45:43 +0530 Sachin Sant wrote: >> >> While booting linux-next [next-20190603] on a POWER9 LPAR following >> BUG is encountered and the boot fails. >> >> If I revert the following 2 patches I no longer see this BUG message >> >> 07031d37b2f9 ( mm/vmalloc.c: switch to WARN_ON() and move it under unlink_va() ) >> 728e0fbf263e ( mm/vmalloc.c: get rid of one single unlink_va() when merge ) > > This latter patch has been fixed in today's linux-next … Thanks Stephen. With today’s next (20190604) I no longer see this issue. Thanks -Sachin