Return-path: Received: from mail-ie0-f177.google.com ([209.85.223.177]:56092 "EHLO mail-ie0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755274AbaDPLB0 (ORCPT ); Wed, 16 Apr 2014 07:01:26 -0400 Received: by mail-ie0-f177.google.com with SMTP id rl12so10339739iec.36 for ; Wed, 16 Apr 2014 04:01:26 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1393376982-28276-1-git-send-email-mcgrof@do-not-panic.com> <1393376982-28276-3-git-send-email-mcgrof@do-not-panic.com> <1393852248.10039.5.camel@jlt4.sipsolutions.net> Date: Wed, 16 Apr 2014 13:01:26 +0200 Message-ID: (sfid-20140416_130130_975325_54226B0D) Subject: Re: [PATCH 2/3] cfg80211: fix processing world regdomain when non modular From: Janusz Dziedzic To: Arik Nemtsov Cc: Colleen T , Eliad Peller , "Luis R. Rodriguez" , Johannes Berg , linux-wireless , Sander Eikelenboom Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: 2014-04-16 12:38 GMT+02:00 Arik Nemtsov : > Thanks for testing Colleen! > > I'll respin the patch on top of wireless-testing. > Please don't remove "Pending regulatory reques ... " dbg print. This could be usefull for debuging. BR Janusz > Arik > > On Mon, Apr 14, 2014 at 10:27 PM, Colleen T wrote: >> Hello, >> >> Applying Arik's patch on top of Luis' resolves our problem. >> >> You also get my: >> >> Tested-by: Colleen Twitty >> >> Thanks, >> -Colleen >> >> On Sun, Apr 13, 2014 at 5:50 AM, Eliad Peller wrote: >>> On Wed, Apr 9, 2014 at 7:33 PM, Arik Nemtsov wrote: >>>> >>>> Seems I might have found the culprit - reg_todo is called while the >>>> request to CRDA is in flight and the patch in question causes the >>>> already-in-process user-request to be handled again. Since it's the >>>> same regdomain as the last request (it's the last request itself), we >>>> get this: >>>> >>>> treatment = __reg_process_hint_user(user_request); >>>> if (treatment == REG_REQ_IGNORE || >>>> treatment == REG_REQ_ALREADY_SET) { >>>> kfree(user_request); <------ >>>> return treatment; >>>> } >>>> >>>> Can you try adding the attached patch? It just replaced relevant >>>> kfree-s with a function that avoids freeing the last request. >>>> >>> i encountered a similar panic, and this patch seems to fix it. >>> so you get my: >>> >>> Tested-by: Eliad Peller >>> >>> Eliad. -- Janusz Dziedzic