From: Ian Kent <raven@themaw.net>
To: Leonardo Chiquitto <leonardo.lists@gmail.com>
Cc: autofs@linux.kernel.org, "Philip Ong Jr." <pongjr@gmail.com>
Subject: [PATCH 0/2] Series for the non-expiring mounts problem
Date: Wed, 30 Mar 2011 13:49:23 +0800 [thread overview]
Message-ID: <20110330054620.22333.45008.stgit@localhost6.localdomain6> (raw)
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 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
next reply other threads:[~2011-03-30 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 5:49 Ian Kent [this message]
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.
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=20110330054620.22333.45008.stgit@localhost6.localdomain6 \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=leonardo.lists@gmail.com \
--cc=pongjr@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;
as well as URLs for NNTP newsgroup(s).