Subject: + binfmt_misc-add-missing-break-statement.patch added to -mm tree
To: luis.henriques@xxxxxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Fri, 28 Mar 2014 16:05:51 -0700
The patch titled
Subject: binfmt_misc: add missing 'break' statement
has been added to the -mm tree. Its filename is
binfmt_misc-add-missing-break-statement.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/binfmt_misc-add-missing-break-statement.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/binfmt_misc-add-missing-break-statement.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: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
Subject: binfmt_misc: add missing 'break' statement
A missing 'break' statement in bm_status_write() results in a user program
receiving '3' when doing the following:
write(fd, "-1", 2);
Signed-off-by: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/binfmt_misc.c | 1 +
1 file changed, 1 insertion(+)
diff -puN fs/binfmt_misc.c~binfmt_misc-add-missing-break-statement fs/binfmt_misc.c
--- a/fs/binfmt_misc.c~binfmt_misc-add-missing-break-statement
+++ a/fs/binfmt_misc.c
@@ -656,6 +656,7 @@ static ssize_t bm_status_write(struct fi
mutex_unlock(&root->d_inode->i_mutex);
dput(root);
+ break;
default: return res;
}
return count;
_
Patches currently in -mm which might be from luis.henriques@xxxxxxxxxxxxx are
binfmt_misc-add-missing-break-statement.patch
linux-next.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
