[lkml]   [2004]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.6-rc3-mm1
==> Regarding Re: 2.6.6-rc3-mm1; adds:

raven> The case where two process similtaneously trigger a mount in autofs4
raven> can cause multiple requests to the daemon for the same mount. The
raven> daemon handles this OK but it's possible an incorrect error to be
raven> returned. For this reason I believe it is better to change the spin
raven> lock to a semaphore in waitq.c. This makes the second and subsequent
raven> request wait on the q as ther supposed to.

This looks good to me. Do you also need to take the semaphore in
autofs4_catatonic_mode(), around the hijacking of the queue?

void autofs4_catatonic_mode(struct autofs_sb_info *sbi)
struct autofs_wait_queue *wq, *nwq;

DPRINTK(("autofs: entering catatonic mode\n"));

sbi->catatonic = 1;
wq = sbi->queues;
sbi->queues = NULL; /* Erase all wait queues */

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:02    [W:0.181 / U:0.856 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site