Return-path: Received: from mail-ie0-f175.google.com ([209.85.223.175]:38578 "EHLO mail-ie0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753808AbaDRUdO (ORCPT ); Fri, 18 Apr 2014 16:33:14 -0400 Received: by mail-ie0-f175.google.com with SMTP id to1so1919684ieb.6 for ; Fri, 18 Apr 2014 13:33:13 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <53513BC4.7020502@gmail.com> References: <5350B340.9020201@gmail.com> <53512D04.5070808@gmail.com> <53513BC4.7020502@gmail.com> Date: Sat, 19 Apr 2014 00:33:13 +0400 Message-ID: (sfid-20140418_223340_662750_77D47C4C) Subject: Re: iwlwifi null pointer dereference From: Alexander Monakov To: Emmanuel Grumbach Cc: linux-wireless Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Apr 18, 2014 at 6:50 PM, Emmanuel Grumbach 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 Date: Mon Dec 9 11:09:47 2013 +0200 iwlwifi: pcie: track interrupt mask in SW