From: kbuild test robot <lkp@intel.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: kbuild-all@01.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Michal Hocko <mhocko@kernel.org>,
Yisheng Xie <xieyisheng1@huawei.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Nic Losby <blurbdust@gmail.com>, Dan Rue <dan.rue@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/1] hugetlbfs: fix bug in pgoff overflow checking
Date: Fri, 30 Mar 2018 00:00:23 +0800 [thread overview]
Message-ID: <201803292346.S3On01hX%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180329041656.19691-2-mike.kravetz@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
Hi Mike,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.16-rc7 next-20180329]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Mike-Kravetz/hugetlbfs-fix-bug-in-pgoff-overflow-checking/20180329-231724
config: i386-randconfig-x000-201812 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
fs/hugetlbfs/inode.c: In function 'hugetlbfs_file_mmap':
>> fs/hugetlbfs/inode.c:119:35: warning: left shift count >= width of type [-Wshift-count-overflow]
(((1UL << (PAGE_SHIFT + 1)) - 1) << \
^
fs/hugetlbfs/inode.c:144:38: note: in expansion of macro 'PGOFF_LOFFT_MAX'
if ((loff_t)vma->vm_pgoff & (loff_t)PGOFF_LOFFT_MAX)
^~~~~~~~~~~~~~~
vim +119 fs/hugetlbfs/inode.c
110
111 /*
112 * Mask used when checking the page offset value passed in via system
113 * calls. This value will be converted to a loff_t which is signed.
114 * Therefore, we want to check the upper PAGE_SHIFT + 1 bits of the
115 * value. The extra bit (- 1 in the shift value) is to take the sign
116 * bit into account.
117 */
118 #define PGOFF_LOFFT_MAX \
> 119 (((1UL << (PAGE_SHIFT + 1)) - 1) << \
120 ((sizeof(loff_t) * BITS_PER_BYTE) - (PAGE_SHIFT + 1)))
121
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29191 bytes --]
next prev parent reply other threads:[~2018-03-29 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 4:16 [PATCH 0/1] fix regression in hugetlbfs overflow checking Mike Kravetz
2018-03-29 4:16 ` [PATCH 1/1] hugetlbfs: fix bug in pgoff " Mike Kravetz
2018-03-29 16:00 ` kbuild test robot [this message]
2018-03-29 20:42 ` [PATCH 0/1] fix regression in hugetlbfs " Mike Kravetz
2018-03-30 14:54 ` [PATCH v2] hugetlbfs: fix bug in pgoff " Mike Kravetz
2018-04-02 16:21 ` Anders Roxell
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=201803292346.S3On01hX%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=blurbdust@gmail.com \
--cc=dan.rue@linaro.org \
--cc=kbuild-all@01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=stable@vger.kernel.org \
--cc=xieyisheng1@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).