mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org,
	Yong Zhang <yong.zhang0@gmail.com>
Subject: Re: [3.2-rc3] 100% CPU usage while in del_timer_sync from iwl3945_rs_free_sta
Date: Thu, 1 Dec 2011 15:05:00 +0100	[thread overview]
Message-ID: <20111201140500.GA4269@tiehlicka.suse.cz> (raw)
In-Reply-To: <20111201124440.GB25614@tiehlicka.suse.cz>

On Thu 01-12-11 13:44:40, Michal Hocko wrote:
> On Thu 01-12-11 12:59:12, Stanislaw Gruszka wrote:
> > On Thu, Dec 01, 2011 at 11:55:38AM +0100, Michal Hocko wrote:
> > > [  349.316070] iwl3945_rs_free_sta rs_sta f4be1ac0
> > > [  349.316076] ------------[ cut here ]------------
> > > [  349.316097] WARNING: at drivers/net/wireless/iwlegacy/iwl-3945-rs.c:438 iwl3945_rs_free_sta+0x33/0x42 [iwl3945]()
> > 
> > Johannes pointed on irc that this problem is most likely caused by:
> > 
> > commit f785d83a19bca326f79d127a413e35769afc0105
> > Author: Eliad Peller <eliad@wizery.com>
> > Date:   Mon Aug 8 16:50:22 2011 +0300
> > 
> >     mac80211: clear sta.drv_priv on reconfiguration
> > 
> > Michal, could you confirm that? If that is the root of the problem, we
> > need patch for iwlegacy (and iwlwifi) that allocate separate memory for
> > rc structures.
> 
> Should I just revert it?

Reverted and guess what ;)
Yeah, it works. So feel free to add
Reported-adn-Tested-by: Michal Hocko <mhocko@suse.cz>
to the revert.

Anyway, I have really no idea about the 80211 stack but the patch
doesn't seem to be correct from the layering POV. Why should generic
layer clear something that is driver private data (or at least the
naming suggests that it is driver specific data)?

Thanks a lot for your help.
-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

  parent reply	other threads:[~2011-12-01 14:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 10:07 Michal Hocko
2011-11-29 11:39 ` Stanislaw Gruszka
2011-11-30 10:10   ` Michal Hocko
2011-11-30 14:23     ` Stanislaw Gruszka
2011-11-30 14:03       ` Michal Hocko
2011-11-30 15:39         ` Stanislaw Gruszka
2011-12-01  8:58           ` Michal Hocko
2011-12-01 10:55             ` Michal Hocko
2011-12-01 11:59               ` Stanislaw Gruszka
2011-12-01 12:44                 ` Michal Hocko
2011-12-01 12:55                   ` Stanislaw Gruszka
2011-12-01 13:13                     ` Eliad Peller
2011-12-01 13:31                       ` Stanislaw Gruszka
2011-12-01 13:37                       ` Sedat Dilek
2011-12-01 14:05                   ` Michal Hocko [this message]
2011-12-01 14:23                     ` Eliad Peller
2011-12-01 15:45                       ` John W. Linville
2011-12-01 12:04               ` Yong Zhang
2011-12-01 12:42                 ` Michal Hocko
2011-12-01  2:09 ` Yong Zhang

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=20111201140500.GA4269@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sgruszka@redhat.com \
    --cc=yong.zhang0@gmail.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

all inboxes | Powered by JetHome®