From: Eric Van Hensbergen <ericvh@gmail.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net,
Eric Van Hensbergen <ericvh@strongmad.texas.9grid.us>,
Eric Van Hensbergen <ericvh@gmail.com>
Subject: [PATCH] 9p: null terminate error strings for debug print
Date: Mon, 22 Jan 2007 19:36:33 -0600 [thread overview]
Message-ID: <11695161931724-git-send-email-ericvh@gmail.com> (raw)
From: Eric Van Hensbergen <ericvh@strongmad.texas.9grid.us> - unquoted
We weren't properly NULL terminating protocol error strings for our
debug printk resulting in garbage being included in the output when debug
was enabled.
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
---
fs/9p/error.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fs/9p/error.c b/fs/9p/error.c
index ae91555..0d7fa4e 100644
--- a/fs/9p/error.c
+++ b/fs/9p/error.c
@@ -83,6 +83,7 @@ int v9fs_errstr2errno(char *errstr, int len)
if (errno == 0) {
/* TODO: if error isn't found, add it dynamically */
+ errstr[len] = 0;
printk(KERN_ERR "%s: errstr :%s: not found\n", __FUNCTION__,
errstr);
errno = 1;
--
1.5.0.rc1.gde38
reply other threads:[~2007-01-23 1:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=11695161931724-git-send-email-ericvh@gmail.com \
--to=ericvh@gmail.com \
--cc=akpm@osdl.org \
--cc=ericvh@strongmad.texas.9grid.us \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox