The patch titled
Subject: hfsplus: incorrect return value
has been added to the -mm tree. Its filename is
hfsplus-incorrect-return-value.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-incorrect-return-value.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/hfsplus-incorrect-return-value.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Chengyu Song <csong84@xxxxxxxxxx>
Subject: hfsplus: incorrect return value
In case of memory allocation error, the return should be -ENOMEM, instead
of -ENOSPC.
Signed-off-by: Chengyu Song <csong84@xxxxxxxxxx>
Reviewed-by: Sergei Antonov <saproj@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/hfsplus/dir.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN fs/hfsplus/dir.c~hfsplus-incorrect-return-value fs/hfsplus/dir.c
--- a/fs/hfsplus/dir.c~hfsplus-incorrect-return-value
+++ a/fs/hfsplus/dir.c
@@ -434,7 +434,7 @@ static int hfsplus_symlink(struct inode
{
struct hfsplus_sb_info *sbi = HFSPLUS_SB(dir->i_sb);
struct inode *inode;
- int res = -ENOSPC;
+ int res = -ENOMEM;
mutex_lock(&sbi->vh_mutex);
inode = hfsplus_new_inode(dir->i_sb, S_IFLNK | S_IRWXUGO);
@@ -476,7 +476,7 @@ static int hfsplus_mknod(struct inode *d
{
struct hfsplus_sb_info *sbi = HFSPLUS_SB(dir->i_sb);
struct inode *inode;
- int res = -ENOSPC;
+ int res = -ENOMEM;
mutex_lock(&sbi->vh_mutex);
inode = hfsplus_new_inode(dir->i_sb, mode);
_
Patches currently in -mm which might be from csong84@xxxxxxxxxx are
ocfs2-incorrect-check-for-debugfs-returns.patch
hfsplus-incorrect-return-value.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
