summaryrefslogtreecommitdiffstats
path: root/fs/jfs/jfs_mount.c
diff options
context:
space:
mode:
authorAkinobu Mita <mita@miraclelinux.com>2006-09-14 09:22:38 -0500
committerDave Kleikamp <shaggy@austin.ibm.com>2006-10-02 09:51:01 -0500
commit087387f90f577f5a0ab68d33ef326c9bb6d80dda (patch)
tree99f2ba6f672c9d98fbd628ee54120f63593f1bd0 /fs/jfs/jfs_mount.c
parent2a6968a9784551c216f9379a728d4104dbad98a8 (diff)
downloadop-kernel-dev-087387f90f577f5a0ab68d33ef326c9bb6d80dda.zip
op-kernel-dev-087387f90f577f5a0ab68d33ef326c9bb6d80dda.tar.gz
[PATCH] JFS: return correct error when i-node allocation failed
I have seen confusing behavior on JFS when I injected many intentional slab allocation errors. The cp command failed with no disk space error with enough disk space. This patch makes: - change the return value in case slab allocation failures happen from -ENOSPC to -ENOMEM - ialloc() return error code so that the caller can know the reason of failures Signed-off-by: Akinobu Mita <mita@miraclelinux.com> Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com> (cherry picked from 2b46f77976f798f3fe800809a1d0ed38763c71c8 commit)
Diffstat (limited to 'fs/jfs/jfs_mount.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud