All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
	Michael Ellerman <mpe@ellerman.id.au>,
	the arch/x86 maintainers <x86@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 08/10] x86: remove address space overrides using set_fs()
Date: Sat, 29 Aug 2020 11:25:31 +0200	[thread overview]
Message-ID: <20200829092531.GC8833@lst.de> (raw)
In-Reply-To: <CAHk-=wjxeN+KrCB2TyC5s2RWhz-dWWO8vbBwWcCiKb0+8ipayw@mail.gmail.com>

On Thu, Aug 27, 2020 at 11:15:12AM -0700, Linus Torvalds wrote:
> >  SYM_FUNC_START(__put_user_2)
> > -       ENTER
> > -       mov TASK_addr_limit(%_ASM_BX),%_ASM_BX
> > +       LOAD_TASK_SIZE_MAX
> >         sub $1,%_ASM_BX
> 
> It's even more obvious here. We load a constant and then immediately
> do a "sub $1" on that value.
> 
> It's not a huge deal, you don't have to respin the series for this, I
> just wanted to point it out so that people are aware of it and if I
> forget somebody else will hopefully remember that "we should fix that
> too".

The changes seem easy enough and I need to respin at least for the
lkdtm changes, and probaby also for a pending fix in the low-level
x86 code that will hopefully be picked up for 5.9.

But the more important questions is: how do we want to pick the series
up?  Especially due to the splice changes I really want it to be in
linux-next as long as possible.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-arch <linux-arch@vger.kernel.org>,
	Kees Cook <keescook@chromium.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 08/10] x86: remove address space overrides using set_fs()
Date: Sat, 29 Aug 2020 11:25:31 +0200	[thread overview]
Message-ID: <20200829092531.GC8833@lst.de> (raw)
In-Reply-To: <CAHk-=wjxeN+KrCB2TyC5s2RWhz-dWWO8vbBwWcCiKb0+8ipayw@mail.gmail.com>

On Thu, Aug 27, 2020 at 11:15:12AM -0700, Linus Torvalds wrote:
> >  SYM_FUNC_START(__put_user_2)
> > -       ENTER
> > -       mov TASK_addr_limit(%_ASM_BX),%_ASM_BX
> > +       LOAD_TASK_SIZE_MAX
> >         sub $1,%_ASM_BX
> 
> It's even more obvious here. We load a constant and then immediately
> do a "sub $1" on that value.
> 
> It's not a huge deal, you don't have to respin the series for this, I
> just wanted to point it out so that people are aware of it and if I
> forget somebody else will hopefully remember that "we should fix that
> too".

The changes seem easy enough and I need to respin at least for the
lkdtm changes, and probaby also for a pending fix in the low-level
x86 code that will hopefully be picked up for 5.9.

