From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: <akpm@linux-foundation.org>
Cc: <penguin-kernel@I-love.SAKURA.ne.jp>,
<linux-kernel@vger.kernel.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>, <mhocko@kernel.org>,
<linux-mm@kvack.org>, <hpa@zytor.com>, <chris@chris-wilson.co.uk>,
<hch@lst.de>, <mingo@elte.hu>, <jszhang@marvell.com>,
<joelaf@google.com>, <joaodias@google.com>, <willy@infradead.org>,
<tglx@linutronix.de>
Subject: [PATCH 3/4] kernel/fork: use vfree() instead of vfree_atomic() to free thread stack
Date: Thu, 30 Mar 2017 13:27:18 +0300 [thread overview]
Message-ID: <20170330102719.13119-3-aryabinin@virtuozzo.com> (raw)
In-Reply-To: <20170330102719.13119-1-aryabinin@virtuozzo.com>
vfree() can be used in any atomic context now, thus there is no point
in using vfree_atomic().
This reverts commit 0f110a9b956c ("kernel/fork: use vfree_atomic()
to free thread stack")
Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
---
kernel/fork.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index a9f642d..084e6a4 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -241,7 +241,7 @@ static inline void free_thread_stack(struct task_struct *tsk)
}
local_irq_restore(flags);
- vfree_atomic(tsk->stack);
+ vfree(tsk->stack);
return;
}
#endif
--
2.10.2
WARNING: multiple messages have this Message-ID (diff)
From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: akpm@linux-foundation.org
Cc: penguin-kernel@I-love.SAKURA.ne.jp, linux-kernel@vger.kernel.org,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
mhocko@kernel.org, linux-mm@kvack.org, hpa@zytor.com,
chris@chris-wilson.co.uk, hch@lst.de, mingo@elte.hu,
jszhang@marvell.com, joelaf@google.com, joaodias@google.com,
willy@infradead.org, tglx@linutronix.de
Subject: [PATCH 3/4] kernel/fork: use vfree() instead of vfree_atomic() to free thread stack
Date: Thu, 30 Mar 2017 13:27:18 +0300 [thread overview]
Message-ID: <20170330102719.13119-3-aryabinin@virtuozzo.com> (raw)
In-Reply-To: <20170330102719.13119-1-aryabinin@virtuozzo.com>
vfree() can be used in any atomic context now, thus there is no point
in using vfree_atomic().
This reverts commit 0f110a9b956c ("kernel/fork: use vfree_atomic()
to free thread stack")
Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
---
kernel/fork.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index a9f642d..084e6a4 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -241,7 +241,7 @@ static inline void free_thread_stack(struct task_struct *tsk)
}
local_irq_restore(flags);
- vfree_atomic(tsk->stack);
+ vfree(tsk->stack);
return;
}
#endif
--
2.10.2
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-03-30 10:26 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 10:27 [PATCH 1/4] mm/vmalloc: allow to call vfree() in atomic context Andrey Ryabinin
2017-03-30 10:27 ` Andrey Ryabinin
2017-03-30 10:27 ` Andrey Ryabinin
2017-03-30 10:27 ` [PATCH 2/4] x86/ldt: use vfree() instead of vfree_atomic() Andrey Ryabinin
2017-03-30 10:27 ` Andrey Ryabinin
2017-03-31 8:05 ` Thomas Gleixner
2017-03-31 8:05 ` Thomas Gleixner
2017-03-30 10:27 ` Andrey Ryabinin [this message]
2017-03-30 10:27 ` [PATCH 3/4] kernel/fork: use vfree() instead of vfree_atomic() to free thread stack Andrey Ryabinin
2017-03-30 10:27 ` [PATCH 4/4] mm/vmalloc: remove vfree_atomic() Andrey Ryabinin
2017-03-30 10:27 ` Andrey Ryabinin
2017-03-30 17:18 ` Matthew Wilcox
2017-03-30 17:18 ` Matthew Wilcox
2017-03-30 15:27 ` Andrey Ryabinin
2017-03-30 15:27 ` Andrey Ryabinin
2017-04-04 9:40 ` Michal Hocko
2017-04-04 9:40 ` Michal Hocko
2017-03-30 12:00 ` [PATCH 1/4] mm/vmalloc: allow to call vfree() in atomic context Thomas Hellstrom
2017-03-30 12:00 ` Thomas Hellstrom
2017-03-30 12:00 ` Thomas Hellstrom
2017-03-30 14:48 ` Andrey Ryabinin
2017-03-30 14:48 ` Andrey Ryabinin
2017-03-30 14:48 ` Andrey Ryabinin
2017-03-30 15:04 ` Thomas Hellstrom
2017-03-30 15:04 ` Thomas Hellstrom
2017-03-30 15:04 ` Thomas Hellstrom
2017-04-04 9:41 ` Michal Hocko
2017-04-04 9:41 ` Michal Hocko
2017-04-04 9:49 ` Thomas Hellstrom
2017-04-04 9:49 ` Thomas Hellstrom
2017-04-04 9:49 ` Thomas Hellstrom
2017-04-05 10:31 ` Andrey Ryabinin
2017-04-05 10:31 ` Andrey Ryabinin
2017-04-05 10:31 ` Andrey Ryabinin
2017-04-05 10:42 ` Michal Hocko
2017-04-05 10:42 ` Michal Hocko
2017-04-05 11:42 ` Vlastimil Babka
2017-04-05 11:42 ` Vlastimil Babka
2017-04-05 12:14 ` Michal Hocko
2017-04-05 12:14 ` Michal Hocko
2017-03-30 22:22 ` Andrew Morton
2017-03-30 22:22 ` Andrew Morton
2017-03-30 22:22 ` Andrew Morton
2017-03-31 7:12 ` Joel Fernandes
2017-03-31 7:12 ` Joel Fernandes
2017-03-31 9:26 ` Andrey Ryabinin
2017-03-31 9:26 ` Andrey Ryabinin
2017-03-31 9:26 ` Andrey Ryabinin
2017-04-04 9:36 ` Michal Hocko
2017-04-04 9:36 ` Michal Hocko
2017-04-04 9:38 ` Michal Hocko
2017-04-04 9:38 ` Michal Hocko
2017-04-12 12:49 ` [PATCH v2 0/5] " Andrey Ryabinin
2017-04-12 12:49 ` Andrey Ryabinin
2017-04-12 12:49 ` [PATCH v2 1/5] mm/vmalloc: " Andrey Ryabinin
2017-04-12 12:49 ` Andrey Ryabinin
2017-04-12 12:49 ` Andrey Ryabinin
2017-04-12 12:49 ` [PATCH v2 2/5] x86/ldt: use vfree() instead of vfree_atomic() Andrey Ryabinin
2017-04-12 12:49 ` Andrey Ryabinin
2017-04-12 12:49 ` [PATCH v2 3/5] kernel/fork: use vfree() instead of vfree_atomic() to free thread stack Andrey Ryabinin
2017-04-12 12:49 ` Andrey Ryabinin
2017-04-12 12:49 ` [PATCH v2 4/5] mm/vmalloc: remove vfree_atomic() Andrey Ryabinin
2017-04-12 12:49 ` Andrey Ryabinin
2017-04-12 12:49 ` [PATCH v2 5/5] mm/vmalloc: Don't spawn workers if somebody already purging Andrey Ryabinin
2017-04-12 12:49 ` Andrey Ryabinin
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=20170330102719.13119-3-aryabinin@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=joaodias@google.com \
--cc=joelaf@google.com \
--cc=jszhang@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mingo@elte.hu \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.