> From: Steve Sistare <steven.sistare@xxxxxxxxxx>
> Sent: Saturday, December 17, 2022 2:51 AM
>
> Track locked_vm per dma struct, and create a new subroutine, both for use
> in a subsequent patch. No functional change.
>
> Fixes: c3cbab24db38 ("vfio/type1: implement interfaces to update vaddr")
> Cc: stable@xxxxxxxxxxxxxxx
> Signed-off-by: Steve Sistare <steven.sistare@xxxxxxxxxx>
Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>, with one nit:
> -static int vfio_lock_acct(struct vfio_dma *dma, long npage, bool async)
> +static int task_lock_acct(struct task_struct *task, struct mm_struct *mm,
> + bool lock_cap, long npage, bool async)
is it more accurate to call it mm_lock_acct() given almost all invocations
in this function are around mm?
