From: "Philip Ong Jr." <pongjr@gmail.com>
To: Leonardo Chiquitto <leonardo.lists@gmail.com>
Cc: autofs@linux.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: [PATCH 0/2] Series for the non-expiring mounts problem
Date: Thu, 28 Apr 2011 19:52:03 -0700 [thread overview]
Message-ID: <4DBA27D3.5030503@gmail.com> (raw)
In-Reply-To: <AANLkTimKbS8A6OW-B-BGiAccAh_71YO8CF92zP0K9TE2@mail.gmail.com>
Have the patches been released yet?
On 3/30/2011 9:13 AM, Leonardo Chiquitto wrote:
> On Wed, Mar 30, 2011 at 2:49 AM, Ian Kent<raven@themaw.net> wrote:
>> These two patches should fix the problem you reported where a USR1
>> signal fails to trigger an expire. They should also fix the unnecessary
>> map reload problem.
>>
>> Please test these for me.
> Ian, thanks for the patches. I just tested them here and confirm that the
> problem is resolved. I tested direct and indirect mounts letting them expire
> after the default timeout and forcing the expiration with SIGUSR1.
>
> I also confirmed that the "unmountable directories" problem reported in
> http://linux.kernel.org/pipermail/autofs/2011-March/006509.html is fixed
> as well (the patch I suggested back then is *not* needed).
>
> Thanks,
> Leonardo
>
>> ---
>>
>> Ian Kent (2):
>> autofs-5.0.5 - fix stale map read
>> autofs-5.0.5 - fix next task list update
>>
>>
>> CHANGELOG | 2 ++
>> daemon/lookup.c | 1 +
>> daemon/state.c | 9 +++++----
>> include/master.h | 1 +
>> lib/master.c | 37 +++++++++++++++++++++++++------------
>> 5 files changed, 34 insertions(+), 16 deletions(-)
>>
>> --
>> Ian
prev parent reply other threads:[~2011-04-29 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 5:49 [PATCH 0/2] Series for the non-expiring mounts problem Ian Kent
2011-03-30 5:49 ` [PATCH 1/2] autofs-5.0.5 - fix next task list update Ian Kent
2011-03-30 5:49 ` [PATCH 2/2] autofs-5.0.5 - fix stale map read Ian Kent
2011-03-30 16:13 ` [PATCH 0/2] Series for the non-expiring mounts problem Leonardo Chiquitto
2011-04-29 2:52 ` Philip Ong Jr. [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=4DBA27D3.5030503@gmail.com \
--to=pongjr@gmail.com \
--cc=autofs@linux.kernel.org \
--cc=leonardo.lists@gmail.com \
--cc=raven@themaw.net \
/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).