linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Oleg Nesterov <oleg@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Arch/task_work cleanup
Date: Thu, 22 Oct 2020 20:04:48 -0600	[thread overview]
Message-ID: <e1e0acc8-1859-bd37-80ab-612a122a334f@kernel.dk> (raw)

Hi Linus,

Two cleanups that don't fit other categories:

- Finally get the task_work_add() cleanup done properly, so we don't
  have random 0/1/false/true/TWA_SIGNAL confusing use cases. Updates all
  callers, and also fixes up the documentation for task_work_add().

- While working on some TIF related changes for 5.11, this
  TIF_NOTIFY_RESUME cleanup fell out of that. Remove some arch
  duplication for how that is handled.

Please pull!


The following changes since commit 324bcf54c449c7b5b7024c9fa4549fbaaae1935d:

  mm: use limited read-ahead to satisfy read (2020-10-17 13:49:08 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/arch-cleanup-2020-10-22

for you to fetch changes up to 91989c707884ecc7cd537281ab1a4b8fb7219da3:

  task_work: cleanup notification modes (2020-10-17 15:05:30 -0600)

----------------------------------------------------------------
arch-cleanup-2020-10-22

----------------------------------------------------------------
Jens Axboe (2):
      tracehook: clear TIF_NOTIFY_RESUME in tracehook_notify_resume()
      task_work: cleanup notification modes

 arch/alpha/kernel/signal.c             |  1 -
 arch/arc/kernel/signal.c               |  2 +-
 arch/arm/kernel/signal.c               |  1 -
 arch/arm64/kernel/signal.c             |  1 -
 arch/c6x/kernel/signal.c               |  4 +---
 arch/csky/kernel/signal.c              |  1 -
 arch/h8300/kernel/signal.c             |  4 +---
 arch/hexagon/kernel/process.c          |  1 -
 arch/ia64/kernel/process.c             |  2 +-
 arch/m68k/kernel/signal.c              |  2 +-
 arch/microblaze/kernel/signal.c        |  2 +-
 arch/mips/kernel/signal.c              |  1 -
 arch/nds32/kernel/signal.c             |  4 +---
 arch/nios2/kernel/signal.c             |  2 +-
 arch/openrisc/kernel/signal.c          |  1 -
 arch/parisc/kernel/signal.c            |  4 +---
 arch/powerpc/kernel/signal.c           |  1 -
 arch/riscv/kernel/signal.c             |  4 +---
 arch/s390/kernel/signal.c              |  1 -
 arch/sh/kernel/signal_32.c             |  4 +---
 arch/sparc/kernel/signal_32.c          |  4 +---
 arch/sparc/kernel/signal_64.c          |  4 +---
 arch/um/kernel/process.c               |  2 +-
 arch/x86/kernel/cpu/mce/core.c         |  2 +-
 arch/x86/kernel/cpu/resctrl/rdtgroup.c |  2 +-
 arch/xtensa/kernel/signal.c            |  2 +-
 drivers/acpi/apei/ghes.c               |  2 +-
 drivers/android/binder.c               |  2 +-
 fs/file_table.c                        |  2 +-
 fs/io_uring.c                          | 13 +++++++------
 fs/namespace.c                         |  2 +-
 include/linux/task_work.h              | 11 ++++++++---
 include/linux/tracehook.h              |  4 ++--
 kernel/entry/common.c                  |  1 -
 kernel/entry/kvm.c                     |  4 +---
 kernel/events/uprobes.c                |  2 +-
 kernel/irq/manage.c                    |  2 +-
 kernel/sched/fair.c                    |  2 +-
 kernel/task_work.c                     | 30 ++++++++++++++++++++----------
 security/keys/keyctl.c                 |  2 +-
 security/yama/yama_lsm.c               |  2 +-
 41 files changed, 64 insertions(+), 76 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2020-10-23  2:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23  2:04 Jens Axboe [this message]
2020-10-23 18:53 ` [GIT PULL] Arch/task_work cleanup pr-tracker-bot

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=e1e0acc8-1859-bd37-80ab-612a122a334f@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).