From: Dan Carpenter <dan.carpenter@oracle.com>
To: darrick.wong@oracle.com
Cc: linux-ext4@vger.kernel.org
Subject: re: ext4: call out CRC and corruption errors with specific error codes
Date: Tue, 17 May 2016 16:15:24 +0300 [thread overview]
Message-ID: <20160517131524.GA14581@mwanda> (raw)
Hello Darrick J. Wong,
The patch 6a797d273783: "ext4: call out CRC and corruption errors
with specific error codes" from Oct 17, 2015, leads to the following
static checker warning:
fs/ext4/xattr.c:854 ext4_xattr_block_set()
warn: error is never (-117)
fs/ext4/xattr.c
837 /*
838 * This must happen under buffer lock for
839 * ext4_xattr_block_set() to reliably detect modified
840 * block
841 */
842 mb_cache_entry_delete_block(ext4_mb_cache, hash,
843 bs->bh->b_blocknr);
844 ea_bdebug(bs->bh, "modifying in-place");
845 error = ext4_xattr_set_entry(i, s);
846 if (!error) {
847 if (!IS_LAST_ENTRY(s->first))
848 ext4_xattr_rehash(header(s->base),
849 s->here);
850 ext4_xattr_cache_insert(ext4_mb_cache,
851 bs->bh);
852 }
853 unlock_buffer(bs->bh);
854 if (error == -EFSCORRUPTED)
We changed this from -EIO to -EFSCORRUPTED but actually
ext4_xattr_set_entry() doesn't return either of those.
855 goto bad_block;
856 if (!error)
857 error = ext4_handle_dirty_xattr_block(handle,
858 inode,
859 bs->bh);
860 if (error)
861 goto cleanup;
862 goto inserted;
863 } else {
regards,
dan carpenter
next reply other threads:[~2016-05-17 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 13:15 Dan Carpenter [this message]
2016-05-17 13:25 ` ext4: call out CRC and corruption errors with specific error codes Dan Carpenter
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=20160517131524.GA14581@mwanda \
--to=dan.carpenter@oracle.com \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@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.