From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com ([66.111.4.29]:52548 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932362AbcEBXoe (ORCPT ); Mon, 2 May 2016 19:44:34 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B213D20A05 for ; Mon, 2 May 2016 19:44:33 -0400 (EDT) Date: Mon, 2 May 2016 16:44:32 -0700 From: Greg KH To: Jan Kara Cc: stable@vger.kernel.org, xfs@oss.sgi.com, Dave Chinner Subject: Re: XFS hole punch races Message-ID: <20160502234432.GB14806@kroah.com> References: <20160322155740.GB28772@quack.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160322155740.GB28772@quack.suse.cz> Sender: stable-owner@vger.kernel.org List-ID: On Tue, Mar 22, 2016 at 04:57:40PM +0100, Jan Kara wrote: > Hi, > > similarly to ext4 also XFS had races between hole punching and page faults > which could result in data corruption. The fixes were merged in 4.1-rc1 but > it might make sense to backport them to older stable releases given the > nature of the issue. > > Relevant fixes are: > > de0e8c20ba3a65b0f15040aabbefdc1999876e6b > 075a924d45cc69c75a35f20b4912b85aa98b180a > e8e9ad42c1f1e1bfbe0e8c32c8cac02e9ebfb7ef > 0f9160b444e4de33b65dfcd3b901358a3129461a > 723cac48473358939759885a18e8df113ea96138 > ec56b1f1fdc69599963574ce94cc5693d535dd64 None of these apply to 3.14-stable, so I'm not going to worry about them :) thanks, greg k-h