From: "J. Bruce Fields" <bfields@fieldses.org>
To: Phil Endecott
<phil_bnaqb_endecott-wZDNlLIRyE5g9hUCZPvPmw@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Make sm-notify faster if there are no servers to notify
Date: Wed, 29 Oct 2008 13:37:50 -0400 [thread overview]
Message-ID: <20081029173750.GD31936@fieldses.org> (raw)
In-Reply-To: <1225301403729-YnoLgZYwwYuCbKHnblo0pmrPP3OPMK55cpQHUIT47Ck@public.gmane.org>
On Wed, Oct 29, 2008 at 05:30:03PM +0000, Phil Endecott wrote:
> J. Bruce Fields wrote:
>> On Wed, Oct 29, 2008 at 12:13:20AM +0000, Phil Endecott wrote:
>>> Dear Experts,
>>>
>>> sm-notify was taking a long time while my laptop booted. This was
>>> odd because I use NFS only rarely - via autofs - on that machine, and
>>> sm-notify actually has no-one to notify most of the time. So I have
>>> patched it as follows. Is this a legitimate thing to do?
>>
>> It looks like your patch was committed to nfs-utils a couple weeks ago:
>> see c8d18e26d2a53d9036a32c2dafebccaf4ce1634d from
>>
>> git://linux-nfs.org/nfs-utils
>>
>> --b.
>
> How curious. I guess someone saw my Debian bug report. No mention of
> it on this list as far as I can see though.
>
> I presume from this that it is considered a safe thing to do.
It looks right to me. Hopefully somebody actually has tested this on a
client that holds locks when it reboots?
I remember this was one of the things Arjan mentioned having to disable
in his "5-second boot" talk at the Linux Plumbers Conference, so you're
not the only one to have noticed the problem....
--b.
next prev parent reply other threads:[~2008-10-29 17:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 0:13 Make sm-notify faster if there are no servers to notify Phil Endecott
[not found] ` <1225239200402-YnoLgZYwwYuCbKHnblo0pmrPP3OPMK55cpQHUIT47Ck@public.gmane.org>
2008-10-29 17:18 ` J. Bruce Fields
2008-10-29 17:30 ` Phil Endecott
[not found] ` <1225301403729-YnoLgZYwwYuCbKHnblo0pmrPP3OPMK55cpQHUIT47Ck@public.gmane.org>
2008-10-29 17:37 ` J. Bruce Fields [this message]
2008-10-29 17:45 ` Phil Endecott
[not found] ` <1225302305994-YnoLgZYwwYuCbKHnblo0pmrPP3OPMK55cpQHUIT47Ck@public.gmane.org>
2008-10-29 18:41 ` J. Bruce Fields
2008-10-29 20:30 ` Chuck Lever
2008-10-29 21:11 ` J. Bruce Fields
2008-11-09 19:25 ` J. Bruce Fields
2008-11-10 0:52 ` Chuck Lever
2008-11-10 0:55 ` J. Bruce Fields
2008-11-10 1:00 ` Chuck Lever
2008-11-10 9:40 ` Phil Endecott
2008-11-10 13:41 ` Steve Dickson
[not found] ` <49183A12.7010707-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-04 21:10 ` J. Bruce Fields
2008-12-05 3:34 ` Neil Brown
[not found] ` <18744.41310.635618.148281-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-12-05 3:58 ` J. Bruce Fields
2008-12-05 13:26 ` Steve Dickson
[not found] ` <49392C14.7000709-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-05 16:38 ` J. Bruce Fields
2008-12-05 17:29 ` J. Bruce Fields
2008-12-05 18:41 ` Chuck Lever
2008-12-06 2:42 ` J. Bruce Fields
2008-12-08 19:50 ` Chuck Lever
2008-12-11 22:44 ` J. Bruce Fields
2008-12-05 19:12 ` Steve Dickson
[not found] ` <49397D1B.3000701-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-06 2:49 ` J. Bruce Fields
2008-12-05 18:42 ` Steve Dickson
[not found] ` <4939760A.9050304-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-06 3:08 ` J. Bruce Fields
2008-10-31 17:52 ` 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=20081029173750.GD31936@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=phil_bnaqb_endecott-wZDNlLIRyE5g9hUCZPvPmw@public.gmane.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