From: Maria Alexeeva <alxvmr@altlinux.org>
To: Steve French <smfrench@gmail.com>
Cc: pc@manguebit.com, linux-cifs@vger.kernel.org,
Ivan Volchenko <ivolchenko86@gmail.com>,
samba-technical@lists.samba.org, Tom Talpey <tom@talpey.com>,
Vitaly Chikunov <vt@altlinux.org>
Subject: Re: [PATCH] fs/smb/client/fs_context: Add hostname option for CIFS module to work with domain-based dfs resources with Kerberos authentication
Date: Mon, 8 Sep 2025 17:24:31 +0400 [thread overview]
Message-ID: <bb31a447-3092-4902-ba38-e5e16f1986dd@altlinux.org> (raw)
In-Reply-To: <CAH2r5mvDa8E8NKNHevoWYARY_52DJ+WQX3oetYw-pwysMyAKYQ@mail.gmail.com>
Good day!
Could you please let me know if you have managed to find the messages
with comments/feedback? This is important for us to make the
corresponding changes to the proposed patches.
On 7/31/25 18:00, Steve French via samba-technical wrote:
> I don't have any strong opinion on: "dfs_server_hostname" vs
> "dfs_domain_hostname" whichever makes more sense.
>
> I will look to see if I can find any more threads on this in earlier email
>
> On Wed, Jul 30, 2025 at 11:54 AM Maria Alexeeva <alxvmr@altlinux.org> wrote:
>>
>> Steve,
>> It seems some of the discussion with review comments fell outside this
>> thread (I can only find vt@altlinux.org Vitaly Chikunov's remarks).
>> Could you please point me to where the rest of the feedback can be
>> found (e.g., about fixing the noisy warning the patch adds and
>> other comments)?
>>
>> An updated patch for fs/smb/client/fs_context has been prepared, renaming
>> the option to dfs_domain_hostname. There's suggestion to further rename
>> it to dfs_server_hostname - what are your thoughts on this?
>>
>> The patches will follow in subsequent messages.
>>
>> Thanks!
>>
>> On 7/25/25 02:50, Steve French via samba-technical wrote:
>>> Maria,
>>> Since this looks like it depends on a cifs-utils change, can you
>>> update your kernel patch with review comments (e.g. changing mount
>>> parm to "dfs_domain_hostname", and there were at least two others in
>>> the thread, e.g. fixing the noisy warning that the patch adds) and
>>> then show the cifs-utils change, so we can make the upcoming merge
>>> window.
>>>
>>> On Thu, Jul 24, 2025 at 5:14 PM Steve French <smfrench@gmail.com> wrote:
>>>>
>>>> I will update the mount parm name, similar to what Tom suggested to
>>>> "dfs_domain_hostname" to be less confusing.
>>>>
>>>> Let me know if you had a v2 of the patch with other changes
next prev parent reply other threads:[~2025-09-08 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 15:22 [PATCH] fs/smb/client/fs_context: Add hostname option for CIFS module to work with domain-based dfs resources with Kerberos authentication Maria Alexeeva
2025-06-14 3:42 ` Vitaly Chikunov
2025-07-03 12:59 ` Maria Alexeeva
2025-07-24 22:14 ` Steve French
2025-07-24 22:50 ` Steve French
2025-07-30 16:54 ` Maria Alexeeva
2025-07-30 17:03 ` [PATCH v2] fs/smb/client/fs_context: Add dfs_domain_hostname " Maria Alexeeva
2025-07-30 17:09 ` [PATCH] mount.cifs: add support for domain-based DFS targets with Kerberos via hostname resolution Maria Alexeeva
2025-07-31 14:00 ` [PATCH] fs/smb/client/fs_context: Add hostname option for CIFS module to work with domain-based dfs resources with Kerberos authentication Steve French
2025-09-08 13:24 ` Maria Alexeeva [this message]
2025-12-30 16:47 ` [PATCH v3 0/1] Add hostname option for CIFS module Maria Alexeeva
2025-12-30 16:47 ` [PATCH v3 1/1] fs/smb/client/fs_context: Add hostname option for CIFS module to work with domain-based dfs resources with Kerberos authentication Maria Alexeeva
2026-02-23 18:02 ` Steve French
2026-02-27 18:46 ` Paulo Alcantara
[not found] ` <CAG5KTOZ6s4AjE0e66D9CMnZTP68YHzUb6p9nQKgeZeBV9ZVVBw@mail.gmail.com>
2026-02-27 21:07 ` Paulo Alcantara
2025-12-30 16:50 ` [PATCH v2] mount.cifs: add support for domain-based DFS targets with Kerberos via hostname resolution Maria Alexeeva
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=bb31a447-3092-4902-ba38-e5e16f1986dd@altlinux.org \
--to=alxvmr@altlinux.org \
--cc=ivolchenko86@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.com \
--cc=vt@altlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.