lkml.org 
[lkml]   [2017]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] ext4: Return EIO on read error in ext4_find_entry
Date
On Jun 22, 2017, at 22:43, Theodore Ts'o <tytso@mit.edu> wrote:
>
>> On Thu, Jun 22, 2017 at 04:23:07PM -0700, Khazhismel Kumykov wrote:
>> Previously, a read error would be ignored and we would eventually return
>> NULL from ext4_find_entry, which signals "no such file or directory". We
>> should be returning EIO.
>>
>> Signed-off-by: Khazhismel Kumykov <khazhy@google.com>
>
> Thanks, applied.

I don't necessarily agree that this is an improvement.

If the requested entry is not in the bad block, this will return an error even if the file name could be found in another block. It would be better to save the error until the end and only return -EIO if the entry cannot be found.

Cheers, Andreas
\
 
 \ /
  Last update: 2017-06-23 08:59    [W:0.084 / U:5.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site