* mmotm 2019-12-06-19-46 uploaded [not found] <20191206170123.cb3ad1f76af2b48505fabb33@linux-foundation.org> @ 2019-12-07 3:47 ` Andrew Morton 2019-12-09 6:31 ` Shaokun Zhang 2019-12-11 3:14 ` mmotm 2019-12-10-19-14 uploaded Andrew Morton 2019-12-18 4:41 ` mmotm 2019-12-17-20-41 uploaded Andrew Morton 2 siblings, 1 reply; 12+ messages in thread From: Andrew Morton @ 2019-12-07 3:47 UTC (permalink / raw) To: broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr The mm-of-the-moment snapshot 2019-12-06-19-46 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You will need quilt to apply these patches to the latest Linus release (5.x or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in http://ozlabs.org/~akpm/mmotm/series The file broken-out.tar.gz contains two datestamp files: .DATE and .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, followed by the base kernel version against which this patch series is to be applied. This tree is partially included in linux-next. To see which patches are included in linux-next, consult the `series' file. Only the patches within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in linux-next. A full copy of the full kernel tree with the linux-next and mmotm patches already applied is available through git within an hour of the mmotm release. Individual mmotm releases are tagged. The master branch always points to the latest release, so it's constantly rebasing. https://github.com/hnaz/linux-mm The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second) contains daily snapshots of the -mm tree. It is updated more frequently than mmotm, and is untested. A git copy of this tree is also available at https://github.com/hnaz/linux-mm This mmotm tree contains the following patches against 5.4: (patches marked "*" will be included in linux-next) origin.patch * hacking-group-sysrq-kgdb-ubsan-into-generic-kernel-debugging-instruments.patch * hacking-create-submenu-for-arch-special-debugging-options.patch * hacking-group-kernel-data-structures-debugging-together.patch * hacking-move-kernel-testing-and-coverage-options-to-same-submenu.patch * hacking-move-oops-into-lockups-and-hangs.patch * hacking-move-sched_stack_end_check-after-debug_stack_usage.patch * hacking-create-a-submenu-for-scheduler-debugging-options.patch * hacking-move-debug_bugverbose-to-printk-and-dmesg-options.patch * hacking-move-debug_fs-to-generic-kernel-debugging-instruments.patch * lib-fix-kconfig-indentation.patch * kasan-fix-crashes-on-access-to-memory-mapped-by-vm_map_ram.patch * kasan-fix-crashes-on-access-to-memory-mapped-by-vm_map_ram-v2.patch * mm-add-apply_to_existing_pages-helper.patch * mm-add-apply_to_existing_pages-helper-fix.patch * mm-add-apply_to_existing_pages-helper-fix-fix.patch * kasan-use-apply_to_existing_pages-for-releasing-vmalloc-shadow.patch * kasan-use-apply_to_existing_pages-for-releasing-vmalloc-shadow-fix.patch * kasan-dont-assume-percpu-shadow-allocations-will-succeed.patch * mm-vmscan-protect-shrinker-idr-replace-with-config_memcg.patch * proc-kpageflags-prevent-an-integer-overflow-in-stable_page_flags.patch * proc-kpageflags-do-not-use-uninitialized-struct-pages.patch * mm-zsmallocc-fix-the-migrated-zspage-statistics.patch * mm-thp-tweak-reclaim-compaction-effort-of-local-only-and-all-node-allocations.patch * x86-mm-split-vmalloc_sync_all.patch * kcov-fix-struct-layout-for-kcov_remote_arg.patch * memcg-account-security-cred-as-well-to-kmemcg.patch * mm-move_pages-return-valid-node-id-in-status-if-the-page-is-already-on-the-target-node.patch * ramfs-support-o_tmpfile.patch mm.patch * mm-avoid-slub-allocation-while-holding-list_lock.patch * mm-vmscan-expose-cgroup_ino-for-memcg-reclaim-tracepoints.patch * mm-pgmap-use-correct-alignment-when-looking-at-first-pfn-from-a-region.patch * mm-mmap-fix-the-adjusted-length-error.patch * mm-memmap_init-update-variable-name-in-memmap_init_zone.patch * mm-memory_hotplug-shrink-zones-when-offlining-memory.patch * mm-memory_hotplug-poison-memmap-in-remove_pfn_range_from_zone.patch * mm-memory_hotplug-we-always-have-a-zone-in-find_smallestbiggest_section_pfn.patch * mm-memory_hotplug-dont-check-for-all-holes-in-shrink_zone_span.patch * mm-memory_hotplug-drop-local-variables-in-shrink_zone_span.patch * mm-memory_hotplug-cleanup-__remove_pages.patch * mm-oom-avoid-printk-iteration-under-rcu.patch * mm-oom-avoid-printk-iteration-under-rcu-fix.patch * info-task-hung-in-generic_file_write_iter.patch * info-task-hung-in-generic_file_write-fix.patch * kernel-hung_taskc-monitor-killed-tasks.patch * string-add-stracpy-and-stracpy_pad-mechanisms.patch * documentation-checkpatch-prefer-stracpy-strscpy-over-strcpy-strlcpy-strncpy.patch * aio-simplify-read_events.patch * smp_mb__beforeafter_atomic-update-documentation.patch * ipc-mqueuec-remove-duplicated-code.patch * ipc-mqueuec-update-document-memory-barriers.patch * ipc-msgc-update-and-document-memory-barriers.patch * ipc-semc-document-and-update-memory-barriers.patch * ipc-consolidate-all-xxxctl_down-functions.patch linux-next.patch linux-next-git-rejects.patch * drivers-block-null_blk_mainc-fix-layout.patch * drivers-block-null_blk_mainc-fix-uninitialized-var-warnings.patch * pinctrl-fix-pxa2xxc-build-warnings.patch * drivers-tty-serial-sh-scic-suppress-warning.patch * fix-read-buffer-overflow-in-delta-ipc.patch make-sure-nobodys-leaking-resources.patch releasing-resources-with-children.patch mutex-subsystem-synchro-test-module.patch kernel-forkc-export-kernel_thread-to-modules.patch workaround-for-a-pci-restoring-bug.patch ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mmotm 2019-12-06-19-46 uploaded 2019-12-07 3:47 ` mmotm 2019-12-06-19-46 uploaded Andrew Morton @ 2019-12-09 6:31 ` Shaokun Zhang 2019-12-11 1:35 ` Andrew Morton 0 siblings, 1 reply; 12+ messages in thread From: Shaokun Zhang @ 2019-12-09 6:31 UTC (permalink / raw) To: Andrew Morton, broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr, jinyuqi Hi Andrew, About this patch, https://lore.kernel.org/lkml/1573091048-10595-1-git-send-email-zhangshaokun@hisilicon.com/ It is not in linux-next or your trees now, has it been dropped? Thanks, Shaokun On 2019/12/7 11:47, Andrew Morton wrote: > The mm-of-the-moment snapshot 2019-12-06-19-46 has been uploaded to > > http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my -mm patch queue. Uploaded at random hopefully > more than once a week. > > You will need quilt to apply these patches to the latest Linus release (5.x > or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in > http://ozlabs.org/~akpm/mmotm/series > > The file broken-out.tar.gz contains two datestamp files: .DATE and > .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, > followed by the base kernel version against which this patch series is to > be applied. > > This tree is partially included in linux-next. To see which patches are > included in linux-next, consult the `series' file. Only the patches > within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in > linux-next. > > > A full copy of the full kernel tree with the linux-next and mmotm patches > already applied is available through git within an hour of the mmotm > release. Individual mmotm releases are tagged. The master branch always > points to the latest release, so it's constantly rebasing. > > https://github.com/hnaz/linux-mm > > The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second) > contains daily snapshots of the -mm tree. It is updated more frequently > than mmotm, and is untested. > > A git copy of this tree is also available at > > https://github.com/hnaz/linux-mm > > > > This mmotm tree contains the following patches against 5.4: > (patches marked "*" will be included in linux-next) > > origin.patch > * hacking-group-sysrq-kgdb-ubsan-into-generic-kernel-debugging-instruments.patch > * hacking-create-submenu-for-arch-special-debugging-options.patch > * hacking-group-kernel-data-structures-debugging-together.patch > * hacking-move-kernel-testing-and-coverage-options-to-same-submenu.patch > * hacking-move-oops-into-lockups-and-hangs.patch > * hacking-move-sched_stack_end_check-after-debug_stack_usage.patch > * hacking-create-a-submenu-for-scheduler-debugging-options.patch > * hacking-move-debug_bugverbose-to-printk-and-dmesg-options.patch > * hacking-move-debug_fs-to-generic-kernel-debugging-instruments.patch > * lib-fix-kconfig-indentation.patch > * kasan-fix-crashes-on-access-to-memory-mapped-by-vm_map_ram.patch > * kasan-fix-crashes-on-access-to-memory-mapped-by-vm_map_ram-v2.patch > * mm-add-apply_to_existing_pages-helper.patch > * mm-add-apply_to_existing_pages-helper-fix.patch > * mm-add-apply_to_existing_pages-helper-fix-fix.patch > * kasan-use-apply_to_existing_pages-for-releasing-vmalloc-shadow.patch > * kasan-use-apply_to_existing_pages-for-releasing-vmalloc-shadow-fix.patch > * kasan-dont-assume-percpu-shadow-allocations-will-succeed.patch > * mm-vmscan-protect-shrinker-idr-replace-with-config_memcg.patch > * proc-kpageflags-prevent-an-integer-overflow-in-stable_page_flags.patch > * proc-kpageflags-do-not-use-uninitialized-struct-pages.patch > * mm-zsmallocc-fix-the-migrated-zspage-statistics.patch > * mm-thp-tweak-reclaim-compaction-effort-of-local-only-and-all-node-allocations.patch > * x86-mm-split-vmalloc_sync_all.patch > * kcov-fix-struct-layout-for-kcov_remote_arg.patch > * memcg-account-security-cred-as-well-to-kmemcg.patch > * mm-move_pages-return-valid-node-id-in-status-if-the-page-is-already-on-the-target-node.patch > * ramfs-support-o_tmpfile.patch > mm.patch > * mm-avoid-slub-allocation-while-holding-list_lock.patch > * mm-vmscan-expose-cgroup_ino-for-memcg-reclaim-tracepoints.patch > * mm-pgmap-use-correct-alignment-when-looking-at-first-pfn-from-a-region.patch > * mm-mmap-fix-the-adjusted-length-error.patch > * mm-memmap_init-update-variable-name-in-memmap_init_zone.patch > * mm-memory_hotplug-shrink-zones-when-offlining-memory.patch > * mm-memory_hotplug-poison-memmap-in-remove_pfn_range_from_zone.patch > * mm-memory_hotplug-we-always-have-a-zone-in-find_smallestbiggest_section_pfn.patch > * mm-memory_hotplug-dont-check-for-all-holes-in-shrink_zone_span.patch > * mm-memory_hotplug-drop-local-variables-in-shrink_zone_span.patch > * mm-memory_hotplug-cleanup-__remove_pages.patch > * mm-oom-avoid-printk-iteration-under-rcu.patch > * mm-oom-avoid-printk-iteration-under-rcu-fix.patch > * info-task-hung-in-generic_file_write_iter.patch > * info-task-hung-in-generic_file_write-fix.patch > * kernel-hung_taskc-monitor-killed-tasks.patch > * string-add-stracpy-and-stracpy_pad-mechanisms.patch > * documentation-checkpatch-prefer-stracpy-strscpy-over-strcpy-strlcpy-strncpy.patch > * aio-simplify-read_events.patch > * smp_mb__beforeafter_atomic-update-documentation.patch > * ipc-mqueuec-remove-duplicated-code.patch > * ipc-mqueuec-update-document-memory-barriers.patch > * ipc-msgc-update-and-document-memory-barriers.patch > * ipc-semc-document-and-update-memory-barriers.patch > * ipc-consolidate-all-xxxctl_down-functions.patch > linux-next.patch > linux-next-git-rejects.patch > * drivers-block-null_blk_mainc-fix-layout.patch > * drivers-block-null_blk_mainc-fix-uninitialized-var-warnings.patch > * pinctrl-fix-pxa2xxc-build-warnings.patch > * drivers-tty-serial-sh-scic-suppress-warning.patch > * fix-read-buffer-overflow-in-delta-ipc.patch > make-sure-nobodys-leaking-resources.patch > releasing-resources-with-children.patch > mutex-subsystem-synchro-test-module.patch > kernel-forkc-export-kernel_thread-to-modules.patch > workaround-for-a-pci-restoring-bug.patch > > . > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mmotm 2019-12-06-19-46 uploaded 2019-12-09 6:31 ` Shaokun Zhang @ 2019-12-11 1:35 ` Andrew Morton 2019-12-11 1:42 ` Shaokun Zhang 0 siblings, 1 reply; 12+ messages in thread From: Andrew Morton @ 2019-12-11 1:35 UTC (permalink / raw) To: Shaokun Zhang Cc: broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr, jinyuqi On Mon, 9 Dec 2019 14:31:55 +0800 Shaokun Zhang <zhangshaokun@hisilicon.com> wrote: > Hi Andrew, > > About this patch, > https://lore.kernel.org/lkml/1573091048-10595-1-git-send-email-zhangshaokun@hisilicon.com/ > > It is not in linux-next or your trees now, has it been dropped? Yes, I dropped it with a "to be updated" note. Michal is asking for significant changelog updates (at least). ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mmotm 2019-12-06-19-46 uploaded 2019-12-11 1:35 ` Andrew Morton @ 2019-12-11 1:42 ` Shaokun Zhang 2019-12-11 1:58 ` Andrew Morton 0 siblings, 1 reply; 12+ messages in thread From: Shaokun Zhang @ 2019-12-11 1:42 UTC (permalink / raw) To: Andrew Morton Cc: broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr, jinyuqi Hi Andrew, On 2019/12/11 9:35, Andrew Morton wrote: > On Mon, 9 Dec 2019 14:31:55 +0800 Shaokun Zhang <zhangshaokun@hisilicon.com> wrote: > >> Hi Andrew, >> >> About this patch, >> https://lore.kernel.org/lkml/1573091048-10595-1-git-send-email-zhangshaokun@hisilicon.com/ >> >> It is not in linux-next or your trees now, has it been dropped? > > Yes, I dropped it with a "to be updated" note. Michal is asking for > significant changelog updates (at least). Ok, Shall I rebase on 5.5-rc1 and send patch v4? Thanks, Shaokun > > > . > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mmotm 2019-12-06-19-46 uploaded 2019-12-11 1:42 ` Shaokun Zhang @ 2019-12-11 1:58 ` Andrew Morton 0 siblings, 0 replies; 12+ messages in thread From: Andrew Morton @ 2019-12-11 1:58 UTC (permalink / raw) To: Shaokun Zhang Cc: broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr, jinyuqi On Wed, 11 Dec 2019 09:42:09 +0800 Shaokun Zhang <zhangshaokun@hisilicon.com> wrote: > Hi Andrew, > > On 2019/12/11 9:35, Andrew Morton wrote: > > On Mon, 9 Dec 2019 14:31:55 +0800 Shaokun Zhang <zhangshaokun@hisilicon.com> wrote: > > > >> Hi Andrew, > >> > >> About this patch, > >> https://lore.kernel.org/lkml/1573091048-10595-1-git-send-email-zhangshaokun@hisilicon.com/ > >> > >> It is not in linux-next or your trees now, has it been dropped? > > > > Yes, I dropped it with a "to be updated" note. Michal is asking for > > significant changelog updates (at least). > > Ok, Shall I rebase on 5.5-rc1 and send patch v4? Yes please. Please ensure that all review comments have been addressed, either with code changes or with changelog additions. ^ permalink raw reply [flat|nested] 12+ messages in thread
* mmotm 2019-12-10-19-14 uploaded [not found] <20191206170123.cb3ad1f76af2b48505fabb33@linux-foundation.org> 2019-12-07 3:47 ` mmotm 2019-12-06-19-46 uploaded Andrew Morton @ 2019-12-11 3:14 ` Andrew Morton 2019-12-11 16:31 ` mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) Randy Dunlap 2019-12-18 4:41 ` mmotm 2019-12-17-20-41 uploaded Andrew Morton 2 siblings, 1 reply; 12+ messages in thread From: Andrew Morton @ 2019-12-11 3:14 UTC (permalink / raw) To: broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr The mm-of-the-moment snapshot 2019-12-10-19-14 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You will need quilt to apply these patches to the latest Linus release (5.x or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in http://ozlabs.org/~akpm/mmotm/series The file broken-out.tar.gz contains two datestamp files: .DATE and .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, followed by the base kernel version against which this patch series is to be applied. This tree is partially included in linux-next. To see which patches are included in linux-next, consult the `series' file. Only the patches within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in linux-next. A full copy of the full kernel tree with the linux-next and mmotm patches already applied is available through git within an hour of the mmotm release. Individual mmotm releases are tagged. The master branch always points to the latest release, so it's constantly rebasing. https://github.com/hnaz/linux-mm The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second) contains daily snapshots of the -mm tree. It is updated more frequently than mmotm, and is untested. A git copy of this tree is also available at https://github.com/hnaz/linux-mm This mmotm tree contains the following patches against 5.5-rc1: (patches marked "*" will be included in linux-next) origin.patch * kasan-fix-crashes-on-access-to-memory-mapped-by-vm_map_ram.patch * kasan-fix-crashes-on-access-to-memory-mapped-by-vm_map_ram-v2.patch * mm-add-apply_to_existing_pages-helper.patch * mm-add-apply_to_existing_pages-helper-fix.patch * mm-add-apply_to_existing_pages-helper-fix-fix.patch * kasan-use-apply_to_existing_pages-for-releasing-vmalloc-shadow.patch * kasan-use-apply_to_existing_pages-for-releasing-vmalloc-shadow-fix.patch * kasan-dont-assume-percpu-shadow-allocations-will-succeed.patch * mm-vmscan-protect-shrinker-idr-replace-with-config_memcg.patch * lib-kconfigdebug-fix-some-messed-up-configurations.patch * lib-kconfigdebug-fix-some-messed-up-configurations-checkpatch-fixes.patch * proc-kpageflags-prevent-an-integer-overflow-in-stable_page_flags.patch * proc-kpageflags-do-not-use-uninitialized-struct-pages.patch * mm-zsmallocc-fix-the-migrated-zspage-statistics.patch * mm-thp-tweak-reclaim-compaction-effort-of-local-only-and-all-node-allocations.patch * x86-mm-split-vmalloc_sync_all.patch * kcov-fix-struct-layout-for-kcov_remote_arg.patch * memcg-account-security-cred-as-well-to-kmemcg.patch * mm-move_pages-return-valid-node-id-in-status-if-the-page-is-already-on-the-target-node.patch * fs-direct-ioc-include-fs-internalh-for-missing-prototype.patch * fs-nsfsc-include-headers-for-missing-declarations.patch * fs-namespacec-make-to_mnt_ns-static.patch * hexagon-define-ioremap_uc.patch * hexagon-parenthesize-registers-in-asm-predicates.patch * hexagon-work-around-compiler-crash.patch * fs-fix-posix_aclc-kernel-doc-warnings.patch * init-kconfig-enable-o3-for-all-arches.patch * ramfs-support-o_tmpfile.patch mm.patch * mm-avoid-slub-allocation-while-holding-list_lock.patch * mm-cleanup-some-useless-code.patch * mm-vmscan-expose-cgroup_ino-for-memcg-reclaim-tracepoints.patch * mm-pgmap-use-correct-alignment-when-looking-at-first-pfn-from-a-region.patch * mm-mmap-fix-the-adjusted-length-error.patch * mm-memmap_init-update-variable-name-in-memmap_init_zone.patch * mm-memory_hotplug-shrink-zones-when-offlining-memory.patch * mm-memory_hotplug-poison-memmap-in-remove_pfn_range_from_zone.patch * mm-memory_hotplug-we-always-have-a-zone-in-find_smallestbiggest_section_pfn.patch * mm-memory_hotplug-dont-check-for-all-holes-in-shrink_zone_span.patch * mm-memory_hotplug-drop-local-variables-in-shrink_zone_span.patch * mm-memory_hotplug-cleanup-__remove_pages.patch * mm-early_remap-use-%pa-to-print-resource_size_t-variables.patch * mm-oom-avoid-printk-iteration-under-rcu.patch * mm-oom-avoid-printk-iteration-under-rcu-fix.patch * mm-clean-up-obsolete-check-on-space-in-page-flags.patch * info-task-hung-in-generic_file_write_iter.patch * info-task-hung-in-generic_file_write-fix.patch * kernel-hung_taskc-monitor-killed-tasks.patch * lib-zlib-add-s390-hardware-support-for-kernel-zlib_deflate.patch * s390-boot-rename-heap_size-due-to-name-collision.patch * lib-zlib-add-s390-hardware-support-for-kernel-zlib_inflate.patch * s390-boot-add-dfltcc=-kernel-command-line-parameter.patch * lib-zlib-add-zlib_deflate_dfltcc_enabled-function.patch * btrfs-use-larger-zlib-buffer-for-s390-hardware-compression.patch * string-add-stracpy-and-stracpy_pad-mechanisms.patch * documentation-checkpatch-prefer-stracpy-strscpy-over-strcpy-strlcpy-strncpy.patch * elf-smaller-code-generation-around-auxv-vector-fill.patch * elf-fix-start_code-calculation.patch * elf-dont-copy-elf-header-around.patch * execve-warn-if-process-starts-with-executable-stack.patch * io-mapping-use-phys_pfn-macro-in-io_mapping_map_atomic_wc.patch * aio-simplify-read_events.patch * smp_mb__beforeafter_atomic-update-documentation.patch * ipc-mqueuec-remove-duplicated-code.patch * ipc-mqueuec-update-document-memory-barriers.patch * ipc-msgc-update-and-document-memory-barriers.patch * ipc-semc-document-and-update-memory-barriers.patch * ipc-consolidate-all-xxxctl_down-functions.patch linux-next.patch linux-next-build-fix.patch * drivers-block-null_blk_mainc-fix-layout.patch * drivers-block-null_blk_mainc-fix-uninitialized-var-warnings.patch * pinctrl-fix-pxa2xxc-build-warnings.patch * drivers-tty-serial-sh-scic-suppress-warning.patch * fix-read-buffer-overflow-in-delta-ipc.patch make-sure-nobodys-leaking-resources.patch releasing-resources-with-children.patch mutex-subsystem-synchro-test-module.patch kernel-forkc-export-kernel_thread-to-modules.patch workaround-for-a-pci-restoring-bug.patch ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) 2019-12-11 3:14 ` mmotm 2019-12-10-19-14 uploaded Andrew Morton @ 2019-12-11 16:31 ` Randy Dunlap 2019-12-12 18:48 ` Josh Poimboeuf 0 siblings, 1 reply; 12+ messages in thread From: Randy Dunlap @ 2019-12-11 16:31 UTC (permalink / raw) To: Andrew Morton, broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr, Josh Poimboeuf, Peter Zijlstra On 12/10/19 7:14 PM, Andrew Morton wrote: > The mm-of-the-moment snapshot 2019-12-10-19-14 has been uploaded to > > http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my -mm patch queue. Uploaded at random hopefully > more than once a week. > > You will need quilt to apply these patches to the latest Linus release (5.x > or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in > http://ozlabs.org/~akpm/mmotm/series > > The file broken-out.tar.gz contains two datestamp files: .DATE and > .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, > followed by the base kernel version against which this patch series is to > be applied. on x86_64: drivers/hwmon/f71882fg.o: warning: objtool: f71882fg_update_device() falls through to next function show_pwm_auto_point_temp_hyst() drivers/ide/ide-probe.o: warning: objtool: hwif_register_devices() falls through to next function hwif_release_dev() drivers/ide/ide-probe.o: warning: objtool: ide_host_remove() falls through to next function ide_disable_port() -- ~Randy Reported-by: Randy Dunlap <rdunlap@infradead.org> ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) 2019-12-11 16:31 ` mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) Randy Dunlap @ 2019-12-12 18:48 ` Josh Poimboeuf [not found] ` <042c6cd7-c983-03f1-6a79-5642549f57c4@infradead.org> 0 siblings, 1 reply; 12+ messages in thread From: Josh Poimboeuf @ 2019-12-12 18:48 UTC (permalink / raw) To: Randy Dunlap Cc: Andrew Morton, broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr, Peter Zijlstra On Wed, Dec 11, 2019 at 08:31:08AM -0800, Randy Dunlap wrote: > On 12/10/19 7:14 PM, Andrew Morton wrote: > > The mm-of-the-moment snapshot 2019-12-10-19-14 has been uploaded to > > > > http://www.ozlabs.org/~akpm/mmotm/ > > > > mmotm-readme.txt says > > > > README for mm-of-the-moment: > > > > http://www.ozlabs.org/~akpm/mmotm/ > > > > This is a snapshot of my -mm patch queue. Uploaded at random hopefully > > more than once a week. > > > > You will need quilt to apply these patches to the latest Linus release (5.x > > or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in > > http://ozlabs.org/~akpm/mmotm/series > > > > The file broken-out.tar.gz contains two datestamp files: .DATE and > > .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, > > followed by the base kernel version against which this patch series is to > > be applied. > > on x86_64: > > drivers/hwmon/f71882fg.o: warning: objtool: f71882fg_update_device() falls through to next function show_pwm_auto_point_temp_hyst() > drivers/ide/ide-probe.o: warning: objtool: hwif_register_devices() falls through to next function hwif_release_dev() > drivers/ide/ide-probe.o: warning: objtool: ide_host_remove() falls through to next function ide_disable_port() Randy, can you share the .o files? -- Josh ^ permalink raw reply [flat|nested] 12+ messages in thread
[parent not found: <042c6cd7-c983-03f1-6a79-5642549f57c4@infradead.org>]
* Re: mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) [not found] ` <042c6cd7-c983-03f1-6a79-5642549f57c4@infradead.org> @ 2019-12-12 20:58 ` Josh Poimboeuf 2020-01-17 18:11 ` Josh Poimboeuf 0 siblings, 1 reply; 12+ messages in thread From: Josh Poimboeuf @ 2019-12-12 20:58 UTC (permalink / raw) To: Randy Dunlap Cc: Andrew Morton, broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr, Peter Zijlstra On Thu, Dec 12, 2019 at 12:21:17PM -0800, Randy Dunlap wrote: > On 12/12/19 10:48 AM, Josh Poimboeuf wrote: > > On Wed, Dec 11, 2019 at 08:31:08AM -0800, Randy Dunlap wrote: > >> On 12/10/19 7:14 PM, Andrew Morton wrote: > >>> The mm-of-the-moment snapshot 2019-12-10-19-14 has been uploaded to > >>> > >>> http://www.ozlabs.org/~akpm/mmotm/ > >>> > >>> mmotm-readme.txt says > >>> > >>> README for mm-of-the-moment: > >>> > >>> http://www.ozlabs.org/~akpm/mmotm/ > >>> > >>> This is a snapshot of my -mm patch queue. Uploaded at random hopefully > >>> more than once a week. > >>> > >>> You will need quilt to apply these patches to the latest Linus release (5.x > >>> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in > >>> http://ozlabs.org/~akpm/mmotm/series > >>> > >>> The file broken-out.tar.gz contains two datestamp files: .DATE and > >>> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, > >>> followed by the base kernel version against which this patch series is to > >>> be applied. > >> > >> on x86_64: > >> > >> drivers/hwmon/f71882fg.o: warning: objtool: f71882fg_update_device() falls through to next function show_pwm_auto_point_temp_hyst() > >> drivers/ide/ide-probe.o: warning: objtool: hwif_register_devices() falls through to next function hwif_release_dev() > >> drivers/ide/ide-probe.o: warning: objtool: ide_host_remove() falls through to next function ide_disable_port() > > > > Randy, can you share the .o files? > > Sure. They are attached. These look like compiler bugs to me... execution is falling off the edge of the functions for no apparent reason. Could potentially be triggered by the '#define if' trace code. -- Josh ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) 2019-12-12 20:58 ` Josh Poimboeuf @ 2020-01-17 18:11 ` Josh Poimboeuf 2020-01-17 22:15 ` Randy Dunlap 0 siblings, 1 reply; 12+ messages in thread From: Josh Poimboeuf @ 2020-01-17 18:11 UTC (permalink / raw) To: Randy Dunlap Cc: Andrew Morton, broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr, Peter Zijlstra On Thu, Dec 12, 2019 at 02:58:11PM -0600, Josh Poimboeuf wrote: > On Thu, Dec 12, 2019 at 12:21:17PM -0800, Randy Dunlap wrote: > > On 12/12/19 10:48 AM, Josh Poimboeuf wrote: > > > On Wed, Dec 11, 2019 at 08:31:08AM -0800, Randy Dunlap wrote: > > >> On 12/10/19 7:14 PM, Andrew Morton wrote: > > >>> The mm-of-the-moment snapshot 2019-12-10-19-14 has been uploaded to > > >>> > > >>> http://www.ozlabs.org/~akpm/mmotm/ > > >>> > > >>> mmotm-readme.txt says > > >>> > > >>> README for mm-of-the-moment: > > >>> > > >>> http://www.ozlabs.org/~akpm/mmotm/ > > >>> > > >>> This is a snapshot of my -mm patch queue. Uploaded at random hopefully > > >>> more than once a week. > > >>> > > >>> You will need quilt to apply these patches to the latest Linus release (5.x > > >>> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in > > >>> http://ozlabs.org/~akpm/mmotm/series > > >>> > > >>> The file broken-out.tar.gz contains two datestamp files: .DATE and > > >>> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, > > >>> followed by the base kernel version against which this patch series is to > > >>> be applied. > > >> > > >> on x86_64: > > >> > > >> drivers/hwmon/f71882fg.o: warning: objtool: f71882fg_update_device() falls through to next function show_pwm_auto_point_temp_hyst() > > >> drivers/ide/ide-probe.o: warning: objtool: hwif_register_devices() falls through to next function hwif_release_dev() > > >> drivers/ide/ide-probe.o: warning: objtool: ide_host_remove() falls through to next function ide_disable_port() > > > > > > Randy, can you share the .o files? > > > > Sure. They are attached. > > These look like compiler bugs to me... execution is falling off the edge > of the functions for no apparent reason. Could potentially be triggered > by the '#define if' trace code. Randy, do you happen to have a config which triggers the above bugs? I can reduce the test cases and open a GCC bug. -- Josh ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) 2020-01-17 18:11 ` Josh Poimboeuf @ 2020-01-17 22:15 ` Randy Dunlap 0 siblings, 0 replies; 12+ messages in thread From: Randy Dunlap @ 2020-01-17 22:15 UTC (permalink / raw) To: Josh Poimboeuf Cc: Andrew Morton, broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr, Peter Zijlstra On 1/17/20 10:11 AM, Josh Poimboeuf wrote: > On Thu, Dec 12, 2019 at 02:58:11PM -0600, Josh Poimboeuf wrote: >> On Thu, Dec 12, 2019 at 12:21:17PM -0800, Randy Dunlap wrote: >>> On 12/12/19 10:48 AM, Josh Poimboeuf wrote: >>>> On Wed, Dec 11, 2019 at 08:31:08AM -0800, Randy Dunlap wrote: >>>>> On 12/10/19 7:14 PM, Andrew Morton wrote: >>>>>> The mm-of-the-moment snapshot 2019-12-10-19-14 has been uploaded to >>>>>> >>>>>> http://www.ozlabs.org/~akpm/mmotm/ >>>>>> >>>>>> mmotm-readme.txt says >>>>>> >>>>>> README for mm-of-the-moment: >>>>>> >>>>>> http://www.ozlabs.org/~akpm/mmotm/ >>>>>> >>>>>> This is a snapshot of my -mm patch queue. Uploaded at random hopefully >>>>>> more than once a week. >>>>>> >>>>>> You will need quilt to apply these patches to the latest Linus release (5.x >>>>>> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in >>>>>> http://ozlabs.org/~akpm/mmotm/series >>>>>> >>>>>> The file broken-out.tar.gz contains two datestamp files: .DATE and >>>>>> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, >>>>>> followed by the base kernel version against which this patch series is to >>>>>> be applied. >>>>> >>>>> on x86_64: >>>>> >>>>> drivers/hwmon/f71882fg.o: warning: objtool: f71882fg_update_device() falls through to next function show_pwm_auto_point_temp_hyst() >>>>> drivers/ide/ide-probe.o: warning: objtool: hwif_register_devices() falls through to next function hwif_release_dev() >>>>> drivers/ide/ide-probe.o: warning: objtool: ide_host_remove() falls through to next function ide_disable_port() >>>> >>>> Randy, can you share the .o files? >>> >>> Sure. They are attached. >> >> These look like compiler bugs to me... execution is falling off the edge >> of the functions for no apparent reason. Could potentially be triggered >> by the '#define if' trace code. > > Randy, do you happen to have a config which triggers the above bugs? I > can reduce the test cases and open a GCC bug. > No, but I'll try to recreate the issue and get back to you. -- ~Randy ^ permalink raw reply [flat|nested] 12+ messages in thread
* mmotm 2019-12-17-20-41 uploaded [not found] <20191206170123.cb3ad1f76af2b48505fabb33@linux-foundation.org> 2019-12-07 3:47 ` mmotm 2019-12-06-19-46 uploaded Andrew Morton 2019-12-11 3:14 ` mmotm 2019-12-10-19-14 uploaded Andrew Morton @ 2019-12-18 4:41 ` Andrew Morton 2 siblings, 0 replies; 12+ messages in thread From: Andrew Morton @ 2019-12-18 4:41 UTC (permalink / raw) To: broonie, linux-fsdevel, linux-kernel, linux-mm, linux-next, mhocko, mm-commits, sfr The mm-of-the-moment snapshot 2019-12-17-20-41 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You will need quilt to apply these patches to the latest Linus release (5.x or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in http://ozlabs.org/~akpm/mmotm/series The file broken-out.tar.gz contains two datestamp files: .DATE and .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, followed by the base kernel version against which this patch series is to be applied. This tree is partially included in linux-next. To see which patches are included in linux-next, consult the `series' file. Only the patches within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in linux-next. A full copy of the full kernel tree with the linux-next and mmotm patches already applied is available through git within an hour of the mmotm release. Individual mmotm releases are tagged. The master branch always points to the latest release, so it's constantly rebasing. https://github.com/hnaz/linux-mm The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second) contains daily snapshots of the -mm tree. It is updated more frequently than mmotm, and is untested. A git copy of this tree is also available at https://github.com/hnaz/linux-mm This mmotm tree contains the following patches against 5.5-rc2: (patches marked "*" will be included in linux-next) origin.patch * kasan-fix-crashes-on-access-to-memory-mapped-by-vm_map_ram.patch * kasan-fix-crashes-on-access-to-memory-mapped-by-vm_map_ram-v2.patch * mm-add-apply_to_existing_pages-helper.patch * mm-add-apply_to_existing_pages-helper-fix.patch * mm-add-apply_to_existing_pages-helper-fix-fix.patch * mm-add-apply_to_existing_pages-helper-fix-fix-fix.patch * kasan-use-apply_to_existing_pages-for-releasing-vmalloc-shadow.patch * kasan-use-apply_to_existing_pages-for-releasing-vmalloc-shadow-fix.patch * kasan-dont-assume-percpu-shadow-allocations-will-succeed.patch * mm-vmscan-protect-shrinker-idr-replace-with-config_memcg.patch * lib-kconfigdebug-fix-some-messed-up-configurations.patch * lib-kconfigdebug-fix-some-messed-up-configurations-checkpatch-fixes.patch * proc-kpageflags-prevent-an-integer-overflow-in-stable_page_flags.patch * proc-kpageflags-do-not-use-uninitialized-struct-pages.patch * mm-zsmallocc-fix-the-migrated-zspage-statistics.patch * mm-thp-tweak-reclaim-compaction-effort-of-local-only-and-all-node-allocations.patch * x86-mm-split-vmalloc_sync_all.patch * kcov-fix-struct-layout-for-kcov_remote_arg.patch * memcg-account-security-cred-as-well-to-kmemcg.patch * mm-move_pages-return-valid-node-id-in-status-if-the-page-is-already-on-the-target-node.patch * fs-direct-ioc-include-fs-internalh-for-missing-prototype.patch * fs-nsfsc-include-headers-for-missing-declarations.patch * fs-namespacec-make-to_mnt_ns-static.patch * hexagon-define-ioremap_uc.patch * hexagon-parenthesize-registers-in-asm-predicates.patch * hexagon-work-around-compiler-crash.patch * fs-fix-posix_aclc-kernel-doc-warnings.patch * revert-ipcsem-remove-uneeded-sem_undo_list-lock-usage-in-exit_sem.patch * mm-oom-fix-pgtables-units-mismatch-in-killed-process-message.patch * mm-gup-fix-memory-leak-in-__gup_benchmark_ioctl.patch * mm-gup-fix-memory-leak-in-__gup_benchmark_ioctl-fix.patch * mm-fix-uninitialized-memmaps-on-a-partially-populated-last-section.patch * fs-proc-pagec-allow-inspection-of-last-section-and-fix-end-detection.patch * mm-initialize-memmap-of-unavailable-memory-directly.patch * mm-hugetlb-defer-freeing-of-huge-pages-if-in-non-task-context.patch * mm-memory_hotplug-dont-free-usage-map-when-removing-a-re-added-early-section.patch * ocfs2-call-journal-flush-to-mark-journal-as-empty-after-journal-recovery-when-mount.patch * init-kconfig-enable-o3-for-all-arches.patch * ramfs-support-o_tmpfile.patch mm.patch * mm-avoid-slub-allocation-while-holding-list_lock.patch * mm-cleanup-some-useless-code.patch * mm-vmscan-expose-cgroup_ino-for-memcg-reclaim-tracepoints.patch * mm-pgmap-use-correct-alignment-when-looking-at-first-pfn-from-a-region.patch * mm-mmap-fix-the-adjusted-length-error.patch * mm-memmap_init-update-variable-name-in-memmap_init_zone.patch * mm-memory_hotplug-shrink-zones-when-offlining-memory.patch * mm-memory_hotplug-poison-memmap-in-remove_pfn_range_from_zone.patch * mm-memory_hotplug-we-always-have-a-zone-in-find_smallestbiggest_section_pfn.patch * mm-memory_hotplug-dont-check-for-all-holes-in-shrink_zone_span.patch * mm-memory_hotplug-drop-local-variables-in-shrink_zone_span.patch * mm-memory_hotplug-cleanup-__remove_pages.patch * mm-early_remap-use-%pa-to-print-resource_size_t-variables.patch * mm-oom-avoid-printk-iteration-under-rcu.patch * mm-oom-avoid-printk-iteration-under-rcu-fix.patch * mm-hugetlb-controller-for-cgroups-v2.patch * mm-clean-up-obsolete-check-on-space-in-page-flags.patch * mm-remove-dead-code-totalram_pages_set.patch * info-task-hung-in-generic_file_write_iter.patch * info-task-hung-in-generic_file_write-fix.patch * kernel-hung_taskc-monitor-killed-tasks.patch * lib-zlib-add-s390-hardware-support-for-kernel-zlib_deflate.patch * s390-boot-rename-heap_size-due-to-name-collision.patch * lib-zlib-add-s390-hardware-support-for-kernel-zlib_inflate.patch * s390-boot-add-dfltcc=-kernel-command-line-parameter.patch * lib-zlib-add-zlib_deflate_dfltcc_enabled-function.patch * btrfs-use-larger-zlib-buffer-for-s390-hardware-compression.patch * string-add-stracpy-and-stracpy_pad-mechanisms.patch * documentation-checkpatch-prefer-stracpy-strscpy-over-strcpy-strlcpy-strncpy.patch * elf-smaller-code-generation-around-auxv-vector-fill.patch * elf-fix-start_code-calculation.patch * elf-dont-copy-elf-header-around.patch * elf-better-codegen-around-current-mm.patch * elf-make-bad_addr-unlikely.patch * init-mainc-log-arguments-and-environment-passed-to-init.patch * init-mainc-remove-unnecessary-repair_env_string-in-do_initcall_level.patch * init-mainc-fix-quoted-value-handling-in-unknown_bootoption.patch * execve-warn-if-process-starts-with-executable-stack.patch * io-mapping-use-phys_pfn-macro-in-io_mapping_map_atomic_wc.patch * aio-simplify-read_events.patch * smp_mb__beforeafter_atomic-update-documentation.patch * ipc-mqueuec-remove-duplicated-code.patch * ipc-mqueuec-update-document-memory-barriers.patch * ipc-msgc-update-and-document-memory-barriers.patch * ipc-semc-document-and-update-memory-barriers.patch * ipc-consolidate-all-xxxctl_down-functions.patch linux-next.patch linux-next-git-rejects.patch * drivers-block-null_blk_mainc-fix-layout.patch * drivers-block-null_blk_mainc-fix-uninitialized-var-warnings.patch * pinctrl-fix-pxa2xxc-build-warnings.patch * mm-remove-__krealloc.patch * drivers-tty-serial-sh-scic-suppress-warning.patch * fix-read-buffer-overflow-in-delta-ipc.patch make-sure-nobodys-leaking-resources.patch releasing-resources-with-children.patch mutex-subsystem-synchro-test-module.patch kernel-forkc-export-kernel_thread-to-modules.patch workaround-for-a-pci-restoring-bug.patch ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2020-01-17 22:16 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <20191206170123.cb3ad1f76af2b48505fabb33@linux-foundation.org> 2019-12-07 3:47 ` mmotm 2019-12-06-19-46 uploaded Andrew Morton 2019-12-09 6:31 ` Shaokun Zhang 2019-12-11 1:35 ` Andrew Morton 2019-12-11 1:42 ` Shaokun Zhang 2019-12-11 1:58 ` Andrew Morton 2019-12-11 3:14 ` mmotm 2019-12-10-19-14 uploaded Andrew Morton 2019-12-11 16:31 ` mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) Randy Dunlap 2019-12-12 18:48 ` Josh Poimboeuf [not found] ` <042c6cd7-c983-03f1-6a79-5642549f57c4@infradead.org> 2019-12-12 20:58 ` Josh Poimboeuf 2020-01-17 18:11 ` Josh Poimboeuf 2020-01-17 22:15 ` Randy Dunlap 2019-12-18 4:41 ` mmotm 2019-12-17-20-41 uploaded Andrew Morton
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).