From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
linux-mips@vger.kernel.org, clang-built-linux@googlegroups.com,
Fangrui Song <maskray@google.com>,
Kees Cook <keescook@chromium.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Paul Burton <paulburton@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Jouni Hogander <jouni.hogander@unikie.com>,
Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>,
Borislav Petkov <bp@suse.de>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] MIPS: Truncate link address into 32bit for 32bit kernel
Date: Mon, 4 May 2020 18:56:14 +0200 [thread overview]
Message-ID: <20200504165614.GA15545@alpha.franken.de> (raw)
In-Reply-To: <86D4A0AC-59E1-4C82-B66D-6BFC71E08376@flygoat.com>
On Tue, May 05, 2020 at 12:09:46AM +0800, Jiaxun Yang wrote:
>
> 于 2020年5月4日 GMT+08:00 下午11:46:13, Thomas Bogendoerfer <tsbogend@alpha.franken.de> 写到:
> >On Fri, Apr 24, 2020 at 01:22:30PM +0100, Maciej W. Rozycki wrote:
> >> On Thu, 23 Apr 2020, Jiaxun Yang wrote:
> >>
> >> > > Alternatively, have you made any attempt to verify if actually replacing
> >> > >the setting for VMLINUX_LOAD_ADDRESS would be safe? Glancing over its use
> >> > >there do not appear to be many places.
> >> >
> >> > Limited experiments showed it should be fine...
> >> >
> >> > But MIPS kernel has some design I'm not really familiar with like SYM32 for
> >> > 64-bit kernel and special address space design for Trap-and-emul KVM.
> >>
> >> This only affects CONFIG_32BIT kernels, so SYM32 does not apply; I can't
> >> comment on KVM. There's still that bunch of:
> >>
> >> $(shell expr $(...) \< 0xffffffff80000000)
> >>
> >> constructs I mentioned before, so let's leave your change as it stands at
> >> this time. Please do rename the variable as I suggested though, I hope
> >> that's not a big deal.
> >
> >Jiaxun, are you going to send an update with this change ?
>
> Sorry my mail server missed Maciej's reply.
>
> Should I send another version or you just fix it at apply time?
please send a new version, thank you.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-05-04 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 6:26 [PATCH v4] MIPS: Truncate link address into 32bit for 32bit kernel Jiaxun Yang
2020-04-13 6:59 ` Maciej W. Rozycki
2020-04-13 7:32 ` Jiaxun Yang
2020-04-13 15:34 ` Fangrui Song
2020-04-13 20:08 ` Maciej W. Rozycki
2020-04-13 20:06 ` Maciej W. Rozycki
2020-04-13 16:25 ` Kees Cook
2020-04-13 18:52 ` Nathan Chancellor
2020-04-22 14:32 ` [PATCH v5] " Jiaxun Yang
2020-04-22 22:16 ` Nathan Chancellor
2020-04-23 0:10 ` Maciej W. Rozycki
2020-04-23 5:42 ` Jiaxun Yang
2020-04-24 12:22 ` Maciej W. Rozycki
2020-05-04 15:46 ` Thomas Bogendoerfer
2020-05-04 16:09 ` Jiaxun Yang
2020-05-04 16:56 ` Thomas Bogendoerfer [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=20200504165614.GA15545@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bp@suse.de \
--cc=clang-built-linux@googlegroups.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jiaxun.yang@flygoat.com \
--cc=jouni.hogander@unikie.com \
--cc=keescook@chromium.org \
--cc=ldir@darbyshire-bryant.me.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=natechancellor@gmail.com \
--cc=paulburton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox