linux-kernel - Re: [PATCH] Revert "MIPS: make userspace mapping young by default".

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: <20210423145131.GA11112@alpha.franken.de>
Date:   Fri, 23 Apr 2021 16:51:31 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Zhou Yanjie <zhouyanjie@...yeetech.com>
Cc:     Huang Pei <huangpei@...ngson.cn>, linux-mips@...r.kernel.org,
        linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
        paul.burton@...s.com, paul@...pouillou.net, siyanteng@...ngson.cn,
        ira.weiny@...el.com, yangtiezhu@...ngson.cn, jun.jiang@...enic.com,
        dongsheng.qiu@...enic.com, aric.pzqi@...enic.com,
        rick.tyliu@...enic.com, sernia.zhou@...mail.com,
        sihui.liu@...enic.com
Subject: Re: [PATCH] Revert "MIPS: make userspace mapping young by default".

On Tue, Apr 20, 2021 at 10:03:01PM +0800, Zhou Yanjie wrote:
> Sorry for my carelessness, the log in the previous email was wrong, please
> check the log in this email.
> 
> [   53.684067] --- pte 1 = 07698685

any chance to print the virtual address to this pte ?

> [   53.687376] --- pte 3 = 07698685
> [   53.737175] --- pte 1 = 07699685
> [   53.740412] --- pte 3 = 07699685
> [   53.744064] --- pte 1 = 076c3685
> [..]

could you print PTE, which faults ? And what is mapped there ?


so far I haven't seen any ill-effects of the (bisected ?) patch.
The problem I have with reverting is that IMHO we re-introduce the bug,
which this patch fixed.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]