From: Johannes Thumshirn <jth@kernel.org>
To: linux-btrfs@vger.kernel.org
Cc: Damien Le Moal <dlemoal@kernel.org>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Johannes Thumshirn <jth@kernel.org>,
Mark Harmstone <maharmstone@fb.com>,
Omar Sandoval <osandov@osandov.com>
Subject: [PATCH 0/2] btrfs: fix use-after-free in btrfs_encoded_read_endio
Date: Mon, 11 Nov 2024 10:28:25 +0100 [thread overview]
Message-ID: <cover.1731316882.git.jth@kernel.org> (raw)
Shinichiro reported a occassional memory corruption in our CI system with
btrfs/248 that lead to panics. He also managed to reproduce this
corruption reliably on one host. See patch 1/2 for details on the
corruption and the fix, patch 2/2 is a cleanup Damien suggested on top of
the fix to make the code more obvious.
Mark, I've tried your test tool for the encoded read io_uring path, but didn't
succeed building it. Can you please have a look at these patches with an
io_uring hat on?
Johannes Thumshirn (2):
btrfs: fix use-after-free in btrfs_encoded_read_endio
btrfs: simplify waiting for encoded read endios
fs/btrfs/inode.c | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2024-11-11 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 9:28 Johannes Thumshirn [this message]
2024-11-11 9:28 ` [PATCH 1/2] btrfs: fix use-after-free in btrfs_encoded_read_endio Johannes Thumshirn
2024-11-11 13:27 ` Filipe Manana
2024-11-11 13:44 ` Damien Le Moal
2024-11-11 14:21 ` Filipe Manana
2024-11-11 18:17 ` Mark Harmstone
2024-11-11 9:28 ` [PATCH 2/2] btrfs: simplify waiting for encoded read endios Johannes Thumshirn
2024-11-11 9:56 ` Damien Le Moal
2024-11-11 10:13 ` Johannes Thumshirn
2024-11-11 18:36 ` Mark Harmstone
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=cover.1731316882.git.jth@kernel.org \
--to=jth@kernel.org \
--cc=dlemoal@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=maharmstone@fb.com \
--cc=osandov@osandov.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