From: Chanho Min <chanho.min@lge.com>
To: Russell King <linux@arm.linux.org.uk>,
Jon Medhurst <tixy@linaro.org>, Will Deacon <will.deacon@arm.com>,
Taras Kondratiuk <taras.kondratiuk@linaro.org>,
Olof Johansson <olof@lixom.net>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Gunho Lee <gunho.lee@lge.com>,
HyoJun Im <hyojun.im@lge.com>,
Jongsung Kim <neidhard.kim@lge.com>,
Chanho Min <chanho.min@lge.com>
Subject: [PATCH] ARM: cacheflush: disallow pending signals during cacheflush
Date: Thu, 13 Nov 2014 16:29:53 +0900 [thread overview]
Message-ID: <1415863793-6219-1-git-send-email-chanho.min@lge.com> (raw)
Since commit 28256d612726 ("ARM: cacheflush: split user cache-flushing
into interruptible chunks"), cacheflush can be interrupted by signal.
But, cacheflush doesn't resume from where we left off if process has
user-defined signal handlers. It returns -EINTR then cacheflush
should be re-invoked from the start of address until cache-flushing
of whole address ranges is completed (restart_syscall isn't available
in userspace). It may cause regression. So I suggest to disallow
pending signals during cacheflush.
This partially reverts commit 28256d612726a28a8b9d3c49f2b74198c4423d6a.
Signed-off-by: Chanho Min <chanho.min@lge.com>
---
arch/arm/kernel/traps.c | 19 -------------------
1 file changed, 19 deletions(-)
diff --git a/arch/arm/kernel/traps.c b/arch/arm/kernel/traps.c
index abd2fc0..275e086 100644
--- a/arch/arm/kernel/traps.c
+++ b/arch/arm/kernel/traps.c
@@ -521,25 +521,6 @@ __do_cache_op(unsigned long start, unsigned long end)
do {
unsigned long chunk = min(PAGE_SIZE, end - start);
- if (signal_pending(current)) {
- struct thread_info *ti = current_thread_info();
-
- ti->restart_block = (struct restart_block) {
- .fn = do_cache_op_restart,
- };
-
- ti->arm_restart_block = (struct arm_restart_block) {
- {
- .cache = {
- .start = start,
- .end = end,
- },
- },
- };
-
- return -ERESTART_RESTARTBLOCK;
- }
-
ret = flush_cache_user_range(start, start + chunk);
if (ret)
return ret;
--
1.7.9.5
next reply other threads:[~2014-11-13 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 7:29 Chanho Min [this message]
2014-11-13 11:26 ` Will Deacon
2014-11-13 17:39 ` Peter Maydell
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=1415863793-6219-1-git-send-email-chanho.min@lge.com \
--to=chanho.min@lge.com \
--cc=gunho.lee@lge.com \
--cc=hyojun.im@lge.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=neidhard.kim@lge.com \
--cc=olof@lixom.net \
--cc=taras.kondratiuk@linaro.org \
--cc=tixy@linaro.org \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®