From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] exec: open code copy_string_kernel
Date: Sat, 2 May 2020 08:23:51 +0200 [thread overview]
Message-ID: <20200502062351.GA2158@lst.de> (raw)
In-Reply-To: <20200501220449.GQ23230@ZenIV.linux.org.uk>
On Fri, May 01, 2020 at 11:04:49PM +0100, Al Viro wrote:
> Long story - basically, it's been a source of massive headache too many times.
> No formal project, but there are several people (me, Arnd, Christoph) who'd
> been reducing its use. For more than a decade now, I think...
>
> FWIW, I doubt that it will be entirely killable; Christoph appears to be
> more optimistic. In any case, its use has been greatly reduced and having
> it narrowed down to even fewer places would be a good thing.
>
> In the same direction: use_mm()/unuse_mm() regularization wrt set_fs(), getting
> rid of it in coredump code, some movements towards killing ioctl_by_bdev();
> not sure if I've spotted everything - Christoph?
That's the big current projects out in the wild. I have a few more
growing.
prev parent reply other threads:[~2020-05-02 6:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 10:41 remove set_fs from copy_strings_kernel Christoph Hellwig
2020-05-01 10:41 ` [PATCH 1/2] exec: simplify the copy_strings_kernel calling convention Christoph Hellwig
2020-05-01 10:41 ` [PATCH 2/2] exec: open code copy_string_kernel Christoph Hellwig
2020-05-01 12:50 ` Al Viro
2020-05-01 19:26 ` Christoph Hellwig
2020-05-01 21:43 ` Al Viro
2020-05-01 21:19 ` Andrew Morton
2020-05-01 21:30 ` Al Viro
2020-05-01 21:40 ` Andrew Morton
2020-05-01 22:04 ` Al Viro
2020-05-02 6:23 ` Christoph Hellwig [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=20200502062351.GA2158@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.