mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Fan Du <fan.du@intel.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org, hch@lst.de,
	dan.j.williams@intel.com, dave.hansen@intel.com,
	mhocko@kernel.org, linux-kernel@vger.kernel.org,
	linux-api@vger.kernel.org, Fan Du <fan.du@intel.com>
Subject: Re: [PATCH 2/2] Add /proc/PID/{smaps, numa_maps} support for DAX
Date: Sat, 28 Oct 2017 10:07:39 +0800	[thread overview]
Message-ID: <201710280935.FrC0bxOA%fengguang.wu@intel.com> (raw)
In-Reply-To: <1508891255-15427-2-git-send-email-fan.du@intel.com>

[-- Attachment #1: Type: text/plain, Size: 3533 bytes --]

Hi Fan,

Thank you for the patch! Yet we hit a small issue.
[auto build test WARNING on linus/master]
[also build test WARNING on v4.14-rc6 next-20171018]
[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/Fan-Du/proc-mm-export-PTE-sizes-directly-in-smaps/20171027-233355
config: i386-randconfig-b0-10280854 (attached as .config)
compiler: gcc-5 (Debian 5.4.1-2) 5.4.1 20160904
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings

All warnings (new ones prefixed by >>):

   In file included from arch/x86/include/asm/processor.h:31:0,
                    from arch/x86/include/asm/cpufeature.h:4,
                    from arch/x86/include/asm/thread_info.h:52,
                    from include/linux/thread_info.h:37,
                    from arch/x86/include/asm/preempt.h:6,
                    from include/linux/preempt.h:80,
                    from include/linux/spinlock.h:50,
                    from include/linux/mmzone.h:7,
                    from include/linux/gfp.h:5,
                    from include/linux/mm.h:9,
                    from fs/proc/task_mmu.c:1:
   fs/proc/task_mmu.c: In function 'smaps_pte_range':
>> include/linux/err.h:40:24: warning: 'page' may be used uninitialized in this function [-Wmaybe-uninitialized]
     return unlikely(!ptr) || IS_ERR_VALUE((unsigned long)ptr);
                           ^
   fs/proc/task_mmu.c:586:15: note: 'page' was declared here
     struct page *page;
                  ^
--
   In file included from arch/x86/include/asm/processor.h:31:0,
                    from arch/x86/include/asm/cpufeature.h:4,
                    from arch/x86/include/asm/thread_info.h:52,
                    from include/linux/thread_info.h:37,
                    from arch/x86/include/asm/preempt.h:6,
                    from include/linux/preempt.h:80,
                    from include/linux/spinlock.h:50,
                    from include/linux/mmzone.h:7,
                    from include/linux/gfp.h:5,
                    from include/linux/mm.h:9,
                    from fs//proc/task_mmu.c:1:
   fs//proc/task_mmu.c: In function 'smaps_pte_range':
>> include/linux/err.h:40:24: warning: 'page' may be used uninitialized in this function [-Wmaybe-uninitialized]
     return unlikely(!ptr) || IS_ERR_VALUE((unsigned long)ptr);
                           ^
   fs//proc/task_mmu.c:586:15: note: 'page' was declared here
     struct page *page;
                  ^

vim +/page +40 include/linux/err.h

^1da177e Linus Torvalds 2005-04-16  37  
a5ed3cee Joe Perches    2014-04-03  38  static inline bool __must_check IS_ERR_OR_NULL(__force const void *ptr)
603c4ba9 Phil Carmody   2009-12-14  39  {
dfffa587 Viresh Kumar   2016-01-15 @40  	return unlikely(!ptr) || IS_ERR_VALUE((unsigned long)ptr);
603c4ba9 Phil Carmody   2009-12-14  41  }
603c4ba9 Phil Carmody   2009-12-14  42  

:::::: The code at line 40 was first introduced by commit
:::::: dfffa587a6bcd84f2087f88e11600b0e8b0aa1ee err.h: add (missing) unlikely() to IS_ERR_OR_NULL()

:::::: TO: Viresh Kumar <viresh.kumar@linaro.org>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>

---
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: 31695 bytes --]

  parent reply	other threads:[~2017-10-28  2:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25  0:27 [PATCHv3 1/2] proc: mm: export PTE sizes directly in smaps Fan Du
2017-10-25  0:27 ` [PATCH 2/2] Add /proc/PID/{smaps, numa_maps} support for DAX Fan Du
2017-10-25  9:30   ` Michal Hocko
2017-10-25 17:14     ` Dave Hansen
2017-10-26 14:16       ` Michal Hocko
2017-10-26 14:24         ` Dave Hansen
2017-10-26 14:31           ` Michal Hocko
2017-10-26 14:51             ` Dave Hansen
2017-10-26 15:07               ` Michal Hocko
2017-10-26 15:56                 ` Dan Williams
2017-10-27  4:00               ` Du, Fan
2017-10-27 10:31                 ` Dan Williams
2017-10-28  2:07   ` kbuild test robot [this message]
2017-10-25  9:28 ` [PATCHv3 1/2] proc: mm: export PTE sizes directly in smaps Michal Hocko
2017-10-26  1:41   ` Du, Fan
2017-10-26  5:13     ` [PATCH v4] Add /proc/PID/smaps support for DAX Fan Du
2017-10-26  9:16       ` Dan Williams
2017-10-27  2:49         ` Du, Fan
2017-10-26 14:03       ` Dave Hansen
2017-10-27  2:47         ` Du, Fan
2017-10-27  8:07           ` Michal Hocko
2017-10-27  8:24             ` Du, Fan
2017-10-27  8:42               ` Michal Hocko
2017-10-27  9:03                 ` Du, Fan
2017-10-27  9:09                   ` Michal Hocko
2017-10-27  9:17                     ` Du, Fan
2017-10-27  9:26                       ` Michal Hocko
2017-10-27  9:34                 ` Du, Fan
2017-10-26 14:19     ` [PATCHv3 1/2] proc: mm: export PTE sizes directly in smaps Michal Hocko
2017-10-26 14:25       ` Dave Hansen
2017-10-29 14:19 ` [lkp-robot] [proc] eb948c71f7: WARNING:at_mm/hugetlb.c:#hugetlb_add_hstate kernel test robot

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=201710280935.FrC0bxOA%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=fan.du@intel.com \
    --cc=hch@lst.de \
    --cc=kbuild-all@01.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®