From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to check readonly condition correctly
Date: Tue, 04 Apr 2023 21:30:18 +0000 [thread overview]
Message-ID: <168064381893.16246.7986262771761292127.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230404152807.4987-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 4 Apr 2023 23:28:07 +0800 you wrote:
> With below case, it can mount multi-device image w/ rw option, however
> one of secondary device is set as ro, later update will cause panic, so
> let's introduce f2fs_dev_is_readonly(), and check multi-devices rw status
> in f2fs_remount() w/ it in order to avoid such inconsistent mount status.
>
> mkfs.f2fs -c /dev/zram1 /dev/zram0 -f
> blockdev --setro /dev/zram1
> mount -t f2fs dev/zram0 /mnt/f2fs
> mount: /mnt/f2fs: WARNING: source write-protected, mounted read-only.
> mount -t f2fs -o remount,rw mnt/f2fs
> dd if=/dev/zero of=/mnt/f2fs/file bs=1M count=8192
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to check readonly condition correctly
https://git.kernel.org/jaegeuk/f2fs/c/2bce08d26c0f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-04-04 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 15:28 [PATCH v2] f2fs: fix to check readonly condition correctly Chao Yu
2023-04-04 21:30 ` patchwork-bot+f2fs [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=168064381893.16246.7986262771761292127.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--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