From: gregkh <gregkh@linuxfoundation.org>
To: Laura Abbott <labbott@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
stable <stable@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Olof's autobuilder <build@lixom.net>
Subject: Re: stable-rc build: 0 warnings 1 failures (stable-rc/v4.9.53-105-g0e59436)
Date: Sat, 7 Oct 2017 12:06:59 +0200 [thread overview]
Message-ID: <20171007100659.GA25029@kroah.com> (raw)
In-Reply-To: <fa7f5e03-f1ea-0bc4-b5c5-28d73c2195c4@redhat.com>
On Fri, Oct 06, 2017 at 08:14:40AM -0700, Laura Abbott wrote:
> On 10/06/2017 04:27 AM, Arnd Bergmann wrote:
> > On Fri, Oct 6, 2017 at 12:03 PM, Olof's autobuilder <build@lixom.net> wrote:
> >> Here are the build results from automated periodic testing.
> >>
> >> The tree being built was stable-rc, found at:
> >>
> >> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable-rc.git/
> >>
> >> Topmost commit:
> >>
> >> 0e59436 Linux 4.9.54-rc1
> >
> >>
> >> arm64.allmodconfig:
> >> /work/build/batch/arch/arm64/mm/kasan_init.c:156:95: error: implicit declaration of function 'lm_alias'; did you mean 'mm_alloc'? [-Werror=implicit-function-declaration]
> >
> > Caused by
> >
> > e773d137b255 ("arm64: kasan: avoid bad virt_to_pfn()")
> > (backported from b0de0ccc8b9ed)
> >
> > Presumably requires a backport of
> >
> > 568c5fe5a54f ("mm: Introduce lm_alias")
> >
> > Mark or Laura, can you confirm that this is the correct fix?
> > I see additional uses of lm_alias in mainline, but only this one
> > backported to stable, not sure if only this one is required there,
> > or we want the others as well.
> >
> > Arnd
> >
>
>
> I don't think backporting lm_alias is the correct fix. That was
> introduced as part of DEBUG_VIRTUAL for arm64 which isn't present
> at all for 4.9. If DEBUG_VIRTUAL isn't present, there should be
> no need for this fix since it's handled by existing code. I
> think the patch should be dropped assuming there isn't another
> issue with kasan.
I've just dropped it now, sorry for this.
thanks,
greg k-h
prev parent reply other threads:[~2017-10-07 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59d754da.44f9620a.a7f1b.52e0@mx.google.com>
2017-10-06 11:27 ` stable-rc build: 0 warnings 1 failures (stable-rc/v4.9.53-105-g0e59436) Arnd Bergmann
2017-10-06 15:14 ` Laura Abbott
2017-10-07 10:06 ` gregkh [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=20171007100659.GA25029@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=build@lixom.net \
--cc=kernel-build-reports@lists.linaro.org \
--cc=labbott@redhat.com \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=stable@vger.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).