From: Dashi DS1 Cao <caods1@lenovo.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Hugh Dickins <hughd@google.com>, Michal Hocko <mhocko@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: A small window for a race condition in mm/rmap.c:page_lock_anon_vma_read
Date: Sun, 25 Dec 2016 02:22:31 +0000 [thread overview]
Message-ID: <23B7B563BA4E9446B962B142C86EF24ADBFD2D@CNMAILEX03.lenovo.com> (raw)
In-Reply-To: <20161223141957.GT3107@twins.programming.kicks-ass.net>
It's a CentOS 7.2, so there is point in asking RHT. I'll try to persuade the customer to have a try with kernel version 4.9, if only I can get it work with CentOS 7.2.
Dashi Cao
-----Original Message-----
From: Peter Zijlstra [mailto:peterz@infradead.org]
Sent: Friday, December 23, 2016 10:20 PM
To: Dashi DS1 Cao <caods1@lenovo.com>
Cc: Hugh Dickins <hughd@google.com>; Michal Hocko <mhocko@kernel.org>; linux-mm@kvack.org; linux-kernel@vger.kernel.org
Subject: Re: A small window for a race condition in mm/rmap.c:page_lock_anon_vma_read
On Fri, Dec 23, 2016 at 02:02:14AM +0000, Dashi DS1 Cao wrote:
> The kernel version is "RELEASE: 3.10.0-327.36.3.el7.x86_64". It was the latest kernel release of CentOS 7.2 at that time, or maybe still now.
This would be the point where we ask you to run a recent upstream kernel and try and reproduce the problem with that, or contact RHT for support on their franken-kernel ;-)
next prev parent reply other threads:[~2016-12-25 2:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 9:32 A small window for a race condition in mm/rmap.c:page_lock_anon_vma_read Dashi DS1 Cao
2016-12-21 14:43 ` Michal Hocko
2016-12-22 11:53 ` Dashi DS1 Cao
2016-12-22 12:03 ` Michal Hocko
2016-12-22 12:43 ` Dashi DS1 Cao
2016-12-22 13:51 ` Peter Zijlstra
2016-12-22 22:26 ` Hugh Dickins
2016-12-23 2:02 ` Dashi DS1 Cao
2016-12-23 3:34 ` Hugh Dickins
2016-12-23 14:19 ` Peter Zijlstra
2016-12-25 2:22 ` Dashi DS1 Cao [this message]
2016-12-23 2:38 ` Dashi DS1 Cao
2017-04-22 12:07 ` 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=23B7B563BA4E9446B962B142C86EF24ADBFD2D@CNMAILEX03.lenovo.com \
--to=caods1@lenovo.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=peterz@infradead.org \
/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).