From: Stafford Horne <shorne@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jonas Bonn <jonas@southpole.se>, Arnd Bergmann <arnd@arndb.de>,
Randy Dunlap <rdunlap@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Openrisc <openrisc@lists.librecores.org>
Subject: Re: [OpenRISC] [PATCH] openrisc: remove CONFIG_SET_FS
Date: Sun, 6 Feb 2022 19:04:06 +0900 [thread overview]
Message-ID: <Yf+dFv1Fj3LFsaot@antec> (raw)
In-Reply-To: <CAMuHMdW2bxEtaYaLN28xk2uc=OV0ecUy-N_+Ay193gZq4nH0jw@mail.gmail.com>
H Geert,
Thanks for looking after it.
On Sun, Feb 06, 2022 at 10:42:46AM +0100, Geert Uytterhoeven wrote:
> Hi Stafford,
>
> Thanks for your patch!
>
> On Sun, Feb 6, 2022 at 2:37 AM Stafford Horne <shorne@gmail.com> wrote:
> > Remove the address space override API set_fs() used for User Mode Linux.
>
> Note: this doesn't have anything to do with UML...
Yes, I agree for UML, I was actually following the text from Christoph's patch
here:
https://lore.kernel.org/lkml/20211215165612.554426-1-hch@lst.de/T/#m439e32b3ecc8404424d2d8115d49fbf27c6393e9
The wording 'User Mode Linux' was perculiar. Maybe I should remove the
misleading text and just say:
Remove the address space override API set_fs().
-Stafford
> > User address space is now limited to TASK_SIZE.
> >
> > To support this we implement and wire in __get_kernel_nofault and
> > __set_kernel_nofault.
> >
> > The function user_addr_max is removed as there is a default definition
> > provided when CONFIG_SET_FS is not used.
> >
> > Signed-off-by: Stafford Horne <shorne@gmail.com>
next prev parent reply other threads:[~2022-02-06 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 1:36 [PATCH] openrisc: remove CONFIG_SET_FS Stafford Horne
2022-02-06 9:42 ` [OpenRISC] " Geert Uytterhoeven
2022-02-06 10:04 ` Stafford Horne [this message]
2022-02-07 6:45 ` Christoph Hellwig
2022-02-07 7:23 ` Stafford Horne
2022-02-07 17:14 ` David Laight
2022-02-08 5:29 ` Stafford Horne
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=Yf+dFv1Fj3LFsaot@antec \
--to=shorne@gmail.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.org \
--cc=rdunlap@infradead.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