Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751646AbcLCVo3 (ORCPT ); Sat, 3 Dec 2016 16:44:29 -0500 Received: from imap.thunk.org ([74.207.234.97]:33982 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751072AbcLCVo1 (ORCPT ); Sat, 3 Dec 2016 16:44:27 -0500 Date: Sat, 3 Dec 2016 16:44:21 -0500 From: "Theodore Ts'o" To: "Darrick J. Wong" Cc: Fabian Frederick , linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org Subject: Re: [PATCH 1/1 linux-next] ext4: fix block_validity definition Message-ID: <20161203214421.ykmrs5rtzuduz4es@thunk.org> Mail-Followup-To: Theodore Ts'o , "Darrick J. Wong" , Fabian Frederick , linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org References: <1477251814-9938-1-git-send-email-fabf@skynet.be> <20161023201003.GA5245@birch.djwong.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161023201003.GA5245@birch.djwong.org> User-Agent: NeoMutt/20161104 (1.7.1) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 480 Lines: 12 I've applied this patch with some further cleanups. The documentation for the mount options now reads: block_validity(*) These options enable or disable the in-kernel noblock_validity facility for tracking filesystem metadata blocks within internal data structures. This allows multi- block allocator and other routines to notice bugs or corrupted allocation bitmaps which cause blocks to be allocated which overlap with filesystem metadata blocks. - Ted