From: Al Viro <viro@ZenIV.linux.org.uk>
To: Steve French <smfrench@gmail.com>
Cc: Adrian Bunk <bunk@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"Q (Igor Mammedov)" <qwerty0987654321@mail.ru>
Subject: Re: Fw: [2.6 patch] make cifs_dfs_automount_list static
Date: Wed, 16 Apr 2008 05:08:19 +0100 [thread overview]
Message-ID: <20080416040818.GB27459@ZenIV.linux.org.uk> (raw)
In-Reply-To: <524f69650804152058v4b12cfc2xc3c60d42c3e64b32@mail.gmail.com>
On Tue, Apr 15, 2008 at 10:58:06PM -0500, Steve French wrote:
> Merged into cifs-2.6.git tree
>
> > Adrian Bunk <bunk@kernel.org>
> > 04/14/2008 01:13 PM
> >
> > To
> > Igor Mammedov <niallain@gmail.com>, Steven French/Austin/IBM@IBMUS
> > cc
> > linux-cifs-client@lists.samba.org, linux-kernel@vger.kernel.org
> > Subject
> > [2.6 patch] make cifs_dfs_automount_list static
> >
> >
> > This patch makes the needlessly global cifs_dfs_automount_list static.
This only hides the real problem, namely that logics in the user of said
list is FUBAR.
What kind of eviction policy does cifs want? "Try to kick all such
mounts out whenever somebody does umount(2) on any mounted cifs instance"?
That's bloody odd, to put it mildly... "Don't kick them out until
somebody tries to umount cifs instance they are mounted on"? That's
done automatically from VFS these days (and should've been done that
way as soon as that kind of automounts had been introduced). "Done
frequently enough"? Then you want timer, like e.g. NFS does...
prev parent reply other threads:[~2008-04-16 4:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF56FD7422.17D776A1-ON8725742B.006981FF-8625742B.00699B35@us.ibm.com>
2008-04-16 3:58 ` Fw: [2.6 patch] make cifs_dfs_automount_list static Steve French
2008-04-16 4:08 ` Al Viro [this message]
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=20080416040818.GB27459@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qwerty0987654321@mail.ru \
--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