From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Shirish Pargaonkar <shirishpargaonkar@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"linux-fsdevel" <linux-fsdevel@vger.kernel.org>
Subject: Re: wait_even_interruptible_timeout(), signal, spin_lock() = system hang
Date: Sun, 6 Jun 2010 10:00:19 +0200 [thread overview]
Message-ID: <201006061000.19503.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <AANLkTiliRFydAhxH2-Dp1RKuz6sq7vgWIcMvLMi68ftg@mail.gmail.com>
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=16139
for your bug report, please add your address to the CC list in there, thanks!
On piątek, 28 maja 2010 o 18:44:46 Shirish Pargaonkar wrote:
> After this sequence of calls, system hangs (smp, x86 box based with
> .34 kernel), can ping only.
> I have not been able to break in with Alt Sysrq t, working on that
>
> rc = wait_event_interruptible_timeout(ses->server->response_q,
> (midQ->midState != MID_REQUEST_SUBMITTED),
> timeout); if (rc < 0) {
> cFYI(1, ("command 0x%x interrupted", midQ->command));
> return -1;
> }
>
> and when function that invoking function after coming out with ERESTARTSYS
> (I kill the command with Ctrl C) calls
> spin_lock(&GlobalMid_Lock);
>
> system hangs. If I sleep before return -1 (e.g. msleep(1), no hang)
>
> I do not have to use wait_event_interruptible_timeout and no such problems
> with wait_event_timeout, it is only when signal/interrupt is involved, I
> run into this problem
>
> Any pointers/ideas what could be happening, would be really really
> appreciated.
>
> Regards,
>
> Shirish
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Maciej Rutecki
http://www.maciek.unixy.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-06 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 16:44 wait_even_interruptible_timeout(), signal, spin_lock() = system hang Shirish Pargaonkar
2010-06-04 11:51 ` Jeff Layton
2010-06-04 12:13 ` Shirish Pargaonkar
2010-06-05 13:57 ` Shirish Pargaonkar
2010-06-06 8:00 ` Maciej Rutecki [this message]
2010-06-06 14:25 ` Shirish Pargaonkar
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=201006061000.19503.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shirishpargaonkar@gmail.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;
as well as URLs for NNTP newsgroup(s).