From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [PATCH 0/2] Btrfs: workqueue cleanups
Date: Tue, 13 Aug 2019 00:26:02 -0700 [thread overview]
Message-ID: <cover.1565680721.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
These are a couple of cleanups for Btrfs workqueues as a follow-up to
"Btrfs: fix workqueue deadlock on dependent filesystems" [1]. They are
based on misc-next + that patch.
Patch 1 removes the previous, incomplete fix for the same issue fixed by
[1]. Patch 2 is more of a nitpick, but I think it makes things clearer.
Thanks!
1: https://lore.kernel.org/linux-btrfs/0bea516a54b26e4e1c42e6fe47548cb48cc4172b.1565112813.git.osandov@fb.com/
Omar Sandoval (2):
Btrfs: get rid of unique workqueue helper functions
Btrfs: get rid of pointless wtag variable in async-thread.c
fs/btrfs/async-thread.c | 79 ++++++++++--------------------------
fs/btrfs/async-thread.h | 33 +--------------
fs/btrfs/block-group.c | 3 +-
fs/btrfs/delayed-inode.c | 4 +-
fs/btrfs/disk-io.c | 34 +++++-----------
fs/btrfs/inode.c | 36 +++++-----------
fs/btrfs/ordered-data.c | 1 -
fs/btrfs/qgroup.c | 1 -
fs/btrfs/raid56.c | 5 +--
fs/btrfs/reada.c | 3 +-
fs/btrfs/scrub.c | 14 +++----
fs/btrfs/volumes.c | 3 +-
include/trace/events/btrfs.h | 6 +--
13 files changed, 61 insertions(+), 161 deletions(-)
--
2.22.0
next reply other threads:[~2019-08-13 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 7:26 Omar Sandoval [this message]
2019-08-13 7:26 ` [PATCH 1/2] Btrfs: get rid of unique workqueue helper functions Omar Sandoval
2019-08-13 8:08 ` Nikolay Borisov
2019-08-13 8:52 ` Filipe Manana
2019-08-13 17:20 ` Omar Sandoval
2019-08-13 7:26 ` [PATCH 2/2] Btrfs: get rid of pointless wtag variable in async-thread.c Omar Sandoval
2019-08-13 8:08 ` Nikolay Borisov
2019-08-13 9:06 ` Filipe Manana
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.1565680721.git.osandov@fb.com \
--to=osandov@osandov.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 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).