All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Natarajan <vivek.natraj@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Vivek Natarajan <vnatarajan@atheros.com>,
	linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/5] ath9k: Fix a locking related issue.
Date: Fri, 18 Mar 2011 06:20:59 +0530	[thread overview]
Message-ID: <AANLkTimDyJ3C4UOi_F_UtMdhO=4MoYjyoCh4zSixKg5p@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim=KNYmEVddpNRD33iOYiMBh+x0WnegBWD0i3FO@mail.gmail.com>

On Fri, Mar 18, 2011 at 5:49 AM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Thu, Jan 27, 2011 at 1:15 AM, Vivek Natarajan <vnatarajan@atheros.com> wrote:
>> Spin_lock has been tried to be acquired twice from ath9k_tasklet
>> to ath_reset which resulted in a machine freeze.
>>
>> Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
>> ---
>
> Was this a stable fix? :(
>

Actually this was meant to be a quickfix for the panic we had noticed.
A proper fix would be to review all the spinlocks in ath9k and do a
revamp. Anyhow, such a revamp might take some time and before that we
will have this patch for stable. Thanks a lot, I will resend this to
stable.

Vivek.

      reply	other threads:[~2011-03-18  0:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27  9:15 [PATCH 1/5] ath9k_hw: Add a function to read sqsum_dvc Vivek Natarajan
2011-01-27  9:15 ` [PATCH 2/5] ath9k: Fix a PLL hang issue observed with AR9485 Vivek Natarajan
2011-01-27  9:15   ` [PATCH 3/5] ath9k_hw: DDR_PLL and BB_PLL need correct setting Vivek Natarajan
2011-01-27  9:15     ` [PATCH 4/5] ath9k: Fix a locking related issue Vivek Natarajan
2011-01-27  9:15       ` [PATCH 5/5] ath9k_hw: Update PMU setting to improve ripple issue for AR9485 Vivek Natarajan
2011-03-18  0:19       ` [PATCH 4/5] ath9k: Fix a locking related issue Luis R. Rodriguez
2011-03-18  0:50         ` Vivek Natarajan [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='AANLkTimDyJ3C4UOi_F_UtMdhO=4MoYjyoCh4zSixKg5p@mail.gmail.com' \
    --to=vivek.natraj@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=vnatarajan@atheros.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.