| 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 09:42:37 -0800 (PST) From: Davide Libenzi <davidel@...ilserver.org> To: Stephen Rothwell <sfr@...b.auug.org.au> cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [patch 1/4] signalfd v1 - signalfd core ... On Wed, 7 Mar 2007, Stephen Rothwell wrote: > Then, of course, you have to think about how to get the siginfo_t out to > the user process. Do you just return it from the read after the read > that returns the signal number? If so, you need to know if the process > did a compat read syscall read or a normal one ... It can be a read(2) of a structure that does not need compat. It must be that way, because compat-on-read are out of question. - Davide - 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