From: Vince Busam <vbusam@google.com>
To: nfs@lists.sourceforge.net
Subject: [PATCH] Fix typo on __rpc_purge_upcall
Date: Mon, 21 Nov 2005 11:51:10 -0800 [thread overview]
Message-ID: <4382252E.4000602@google.com> (raw)
I posted this last week. Here's an official style patch.
Vince
------------------------------------------------------------------
Fix an obvious typo that would cause a NULL pointer dereference.
Signed-off-by: Vince Busam <vbusam@google.com>
---
--- linux-2.6.13.4/net/sunrpc/rpc_pipe.c.orig 2005-11-16 16:48:00.000000000 -0800
+++ linux-2.6.13.4/net/sunrpc/rpc_pipe.c 2005-11-16 16:52:23.000000000 -0800
@@ -51,7 +51,7 @@ __rpc_purge_upcall(struct inode *inode,
rpci->ops->destroy_msg(msg);
}
while (!list_empty(&rpci->in_upcall)) {
- msg = list_entry(rpci->pipe.next, struct rpc_pipe_msg, list);
+ msg = list_entry(rpci->in_upcall.next, struct rpc_pipe_msg, list);
list_del_init(&msg->list);
msg->errno = err;
rpci->ops->destroy_msg(msg);
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-11-21 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 19:51 Vince Busam [this message]
2005-11-21 19:55 ` [PATCH] Fix typo on __rpc_purge_upcall Trond Myklebust
2005-11-21 21:51 ` Vince Busam
2005-11-21 22:34 ` Trond Myklebust
2005-11-21 22:59 ` Vince Busam
2005-11-21 23:07 ` Trond Myklebust
2005-11-28 18:16 ` Vince Busam
2005-11-28 18:52 ` Trond Myklebust
2005-12-05 21:03 ` Vince Busam
2005-12-12 18:57 ` Vince Busam
2005-12-12 19:18 ` Trond Myklebust
2005-12-12 20:33 ` Vince Busam
2005-12-12 23:51 ` Trond Myklebust
2006-01-05 22:30 ` Vince Busam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4382252E.4000602@google.com \
--to=vbusam@google.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.