From: Christoph Hellwig <hch@infradead.org>
To: Leo Martins <loemra.dev@gmail.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] btrfs: fix delayed_node ref_tracker use after free
Date: Mon, 20 Oct 2025 22:26:53 -0700 [thread overview]
Message-ID: <aPcZnUICwvlZXwsq@infradead.org> (raw)
In-Reply-To: <e5d6dd45f720f2543ca4ea7ee3e66454ef55f639.1761001854.git.loemra.dev@gmail.com>
This fixes the use after free I saw in xfstests btrfs/071:
Tested-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-10-21 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 23:16 [PATCH] btrfs: fix delayed_node ref_tracker use after free Leo Martins
2025-10-21 5:26 ` Christoph Hellwig [this message]
2025-10-22 6:42 ` David Sterba
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=aPcZnUICwvlZXwsq@infradead.org \
--to=hch@infradead.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=loemra.dev@gmail.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