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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 23 Sep 2021 19:48:11 +0200
From:   Thomas Gleixner <>
To:     "Luck, Tony" <>
Cc:     Fenghua Yu <>, Ingo Molnar <>,
        Borislav Petkov <>,
        Peter Zijlstra <>,
        Andy Lutomirski <>,
        Dave Hansen <>,
        Lu Baolu <>,
        Joerg Roedel <>,
        Josh Poimboeuf <>,
        Dave Jiang <>,
        Jacob Jun Pan <>,
        Ashok Raj <>,
        Ravi V Shankar <>,, x86 <>,
        linux-kernel <>
Subject: Re: [PATCH 5/8] x86/mmu: Add mm-based PASID refcounting

On Thu, Sep 23 2021 at 09:40, Tony Luck wrote:
> On Thu, Sep 23, 2021 at 04:36:50PM +0200, Thomas Gleixner wrote:
>> 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?
> It's a bit messy (surprise).
> There are two reasons to hold a refcount on a PASID
> 1) The process has done a bind on a device that uses PASIDs
> 	This one isn't dependent on Intel.


> 2) A task within a process is using ENQCMD (and thus holds
>    a reference on the PASID because IA32_PASID MSR for this
>    task has the PASID value loaded with the enable bit set).
> 	This is (currently) Intel specific (until others
> 	implement an ENQCMD-like feature to allow apps to
> 	access PASID enabled devices without going through
> 	the OS).

Right, but all it does is to grab another reference on the PASID and if
the task exits it needs to be dropped, right?

So you already added 'has_valid_pasid' to task_struct, which is a
misnomer btw. The meaning of this flag is that the task is actually
using the PASID (in the ENQCMD case written to the MSR) beyond the
purposes of the PASID which is attached to current->mm.

But the information which is important from a pasid resource management
POV is whether the task actually holds a seperate refcount on the PASID
or not. That's completely generic. It does not matter whether the task
uses it to populate the IA32_PASID_MSR or to just keeps it in memory
just because it can. The point is that is holds a refcount.

So we can have a generic interface:

int iommu_pasid_get_task_ref()
        if (current->holds_pasid_ref)
        	return -EYOUGOTONEALREADY;

	if (!has_pasid(current->mm)

	if (!iommu->pasid_get_ref)

	if (iommu->pasid_get_ref())
        current->holds_pasid_ref = true;
        return 0;

Actually letting this return a bool should be good enough, but you get
the idea.

void iommu_pasid_put_task_ref()
        if (!current->holds_pasid_ref)
        current->holds_pasid_ref = false;

Which makes the exception handling in traps.c the real x86/intel
specific muck:

bool fixup_pasid_exception(...)
        /* ENCQMD and future muck */
	if (!per_task_pasid_usage_enabled())
        	return false;
        if (iommu_pasid_get_ref())
        	return false;
        return true;

fpu_write_task_pasid() can just grab the pasid from current->mm->pasid
and be done with it.

The task exit code can just call iommu_pasid_put_task_ref() from the
generic code and not from within x86.

That means you want in Kconfig:


and select that when a IOMMU supporting it is enabled and provide either
the proper protypes or stub functions depending on that.




Powered by blists - more mailing lists