Comments

When argument '-n' was specified and should run in read-only mode, we
should not attempt to discard anything. In order to do that we have to
check for E2F_OPT_NO flag and clear E2F_OPT_DISCARD flag if E2F_OPT_NO
is set.
This commit fixes the problem when we would mark inode tables as zeroed
(EXT2_BG_INODE_ZEROED) even when e2fsck is running in read-only mode. We
also move the check for E2F_OPT_NO so we can clear E2F_OPT_DISCARD as
early as possible.
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
---
e2fsck/pass5.c | 5 ++---
e2fsck/unix.c | 5 +++++
2 files changed, 7 insertions(+), 3 deletions(-)

On Mon, Mar 05, 2012 at 08:49:35AM +0100, Lukas Czerner wrote:
> When argument '-n' was specified and should run in read-only mode, we> should not attempt to discard anything. In order to do that we have to> check for E2F_OPT_NO flag and clear E2F_OPT_DISCARD flag if E2F_OPT_NO> is set.> > This commit fixes the problem when we would mark inode tables as zeroed> (EXT2_BG_INODE_ZEROED) even when e2fsck is running in read-only mode. We> also move the check for E2F_OPT_NO so we can clear E2F_OPT_DISCARD as> early as possible.> > Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Applied, thanks.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html