From: Nick Desaulniers <ndesaulniers@google.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Tue, 19 Sep 2023 14:18:36 -0700 [thread overview]
Message-ID: <ZQoQLJnGFxjA8p5E@google.com> (raw)
In-Reply-To: <04b8a6de-2b20-4488-b20f-c8a8f6001fd2@infradead.org>
On Tue, Sep 19, 2023 at 08:42:07AM -0700, Randy Dunlap wrote:
>
>
> On 9/18/23 23:37, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20230918:
> >
> > New tree: kvm-ppc
> >
> > The mm tree gained a boot warning for which I reverted 5 commits.
> >
> > Non-merge commits (relative to Linus' tree): 5750
> > 3717 files changed, 446028 insertions(+), 107378 deletions(-)
> >
> > ----------------------------------------------------------------------------
> >
>
> 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?
Oh 3300c3 was patch 10/13; maybe a clean revert is not possible without
other reverts in addition?
https://lore.kernel.org/lkml/20230918072955.2507221-11-rppt@kernel.org/
Seems like there's more info in this thread:
https://lore.kernel.org/lkml/20230919152031.GF3303@kernel.org/
WARNING: multiple messages have this Message-ID (diff)
From: Nick Desaulniers <ndesaulniers@google.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Tue, 19 Sep 2023 14:18:36 -0700 [thread overview]
Message-ID: <ZQoQLJnGFxjA8p5E@google.com> (raw)
In-Reply-To: <04b8a6de-2b20-4488-b20f-c8a8f6001fd2@infradead.org>
On Tue, Sep 19, 2023 at 08:42:07AM -0700, Randy Dunlap wrote:
>
>
> On 9/18/23 23:37, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20230918:
> >
> > New tree: kvm-ppc
> >
> > The mm tree gained a boot warning for which I reverted 5 commits.
> >
> > Non-merge commits (relative to Linus' tree): 5750
> > 3717 files changed, 446028 insertions(+), 107378 deletions(-)
> >
> > ----------------------------------------------------------------------------
> >
>
> 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?
Oh 3300c3 was patch 10/13; maybe a clean revert is not possible without
other reverts in addition?
https://lore.kernel.org/lkml/20230918072955.2507221-11-rppt@kernel.org/
Seems like there's more info in this thread:
https://lore.kernel.org/lkml/20230919152031.GF3303@kernel.org/
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-09-19 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 6:37 linux-next: Tree for Sep 19 Stephen Rothwell
2023-09-19 15:42 ` linux-next: Tree for Sep 19 (UML) Randy Dunlap
2023-09-19 15:42 ` Randy Dunlap
2023-09-19 21:18 ` Nick Desaulniers [this message]
2023-09-19 21:18 ` Nick Desaulniers
2023-09-19 23:18 ` Stephen Rothwell
2023-09-19 23:18 ` Stephen Rothwell
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=ZQoQLJnGFxjA8p5E@google.com \
--to=ndesaulniers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=sfr@canb.auug.org.au \
/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.