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=-4.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no 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 5F9ACC433E0 for ; Sat, 30 Jan 2021 16:45:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1DEBE64E0F for ; Sat, 30 Jan 2021 16:45:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229851AbhA3QpX (ORCPT ); Sat, 30 Jan 2021 11:45:23 -0500 Received: from mail.kernel.org ([198.145.29.99]:53762 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231783AbhA3QpE (ORCPT ); Sat, 30 Jan 2021 11:45:04 -0500 Received: by mail.kernel.org (Postfix) with ESMTPS id 1991964E13 for ; Sat, 30 Jan 2021 16:32:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1612024364; bh=nsVOdFqkFz1Ann0zMtV4YpocUa1kMmg8B6elpKMp2u4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KgpGC1zXSDM2d9+1vsWkKeW88sUOgXTSXzRBs5gkbowtOFCdwWaWFOfUtwONcvNBC dMJWHzfN70BRD+Iopwta7Df3XUzLypYk+em5vfA7+/mBhyAdwvJbvo6oWMZKx0Fd9O 0VSMBZLdBKe7WZSQfUdKsfQz56bKLIVhdqoH0RVOkCPSIZBmywamJIMn9MVJomxkHR hrst2hhXM3znUDOSSVelBMw25X8f15gmKIX1V2szjFj2yHizqxuRuAISPN6r43viON REuiKOrVBHiUN0k29vAEZYo+IG1Ka2MSntj3zEGX3EHIKfGTNOHMN6mScTgxTqInn+ kvXLUJUcaOZ4g== From: bugzilla-daemon@bugzilla.kernel.org To: linux-xfs@vger.kernel.org Subject: [Bug 211329] blkg_alloc memory leak on ppc64le Date: Sat, 30 Jan 2021 16:32:43 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo filesystem_xfs@kernel-bugs.kernel.org X-Bugzilla-Product: IO/Storage X-Bugzilla-Component: Block Layer X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cam@neo-zeon.de X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: CODE_FIX X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: filesystem_xfs@kernel-bugs.kernel.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=3D211329 Cameron (cam@neo-zeon.de) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |CODE_FIX --- Comment #6 from Cameron (cam@neo-zeon.de) --- The issue appears to be transient. Leaks are detected, and after a clear an= d a a re-scan, leaks are no longer present. I'm thinking these are false positi= ves. --=20 You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.=