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  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, 23 Sep 2021 16:36:50 +0200
From:   Thomas Gleixner <>
To:     Fenghua Yu <>, Ingo Molnar <>,
        Borislav Petkov <>,
        Peter Zijlstra <>,
        Andy Lutomirski <>,
        Dave Hansen <>,
        Tony Luck <>,
        Lu Baolu <>,
        Joerg Roedel <>,
        Josh Poimboeuf <>,
        Dave Jiang <>,
        Jacob Jun Pan <>,
        Ashok Raj <>,
        Ravi V Shankar <>
Cc:, x86 <>,
        linux-kernel <>,
        Fenghua Yu <>
Subject: Re: [PATCH 5/8] x86/mmu: Add mm-based PASID refcounting

On Mon, Sep 20 2021 at 19:23, Fenghua Yu wrote:
> +void pasid_put(struct task_struct *tsk, struct mm_struct *mm);
> +#else
> +static inline void pasid_put(struct task_struct *tsk, struct mm_struct *mm) { }
> +#endif

This code is again defining that PASID is entirely restricted to
INTEL. It's true, that no other vendor supports this, but PASID is
a non-vendor specific concept.

Sticking this into INTEL code means that any other PASID implementation
has to rip it out again from INTEL code and make it a run time property.

The refcounting issue should be the same for all PASID mechanisms which
attach PASID to a mm. What's INTEL specific about that?

So can we pretty please do that correct right away?



Powered by blists - more mailing lists