From: Yunseong Kim <yunseong.kim@est.tech>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Yunseong Kim <yunseong.kim@est.tech>,
Steve French <stfrench@microsoft.com>,
David Howells <dhowells@redhat.com>,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
linux-kernel@vger.kernel.org, Paulo Alcantara <pc@manguebit.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Tom Talpey <tom@talpey.com>, Bharath SM <bharathsm@microsoft.com>
Subject: Re: [PATCH v1 1/1] smb: client: transport: Fix debug printing in __release_mid()
Date: Wed, 26 Aug 2026 01:34:06 +0200 [thread overview]
Message-ID: <20260825233419.762040-1-yunseong.kim@est.tech> (raw)
In-Reply-To: <20260825083043.4037868-1-andriy.shevchenko@linux.intel.com>
Hi Andy,
On Tue, 25 Aug 2026 10:30:43 +0200 Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> Long time ago during upgrading printk():s to the respective pr_<level>()
> calls one misconversion happened and nobody has noticed that. So,
> previously printk(KERN_DEBUG) + printk() worked as one long debug print
> since the trailing '\n' is only present in the followup printk() format
> string. The culprit change missed that and split the message to two on
> the different levels. Restore the original behaviour to make users be
> less confused in the most likely never happen cases of partially getting
> that message.
>
> Fixes: 0b456f04bcdf ("cifs: convert printk(LEVEL...) to pr_<level>")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> fs/smb/client/transport.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/fs/smb/client/transport.c b/fs/smb/client/transport.c
> index fdf4e50c27ce..e266859818a4 100644
> --- a/fs/smb/client/transport.c
> +++ b/fs/smb/client/transport.c
> @@ -101,12 +101,11 @@ void __release_mid(struct TCP_Server_Info *server, struct mid_q_entry *midEntry)
> trace_smb3_slow_rsp(smb_cmd, midEntry->mid, midEntry->pid,
> midEntry->when_sent, midEntry->when_received);
> if (cifsFYI & CIFS_TIMER) {
> - pr_debug("slow rsp: cmd %d mid %llu",
> - midEntry->command, midEntry->mid);
> - cifs_info("A: 0x%lx S: 0x%lx R: 0x%lx\n",
> - now - midEntry->when_alloc,
> - now - midEntry->when_sent,
> - now - midEntry->when_received);
> + pr_debug("slow rsp: cmd %d mid %llu A: 0x%lx S: 0x%lx R: 0x%lx\n",
> + midEntry->command, midEntry->mid,
The change looks correct to me.
One minor suggestion: could the format string be split using adjacent
string literals to avoid the long source line?
pr_debug("slow rsp: cmd %d mid %llu "
"A: 0x%lx S: 0x%lx R: 0x%lx\n",
...);
> + now - midEntry->when_alloc,
> + now - midEntry->when_sent,
> + now - midEntry->when_received);
> }
> }
> #endif
> --
> 2.50.1
>
>
Thank you!
Best regards,
Yunseong
next prev parent reply other threads:[~2026-08-25 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 8:30 Andy Shevchenko
2026-08-25 23:34 ` Yunseong Kim [this message]
2026-08-26 8:04 ` Andy Shevchenko
2026-08-27 2:22 ` Paulo Alcantara
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=20260825233419.762040-1-yunseong.kim@est.tech \
--to=yunseong.kim@est.tech \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bharathsm@microsoft.com \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sprasad@microsoft.com \
--cc=stfrench@microsoft.com \
--cc=tom@talpey.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
all inboxes | Powered by JetHome®