tree 251f0feaddfbbf6e98690943d470972d7b37c3d6
parent 951555856b88aa47bc238de6b4c6e97bfd9d36df
author Filipe Manana <fdmanana@suse.com> 1465210285 +0100
committer Filipe Manana <fdmanana@suse.com> 1470033123 +0100

Btrfs: be more precise on errors when getting an inode from disk

When we attempt to read an inode from disk, we end up always returning an
-ESTALE error to the caller regardless of the actual failure reason, which
can be an out of memory problem (when allocating a path), some error found
when reading from the fs/subvolume btree (like a genuine IO error) or the
inode does not exists. So lets start returning the real error code to the
callers so that they don't treat all -ESTALE errors as meaning that the
inode does not exists (such as during orphan cleanup). This will also be
needed for a subsequent patch in the same series dealing with a special
fsync case.

Signed-off-by: Filipe Manana <fdmanana@suse.com>