On Mon, Mar 31, 2014 at 07:23:59PM -0400, Theodore Ts'o wrote: > On Mon, Mar 31, 2014 at 03:15:44PM -0700, gregkh@xxxxxxxxxxxxxxxxxxx wrote: > > > > This is a note to let you know that I've just added the patch titled > > > > ext4: atomically set inode->i_flags in ext4_set_inode_flags() > > > > to the 3.10-stable tree which can be found at: > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary > > > > The filename of the patch is: > > ext4-atomically-set-inode-i_flags-in-ext4_set_inode_flags.patch > > and it can be found in the queue-3.10 subdirectory. > > I was going to make a one or two minor changes based on akpm's > changes, and this change hasn't been merged upstream yet. The plan > was for this to go upstream in a few more days, after we finish off > some last minute testing, and and fixing a bug in an existing patch in > the ext4 tree that was discovered last week, so if you want to wait a > week, this patch should be upstream by then (and hopefully sooner). > > OTOH, this is a security fix, and the bug has been reported and > outstanding for a while, so if you want to push this sooner, that's > fine. Yes, I'd prefer to take this as-is, and I'll take any "cleanups" later when they hit Linus's tree, if they actually matter. > It should also be noted that a similar bug exists for btrfs and > several other file systems (although btrfs is probably the most > important mainstream fs that should get fixed sooner rather than > later). That would be good to get fixed as well. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html