From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [RESEND PATCH 0/3] cleanup rdonly flag and BTRFS_FS_OPEN flag
Date: Fri, 3 Jun 2022 07:12:08 +0530 [thread overview]
Message-ID: <cover.1654216941.git.anand.jain@oracle.com> (raw)
Patch 1/3 brings the check for the rdonly to a new function
btrfs_fs_is_rdonly().
Patch 2/3 wraps the check for BTRFS_FS_OPEN flag into
btrfs_fs_state_is_open_rw().
Patch 3/3 removes the rdonly part from the BTRFS_FS_OPEN flag is true
for both rdonly and rw.
Anand Jain (3):
btrfs: wrap rdonly check into btrfs_fs_is_rdonly
btrfs: wrap check for BTRFS_FS_OPEN flag into function
btrfs: set BTRFS_FS_OPEN flag for both rdonly and rw
fs/btrfs/block-group.c | 6 ++---
fs/btrfs/ctree.h | 19 ++++++++++++++--
fs/btrfs/dev-replace.c | 2 +-
fs/btrfs/disk-io.c | 50 +++++++++++++++++++++--------------------
fs/btrfs/extent_io.c | 4 ++--
fs/btrfs/inode.c | 2 +-
fs/btrfs/ioctl.c | 2 +-
fs/btrfs/super.c | 14 +++++-------
fs/btrfs/sysfs.c | 4 ++--
fs/btrfs/tree-checker.c | 2 +-
fs/btrfs/volumes.c | 6 ++---
11 files changed, 63 insertions(+), 48 deletions(-)
--
2.33.1
next reply other threads:[~2022-06-03 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 1:42 Anand Jain [this message]
2022-06-03 1:42 ` [RESEND PATCH 1/3] btrfs: wrap rdonly check into btrfs_fs_is_rdonly Anand Jain
2022-06-03 8:43 ` Johannes Thumshirn
2022-06-07 10:15 ` Anand Jain
2022-06-07 13:30 ` Johannes Thumshirn
2022-06-21 17:10 ` David Sterba
2022-06-03 1:42 ` [RESEND PATCH 2/3] btrfs: wrap check for BTRFS_FS_OPEN flag into function Anand Jain
2022-06-03 1:42 ` [RESEND PATCH 3/3] btrfs: set BTRFS_FS_OPEN flag for both rdonly and rw Anand Jain
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.1654216941.git.anand.jain@oracle.com \
--to=anand.jain@oracle.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