]> code.ossystems Code Review - openembedded-core.git/commit
e2fsprogs: Fix wrong error code after optimization
authorDaniel Schultz <d.schultz@phytec.de>
Wed, 5 Apr 2017 12:48:57 +0000 (14:48 +0200)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 29 Aug 2017 14:11:36 +0000 (15:11 +0100)
commit34ccb6b66162400c3a3164cbdcca02fc1b42c92b
tree19324e8ce6db3e3bd4f28a771ff36cb702fc56b8
parentd767d24edb32f2a4303579371df2e526cdbf5c04
e2fsprogs: Fix wrong error code after optimization

fsck.ext will return an error code of 1 if a file systems was checked
and successfully repaired. Even when an optimization was performed it
will return this error code.

This patch will change the error code to 0 if only optimizations had
changed the file systems.

The reason for this patch is a question I asked at the ext4 ML:
http://www.spinics.net/lists/linux-ext4/msg55700.html

Backport from git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
    Based on commit bf9f3b6d5b10d19218b4ed904c12b22e36ec57dd

Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch [new file with mode: 0644]
meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb