Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/3] btrfs: __TRANS_* flags cleanup
Date: Thu, 24 Sep 2026 15:28:13 +0930	[thread overview]
Message-ID: <cover.1790229298.git.wqu@suse.com> (raw)

This series is inspired by a recent comment from David, mentioning that
"if (type & TRANS_START == TRANS_START)" doesn't look sane.

It turns out that we should not define TRANS_START as multi-bit mask in
the first place.

The first patch is one sent in into the mailing list before, but since
later patches all rely on it, it's included into the series.

The second one is to remove the only flag that caused the exception.

The final one removes __TRANS_* flags completely, so every TRANS_* flag
is just a single bit.

Qu Wenruo (3):
  btrfs: move __TRANS_* and TRANS_* flags out of transaction.h
  btrfs: remove __TRANS_FREEZABLE
  btrfs: remove __TRANS_* flags

 fs/btrfs/backref.c           |  2 +-
 fs/btrfs/tests/btrfs-tests.c |  9 ----
 fs/btrfs/tests/btrfs-tests.h |  2 -
 fs/btrfs/transaction.c       | 95 +++++++++++++++++++++++++-----------
 fs/btrfs/transaction.h       | 29 +++++------
 5 files changed, 78 insertions(+), 59 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-09-24  5:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24  5:58 Qu Wenruo [this message]
2026-09-24  5:58 ` [PATCH v2 1/3] btrfs: move __TRANS_* and TRANS_* flags out of transaction.h Qu Wenruo
2026-09-28 18:27   ` Filipe Manana
2026-09-28 21:59     ` Qu Wenruo
2026-09-24  5:58 ` [PATCH v2 2/3] btrfs: remove __TRANS_FREEZABLE Qu Wenruo
2026-09-28 18:32   ` Filipe Manana
2026-09-24  5:58 ` [PATCH v2 3/3] btrfs: remove __TRANS_* flags Qu Wenruo
2026-09-28 18:34   ` 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.1790229298.git.wqu@suse.com \
    --to=wqu@suse.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