On Thu, May 13, 2021 at 10:47 AM Andrey Grodzovsky
wrote:
>
>
>
> On 2021-05-12 4:50 p.m., Alex Deucher wrote:
> > On Wed, May 12, 2021 at 4:30 PM Andrey Grodzovsky
> > wrote:
> >>
> >>
> >>
> >> On 2021-05-12 4:17 p.m., Alex Deucher wrote:
> >>> On Wed, May 12, 2021 at 10:27 AM Andrey
On 2021-05-12 4:50 p.m., Alex Deucher wrote:
On Wed, May 12, 2021 at 4:30 PM Andrey Grodzovsky
wrote:
On 2021-05-12 4:17 p.m., Alex Deucher wrote:
On Wed, May 12, 2021 at 10:27 AM Andrey Grodzovsky
wrote:
This should prevent writing to memory or IO ranges possibly
already allocated
On Wed, May 12, 2021 at 4:30 PM Andrey Grodzovsky
wrote:
>
>
>
> On 2021-05-12 4:17 p.m., Alex Deucher wrote:
> > On Wed, May 12, 2021 at 10:27 AM Andrey Grodzovsky
> > wrote:
> >>
> >> This should prevent writing to memory or IO ranges possibly
> >> already allocated for other uses after our
On 2021-05-12 4:17 p.m., Alex Deucher wrote:
On Wed, May 12, 2021 at 10:27 AM Andrey Grodzovsky
wrote:
This should prevent writing to memory or IO ranges possibly
already allocated for other uses after our device is removed.
v5:
Protect more places wher memcopy_to/form_io takes place
On Wed, May 12, 2021 at 10:27 AM Andrey Grodzovsky
wrote:
>
> This should prevent writing to memory or IO ranges possibly
> already allocated for other uses after our device is removed.
>
> v5:
> Protect more places wher memcopy_to/form_io takes place
where
> Protect IB submissions
>
> v6:
This should prevent writing to memory or IO ranges possibly
already allocated for other uses after our device is removed.
v5:
Protect more places wher memcopy_to/form_io takes place
Protect IB submissions
v6: Switch to !drm_dev_enter instead of scoping entire code
with brackets.
v7:
Drop guard
