linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: Filipe Manana <fdmanana@kernel.org>, linux-btrfs@vger.kernel.org
Subject: Re: fstests btrfs/232 triggle warning of btrfs_extent_buffer_leak_debug_check
Date: Mon, 26 Sep 2022 18:16:05 +0200	[thread overview]
Message-ID: <20220926161604.GA13389@twin.jikos.cz> (raw)
In-Reply-To: <20220926201940.B938.409509F4@e16-tech.com>

On Mon, Sep 26, 2022 at 08:19:43PM +0800, Wang Yugui wrote:
> Hi,
> 
> > On Sun, Sep 25, 2022 at 8:06 AM Wang Yugui <wangyugui@e16-tech.com> wrote:
> > >
> > > Hi,
> > >
> > > fstests btrfs/232 triggle warning of btrfs_extent_buffer_leak_debug_check
> > 
> > Try the fixup I reported here:
> > 
> > https://lore.kernel.org/linux-btrfs/20220926091440.GA1198392@falcondesktop/
> > 
> > And see if it still triggers the leak.
> > Thanks.
> 
> With this fixup, this leak does not happen again.
> test times: 3
> 
> Thanks a lot.

Thank you for the report and test.

      reply	other threads:[~2022-09-26 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25  6:18 fstests btrfs/232 triggle warning of btrfs_extent_buffer_leak_debug_check Wang Yugui
2022-09-26  9:19 ` Filipe Manana
2022-09-26 12:19   ` Wang Yugui
2022-09-26 16:16     ` 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=20220926161604.GA13389@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wangyugui@e16-tech.com \
    /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;
as well as URLs for NNTP newsgroup(s).