linux-kernel - Re: x86: Use named address spaces in asm/percpu.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAFULd4ZDbg5jFkLzRnEgnVgRwRJa+OG2EvGYUEFQ0RASux2qqg@mail.gmail.com>
Date:   Thu, 25 Apr 2019 14:20:08 +0200
From:   Uros Bizjak <ubizjak@...il.com>
To:     linux-kernel@...r.kernel.org
Cc:     Ingo Molnar <mingo@...nel.org>,
        Matthew Wilcox <willy@...radead.org>
Subject: Re: x86: Use named address spaces in asm/percpu.h

> * Ingo Molnar <mingo@...nel.org> wrote:
>
>> Not all GCC versions seem to like this series:
>>
>>  In file included from arch/x86/mm/tlb.c:12:0:
>>  arch/x86/mm/tlb.c: In function ‘switch_mm_irqs_off’:
>>  ./arch/x86/include/asm/mmu_context.h:210:28: internal compiler error: Segmentation fault
>>   #define switch_mm_irqs_off switch_mm_irqs_off
>>  arch/x86/mm/tlb.c:183:6: note: in expansion of macro ‘switch_mm_irqs_off’
>>   void switch_mm_irqs_off(struct mm_struct *prev, struct mm_struct *next,
>>  Please submit a full bug report,
>>  with preprocessed source if appropriate.
>>  See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions.
>>
>> gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
>
> That's with a 32-bit kernel, config attached.

I am resurrecting an old thread at [1] that tried to introduce named
address spaces in asm/percpu.h. The thread ended with the above
message [2], but no bugreport was ever filled to GCC's bugzilla. Can
please someone from linux  community file a PR with a failing testcase
to GCC Bugzilla, so we (the GCC community) can analyze the problem and
eventually fix the compiler?

[1] https://lkml.org/lkml/2018/9/12/646
[2] https://lkml.org/lkml/2018/9/12/1052
[3] https://gcc.gnu.org/bugs/

Thanks,
Uros.