From: luojiajun <luojiajun3@huawei.com>
To: <linux-mm@kvack.org>
Cc: <mike.kravetz@oracle.com>, <yi.zhang@huawei.com>, <miaoxie@huawei.com>
Subject: [PATCH] hugetlbfs: end hpage in hugetlbfs_fallocate overflow
Date: Tue, 9 Apr 2019 10:00:26 +0800 [thread overview]
Message-ID: <1554775226-67213-1-git-send-email-luojiajun3@huawei.com> (raw)
In hugetlbfs_fallocate, start is rounded down and end is rounded up.
But it is inappropriate to use loff_t rounding up end, it may cause
overflow.
UBSAN: Undefined behaviour in fs/hugetlbfs/inode.c:582:22
signed integer overflow:
2097152 + 9223372036854775805 cannot be represented in type 'long long int'
CPU: 0 PID: 2669 Comm: syz-executor662 Not tainted 4.19.30 #5
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.10.2-1ubuntu1 04/01/2014
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0xca/0x13e lib/dump_stack.c:113
ubsan_epilogue+0xe/0x81 lib/ubsan.c:159
handle_overflow+0x193/0x1e2 lib/ubsan.c:190
hugetlbfs_fallocate+0xe72/0x1140 fs/hugetlbfs/inode.c:582
vfs_fallocate+0x346/0x7a0 fs/open.c:308
ioctl_preallocate+0x15d/0x200 fs/ioctl.c:482
file_ioctl fs/ioctl.c:498 [inline]
do_vfs_ioctl+0xde3/0x10a0 fs/ioctl.c:688
ksys_ioctl+0x89/0xa0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x74/0xb0 fs/ioctl.c:710
do_syscall_64+0xc8/0x580 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x44a3e9
Fix this problem by casting loff_t to unsigned long long when end
is rounded up.
This problem can be reproduced by syzkaller
Signed-off-by: luojiajun <luojiajun3@huawei.com>
---
fs/hugetlbfs/inode.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
index 7f33244..0fe07f2 100644
--- a/fs/hugetlbfs/inode.c
+++ b/fs/hugetlbfs/inode.c
@@ -578,8 +578,9 @@ static long hugetlbfs_fallocate(struct file *file, int mode, loff_t offset,
* For this range, start is rounded down and end is rounded up
* as well as being converted to page offsets.
*/
- start = offset >> hpage_shift;
- end = (offset + len + hpage_size - 1) >> hpage_shift;
+ start = (unsigned long long)offset >> hpage_shift;
+ end = ((unsigned long long)(offset + len + hpage_size) - 1)
+ >> hpage_shift;
inode_lock(inode);
--
2.7.4
next reply other threads:[~2019-04-09 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 2:00 luojiajun [this message]
2019-04-09 2:54 ` [PATCH] hugetlbfs: end hpage in hugetlbfs_fallocate overflow Matthew Wilcox
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=1554775226-67213-1-git-send-email-luojiajun3@huawei.com \
--to=luojiajun3@huawei.com \
--cc=linux-mm@kvack.org \
--cc=miaoxie@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=yi.zhang@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;
as well as URLs for NNTP newsgroup(s).