Date: Mon, 14 Mar 2011 11:03:18 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Ravi Murty <ravi.murty@gmail.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Erich Dollansky <erich@alogreentechnologies.com> Subject: Re: SIGSTOP and SIGKILL Message-ID: <20110314090318.GG78089@deviant.kiev.zoral.com.ua> In-Reply-To: <BD0E19B5-6195-420D-B353-B639818890E7@gmail.com> References: <AANLkTi=70WWQLz7iT413tGXq_dhp_jBX7hu0qHWT=ar6@mail.gmail.com> <201103141230.49277.erich@alogreentechnologies.com> <BD0E19B5-6195-420D-B353-B639818890E7@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--vBwLacbGVLp/4r+w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 13, 2011 at 11:30:00PM -0700, Ravi Murty wrote: > I haven't, are there specific improvements in this area of the kernel? First, the 8.2, compared to 8.0, changed the mechanism of delivering the process-global signal to a thread. Now, the thread to deliver is selected at the moment of delivery, instead of the moment of post. This was done to close a race where either thread changed signal mask after post, or exited after post, causing signal be undefinitely delayed or ignored, respectively. Second, 8.2 less often stops the threads in the sleep state, more often trying to move the thread to safer user<->kernel boundary, to take a stop. Sleeping thread might indicate the unsafe sleep (from the POV of stopping) by using PBDRY flag to msleep. Both the changes are not directly address the behaviour you described, but they are explicitely in the area of your interest. BTW, it is not clear to me, does the process in the state as you described, able to unwind from the stop state using SIGCONT ? I.e., is it 'weird but recoverable' state, or is it 'weird and unrecoverable' state ? >=20 > On Mar 13, 2011, at 10:30 PM, Erich Dollansky <erich@alogreentechnologies= .com> wrote: >=20 > > Hi, > >=20 > > On Monday 14 March 2011 11:41:21 Ravi Murty wrote: > >=20 > >>=20 > >> Any good solutions to this problem? > >=20 > > did you try your program on 8.2? > >=20 > > Erich > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" --vBwLacbGVLp/4r+w Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk192dUACgkQC3+MBN1Mb4h1VwCgxwjjrxGe5lW+RWej+OIAbYc7 oxsAn2kiD6Wj3ldTS/DJvfZDS/rJ0Cxo =6l8B -----END PGP SIGNATURE----- --vBwLacbGVLp/4r+w--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110314090318.GG78089>