From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs: fix a deadlock with reclaim during logging/log replay
Date: Thu, 13 Jun 2024 12:05:24 +0100 [thread overview]
Message-ID: <cover.1718276261.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Fix a deadlock when opening an inode during inode logging and log replay
due to a GFP_KERNEL allocation, reported by syzbot. The rest is just some
trivial cleanups. Details in the change logs.
Filipe Manana (4):
btrfs: use NOFS context when getting inodes during logging and log replay
btrfs: remove super block argument from btrfs_iget()
btrfs: remove super block argument from btrfs_iget_path()
btrfs: remove super block argument from btrfs_iget_locked()
fs/btrfs/btrfs_inode.h | 6 +++---
fs/btrfs/defrag.c | 2 +-
fs/btrfs/export.c | 4 ++--
fs/btrfs/free-space-cache.c | 3 +--
fs/btrfs/inode.c | 24 ++++++++++-----------
fs/btrfs/ioctl.c | 3 +--
fs/btrfs/relocation.c | 4 ++--
fs/btrfs/send.c | 9 ++++----
fs/btrfs/super.c | 2 +-
fs/btrfs/tree-log.c | 43 ++++++++++++++++++++++++-------------
10 files changed, 54 insertions(+), 46 deletions(-)
--
2.43.0
next reply other threads:[~2024-06-13 11:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 11:05 fdmanana [this message]
2024-06-13 11:05 ` [PATCH 1/4] btrfs: use NOFS context when getting inodes during logging and log replay fdmanana
2024-06-13 21:37 ` Qu Wenruo
2024-06-13 21:54 ` Filipe Manana
2024-06-13 22:21 ` Qu Wenruo
2024-06-13 22:29 ` Filipe Manana
2024-06-16 18:40 ` David Sterba
2024-06-13 11:05 ` [PATCH 2/4] btrfs: remove super block argument from btrfs_iget() fdmanana
2024-06-13 11:05 ` [PATCH 3/4] btrfs: remove super block argument from btrfs_iget_path() fdmanana
2024-06-13 11:05 ` [PATCH 4/4] btrfs: remove super block argument from btrfs_iget_locked() fdmanana
2024-06-13 14:04 ` [PATCH 0/4] btrfs: fix a deadlock with reclaim during logging/log replay Johannes Thumshirn
2024-06-13 14:56 ` Josef Bacik
2024-06-13 21:10 ` David Sterba
2024-06-13 21:37 ` Qu Wenruo
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.1718276261.git.fdmanana@suse.com \
--to=fdmanana@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 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.