From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH 6/6] f2fs: use EFSCORRUPTED in f2fs_get_verity_descriptor()
Date: Sun, 11 Aug 2019 14:35:57 -0700 [thread overview]
Message-ID: <20190811213557.1970-7-ebiggers@kernel.org> (raw)
In-Reply-To: <20190811213557.1970-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
EFSCORRUPTED is now defined in f2fs.h, so use it instead of EUCLEAN.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
fs/f2fs/verity.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/verity.c b/fs/f2fs/verity.c
index 6bc3470d99d00..a401ef72bc821 100644
--- a/fs/f2fs/verity.c
+++ b/fs/f2fs/verity.c
@@ -210,7 +210,7 @@ static int f2fs_get_verity_descriptor(struct inode *inode, void *buf,
if (pos + size < pos || pos + size > inode->i_sb->s_maxbytes ||
pos < f2fs_verity_metadata_pos(inode) || size > INT_MAX) {
f2fs_warn(F2FS_I_SB(inode), "invalid verity xattr");
- return -EUCLEAN; /* EFSCORRUPTED */
+ return -EFSCORRUPTED;
}
if (buf_size) {
if (size > buf_size)
--
2.22.0
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 6/6] f2fs: use EFSCORRUPTED in f2fs_get_verity_descriptor()
Date: Sun, 11 Aug 2019 14:35:57 -0700 [thread overview]
Message-ID: <20190811213557.1970-7-ebiggers@kernel.org> (raw)
In-Reply-To: <20190811213557.1970-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
EFSCORRUPTED is now defined in f2fs.h, so use it instead of EUCLEAN.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
fs/f2fs/verity.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/verity.c b/fs/f2fs/verity.c
index 6bc3470d99d00..a401ef72bc821 100644
--- a/fs/f2fs/verity.c
+++ b/fs/f2fs/verity.c
@@ -210,7 +210,7 @@ static int f2fs_get_verity_descriptor(struct inode *inode, void *buf,
if (pos + size < pos || pos + size > inode->i_sb->s_maxbytes ||
pos < f2fs_verity_metadata_pos(inode) || size > INT_MAX) {
f2fs_warn(F2FS_I_SB(inode), "invalid verity xattr");
- return -EUCLEAN; /* EFSCORRUPTED */
+ return -EFSCORRUPTED;
}
if (buf_size) {
if (size > buf_size)
--
2.22.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-08-11 21:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 21:35 [PATCH 0/6] fs-verity fixups Eric Biggers
2019-08-11 21:35 ` [f2fs-dev] " Eric Biggers
2019-08-11 21:35 ` [PATCH 1/6] fs-verity: fix crash on read error in build_merkle_tree_level() Eric Biggers
2019-08-11 21:35 ` [f2fs-dev] " Eric Biggers
2019-08-11 21:35 ` [f2fs-dev] [PATCH 2/6] ext4: skip truncate when verity in progress in ->write_begin() Eric Biggers
2019-08-11 21:35 ` Eric Biggers
2019-08-11 21:35 ` [PATCH 3/6] f2fs: " Eric Biggers
2019-08-11 21:35 ` [f2fs-dev] " Eric Biggers
2019-08-12 12:25 ` Chao Yu
2019-08-12 12:25 ` [f2fs-dev] " Chao Yu
2019-08-12 12:25 ` Chao Yu
2019-08-12 22:58 ` [f2fs-dev] " Eric Biggers
2019-08-12 22:58 ` Eric Biggers
2019-08-13 2:40 ` [f2fs-dev] " Chao Yu
2019-08-13 2:40 ` Chao Yu
2019-08-13 2:40 ` Chao Yu
2019-08-18 20:24 ` [f2fs-dev] " Eric Biggers
2019-08-18 20:24 ` Eric Biggers
2019-08-11 21:35 ` [PATCH 4/6] ext4: remove ext4_bio_encrypted() Eric Biggers
2019-08-11 21:35 ` [f2fs-dev] " Eric Biggers
2019-08-11 21:35 ` [PATCH 5/6] ext4: fix comment in ext4_end_enable_verity() Eric Biggers
2019-08-11 21:35 ` [f2fs-dev] " Eric Biggers
2019-08-11 21:35 ` Eric Biggers [this message]
2019-08-11 21:35 ` [f2fs-dev] [PATCH 6/6] f2fs: use EFSCORRUPTED in f2fs_get_verity_descriptor() Eric Biggers
2019-08-12 12:26 ` Chao Yu
2019-08-12 12:26 ` [f2fs-dev] " Chao Yu
2019-08-12 12:26 ` Chao Yu
2019-08-18 20:23 ` [f2fs-dev] [PATCH 0/6] fs-verity fixups Eric Biggers
2019-08-18 20:23 ` Eric Biggers
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=20190811213557.1970-7-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@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.