Re: linux-next: build warning after merge of the akpm tree

On 1/28/2021 2:16 PM, Stephen Rothwell wrote: > Hi all, > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > lib/stackdepot.c: In function 'is_stack_depot_disabled': > lib/stackdepot.c:154:2: warning: ignoring return value of

linux-next: build warning after merge of the akpm tree

Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) produced this warning: lib/stackdepot.c: In function 'is_stack_depot_disabled': lib/stackdepot.c:154:2: warning: ignoring return value of 'kstrtobool' declared with attribute 'warn_unused_result'

Re: linux-next: build warning after merge of the akpm tree

Hi Michael, On Thu, 10 Dec 2020 11:19:45 +1100 Michael Ellerman wrote: > > Stephen Rothwell writes: > > > > On Wed, 09 Dec 2020 15:44:35 +1100 Michael Ellerman > > wrote: > >> > >> They should really be in DATA_DATA or similar shouldn't they? > > > > No other architecture appears t need

Re: linux-next: build warning after merge of the akpm tree

Stephen Rothwell writes: > Hi Michael, > > On Wed, 09 Dec 2020 15:44:35 +1100 Michael Ellerman > wrote: >> >> They should really be in DATA_DATA or similar shouldn't they? > > No other architecture appears t need them ... Any arch with orphan-handling=warn should see them I thought? cheers

Re: linux-next: build warning after merge of the akpm tree

On Tue, Dec 08, 2020 at 11:01:57PM +1100, Stephen Rothwell wrote: > Hi Stephen, > > On Fri, 4 Dec 2020 21:00:00 +1100 Stephen Rothwell > wrote: > > > > Hi all, > > > > After merging the akpm tree, today's linux-next build (powerpc > > allyesconfig) produced warnings like this: > > > > ld:

Re: linux-next: build warning after merge of the akpm tree

Hi all, On Tue, 8 Dec 2020 23:01:57 +1100 Stephen Rothwell wrote: > > I will try the following patch tomorrow: > > From: Stephen Rothwell > Date: Tue, 8 Dec 2020 22:58:24 +1100 > Subject: [PATCH] powerpc: Add .data..Lubsan_data*/.data..Lubsan_type* > sections explicitly > > Similarly to

Re: linux-next: build warning after merge of the akpm tree

On Mon, Dec 7, 2020 at 1:52 PM Marco Elver wrote: > > On Mon, 7 Dec 2020 at 13:38, 'Dmitry Vyukov' via kasan-dev > wrote: > > On Mon, Dec 7, 2020 at 1:08 PM Dmitry Vyukov wrote: > > > > > Hi all, > > > > > > > > > > After merging the akpm tree, today's linux-next build (powerpc > > > > >

Re: linux-next: build warning after merge of the akpm tree

Hi Michael, On Wed, 09 Dec 2020 15:44:35 +1100 Michael Ellerman wrote: > > They should really be in DATA_DATA or similar shouldn't they? No other architecture appears t need them ... -- Cheers, Stephen Rothwell pgpHxEGuWLRlX.pgp Description: OpenPGP digital signature

Re: linux-next: build warning after merge of the akpm tree

Stephen Rothwell writes: > Hi Stephen, > > On Fri, 4 Dec 2020 21:00:00 +1100 Stephen Rothwell > wrote: >> >> Hi all, >> >> After merging the akpm tree, today's linux-next build (powerpc >> allyesconfig) produced warnings like this: >> >> ld: warning: orphan section `.data..Lubsan_data177'

Re: linux-next: build warning after merge of the akpm tree

Hi Stephen, On Fri, 4 Dec 2020 21:00:00 +1100 Stephen Rothwell wrote: > > Hi all, > > After merging the akpm tree, today's linux-next build (powerpc > allyesconfig) produced warnings like this: > > ld: warning: orphan section `.data..Lubsan_data177' from >

Re: linux-next: build warning after merge of the akpm tree

