From: Mohammed Shafi <mshajakhan@atheros.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Mohammed Shajakhan <Mohammed.Shajakhan@Atheros.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath9k: Fix memory leak due to failed PAPRD frames
Date: Tue, 1 Feb 2011 20:34:53 +0530 [thread overview]
Message-ID: <4D482115.3090504@atheros.com> (raw)
In-Reply-To: <20110201140538.GA2560@tuxdriver.com>
On Tuesday 01 February 2011 07:35 PM, John W. Linville wrote:
> On Tue, Feb 01, 2011 at 10:11:54AM +0530, Mohammed Shafi wrote:
>
>> On Tuesday 01 February 2011 12:13 AM, Luis R. Rodriguez wrote:
>>
>>> On Sun, Jan 30, 2011 at 11:55 PM, Mohammed Shafi Shajakhan
>>> <mshajakhan@atheros.com> wrote:
>>>
>>>> From: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
>>>>
>>>> free the skb's when the Tx of PAPRD frames fails and also add a debug
>>>> message indicating that.
>>>>
>>>> Signed-off-by: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
>>>>
>>> Is this a stable fix?
>>>
>> No Luis, this problem came from some recent changes in PAPRD before
>> that it was Ok.
>>
> The patch applied to wireless-2.6 without changes, and the error
> handling for ath_tx_start matched existing usage. So, I have it
> queued now in wireless-2.6 with an added "Cc: stable@kernel.org".
>
> Should I not?
>
John this will be applicable for only 2.6.38 stable kernel.
The issue fixes for 2.6.37-rc5+ and this problem is not handled in the
following commit id:
commit 7607cbe2ad6931400c5d15ced342ab329ab8f92c
Date: Mon Dec 13 08:40:52 2010 +0100
This will not be even applicable for 2.6.37. It will introduce a
regression of double freeing skb's.
thanks,
shafi
> John
>
prev parent reply other threads:[~2011-02-01 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 7:55 [PATCH] ath9k: Fix memory leak due to failed PAPRD frames Mohammed Shafi Shajakhan
2011-01-31 18:43 ` Luis R. Rodriguez
2011-02-01 4:41 ` Mohammed Shafi
2011-02-01 14:05 ` John W. Linville
2011-02-01 15:04 ` Mohammed Shafi [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=4D482115.3090504@atheros.com \
--to=mshajakhan@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Mohammed.Shajakhan@Atheros.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).