linux-kernel - Re: "kernel ade access" oops on LoongArch

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <bf0e57db317d7061ecaaf928ce6cf40941b1740c.camel@xry111.site>
Date:   Wed, 15 Feb 2023 19:52:04 +0800
From:   Xi Ruoyao <xry111@...111.site>
To:     Youling Tang <tangyouling@...ngson.cn>
Cc:     Jinyang He <hejinyang@...ngson.cn>, loongarch@...ts.linux.dev,
        Huacai Chen <chenhuacai@...nel.org>,
        WANG Xuerui <kernel@...0n.name>, linux-kernel@...r.kernel.org
Subject: Re: "kernel ade access" oops on LoongArch

On Wed, 2023-02-15 at 16:35 +0800, Xi Ruoyao wrote:
> On Wed, 2023-02-15 at 16:25 +0800, Youling Tang wrote:
> > Can you modify the kernel as follows and test it, so as to avoid
> > possible relationship with the exception table data link position and
> > alignment rules (or use EXCEPTION_TABLE(12))?
> > 
> > --- a/arch/loongarch/kernel/vmlinux.lds.S
> > +++ b/arch/loongarch/kernel/vmlinux.lds.S
> > @@ -4,7 +4,6 @@
> >   #include <asm/thread_info.h>
> > 
> >   #define PAGE_SIZE _PAGE_SIZE
> > -#define RO_EXCEPTION_TABLE_ALIGN       4
> > 
> >   /*
> >    * Put .bss..swapper_pg_dir as the first thing in .bss. This will
> > @@ -54,6 +53,8 @@ SECTIONS
> >          . = ALIGN(PECOFF_SEGMENT_ALIGN);
> >          _etext = .;
> > 
> > +       EXCEPTION_TABLE(16)
> > +
> 
> It seems the kernel refuses to boot after the change, but I'm not
> completely sure: I'm 5 km away from the board and operating it via ssh
> so maybe it's a reboot failure or network failure.  I'll report again in
> the evening.

It was a reboot failure.

Now it has booted successfully, but the stack trace still shows (during
the 25th run of the make test t=... command).

-- 
Xi Ruoyao <xry111@...111.site>
School of Aerospace Science and Technology, Xidian University