From: Parag Warudkar <kernel-stuff@comcast.net>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH] raw1394 : Fix hang on unload
Date: Tue, 08 Feb 2005 11:40:52 -0500 [thread overview]
Message-ID: <1107880852.4154.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1107872677l.6054l.0l@werewolf.able.es>
> I looked also at other 1394 drivers and all have the calls in 'bad' order.
> Sure this ordering has to be reversed or it is correct and is triggering
> other hidden bug ?
>
Quite possibly it's triggering (or is triggered by) some other bug.
There is also a possibility that raw1394.c might be doing something
wrong and gets away with it with the changed ordering. Because dv1394.c
does it the "seemingly-bad" way and I haven't got rmmod to hang while
removing it.
Can anyone answer this - in what cases will generic_delete_inode hang
on __down_failed -> default_wake_function -> __down?
Thanks
Parag
prev parent reply other threads:[~2005-02-08 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 19:41 [PATCH] raw1394 : Fix hang on unload Parag Warudkar
2005-02-07 10:19 ` hugang
2005-02-08 14:24 ` J.A. Magallon
2005-02-08 16:40 ` Parag Warudkar [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=1107880852.4154.6.camel@localhost.localdomain \
--to=kernel-stuff@comcast.net \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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