From: "Pali Rohár" <pali@kernel.org>
To: Tom Talpey <tom@talpey.com>
Cc: Steve French <smfrench@gmail.com>,
Paulo Alcantara <pc@manguebit.org>,
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 18:55:55 +0200 [thread overview]
Message-ID: <20250610165555.sekma4ybcl63flnw@pali> (raw)
In-Reply-To: <ac80cb46-5787-4fc9-a405-fd38a505c613@talpey.com>
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.
On Tuesday 10 June 2025 11:36:30 Tom Talpey wrote:
> The message text is pretty cryptic: "inode numbers won't match anymore".
> Can this be stated in a more actionable way? The primary consumer of
> the log is the sysadmin, after all.
>
> At a minimum, stating that hardlink detection won't work, as noted in
> the commit. Perhaps more helpfully, state that it's not a client issue.
>
> Tom.
>
> On 6/9/2025 3:36 AM, Pali Rohár wrote:
> > cifs_autodisable_serverino() is already printing at the VFS level
> > information that it is disabling the serverino. It is one time thing as
> > once it is disabled, it is not printing it second time. So it does not
> > flood logs.
> >
> > In this change I have just extended this existing logging to print also reason.
> >
> > On Sunday 08 June 2025 22:40:21 Steve French wrote:
> > > Since this could flood logs (e.g. in some DFS cases), probably better
> > > to do these via the usual dynamic trace points (and can document a
> > > simple "trace-cmd -e smb3_disable_serverino" script to avoid risk of
> > > flooding logs. cifsFYI is an alternative but the world has moved to
> > > the dynamic tracing (eBPF etc.)
> > >
> > > On Sun, Jun 8, 2025 at 3:57 PM Paulo Alcantara <pc@manguebit.org> wrote:
> > > >
> > > > Pali Rohár <pali@kernel.org> writes:
> > > >
> > > > > Before calling cifs_autodisable_serverino() function, show reason why it
> > > > > has to be called.
> > > > >
> > > > > This change allows to debug issues why cifs.ko decide to turn off server
> > > > > inode number support and hence disable support for detection of hardlinks.
> > > > >
> > > > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > > > > Cc: stable@vger.kernel.org
> > > > > ---
> > > > > fs/smb/client/connect.c | 2 ++
> > > > > fs/smb/client/dfs_cache.c | 2 ++
> > > > > fs/smb/client/inode.c | 3 +++
> > > > > fs/smb/client/readdir.c | 3 +++
> > > > > 4 files changed, 10 insertions(+)
> > > >
> > > > NACK.
> > > >
> > >
> > >
> > > --
> > > Thanks,
> > >
> > > Steve
> >
> >
>
next prev parent reply other threads:[~2025-06-10 16:55 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 [this message]
2025-06-10 17:10 ` Paulo Alcantara
2025-06-10 17:22 ` Pali Rohár
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=20250610165555.sekma4ybcl63flnw@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