From: Andrey Borzenkov <arvidjaar@mail.ru>
To: David Kilroy <kilroyd@googlemail.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH] orinoco: take the driver lock in the rx tasklet
Date: Thu, 8 Jan 2009 11:28:27 +0300 [thread overview]
Message-ID: <200901081128.30143.arvidjaar@mail.ru> (raw)
In-Reply-To: <1231287835-17707-1-git-send-email-kilroyd@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On Среда 07 января 2009 03:23:55 David Kilroy wrote:
> Fix the warning reproduced below.
>
> We add to rx_list in interrupt context and remove elements in tasklet
> context. While removing elements we need to prevent the interrupt
> modifying the list.
>
> Note that commit 31afcef385bb8bf528c6fbe05b359af9f456f02a did not
> preserve locking semantics on what is now orinoco_rx.
>
> This patch reinstates the locking semantics and ensures it covers
> rx_list as well.
[...]
> --- a/drivers/net/wireless/orinoco/orinoco.c
> +++ b/drivers/net/wireless/orinoco/orinoco.c
> @@ -1613,6 +1613,16 @@ static void orinoco_rx_isr_tasklet(unsigned
[...]
> + if (orinoco_lock(priv, &flags) != 0)
> + return;
>
this effectively serializes rx list processing with the rest of driver
(specifically orinoco_interrupt) eliminating any benefit from doing it
in separate tasklet. It is more simple and less confusing to just revert
commit 31afcef385bb8bf528c6fbe05b359af9f456f02a then.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-08 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 0:23 [PATCH] orinoco: take the driver lock in the rx tasklet David Kilroy
2009-01-08 8:28 ` Andrey Borzenkov [this message]
2009-01-08 18:24 ` Dave
2009-01-08 18:55 ` Andrey Borzenkov
2009-01-22 4:02 ` Andrey Borzenkov
2009-01-22 19:58 ` Dave
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=200901081128.30143.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).