Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753743AbdDJOhl (ORCPT ); Mon, 10 Apr 2017 10:37:41 -0400 Received: from szxga02-in.huawei.com ([45.249.212.188]:5354 "EHLO dggrg02-dlp.huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753716AbdDJOhg (ORCPT ); Mon, 10 Apr 2017 10:37:36 -0400 Message-ID: <58EB97D4.1040605@huawei.com> Date: Mon, 10 Apr 2017 22:33:56 +0800 From: zhong jiang User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Willy Tarreau CC: Michal Hocko , Mel Gorman , Johannes Weiner , , Vlastimil Babka , "Linux Memory Management List" , LKML Subject: Re: NULL pointer dereference in the kernel 3.10 References: <58E8E81E.6090304@huawei.com> <20170410085604.zpenj6ggc3dsbgxw@techsingularity.net> <58EB761E.9040002@huawei.com> <20170410124814.GC4618@dhcp22.suse.cz> <58EB9183.2030806@huawei.com> <20170410141321.GB8008@1wt.eu> In-Reply-To: <20170410141321.GB8008@1wt.eu> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.29.68] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.58EB97E5.01D5,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: f531c773eebdda618edf49a7549c0877 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1834 Lines: 37 On 2017/4/10 22:13, Willy Tarreau wrote: > On Mon, Apr 10, 2017 at 10:06:59PM +0800, zhong jiang wrote: >> On 2017/4/10 20:48, Michal Hocko wrote: >>> On Mon 10-04-17 20:10:06, zhong jiang wrote: >>>> On 2017/4/10 16:56, Mel Gorman wrote: >>>>> On Sat, Apr 08, 2017 at 09:39:42PM +0800, zhong jiang wrote: >>>>>> when runing the stabile docker cases in the vm. The following issue will come up. >>>>>> >>>>>> #40 [ffff8801b57ffb30] async_page_fault at ffffffff8165c9f8 >>>>>> [exception RIP: down_read_trylock+5] >>>>>> RIP: ffffffff810aca65 RSP: ffff8801b57ffbe8 RFLAGS: 00010202 >>>>>> RAX: 0000000000000000 RBX: ffff88018ae858c1 RCX: 0000000000000000 >>>>>> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000008 >>>>>> RBP: ffff8801b57ffc10 R8: ffffea0006903de0 R9: ffff8800b3c61810 >>>>>> R10: 00000000000022cb R11: 0000000000000000 R12: ffff88018ae858c0 >>>>>> R13: ffffea0006903dc0 R14: 0000000000000008 R15: ffffea0006903dc0 >>>>>> ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000 >>>>> Post the full report including the kernel version and state whether any >>>>> additional patches to 3.10 are applied. >>>>> >>>> Hi, Mel >>>> >>>> Our kernel from RHEL 7.2, Addtional patches all from upstream -- include Bugfix and CVE. >>> I believe you should contact Redhat for the support. This is a) old >>> kernel and b) with other patches which might or might not be relevant. >> Ok, regardless of the kernel version, we just discuss the situation in theory. if commit >> 624483f3ea8 ("mm: rmap: fix use-after-free in __put_anon_vma") is not exist. the issue >> will trigger . Any thought. > But this commit was backported into 3.10.43, so stable kernel users are safe. > > Regards, > Willy > > . yes, you are sure that the commit can fix the issue.