Next patch introduces nolock variant of this label,
so we will have new_owner and new_owner_nolock.
assign_new_owner_nolock would be too long there.

Signed-off-by: Kirill Tkhai <ktk...@virtuozzo.com>
---
 kernel/exit.c |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/kernel/exit.c b/kernel/exit.c
index 5c42a9b9c1d7..40f734ed1193 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -430,7 +430,7 @@ void mm_update_next_owner(struct mm_struct *mm)
         */
        list_for_each_entry(c, &p->children, sibling) {
                if (c->mm == mm)
-                       goto assign_new_owner;
+                       goto new_owner;
        }
 
        /*
@@ -438,7 +438,7 @@ void mm_update_next_owner(struct mm_struct *mm)
         */
        list_for_each_entry(c, &p->real_parent->children, sibling) {
                if (c->mm == mm)
-                       goto assign_new_owner;
+                       goto new_owner;
        }
 
        /*
@@ -449,7 +449,7 @@ void mm_update_next_owner(struct mm_struct *mm)
                        continue;
                for_each_thread(g, c) {
                        if (c->mm == mm)
-                               goto assign_new_owner;
+                               goto new_owner;
                        if (c->mm)
                                break;
                }
@@ -463,7 +463,7 @@ void mm_update_next_owner(struct mm_struct *mm)
        mm->owner = NULL;
        return;
 
-assign_new_owner:
+new_owner:
        rcu_read_lock();
        read_unlock(&tasklist_lock);
        BUG_ON(c == p);

Reply via email to