The patch titled
AFS: use patched rxrpc_kernel_send_data() correctly
has been added to the -mm tree. Its filename is
afs-use-patched-rxrpc_kernel_send_data-correctly.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: AFS: use patched rxrpc_kernel_send_data() correctly
From: David Howells <dhowells@xxxxxxxxxx>
Fix afs_send_simple_reply() to accept a greater-than-zero return value from
rxrpc_kernel_send_data() as being a successful return rather than thinking
it an error and aborting the call.
rxrpc_kernel_send_data() previously returned zero incorrectly when it
worked successfully, but has been patched to return the number of bytes it
transmitted.
Signed-off-by: David Howells <dhowells@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/afs/rxrpc.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff -puN fs/afs/rxrpc.c~afs-use-patched-rxrpc_kernel_send_data-correctly fs/afs/rxrpc.c
--- a/fs/afs/rxrpc.c~afs-use-patched-rxrpc_kernel_send_data-correctly
+++ a/fs/afs/rxrpc.c
@@ -792,6 +792,7 @@ void afs_send_simple_reply(struct afs_ca
{
struct msghdr msg;
struct iovec iov[1];
+ int n;
_enter("");
@@ -806,8 +807,9 @@ void afs_send_simple_reply(struct afs_ca
msg.msg_flags = 0;
call->state = AFS_CALL_AWAIT_ACK;
- switch (rxrpc_kernel_send_data(call->rxcall, &msg, len)) {
- case 0:
+ n = rxrpc_kernel_send_data(call->rxcall, &msg, len);
+ switch (n) {
+ case 0 ... INT_MAX:
_leave(" [replied]");
return;
_
Patches currently in -mm which might be from dhowells@xxxxxxxxxx are
origin.patch
nommu-present-backing-device-capabilities-for-mtd.patch
nommu-add-support-for-direct-mapping-through-mtdconcat.patch
afs-fix-file-locking.patch
afs-use-patched-rxrpc_kernel_send_data-correctly.patch
mutex-subsystem-synchro-test-module.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
