From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: dhowells@redhat.com, linux-cachefs@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] fscache: offer the right volume key when printing
Date: Thu, 9 Feb 2023 11:52:24 +0800 [thread overview]
Message-ID: <20230209035224.8317-1-jefflexu@linux.alibaba.com> (raw)
This is a trivial fix as the first slot of volume->key[] actually stores
the length of the volume key.
Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
---
fs/fscache/cookie.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/fscache/cookie.c b/fs/fscache/cookie.c
index bce2492186d0..ea13697a8556 100644
--- a/fs/fscache/cookie.c
+++ b/fs/fscache/cookie.c
@@ -46,7 +46,7 @@ void fscache_print_cookie(struct fscache_cookie *cookie, char prefix)
pr_err("%c-cookie V=%08x [%s]\n",
prefix,
cookie->volume->debug_id,
- cookie->volume->key);
+ cookie->volume->key + 1);
k = (cookie->key_len <= sizeof(cookie->inline_key)) ?
cookie->inline_key : cookie->key;
--
2.19.1.6.gb485710b
reply other threads:[~2023-02-09 3:52 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=20230209035224.8317-1-jefflexu@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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