On Mon, 7 Dec 2020 at 13:38, 'Dmitry Vyukov' via kasan-dev wrote: > On Mon, Dec 7, 2020 at 1:08 PM Dmitry Vyukov wrote: > > > > Hi all, > > > > > > > > After merging the akpm tree, today's linux-next build (powerpc > > > > allyesconfig) produced warnings like this: > > > > > > > >

Re: linux-next: build warning after merge of the akpm tree

On Mon, Dec 7, 2020 at 1:08 PM Dmitry Vyukov wrote: > > > Hi all, > > > > > > After merging the akpm tree, today's linux-next build (powerpc > > > allyesconfig) produced warnings like this: > > > > > > kernel/kcov.c:296:14: warning: conflicting types for built-in function > > >

Re: linux-next: build warning after merge of the akpm tree

On Sat, Dec 5, 2020 at 6:19 AM Andrew Morton wrote: > > On Fri, 4 Dec 2020 21:00:00 +1100 Stephen Rothwell > wrote: > > > Hi all, > > > > After merging the akpm tree, today's linux-next build (powerpc > > allyesconfig) produced warnings like this: > > > > kernel/kcov.c:296:14: warning:

Re: linux-next: build warning after merge of the akpm tree

Hi Andrew, On Fri, 4 Dec 2020 21:19:23 -0800 Andrew Morton wrote: > > Odd. clang wants that signature, according to > https://clang.llvm.org/docs/SanitizerCoverage.html. But gcc seems to > want a different signature. Beats me - best I can do is to cc various > likely culprits ;) > > Which

Re: linux-next: build warning after merge of the akpm tree

On Fri, 4 Dec 2020 21:00:00 +1100 Stephen Rothwell wrote: > Hi all, > > After merging the akpm tree, today's linux-next build (powerpc > allyesconfig) produced warnings like this: > > kernel/kcov.c:296:14: warning: conflicting types for built-in function > '__sanitizer_cov_trace_switch';

linux-next: build warning after merge of the akpm tree

Hi all, After merging the akpm tree, today's linux-next build (powerpc allyesconfig) produced warnings like this: kernel/kcov.c:296:14: warning: conflicting types for built-in function '__sanitizer_cov_trace_switch'; expected 'void(long unsigned int, void *)' [-Wbuiltin-declaration-mismatch]

Re: linux-next: build warning after merge of the akpm tree

On 30/11/2018 5:40 am, Stephen Rothwell wrote: > After merging the akpm tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > lib/lzo/lzo1x_compress.c: In function 'lzo1x_1_do_compress': > lib/lzo/lzo1x_compress.c:239:14: warning: 'm_pos' may be used uninitialized >

Re: linux-next: build warning after merge of the akpm tree

On 30/11/2018 5:40 am, Stephen Rothwell wrote: > After merging the akpm tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > lib/lzo/lzo1x_compress.c: In function 'lzo1x_1_do_compress': > lib/lzo/lzo1x_compress.c:239:14: warning: 'm_pos' may be used uninitialized >

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: lib/lzo/lzo1x_compress.c: In function 'lzo1x_1_do_compress': lib/lzo/lzo1x_compress.c:239:14: warning: 'm_pos' may be used uninitialized in this function [-Wmaybe-uninitialized]

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: lib/lzo/lzo1x_compress.c: In function 'lzo1x_1_do_compress': lib/lzo/lzo1x_compress.c:239:14: warning: 'm_pos' may be used uninitialized in this function [-Wmaybe-uninitialized]

Re: linux-next: build warning after merge of the akpm tree

On Tue, Aug 1, 2017 at 8:15 AM, Huang, Ying wrote: > From 7a7ff76d7bcbd7affda169b29abcf3dafa38052e Mon Sep 17 00:00:00 2001 > From: Huang Ying > Date: Tue, 1 Aug 2017 14:12:21 +0800 > Subject: [PATCH] mm, THP, swap: Silence a compiler warning > > To

Re: linux-next: build warning after merge of the akpm tree

