Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753949Ab0DYTW7 (ORCPT ); Sun, 25 Apr 2010 15:22:59 -0400 Received: from mail-bw0-f219.google.com ([209.85.218.219]:57226 "EHLO mail-bw0-f219.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753810Ab0DYTW4 convert rfc822-to-8bit (ORCPT ); Sun, 25 Apr 2010 15:22:56 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=b/mG925+cESKV0+aBT7ujtg9z+th2YISQKUiuuepYzS8pVdWeNrW/RxtBbNudNy9NQ zNPSZ/wy6FL8l8L5zugGPqR1Lw6XOHe1ngVxOPf09/c0PSqfo+a6LbBQiASITUL81kck M+xBteU/IYMOEEzB5VJdtW5PNkOdC2yU7Q0x8= MIME-Version: 1.0 In-Reply-To: <20100425163711.GA20196@kroah.com> References: <20100419145934.GA10893@kroah.com> <20100425163711.GA20196@kroah.com> Date: Sun, 25 Apr 2010 22:22:54 +0300 Message-ID: Subject: Re: request_firmware API exhaust memory From: Tomas Winkler To: Greg KH Cc: Johannes Berg , Kay Sievers , David Woodhouse , "Rafael J. Wysocki" , Emmanuel Grumbach , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1531 Lines: 34 On Sun, Apr 25, 2010 at 7:37 PM, Greg KH wrote: > On Thu, Apr 22, 2010 at 01:22:51AM +0300, Tomas Winkler wrote: >> On Mon, Apr 19, 2010 at 5:59 PM, Greg KH wrote: >> > On Mon, Apr 19, 2010 at 03:20:34PM +0300, Tomas Winkler wrote: >> >> Lately we've been developing a device that rather more extensively >> >> used request_firmware API in load and also using pm_notifiers to load >> >> firmware. >> > >> > Do you have a pointer to your driver source anywhere that shows how you >> > are trying to use the firmware api in this manner? >> >> I've attached a very simple  test driver I'm using.  Just wanted to >> eliminate anything else. >> Bellow is a little script that loads and releases the firmware. My >> previous observation was wrong. >> The free memory gradually decreases regardless of number or dangling >> udevd forks, which are eventually collected if the sleep period is >> long enough ~10s. > > That sounds normal for the free memory.  Kay, that's also to be expected > for the udevd forks as well, right? Sorry maybe I was not clear what I mean that the memory will be eventually exhausted and system will crash Is this normal? Actually I less suspect now udevd as the same happens on android platform where there is no udev Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/