Re: [RESEND v2 PATCH 0/2] Bug fix in aio ring page migration

[Gu Zheng]

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@xxxxxxxxxxxxxx>
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@xxxxxxxxxxxxxx>
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/