On Tue, Aug 1, 2017 at 8:15 AM, Huang, Ying wrote: > From 7a7ff76d7bcbd7affda169b29abcf3dafa38052e Mon Sep 17 00:00:00 2001 > From: Huang Ying > Date: Tue, 1 Aug 2017 14:12:21 +0800 > Subject: [PATCH] mm, THP, swap: Silence a compiler warning > > To fix the following compiler warning, > >

Re: linux-next: build warning after merge of the akpm tree

Hi, Stephen, Thanks for reporting. Stephen Rothwell writes: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > mm/swapfile.c: In function 'reuse_swap_page': > mm/swapfile.c:1429:16: warning: 'offset'

Re: linux-next: build warning after merge of the akpm tree

Hi, Stephen, Thanks for reporting. Stephen Rothwell writes: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > mm/swapfile.c: In function 'reuse_swap_page': > mm/swapfile.c:1429:16: warning: 'offset' may be used

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/swapfile.c: In function 'reuse_swap_page': mm/swapfile.c:1429:16: warning: 'offset' may be used uninitialized in this function [-Wmaybe-uninitialized] unsigned long offset;

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/swapfile.c: In function 'reuse_swap_page': mm/swapfile.c:1429:16: warning: 'offset' may be used uninitialized in this function [-Wmaybe-uninitialized] unsigned long offset;

Re: linux-next: build warning after merge of the akpm tree

Thanks, I just found it. On Mon, Jun 26, 2017 at 04:30:12PM +1000, Stephen Rothwell wrote: >Hi Andrew, > >After merging the akpm tree, today's linux-next build (x86_64 >allmodconfig) produced this warning: > >mm/memory_hotplug.c: In function 'move_pfn_range_to_zone': >mm/memory_hotplug.c:891:16:

Re: linux-next: build warning after merge of the akpm tree

Thanks, I just found it. On Mon, Jun 26, 2017 at 04:30:12PM +1000, Stephen Rothwell wrote: >Hi Andrew, > >After merging the akpm tree, today's linux-next build (x86_64 >allmodconfig) produced this warning: > >mm/memory_hotplug.c: In function 'move_pfn_range_to_zone': >mm/memory_hotplug.c:891:16:

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/memory_hotplug.c: In function 'move_pfn_range_to_zone': mm/memory_hotplug.c:891:16: warning: unused variable 'i' [-Wunused-variable] unsigned long i; ^ Introduced

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/memory_hotplug.c: In function 'move_pfn_range_to_zone': mm/memory_hotplug.c:891:16: warning: unused variable 'i' [-Wunused-variable] unsigned long i; ^ Introduced

Re: linux-next: build warning after merge of the akpm tree

On Tue, 2014-05-20 at 07:36 +1000, Stephen Rothwell wrote: > Hi, > > On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso wrote: > > > > On Mon, 2014-05-19 at 18:13 +1000, Stephen Rothwell wrote: > > > Hi Andrew, > > > > > > After merging the akpm tree, today's linux-next build (arm > > >

Re: linux-next: build warning after merge of the akpm tree

Hi, On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso wrote: > > On Mon, 2014-05-19 at 18:13 +1000, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm tree, today's linux-next build (arm > > multi_v7_defconfig) produced these warnings: > > > > > >

Re: linux-next: build warning after merge of the akpm tree

On Mon, 19 May 2014 13:56:20 -0700 Davidlohr Bueso wrote: > On Mon, 2014-05-19 at 12:48 -0700, Andrew Morton wrote: > > On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso wrote: > > > > > > Presumably a result of commit fe2038c57c03 ("rwsem: Support optimistic > > > > spinning"). > > > > > >

Re: linux-next: build warning after merge of the akpm tree

On Mon, 2014-05-19 at 12:48 -0700, Andrew Morton wrote: > On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso wrote: > > > > Presumably a result of commit fe2038c57c03 ("rwsem: Support optimistic > > > spinning"). > > > > If CONFIG_SMP, we add two new fields to the rwsem structure > >

