From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] loop: potential kernel hang waiting for kthread
Date: Sat, 25 Mar 2006 11:20:42 +0000 [thread overview]
Message-ID: <20060325112041.GA25252@infradead.org> (raw)
In-Reply-To: <20060325014932.GA16485@MAIL.13thfloor.at>
On Sat, Mar 25, 2006 at 02:49:32AM +0100, Herbert Poetzl wrote:
>
> Hi Andrew! Folks!
>
> just stumbled over the following issue with loop_set_fd()
> calling kernel_thread(loop_thread), ignoring the return
> value, even if it is an error, then doing wait_for_completion()
> on the device, which, in beforementioned error case, would
> wait forever (keeping a process stuck in 'D' state)
>
> I can imagine at least three other solutions, but this
> one seemed quite organic to me, YMMV ...
Best thing would be to switch it to the kthread_ API.
prev parent reply other threads:[~2006-03-25 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 1:49 Herbert Poetzl
2006-03-25 11:20 ` Christoph Hellwig [this message]
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=20060325112041.GA25252@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®