Re: possible fix for: PR# 39420 - stopped processes can hold locks

[christos%astron.com@localhost (Christos Zoulas)]

In article <20090817213523.1102263B100%mail.netbsd.org@localhost>,
Mindaugas Rasiukevicius  <rmind%netbsd.org@localhost> wrote:
>christos%zoulas.com@localhost (Christos Zoulas) wrote:
>> The following patch adds an optional sigset to the list of signals
>> that we are not allowed to catch when waiting with PCATCH, and a
>> flag 'PNOSTOP' that uses this feature. This is so that NFS
>> interruptible mounts don't get stuck when people suspend their
>> processes while the NFS client code is holding locks. This is a
>> stopgap measure and is written in a way to minimize diffs.
>> 
>> Opinions?
>
>Well, it's a hack. :) I do not think we should apply it to condvar(9).
>Solution suggested by <yamt> in the PR would be better.

Suspending processes only on user-kernel boundaries? Well, the patch achieves
that. How else would you implement it?

christos