From: Boaz Harrosh <bharrosh@panasas.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: NFS list <linux-nfs@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>,
"Bhamare, Sachin" <sbhamare@panasas.com>,
Benny Halevy <bhalevy@tonian.com>,
Steve Dickson <steved@redhat.com>,
"Welch, Brent" <welch@panasas.com>
Subject: Re: [PATCH 3/4] pnfs-obj: autologin: Add support for protocol autologin
Date: Mon, 19 Mar 2012 13:58:23 -0700 [thread overview]
Message-ID: <4F679DEF.3040002@panasas.com> (raw)
In-Reply-To: <1331934052.13255.7.camel@lade.trondhjem.org>
On 03/16/2012 02:40 PM, Myklebust, Trond wrote:
> On Thu, 2012-03-15 at 23:23 -0700, Boaz Harrosh wrote:
>> From: Sachin Bhamare <sbhamare@panasas.com>
>>
>> The pnfs-objects protocol mandates that we autologin into devices not
>> present in the system, according to information specified in the
>> get_device_info returned from the server.
>>
>> The Protocol specifies two login hints.
>> 1. An IP address:port combination
>> 2. A string URI which is constructed as a URL with a protocol prefix
>> followed by :// and a string as address. For each protocol prefix
>> the string-address format might be different.
>>
>> We only support the second option. The first option is just redundant
>> to the second one.
>> NOTE: The Kernel part of autologin does not parse the URI string. It
>> just channels it to a user-mode script. So any new login protocols should
>> only update the user-mode script which is a part of the nfs-utils package,
>> but the Kernel need not change.
>>
>> We implement the autologin by using the call_usermodehelper() API.
>> (Thanks to Steve Dickson <steved@redhat.com> for pointing it out)
>> So there is no running daemon needed, and or special setup.
>>
>> All is needed is that "/sbin/osd_login" script exists.
>> TODO:
>> "osd_login" is an hard coded name. If not present we will rate_limit
>> print to dmsg and keep failing. In such cases we should stop trying
>> and provide sysfs interface for re-enabling autologin. For example,
>> we could ZERO out the script name and let user-mode set a new script
>> name.
>> [Q] Where in sysfs should a layout-driver put its things?
>
> Please see fs/nfs/cache_lib.c, which already does this sort of thing.
> The right thing to do is not sysfs, but a kernel module parameter.
>
I have a question about the "kernel module parameter" is that an hot
affair. I mean if the module is loaded, does it have to be unloaded
before I can specify a new "module parameter" on load. Or it will
update globally even if the module is already loaded?
The reason I'm asking is because the layout-driver is referenced
by nfs-core on mount. And will not release until unmount, of the
last pnf-objects mount-point.
That's why I thought of a /sys so all mount-points need not be unmounted
before admin can fix the problem.
>
Thanks
Boaz
next prev parent reply other threads:[~2012-03-19 20:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 6:17 [PATCHSET 0/4] Auto-login support for the pnfs-objects protocol Boaz Harrosh
2012-03-16 6:19 ` [PATCH 1/4] pnfsd-exofs: Add autologin support to exofs Boaz Harrosh
2012-03-16 6:30 ` Boaz Harrosh
2012-03-16 6:21 ` [PATCH 2/4] pnfs-obj: Remove unused variable from objlayout_get_deviceinfo() Boaz Harrosh
2012-03-16 6:23 ` [PATCH 3/4] pnfs-obj: autologin: Add support for protocol autologin Boaz Harrosh
2012-03-16 21:40 ` Myklebust, Trond
2012-03-19 20:58 ` Boaz Harrosh [this message]
2012-03-19 21:12 ` Myklebust, Trond
2012-03-19 23:23 ` Boaz Harrosh
2012-03-20 1:16 ` Boaz Harrosh
2012-03-20 3:10 ` Boaz Harrosh
2012-03-20 3:26 ` Boaz Harrosh
2012-03-20 3:47 ` [PATCH version2] " Boaz Harrosh
2012-03-16 6:27 ` [PATCH 4/4] osd_login: Add autologin script for objlayoutdriver Boaz Harrosh
2012-03-23 2:36 ` SQUASHME: " Boaz Harrosh
2012-03-23 2:57 ` [PATCH version2] " Boaz Harrosh
2012-05-01 18:50 ` [PATCH 4/4] " Steve Dickson
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=4F679DEF.3040002@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bhalevy@tonian.com \
--cc=linux-nfs@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=sbhamare@panasas.com \
--cc=steved@redhat.com \
--cc=welch@panasas.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;
as well as URLs for NNTP newsgroup(s).