From: Jens Axboe <axboe@suse.de>
To: Nate Eldredge <neldredge@hmc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.2-ac3: loop threads in D state
Date: Sun, 25 Feb 2001 23:39:57 +0100 [thread overview]
Message-ID: <20010225233957.R7830@suse.de> (raw)
In-Reply-To: <15000.9242.867644.29523@mercury.st.hmc.edu> <15001.34865.543658.820963@mercury.st.hmc.edu>
In-Reply-To: <15001.34865.543658.820963@mercury.st.hmc.edu>; from neldredge@hmc.edu on Sun, Feb 25, 2001 at 02:33:21PM -0800
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Sun, Feb 25 2001, Nate Eldredge wrote:
> Nate Eldredge writes:
> > Kernel 2.4.2-ac3.
> >
> > FLAGS UID PID PPID PRI NI SIZE RSS WCHAN STA TTY TIME COMMAND
> > 40 0 425 1 -1 -20 0 0 down DW< ? 0:00 (loop0)
>
> It looks like this has been addressed in the thread "242-ac3 loop
> bug". Jens Axboe posted a patch, but the list archive I'm reading
> mangled it. Jens, could you make this patch available somewhere, or
> at least email me a copy? (If it's going in an upcoming -ac patch,
> then don't bother; I can wait until then.)
Patch is here, I haven't checked whether Alan put it in ac4 yet (I
did cc him, but noone knows for sure :-).
--
Jens Axboe
[-- Attachment #2: loop_sig-1 --]
[-- Type: text/plain, Size: 546 bytes --]
--- drivers/block/loop.c~ Sat Feb 24 23:08:38 2001
+++ drivers/block/loop.c Sat Feb 24 23:11:13 2001
@@ -507,7 +507,7 @@
sprintf(current->comm, "loop%d", lo->lo_number);
spin_lock_irq(¤t->sigmask_lock);
- siginitsetinv(¤t->blocked, sigmask(SIGKILL));
+ sigfillset(¤t->blocked);
flush_signals(current);
spin_unlock_irq(¤t->sigmask_lock);
@@ -525,7 +525,7 @@
up(&lo->lo_sem);
for (;;) {
- down(&lo->lo_bh_mutex);
+ down_interruptible(&lo->lo_bh_mutex);
if (!atomic_read(&lo->lo_pending))
break;
next prev parent reply other threads:[~2001-02-25 22:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-24 21:14 2.4.2-ac3: loop threads in D state Nate Eldredge
2001-02-25 22:33 ` Nate Eldredge
2001-02-25 22:39 ` Jens Axboe [this message]
2001-02-25 22:48 ` Alexander Viro
2001-02-26 0:24 ` Jens Axboe
2001-02-26 0:29 ` Alexander Viro
2001-02-26 0:33 ` Jens Axboe
2001-02-26 0:36 ` Alexander Viro
2001-02-26 0:39 ` Jens Axboe
2001-02-26 1:42 ` Alexander Viro
2001-02-26 0:40 ` Alexander Viro
2001-02-26 0:48 ` Jens Axboe
2001-02-26 0:53 ` Alexander Viro
2001-02-26 0:54 ` Jens Axboe
2001-02-27 19:11 ` Nate Eldredge
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=20010225233957.R7830@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neldredge@hmc.edu \
/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.