Instead of -1, properly return -EIO upon write_inode()
error, similar/consistant to the rest of filesystems.
Signed-off-by: Taesoo Kim <tsgat...@gmail.com>
---
fs/ufs/inode.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/ufs/inode.c b/fs/ufs/inode.c
index be7d42c..9f910d8 100644
--- a/fs/ufs/inode.c
+++ b/fs/ufs/inode.c
@@ -836,13 +836,13 @@ static int ufs_update_inode(struct inode * inode, int
do_sync)
if (inode->i_ino < UFS_ROOTINO ||
inode->i_ino > (uspi->s_ncg * uspi->s_ipg)) {
ufs_warning (sb, "ufs_read_inode", "bad inode number (%lu)\n",
inode->i_ino);
- return -1;
+ return -EIO;
}
bh = sb_bread(sb, ufs_inotofsba(inode->i_ino));
if (!bh) {
ufs_warning (sb, "ufs_read_inode", "unable to read inode
%lu\n", inode->i_ino);
- return -1;
+ return -EIO;
}
if (uspi->fs_magic == UFS2_MAGIC) {
struct ufs2_inode *ufs2_inode = (struct ufs2_inode *)bh->b_data;
--
2.3.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
