From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kvalo@adurom.com>
Cc: Soumik DAS <soumik.das@stericsson.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] mac80211: Increment probe_send_count earlier
Date: Tue, 5 Jun 2012 15:00:58 -0400 [thread overview]
Message-ID: <20120605190058.GC1937@tuxdriver.com> (raw)
In-Reply-To: <87mx5g8j31.fsf@purkki.adurom.net>
On Thu, May 10, 2012 at 12:46:10PM +0300, Kalle Valo wrote:
> Hi Soumik,
>
> Soumik DAS <soumik.das@stericsson.com> writes:
>
> > In some cases the sequence of events gets changed -
> > a. call ieee80211_send_nullfunc()
> > (current thread gets scheduled out/pre-empted at this point)
> > b. null frame gets transmitted and acked
> > c. probe_send_count is incremented
> > d. mac80211 waits for some specified timeout and checks that probe_send_count is still > 0. It concludes that AP did not acknowledge the null frame and disassociates from the current AP.
> > e. After a scan STA again re-associate with the same AP.
>
> Ok, so there's a race in mac80211? You should describe the race in the
> commit log so that a random developer understands what's happening. It
> doesn't need to be anything fancy, usually just few sentences is enough
> to give sufficient background for the patch. Where the race is, how
> often it happens and how to fix it properly, that sort of things.
>
> I repeat this a lot (sorry!) but the most important question the commit
> log should answer is "Why?". The question "What?" isn't actually that
> important as anyone can read the patch themselves.
>
> --
> Kalle Valo
Soumik,
Are you going to repost with a proper changelog?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2012-06-05 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 5:46 [PATCH] mac80211: Increment probe_send_count earlier Soumik DAS
2012-05-10 7:11 ` Kalle Valo
2012-05-10 8:43 ` Soumik DAS
2012-05-10 9:46 ` Kalle Valo
2012-06-05 19:00 ` John W. Linville [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=20120605190058.GC1937@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=soumik.das@stericsson.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;
as well as URLs for NNTP newsgroup(s).