From: Paulo Alcantara <pc@cjr.nz>
To: Enzo Matsumiya <ematsumiya@suse.de>, linux-cifs@vger.kernel.org
Cc: smfrench@gmail.com, ronniesahlberg@gmail.com,
nspmangalore@gmail.com, Enzo Matsumiya <ematsumiya@suse.de>
Subject: Re: [PATCH 0/2] Introduce dns_interval procfs setting
Date: Thu, 09 Jun 2022 11:53:13 -0300 [thread overview]
Message-ID: <87czfhx50m.fsf@cjr.nz> (raw)
In-Reply-To: <20220608215444.1216-1-ematsumiya@suse.de>
Hi Enzo,
Enzo Matsumiya <ematsumiya@suse.de> writes:
> These 2 patches are a simple way to fix the DNS issue that
> currently exists in cifs, where the upcall to key.dns_resolver will
> always return 0 for the record TTL, hence, making the resolve worker
> always use the default value SMB_DNS_RESOLVE_INTERVAL_DEFAULT
> (currently 600 seconds).
>
> This also makes the new setting `dns_interval' user-configurable via
> procfs (/proc/fs/cifs/dns_interval).
How is the user supposed to know which TTL value will be used? If the
expire time is set by either key.dns_resolver or any other program used
for dns_resolver key, the above setting would no longer work and users
might get confused.
next prev parent reply other threads:[~2022-06-09 14:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 21:54 [PATCH 0/2] Introduce dns_interval procfs setting Enzo Matsumiya
2022-06-08 21:54 ` [PATCH 1/2] cifs: create procfs for dns_interval setting Enzo Matsumiya
2022-06-08 21:54 ` [PATCH 2/2] cifs: reschedule DNS resolve worker based on dns_interval Enzo Matsumiya
2022-06-09 0:39 ` [PATCH 0/2] Introduce dns_interval procfs setting ronnie sahlberg
2022-06-09 14:17 ` Tom Talpey
2022-06-09 15:03 ` Enzo Matsumiya
2022-06-09 15:24 ` Tom Talpey
2022-06-09 16:17 ` Enzo Matsumiya
2022-06-09 14:53 ` Paulo Alcantara [this message]
2022-06-09 15:14 ` Enzo Matsumiya
2022-06-09 15:21 ` Paulo Alcantara
2022-06-09 15:30 ` Enzo Matsumiya
2022-06-09 15:49 ` Paulo Alcantara
2022-06-09 16:16 ` Enzo Matsumiya
2022-06-09 16:42 ` 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=87czfhx50m.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=ematsumiya@suse.de \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.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 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.