openrisc.lists.librecores.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v2 15/18] sparc64: remove CONFIG_SET_FS support
Date: Wed, 16 Feb 2022 19:41:09 +0100	[thread overview]
Message-ID: <Yg1FRZcrhlh5C//V@ravnborg.org> (raw)
In-Reply-To: <Yg1D08+olCSGmnYU@ravnborg.org>

Hi Arnd,

On Wed, Feb 16, 2022 at 07:34:59PM +0100, Sam Ravnborg wrote:
> Hi Arnd.
> 
> On Wed, Feb 16, 2022 at 02:13:29PM +0100, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> > 
> > sparc64 uses address space identifiers to differentiate between kernel
> > and user space, using ASI_P for kernel threads but ASI_AIUS for normal
> > user space, with the option of changing between them.
> > 
> > As nothing really changes the ASI any more, just hardcode ASI_AIUS
> > everywhere. Kernel threads are not allowed to access __user pointers
> > anyway.
> > 
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> >  arch/sparc/include/asm/processor_64.h   |  4 ----
> >  arch/sparc/include/asm/switch_to_64.h   |  4 +---
> >  arch/sparc/include/asm/thread_info_64.h |  4 +---
> >  arch/sparc/include/asm/uaccess_64.h     | 20 +-------------------
> >  arch/sparc/kernel/process_64.c          | 12 ------------
> >  arch/sparc/kernel/traps_64.c            |  2 --
> >  arch/sparc/lib/NGmemcpy.S               |  3 +--
> >  arch/sparc/mm/init_64.c                 |  7 ++++---
> >  8 files changed, 8 insertions(+), 48 deletions(-)
> 
> I think you somehow missed the Kconfig change, and also the related
> sparc32 change which continue to have set_fs() after this patch.
I now notice the sparc32 bits are in the last patch.
To avoid breaking bisect-ability on sparc64 I think you need to merge
the sparc32 changes with this patch, unless the sparc64 changes can
coexist with CONFIG_SET_FS continue to be set.

	Sam

  reply	other threads:[~2022-02-16 18:41 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 13:13 [OpenRISC] [PATCH v2 00/18] clean up asm/uaccess.h, kill set_fs for good Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 01/18] uaccess: fix integer overflow on access_ok() Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 02/18] uaccess: fix nios2 and microblaze get_user_8() Arnd Bergmann
2022-02-16 13:35   ` David Laight
2022-02-18  6:25   ` Christoph Hellwig
2022-02-25  4:28   ` Dinh Nguyen
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 03/18] nds32: fix access_ok() checks in get/put_user Arnd Bergmann
2022-02-18  6:25   ` Christoph Hellwig
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 04/18] sparc64: add __{get, put}_kernel_nocheck() Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 05/18] x86: remove __range_not_ok() Arnd Bergmann
2022-02-18  6:28   ` Christoph Hellwig
2022-02-18  7:29     ` Arnd Bergmann
2022-02-18 15:45     ` David Laight
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 06/18] x86: use more conventional access_ok() definition Arnd Bergmann
2022-02-18  6:29   ` Christoph Hellwig
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 07/18] nios2: drop access_ok() check from __put_user() Arnd Bergmann
2022-02-18  6:29   ` Christoph Hellwig
2022-02-23 23:30   ` Dinh Nguyen
2022-02-24  7:05     ` Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 08/18] uaccess: add generic __{get, put}_kernel_nofault Arnd Bergmann
2022-02-18  6:30   ` Christoph Hellwig
2022-02-18  8:55   ` Geert Uytterhoeven
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 09/18] mips: use simpler access_ok() Arnd Bergmann
2022-02-21 13:24   ` Thomas Bogendoerfer
2022-02-21 14:31     ` Arnd Bergmann
2022-02-21 15:21       ` Thomas Bogendoerfer
2022-02-22 16:36       ` Thomas Bogendoerfer
2022-02-23 20:05     ` Linus Torvalds
2022-02-23  7:41   ` Thomas Bogendoerfer
2022-02-23  9:26     ` Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 10/18] m68k: fix access_ok for coldfire Arnd Bergmann
2022-02-18  6:30   ` Christoph Hellwig
2022-02-18  9:00   ` Geert Uytterhoeven
2022-02-18  9:24     ` Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 11/18] arm64: simplify access_ok() Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 12/18] uaccess: fix type mismatch warnings from access_ok() Arnd Bergmann
2022-02-18  6:31   ` Christoph Hellwig
2022-02-25  4:30   ` Dinh Nguyen
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 13/18] uaccess: generalize access_ok() Arnd Bergmann
2022-02-17  7:52   ` Arnd Bergmann
2022-02-17 19:15   ` Andy Lutomirski
2022-02-18  7:16     ` Arnd Bergmann
2022-02-18  9:30     ` David Laight
2022-02-18 18:07       ` Andy Lutomirski
2022-02-18  6:34   ` Christoph Hellwig
2022-02-18  7:23     ` Arnd Bergmann
2022-02-18  9:04   ` Geert Uytterhoeven
2022-02-24  8:29   ` Stafford Horne
2022-02-24  8:41     ` Arnd Bergmann
2022-02-25  4:31   ` Dinh Nguyen
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 14/18] lib/test_lockup: fix kernel pointer check for separate address spaces Arnd Bergmann
2022-02-18  6:35   ` Christoph Hellwig
2022-02-18  7:15     ` Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 15/18] sparc64: remove CONFIG_SET_FS support Arnd Bergmann
2022-02-16 18:34   ` Sam Ravnborg
2022-02-16 18:41     ` Sam Ravnborg [this message]
2022-02-16 22:01       ` Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 16/18] sh: " Arnd Bergmann
2022-02-18  6:36   ` Christoph Hellwig
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 17/18] ia64: " Arnd Bergmann
2022-02-16 13:13 ` [OpenRISC] [PATCH v2 18/18] uaccess: drop maining CONFIG_SET_FS users Arnd Bergmann
2022-02-16 18:44   ` Sam Ravnborg
2022-02-16 22:02     ` Arnd Bergmann
2022-02-17 22:36   ` Eric W. Biederman
2022-02-18  6:37   ` Christoph Hellwig
2022-02-18  7:10     ` Arnd Bergmann
2022-02-18 10:18   ` Sergey Matyukevich
2022-02-24  8:45   ` Stafford Horne
2022-02-25  4:33   ` Dinh Nguyen
2022-02-17  7:20 ` [OpenRISC] [PATCH v2 00/18] clean up asm/uaccess.h, kill set_fs for good Christophe Leroy
2022-02-17  7:49   ` Arnd Bergmann
2022-02-18  2:21     ` Al Viro
2022-02-18  9:20       ` Arnd Bergmann
2022-02-18  1:50   ` Al Viro
2022-02-18 10:01     ` Christophe Leroy
2022-02-17  8:13 ` 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=Yg1FRZcrhlh5C//V@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=openrisc@lists.librecores.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 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).