From: Anders Blomdell <anders.blomdell@control.lth.se>
To: autofs@linux.kernel.org
Subject: Minor change to alarm_handler to avoid code duplication
Date: Thu, 07 Jun 2007 15:49:35 +0200 [thread overview]
Message-ID: <46680CEF.2080803@control.lth.se> (raw)
[-- Attachment #1: Type: text/plain, Size: 147 bytes --]
As per request from discussions in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241780
a patch against git.
Best regards
Anders Blomdell
[-- Attachment #2: alarm_handler.patch --]
[-- Type: text/plain, Size: 3421 bytes --]
--- autofs/lib/alarm.c 2007-06-07 15:05:03.000000000 +0200
+++ /usr/src/autofs/autofs.patched/lib/alarm.c 2007-06-07 15:08:29.000000000 +0200
@@ -28,16 +28,16 @@
#define alarm_lock() \
do { \
- int _alm_lock = pthread_mutex_lock(&mutex); \
- if (_alm_lock) \
- fatal(_alm_lock); \
+ int status = pthread_mutex_lock(&mutex); \
+ if (status) \
+ fatal(status); \
} while (0)
#define alarm_unlock() \
do { \
- int _alm_unlock = pthread_mutex_unlock(&mutex); \
- if (_alm_unlock) \
- fatal(_alm_unlock); \
+ int status = pthread_mutex_unlock(&mutex); \
+ if (status) \
+ fatal(status); \
} while (0)
void dump_alarms(void)
@@ -168,87 +168,65 @@
static void *alarm_handler(void *arg)
{
struct list_head *head;
- struct timespec expire;
- time_t now;
int status;
-
+
alarm_lock();
head = &alarms;
while (1) {
- struct alarm *current;
-
- /*
- * If the alarm list is empty, wait until an alarm is
- * added.
- */
- while (list_empty(head)) {
+ if (list_empty(head)) {
+ /* No alarms, wait for one to be added */
status = pthread_cond_wait(&cond, &mutex);
if (status)
fatal(status);
- }
-
- current = list_entry(head->next, struct alarm, list);
-
- now = time(NULL);
-
- if (current->time <= now) {
- struct autofs_point *ap;
-
- list_del(¤t->list);
-
- if (current->cancel) {
- free(current);
- continue;
- }
-
- ap = current->ap;
- free(current);
- alarm_unlock();
-
- state_mutex_lock(ap);
- nextstate(ap->state_pipe[1], ST_EXPIRE);
- state_mutex_unlock(ap);
-
- alarm_lock();
- continue;
- }
-
- expire.tv_sec = current->time;
- expire.tv_nsec = 0;
-
- while (1) {
- struct autofs_point *ap;
- struct alarm *next;
-
- status = pthread_cond_timedwait(&cond, &mutex, &expire);
- if (status && status != ETIMEDOUT)
- fatal(status);
-
- next = list_entry(head->next, struct alarm, list);
- if (next->cancel) {
- list_del(&next->list);
- free(next);
- break;
+ } else {
+ struct alarm *first;
+ time_t now;
+
+ first = list_entry(head->next, struct alarm, list);
+
+ now = time(NULL);
+
+ if (first->time > now) {
+ /* Wait for alarm to trigger or a new alarm
+ to be added */
+ struct timespec expire;
+
+ expire.tv_sec = first->time;
+ expire.tv_nsec = 0;
+
+ status = pthread_cond_timedwait(&cond, &mutex,
+ &expire);
+ if (status && status != ETIMEDOUT)
+ fatal(status);
+ } else {
+ /* First alarm has triggered, run it */
+ struct autofs_point *ap;
+
+ list_del(&first->list);
+ ap = first->ap;
+ if (!first->cancel) {
+ /* We need to unlock the alarm list
+ in case some other thread holds
+ the state_mutex_lock(ap), and is
+ currently trying to do some
+ alarm_* function (i.e if we don't
+ unlock, we might deadlock) */
+ alarm_unlock();
+
+ state_mutex_lock(ap);
+ nextstate(ap->state_pipe[1],
+ ST_EXPIRE);
+ state_mutex_unlock(ap);
+
+ alarm_lock();
+ }
+ free(first);
}
-
- if (next != current)
- break;
-
- list_del(¤t->list);
- ap = current->ap;
- free(current);
- alarm_unlock();
-
- state_mutex_lock(ap);
- nextstate(ap->state_pipe[1], ST_EXPIRE);
- state_mutex_unlock(ap);
-
- alarm_lock();
- break;
}
}
+ /* Will never come here, so alarm_unlock is not necessary */
}
int alarm_start_handler(void)
[-- Attachment #3: Type: text/plain, Size: 140 bytes --]
_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
next reply other threads:[~2007-06-07 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 13:49 Anders Blomdell [this message]
2007-06-11 4:52 ` Minor change to alarm_handler to avoid code duplication Ian Kent
2007-06-11 5:06 ` Ian Kent
2007-06-13 4:13 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2007-06-08 7:19 Anders Blomdell
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=46680CEF.2080803@control.lth.se \
--to=anders.blomdell@control.lth.se \
--cc=autofs@linux.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.