On 10/8/18 1:56 PM, Jason Gunthorpe wrote:
> On Mon, Oct 08, 2018 at 01:37:35PM -0700, John Hubbard wrote:
>> On 10/8/18 12:42 PM, Jason Gunthorpe wrote:
>>> On Fri, Oct 05, 2018 at 07:49:49PM -0700, john.hubb...@gmail.com wrote:
From: John Hubbard
>> [...]
On 10/8/18 1:56 PM, Jason Gunthorpe wrote:
> On Mon, Oct 08, 2018 at 01:37:35PM -0700, John Hubbard wrote:
>> On 10/8/18 12:42 PM, Jason Gunthorpe wrote:
>>> On Fri, Oct 05, 2018 at 07:49:49PM -0700, john.hubb...@gmail.com wrote:
From: John Hubbard
>> [...]
On Mon, Oct 08, 2018 at 01:37:35PM -0700, John Hubbard wrote:
> On 10/8/18 12:42 PM, Jason Gunthorpe wrote:
> > On Fri, Oct 05, 2018 at 07:49:49PM -0700, john.hubb...@gmail.com wrote:
> >> From: John Hubbard
> [...]
> >> drivers/infiniband/core/umem.c | 7 ---
> >>
On Mon, Oct 08, 2018 at 01:37:35PM -0700, John Hubbard wrote:
> On 10/8/18 12:42 PM, Jason Gunthorpe wrote:
> > On Fri, Oct 05, 2018 at 07:49:49PM -0700, john.hubb...@gmail.com wrote:
> >> From: John Hubbard
> [...]
> >> drivers/infiniband/core/umem.c | 7 ---
> >>
On 10/8/18 12:42 PM, Jason Gunthorpe wrote:
> On Fri, Oct 05, 2018 at 07:49:49PM -0700, john.hubb...@gmail.com wrote:
>> From: John Hubbard
[...]
>> drivers/infiniband/core/umem.c | 7 ---
>> drivers/infiniband/core/umem_odp.c | 2 +-
>>
On 10/8/18 12:42 PM, Jason Gunthorpe wrote:
> On Fri, Oct 05, 2018 at 07:49:49PM -0700, john.hubb...@gmail.com wrote:
>> From: John Hubbard
[...]
>> drivers/infiniband/core/umem.c | 7 ---
>> drivers/infiniband/core/umem_odp.c | 2 +-
>>
On Fri, Oct 05, 2018 at 07:49:49PM -0700, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For code that retains pages via get_user_pages*(),
> release those pages via the new put_user_page(), or
> put_user_pages*(), instead of put_page()
>
> This prepares for eventually fixing the
On Fri, Oct 05, 2018 at 07:49:49PM -0700, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For code that retains pages via get_user_pages*(),
> release those pages via the new put_user_page(), or
> put_user_pages*(), instead of put_page()
>
> This prepares for eventually fixing the
On Fri 05-10-18 19:49:49, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For code that retains pages via get_user_pages*(),
> release those pages via the new put_user_page(), or
> put_user_pages*(), instead of put_page()
>
> This prepares for eventually fixing the problem described
> in
On Fri 05-10-18 19:49:49, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For code that retains pages via get_user_pages*(),
> release those pages via the new put_user_page(), or
> put_user_pages*(), instead of put_page()
>
> This prepares for eventually fixing the problem described
> in
From: John Hubbard
For code that retains pages via get_user_pages*(),
release those pages via the new put_user_page(), or
put_user_pages*(), instead of put_page()
This prepares for eventually fixing the problem described
in [1], and is following a plan listed in [2], [3], [4].
[1]
From: John Hubbard
For code that retains pages via get_user_pages*(),
release those pages via the new put_user_page(), or
put_user_pages*(), instead of put_page()
This prepares for eventually fixing the problem described
in [1], and is following a plan listed in [2], [3], [4].
[1]
12 matches
Mail list logo