Re: linux-next: build warning after merge of the akpm tree

On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso wrote: > > Presumably a result of commit fe2038c57c03 ("rwsem: Support optimistic > > spinning"). > > If CONFIG_SMP, we add two new fields to the rwsem structure > (include/linux/rwsem.h) and likewise we update the > __RWSEM_INITIALIZER(name)

Re: linux-next: build warning after merge of the akpm tree

Hi Stephen, On Mon, 2014-05-19 at 18:13 +1000, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (arm > multi_v7_defconfig) produced these warnings: > > > ipc/ipcns_notifier.c:22:8: warning: excess elements in struct initializer > [enabled by

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) produced these warnings: ipc/ipcns_notifier.c:22:8: warning: excess elements in struct initializer [enabled by default] ipc/ipcns_notifier.c:22:8: warning: (near initialization for 'ipcns_chain.rwsem')

Re: linux-next: build warning after merge of the akpm tree

On Mon, 19 May 2014 13:56:20 -0700 Davidlohr Bueso davidl...@hp.com wrote: On Mon, 2014-05-19 at 12:48 -0700, Andrew Morton wrote: On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso davidl...@hp.com wrote: Presumably a result of commit fe2038c57c03 (rwsem: Support optimistic

Re: linux-next: build warning after merge of the akpm tree

Hi, On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso davidl...@hp.com wrote: On Mon, 2014-05-19 at 18:13 +1000, Stephen Rothwell wrote: Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) produced these warnings:

Re: linux-next: build warning after merge of the akpm tree

On Tue, 2014-05-20 at 07:36 +1000, Stephen Rothwell wrote: Hi, On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso davidl...@hp.com wrote: On Mon, 2014-05-19 at 18:13 +1000, Stephen Rothwell wrote: Hi Andrew, After merging the akpm tree, today's linux-next build (arm

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) produced these warnings: ipc/ipcns_notifier.c:22:8: warning: excess elements in struct initializer [enabled by default] ipc/ipcns_notifier.c:22:8: warning: (near initialization for 'ipcns_chain.rwsem')

Re: linux-next: build warning after merge of the akpm tree

Hi Stephen, On Mon, 2014-05-19 at 18:13 +1000, Stephen Rothwell wrote: Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) produced these warnings: ipc/ipcns_notifier.c:22:8: warning: excess elements in struct initializer [enabled by default]

Re: linux-next: build warning after merge of the akpm tree

On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso davidl...@hp.com wrote: Presumably a result of commit fe2038c57c03 (rwsem: Support optimistic spinning). If CONFIG_SMP, we add two new fields to the rwsem structure (include/linux/rwsem.h) and likewise we update the

Re: linux-next: build warning after merge of the akpm tree

On Mon, 2014-05-19 at 12:48 -0700, Andrew Morton wrote: On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso davidl...@hp.com wrote: Presumably a result of commit fe2038c57c03 (rwsem: Support optimistic spinning). If CONFIG_SMP, we add two new fields to the rwsem structure

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/fat/inode.c: In function 'fat_zero_falloc_area': fs/fat/inode.c:170:11: warning: comparison of distinct pointer types lacks a cast [enabled by default] Introduced by commit

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/fat/inode.c: In function 'fat_zero_falloc_area': fs/fat/inode.c:170:11: warning: comparison of distinct pointer types lacks a cast [enabled by default] Introduced by commit fat:

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc44x_defconfig) produced these warnings: ipc/util.c: In function 'ipc_init': ipc/util.c:105:2: warning: statement with no effect [-Wunused-value] mm/slub.c: In function 'kmem_cache_init': mm/slub.c:3600:2: warning:

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: include/linux/genalloc.h:109:3: warning: 'struct device' declared inside parameter list [enabled by default] include/linux/genalloc.h:109:3: warning: its scope is only this

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: include/linux/genalloc.h:109:3: warning: 'struct device' declared inside parameter list [enabled by default] include/linux/genalloc.h:109:3: warning: its scope is only this

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc44x_defconfig) produced these warnings: ipc/util.c: In function 'ipc_init': ipc/util.c:105:2: warning: statement with no effect [-Wunused-value] mm/slub.c: In function 'kmem_cache_init': mm/slub.c:3600:2: warning:

