From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] signal.git pile 2 (of 3, probably)
Date: Fri, 1 Jun 2012 00:57:48 +0100 [thread overview]
Message-ID: <20120531235748.GE30000@ZenIV.linux.org.uk> (raw)
That one is just task_work_add() series + remaining prereqs for it.
There probably will be another pull request from that tree this
cycle - at least for helpers, to get them out of the way for per-arch
fixes remaining in the tree. Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal for-linus
Shortlog:
Al Viro (4):
TIF_NOTIFY_RESUME is defined on all targets now
move key_repace_session_keyring() into tracehook_notify_resume()
parisc: need to check NOTIFY_RESUME when exiting from syscall
avr32: missed _TIF_NOTIFY_RESUME on one of do_notify_resume callers
Oleg Nesterov (5):
task_work_add: generic process-context callbacks
genirq: reimplement exit_irq_thread() hook via task_work_add()
keys: change keyctl_session_to_parent() to use task_work_add()
keys: kill the dummy key_replace_session_keyring()
keys: kill task_struct->replacement_session_keyring
Diffstat:
arch/alpha/kernel/signal.c | 2 -
arch/arm/kernel/signal.c | 2 -
arch/avr32/kernel/entry-avr32b.S | 2 +-
arch/avr32/kernel/signal.c | 2 -
arch/blackfin/kernel/signal.c | 2 -
arch/c6x/kernel/signal.c | 2 -
arch/cris/kernel/ptrace.c | 2 -
arch/frv/kernel/signal.c | 2 -
arch/h8300/kernel/signal.c | 2 -
arch/hexagon/kernel/signal.c | 2 -
arch/ia64/kernel/process.c | 2 -
arch/m32r/kernel/signal.c | 2 -
arch/m68k/kernel/signal.c | 5 +--
arch/microblaze/kernel/signal.c | 5 +--
arch/mips/kernel/signal.c | 2 -
arch/mn10300/kernel/signal.c | 2 -
arch/openrisc/kernel/signal.c | 2 -
arch/parisc/kernel/entry.S | 2 +-
arch/parisc/kernel/signal.c | 2 -
arch/powerpc/kernel/signal.c | 2 -
arch/s390/kernel/signal.c | 2 -
arch/score/kernel/signal.c | 2 -
arch/sh/kernel/signal_32.c | 2 -
arch/sh/kernel/signal_64.c | 2 -
arch/sparc/kernel/signal_32.c | 2 -
arch/sparc/kernel/signal_64.c | 2 -
arch/tile/kernel/process.c | 2 -
arch/um/kernel/process.c | 5 +--
arch/unicore32/kernel/signal.c | 2 -
arch/x86/kernel/signal.c | 2 -
arch/xtensa/kernel/signal.c | 5 +--
include/linux/interrupt.h | 4 --
include/linux/key.h | 4 --
include/linux/sched.h | 14 ++-----
include/linux/task_work.h | 33 +++++++++++++++
include/linux/tracehook.h | 13 +++++-
kernel/Makefile | 2 +-
kernel/cred.c | 9 ----
kernel/exit.c | 5 +-
kernel/fork.c | 1 +
kernel/irq/manage.c | 68 +++++++++++++++----------------
kernel/task_work.c | 84 ++++++++++++++++++++++++++++++++++++++
security/keys/internal.h | 2 +
security/keys/keyctl.c | 73 ++++++++++++++++-----------------
security/keys/process_keys.c | 20 +++------
45 files changed, 220 insertions(+), 186 deletions(-)
create mode 100644 include/linux/task_work.h
create mode 100644 kernel/task_work.c
next reply other threads:[~2012-05-31 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 23:57 Al Viro [this message]
2012-06-01 1:49 ` [git pull] signal.git pile 2 (of 3, probably) Linus Torvalds
2012-06-01 2:14 ` Al Viro
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=20120531235748.GE30000@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.