All of lore.kernel.org
 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, Miao Xie <miaox@cn.fujitsu.com>
Subject: [V2 PATCH 0/2] Bug fix in aio ring page migration
Date: Mon, 10 Mar 2014 13:30:34 +0800	[thread overview]
Message-ID: <531D4DFA.4000809@cn.fujitsu.com> (raw)
In-Reply-To: <1393403919-1178-1-git-send-email-tangchen@cn.fujitsu.com>

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 |   42 ++++++++++++++++++++++++++++++++++++++++++
  1 files changed, 42 insertions(+), 0 deletions(-)

-- 
1.7.7

--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org.  For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

WARNING: multiple messages have this Message-ID (diff)
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, Miao Xie <miaox@cn.fujitsu.com>
Subject: [V2 PATCH 0/2] Bug fix in aio ring page migration
Date: Mon, 10 Mar 2014 13:30:34 +0800	[thread overview]
Message-ID: <531D4DFA.4000809@cn.fujitsu.com> (raw)
In-Reply-To: <1393403919-1178-1-git-send-email-tangchen@cn.fujitsu.com>

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 |   42 ++++++++++++++++++++++++++++++++++++++++++
  1 files changed, 42 insertions(+), 0 deletions(-)

-- 
1.7.7

  parent reply	other threads:[~2014-03-10  5:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26  8:38 [PATCH 1/1] aio, memory-hotplug: Fix confliction when migrating and accessing ring pages Tang Chen
2014-02-26  8:38 ` Tang Chen
2014-02-27  0:26 ` Tang Chen
2014-02-27  0:26   ` Tang Chen
2014-02-27 10:03   ` Benjamin LaHaise
2014-02-27 10:03     ` Benjamin LaHaise
2014-02-27 14:38     ` tom
2014-03-10  5:30 ` Tang Chen [this message]
2014-03-10  5:30   ` [V2 PATCH 0/2] Bug fix in aio ring page migration Tang Chen
2014-03-10  5:30 ` [V2 PATCH 1/2] aio, memory-hotplug: Fix confliction when migrating and, accessing ring pages Tang Chen
2014-03-10  5:30   ` Tang Chen
2014-03-10  5:31 ` [V2 PATCH 2/2] aio, mem-hotplug: Add memory barrier to aio ring page migration Tang Chen
2014-03-10  5:31   ` Tang Chen

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=531D4DFA.4000809@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=miaox@cn.fujitsu.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.