From: Michael Buesch <mb@bu3sch.de>
To: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
"Hin-Tak Leung" <hintak.leung@gmail.com>,
Pavel Roskin <proski@gnu.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC/RFT] rtl8187: Protect the config callback from mac80211 with a mutex
Date: Wed, 30 Jul 2008 18:16:37 +0200 [thread overview]
Message-ID: <200807301816.37570.mb@bu3sch.de> (raw)
In-Reply-To: <200807301308.01631.herton@mandriva.com.br>
On Wednesday 30 July 2008 18:08:01 Herton Ronaldo Krzesinski wrote:
> Em Wednesday 30 July 2008 12:02:30 Michael Buesch escreveu:
> > On Wednesday 30 July 2008 16:53:13 Herton Ronaldo Krzesinski wrote:
> > > Em Wednesday 30 July 2008 10:27:26 Michael Buesch escreveu:
> > > > On Wednesday 30 July 2008 15:24:40 Michael Buesch wrote:
> <snip>
> > > > and the mutex name, of course.
> > > >
> > > > /* Mutex to protect the device configuration data,
> > > > * which is foobar and bizzbaz */
> > > > struct mutex conf_mutex;
> > >
> > > Yes, it's better this way. About the lock, the problem here is you can't
> > > set the channel while transmitting data on 8187 (the card stops working
> > > util reset like the comment on the code), so we must enable tx loopback
> > > while setting channels, but you can't run rtl8187_config concurrently
> > > because one instance may be disabling tx loopback while other is still
> > > setting channel, or like the code is today there is a possibility that
> > > you set tx loopback forever. The lock could be only in that section.
> > >
> > > The comment could be:
> > > /* Mutex to protect the device configuration data,
> > > * we can't set channels concurrently */
> >
> > I think you probably want to protect the tx-loopback (enabled or disabled)
> > state. That's what you're actually doing implicitely. The problem is not
> > any channel concurrency or something like that, but that the
> > tx-loopback-enable/disable is not recursive is the real thing we want to
> > lock here, probably.
>
> No, the issue is that I must enter in tx-loopback mode to set the channels
> inside rtl8187_config, to avoid transmission of packets, so the hardware
> doesn't halt. So that's why the lock, it must cover the entire section
> of "enable loopback"->"set_chan"->"disable loopback", not only the state of
> TX_CONF register.
Yeah, I said exactly that.
You protect the loopback stuff. Not any config callback or anything else.
--
Greetings Michael.
next prev parent reply other threads:[~2008-07-30 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 6:12 [RFC/RFT] rtl8187: Protect the config callback from mac80211 with a mutex Larry Finger
2008-07-30 13:24 ` Michael Buesch
2008-07-30 13:27 ` Michael Buesch
2008-07-30 14:53 ` Herton Ronaldo Krzesinski
2008-07-30 15:02 ` Michael Buesch
2008-07-30 16:08 ` Herton Ronaldo Krzesinski
2008-07-30 16:16 ` Michael Buesch [this message]
2008-07-30 17:13 ` Herton Ronaldo Krzesinski
2008-07-30 17:31 ` Larry Finger
2008-07-30 17:46 ` Michael Buesch
2008-07-30 18:11 ` Herton Ronaldo Krzesinski
2008-07-30 18:41 ` Michael Buesch
2008-07-30 19:26 ` Hin-Tak Leung
2008-07-30 13:27 ` Herton Ronaldo Krzesinski
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=200807301816.37570.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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;
as well as URLs for NNTP newsgroup(s).