Re: Build failures in v3.10-stable-queue, v3.14-stable-queue (+4.1, 4.3, 4.4)

[Sudeep Holla <sudeep.holla@arm.com>]

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]

>
> Ok, as I have no idea here, and don't have an arm64 system to do
> anything with (i.e. test), I'll just leave this alone until someone who
> does care about the architecture comes along with a fix :)
>
-- 
Regards,
Sudeep

[1] https://patchwork.kernel.org/patch/8147861/