But the more important questions is: how do we want to pick the series
up?  Especially due to the splice changes I really want it to be in
linux-next as long as possible.

  reply	other threads:[~2020-08-29  9:25 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 15:00 remove the last set_fs() in common code, and remove it for x86 and powerpc v2 Christoph Hellwig
2020-08-27 15:00 ` Christoph Hellwig
2020-08-27 15:00 ` [PATCH 01/10] fs: don't allow kernel reads and writes without iter ops Christoph Hellwig
2020-08-27 15:00   ` Christoph Hellwig
2020-08-27 15:58   ` David Laight
2020-08-29  9:23     ` 'Christoph Hellwig'
2020-08-29  9:23       ` 'Christoph Hellwig'
2020-09-01  6:48   ` [fs] ef30fb3c60: kernel write not supported for file /sys/kernel/softlockup_panic kernel test robot
2020-09-01  6:48     ` kernel test robot
2020-09-01  6:48     ` kernel test robot
2020-09-01  7:08     ` Christoph Hellwig
2020-09-01  7:08       ` Christoph Hellwig
2020-09-01  7:08       ` Christoph Hellwig
2020-08-27 15:00 ` [PATCH 02/10] fs: don't allow splice read/write without explicit ops Christoph Hellwig
2020-08-27 15:00   ` Christoph Hellwig
2020-10-27  9:29   ` David Howells
2020-10-27  9:29     ` David Howells
2020-10-27  9:51     ` David Howells
2020-10-27  9:51       ` David Howells
2020-10-27  9:54       ` Christoph Hellwig
2020-10-27  9:54         ` Christoph Hellwig
2020-10-27 10:38         ` David Howells
2020-10-27 10:38           ` David Howells
2020-08-27 15:00 ` [PATCH 03/10] uaccess: add infrastructure for kernel builds with set_fs() Christoph Hellwig
2020-08-27 15:00   ` Christoph Hellwig
2020-08-27 15:00 ` [PATCH 04/10] test_bitmap: skip user bitmap tests for !CONFIG_SET_FS Christoph Hellwig
2020-08-27 15:00   ` Christoph Hellwig
2020-08-27 15:00 ` [PATCH 05/10] lkdtm: disable set_fs-based " Christoph Hellwig
2020-08-27 15:00   ` Christoph Hellwig
2020-08-27 18:06   ` Linus Torvalds
2020-08-27 18:06     ` Linus Torvalds
2020-08-29  9:24     ` Christoph Hellwig
2020-08-29  9:24       ` Christoph Hellwig
2020-09-01 18:52       ` Kees Cook
2020-09-01 18:52         ` Kees Cook
2020-09-01 18:57       ` Kees Cook
2020-09-01 18:57         ` Kees Cook
2020-09-02  8:09         ` Christoph Hellwig
2020-09-02  8:09           ` Christoph Hellwig
2020-08-27 15:00 ` [PATCH 06/10] x86: move PAGE_OFFSET, TASK_SIZE & friends to page_{32,64}_types.h Christoph Hellwig
2020-08-27 15:00   ` [PATCH 06/10] x86: move PAGE_OFFSET, TASK_SIZE & friends to page_{32, 64}_types.h Christoph Hellwig
2020-08-27 15:00 ` [PATCH 07/10] x86: make TASK_SIZE_MAX usable from assembly code Christoph Hellwig
2020-08-27 15:00   ` Christoph Hellwig
2020-08-27 15:00 ` [PATCH 08/10] x86: remove address space overrides using set_fs() Christoph Hellwig
2020-08-27 15:00   ` Christoph Hellwig
2020-08-27 18:15   ` Linus Torvalds
2020-08-27 18:15     ` Linus Torvalds
2020-08-29  9:25     ` Christoph Hellwig [this message]
2020-08-29  9:25       ` Christoph Hellwig
2020-08-27 15:00 ` [PATCH 09/10] powerpc: use non-set_fs based maccess routines Christoph Hellwig
2020-08-27 15:00   ` Christoph Hellwig
2020-08-27 15:00 ` [PATCH 10/10] powerpc: remove address space overrides using set_fs() Christoph Hellwig
2020-08-27 15:00   ` Christoph Hellwig
2020-09-02  6:15   ` Christophe Leroy
2020-09-02 12:36     ` Christoph Hellwig
2020-09-02 12:36       ` Christoph Hellwig
2020-09-02 13:13       ` David Laight
2020-09-02 13:13         ` David Laight
2020-09-02 13:24         ` Christophe Leroy
2020-09-02 13:24           ` Christophe Leroy
2020-09-02 13:51           ` David Laight
2020-09-02 13:51             ` David Laight
2020-09-02 14:12             ` Christophe Leroy
2020-09-02 14:12               ` Christophe Leroy
2020-09-02 15:02               ` David Laight
2020-09-02 15:02                 ` David Laight
2020-09-02 15:17       ` Christophe Leroy
2020-09-02 15:17         ` Christophe Leroy
2020-09-02 18:02         ` Linus Torvalds
2020-09-02 18:02           ` Linus Torvalds
2020-09-03  7:11           ` Christoph Hellwig
2020-09-03  7:11             ` Christoph Hellwig
2020-09-03  7:27             ` Christophe Leroy
2020-09-03  7:27               ` Christophe Leroy
2020-09-03  8:55             ` Christophe Leroy
2020-09-03  8:55               ` Christophe Leroy
2020-09-03  7:20           ` Christophe Leroy
2020-09-03  7:20             ` Christophe Leroy
2020-08-27 15:31 ` remove the last set_fs() in common code, and remove it for x86 and powerpc v2 Christoph Hellwig
2020-09-01 17:13 ` Christophe Leroy
2020-09-01 17:25   ` Al Viro
2020-09-01 17:25     ` Al Viro
2020-09-01 17:42     ` Matthew Wilcox
2020-09-01 17:42       ` Matthew Wilcox
2020-09-01 18:39     ` Christophe Leroy
2020-09-01 18:39       ` Christophe Leroy
2020-09-01 19:01     ` Christophe Leroy
2020-09-01 19:01       ` Christophe Leroy
2020-09-02  8:10     ` Christoph Hellwig
2020-09-02  8:10       ` 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=20200829092531.GC8833@lst.de \
    --to=hch@lst.de \
    --cc=keescook@chromium.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=x86@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.