From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Yong Zhang <yong.zhang0@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
Thomas Gleixner <tglx@linutronix.de>,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: lockdep false positive? -- firewire-core transaction timer vs. scsi-core host lock
Date: Wed, 18 Aug 2010 14:50:25 +0200 (CEST) [thread overview]
Message-ID: <tkrat.2aa42a952e4df4b1@s5r6.in-berlin.de> (raw)
In-Reply-To: <4C6BA757.7050108@ladisch.de>
Clemens Ladisch wrote:
> firewire: core: do not use del_timer_sync() in interrupt context
>
> Because we might be in interrupt context, replace del_timer_sync() with
> del_timer().
OK. And thanks for the pointers into the locking guide.
> If the timer is already running, we know that it will
> clean up the transaction, so we do not need to do any further processing
> in the normal transaction handler.
>
> Many thanks to Yong Zhang for diagnosing this.
>
> Reported-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> Signed-off-by: Clemens Ladisch <clemens@ladisch.de>
> ---
> drivers/firewire/core-transaction.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> --- a/drivers/firewire/core-transaction.c
> +++ b/drivers/firewire/core-transaction.c
> @@ -81,6 +81,8 @@ static int close_transaction(struct fw_transaction *transaction,
> spin_lock_irqsave(&card->lock, flags);
> list_for_each_entry(t, &card->transaction_list, link) {
> if (t == transaction) {
> + if (!del_timer(&t->split_timeout_timer))
> + goto timed_out;
+ if (!del_timer(&t->split_timeout_timer)) {
+ spin_unlock_irqrestore(&card->lock, flags);
+ goto timed_out;
+ }
> list_del_init(&t->link);
> card->tlabel_mask &= ~(1ULL << t->tlabel);
> break;
> @@ -89,11 +91,11 @@ static int close_transaction(struct fw_transaction *transaction,
> spin_unlock_irqrestore(&card->lock, flags);
>
> if (&t->link != &card->transaction_list) {
> - del_timer_sync(&t->split_timeout_timer);
> t->callback(card, rcode, NULL, 0, t->callback_data);
> return 0;
> }
>
> +timed_out:
> return -ENOENT;
> }
>
> @@ -921,6 +923,8 @@ void fw_core_handle_response(struct fw_card *card, struct fw_packet *p)
> spin_lock_irqsave(&card->lock, flags);
> list_for_each_entry(t, &card->transaction_list, link) {
> if (t->node_id == source && t->tlabel == tlabel) {
> + if (!del_timer(&t->split_timeout_timer))
> + goto timed_out;
Ditto.
> list_del_init(&t->link);
> card->tlabel_mask &= ~(1ULL << t->tlabel);
> break;
> @@ -929,6 +933,7 @@ void fw_core_handle_response(struct fw_card *card, struct fw_packet *p)
> spin_unlock_irqrestore(&card->lock, flags);
>
> if (&t->link == &card->transaction_list) {
> +timed_out:
> fw_notify("Unsolicited response (source %x, tlabel %x)\n",
> source, tlabel);
> return;
> @@ -963,8 +968,6 @@ void fw_core_handle_response(struct fw_card *card, struct fw_packet *p)
> break;
> }
>
> - del_timer_sync(&t->split_timeout_timer);
> -
> /*
> * The response handler may be executed while the request handler
> * is still pending. Cancel the request handler.
Shall I commit with the added spin_unlocks? Or do you prefer to send an update?
--
Stefan Richter
-=====-==-=- =--- =--=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-08-18 12:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 18:42 Stefan Richter
2010-08-16 21:42 ` Peter Zijlstra
2010-08-16 22:09 ` Johannes Berg
2010-08-16 22:27 ` Johannes Berg
2010-08-17 16:22 ` Stefan Richter
2010-08-18 13:17 ` Stefan Richter
2010-08-17 14:35 ` Yong Zhang
2010-08-17 16:23 ` Stefan Richter
2010-08-18 7:01 ` Clemens Ladisch
2010-08-18 8:09 ` Stefan Richter
2010-08-18 8:53 ` Clemens Ladisch
2010-08-18 9:08 ` Yong Zhang
2010-08-18 8:59 ` Peter Zijlstra
2010-08-18 9:26 ` Clemens Ladisch
2010-08-18 9:43 ` Peter Zijlstra
2010-08-18 12:50 ` Stefan Richter [this message]
2010-08-18 13:05 ` Clemens Ladisch
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.2aa42a952e4df4b1@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=clemens@ladisch.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=yong.zhang0@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
Powered by JetHome