All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	frank.li@vivo.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v11] f2fs: support errors=remount-ro|continue|panic mountoption
Date: Mon, 08 May 2023 18:34:27 +0000	[thread overview]
Message-ID: <168357086712.2764.18059620800942332067.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230423154915.530254-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Sun, 23 Apr 2023 23:49:15 +0800 you wrote:
> This patch supports errors=remount-ro|continue|panic mount option
> for f2fs.
> 
> f2fs behaves as below in three different modes:
> mode			continue	remount-ro	panic
> access ops		normal		noraml		N/A
> syscall errors		-EIO		-EROFS		N/A
> mount option		rw		ro		N/A
> pending dir write	keep		keep		N/A
> pending non-dir write	drop		keep		N/A
> pending node write	drop		keep		N/A
> pending meta write	keep		keep		N/A
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v11] f2fs: support errors=remount-ro|continue|panic mountoption
    https://git.kernel.org/jaegeuk/f2fs/c/b62e71be2110

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, frank.li@vivo.com
Subject: Re: [f2fs-dev] [PATCH v11] f2fs: support errors=remount-ro|continue|panic mountoption
Date: Mon, 08 May 2023 18:34:27 +0000	[thread overview]
Message-ID: <168357086712.2764.18059620800942332067.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230423154915.530254-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Sun, 23 Apr 2023 23:49:15 +0800 you wrote:
> This patch supports errors=remount-ro|continue|panic mount option
> for f2fs.
> 
> f2fs behaves as below in three different modes:
> mode			continue	remount-ro	panic
> access ops		normal		noraml		N/A
> syscall errors		-EIO		-EROFS		N/A
> mount option		rw		ro		N/A
> pending dir write	keep		keep		N/A
> pending non-dir write	drop		keep		N/A
> pending node write	drop		keep		N/A
> pending meta write	keep		keep		N/A
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v11] f2fs: support errors=remount-ro|continue|panic mountoption
    https://git.kernel.org/jaegeuk/f2fs/c/b62e71be2110

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2023-05-08 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 15:49 [PATCH v11] f2fs: support errors=remount-ro|continue|panic mountoption Chao Yu
2023-04-23 15:49 ` [f2fs-dev] " Chao Yu
2023-05-08 18:34 ` patchwork-bot+f2fs [this message]
2023-05-08 18:34   ` patchwork-bot+f2fs

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=168357086712.2764.18059620800942332067.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.