From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org
Subject: Re: Build failures and crashes in stable queues (3.19, 4.19, 5.0)
Date: Thu, 21 Mar 2019 19:32:31 +0100 [thread overview]
Message-ID: <20190321183231.GC10586@kroah.com> (raw)
In-Reply-To: <20190321173830.GB29700@roeck-us.net>
On Thu, Mar 21, 2019 at 10:38:30AM -0700, Guenter Roeck wrote:
> On Thu, Mar 21, 2019 at 05:49:40PM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Mar 21, 2019 at 09:16:23AM -0700, Guenter Roeck wrote:
> > > ---
> > > v4.19.y.queue:
> > >
> > > m68k, all builds:
> > >
> > > mm/slab.c: In function '__check_heap_object':
> > > mm/slab.c:4424:8: error: implicit declaration of function 'kasan_reset_tag'
> >
> > That's odd, I don't see that function in the tree at all:
> > $ git grep kasan_reset_tag
> > $
> >
> That is odd.
>
> groeck@server:~/src/linux-stable$ git grep kasan_reset_tag
> mm/slab.c: ptr = kasan_reset_tag(ptr);
> groeck@server:~/src/linux-stable$ git describe
> v4.19.30-212-g4107be0fa04a
>
> This is from commit 06fc4a6d44dce ("kasan, slab: fix conflicts with
> CONFIG_HARDENED_USERCOPY"). Upstream commit is 219667c23c68eb3.
>
> Is your branch different ?
Ah, yes, Sasha dropped those patches earlier today, sorry about that.
Let me push out another -rc git tree so you can sync up properly.
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-21 18:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 16:16 Build failures and crashes in stable queues (3.19, 4.19, 5.0) Guenter Roeck
2019-03-21 16:47 ` Greg Kroah-Hartman
2019-03-21 16:49 ` Greg Kroah-Hartman
2019-03-21 17:38 ` Guenter Roeck
2019-03-21 18:32 ` Greg Kroah-Hartman [this message]
2019-03-21 16:50 ` Greg Kroah-Hartman
2019-03-21 17:28 ` Guenter Roeck
2019-03-21 17:32 ` Greg Kroah-Hartman
2019-03-21 17:52 ` Guenter Roeck
2019-03-21 18:20 ` Guenter Roeck
2019-03-22 11:08 ` Greg Kroah-Hartman
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=20190321183231.GC10586@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.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).