| 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
| ||
|
Message-ID: <2fa748260901132321k6f24f567u65691f653e2ec62b@mail.gmail.com> Date: Tue, 13 Jan 2009 23:21:39 -0800 From: anarcherty <anarcherty@...il.com> To: linux-kernel@...r.kernel.org Subject: lock_page_killable limitations? What's preventing lock_page_killable from replacing lock_page? Is there more on the table than implementing the small amount of at each callsite of lock_page to handle the return condition -- ie, restrictions that prevent the kernel from being able to fail at successfully requiring and releasing a lock? -- 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