Linux Security Modules development
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	<john.hubbard@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] security/tomoyo: convert put_page() to put_user_page*()
Date: Mon, 5 Aug 2019 10:48:48 -0700	[thread overview]
Message-ID: <fa58ec66-dea7-8e00-cc31-426b997eafae@nvidia.com> (raw)
In-Reply-To: <346e5a8e-57fe-b2ac-4069-50a8a83048b5@i-love.sakura.ne.jp>

On 8/5/19 3:01 AM, Tetsuo Handa wrote:
> On 2019/08/05 11:26, john.hubbard@gmail.com wrote:
>> From: John Hubbard <jhubbard@nvidia.com>
>>
>> For pages that were retained via get_user_pages*(), release those pages
>> via the new put_user_page*() routines, instead of via put_page() or
>> release_pages().
>>
>> This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
>> ("mm: introduce put_user_page*(), placeholder versions").
>>
>> Cc: Kentaro Takeda <takedakn@nttdata.co.jp>
>> Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
>> Cc: linux-security-module@vger.kernel.org
>> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> 
> Acked-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> 
> Sending to Andrew Morton means you expect this patch to go via -mm tree, don't you?

Yes, exactly.

thanks,
-- 
John Hubbard
NVIDIA

> Andrew, please take this patch. Thank you.
> 


      reply	other threads:[~2019-08-05 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05  2:26 [PATCH] security/tomoyo: convert put_page() to put_user_page*() john.hubbard
2019-08-05 10:01 ` Tetsuo Handa
2019-08-05 17:48   ` John Hubbard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fa58ec66-dea7-8e00-cc31-426b997eafae@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=john.hubbard@gmail.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox