| 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, 10 Feb 2010 19:30:40 -0800 (PST) From: Roland McGrath <roland@...hat.com> To: "H. Peter Anvin" <hpa@...or.com> Cc: Oleg Nesterov <oleg@...hat.com>, Suresh Siddha <suresh.b.siddha@...el.com>, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>, hjl.tools@...il.com Subject: Re: [patch v2 4/4] ptrace: Add support for generic PTRACE_GETREGSET/PTRACE_SETREGSET > Allowing a larger size for get seems very sane. Allowing a smaller size > would be ok iff we make sure we handle corner cases right (i.e. a > partially overwritten subregister.) It should enforce the static constraints of the user_regset, which include a starting position that's 0 % .align (if we had non-zero starting position in the request) and a size that's 0 % .size. The arch code sets those and then is not obliged to handle requests outside those constraints. It's already documented that the arch code is obliged to handle any partial regset access that meets them. The usual thing is to set .size and .align to the size of a register. This is exactly so that the arch code does not need to add gratuitous corner case complications such as "partially overwritten subregister". Thanks, Roland -- 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