| 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: <787b0d920609140901l46ce6cd3l400c33e74a67b8db@mail.gmail.com> Date: Thu, 14 Sep 2006 12:01:48 -0400 From: "Albert Cahalan" <acahalan@...il.com> To: "Andi Kleen" <ak@...e.de> Cc: linux-kernel@...r.kernel.org, "Andrew Morton" <akpm@...l.org>, "Linus Torvalds" <torvalds@...l.org>, hpa@...or.com Subject: Re: [PATCH] i386/x86_64 signal handler arg fixes On 9/14/06, Andi Kleen <ak@...e.de> wrote: > > > I guess that should be deleted then? > > Yes. I will delete it right now. Thanks for the notice. Er, OK. This means I can't patch it without conflict. Mind just adding the six lines of code needed for support of regparm(3) apps? > > Currently you remap signals. Whatever you do this for > > regparm(0) should also be done for regparm(3). > > Not sure I parse you here. You're asking how to fix the regparm(3) > case? No. I'd thought that the two cases should match. The regparm(3) case should remap signals if and only if the regparm(0) case remaps signals. Perhaps this is not correct if the remapping is not needed for native Linux apps; I doubt iBCS stuff would ever be needing regparm(3) support. Since you plan to delete the remapping cruft from the regparm(0) case, then obviously it should not be added to the regparm(3) case. - 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