From: Jeff Layton <jlayton@redhat.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v3 1/9] nfsdcltrack: fix segfault in sqlite debug logging
Date: Thu, 25 Oct 2012 13:21:35 -0400 [thread overview]
Message-ID: <1351185703-14191-2-git-send-email-jlayton@redhat.com> (raw)
In-Reply-To: <1351185703-14191-1-git-send-email-jlayton@redhat.com>
One too few arguments...
Signed-off-by: Jeff Layton <jlayton@redhat.com>
---
utils/nfsdcld/sqlite.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/utils/nfsdcld/sqlite.c b/utils/nfsdcld/sqlite.c
index bb2519d..fc882c6 100644
--- a/utils/nfsdcld/sqlite.c
+++ b/utils/nfsdcld/sqlite.c
@@ -320,7 +320,7 @@ sqlite_check_client(const unsigned char *clname, const size_t namelen)
}
ret = sqlite3_column_int(stmt, 0);
- xlog(D_GENERAL, "%s: select returned %d rows", ret);
+ xlog(D_GENERAL, "%s: select returned %d rows", __func__, ret);
if (ret != 1) {
ret = -EACCES;
goto out_err;
--
1.7.11.7
next prev parent reply other threads:[~2012-10-25 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 17:21 [PATCH v3 0/9] nfsdcltrack: create a new usermodehelper upcall program for tracking clients Jeff Layton
2012-10-25 17:21 ` Jeff Layton [this message]
2012-10-25 17:21 ` [PATCH v3 2/9] nfsdcltrack: rename the nfsdcld directory and options to nfsdcltrack Jeff Layton
2012-10-25 17:21 ` [PATCH v3 3/9] nfsdcltrack: remove pointless sqlite_topdir variable Jeff Layton
2012-10-25 17:21 ` [PATCH v3 4/9] nfsdcltrack: break out a function to open the database handle Jeff Layton
2012-10-25 17:21 ` [PATCH v3 5/9] nfsdcltrack: add a new "one-shot" program for manipulating the client tracking db Jeff Layton
2012-10-25 17:21 ` [PATCH v3 6/9] nfsdcltrack: add a legacy transition mechanism Jeff Layton
2012-10-25 17:21 ` [PATCH v3 7/9] nfsdcltrack: add a manpage for nfsdcltrack Jeff Layton
2012-10-25 17:21 ` [PATCH v3 8/9] nfsdcltrack: remove the nfsdcld daemon Jeff Layton
2012-10-25 17:21 ` [PATCH v3 9/9] nfsdcltrack: update the README about server startup order Jeff Layton
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=1351185703-14191-2-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).