mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: viro@zeniv.linux.org.uk, bcrl@kvack.org, jmoyer@redhat.com,
	kosaki.motohiro@gmail.com, kosaki.motohiro@jp.fujitsu.com,
	isimatu.yasuaki@jp.fujitsu.com, guz.fnst@cn.fujitsu.com
Cc: linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Bug fix in aio ring page migration.
Date: Thu, 27 Feb 2014 18:40:14 +0800	[thread overview]
Message-ID: <1393497616-16428-1-git-send-email-tangchen@cn.fujitsu.com> (raw)

This patch-set fixes the following two problems:

1. Need to use ctx->completion_lock to protect ring pages 
   from being mis-written while migration.

2. Need memory barrier to ensure memory copy is done before 
   ctx->ring_pages[] is updated.

NOTE: AIO ring page migration was implemented since Linux 3.12.
      So we need to merge these two patches into 3.12 stable tree.  


Tang Chen (2):
  aio, memory-hotplug: Fix confliction when migrating and accessing ring
    pages.
  aio, mem-hotplug: Add memory barrier to aio ring page migration.

 fs/aio.c | 41 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)

-- 
1.8.3.1


             reply	other threads:[~2014-02-27 10:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 10:40 Tang Chen [this message]
2014-02-27 10:40 ` [PATCH 1/2] aio, memory-hotplug: Fix confliction when migrating and accessing ring pages Tang Chen
2014-03-05 19:23   ` Jeff Moyer
2014-02-27 10:40 ` [PATCH 2/2] aio, mem-hotplug: Add memory barrier to aio ring page migration Tang Chen
2014-02-27 12:06   ` Yasuaki Ishimatsu
2014-02-27 12:44     ` [Update PATCH " Yasuaki Ishimatsu
2014-03-04  5:35       ` Miao Xie
2014-03-05  3:04         ` KOSAKI Motohiro
2014-03-05  6:59         ` Yasuaki Ishimatsu
2014-03-05  7:17       ` [Update v2 " Yasuaki Ishimatsu
2014-02-27 14:57   ` [PATCH " Benjamin LaHaise
2014-02-28  1:29     ` Gu Zheng
2014-02-28  7:25     ` Yasuaki Ishimatsu

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=1393497616-16428-1-git-send-email-tangchen@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=bcrl@kvack.org \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=jmoyer@redhat.com \
    --cc=kosaki.motohiro@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®