Re: [PATCH 12/30] IGET: Stop EXT3 from using iget() and read_inode()

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Jan Kara <jack@...>
Cc: <dhowells@...>, <hch@...>, <viro@...>, <torvalds@...>, <akpm@...>, <linux-kernel@...>, <linux-fsdevel@...>
Date: Tuesday, October 2, 2007 - 9:16 am

Jan Kara <jack@suse.cz> wrote:


Ugh.  Okay, I need to rework the changes to that function.


I would have thought so, but -EACCES was what it returned before I touched it.
OTOH, it's calling ext3_error(), so EIO ought to be the right thing to do.
I'll alter it and see if anyone complains.


I do wonder why it used to return EINVAL rather than EIO.  It's understandable
if the magic number doesn't match, but if it appears to be an otherwise
corrupt filesystem, then yes, I guess it should return EIO.  I'll change it.

David
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 00/30] Remove iget() and read_inode(), David Howells, (Mon Oct 1, 9:09 am)
[PATCH 18/30] IGET: Stop ISOFS from using read_inode(), David Howells, (Mon Oct 1, 9:10 am)
Re: [PATCH 12/30] IGET: Stop EXT3 from using iget() and read..., David Howells, (Tue Oct 2, 9:16 am)
[PATCH 03/30] IGET: Use iget_failed() in GFS2, David Howells, (Mon Oct 1, 9:09 am)
[PATCH 02/30] IGET: Use iget_failed() in AFS, David Howells, (Mon Oct 1, 9:09 am)