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]

Date:   Wed, 15 Feb 2023 16:07:15 +0800
From:   Xi Ruoyao <xry111@...111.site>
To:     Jinyang He <hejinyang@...ngson.cn>,
        Youling Tang <tangyouling@...ngson.cn>
Cc:     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 15:51 +0800, Jinyang He wrote:

> > There was a build error in make check, so only tst-mallocfork3-
> > malloc-check was tested separately.
> > 
> > # make test t=malloc/tst-mallocfork3-malloc-check
> > make[2]: 离开目录“/home/loongson/glibc/malloc”
> > PASS: malloc/tst-mallocfork3-malloc-check
> > original exit status 0
> > info: signals received during fork: 301
> > info: signals received during free: 1693
> > info: signals received during malloc: 119
> > make[1]: 离开目录“/home/loongson/glibc”
> > 
> > A total of five tests are PASS, and the serial port does not display
> > CallTrace.
> > 
> > Youling.
> > 
> I had test it by using the cmd "while true..." Ruoyao gave on
> 
> Loongson-3A5000, CLFS 7.1, 6.2-rc8 kernel with those patches and
> 
> 6.2-rc7 kernel form loongson-next. No calltrace displayed, either.

Hmm... I've read the code for a while and I couldn't see how it could
end up accessing a bad address too.  Maybe my hardware or compiler is
really faulty?


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