From: Arnd Bergmann <arnd@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-arch <linux-arch@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>, Brian Gerst <brgerst@gmail.com>,
Eric Biederman <ebiederm@xmission.com>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
kexec@lists.infradead.org
Subject: Re: [PATCH v4 1/4] kexec: avoid compat_alloc_user_space
Date: Wed, 21 Jul 2021 23:22:24 +0200 [thread overview]
Message-ID: <CAK8P3a0OkF1G2kNTnn8Nh5aGAf5nnHNZqoQD3TB7mN2_VTV_9w@mail.gmail.com> (raw)
In-Reply-To: <YPbtsU4GX6PL7/42@infradead.org>
On Tue, Jul 20, 2021 at 5:37 PM Christoph Hellwig <hch@infradead.org> wrote:
>
> This can be simplified a little more by killing off
> copy_user_segment_list entirely, using memdup_user and dropping the
> not really required _locked wrapper. The locking move might make
> most sense as a separate prep patch.
Ok, I've integrated this as separate patches into my series now, will resend
after some more build testing.
Arnd
next prev parent reply other threads:[~2021-07-21 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 15:09 [PATCH v4 0/4] compat: remove compat_alloc_user_space callers Arnd Bergmann
2021-07-20 15:09 ` [PATCH v4 1/4] kexec: avoid compat_alloc_user_space Arnd Bergmann
2021-07-20 15:37 ` Christoph Hellwig
2021-07-21 21:22 ` Arnd Bergmann [this message]
2021-07-20 15:09 ` [PATCH v4 2/4] mm: simplify compat_sys_move_pages Arnd Bergmann
2021-07-20 15:09 ` [PATCH v4 3/4] mm: simplify compat numa syscalls Arnd Bergmann
2021-07-20 15:09 ` [PATCH v4 4/4] compat: remove some compat entry points Arnd Bergmann
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=CAK8P3a0OkF1G2kNTnn8Nh5aGAf5nnHNZqoQD3TB7mN2_VTV_9w@mail.gmail.com \
--to=arnd@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=ebiederm@xmission.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.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;
as well as URLs for NNTP newsgroup(s).