From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <jth@kernel.org>
Cc: Dennis Zhou <dennis@kernel.org>,
linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: Re: memleaks in btrfs-devel/misc-next
Date: Wed, 8 Jan 2020 14:02:17 +0100 [thread overview]
Message-ID: <20200108130217.GD3929@twin.jikos.cz> (raw)
In-Reply-To: <a1834955-9d1e-2f7b-13e9-7be02bd368fe@kernel.org>
On Wed, Jan 08, 2020 at 08:28:12AM +0100, Johannes Thumshirn wrote:
> Am 08.01.20 um 01:31 schrieb Dennis Zhou:
> [...]
> > I believe it's because I forgot to put a reference in the relocation
> > path. The below seems to fix it in my tests, but would you mind
> > verifying?
>
>
> Thanks for the quick turn around.
> Tested-by: Johannes Thumshirn <jth@kernel.org>
>
> @David can you fold this into
> 63c3d72cf65e ("btrfs: add the beginning of async discard, discard
> workqueue")
Folded and pushed, thanks for catching it.
prev parent reply other threads:[~2020-01-08 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 11:43 memleaks in btrfs-devel/misc-next Johannes Thumshirn
2020-01-07 18:04 ` Dennis Zhou
2020-01-08 0:31 ` Dennis Zhou
2020-01-08 7:28 ` Johannes Thumshirn
2020-01-08 13:02 ` David Sterba [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200108130217.GD3929@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dennis@kernel.org \
--cc=dsterba@suse.com \
--cc=jth@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox