lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 7 Mar 2007 16:03:36 -0500 From: "Lee Revell" <rlrevell@...-job.com> To: "linux-os (Dick Johnson)" <linux-os@...logic.com> Cc: "Luong Ngo" <luong.ngo@...il.com>, "Linux kernel" <linux-kernel@...r.kernel.org> Subject: Re: Sleeping thread not receive signal until it wakes up On 3/7/07, linux-os (Dick Johnson) <linux-os@...logic.com> wrote: > Interruptible_sleep_on is interruptible, but for your task to > actually be awakened and your alarm handler to get some CPU, > it needs to be scheduled. If the BKL (big kernel lock) is > held, it won't be scheduled until it is released. You can schedule while holding the BKL and it will be dropped and reacquired. Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists