public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Chao Yu <yuchao0@huawei.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, chao@kernel.org
Subject: Re: [PATCH 1/2] f2fs: use generic EFSBADCRC/EFSCORRUPTED
Date: Fri, 21 Jun 2019 13:00:55 +0200	[thread overview]
Message-ID: <20190621110055.GC24145@amd> (raw)
In-Reply-To: <20190620033615.32284-1-yuchao0@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 724 bytes --]

On Thu 2019-06-20 11:36:14, Chao Yu wrote:
> f2fs uses EFAULT as error number to indicate filesystem is corrupted
> all the time, but generic filesystems use EUCLEAN for such condition,
> we need to change to follow others.
> 
> This patch adds two new macros as below to wrap more generic error
> code macros, and spread them in code.
> 
> EFSBADCRC	EBADMSG		/* Bad CRC detected */
> EFSCORRUPTED	EUCLEAN		/* Filesystem is corrupted */
> 
> Reported-by: Pavel Machek <pavel@ucw.cz>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>

Acked-by: Pavel Machek <pavel@ucw.cz>

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      parent reply	other threads:[~2019-06-21 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20  3:36 [PATCH 1/2] f2fs: use generic EFSBADCRC/EFSCORRUPTED Chao Yu
2019-06-20  3:36 ` [PATCH 2/2] f2fs: set SBI_NEED_FSCK for xattr corruption case Chao Yu
2019-06-21 11:00   ` Pavel Machek
2019-06-21 11:00 ` Pavel Machek [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=20190621110055.GC24145@amd \
    --to=pavel@ucw.cz \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.com \
    /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