From: Sachin Sant <sachinp@in.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Frederik Deweerdt <frederik.deweerdt@xprog.eu>,
greg@kroah.org, Lars Ericsson <Lars_Ericsson@telia.com>,
David.Woodhouse@intel.com, linux-kernel@vger.kernel.org,
"'Ivo van Doorn'" <ivdoorn@gmail.com>
Subject: Re: [patch -stable] firware_class oops: fix firmware_loading_store locking
Date: Thu, 24 Sep 2009 20:43:57 +0530 [thread overview]
Message-ID: <4ABB8CB5.9080402@in.ibm.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0909230936320.3303@localhost.localdomain>
Linus Torvalds wrote:
> I don't think this is correct.
>
> I think you should protect the FW_STATUS_LOADING bit too, shouldn't you?
>
> As it is, it does this:
>
> if (test_bit(FW_STATUS_LOADING, &fw_priv->status)) {
> mutex_lock(&fw_lock);
> ...
> clear_bit(FW_STATUS_LOADING, &fw_priv->status);
> mutex_unlock(&fw_lock);
> break;
> }
>
> and if this code can race (which it obviously can, since your addition of
> fw_lock mutex matters), then I think it can race on that FW_STATUS_LOADING
> bit too. No?
>
> So my gut feel is that the whole damn function should be protected by the
> mutex_lock thing. IOW, the patch would be something like the appended.
>
> UNTESTED. Somebody needs to test this, verify, and send it back to me.
>
I did a quick boot test with this patch and didn't find any issues.
But that said i haven't been able to recreate the problem reported by Lars,
so not sure how relevant would be the test results from me.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-09-24 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 18:44 Oops in drivers\base\firmware_class Lars Ericsson
2009-09-16 20:57 ` Frederik Deweerdt
2009-09-18 17:53 ` Lars Ericsson
2009-09-21 13:32 ` [patch -stable] firware_class oops: fix firmware_loading_store locking Frederik Deweerdt
2009-09-23 16:42 ` Linus Torvalds
2009-09-24 15:13 ` Sachin Sant [this message]
2009-09-24 15:26 ` Frederik Deweerdt
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=4ABB8CB5.9080402@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=David.Woodhouse@intel.com \
--cc=Lars_Ericsson@telia.com \
--cc=frederik.deweerdt@xprog.eu \
--cc=greg@kroah.org \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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