From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Will Deacon <will.deacon@arm.com>,
stable <stable@vger.kernel.org>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: Build failures in v3.10-stable-queue, v3.14-stable-queue (+4.1, 4.3, 4.4)
Date: Sun, 31 Jan 2016 11:22:36 -0800 [thread overview]
Message-ID: <20160131192236.GF23698@kroah.com> (raw)
In-Reply-To: <56AA389A.3080108@arm.com>
On Thu, Jan 28, 2016 at 03:49:46PM +0000, Sudeep Holla wrote:
>
>
> On 27/01/16 17:49, Greg Kroah-Hartman wrote:
> >On Wed, Jan 27, 2016 at 09:16:12AM -0800, Guenter Roeck wrote:
> >>On 01/27/2016 08:34 AM, Guenter Roeck wrote:
> >>>On 01/27/2016 04:22 AM, Guenter Roeck wrote:
> >>>[ ... ]
> >>>
> >>>>---
> >>>>mn10300 (v3.10, v3.14):
> >>>>
> >>>>kernel/uid16.c:19:1: error: unknown type name 'old_uid_t'
> >>>>kernel/uid16.c:19:1: error: unknown type name 'old_gid_t'
> >>>>ipc/util.c:609:2: error: 'old_uid_t' undeclared
> >>>>
> >>>>and other similar errors. Requires c86576ea114a ("mn10300: Select CONFIG_HAVE_UID16
> >>>>to fix build failure"). Results in minor easy to resolve conflict in v3.10.y (I didn't
> >>>>check v3.14.y). Let me know if you need a backport.
> >>>>
> >>>4.1 and 4.3 are also affected by this problem.
> >>>
> >>>---
> >>>arm64 (4.1, 4.3):
> >>>
> >>>allmodconfig core dumps (oops). I'll need to look into that one.
> >>>
> >>
> >>Two patches are culprits here:
> >>
> >>- 'recordmcount: arm64: Replace the ignored mcount call into nop' causes the crash.
> >> It is not the C compiler. Maybe some other patch to recordmcount is missing.
> >>
>
> This bug is due the endianness mix at-least in my build setup and commit
> c84da8b9ad37 ("recordmcount: Fix endianness handling bug for
> nop_mcount") seems to fix it for me.
>
> It's already marked for stable and I see that there are quite a few
> patches queued for stable in scripts/recordmcount.[ch]. But I see Greg
> has already pointed this out in the NOTE in his initial "[PATCH 4.1 000/127]
> 4.1.17-stable review" email.
>
> >>- 'arm64: mm: use correct mapping granularity under DEBUG_RODATA' uses SWAPPER_BLOCK_SIZE
> >> which is not defined in 4.3. This causes a build failure in 4.3 after reverting the above.
> >> I didn't check 4.1.
>
> Ardb already posted a fix for this [1]
Thanks, I should have this all straightened out now...
greg k-h
next prev parent reply other threads:[~2016-01-31 19:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 12:22 Build failures in v3.10-stable-queue, v3.14-stable-queue Guenter Roeck
2016-01-27 12:31 ` Will Deacon
2016-01-27 17:39 ` Greg Kroah-Hartman
2016-01-27 13:27 ` Nicolas Dichtel
2016-01-27 15:48 ` Greg Kroah-Hartman
2016-01-27 16:34 ` Build failures in v3.10-stable-queue, v3.14-stable-queue (+4.1, 4.3, 4.4) Guenter Roeck
2016-01-27 16:37 ` Will Deacon
2016-01-27 17:16 ` Guenter Roeck
2016-01-27 17:49 ` Greg Kroah-Hartman
2016-01-28 9:38 ` Will Deacon
2016-01-28 15:49 ` Sudeep Holla
2016-01-31 19:22 ` Greg Kroah-Hartman [this message]
2016-01-27 17:20 ` Build failures in v3.10-stable-queue, v3.14-stable-queue Greg Kroah-Hartman
2016-01-27 17:42 ` 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=20160131192236.GF23698@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=nicolas.dichtel@6wind.com \
--cc=stable@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will.deacon@arm.com \
/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).