]> code.ossystems Code Review - openembedded-core.git/commit
e2fsprogs: Fix wrong error code after optimization
authorDaniel Schultz <d.schultz@phytec.de>
Mon, 20 Mar 2017 12:18:51 +0000 (13:18 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 21 Mar 2017 22:43:03 +0000 (22:43 +0000)
commit8341ee45d721cf07b19d50c249bb3a77ef1bf100
tree05396de21b2c2e1cb15ab4de2905f9fa7eb449bb
parentfb9fdd7a74917cdcab039aa3a9a9944b18246fea
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: Ross Burton <ross.burton@intel.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.4.bb