Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:55536 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755130Ab0JRNsY convert rfc822-to-8bit (ORCPT ); Mon, 18 Oct 2010 09:48:24 -0400 Received: by iwn35 with SMTP id 35so73122iwn.19 for ; Mon, 18 Oct 2010 06:48:23 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <4CAE1DFB.303@candelatech.com> <1286479642.20974.32.camel@jlt3.sipsolutions.net> <4CB378CD.1080800@candelatech.com> <4CB3D598.7050904@candelatech.com> <4CB4AA89.1070009@candelatech.com> <20101013053141.GA15798@vasanth-laptop> <4CB5E0A8.5020502@candelatech.com> <4CB78870.8040207@candelatech.com> Date: Mon, 18 Oct 2010 15:48:23 +0200 Message-ID: Subject: Re: memory clobber in rx path, maybe related to ath9k. From: =?ISO-8859-1?Q?Bj=F6rn_Smedman?= To: Ben Greear , "Luis R. Rodriguez" Cc: Vasanthakumar Thiagarajan , Johannes Berg , "linux-wireless@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: 2010/10/15 Bj?rn Smedman > > 2010/10/15 Ben Greear : > > I tried the patch below, and it didn't seem to help. ?Might even > > have hurt..as it died on divide-by-zero error: > > Hmm, looks like the ani code got a zero listen time from the hw... > That just might mean that the DMA actually hits one of these > descriptors. :) Am I the only one worried about this? Leaving a DMA descriptor pointing at memory which has been passed on to somebody else... To me that's like pointing a loaded gun at someone (and it seems this particular gun can go off a little haphazardly). Luis, given how hard it seems to be to get that locking and skb shoveling right, are you sure you want to keep pointing that DMA engine on innocent people's data? /Bj?rn