From: Al Viro <viro@zeniv•linux.org.uk>
To: Christoph Hellwig <hch@lst•de>
Cc: Arnd Bergmann <arnd@arndb•de>,
linuxppc-dev@lists•ozlabs.org, x86@kernel•org,
Oleg Nesterov <oleg@redhat•com>,
linux-kernel@vger•kernel.org,
"Eric W . Biederman" <ebiederm@xmission•com>,
linux-fsdevel@vger•kernel.org,
Andrew Morton <akpm@linux-foundation•org>,
Linus Torvalds <torvalds@linux-foundation•org>,
Jeremy Kerr <jk@ozlabs•org>
Subject: Re: remove set_fs calls from the coredump code v6
Date: Tue, 5 May 2020 21:47:21 +0100 [thread overview]
Message-ID: <20200505204721.GA23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200505204258.GA24277@lst.de>
On Tue, May 05, 2020 at 10:42:58PM +0200, Christoph Hellwig wrote:
> On Tue, May 05, 2020 at 09:34:46PM +0100, Al Viro wrote:
> > Looks good. Want me to put it into vfs.git? #work.set_fs-exec, perhaps?
>
> Sounds good.
Applied, pushed and added into #for-next
prev parent reply other threads:[~2020-05-05 20:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 10:12 remove set_fs calls from the coredump code v6 Christoph Hellwig
2020-05-05 10:12 ` [PATCH 1/7] powerpc/spufs: fix copy_to_user while atomic Christoph Hellwig
2020-05-05 10:12 ` [PATCH 2/7] powerpc/spufs: stop using access_ok Christoph Hellwig
2020-05-05 10:12 ` [PATCH 3/7] powerpc/spufs: simplify spufs core dumping Christoph Hellwig
2020-05-05 10:12 ` [PATCH 4/7] signal: refactor copy_siginfo_to_user32 Christoph Hellwig
2020-05-05 10:12 ` [PATCH 5/7] binfmt_elf: remove the set_fs in fill_siginfo_note Christoph Hellwig
2020-05-05 10:12 ` [PATCH 6/7] binfmt_elf: remove the set_fs(KERNEL_DS) in elf_core_dump Christoph Hellwig
2020-05-05 10:12 ` [PATCH 7/7] binfmt_elf_fdpic: remove the set_fs(KERNEL_DS) in elf_fdpic_core_dump Christoph Hellwig
2020-05-05 16:52 ` remove set_fs calls from the coredump code v6 Linus Torvalds
2020-05-05 20:28 ` Eric W. Biederman
2020-05-06 6:31 ` Christoph Hellwig
2020-05-06 15:44 ` Eric W. Biederman
2020-05-05 20:34 ` Al Viro
2020-05-05 20:42 ` Christoph Hellwig
2020-05-05 20:47 ` Al Viro [this message]
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=20200505204721.GA23230@ZenIV.linux.org.uk \
--to=viro@zeniv$(echo .)linux.org.uk \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=ebiederm@xmission$(echo .)com \
--cc=hch@lst$(echo .)de \
--cc=jk@ozlabs$(echo .)org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=oleg@redhat$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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