All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Harald Freudenberger <freude@linux.ibm.com>
Cc: linux-s390@vger.kernel.org
Subject: set_fs removal for s390
Date: Tue, 8 Sep 2020 08:31:33 +0200	[thread overview]
Message-ID: <20200908063133.GA14217@lst.de> (raw)

Hi s390 maintainers,

the base work to remove address space overrides using set_fs() has
landed in linux-next through this tree:

https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git/log/?h=base.set_fs

and in addition to x86 and powerpc converted there, we have arm, arm64
and RISC-V conversion in progress.  That means s390 is the only "tier 1"
architecture still missing.  Due to the special instructions for
accessing the user space address space I don't really feel like doing
the conversion myself, but it would be great if we could get s390 done
for 5.10 as well.

The rought TODO list is:
 (1) actually stop using set_fs in the zrcypt driver.  I could prepare
     a crude untested patch for that if it helps.
 (2) implement the __get_user_nofault and __put_user_nofault helpers to
     safely access kernel memory.  These should behave like
     get_user/put_user under set_fs(KERNEL_DS), but not actually
     manipulate any task state to do so
 (3) unselect CONFIG_SET_FS and remove all the code related to overriding
     the address space(3) unselect CONFIG_SET_FS and remove all the code
     related to overriding the address space limit

             reply	other threads:[~2020-09-08  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08  6:31 Christoph Hellwig [this message]
2020-09-08 12:26 ` set_fs removal for s390 Heiko Carstens
2020-09-08 12:28   ` Christoph Hellwig

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=20200908063133.GA14217@lst.de \
    --to=hch@lst.de \
    --cc=borntraeger@de.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.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.