linux-kernel - Re: [PATCH] irqchip: Skip contexts other supervisor in plic

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:   Thu, 24 Oct 2019 00:03:11 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Marc Zyngier <maz@...nel.org>
Cc:     Christoph Hellwig <hch@...radead.org>,
        Palmer Dabbelt <palmer@...ive.com>,
        Paul Walmsley <paul.walmsley@...ive.com>,
        alan.mikhak@...ive.com, linux-kernel@...r.kernel.org,
        linux-riscv@...ts.infradead.org, tglx@...utronix.de,
        jason@...edaemon.net
Subject: Re: [PATCH] irqchip: Skip contexts other supervisor in plic_init()

On Thu, Oct 24, 2019 at 07:51:16AM +0100, Marc Zyngier wrote:
> > > > Will this need to change for RISC-V M-mode Linux support?
> > > > 
> > > > https://lore.kernel.org/linux-riscv/20191017173743.5430-1-hch@lst.de/  
> > > 
> > > Yes.  
> > 
> > For M-mode we'll want to check IRQ_M_EXT above.  So we should just
> > merge this patch ASAP and then for my rebased M-mode series I'll
> > fix the check to do that for the M-Mode case, which is much cleaner
> > than my hack.
> 
> Does this need to be taken as a fix, potentially Cc to stable? Or is
> that 5.5 material?

So I though that the S-mode context were kinda aways to be sorted before
M-mode, but I can't find anything guranteeing it.  So I think this
actually is a fix, and getting this queued up in the next -rc would
really help me with the nommu stuff - otherwise we'd need to take it
through the riscv tree for 5.5 to avoid conflicts.

Btw, here is my:

Reviewed-by: Christoph Hellwig <hch@....de>

for the patch.