Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752039Ab0KIGBY (ORCPT ); Tue, 9 Nov 2010 01:01:24 -0500 Received: from mail-fx0-f46.google.com ([209.85.161.46]:40117 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751273Ab0KIGBW convert rfc822-to-8bit (ORCPT ); Tue, 9 Nov 2010 01:01:22 -0500 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=iPouDhG1tqRPPNDsrX1OoDD7nxfPtXSBTqR59o7dwymbbn6ICYtgbVS1uYCWd04Bkm sE0PR/QPg6VdXEWTjgP8UVhzTbIaFF2jtT5n8bPOccGCSQs2UIuqrQfl06lUulZRFYUM T0EIy3kbzQp5hnTUt+ZajUOYXx0p4Ca6uu1ZU= MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 9 Nov 2010 17:01:20 +1100 Message-ID: Subject: Re: 2.6.37-rc1 kmemleak warnings when saving a file over cifs. From: Andrew Hendry To: Steve French Cc: linux-kernel , linux-cifs@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1805 Lines: 41 The server is a qnap NAS, running linux 2.6.24 On Tue, Nov 9, 2010 at 3:12 PM, Steve French wrote: > On Mon, Nov 8, 2010 at 6:13 PM, Andrew Hendry wrote: >> Have just noticed these in the past few days, now running 2.6.37-rc1+ >> Seems to be 1 logged per file save when using a text file with gedit over cifs. > > Can you tell the called function in cifs_setattr_unix vs. cifs_setattr_nounix > (the former will usually be called when the server is Samba, the latter > when the server is Windows or NetApp). ?What is the server type? > >> unreferenced object 0xffff88022ee08b40 (size 32): >> ?comm "gedit", pid 2524, jiffies 4300160388 (age 2633.655s) >> ?hex dump (first 32 bytes): >> ? ?5c 2e 67 6f 75 74 70 75 74 73 74 72 65 61 6d 2d ?\.goutputstream- >> ? ?35 42 41 53 4c 56 00 de 09 00 00 00 2c 26 78 ee ?5BASLV......,&x. >> ?backtrace: >> ? ?[] kmemleak_alloc+0x2d/0x60 >> ? ?[] __kmalloc+0xe3/0x1d0 >> ? ?[] build_path_from_dentry+0xf0/0x230 [cifs] >> ? ?[] cifs_setattr+0x9e/0x770 [cifs] >> ? ?[] notify_change+0x170/0x2e0 >> ? ?[] sys_fchmod+0x10b/0x140 >> ? ?[] system_call_fastpath+0x16/0x1b >> ? ?[] 0xffffffffffffffff > > Didn't see anything obvious in cifs_setattr_unix on the kmalloc/kfree > of full_path, > but it will help when we know which path we are in. ?We did make some recent > changes in 2.6.37 in file allocation. > > -- > Thanks, > > Steve > -- 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/