Re: [PATCH 2/2] gssd: don't let parent exit until child has a chance to scan directory once

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Nov 18, 2013, at 11:38, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote:

> On Fri, Nov 15, 2013 at 02:15:31PM -0500, Jeff Layton wrote:
>> With some proposed kernel changes, it won't even attempt to upcall
>> sometimes if it doesn't appear that gssd is running. This means that
>> we have a theoretical race between gssd starting up at boot time and
>> the init process attempting to mount kerberized filesystems.
>> 
>> Fix this by switching gssd to use mydaemon() and having the child
>> only release the parent after it has processed the directory once.
> 
> Makes sense to me, thanks--ACK.

We now appear to have 2 more or less identical copies of mydaemon in nfs-utils (one in utils/gssd/svcgssd.c and one in utils/idmapd/idmapd.c). Time to make it a common library function?

--
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux