linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: <akpm@linux-foundation.org>, <mike.kravetz@oracle.com>,
	<naoya.horiguchi@nec.com>
Cc: <ying.huang@intel.com>, <hch@lst.de>, <dhowells@redhat.com>,
	<cl@linux.com>, <david@redhat.com>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>, <linmiaohe@huawei.com>
Subject: [PATCH v2 1/4] mm/migration: reduce the rcu lock duration
Date: Mon, 25 Apr 2022 21:27:20 +0800	[thread overview]
Message-ID: <20220425132723.34824-2-linmiaohe@huawei.com> (raw)
In-Reply-To: <20220425132723.34824-1-linmiaohe@huawei.com>

rcu_read_lock is required by grabbing the task refcount but it's not
needed for ptrace_may_access. So we could release the rcu lock after
task refcount is successfully grabbed to reduce the rcu holding time.

Reviewed-by: Muchun Song <songmuchun@bytedance.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Cc: Huang Ying <ying.huang@intel.com>
Cc: David Howells <dhowells@redhat.com>
Cc: Christoph Lameter <cl@linux.com>
---
 mm/migrate.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/mm/migrate.c b/mm/migrate.c
index b2678279eb43..b779646665fe 100644
--- a/mm/migrate.c
+++ b/mm/migrate.c
@@ -1902,17 +1902,16 @@ static struct mm_struct *find_mm_struct(pid_t pid, nodemask_t *mem_nodes)
 		return ERR_PTR(-ESRCH);
 	}
 	get_task_struct(task);
+	rcu_read_unlock();
 
 	/*
 	 * Check if this process has the right to modify the specified
 	 * process. Use the regular "ptrace_may_access()" checks.
 	 */
 	if (!ptrace_may_access(task, PTRACE_MODE_READ_REALCREDS)) {
-		rcu_read_unlock();
 		mm = ERR_PTR(-EPERM);
 		goto out;
 	}
-	rcu_read_unlock();
 
 	mm = ERR_PTR(security_task_movememory(task));
 	if (IS_ERR(mm))
-- 
2.23.0



  reply	other threads:[~2022-04-25 13:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 13:27 [PATCH v2 0/4] A few cleanup and fixup patches for migration Miaohe Lin
2022-04-25 13:27 ` Miaohe Lin [this message]
2022-04-29  9:54   ` [PATCH v2 1/4] mm/migration: reduce the rcu lock duration David Hildenbrand
2022-05-09  3:14     ` Miaohe Lin
2022-05-24 12:36     ` Miaohe Lin
2022-05-06  3:23   ` ying.huang
2022-05-09  3:20     ` Miaohe Lin
2022-04-25 13:27 ` [PATCH v2 2/4] mm/migration: remove unneeded lock page and PageMovable check Miaohe Lin
2022-04-29 10:07   ` David Hildenbrand
2022-05-09  8:51     ` Miaohe Lin
2022-05-11 15:23       ` David Hildenbrand
2022-05-12  2:25         ` Miaohe Lin
2022-05-12  7:10           ` David Hildenbrand
2022-05-12 13:26             ` Miaohe Lin
2022-05-12 16:50               ` David Hildenbrand
2022-05-16  2:44                 ` Miaohe Lin
2022-05-31 11:59                   ` David Hildenbrand
2022-05-31 12:37                     ` Miaohe Lin
2022-06-01 10:31                       ` David Hildenbrand
2022-06-02  7:40                         ` Miaohe Lin
2022-06-02  8:47                           ` David Hildenbrand
2022-06-07  2:20                             ` Miaohe Lin
2022-06-08 10:05                               ` David Hildenbrand
2022-06-08 13:31                                 ` Miaohe Lin
2022-05-24 12:47                 ` Miaohe Lin
2022-04-25 13:27 ` [PATCH v2 3/4] mm/migration: return errno when isolate_huge_page failed Miaohe Lin
2022-04-29 10:08   ` David Hildenbrand
2022-05-09  8:03     ` Miaohe Lin
2022-04-29 11:36   ` Muchun Song
2022-05-09  3:23     ` Miaohe Lin
2022-05-09  4:21       ` Muchun Song
2022-05-09  7:51         ` Miaohe Lin
2022-04-25 13:27 ` [PATCH v2 4/4] mm/migration: fix potential pte_unmap on an not mapped pte Miaohe Lin
2022-04-29  9:48   ` David Hildenbrand

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=20220425132723.34824-2-linmiaohe@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=david@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=naoya.horiguchi@nec.com \
    --cc=ying.huang@intel.com \
    /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