All of lore.kernel.org
 help / color / mirror / Atom feed
From: Filipe Manana <fdmanana@gmail.com>
To: dsterba@suse.cz, Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
	Josef Bacik <josef@toxicpanda.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	"kernel-team@fb.com" <kernel-team@fb.com>
Subject: Re: [PATCH] btrfs: fix setting last_trans for reloc roots
Date: Tue, 21 Apr 2020 09:04:41 +0100	[thread overview]
Message-ID: <CAL3q7H5bduJcyZ5S8ZYnV7tznWsXQiPhvQ773mUfsMn=Voau0w@mail.gmail.com> (raw)
In-Reply-To: <20200420232016.GL18421@twin.jikos.cz>

On Tue, Apr 21, 2020 at 12:22 AM David Sterba <dsterba@suse.cz> wrote:
>
> On Thu, Apr 16, 2020 at 03:34:30PM +0000, Johannes Thumshirn wrote:
> > On 16/04/2020 14:38, Johannes Thumshirn wrote:
> > > This fixes a kmemleak complaint from btrfs/074, complete re-run of
> > > xfstests is pending, but one down again.
> > >
> > > Tested-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> > >
> >
> > I'll take that back, I still see a leak of 'cur_trans' allocated in
> > join_transaction() for btrfs/074 on a full xfstests run. The same leak
> > is reported for btrfs/072 and generic/127.
>
> I'm not sure, but the patch "btrfs: drop logs when we've aborted a
> transaction" is fixing transaction handle leaks. I've added it to
> misc-next, the effects have been observed in test generic/475 so it's
> only a weak link, tests btrfs/074 do not stress the transaction cleanup
> that much.

Hum?
That patch fixes a use-after-crash during unmount after a transaction
was aborted - it doesn't fix transaction leaks as far as I can see.
Perhaps you meant patch "btrfs: fix memory leak of transaction when
deleting unused block group", which fixes a regression introduced in
5.7-rc1.
btrfs/074 (and tests 060 to 073) often triggers unused block group
deletion due to fsstress and other operations in parallel.



-- 
Filipe David Manana,

“Whether you think you can, or you think you can't — you're right.”

      reply	other threads:[~2020-04-21  8:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 15:42 [PATCH] btrfs: fix setting last_trans for reloc roots Josef Bacik
2020-04-14 16:24 ` Filipe Manana
2020-04-16 12:24 ` David Sterba
2020-04-16 12:37 ` Johannes Thumshirn
2020-04-16 15:34   ` Johannes Thumshirn
2020-04-20 23:20     ` David Sterba
2020-04-21  8:04       ` Filipe Manana [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='CAL3q7H5bduJcyZ5S8ZYnV7tznWsXQiPhvQ773mUfsMn=Voau0w@mail.gmail.com' \
    --to=fdmanana@gmail.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=dsterba@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.