From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Qu Wenruo <wqu@suse.de>,
linux-block@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] errno.h: Export EFSCORRUPTED error number
Date: Wed, 10 Apr 2019 18:47:38 -0700 [thread overview]
Message-ID: <20190411014738.GU15524@magnolia> (raw)
In-Reply-To: <89fc7ffb-412f-4e9f-efa2-a624f3ec6a14@gmx.com>
On Thu, Apr 11, 2019 at 09:43:05AM +0800, Qu Wenruo wrote:
>
>
> On 2019/4/11 上午9:06, Darrick J. Wong wrote:
> > On Thu, Apr 11, 2019 at 08:28:44AM +0800, Qu Wenruo wrote:
> >>
> >>
> >> On 2019/4/10 下午11:11, Darrick J. Wong wrote:
> >>> On Wed, Apr 10, 2019 at 04:35:07PM +0800, Qu Wenruo wrote:
> >>>> Xfs and Ext* uses EFSCORRUPTED to indicate filesystem corruption.
> >>>> They both map EFSCORRUPTED to EUCLEAN.
> >>>>
> >>>> Btrfs/Ubifs/fscrypto all use EUCLEAN directly to indicate filesystem
> >>>> corruption.
> >>>
> >>> I don't know if you (btrfs folks specifically) care but ext* and xfs
> >>> also use EFSBADCRC to signal unrecovered checksum validation failures.
> >>> Can we promote both of them to asm-generic/errno.h at the same time?
> >>
> >> It looks pretty good to me in fact.
> >>
> >> I'm really tired of using -EIO for csum mismatch/any other higher level
> >> mismatch.
> >>
> >> The only concern is the "CRC" part. Yes, btrfs uses and only supports
> >> CRC32 so far, but I'm sure btrfs will support cryptographic hash.
> >>
> >> So what about renaming it to EFSBADCSUM?
> >
> > We've been shipping EFSBADCRC in xfslibs-dev userspace libraries for
> > years now, so we can't change the symbol name.
>
> Fair enough.
>
> Any extra error number worthy export?
None that I can think of...
--D
> Thanks,
> Qu
>
> >
> > --D
> >
> >> Thanks,
> >> Qu
> >>
> >>>
> >>> #define EFSBADCRC EBADMSG
> >>>
> >>> --D
> >>>
> >>>> And block layer is going to distinguish filesystem corruption with
> >>>> oridinary EIO error, it's a good idea to export the initial EFSCORRUPTED
> >>>> declaration to <linux/errno.h> so all filesystems and block layer can
> >>>> take advantage of this easier-to-read error number.
> >>>>
> >>>> Signed-off-by: Qu Wenruo <wqu@suse.com>
> >>>> ---
> >>>> fs/ext2/ext2.h | 1 -
> >>>> fs/ext4/ext4.h | 1 -
> >>>> fs/xfs/xfs_linux.h | 1 -
> >>>> include/uapi/asm-generic/errno.h | 3 +++
> >>>> 4 files changed, 3 insertions(+), 3 deletions(-)
> >>>>
> >>>> diff --git a/fs/ext2/ext2.h b/fs/ext2/ext2.h
> >>>> index 10ab238de9a6..03d0ca8fae42 100644
> >>>> --- a/fs/ext2/ext2.h
> >>>> +++ b/fs/ext2/ext2.h
> >>>> @@ -369,7 +369,6 @@ struct ext2_inode {
> >>>> */
> >>>> #define EXT2_VALID_FS 0x0001 /* Unmounted cleanly */
> >>>> #define EXT2_ERROR_FS 0x0002 /* Errors detected */
> >>>> -#define EFSCORRUPTED EUCLEAN /* Filesystem is corrupted */
> >>>>
> >>>> /*
> >>>> * Mount flags
> >>>> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> >>>> index 82ffdacdc7fa..f906b5cbf96d 100644
> >>>> --- a/fs/ext4/ext4.h
> >>>> +++ b/fs/ext4/ext4.h
> >>>> @@ -3248,6 +3248,5 @@ extern const struct iomap_ops ext4_iomap_ops;
> >>>> #endif /* __KERNEL__ */
> >>>>
> >>>> #define EFSBADCRC EBADMSG /* Bad CRC detected */
> >>>> -#define EFSCORRUPTED EUCLEAN /* Filesystem is corrupted */
> >>>>
> >>>> #endif /* _EXT4_H */
> >>>> diff --git a/fs/xfs/xfs_linux.h b/fs/xfs/xfs_linux.h
> >>>> index edbd5a210df2..36e5c6549f15 100644
> >>>> --- a/fs/xfs/xfs_linux.h
> >>>> +++ b/fs/xfs/xfs_linux.h
> >>>> @@ -125,7 +125,6 @@ typedef __u32 xfs_nlink_t;
> >>>>
> >>>> #define ENOATTR ENODATA /* Attribute not found */
> >>>> #define EWRONGFS EINVAL /* Mount with wrong filesystem type */
> >>>> -#define EFSCORRUPTED EUCLEAN /* Filesystem is corrupted */
> >>>> #define EFSBADCRC EBADMSG /* Bad CRC detected */
> >>>>
> >>>> #define SYNCHRONIZE() barrier()
> >>>> diff --git a/include/uapi/asm-generic/errno.h b/include/uapi/asm-generic/errno.h
> >>>> index cf9c51ac49f9..ebd6e7e76a98 100644
> >>>> --- a/include/uapi/asm-generic/errno.h
> >>>> +++ b/include/uapi/asm-generic/errno.h
> >>>> @@ -98,6 +98,9 @@
> >>>> #define EINPROGRESS 115 /* Operation now in progress */
> >>>> #define ESTALE 116 /* Stale file handle */
> >>>> #define EUCLEAN 117 /* Structure needs cleaning */
> >>>> +
> >>>> +#define EFSCORRUPTED EUCLEAN /* Filesystem is corrupted */
> >>>> +
> >>>> #define ENOTNAM 118 /* Not a XENIX named type file */
> >>>> #define ENAVAIL 119 /* No XENIX semaphores available */
> >>>> #define EISNAM 120 /* Is a named type file */
> >>>> --
> >>>> 2.21.0
> >>>>
> >>>
> >>
> >
> >
> >
>
prev parent reply other threads:[~2019-04-11 1:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 8:35 [PATCH RFC 1/2] errno.h: Export EFSCORRUPTED error number Qu Wenruo
2019-04-10 8:35 ` [PATCH 2/2] block: Add new BLK_STS_FSCORRUPTED status Qu Wenruo
2019-04-10 8:55 ` Nikolay Borisov
2019-04-10 13:04 ` kbuild test robot
2019-04-10 15:11 ` [PATCH RFC 1/2] errno.h: Export EFSCORRUPTED error number Darrick J. Wong
2019-04-10 15:28 ` Nikolay Borisov
2019-04-11 0:28 ` Qu Wenruo
2019-04-11 1:06 ` Darrick J. Wong
2019-04-11 1:43 ` Qu Wenruo
2019-04-11 1:47 ` Darrick J. Wong [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=20190411014738.GU15524@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.de \
/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).