linux-next: build warning after merge of the akpm tree

Stephen, The following email is an updated patch which should fix the warning you're seeing on architectures where sizeof is unsigned int rather than unsigned long. This completely replaces the ef25bb0fa6e2 patch. Andrew, if you'd prefer a single-line fixup patch, I can send you that instead.

linux-next: build warning after merge of the akpm tree

Stephen, The following email is an updated patch which should fix the warning you're seeing on architectures where sizeof is unsigned int rather than unsigned long. This completely replaces the ef25bb0fa6e2 patch. Andrew, if you'd prefer a single-line fixup patch, I can send you that instead.

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc44x_defconfig) produced this warning: block/partitions/efi.c: In function 'is_gpt_valid': block/partitions/efi.c:324:3: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc44x_defconfig) produced this warning: block/partitions/efi.c: In function 'is_gpt_valid': block/partitions/efi.c:324:3: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type

Re: linux-next: build warning after merge of the akpm tree

On 01/23/2013 02:33 PM, Stephen Rothwell wrote: Hi Andrew, After merging the akpm tree, today's linux-next build (arm defconfig) produced this warning: mm/page_alloc.c:4477:23: warning: 'sanitize_zone_movable_limit' defined but not used [-Wunused-function] Introduced by commit "page_alloc:

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (arm defconfig) produced this warning: mm/page_alloc.c:4477:23: warning: 'sanitize_zone_movable_limit' defined but not used [-Wunused-function] Introduced by commit "page_alloc: introduce zone_movable_limit[] to keep movable

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (arm defconfig) produced this warning: mm/page_alloc.c:4477:23: warning: 'sanitize_zone_movable_limit' defined but not used [-Wunused-function] Introduced by commit page_alloc: introduce zone_movable_limit[] to keep movable limit

Re: linux-next: build warning after merge of the akpm tree

On 01/23/2013 02:33 PM, Stephen Rothwell wrote: Hi Andrew, After merging the akpm tree, today's linux-next build (arm defconfig) produced this warning: mm/page_alloc.c:4477:23: warning: 'sanitize_zone_movable_limit' defined but not used [-Wunused-function] Introduced by commit page_alloc:

Re: linux-next: build warning after merge of the akpm tree

On Fri, Nov 9, 2012 at 3:43 AM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > allnoconfig - among others) produced this warning: > > drivers/of/fdt.c: In function 'of_scan_flat_dt': > drivers/of/fdt.c:490:10: warning: assignment discards

Re: linux-next: build warning after merge of the akpm tree

On Fri, Nov 9, 2012 at 3:43 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allnoconfig - among others) produced this warning: drivers/of/fdt.c: In function 'of_scan_flat_dt': drivers/of/fdt.c:490:10: warning:

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allnoconfig - among others) produced this warning: drivers/of/fdt.c: In function 'of_scan_flat_dt': drivers/of/fdt.c:490:10: warning: assignment discards 'const' qualifier from pointer target type [enabled by default]

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allnoconfig - among others) produced this warning: drivers/of/fdt.c: In function 'of_scan_flat_dt': drivers/of/fdt.c:490:10: warning: assignment discards 'const' qualifier from pointer target type [enabled by default]

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/rmap.c: In function 'try_to_unmap_cluster': mm/rmap.c:1364:9: warning: unused variable 'pud' [-Wunused-variable] mm/rmap.c:1363:9: warning: unused variable 'pgd' [-Wunused-variable]

linux-next: build warning after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/rmap.c: In function 'try_to_unmap_cluster': mm/rmap.c:1364:9: warning: unused variable 'pud' [-Wunused-variable] mm/rmap.c:1363:9: warning: unused variable 'pgd' [-Wunused-variable]