From: wwguy <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] iwlwifi: fix dma mappings and skbs leak
Date: Mon, 14 Feb 2011 07:51:36 -0800 [thread overview]
Message-ID: <1297698696.4723.16.camel@wwguy-ubuntu> (raw)
In-Reply-To: <1297693947-15310-1-git-send-email-sgruszka@redhat.com>
On Mon, 2011-02-14 at 06:32 -0800, Stanislaw Gruszka wrote:
> Since commit commit 470058e0ad82fcfaaffd57307d8bf8c094e8e9d7
> "iwlwifi: avoid Tx queue memory allocation in interface down" we do
> not unmap dma and free skbs when down device and there is pending
> transfer. What in consequence may cause that system hung when
> performing shutdown at iptables module unload.
>
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> ---
> v1 -> v2: do not claim patch fixes warning, which is still
> observable with patch applied
>
> drivers/net/wireless/iwlwifi/iwl-agn-tx.c | 12 +++++-
> drivers/net/wireless/iwlwifi/iwl-core.h | 2 +
> drivers/net/wireless/iwlwifi/iwl-tx.c | 61 ++++++++++++++++++++--------
> 3 files changed, 56 insertions(+), 19 deletions(-)
Are you still seeing the "warning"
Wey
next prev parent reply other threads:[~2011-02-14 15:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 14:32 [PATCH v2] iwlwifi: fix dma mappings and skbs leak Stanislaw Gruszka
2011-02-14 15:51 ` wwguy [this message]
2011-02-15 11:34 ` Stanislaw Gruszka
2011-02-15 11:50 ` Johannes Berg
2011-02-15 13:04 ` Stanislaw Gruszka
2011-02-15 13:09 ` Johannes Berg
2011-02-15 13:22 ` Stanislaw Gruszka
2011-02-15 13:30 ` Johannes Berg
2011-02-16 9:49 ` Stanislaw Gruszka
2011-02-16 9:54 ` [PATCH] mac80211: fix conn_mon_timer running after disassociate Stanislaw Gruszka
2011-02-16 11:10 ` Johannes Berg
2011-02-18 2:19 ` Sujith
2011-02-18 7:48 ` Stanislaw Gruszka
2011-02-19 9:04 ` [PATCH v2] iwlwifi: fix dma mappings and skbs leak 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=1297698696.4723.16.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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.