Re: [ 12/48] signal: always clear sa_restorer on execve

2013-03-20 Thread Ben Hutchings
On Wed, 2013-03-20 at 21:43 +0100, Sebastian Gottschall (DD-WRT) wrote: > Am 20.03.2013 20:02, schrieb Sebastian Gottschall (DD-WRT): > > Hello > > > > The patch for sa_restorer will break mips builds, since sa_restorer > > isnt defined as field within the struct, but the MACRO is. > > so use the

Re: [ 12/48] signal: always clear sa_restorer on execve

2013-03-20 Thread Sebastian Gottschall (DD-WRT)
Am 20.03.2013 20:02, schrieb Sebastian Gottschall (DD-WRT): Hello The patch for sa_restorer will break mips builds, since sa_restorer isnt defined as field within the struct, but the MACRO is. so use the __ARCH_HAS_SA_RESTORER way which is implemented in that way in linux 3.9 or simply revert

Re: [ 12/48] signal: always clear sa_restorer on execve

2013-03-20 Thread Sebastian Gottschall (DD-WRT)
Am 20.03.2013 20:02, schrieb Sebastian Gottschall (DD-WRT): Hello The patch for sa_restorer will break mips builds, since sa_restorer isnt defined as field within the struct, but the MACRO is. so use the __ARCH_HAS_SA_RESTORER way which is implemented in that way in linux 3.9 or simply revert

Re: [ 12/48] signal: always clear sa_restorer on execve

2013-03-20 Thread Ben Hutchings
On Wed, 2013-03-20 at 21:43 +0100, Sebastian Gottschall (DD-WRT) wrote: Am 20.03.2013 20:02, schrieb Sebastian Gottschall (DD-WRT): Hello The patch for sa_restorer will break mips builds, since sa_restorer isnt defined as field within the struct, but the MACRO is. so use the

[ 12/48] signal: always clear sa_restorer on execve

2013-03-18 Thread Greg Kroah-Hartman
3.4-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 2ca39528c01a933f6689cd6505ce65bd6d68a530 upstream. When the new signal handlers are set up, the location of sa_restorer is not cleared, leaking a parent process's address

[ 12/48] signal: always clear sa_restorer on execve

2013-03-18 Thread Greg Kroah-Hartman
3.4-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook keesc...@chromium.org commit 2ca39528c01a933f6689cd6505ce65bd6d68a530 upstream. When the new signal handlers are set up, the location of sa_restorer is not cleared, leaking a parent