[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZL30Vaj8RYxmsF9o@casper.infradead.org>
Date: Mon, 24 Jul 2023 04:47:33 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Linke Li <lilinke99@...mail.com>
Cc: linux-mm@...ck.org, mike.kravetz@...cle.com, muchun.song@...ux.dev,
nathan@...nel.org, ndesaulniers@...gle.com, trix@...hat.com,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
dan.carpenter@...aro.org, Linke Li <lilinke99@...il.com>
Subject: Re: [PATCH v3] hugetlbfs: Fix integer overflow check in
hugetlbfs_file_mmap()
On Thu, Jul 20, 2023 at 10:49:52PM +0800, Linke Li wrote:
> +++ b/fs/hugetlbfs/inode.c
> @@ -154,10 +154,7 @@ static int hugetlbfs_file_mmap(struct file *file, struct vm_area_struct *vma)
> if (vma->vm_pgoff & (~huge_page_mask(h) >> PAGE_SHIFT))
> return -EINVAL;
>
> - vma_len = (loff_t)(vma->vm_end - vma->vm_start);
> - len = vma_len + ((loff_t)vma->vm_pgoff << PAGE_SHIFT);
> - /* check for overflow */
> - if (len < vma_len)
> + if (check_add_overflow(vma_len, (loff_t)vma->vm_pgoff << PAGE_SHIFT, &len))
> return -EINVAL;
Doesn't this check duplicate that performed by file_mmap_ok()? Can't we
just delete the check, or is there a code path that leads here while
avoiding file_mmap_ok()?
Powered by blists - more mailing lists