Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@cjr.nz>
To: Enzo Matsumiya <ematsumiya@suse.de>
Cc: linux-cifs@vger.kernel.org, smfrench@gmail.com,
	ronniesahlberg@gmail.com, nspmangalore@gmail.com
Subject: Re: [PATCH 0/2] Introduce dns_interval procfs setting
Date: Thu, 09 Jun 2022 12:49:40 -0300	[thread overview]
Message-ID: <877d5px2ej.fsf@cjr.nz> (raw)
In-Reply-To: <20220609153046.pbb6pazfsnaweayv@cyberdelia>

Enzo Matsumiya <ematsumiya@suse.de> writes:

> Currently, key.dns_resolver uses getaddrinfo() to resolve names, which
> doesn't contain the TTL for the record, hence *always* returns 0 to cifs.ko.
> This patch is just a way to provide some flexibility to the user, in
> case they don't want to use the currently-always-fixed 600s.

It is not limited to key.dns_resolver.  The user is free to choose
whatever program he/she wants to be upcalled for dns_resolver key.

For instance, some distros might still be using cifs.upcall(8) that
actually set record TTL, thus making it impossible for the user to
change default via /proc/fs/cifs/dns_interval.

  reply	other threads:[~2022-06-09 15:49 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
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 [this message]
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=877d5px2ej.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox