On Mon, 4 Feb 2013 13:46:37 -0800 Greg KH <[email protected]> wrote:
> On Mon, Feb 04, 2013 at 12:31:09PM -0800, [email protected] wrote: > > > > The patch titled > > Subject: ext4: fix possible use-after-free with AIO > > has been removed from the -mm tree. Its filename was > > ext4-fix-possible-use-after-free-with-aio.patch > > > > This patch was dropped because it was merged into mainline or a subsystem > > tree > > Any hint from anyone as to where this patch ended up at? Most (all?) of my dropped/merged events are due to the patch turning up in linux-next or mainline. Alas, I very rarely bother to check whether the next/mainline patch has forgotten the -stable tag. I hope that you treat the added/removed mm emails as a hint to go and check. Which is what you did here. > Is this in the > ext4 tree in linux-next and it is marked with a stable@ tag as well? It's in -next and has the stable tag: commit 091e26dfc156aeb3b73bc5c5f277e433ad39331c Author: Jan Kara <[email protected]> AuthorDate: Tue Jan 29 22:48:17 2013 -0500 Commit: Theodore Ts'o <[email protected]> CommitDate: Tue Jan 29 22:48:17 2013 -0500 ext4: 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. CC: [email protected] Reviewed-by: Carlos Maiolino <[email protected]> Acked-by: Jeff Moyer <[email protected]> Signed-off-by: Jan Kara <[email protected]> Signed-off-by: "Theodore Ts'o" <[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
