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
Date: Mon, 10 Apr 2017 16:43:57 +0200 [thread overview]
Message-ID: <20170410144357.GA8092@1wt.eu> (raw)
In-Reply-To: <58EB97D4.1040605@huawei.com>
On Mon, Apr 10, 2017 at 10:33:56PM +0800, zhong jiang wrote:
> 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.
No, I have absolutely no opinion on either the commit nor the bug, what
I'm saying is that any up-to-date 3.10 contains the commit you mentionned,
so if that's the fix, you just need to ensure your kernel is up to date,
that's all.
Willy
next prev parent reply other threads:[~2017-04-10 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 13:39 NULL pointer dereference in the kernel 3.10 zhong jiang
2017-04-10 6:42 ` Hillf Danton
2017-04-10 8:56 ` Xishi Qiu
2017-04-10 9:37 ` Hillf Danton
2017-04-10 9:53 ` Xishi Qiu
2017-04-10 10:08 ` Hillf Danton
2017-04-10 8:56 ` Mel Gorman
2017-04-10 12:10 ` zhong jiang
2017-04-10 12:48 ` Michal Hocko
2017-04-10 14:06 ` zhong jiang
2017-04-10 14:13 ` Willy Tarreau
2017-04-10 14:33 ` zhong jiang
2017-04-10 14:43 ` Willy Tarreau [this message]
2017-04-10 14:06 ` Mel Gorman
2017-04-10 14:11 ` zhong jiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170410144357.GA8092@1wt.eu \
--to=w@1wt.eu \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=zhongjiang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).