From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Alexander Monakov <amonakov@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi null pointer dereference
Date: Sun, 20 Apr 2014 09:06:13 +0300 [thread overview]
Message-ID: <535363D5.4070708@gmail.com> (raw)
In-Reply-To: <CABtfrpDcZq=Ss=Zv9u0P3vz1D8rmgJ_jXGut-kZ0tkOmDZq9aw@mail.gmail.com>
Hi,
On 04/18/2014 11:33 PM, Alexander Monakov wrote:
> On Fri, Apr 18, 2014 at 6:50 PM, Emmanuel Grumbach <egrumbach@gmail.com> wrote:
>>>> I have to say that this is really strange - I must miss something. It looks like the ISR is called even before it is requested...
>>>> So I definitely want to understand what is happening here before applying the fix.
>>>
>>> Sure, I can help with further investigation. Would it help if I bisected?
>>>
>>
>> I can't decline such an offer:)
>>
>> Note that the "bad" commit might be in pci too.
>> As a first try, I'd try 3.13.
>> I've made quite a few changes in the ISR for 3.14.
>
> It bisects to
>
> commit 2dbc368d7fded35ed221a3751405b15e06eb8925
> Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> Date: Mon Dec 9 11:09:47 2013 +0200
>
> iwlwifi: pcie: track interrupt mask in SW
>
Yeah - ok.
Thank you for this information.
I'll check again later.
next prev parent reply other threads:[~2014-04-20 6:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 15:11 iwlwifi null pointer dereference Alexander Monakov
2014-04-13 7:23 ` Emmanuel Grumbach
2014-04-13 8:49 ` Alexander Monakov
2014-04-17 20:56 ` Alexander Monakov
2014-04-18 5:08 ` Emmanuel Grumbach
2014-04-18 13:47 ` Emmanuel Grumbach
2014-04-18 14:34 ` Alexander Monakov
2014-04-18 14:50 ` Emmanuel Grumbach
2014-04-18 20:33 ` Alexander Monakov
2014-04-20 6:06 ` Emmanuel Grumbach [this message]
2014-05-01 1:19 ` Emmanuel Grumbach
2014-05-01 8:43 ` Alexander Monakov
2014-05-07 13:37 ` Emmanuel Grumbach
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=535363D5.4070708@gmail.com \
--to=egrumbach@gmail.com \
--cc=amonakov@gmail.com \
--cc=linux-wireless@vger.kernel.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.