[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YxE9Aco0Wz2vBYfF@nvidia.com>
Date: Thu, 1 Sep 2022 20:15:13 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: joao.m.martins@...cle.com
Cc: Alex Williamson <alex.williamson@...hat.com>,
Yishai Hadas <yishaih@...dia.com>, saeedm@...dia.com,
kvm@...r.kernel.org, netdev@...r.kernel.org, kuba@...nel.org,
kevin.tian@...el.com, leonro@...dia.com, maorg@...dia.com,
cohuck@...hat.com
Subject: Re: [PATCH V5 vfio 04/10] vfio: Add an IOVA bitmap support
On Thu, Sep 01, 2022 at 08:39:40PM +0100, joao.m.martins@...cle.com wrote:
> > There's no sanity testing here that the caller provided an iova within
> > the mapped ranged. Thanks,
> >
>
> Much of the bitmap helpers don't check that the offset is within the range
> of the passed ulong array. So I followed the same thinking and the
> caller is /provided/ with the range that the IOVA bitmap covers. The intention
> was minimizing the number of operations given that this function sits on the
> hot path. I can add this extra check.
I wouldn't add sanity testing on these hot paths..
Jason
Powered by blists - more mailing lists