From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: [patch 4/4] firewire: warn on unfinished transactions during card removal
Date: Sat, 12 Jul 2008 14:51:18 +0200 (CEST) [thread overview]
Message-ID: <tkrat.c73716c44f10b8fb@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.3186168349c88b15@s5r6.in-berlin.de>
After card->done and card->work are completed, any remaining pending
request would be a bug. We cannot safely complete a transaction at
that point anymore.
IOW card users must not drop their last fw_card reference (usually
indirect references through fw_device references) before their last
outbound transaction through that card was finished.
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
drivers/firewire/fw-card.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/drivers/firewire/fw-card.c
===================================================================
--- linux.orig/drivers/firewire/fw-card.c
+++ linux/drivers/firewire/fw-card.c
@@ -539,7 +539,7 @@ fw_core_remove_card(struct fw_card *card
wait_for_completion(&card->done);
cancel_delayed_work_sync(&card->work);
- fw_flush_transactions(card);
+ WARN_ON(!list_empty(&card->transaction_list));
del_timer_sync(&card->flush_timer);
}
EXPORT_SYMBOL(fw_core_remove_card);
--
Stefan Richter
-=====-==--- -=== -==--
http://arcgraph.de/sr/
prev parent reply other threads:[~2008-07-12 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 12:48 [patch 0/4] firewire: keeping accesses to fw_transaction in check Stefan Richter
2008-07-12 12:49 ` [patch 1/4] firewire: fix race of bus reset with request transmission Stefan Richter
2008-07-12 12:59 ` Stefan Richter
2008-07-12 12:50 ` [patch 2/4] firewire: fully initialize fw_transaction before marking it pending Stefan Richter
2008-07-12 12:50 ` [patch 3/4] firewire: small fw_fill_request cleanup Stefan Richter
2008-07-12 12:51 ` Stefan Richter [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=tkrat.c73716c44f10b8fb@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--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
all inboxes | Powered by JetHome®