From: Jens Axboe <axboe@kernel.dk>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64: add support for TIF_NOTIFY_SIGNAL
Date: Thu, 28 Jan 2021 22:45:51 +0000 [thread overview]
Message-ID: <61a8ba7e-1591-4c80-ccd8-6b820e3482d6@kernel.dk> (raw)
In-Reply-To: <d3a2aa1e-0fae-1d3f-519f-d32adc608c38@kernel.dk>
On 1/28/21 3:42 PM, Jens Axboe wrote:
> On 1/28/21 12:22 PM, John Paul Adrian Glaubitz wrote:
>> Hi Jens!
>>
>> On 1/20/21 5:08 PM, Jens Axboe wrote:
>>>> This change broke the hpsa driver on my RX-2600 ia64 workstation in the sense that the
>>>> driver no longer loads and hence hard disks are no longer recognized.
>>>
>>> What does "no longer loads" mean? Does it hang?
>>>
>>>> Any idea what could be wrong?
>>>
>>> Can you try current -git? There's a task_work related fix in there which is
>>> related to this series, maybe that's it...
>>
>> I just tried Linus' current tree (ge5ff2cb9cf67) and the problem still persists.
>
> Funky... Can you see if this helps?
Actually, this one might be better.
diff --git a/arch/ia64/kernel/signal.c b/arch/ia64/kernel/signal.c
index e67b22fc3c60..22d825f26668 100644
--- a/arch/ia64/kernel/signal.c
+++ b/arch/ia64/kernel/signal.c
@@ -340,7 +340,7 @@ ia64_do_signal (struct sigscratch *scr, long in_syscall)
* This only loops in the rare cases of handle_signal() failing, in which case we
* need to push through a forced SIGSEGV.
*/
- while (1) {
+ do {
get_signal(&ksig);
/*
@@ -358,9 +358,6 @@ ia64_do_signal (struct sigscratch *scr, long in_syscall)
*/
restart = 0;
- if (ksig.sig <= 0)
- break;
-
if (unlikely(restart)) {
switch (errno) {
case ERESTART_RESTARTBLOCK:
@@ -387,7 +384,7 @@ ia64_do_signal (struct sigscratch *scr, long in_syscall)
*/
if (handle_signal(&ksig, scr))
return;
- }
+ } while (ksig.sig > 0);
/* Did we come from a system call? */
if (restart) {
--
Jens Axboe
next prev parent reply other threads:[~2021-01-28 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 16:15 [PATCH] ia64: add support for TIF_NOTIFY_SIGNAL Jens Axboe
2020-11-05 16:18 ` Jens Axboe
2021-01-19 1:50 ` John Paul Adrian Glaubitz
2021-01-20 16:08 ` Jens Axboe
2021-01-20 16:09 ` John Paul Adrian Glaubitz
2021-01-20 16:12 ` Jens Axboe
2021-01-28 22:42 ` Jens Axboe
2021-01-28 22:45 ` Jens Axboe [this message]
2021-01-28 22:51 ` John Paul Adrian Glaubitz
2021-01-28 22:56 ` Jens Axboe
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=61a8ba7e-1591-4c80-ccd8-6b820e3482d6@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox