From: "Pali Rohár" <pali@kernel.org>
To: Paulo Alcantara <pc@manguebit.org>
Cc: Tom Talpey <tom@talpey.com>, Steve French <smfrench@gmail.com>,
Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: Show reason why autodisabling serverino support
Date: Tue, 10 Jun 2025 19:22:21 +0200 [thread overview]
Message-ID: <20250610172221.ihsrjrikbiijyb4n@pali> (raw)
In-Reply-To: <b51772c542618b56cf0fed0cf95836f5@manguebit.org>
On Tuesday 10 June 2025 14:10:00 Paulo Alcantara wrote:
> Pali Rohár <pali@kernel.org> writes:
>
> > For sure I can improve also existing text message. But Tom already sent
> > NACK so I'm not sure if I should continue with improvement or discard it.
>
> Oh, feel free to continue as I'm not the CIFS maintainer, so my NACK
> doesn't matter much.
>
> Go ahead with Steve's suggestion to make those dynamic tracepoints.
> These VFS messages will simply flood dmesg when reconnecting,
> automounting DFS links or surrogate reparse points -- note that they
> expire after 10 minutes, so next access will print the VFS message
> again.
Ok, I will try to improve it and I will start with the text messages.
Tom is right that that currently those text messages are missing
important details.
next prev parent reply other threads:[~2025-06-10 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 16:44 [PATCH] cifs: Show reason why autodisabling serverino support Pali Rohár
2025-06-08 20:57 ` Paulo Alcantara
2025-06-09 3:40 ` Steve French
2025-06-09 7:36 ` Pali Rohár
2025-06-10 15:36 ` Tom Talpey
2025-06-10 16:55 ` Pali Rohár
2025-06-10 17:10 ` Paulo Alcantara
2025-06-10 17:22 ` Pali Rohár [this message]
2025-06-10 18:15 ` [PATCH v2] " Pali Rohár
2025-06-17 22:23 ` Paulo Alcantara
2025-06-17 23:01 ` Pali Rohár
2025-06-17 23:48 ` Paulo Alcantara
2025-06-18 21:53 ` Pali Rohár
-- strict thread matches above, loose matches on Subject: below --
2025-10-09 17:15 [PATCH] " Steve French
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=20250610172221.ihsrjrikbiijyb4n@pali \
--to=pali@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.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