The patch titled
Subject: hfs: incorrect return values
has been added to the -mm tree. Its filename is
hfs-incorrect-return-values.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/hfs-incorrect-return-values.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/hfs-incorrect-return-values.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: hfs: incorrect return values
In case of memory allocation error, the return should be -ENOMEM, instead
of -ENOSPC.
Signed-off-by: Chengyu Song <csong84@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/hfs/dir.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN fs/hfs/dir.c~hfs-incorrect-return-values fs/hfs/dir.c
--- a/fs/hfs/dir.c~hfs-incorrect-return-values
+++ a/fs/hfs/dir.c
@@ -197,7 +197,7 @@ static int hfs_create(struct inode *dir,
inode = hfs_new_inode(dir, &dentry->d_name, mode);
if (!inode)
- return -ENOSPC;
+ return -ENOMEM;
res = hfs_cat_create(inode->i_ino, dir, &dentry->d_name, inode);
if (res) {
@@ -226,7 +226,7 @@ static int hfs_mkdir(struct inode *dir,
inode = hfs_new_inode(dir, &dentry->d_name, S_IFDIR | mode);
if (!inode)
- return -ENOSPC;
+ return -ENOMEM;
res = hfs_cat_create(inode->i_ino, dir, &dentry->d_name, inode);
if (res) {
_
Patches currently in -mm which might be from csong84@xxxxxxxxxx are
ocfs2-incorrect-check-for-debugfs-returns.patch
hfs-incorrect-return-values.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
