[0/2,v2] Some leaked root fixes

Message ID	cover.1597953516.git.josef@toxicpanda.com (mailing list archive)
Headers	show Return-Path: <SRS0=L84K=B6=vger.kernel.org=linux-btrfs-owner@kernel.org> From: Josef Bacik <josef@toxicpanda.com> To: linux-btrfs@vger.kernel.org, kernel-team@fb.com Subject: [PATCH 0/2][v2] Some leaked root fixes Date: Thu, 20 Aug 2020 16:00:13 -0400 Message-Id: <cover.1597953516.git.josef@toxicpanda.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk
Series	Some leaked root fixes \| expand [0/2,v2] Some leaked root fixes [1/2] btrfs: free fs roots on failed mount [2/2] btrfs: pretty print leaked root name

Message ID

cover.1597953516.git.josef@toxicpanda.com (mailing list archive)

Headers

From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/2][v2] Some leaked root fixes
Date: Thu, 20 Aug 2020 16:00:13 -0400
Message-Id: <cover.1597953516.git.josef@toxicpanda.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-btrfs-owner@vger.kernel.org
Precedence: bulk

Series

Some leaked root fixes | expand

Message

Josef Bacik Aug. 20, 2020, 8 p.m. UTC

Hello,

These are two fixes for a leaked root problem I noticed a while ago.  One is the
actual leaked root fix, the other is to add a pretty print for the leaked root
message, as figuring out that some giant %llu number was the data reloc root is
not a feat meant for humans.  Thanks,

Josef