From: Chao Yu <chao@kernel.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: f2fs: support fault injection for f2fs_down_write_trylock()
Date: Mon, 3 Apr 2023 09:22:06 +0800 [thread overview]
Message-ID: <d1bbd9b1-9fcb-526b-30b1-efa4b1b92c4c@kernel.org> (raw)
In-Reply-To: <20230331185505.58726-1-frank.li@vivo.com>
On 2023/4/1 2:55, Yangtao Li wrote:
>> I guess we can cover all trylock w/ FAULT_LOCK_OP type fault injection,
Oops, there is a typo, s/FAULT_LOCK_OP/FAULT_LOCK.
I meant introducing FAULT_LOCK to cover all below functions, and keep
FAULT_LOCK_OP as it is to just cover f2fs_trylock_op...
- inode_trylock
- down_read_trylock
- down_write_trylock
- mutex_trylock
- sb_start_write_trylock
- trylock_page
Thanks,
prev parent reply other threads:[~2023-04-03 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 15:25 [PATCH v2] " Yangtao Li
2023-03-31 12:58 ` Chao Yu
2023-03-31 18:55 ` Yangtao Li
2023-04-03 1:22 ` Chao Yu [this message]
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=d1bbd9b1-9fcb-526b-30b1-efa4b1b92c4c@kernel.org \
--to=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®