From: Paulo Alcantara <pc@manguebit.org>
To: "Pali Rohár" <pali@kernel.org>, "Steve French" <sfrench@samba.org>
Cc: linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: Show reason why autodisabling serverino support
Date: Sun, 08 Jun 2025 17:57:32 -0300 [thread overview]
Message-ID: <3d644c3f8acb3dbcef395bd96e7e957c@manguebit.org> (raw)
In-Reply-To: <20250608164453.6699-1-pali@kernel.org>
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.
next prev parent reply other threads:[~2025-06-08 20:57 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 [this message]
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
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=3d644c3f8acb3dbcef395bd96e7e957c@manguebit.org \
--to=pc@manguebit.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.org \
--cc=sfrench@samba.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