From: Wang Shilong <wangshilong1991@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: ebiggers@kernel.org, Wang Shilong <wshilong@ddn.com>
Subject: [PATCH v2] Valgrind reported error messages like following:
Date: Fri, 19 Jun 2020 11:26:14 +0900 [thread overview]
Message-ID: <1592533574-24249-1-git-send-email-wangshilong1991@gmail.com> (raw)
From: Wang Shilong <wshilong@ddn.com>
==129205== Address 0x1b804b04 is 4 bytes after a block of size 4,096 alloc'd
==129205== at 0x483980B: malloc (vg_replace_malloc.c:307)
==129205== by 0x44F973: ext2fs_get_mem (ext2fs.h:1846)
==129205== by 0x44F973: ext2fs_get_pathname (get_pathname.c:162)
==129205== by 0x430917: print_pathname (message.c:212)
==129205== by 0x430FB1: expand_percent_expression (message.c:462)
==129205== by 0x430FB1: print_e2fsck_message (message.c:544)
==129205== by 0x430BED: expand_at_expression (message.c:262)
==129205== by 0x430BED: print_e2fsck_message (message.c:528)
==129205== by 0x430450: fix_problem (problem.c:2494)
==129205== by 0x423F8B: e2fsck_process_bad_inode (pass2.c:1929)
==129205== by 0x425AE8: check_dir_block (pass2.c:1407)
==129205== by 0x426942: check_dir_block2 (pass2.c:961)
==129205== by 0x445736: ext2fs_dblist_iterate3.part.0 (dblist.c:254)
==129205== by 0x423835: e2fsck_pass2 (pass2.c:187)
==129205== by 0x414B19: e2fsck_run (e2fsck.c:257)
Dir block might be corrupted and cause the next dirent is out
of block size boundary, even though we have the check to avoid
problem, memory check tools like valgrind still complains it.
Patch try to fix the problem by checking if offset exceed max
offset firstly before getting the pointer.
Signed-off-by: Wang Shilong <wshilong@ddn.com>
---
v1->v2:
kept same return value for corruption case as before.
---
lib/ext2fs/csum.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/lib/ext2fs/csum.c b/lib/ext2fs/csum.c
index c2550365..417a1fba 100644
--- a/lib/ext2fs/csum.c
+++ b/lib/ext2fs/csum.c
@@ -266,16 +266,14 @@ static errcode_t __get_dirent_tail(ext2_filsys fs,
d = dirent;
top = EXT2_DIRENT_TAIL(dirent, fs->blocksize);
- rec_len = translate(d->rec_len);
while ((void *) d < top) {
- if ((rec_len < 8) || (rec_len & 0x03))
+ rec_len = translate(d->rec_len);
+ if ((rec_len < 8) || (rec_len & 0x03) ||
+ (rec_len > (char *)dirent + fs->blocksize - (char *)d))
return EXT2_ET_DIR_CORRUPTED;
d = (struct ext2_dir_entry *)(((char *)d) + rec_len);
- rec_len = translate(d->rec_len);
}
- if ((char *)d > ((char *)dirent + fs->blocksize))
- return EXT2_ET_DIR_CORRUPTED;
if (d != top)
return EXT2_ET_DIR_NO_SPACE_FOR_CSUM;
--
2.25.4
next reply other threads:[~2020-06-19 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 2:26 Wang Shilong [this message]
2020-06-19 2:30 ` [PATCH v2] Valgrind reported error messages like following: Wang Shilong
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=1592533574-24249-1-git-send-email-wangshilong1991@gmail.com \
--to=wangshilong1991@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=wshilong@ddn.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