From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753379AbdDJOOH (ORCPT <rfc822;w@1wt.eu>);
        Mon, 10 Apr 2017 10:14:07 -0400
Received: from wtarreau.pck.nerim.net ([62.212.114.60]:25112 "EHLO 1wt.eu"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753566AbdDJOOG (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 10 Apr 2017 10:14:06 -0400
Date: Mon, 10 Apr 2017 16:13:21 +0200
From: Willy Tarreau <w@1wt.eu>
To: zhong jiang <zhongjiang@huawei.com>
Cc: Michal Hocko <mhocko@kernel.org>,
        Mel Gorman <mgorman@techsingularity.net>,
        Johannes Weiner <hannes@cmpxchg.org>, vdavydov.dev@gmail.com,
        Vlastimil Babka <vbabka@suse.cz>,
        Linux Memory Management List <linux-mm@kvack.org>,
        LKML <linux-kernel@vger.kernel.org>
Subject: Re: NULL pointer dereference in the kernel 3.10
Message-ID: <20170410141321.GB8008@1wt.eu>
References: <58E8E81E.6090304@huawei.com>
 <20170410085604.zpenj6ggc3dsbgxw@techsingularity.net>
 <58EB761E.9040002@huawei.com>
 <20170410124814.GC4618@dhcp22.suse.cz>
 <58EB9183.2030806@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <58EB9183.2030806@huawei.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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