From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: [git pull] set_fs() removal in coredump-related area
Date: Mon, 1 Jun 2020 19:35:15 +0100 [thread overview]
Message-ID: <20200601183515.GG23230@ZenIV.linux.org.uk> (raw)
Mostly Christoph's stuff...
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.set_fs-exec
for you to fetch changes up to 38cdabb7d83522394aaf2de82c3af017ad94e5d8:
binfmt_elf_fdpic: remove the set_fs(KERNEL_DS) in elf_fdpic_core_dump (2020-05-05 16:46:10 -0400)
----------------------------------------------------------------
Christoph Hellwig (5):
powerpc/spufs: stop using access_ok
powerpc/spufs: simplify spufs core dumping
signal: refactor copy_siginfo_to_user32
binfmt_elf: remove the set_fs(KERNEL_DS) in elf_core_dump
binfmt_elf_fdpic: remove the set_fs(KERNEL_DS) in elf_fdpic_core_dump
Eric W. Biederman (1):
binfmt_elf: remove the set_fs in fill_siginfo_note
Jeremy Kerr (1):
powerpc/spufs: fix copy_to_user while atomic
arch/powerpc/platforms/cell/spufs/coredump.c | 87 +++----
arch/powerpc/platforms/cell/spufs/file.c | 330 +++++++++++++--------------
arch/powerpc/platforms/cell/spufs/spufs.h | 3 +-
arch/x86/ia32/ia32_signal.c | 2 +-
arch/x86/include/asm/compat.h | 8 +-
arch/x86/kernel/signal.c | 28 ++-
fs/binfmt_elf.c | 21 +-
fs/binfmt_elf_fdpic.c | 21 +-
fs/compat_binfmt_elf.c | 2 +-
include/linux/compat.h | 11 +-
include/linux/signal.h | 8 +
kernel/signal.c | 106 ++++-----
12 files changed, 300 insertions(+), 327 deletions(-)
next reply other threads:[~2020-06-01 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 18:35 Al Viro [this message]
2020-06-01 23:55 ` [git pull] set_fs() removal in coredump-related area 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=20200601183515.GG23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--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.