From: David Howells <dhowells@redhat.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: dhowells@redhat.com, jmorris@namei.org,
linux-security-module@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH [try #4] 8/9] KEYS: Extend TIF_NOTIFY_RESUME to (almost) all architectures
Date: Tue, 01 Sep 2009 18:26:04 +0100 [thread overview]
Message-ID: <14644.1251825964@redhat.com> (raw)
In-Reply-To: <20090901171649.GA16779@flint.arm.linux.org.uk>
Russell King <rmk@arm.linux.org.uk> wrote:
> > @@ -707,4 +707,9 @@ do_notify_resume(struct pt_regs *regs, unsigned int thread_flags, int syscall)
> > {
> > if (thread_flags & _TIF_SIGPENDING)
> > do_signal(¤t->blocked, regs, syscall);
> > +
> > + if (thread_info_flags & _TIF_NOTIFY_RESUME) {
>
> Shouldn't this be thread_flags ?
Yes, thanks. Fixed.
David
next prev parent reply other threads:[~2009-09-01 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090901163231.14180.43426.stgit@warthog.procyon.org.uk>
2009-09-01 16:33 ` [PATCH [try #4] 8/9] KEYS: Extend TIF_NOTIFY_RESUME to (almost) all architectures David Howells
2009-09-01 17:16 ` Russell King
2009-09-01 17:16 ` Russell King
2009-09-01 17:26 ` David Howells [this message]
2009-09-01 17:26 ` David Howells
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=14644.1251825964@redhat.com \
--to=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox