LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com> To: Greg Thelen <gthelen@google.com> Cc: kbuild-all@01.org, Wang Long <wanglong19@meituan.com>, Michal Hocko <mhocko@kernel.org>, Andrew Morton <akpm@linux-foundation.org>, Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>, npiggin@gmail.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Greg Thelen <gthelen@google.com> Subject: Re: [PATCH v2] writeback: safer lock nesting Date: Sun, 8 Apr 2018 02:56:50 +0800 [thread overview] Message-ID: <201804080259.VS5U0mKT%fengguang.wu@intel.com> (raw) In-Reply-To: <20180406185546.189305-1-gthelen@google.com> [-- Attachment #1: Type: text/plain, Size: 6265 bytes --] Hi Greg, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.16] [cannot apply to next-20180406] [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/Greg-Thelen/writeback-safer-lock-nesting/20180407-122200 config: mips-db1xxx_defconfig (attached as .config) compiler: mipsel-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # save the attached .config to linux build tree make.cross ARCH=mips 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/mips/include/asm/atomic.h:17:0, from include/linux/atomic.h:5, from arch/mips/include/asm/processor.h:14, from arch/mips/include/asm/thread_info.h:16, from include/linux/thread_info.h:38, from include/asm-generic/preempt.h:5, from ./arch/mips/include/generated/asm/preempt.h:1, from include/linux/preempt.h:81, from include/linux/spinlock.h:51, from mm/page-writeback.c:16: mm/page-writeback.c: In function 'account_page_redirty': >> include/linux/irqflags.h:80:3: warning: 'cookie.flags' may be used uninitialized in this function [-Wmaybe-uninitialized] arch_local_irq_restore(flags); \ ^~~~~~~~~~~~~~~~~~~~~~ mm/page-writeback.c:2504:25: note: 'cookie.flags' was declared here struct wb_lock_cookie cookie; ^~~~~~ In file included from arch/mips/include/asm/atomic.h:17:0, from include/linux/atomic.h:5, from arch/mips/include/asm/processor.h:14, from arch/mips/include/asm/thread_info.h:16, from include/linux/thread_info.h:38, from include/asm-generic/preempt.h:5, from ./arch/mips/include/generated/asm/preempt.h:1, from include/linux/preempt.h:81, from include/linux/spinlock.h:51, from mm/page-writeback.c:16: mm/page-writeback.c: In function '__cancel_dirty_page': >> include/linux/irqflags.h:80:3: warning: 'cookie.flags' may be used uninitialized in this function [-Wmaybe-uninitialized] arch_local_irq_restore(flags); \ ^~~~~~~~~~~~~~~~~~~~~~ mm/page-writeback.c:2616:25: note: 'cookie.flags' was declared here struct wb_lock_cookie cookie; ^~~~~~ In file included from arch/mips/include/asm/atomic.h:17:0, from include/linux/atomic.h:5, from arch/mips/include/asm/processor.h:14, from arch/mips/include/asm/thread_info.h:16, from include/linux/thread_info.h:38, from include/asm-generic/preempt.h:5, from ./arch/mips/include/generated/asm/preempt.h:1, from include/linux/preempt.h:81, from include/linux/spinlock.h:51, from mm/page-writeback.c:16: mm/page-writeback.c: In function 'clear_page_dirty_for_io': >> include/linux/irqflags.h:80:3: warning: 'cookie.flags' may be used uninitialized in this function [-Wmaybe-uninitialized] arch_local_irq_restore(flags); \ ^~~~~~~~~~~~~~~~~~~~~~ mm/page-writeback.c:2656:25: note: 'cookie.flags' was declared here struct wb_lock_cookie cookie; ^~~~~~ vim +80 include/linux/irqflags.h 81d68a96 Steven Rostedt 2008-05-12 66 df9ee292 David Howells 2010-10-07 67 /* df9ee292 David Howells 2010-10-07 68 * Wrap the arch provided IRQ routines to provide appropriate checks. df9ee292 David Howells 2010-10-07 69 */ df9ee292 David Howells 2010-10-07 70 #define raw_local_irq_disable() arch_local_irq_disable() df9ee292 David Howells 2010-10-07 71 #define raw_local_irq_enable() arch_local_irq_enable() df9ee292 David Howells 2010-10-07 72 #define raw_local_irq_save(flags) \ df9ee292 David Howells 2010-10-07 73 do { \ df9ee292 David Howells 2010-10-07 74 typecheck(unsigned long, flags); \ df9ee292 David Howells 2010-10-07 75 flags = arch_local_irq_save(); \ df9ee292 David Howells 2010-10-07 76 } while (0) df9ee292 David Howells 2010-10-07 77 #define raw_local_irq_restore(flags) \ df9ee292 David Howells 2010-10-07 78 do { \ df9ee292 David Howells 2010-10-07 79 typecheck(unsigned long, flags); \ df9ee292 David Howells 2010-10-07 @80 arch_local_irq_restore(flags); \ df9ee292 David Howells 2010-10-07 81 } while (0) df9ee292 David Howells 2010-10-07 82 #define raw_local_save_flags(flags) \ df9ee292 David Howells 2010-10-07 83 do { \ df9ee292 David Howells 2010-10-07 84 typecheck(unsigned long, flags); \ df9ee292 David Howells 2010-10-07 85 flags = arch_local_save_flags(); \ df9ee292 David Howells 2010-10-07 86 } while (0) df9ee292 David Howells 2010-10-07 87 #define raw_irqs_disabled_flags(flags) \ df9ee292 David Howells 2010-10-07 88 ({ \ df9ee292 David Howells 2010-10-07 89 typecheck(unsigned long, flags); \ df9ee292 David Howells 2010-10-07 90 arch_irqs_disabled_flags(flags); \ df9ee292 David Howells 2010-10-07 91 }) df9ee292 David Howells 2010-10-07 92 #define raw_irqs_disabled() (arch_irqs_disabled()) df9ee292 David Howells 2010-10-07 93 #define raw_safe_halt() arch_safe_halt() de30a2b3 Ingo Molnar 2006-07-03 94 :::::: The code at line 80 was first introduced by commit :::::: df9ee29270c11dba7d0fe0b83ce47a4d8e8d2101 Fix IRQ flag handling naming :::::: TO: David Howells <dhowells@redhat.com> :::::: CC: David Howells <dhowells@redhat.com> --- 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: 22089 bytes --]
next prev parent reply other threads:[~2018-04-07 18:57 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <157ed606-4a61-508b-d26a-2f5d638f39bb@meituan.com> 2018-04-02 11:50 ` [RFC] Is it correctly that the usage for spin_{lock|unlock}_irq in clear_page_dirty_for_io Wang Long 2018-04-03 12:03 ` Michal Hocko 2018-04-03 23:12 ` Greg Thelen 2018-04-04 6:31 ` Wang Long 2018-04-06 8:03 ` [PATCH] writeback: safer lock nesting Greg Thelen 2018-04-06 8:07 ` Michal Hocko 2018-04-06 18:49 ` Greg Thelen 2018-04-06 18:55 ` [PATCH v2] " Greg Thelen 2018-04-07 18:56 ` kbuild test robot [this message] 2018-04-10 0:59 ` [PATCH v3] " Greg Thelen 2018-04-10 6:33 ` Michal Hocko 2018-04-10 20:48 ` Andrew Morton 2018-04-11 5:50 ` Michal Hocko 2018-04-10 8:14 ` Wang Long 2018-04-11 0:40 ` Greg Thelen 2018-04-10 20:37 ` Andrew Morton 2018-04-11 1:03 ` Greg Thelen 2018-04-11 8:46 ` [PATCH v4] " Greg Thelen 2018-04-10 13:50 ` [PATCH] " Sasha Levin 2018-04-11 2:44 ` Wang Long 2018-04-11 3:13 ` Greg Thelen 2018-04-11 8:45 ` [PATCH for-4.4] " Greg Thelen 2018-04-11 8:50 ` Greg Thelen
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=201804080259.VS5U0mKT%fengguang.wu@intel.com \ --to=lkp@intel.com \ --cc=akpm@linux-foundation.org \ --cc=gthelen@google.com \ --cc=hannes@cmpxchg.org \ --cc=kbuild-all@01.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@kernel.org \ --cc=npiggin@gmail.com \ --cc=tj@kernel.org \ --cc=wanglong19@meituan.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: linkBe 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).