Date: Thu, 10 Nov 2011 10:18:16 +0100
From: =?utf-8?B?VG9tw6HFoSBKYW5vdcWhZWs=?= <tomi@nomi.cz>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-kernel@vger.kernel.org, Wey-Yi Guy <wey-yi.w.guy@intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: iwlagn: memory corruption with WPA enterprise
Message-ID: <20111110091816.GA2247@nomi.cz> (sfid-20111110_101844_068858_5867EEE0)
References: <20111029171554.GA16596@nomi.cz> <20111031160342.GB2225@redhat.com> <20111109155411.GA1669@nomi.cz> <20111109165158.GA2254@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <20111109165158.GA2254@redhat.com>
Sender: linux-wireless-owner@vger.kernel.org

Hello,

On Wed, Nov 09, 2011 at 05:51:59PM +0100, Stanislaw Gruszka wrote:
> I just discovered that CONFIG_DEBUG_PAGEALLOC does not work as expected.
> It leave most of free pages unprotected, hence unintentional write to
> them is not discovered. I'm attaching additional patch, which should
> make detection actually work.
> 
> If kernel will does not boot with corrupt_dbg=1, you may try to catch
> corruption without that option. Attached patch should make it possible,
> however having corrupt_dbg=1 increase probability of the catch.

Okay, I applied this additional patch, and by the increased memory usage (as
shown by free) I concluded that it indeed works. However, I was still able to
reproduce the issue without a single error being written to dmesg. :-(

I will try some really old kernels as Wey suggested to see whether it makes
any sense to bisect it, but if it does, it might take more time than I can
make free. Perhaps it would be cheaper to just get another card in that case.
:-)

Kind regards,
-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/