From: Paulo Alcantara <pc@manguebit.com>
To: Eduard Bachmakov <e.bachmakov@gmail.com>
Cc: linux-cifs@vger.kernel.org
Subject: Re: Unexpected additional umh-based DNS lookup in 6.6.0
Date: Thu, 09 Nov 2023 14:29:18 -0300 [thread overview]
Message-ID: <482ee449a063acf441b943346b85e2d0.pc@manguebit.com> (raw)
In-Reply-To: <CADCRUiNSk7b7jVQrYoD153UmaBdFzpcA1q3DvfwJcNC6Q=gy0w@mail.gmail.com>
Eduard Bachmakov <e.bachmakov@gmail.com> writes:
> I don't see is_dfs_mount() being called so in my scenario we're simply
> relying on kzalloc initializing dfs_automount to false.
It's expected. If your share is DFS and client finds a DFS link or
reparse mount point, the dentry set for automount will get mounted with
new fs context where where @dfs_automount will be set.
next prev parent reply other threads:[~2023-11-09 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 21:23 Unexpected additional umh-based DNS lookup in 6.6.0 Eduard Bachmakov
2023-11-09 3:43 ` Paulo Alcantara
2023-11-09 9:55 ` Eduard Bachmakov
2023-11-09 17:29 ` Paulo Alcantara [this message]
2023-11-14 21:59 ` Eduard Bachmakov
2023-11-14 22:06 ` Steve French
2023-11-24 1:56 ` Paulo Alcantara
2023-11-24 11:53 ` Greg KH
2023-11-09 15:01 ` [PATCH] smb: client: fix mount when dns_resolver key is not available 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=482ee449a063acf441b943346b85e2d0.pc@manguebit.com \
--to=pc@manguebit.com \
--cc=e.bachmakov@gmail.com \
--cc=linux-cifs@vger.kernel.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