From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Hugh Dickins" <hughd@google.com>,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
"Minchan Kim" <minchan@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Tim Chen" <tim.c.chen@linux.intel.com>,
"Mel Gorman" <mgorman@techsingularity.net>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Michal Hocko" <mhocko@suse.com>,
"Andrea Arcangeli" <aarcange@redhat.com>,
"David Rientjes" <rientjes@google.com>,
"Rik van Riel" <riel@redhat.com>, "Jan Kara" <jack@suse.cz>,
"Dave Jiang" <dave.jiang@intel.com>,
"Daniel Jordan" <daniel.m.jordan@oracle.com>
Subject: Re: [PATCH -mm -V7] mm, swap: fix race between swapoff and some swap operations
Date: Tue, 12 Feb 2019 11:13:16 +0100 [thread overview]
Message-ID: <20190212101316.GA6905@andrea> (raw)
In-Reply-To: <20190211083846.18888-1-ying.huang@intel.com>
> Alternative implementation could be replacing disable preemption with
> rcu_read_lock_sched and stop_machine() with synchronize_sched().
JFYI, starting with v4.20-rc1, synchronize_rcu{,expedited}() also wait
for preempt-disable sections (the intent seems to retire the RCU-sched
update-side API), so that here you could instead use preempt-disable +
synchronize_rcu{,expedited}(). This LWN article gives an overview of
the latest RCU API/semantics changes: https://lwn.net/Articles/777036/.
Andrea
next prev parent reply other threads:[~2019-02-12 10:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 8:38 Huang, Ying
2019-02-11 19:06 ` Daniel Jordan
2019-02-12 3:21 ` Andrea Parri
2019-02-12 6:47 ` Huang, Ying
2019-02-12 17:58 ` Tim Chen
2019-02-13 3:23 ` Huang, Ying
2019-02-12 20:06 ` Daniel Jordan
2019-02-12 6:40 ` Huang, Ying
2019-02-12 10:13 ` Andrea Parri [this message]
2019-02-15 6:34 ` Huang, Ying
2019-02-14 2:38 ` Andrea Arcangeli
2019-02-14 8:07 ` Huang, Ying
2019-02-14 21:47 ` Andrea Arcangeli
2019-02-15 7:50 ` Huang, Ying
2019-02-14 14:33 ` Michal Hocko
2019-02-14 20:30 ` Andrew Morton
2019-02-14 21:22 ` Andrea Arcangeli
2019-02-15 7:08 ` Huang, Ying
2019-02-15 13:11 ` Michal Hocko
2019-02-18 0:51 ` Huang, Ying
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=20190212101316.GA6905@andrea \
--to=andrea.parri@amarulasolutions.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.m.jordan@oracle.com \
--cc=dave.jiang@intel.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=tim.c.chen@linux.intel.com \
--cc=ying.huang@intel.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