Acked-by: Joel Becker <[email protected]>

On Tue, Jan 29, 2013 at 03:47:59PM -0800, [email protected] wrote:
> 
> The patch titled
>      Subject: ocfs2: fix possible use-after-free with AIO
> has been added to the -mm tree.  Its filename is
>      ocfs2-fix-possible-use-after-free-with-aio.patch
> 
> Before you just go and hit "reply", please:
>    a) Consider who else should be cc'ed
>    b) Prefer to cc a suitable mailing list as well
>    c) Ideally: find the original patch on the mailing list and do a
>       reply-to-all to that, adding suitable additional cc's
> 
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
> 
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
> 
> ------------------------------------------------------
> From: Jan Kara <[email protected]>
> Subject: ocfs2: fix possible use-after-free with AIO
> 
> Running AIO is pinning inode in memory using file reference. Once AIO
> is completed using aio_complete(), file reference is put and inode can
> be freed from memory. So we have to be sure that calling aio_complete()
> is the last thing we do with the inode.
> 
> Signed-off-by: Jan Kara <[email protected]>
> Acked-by: Jeff Moyer <[email protected]>
> Cc: Joel Becker <[email protected]>
> Cc: Mark Fasheh <[email protected]>
> Cc: Al Viro <[email protected]>
> Cc: <[email protected]>
> Signed-off-by: Andrew Morton <[email protected]>
> ---
> 
>  fs/ocfs2/aops.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff -puN fs/ocfs2/aops.c~ocfs2-fix-possible-use-after-free-with-aio 
> fs/ocfs2/aops.c
> --- a/fs/ocfs2/aops.c~ocfs2-fix-possible-use-after-free-with-aio
> +++ a/fs/ocfs2/aops.c
> @@ -593,9 +593,9 @@ static void ocfs2_dio_end_io(struct kioc
>       level = ocfs2_iocb_rw_locked_level(iocb);
>       ocfs2_rw_unlock(inode, level);
>  
> +     inode_dio_done(inode);
>       if (is_async)
>               aio_complete(iocb, ret, 0);
> -     inode_dio_done(inode);
>  }
>  
>  /*
> _
> 
> Patches currently in -mm which might be from [email protected] are
> 
> linux-next.patch
> fs-change-return-values-from-eacces-to-eperm.patch
> bdi-allow-block-devices-to-say-that-they-require-stable-page-writes.patch
> mm-only-enforce-stable-page-writes-if-the-backing-device-requires-it.patch
> 9pfs-fix-filesystem-to-wait-for-stable-page-writeback.patch
> block-optionally-snapshot-page-contents-to-provide-stable-pages-during-write.patch
> ocfs2-wait-for-page-writeback-to-provide-stable-pages.patch
> ubifs-wait-for-page-writeback-to-provide-stable-pages.patch
> hfsplus-add-osx-prefix-for-handling-namespace-of-mac-os-x-extended-attributes.patch
> hfsplus-add-on-disk-layout-declarations-related-to-attributes-tree.patch
> hfsplus-add-functionality-of-manipulating-by-records-in-attributes-tree.patch
> hfsplus-rework-functionality-of-getting-setting-and-deleting-of-extended-attributes.patch
> hfsplus-add-support-of-manipulation-by-attributes-file.patch
> ext4-fix-possible-use-after-free-with-aio.patch
> ocfs2-fix-possible-use-after-free-with-aio.patch
> fs-direct-ioc-fix-possible-use-after-free-with-aio.patch
> 

-- 

Life's Little Instruction Book #407

        "Every once in a while, take the scenic route."

                        http://www.jlbec.org/
                        [email protected]
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to