From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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, linux-fsdevel@vger.kernel.org,
linux-aio@kvack.org, linux-kernel@vger.kernel.org,
miaox@cn.fujitsu.com, tangchen <tangchen@cn.fujitsu.com>,
guz.fnst@cn.fujitsu.com
Subject: Re: [RESEND v2 PATCH 0/2] Bug fix in aio ring page migration
Date: Thu, 13 Mar 2014 17:45:42 +0800 [thread overview]
Message-ID: <53217E46.3060100@cn.fujitsu.com> (raw)
In-Reply-To: <1394439334-28523-1-git-send-email-tangchen@cn.fujitsu.com>
This patchset has been applied to linux-next, and these problems also exist
in 3.12.y and 3.13.y stable tree.
So please merge this patchset to 3.12.y and 3.13.y stable tree.
commit 692c9b8c5ee8d263bb8348171f0bebd3d84eb2c1
Author: Tang Chen <tangchen@cn.fujitsu.com>
Date: Mon Mar 10 16:15:33 2014 +0800
aio, memory-hotplug: Fix confliction when migrating and accessing ring pages.
commit e0f5e0add36d2e3c456cf2f4283673ed834b3c24
Author: Tang Chen <tangchen@cn.fujitsu.com>
Date: Mon Mar 10 16:15:34 2014 +0800
aio, mem-hotplug: Add memory barrier to aio ring page migration.
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/fs/aio.c?id=692c9b8c5ee8d263bb8348171f0bebd3d84eb2c1
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/fs/aio.c?id=e0f5e0add36d2e3c456cf2f4283673ed834b3c24
https://lkml.org/lkml/2014/3/10/56
https://lkml.org/lkml/2014/3/10/58
On 03/10/2014 04:15 PM, Tang Chen wrote:
> 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(-)
>
--
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>
next prev parent reply other threads:[~2014-03-13 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 8:15 [RESEND v2 PATCH 0/2] Bug fix in aio ring page migration Tang Chen
2014-03-10 8:15 ` [RESEND v2 PATCH 1/2] aio, memory-hotplug: Fix confliction when migrating and accessing ring pages Tang Chen
2014-03-11 18:46 ` Benjamin LaHaise
2014-03-12 5:25 ` Tang Chen
2014-03-12 22:17 ` Benjamin LaHaise
2014-03-14 10:25 ` Gu Zheng
2014-03-14 15:14 ` Benjamin LaHaise
2014-03-16 2:06 ` Gu Zheng
2014-03-17 6:50 ` Tang Chen
2014-03-10 8:15 ` [RESEND v2 PATCH 2/2] aio, mem-hotplug: Add memory barrier to aio ring page migration Tang Chen
2014-03-13 9:45 ` Gu Zheng [this message]
2014-03-16 21:21 ` [RESEND v2 PATCH 0/2] Bug fix in " Ben Hutchings
2014-05-13 23:58 ` Greg Kroah-Hartman
2014-05-14 1:13 ` Gu Zheng
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=53217E46.3060100@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=bcrl@kvack.org \
--cc=gregkh@linuxfoundation.org \
--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=stable@vger.kernel.org \
--cc=tangchen@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 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).