From: Filipe Manana <fdmanana@kernel.org>
To: Naohiro Aota <naohiro.aota@wdc.com>
Cc: linux-btrfs@vger.kernel.org, johannes.thumshirn@wdc.com,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
david@fromorbit.com
Subject: Re: [PATCH 3/4] fs: add check functions for sb_start_{write,pagefault,intwrite}
Date: Fri, 11 Mar 2022 14:28:38 +0000 [thread overview]
Message-ID: <YitclpgTvXZ6lkf7@debian9.Home> (raw)
In-Reply-To: <407d74293ca164d44eb419d34c2365795e27c02f.1646983176.git.naohiro.aota@wdc.com>
On Fri, Mar 11, 2022 at 04:38:04PM +0900, Naohiro Aota wrote:
> Add a function sb_write_started() to return if sb_start_write() is
> properly called. It is used in the next commit.
>
> Also, add the similar functions for sb_start_pagefault() and
> sb_start_intwrite().
>
> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Looks good, thanks.
> ---
> include/linux/fs.h | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index 27746a3da8fd..0c8714d64169 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -1732,6 +1732,11 @@ static inline bool __sb_start_write_trylock(struct super_block *sb, int level)
> #define __sb_writers_release(sb, lev) \
> percpu_rwsem_release(&(sb)->s_writers.rw_sem[(lev)-1], 1, _THIS_IP_)
>
> +static inline bool __sb_write_started(struct super_block *sb, int level)
> +{
> + return lockdep_is_held_type(sb->s_writers.rw_sem + level - 1, 1);
> +}
> +
> /**
> * sb_end_write - drop write access to a superblock
> * @sb: the super we wrote to
> @@ -1797,6 +1802,11 @@ static inline bool sb_start_write_trylock(struct super_block *sb)
> return __sb_start_write_trylock(sb, SB_FREEZE_WRITE);
> }
>
> +static inline bool sb_write_started(struct super_block *sb)
> +{
> + return __sb_write_started(sb, SB_FREEZE_WRITE);
> +}
> +
> /**
> * sb_start_pagefault - get write access to a superblock from a page fault
> * @sb: the super we write to
> @@ -1821,6 +1831,11 @@ static inline void sb_start_pagefault(struct super_block *sb)
> __sb_start_write(sb, SB_FREEZE_PAGEFAULT);
> }
>
> +static inline bool sb_pagefault_started(struct super_block *sb)
> +{
> + return __sb_write_started(sb, SB_FREEZE_PAGEFAULT);
> +}
> +
> /**
> * sb_start_intwrite - get write access to a superblock for internal fs purposes
> * @sb: the super we write to
> @@ -1844,6 +1859,11 @@ static inline bool sb_start_intwrite_trylock(struct super_block *sb)
> return __sb_start_write_trylock(sb, SB_FREEZE_FS);
> }
>
> +static inline bool sb_intwrite_started(struct super_block *sb)
> +{
> + return __sb_write_started(sb, SB_FREEZE_FS);
> +}
> +
> bool inode_owner_or_capable(struct user_namespace *mnt_userns,
> const struct inode *inode);
>
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-03-11 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 7:38 [PATCH 0/4] protect relocation with sb_start_write Naohiro Aota
2022-03-11 7:38 ` [PATCH 1/4] btrfs: mark resumed async balance as writing Naohiro Aota
2022-03-11 14:08 ` Filipe Manana
2022-03-14 2:29 ` Naohiro Aota
2022-03-14 11:25 ` Filipe Manana
2022-03-11 7:38 ` [PATCH 2/4] btrfs: mark device addition as sb_writing Naohiro Aota
2022-03-11 14:21 ` Filipe Manana
2022-03-14 2:31 ` Naohiro Aota
2022-03-11 7:38 ` [PATCH 3/4] fs: add check functions for sb_start_{write,pagefault,intwrite} Naohiro Aota
2022-03-11 14:28 ` Filipe Manana [this message]
2022-03-11 7:38 ` [PATCH 4/4] btrfs: assert that relocation is protected with sb_start_write() Naohiro Aota
2022-03-11 14:33 ` 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=YitclpgTvXZ6lkf7@debian9.Home \
--to=fdmanana@kernel.org \
--cc=david@fromorbit.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=viro@zeniv.linux.org.uk \
/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).