From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-um <linux-um@lists.infradead.org>,
Mike Rapoport <rppt@kernel.org>,
llvm@lists.linux.dev
Subject: Re: linux-next: Tree for Sep 19 (UML)
Date: Wed, 20 Sep 2023 09:18:28 +1000 [thread overview]
Message-ID: <20230920091714.10053ba5@canb.auug.org.au> (raw)
In-Reply-To: <ZQoQLJnGFxjA8p5E@google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1428 bytes --]
Hi Nick,
On Tue, 19 Sep 2023 14:18:36 -0700 Nick Desaulniers <ndesaulniers@google.com> wrote:
>
> On Tue, Sep 19, 2023 at 08:42:07AM -0700, Randy Dunlap wrote:
> >
> > on i386 or x86_64:
> >
> > ../arch/x86/um/../kernel/module.c: In function 'execmem_arch_params':
> > ../arch/x86/um/../kernel/module.c:54:50: error: implicit declaration of function 'kaslr_enabled'; did you mean 'kasan_enabled'? [-Werror=implicit-function-declaration]
> > 54 | if (IS_ENABLED(CONFIG_RANDOMIZE_BASE) && kaslr_enabled())
> > | ^~~~~~~~~~~~~
> > | kasan_enabled
> >
> >
> >
> > git blames this on:
> >
> > commit 12633d679796
> > Author: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Tue Sep 19 15:14:03 2023 +1000
> >
> > Revert "arch: make execmem setup available regardless of CONFIG_MODULES"
> >
> > This reverts commit 3300c3af20090ff5e03e5c4bf2ef2cfaa03d4e9b.
>
> Thanks for the report, FWIW, our CI is hitting this, too.
>
> Was 12633d679796 a pure revert, or was it manually modified?
It was a pure revert due to having to revert a previous commit to fix a
boot warning. These reverts should not need to be in the next
linux-next as a patch has been applied to the appropriate included tree
to fix the boot warning.
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
prev parent reply other threads:[~2023-09-19 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230919163728.78432283@canb.auug.org.au>
2023-09-19 15:42 ` linux-next: Tree for Sep 19 (UML) Randy Dunlap
2023-09-19 21:18 ` Nick Desaulniers
2023-09-19 23:18 ` Stephen Rothwell [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=20230920091714.10053ba5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=rdunlap@infradead.org \
--cc=rppt@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;
as well as URLs for NNTP newsgroup(s).