From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E6E9EC43381 for ; Tue, 26 Mar 2019 12:55:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AF2CE20823 for ; Tue, 26 Mar 2019 12:55:50 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=c-s.fr header.i=@c-s.fr header.b="UiCCQ5WN" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731483AbfCZMzt (ORCPT ); Tue, 26 Mar 2019 08:55:49 -0400 Received: from pegase1.c-s.fr ([93.17.236.30]:50859 "EHLO pegase1.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726241AbfCZMzs (ORCPT ); Tue, 26 Mar 2019 08:55:48 -0400 Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 44TB2B2bW4z9v1gl; Tue, 26 Mar 2019 13:55:46 +0100 (CET) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=UiCCQ5WN; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id 9I57AftTqaND; Tue, 26 Mar 2019 13:55:46 +0100 (CET) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 44TB2B1XJfz9v1gh; Tue, 26 Mar 2019 13:55:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1553604946; bh=TvigbH1h2KALPmzqyb+VabwfL492c4scfq3E6byADRU=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=UiCCQ5WN/NAqKHRntaGP4nDeLD6Rv3mNAVbDEO7utC6g/kWPmhzO8tZDSKcKwdY37 repeT8NKtBxx8uFFwmrG32Aa2dlCPTVsDLjlfxGUU6cu+E3mzLdA6Xlfe8CXhwbOSg DtGKb0inNe8D3Ujh/Omebn3N+ywSKJ1zHB0XiVEI= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 7FC398B8D3; Tue, 26 Mar 2019 13:55:47 +0100 (CET) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id OKukCXTG8ZSk; Tue, 26 Mar 2019 13:55:47 +0100 (CET) Received: from PO15451 (unknown [192.168.4.90]) by messagerie.si.c-s.fr (Postfix) with ESMTP id EB4408B8D0; Tue, 26 Mar 2019 13:55:46 +0100 (CET) Subject: Re: Reading `/sys/kernel/debug/kmemleak` takes 3 s and content not shown To: Paul Menzel , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org References: <88e651e2-d876-376e-81fa-eab0729ebb47@molgen.mpg.de> From: Christophe Leroy Message-ID: Date: Tue, 26 Mar 2019 13:55:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 26/03/2019 à 13:49, Paul Menzel a écrit : > Dear Linux folks, > > > On 19.02.19 10:44, Paul Menzel wrote: > >> On a the IBM S822LC (8335-GTA) with Ubuntu 18.10, and Linux 5.0-rc5+ >> accessing `/sys/kernel/debug/kmemleak` takes a long time. According to >> strace it takes three seconds. >> >> $ dmesg | grep leak >> [    4.407957] kmemleak: Kernel memory leak detector initialized >> [    4.407959] kmemleak: Automatic memory scanning thread started >> [745989.625624] kmemleak: 1 new suspected memory leaks (see >> /sys/kernel/debug/kmemleak) >> [1002619.951902] kmemleak: 1 new suspected memory leaks (see >> /sys/kernel/debug/kmemleak) >> ``` >> >> Unfortunately, the leaks supposedly stored in that file are not shown >> either. > > The problem is still present with Linux 5.0. Do you have an idea, how to > fix this? > Have you identified a previous version that works properly ? If so, have you been able to bisect the problem ? Christophe