From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:51765 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727482AbfCWQNr (ORCPT ); Sat, 23 Mar 2019 12:13:47 -0400 Date: Sat, 23 Mar 2019 12:13:34 -0400 From: "Theodore Ts'o" Subject: Re: [PATCH] ext4: prohibit fstrim in norecovery mode Message-ID: <20190323161334.GE5675@mit.edu> References: <20190323003532.GB1180@magnolia> <20190323003813.GR1183@magnolia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190323003813.GR1183@magnolia> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: "Darrick J. Wong" Cc: Eryu Guan , fstests , xfs , linux-ext4 On Fri, Mar 22, 2019 at 05:38:13PM -0700, Darrick J. Wong wrote: > From: Darrick J. Wong > > The ext4 fstrim implementation uses the block bitmaps to find free space > that can be discarded. If we haven't replayed the journal, the bitmaps > will be stale and we absolutely *cannot* use stale metadata to zap the > underlying storage. > > Signed-off-by: Darrick J. Wong Thanks, applied. - Ted