From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Possible memory leak in ath9k monitor mode injection
Date: Thu, 12 Nov 2009 07:44:40 -0800 [thread overview]
Message-ID: <20091112154440.GD19349@tux> (raw)
In-Reply-To: <40101cc30911120618m5d9acd34pf6aa9ec89c6c40b8@mail.gmail.com>
On Thu, Nov 12, 2009 at 06:18:46AM -0800, Matteo Croce wrote:
> On Thu, Nov 12, 2009 at 12:31 PM, Lorenzo Bianconi
> <lorenzo.bianconi83@gmail.com> wrote:
> > Hi all
> >
> > I am playing with ath9k/mac80211 in monitor mode and I suspect there
> > is a memory leak.
> > The leak happens when injecting in monitor mode when the destination
> > MAC address is unicast.
> > In fact there is no leak sending broadcast packet.
> > I wrote this minimal test case module which triggers the leak.
>
> I can reproduce it with ath5k but not with madwifi, so the leak could
> be in mac80211
Can you please resend the thread to linux-wireless for wider review, with
the code snippet and all?
Luis
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Matteo Croce <technoboy85@gmail.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] Possible memory leak in ath9k monitor mode injection
Date: Thu, 12 Nov 2009 07:44:40 -0800 [thread overview]
Message-ID: <20091112154440.GD19349@tux> (raw)
In-Reply-To: <40101cc30911120618m5d9acd34pf6aa9ec89c6c40b8@mail.gmail.com>
On Thu, Nov 12, 2009 at 06:18:46AM -0800, Matteo Croce wrote:
> On Thu, Nov 12, 2009 at 12:31 PM, Lorenzo Bianconi
> <lorenzo.bianconi83@gmail.com> wrote:
> > Hi all
> >
> > I am playing with ath9k/mac80211 in monitor mode and I suspect there
> > is a memory leak.
> > The leak happens when injecting in monitor mode when the destination
> > MAC address is unicast.
> > In fact there is no leak sending broadcast packet.
> > I wrote this minimal test case module which triggers the leak.
>
> I can reproduce it with ath5k but not with madwifi, so the leak could
> be in mac80211
Can you please resend the thread to linux-wireless for wider review, with
the code snippet and all?
Luis
next prev parent reply other threads:[~2009-11-12 15:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 11:31 [ath9k-devel] Possible memory leak in ath9k monitor mode injection Lorenzo Bianconi
2009-11-12 11:31 ` Lorenzo Bianconi
2009-11-12 14:18 ` [ath9k-devel] " Matteo Croce
2009-11-12 14:18 ` Matteo Croce
2009-11-12 15:44 ` Luis R. Rodriguez [this message]
2009-11-12 15:44 ` [ath9k-devel] " Luis R. Rodriguez
2009-11-12 15:49 ` Luis R. Rodriguez
2009-11-12 15:49 ` Luis R. Rodriguez
2009-11-12 19:18 ` Matteo Croce
2009-11-12 19:31 ` Johannes Berg
2009-11-12 19:35 ` Luis R. Rodriguez
2009-11-12 19:36 ` Luis R. Rodriguez
2009-11-12 22:16 ` Matteo Croce
2009-11-12 22:28 ` Luis R. Rodriguez
2009-11-12 22:37 ` Matteo Croce
2009-11-12 22:58 ` Lorenzo Bianconi
2009-11-12 23:04 ` Matteo Croce
2009-11-13 7:06 ` Johannes Berg
2009-11-12 22:08 ` Matteo Croce
2009-11-12 22:18 ` Matteo Croce
2009-11-13 7:31 ` Johannes Berg
2009-11-13 8:55 ` Lorenzo Bianconi
2009-11-13 12:20 ` Matteo Croce
2009-11-14 2:13 ` Luis R. Rodriguez
2009-11-16 15:08 ` Matteo Croce
[not found] ` <0015174c1d0a8aa23304783ef2ae@google.com>
2009-11-13 14:42 ` R:Re: " Matteo Croce
2009-11-13 14:47 ` Johannes Berg
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=20091112154440.GD19349@tux \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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 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.