linux-kernel - Re: [PATCH v2] all arches, signal: Move restart_block to struct task

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20141203155352.ea5322ff45c6200238c7ef51@linux-foundation.org>
Date:	Wed, 3 Dec 2014 15:53:52 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Richard Weinberger <richard@....at>,
	David Miller <davem@...emloft.net>,
	Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-arch <linux-arch@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	richard -rw- weinberger <richard.weinberger@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>,
	Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH v2] all arches, signal: Move restart_block to struct
 task_struct

On Wed, 3 Dec 2014 15:38:29 -0800 Andy Lutomirski <luto@...capital.net> wrote:

> Yes, exactly.
> 
> >
> > Spelling this out in the changelog would be useful for the ignorant and
> > the forgetful ;)
> 
> Want a new version, or will you fix it up yourself?
> 

I think I can work that out.

A couple of linux-next things to check:

- arch/arm/include/asm/thread_info.h:arm_restart_block has
  disappeared from the thread_info.

- the reference to ti->restart_block in arch/arm/kernel/traps.c has
  vanished.  I couldn't find anywhere where it was moved to.
--
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/