From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marco Elver <elver@google.com>
Cc: Hui Su <sh_def@163.com>, Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH][next] arm64: fix the mm build error in mm/kfence/core.c
Date: Tue, 8 Dec 2020 07:32:14 +1100 [thread overview]
Message-ID: <20201208073214.0d3bd2b8@canb.auug.org.au> (raw)
In-Reply-To: <CANpmjNOWpa17L7mjhKdaFjWYfAzy12NjXUDtuPHpzm808QApRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Hi Marco,
On Mon, 7 Dec 2020 15:52:07 +0100 Marco Elver <elver@google.com> wrote:
>
> On Sun, 6 Dec 2020 at 23:08, Marco Elver <elver@google.com> wrote:
> > On Sun, 6 Dec 2020 at 22:23, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> [...]
> > > > ../arch/arm64/include/asm/kfence.h:12:2: error: implicit declaration of
> > > > function ‘set_memory_valid’ [-Werror=implicit-function-declaration]
> > > > 12 | set_memory_valid(addr, 1, !protect);
> > > > | ^~~~~~~~~~~~~~~~
> > > > cc1: some warnings being treated as errors
> > > >
> > > > which introduced by commit d54febeba2ff ("kfence: use pt_regs to
> > > > generate stack trace on faults").
> > > >
> > > > Signed-off-by: Hui Su <sh_def@163.com>
> > > > ---
> > > > arch/arm64/include/asm/kfence.h | 1 +
> > > > 1 file changed, 1 insertion(+)
> >
> > Thanks, but a patch for this is already in the -mm tree:
> > https://lore.kernel.org/mm-commits/20201205011409.o9PNsRntR%25akpm@linux-foundation.org/
> >
> > Perhaps try the latest -next?
>
> Although I notice that patch somehow was dropped from -mm, or maybe
> I'm not looking hard enough?
It may just be that Andrew has not published that version of his patch
series yet.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-12-07 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 17:22 [PATCH][next] arm64: fix the mm build error in mm/kfence/core.c Hui Su
2020-12-06 21:23 ` Stephen Rothwell
2020-12-06 22:08 ` Marco Elver
2020-12-07 14:52 ` Marco Elver
2020-12-07 20:32 ` 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=20201208073214.0d3bd2b8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sh_def@163.com \
--cc=will@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).