All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: jmorris@namei.org, linux-security-module@vger.kernel.org,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH 8/9] KEYS: Extend TIF_NOTIFY_RESUME to (almost) all architectures [try #5]
Date: Wed, 2 Sep 2009 09:05:43 +0100	[thread overview]
Message-ID: <20090902080542.GA29221@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20090902072129.3578.81364.stgit@warthog.procyon.org.uk>

On Wed, Sep 02, 2009 at 08:21:29AM +0100, David Howells wrote:
> diff --git a/arch/arm/kernel/signal.c b/arch/arm/kernel/signal.c
> index f6bc5d4..6759f45 100644
> --- a/arch/arm/kernel/signal.c
> +++ b/arch/arm/kernel/signal.c
> @@ -707,4 +707,9 @@ do_notify_resume(struct pt_regs *regs, unsigned int thread_flags, int syscall)
>  {
>  	if (thread_flags & _TIF_SIGPENDING)
>  		do_signal(&current->blocked, regs, syscall);
> +
> +	if (thread_info_flags & _TIF_NOTIFY_RESUME) {

This still has the same error - is this just a repost of the previous
patch?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2009-09-02  8:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090902072053.3578.69125.stgit@warthog.procyon.org.uk>
2009-09-02  7:21 ` [PATCH 8/9] KEYS: Extend TIF_NOTIFY_RESUME to (almost) all architectures [try #5] David Howells
2009-09-02  8:05   ` Russell King [this message]
2009-09-02  8:13     ` David Howells
2009-09-03  1:57   ` Kyle McMartin
2009-09-04  7:05     ` David Howells
2009-09-04 14:24       ` Kyle McMartin
2009-09-04 14:35         ` David Howells
2009-09-08 14:15           ` Kyle McMartin
2009-09-14 13:48             ` Kyle McMartin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090902080542.GA29221@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.