From a370ac98d706f0613da989429edba1920275f384 Mon Sep 17 00:00:00 2001 From: Salvatore Bonaccorso Date: Mon, 22 Jun 2020 15:14:16 +0200 Subject: [PATCH] [rt] Update to 4.19.120-rt52 --- debian/changelog | 1 + ...M-at91-add-TCB-registers-definitions.patch | 9 +- ...ers-Add-a-new-driver-for-the-Atmel-A.patch | 11 +- ...ers-timer-atmel-tcb-add-clockevent-d.patch | 11 +- ...drivers-atmel-pit-make-option-silent.patch | 11 +- ...at91-Implement-clocksource-selection.patch | 11 +- ...onfigs-at91-use-new-TCB-timer-driver.patch | 11 +- .../0007-ARM-configs-at91-unselect-PIT.patch | 11 +- ...ts-Move-pending-table-allocation-to-.patch | 19 +-- ...-convert-worker-lock-to-raw-spinlock.patch | 11 +- ...m-qi-simplify-CGR-allocation-freeing.patch | 11 +- ...obustify-CFS-bandwidth-timer-locking.patch | 11 +- ...012-arm-Convert-arm-boot_lock-to-raw.patch | 11 +- ...-let-setaffinity-unmask-threaded-EOI.patch | 11 +- ...irqsave-in-cgroup_rstat_flush_locked.patch | 11 +- ...lize-cookie-hash-table-raw-spinlocks.patch | 11 +- ...mbus-include-header-for-get_irq_regs.patch | 11 +- ...de-irqflags.h-for-raw_local_irq_save.patch | 11 +- .../0018-efi-Allow-efi-runtime.patch | 13 +- ...fi-drop-task_lock-from-efi_switch_mm.patch | 13 +- ...e_layout-before-altenates-are-applie.patch | 11 +- ...-phandle-cache-outside-of-the-devtre.patch | 11 +- ...ake-quarantine_lock-a-raw_spinlock_t.patch | 11 +- ...xpedited-GP-parallelization-cleverne.patch | 11 +- ...-kmemleak_lock-to-raw-spinlock-on-RT.patch | 11 +- ...-replace-seqcount_t-with-a-seqlock_t.patch | 11 +- ...vide-a-pointer-to-the-valid-CPU-mask.patch | 13 +- ...ernel-sched-core-add-migrate_disable.patch | 13 +- ...sable-Add-export_symbol_gpl-for-__mi.patch | 11 +- ...o-not-disable-enable-clocks-in-a-row.patch | 11 +- ...B-Allow-higher-clock-rates-for-clock.patch | 11 +- ...31-timekeeping-Split-jiffies-seqlock.patch | 11 +- ...2-signal-Revert-ptrace-preempt-magic.patch | 13 +- ...et-sched-Use-msleep-instead-of-yield.patch | 11 +- ...rq-remove-BUG_ON-irqs_disabled-check.patch | 11 +- ...do-no-disable-interrupts-in-giveback.patch | 11 +- ...rovide-PREEMPT_RT_BASE-config-switch.patch | 11 +- ...sable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch | 11 +- ...abel-disable-if-stop_machine-is-used.patch | 11 +- ...config-options-which-are-not-RT-comp.patch | 11 +- .../0040-lockdep-disable-self-test.patch | 11 +- .../0041-mm-Allow-only-slub-on-RT.patch | 11 +- ...locking-Disable-spin-on-owner-for-RT.patch | 11 +- ...043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch | 11 +- ...044-rcu-make-RCU_BOOST-default-on-RT.patch | 11 +- ...-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch | 11 +- ...46-net-core-disable-NET_RX_BUSY_POLL.patch | 11 +- ...0047-arm-disable-NEON-in-kernel-mode.patch | 11 +- ...0048-powerpc-Use-generic-rwsem-on-RT.patch | 11 +- ...ble-in-kernel-MPIC-emulation-for-PRE.patch | 11 +- .../0050-powerpc-Disable-highmem-on-RT.patch | 11 +- .../0051-mips-Disable-highmem-on-RT.patch | 11 +- ...86-Use-generic-rwsem_spinlocks-on-rt.patch | 11 +- ...ds-trigger-disable-CPU-trigger-on-RT.patch | 11 +- ...rop-K8-s-driver-from-beeing-selected.patch | 11 +- .../patches-rt/0055-md-disable-bcache.patch | 11 +- ...6-efi-Disable-runtime-services-on-RT.patch | 13 +- ...0057-printk-Add-a-printk-kill-switch.patch | 11 +- ..._early_printk-boot-param-to-help-wit.patch | 11 +- ...pt-Provide-preempt_-_-no-rt-variants.patch | 11 +- ...-migrate_disable-enable-in-different.patch | 11 +- .../0061-rt-Add-local-irq-locks.patch | 11 +- ...provide-get-put-_locked_ptr-variants.patch | 11 +- ...catterlist-Do-not-disable-irqs-on-RT.patch | 11 +- ...-x86-Delay-calling-signals-in-atomic.patch | 15 ++- ...ignal-delay-calling-signals-on-32bit.patch | 11 +- ...head-Replace-bh_uptodate_lock-for-rt.patch | 17 ++- ...-state-lock-and-journal-head-lock-rt.patch | 13 +- ...st_bl-Make-list-head-locking-RT-safe.patch | 11 +- ...-list_bl-fixup-bogus-lockdep-warning.patch | 11 +- .../0070-genirq-Disable-irqpoll-on-rt.patch | 11 +- ...-genirq-Force-interrupt-thread-on-RT.patch | 11 +- ...d-zone-lock-while-freeing-pages-from.patch | 13 +- ...d-zone-lock-while-freeing-pages-from.patch | 13 +- ...B-change-list_lock-to-raw_spinlock_t.patch | 13 +- ...ving-back-empty-slubs-to-IRQ-enabled.patch | 13 +- ...page_alloc-rt-friendly-per-cpu-pages.patch | 13 +- ...077-mm-swap-Convert-to-percpu-locked.patch | 13 +- ...m-perform-lru_add_drain_all-remotely.patch | 11 +- ...t-per-cpu-variables-with-preempt-dis.patch | 11 +- ...plit-page-table-locks-for-vector-pag.patch | 11 +- .../0081-mm-Enable-SLUB-for-RT.patch | 13 +- ...0082-slub-Enable-irqs-for-__GFP_WAIT.patch | 13 +- .../0083-slub-Disable-SLUB_CPU_PARTIAL.patch | 11 +- ...n-t-call-schedule_work_on-in-preempt.patch | 11 +- ...place-local_irq_disable-with-local-l.patch | 11 +- ...oc-copy-with-get_cpu_var-and-locking.patch | 11 +- ...le-preemption-__split_large_page-aft.patch | 11 +- .../0088-radix-tree-use-local-locks.patch | 11 +- ...9-timers-Prepare-for-full-preemption.patch | 11 +- ...090-x86-kvm-Require-const-tsc-for-RT.patch | 15 ++- ...ec-Don-t-use-completion-s-wait-queue.patch | 16 +-- .../0092-wait.h-include-atomic.h.patch | 11 +- ...mple-Simple-work-queue-implemenation.patch | 11 +- ...-a-shit-statement-in-SWORK_EVENT_PEN.patch | 11 +- ...95-completion-Use-simple-wait-queues.patch | 15 ++- .../0096-fs-aio-simple-simple-work.patch | 11 +- ...id-schedule_work-with-interrupts-dis.patch | 11 +- ...ate-hrtimer_init-hrtimer_init_sleepe.patch | 11 +- ...099-hrtimers-Prepare-full-preemption.patch | 11 +- ...s-by-default-into-the-softirq-contex.patch | 15 ++- ...air-Make-the-hrtimers-non-hard-again.patch | 11 +- ...-schedule_work-call-to-helper-thread.patch | 11 +- ...te-change-before-hrtimer_cancel-in-d.patch | 11 +- ...timers-Thread-posix-cpu-timers-on-rt.patch | 13 +- ...ched-Move-task_struct-cleanup-to-RCU.patch | 13 +- ...-number-of-task-migrations-per-batch.patch | 11 +- .../0107-sched-Move-mmdrop-to-RCU-on-RT.patch | 11 +- ...e-stack-kprobe-clean-up-to-__put_tas.patch | 11 +- ...state-for-tasks-blocked-on-sleeping-.patch | 17 ++- ...ount-rcu_preempt_depth-on-RT-in-migh.patch | 11 +- ...-proper-LOCK_OFFSET-for-cond_resched.patch | 11 +- .../0112-sched-Disable-TTWU_QUEUE-on-RT.patch | 11 +- ...Only-wake-up-idle-workers-if-not-blo.patch | 11 +- ...ease-the-nr-of-migratory-tasks-when-.patch | 11 +- ...-hotplug-Lightweight-get-online-cpus.patch | 13 +- ...e-disabled-counter-to-tracing-output.patch | 11 +- .../0117-lockdep-Make-it-RT-aware.patch | 17 ++- ...tasklets-from-going-into-infinite-sp.patch | 11 +- ...eemption-after-reenabling-interrupts.patch | 21 +-- ...oftirq-Disable-softirq-stacks-for-RT.patch | 11 +- .../0121-softirq-Split-softirq-locks.patch | 13 +- ...-use-local_bh_disable-in-netif_rx_ni.patch | 15 ++- ...abling-of-softirq-processing-in-irq-.patch | 11 +- ...plit-timer-softirqs-out-of-ksoftirqd.patch | 11 +- ...cal_softirq_pending-messages-if-ksof.patch | 11 +- ...cal_softirq_pending-messages-if-task.patch | 11 +- .../0127-rtmutex-trylock-is-okay-on-RT.patch | 11 +- ...-nfs-turn-rmdir_sem-into-a-semaphore.patch | 11 +- ...he-various-new-futex-race-conditions.patch | 11 +- ...on-when-a-requeued-RT-task-times-out.patch | 11 +- ...k-unlock-symetry-versus-pi_lock-and-.patch | 11 +- .../0132-pid.h-include-atomic.h.patch | 11 +- ...arm-include-definition-for-cpumask_t.patch | 11 +- ...ure-Do-NOT-include-rwlock.h-directly.patch | 13 +- ...35-rtmutex-Add-rtmutex_lock_killable.patch | 11 +- ...0136-rtmutex-Make-lock_killable-work.patch | 11 +- ...spinlock-Split-the-lock-types-header.patch | 11 +- .../0138-rtmutex-Avoid-include-hell.patch | 11 +- ...-rbtree-don-t-include-the-rcu-header.patch | 11 +- ...tex-Provide-rt_mutex_slowlock_locked.patch | 11 +- ...ockdep-less-version-of-rt_mutex-s-lo.patch | 11 +- ...tex-add-sleeping-lock-implementation.patch | 13 +- ...utex-implementation-based-on-rtmutex.patch | 11 +- ...wsem-implementation-based-on-rtmutex.patch | 11 +- ...lock-implementation-based-on-rtmutex.patch | 11 +- ...-preserve-state-like-a-sleeping-lock.patch | 11 +- .../0147-rtmutex-wire-up-RT-s-locking.patch | 11 +- ...utex-add-ww_mutex-addon-for-mutex-rt.patch | 11 +- .../0149-kconfig-Add-PREEMPT_RT_FULL.patch | 11 +- ...-fix-deadlock-in-device-mapper-block.patch | 11 +- ...utex-Flush-block-plug-on-__down_read.patch | 11 +- ...re-init-the-wait_lock-in-rt_mutex_in.patch | 11 +- ...ace-fix-ptrace-vs-tasklist_lock-race.patch | 13 +- ...mutex-annotate-sleeping-lock-context.patch | 13 +- ...sable-fallback-to-preempt_disable-in.patch | 13 +- ...eck-for-__LINUX_SPINLOCK_TYPES_H-on-.patch | 11 +- .../0157-rcu-Frob-softirq-test.patch | 11 +- ...58-rcu-Merge-RCU-bh-into-RCU-preempt.patch | 11 +- ...ke-ksoftirqd-do-RCU-quiescent-states.patch | 11 +- ...nate-softirq-processing-from-rcutree.patch | 11 +- ...-use-cpu_online-instead-custom-check.patch | 11 +- ...place-local_irqsave-with-a-locallock.patch | 11 +- ..._normal_after_boot-by-default-for-RT.patch | 11 +- ...erial-omap-Make-the-locking-RT-aware.patch | 11 +- ...al-pl011-Make-the-locking-work-on-RT.patch | 11 +- ...-explicitly-initialize-the-flags-var.patch | 11 +- ...mprove-the-serial-console-PASS_LIMIT.patch | 11 +- ...0-don-t-take-the-trylock-during-oops.patch | 11 +- ...wsem-Remove-preempt_disable-variants.patch | 11 +- ...ate_mm-by-preempt_-disable-enable-_r.patch | 13 +- ...back-explicit-INIT_HLIST_BL_HEAD-ini.patch | 11 +- ...e-preemption-on-i_dir_seq-s-write-si.patch | 11 +- ...e-of-local-lock-in-multi_cpu-decompr.patch | 11 +- ...rmal-Defer-thermal-wakups-to-threads.patch | 11 +- ...e-preemption-around-local_bh_disable.patch | 11 +- ...poll-Do-not-disable-preemption-on-RT.patch | 11 +- ...er-preempt-disable-region-which-suck.patch | 23 ++-- .../0178-block-mq-use-cpu_light.patch | 11 +- ...ock-mq-do-not-invoke-preempt_disable.patch | 11 +- ...k-mq-don-t-complete-requests-via-IPI.patch | 13 +- ...-Make-raid5_percpu-handling-RT-aware.patch | 11 +- .../0182-rt-Introduce-cpu_chill.patch | 11 +- ...rtimer-Don-t-lose-state-in-cpu_chill.patch | 11 +- ...chill-save-task-state-in-saved_state.patch | 11 +- ...e-blk_queue_usage_counter_release-in.patch | 13 +- ...-block-Use-cpu_chill-for-retry-loops.patch | 17 ++- ...cache-Use-cpu_chill-in-trylock-loops.patch | 13 +- ...t-Use-cpu_chill-instead-of-cpu_relax.patch | 11 +- ...use-swait_queue-instead-of-waitqueue.patch | 11 +- .../0190-workqueue-Use-normal-rcu.patch | 11 +- ...cal-irq-lock-instead-of-irq-disable-.patch | 11 +- ...t-workqueue-versus-ata-piix-livelock.patch | 11 +- ...tangle-worker-accounting-from-rqlock.patch | 11 +- .../0194-debugobjects-Make-RT-aware.patch | 11 +- .../0195-seqlock-Prevent-rt-starvation.patch | 11 +- ...vc_xprt_do_enqueue-use-get_cpu_light.patch | 13 +- ...0197-net-Use-skbufhead-with-raw-lock.patch | 27 ++-- ...recursion-to-per-task-variable-on-RT.patch | 17 ++- ...y-to-delegate-processing-a-softirq-t.patch | 15 ++- ...ake-qdisc-s-busylock-in-__dev_xmit_s.patch | 13 +- ...Qdisc-use-a-seqlock-instead-seqcount.patch | 11 +- ...-missing-serialization-in-ip_send_un.patch | 11 +- .../0203-net-add-a-lock-around-icmp_sk.patch | 11 +- ...schedule_irqoff-disable-interrupts-o.patch | 17 ++- ...-push-most-work-into-softirq-context.patch | 11 +- .../0206-printk-Make-rt-aware.patch | 11 +- ...n-t-try-to-print-from-IRQ-NMI-region.patch | 11 +- ...intk-Drop-the-logbuf_lock-more-often.patch | 11 +- ...n-translation-section-permission-fau.patch | 11 +- ...-irq_set_irqchip_state-documentation.patch | 11 +- ...wngrade-preempt_disable-d-region-to-.patch | 11 +- ...-preemp_disable-in-addition-to-local.patch | 11 +- ...13-kgdb-serial-Short-term-workaround.patch | 11 +- ...-sysfs-Add-sys-kernel-realtime-entry.patch | 11 +- .../0215-mm-rt-kmap_atomic-scheduling.patch | 13 +- ...highmem-Add-a-already-used-pte-check.patch | 11 +- .../0217-arm-highmem-Flush-tlb-on-unmap.patch | 11 +- .../0218-arm-Enable-highmem-for-rt.patch | 11 +- .../0219-scsi-fcoe-Make-RT-aware.patch | 11 +- ...ypto-Reduce-preempt-disabled-regions.patch | 11 +- ...-preempt-disabled-regions-more-algos.patch | 11 +- ...ypto-limit-more-FPU-enabled-sections.patch | 11 +- ...-serialize-RT-percpu-scratch-buffer-.patch | 11 +- ...d-a-lock-instead-preempt_disable-loc.patch | 11 +- ...andom_bytes-for-RT_FULL-in-init_oops.patch | 11 +- ...ackprotector-Avoid-random-pool-on-rt.patch | 11 +- .../0227-random-Make-it-work-on-rt.patch | 17 ++- ...28-cpu-hotplug-Implement-CPU-pinning.patch | 15 ++- ...ed-user-tasks-to-be-awakened-to-the-.patch | 11 +- ...duct-tape-RT-rwlock-usage-for-non-RT.patch | 13 +- ...ove-preemption-disabling-in-netif_rx.patch | 17 ++- ...r-local_irq_disable-kmalloc-headache.patch | 11 +- ...-users-of-napi_alloc_cache-against-r.patch | 11 +- ...rialize-xt_write_recseq-sections-on-.patch | 11 +- ...Add-a-mutex-around-devnet_rename_seq.patch | 13 +- ...-Only-do-hardirq-context-test-for-ra.patch | 11 +- ...-fix-warnings-due-to-missing-PREEMPT.patch | 11 +- ...ched-Add-support-for-lazy-preemption.patch | 19 +-- ...39-ftrace-Fix-trace-header-alignment.patch | 11 +- ...0240-x86-Support-for-lazy-preemption.patch | 13 +- ...-properly-check-against-preempt-mask.patch | 11 +- ...-use-proper-return-label-on-32bit-x8.patch | 13 +- ...-arm-Add-support-for-lazy-preemption.patch | 11 +- ...erpc-Add-support-for-lazy-preemption.patch | 11 +- ...-arch-arm64-Add-lazy-preempt-support.patch | 13 +- ...c-Protect-send_msg-with-a-local-lock.patch | 11 +- ...am-Replace-bit-spinlocks-with-rtmute.patch | 11 +- ...-t-disable-preemption-in-zcomp_strea.patch | 11 +- ...-zcomp_stream_get-smp_processor_id-u.patch | 11 +- ...50-tpm_tis-fix-stall-after-iowrite-s.patch | 11 +- ...t-deferral-of-watchdogd-wakeup-on-RT.patch | 17 ++- ...Use-preempt_disable-enable_rt-where-.patch | 11 +- ...al_lock-unlock_irq-in-intel_pipe_upd.patch | 11 +- .../0254-drm-i915-disable-tracing-on-RT.patch | 11 +- ...M_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch | 11 +- ...roups-use-simple-wait-in-css_release.patch | 11 +- ...vert-callback_lock-to-raw_spinlock_t.patch | 11 +- ...-a-locallock-instead-preempt_disable.patch | 11 +- ...rkqueue-Prevent-deadlock-stall-on-RT.patch | 11 +- ...t-tasks-to-cache-one-sigqueue-struct.patch | 15 ++- ...0261-Add-localversion-for-RT-release.patch | 11 +- ...iommu-Use-a-locallock-instead-local_.patch | 11 +- .../0263-powerpc-reshuffle-TIF-bits.patch | 11 +- ...-Convert-show_lock-to-raw_spinlock_t.patch | 11 +- ...isable-interrupts-independently-of-t.patch | 11 +- ...-Fix-a-lockup-in-wait_for_completion.patch | 11 +- ...7-kthread-add-a-global-worker-thread.patch | 13 +- ...-arm-imx6-cpuidle-Use-raw_spinlock_t.patch | 11 +- ...to-change-rcu_normal_after_boot-on-R.patch | 11 +- ...chtec-fix-stream_open.cocci-warnings.patch | 11 +- ...-Drop-a-preempt_disable_rt-statement.patch | 11 +- ...notification-of-canceling-timers-on-.patch | 11 +- ...ure-lock-unlock-symetry-versus-pi_lo.patch | 11 +- ...-bug-on-when-a-requeued-RT-task-time.patch | 11 +- ...andle-the-various-new-futex-race-con.patch | 11 +- ...karound-migrate_disable-enable-in-di.patch | 11 +- ...-Make-the-futex_hash_bucket-lock-raw.patch | 11 +- ...futex-Delay-deallocation-of-pi_state.patch | 11 +- ...disable-preemption-in-zswap_frontswa.patch | 11 +- debian/patches-rt/0280-revert-aio.patch | 11 +- .../0281-fs-aio-simple-simple-work.patch | 11 +- debian/patches-rt/0282-revert-thermal.patch | 11 +- ...rmal-Defer-thermal-wakups-to-threads.patch | 11 +- debian/patches-rt/0284-revert-block.patch | 13 +- ...e-blk_queue_usage_counter_release-in.patch | 13 +- debian/patches-rt/0286-workqueue-rework.patch | 15 ++- ...0287-i2c-exynos5-Remove-IRQF_ONESHOT.patch | 11 +- ...0288-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch | 11 +- ...nsure-inactive_timer-runs-in-hardirq.patch | 11 +- ...temp-make-pkg_temp_lock-a-raw-spinlo.patch | 11 +- ...lock_t-instread-disabling-preemption.patch | 11 +- ...t-the-timer-expire-in-hardirq-contex.patch | 11 +- ...k-preemption-level-before-looking-at.patch | 11 +- ..._ONCE-to-access-timer-base-in-hrimer.patch | 11 +- ...ab-the-expiry-lock-for-non-soft-hrti.patch | 11 +- ...using-hrtimer_grab_expiry_lock-on-mi.patch | 11 +- ...ssing-bracket-and-hide-migration_bas.patch | 11 +- ...lock-expiry-lock-in-the-early-return.patch | 11 +- ...s-enable-Use-sleeping_lock-to-annota.patch | 13 +- ..._allowed_ptr-Check-cpus_mask-not-cpu.patch | 11 +- ...Remove-dead-__migrate_disabled-check.patch | 11 +- ...e-disable-Protect-cpus_ptr-with-lock.patch | 11 +- ...processor_id-Don-t-use-cpumask_equal.patch | 11 +- ...utex_hash_bucket-spinlock_t-again-an.patch | 11 +- ...Clean-pi_blocked_on-in-the-error-cas.patch | 11 +- ...ib-ubsan-Don-t-seralize-UBSAN-report.patch | 11 +- ...the-lock-of-kmemleak_object-to-raw_s.patch | 11 +- ...igrate_enable-Use-select_fallback_rq.patch | 11 +- ...ched-Lazy-migrate_disable-processing.patch | 19 +-- ...grate_enable-Use-stop_one_cpu_nowait.patch | 11 +- ...alize-split-page-table-locks-for-vec.patch | 11 +- ...nlock_t-and-rwlock_t-a-RCU-section-o.patch | 11 +- ...te_enable-must-access-takedown_cpu_t.patch | 13 +- ...r_id-Adjust-check_preemption_disable.patch | 11 +- ...able-Busy-loop-until-the-migration-r.patch | 11 +- ...fd-Use-a-seqlock-instead-of-seqcount.patch | 11 +- ...ate_enable-Use-per-cpu-cpu_stop_work.patch | 11 +- ...igrate_enable-Remove-__schedule-call.patch | 11 +- ...ve-misplaced-local_unlock_irqrestore.patch | 11 +- ...Include-header-for-the-current-macro.patch | 11 +- ...preempt_disable-in-vmw_fifo_ping_hos.patch | 11 +- ...empt_lazy-and-migrate_disable-counte.patch | 11 +- ...-flags-parameter-from-calls-to-ubsan.patch | 11 +- ...cking-of-IRQ_WORK_LAZY-flag-set-on-n.patch | 11 +- .../0325-Linux-4.19.115-rt48-REBASE.patch | 20 --- ...s-a-race-resulting-in-double-enqueue.patch | 123 ++++++++++++++++++ ...c-for-when-grabbing-softirq_expiry_l.patch | 53 ++++++++ .../0327-Linux-4.19.120-rt52-REBASE.patch | 24 ++++ debian/patches-rt/series | 4 +- 330 files changed, 2588 insertions(+), 1438 deletions(-) delete mode 100644 debian/patches-rt/0325-Linux-4.19.115-rt48-REBASE.patch create mode 100644 debian/patches-rt/0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch create mode 100644 debian/patches-rt/0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch create mode 100644 debian/patches-rt/0327-Linux-4.19.120-rt52-REBASE.patch diff --git a/debian/changelog b/debian/changelog index dd20096a9..500c179f1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -148,6 +148,7 @@ linux (4.19.120-1) UNRELEASED; urgency=medium * apparmor: don't try to replace stale label in ptraceme check (Closes: #963493) * nfsd: apply umask on fs without ACL support (Closes: #962254) + * [rt] Update to 4.19.120-rt52 -- Salvatore Bonaccorso Wed, 13 May 2020 17:44:43 +0200 diff --git a/debian/patches-rt/0001-ARM-at91-add-TCB-registers-definitions.patch b/debian/patches-rt/0001-ARM-at91-add-TCB-registers-definitions.patch index b3bb134c9..e16896840 100644 --- a/debian/patches-rt/0001-ARM-at91-add-TCB-registers-definitions.patch +++ b/debian/patches-rt/0001-ARM-at91-add-TCB-registers-definitions.patch @@ -1,8 +1,9 @@ -From 119971df8e4c3a8550b9b7479e5e409dc03f07b6 Mon Sep 17 00:00:00 2001 +From 94c546b56877133a33b6e344bfe3ee7f698d069a Mon Sep 17 00:00:00 2001 +Message-Id: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:18 +0200 -Subject: [PATCH 001/325] ARM: at91: add TCB registers definitions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 001/327] ARM: at91: add TCB registers definitions +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Add registers and bits definitions for the timer counter blocks found on Atmel ARM SoCs. @@ -206,5 +207,5 @@ index 000000000000..657e234b1483 + +#endif /* __SOC_ATMEL_TCB_H */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0002-clocksource-drivers-Add-a-new-driver-for-the-Atmel-A.patch b/debian/patches-rt/0002-clocksource-drivers-Add-a-new-driver-for-the-Atmel-A.patch index 78419c826..3f1a9e5b2 100644 --- a/debian/patches-rt/0002-clocksource-drivers-Add-a-new-driver-for-the-Atmel-A.patch +++ b/debian/patches-rt/0002-clocksource-drivers-Add-a-new-driver-for-the-Atmel-A.patch @@ -1,9 +1,12 @@ -From aba8ef8111b7a69621be5dd2358f8163dc4a2263 Mon Sep 17 00:00:00 2001 +From f4ba1e096c17024b919eed42e42b95906f78e9d4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:19 +0200 -Subject: [PATCH 002/325] clocksource/drivers: Add a new driver for the Atmel +Subject: [PATCH 002/327] clocksource/drivers: Add a new driver for the Atmel ARM TC blocks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Add a driver for the Atmel Timer Counter Blocks. This driver provides a clocksource and two clockevent devices. @@ -481,5 +484,5 @@ index 000000000000..21fbe430f91b +} +TIMER_OF_DECLARE(atmel_tcb_clksrc, "atmel,tcb-timer", tcb_clksrc_init); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0003-clocksource-drivers-timer-atmel-tcb-add-clockevent-d.patch b/debian/patches-rt/0003-clocksource-drivers-timer-atmel-tcb-add-clockevent-d.patch index 641bfab2b..d9c69a8a2 100644 --- a/debian/patches-rt/0003-clocksource-drivers-timer-atmel-tcb-add-clockevent-d.patch +++ b/debian/patches-rt/0003-clocksource-drivers-timer-atmel-tcb-add-clockevent-d.patch @@ -1,9 +1,12 @@ -From 8cbcac5c2b1a35f8c81134219ef264b8c9f9e9d7 Mon Sep 17 00:00:00 2001 +From 606f1ed4ca9ae32b18b73646e197f5bccddd24e8 Mon Sep 17 00:00:00 2001 +Message-Id: <606f1ed4ca9ae32b18b73646e197f5bccddd24e8.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:20 +0200 -Subject: [PATCH 003/325] clocksource/drivers: timer-atmel-tcb: add clockevent +Subject: [PATCH 003/327] clocksource/drivers: timer-atmel-tcb: add clockevent device on separate channel -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Add an other clockevent device that uses a separate TCB channel when available. @@ -267,5 +270,5 @@ index 21fbe430f91b..63ce3b69338a 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0004-clocksource-drivers-atmel-pit-make-option-silent.patch b/debian/patches-rt/0004-clocksource-drivers-atmel-pit-make-option-silent.patch index 91c58dd40..420329e9d 100644 --- a/debian/patches-rt/0004-clocksource-drivers-atmel-pit-make-option-silent.patch +++ b/debian/patches-rt/0004-clocksource-drivers-atmel-pit-make-option-silent.patch @@ -1,8 +1,11 @@ -From 5e34b2461c24c7ec974e6c5f33e4431a3260b2c1 Mon Sep 17 00:00:00 2001 +From 5a68ab1574e969066b19959eea4f840184d8c234 Mon Sep 17 00:00:00 2001 +Message-Id: <5a68ab1574e969066b19959eea4f840184d8c234.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:21 +0200 -Subject: [PATCH 004/325] clocksource/drivers: atmel-pit: make option silent -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 004/327] clocksource/drivers: atmel-pit: make option silent +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz To conform with the other option, make the ATMEL_PIT option silent so it can be selected from the platform @@ -32,5 +35,5 @@ index 0ab22e7037f4..34b07047b91f 100644 config ATMEL_ST bool "Atmel ST timer support" if COMPILE_TEST -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch b/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch index 29c1b5d8d..2a57fe58c 100644 --- a/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch +++ b/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch @@ -1,8 +1,11 @@ -From 7c8bbf08ffe494d923710239c313474054189139 Mon Sep 17 00:00:00 2001 +From 8c3d27d3b3cd3aecb7c92684466a2edab6702d74 Mon Sep 17 00:00:00 2001 +Message-Id: <8c3d27d3b3cd3aecb7c92684466a2edab6702d74.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:22 +0200 -Subject: [PATCH 005/325] ARM: at91: Implement clocksource selection -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 005/327] ARM: at91: Implement clocksource selection +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Allow selecting and unselecting the PIT clocksource driver so it doesn't have to be compile when unused. @@ -51,5 +54,5 @@ index 903f23c309df..fa493a86e2bb 100644 bool -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0006-ARM-configs-at91-use-new-TCB-timer-driver.patch b/debian/patches-rt/0006-ARM-configs-at91-use-new-TCB-timer-driver.patch index 313ad6fb6..24eb6591b 100644 --- a/debian/patches-rt/0006-ARM-configs-at91-use-new-TCB-timer-driver.patch +++ b/debian/patches-rt/0006-ARM-configs-at91-use-new-TCB-timer-driver.patch @@ -1,8 +1,11 @@ -From 546eacc7d54dbf5c6b35cea154d82a1aa2611af1 Mon Sep 17 00:00:00 2001 +From b03704eee6d051563cf2a10bad6eb191d1199e7e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:23 +0200 -Subject: [PATCH 006/325] ARM: configs: at91: use new TCB timer driver -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 006/327] ARM: configs: at91: use new TCB timer driver +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Unselecting ATMEL_TCLIB switches the TCB timer driver from tcb_clksrc to timer-atmel-tcb. @@ -39,5 +42,5 @@ index 2080025556b5..f2bbc6339ca6 100644 CONFIG_EEPROM_AT24=y CONFIG_SCSI=y -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch b/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch index 92bdf8e72..3d6772ca4 100644 --- a/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch +++ b/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch @@ -1,8 +1,11 @@ -From 44a288d26c969a743059392f799ee270bd87e9bb Mon Sep 17 00:00:00 2001 +From f1aaef6e633365e7d9ab49f80ccac5bd16ae4fa1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:24 +0200 -Subject: [PATCH 007/325] ARM: configs: at91: unselect PIT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 007/327] ARM: configs: at91: unselect PIT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The PIT is not required anymore to successfully boot and may actually harm in case preempt-rt is used because the PIT interrupt is shared. @@ -40,5 +43,5 @@ index f2bbc6339ca6..be92871ab155 100644 CONFIG_UACCESS_WITH_MEMCPY=y CONFIG_ZBOOT_ROM_TEXT=0x0 -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0008-irqchip-gic-v3-its-Move-pending-table-allocation-to-.patch b/debian/patches-rt/0008-irqchip-gic-v3-its-Move-pending-table-allocation-to-.patch index ae974105b..dd04b5f69 100644 --- a/debian/patches-rt/0008-irqchip-gic-v3-its-Move-pending-table-allocation-to-.patch +++ b/debian/patches-rt/0008-irqchip-gic-v3-its-Move-pending-table-allocation-to-.patch @@ -1,9 +1,12 @@ -From d70eac98c1314f780bfe229544f829b50453ae2b Mon Sep 17 00:00:00 2001 +From 9e80d0692dd5fa2ead7ea71292c9bcc52d4f41bc Mon Sep 17 00:00:00 2001 +Message-Id: <9e80d0692dd5fa2ead7ea71292c9bcc52d4f41bc.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Marc Zyngier Date: Fri, 27 Jul 2018 13:38:54 +0100 -Subject: [PATCH 008/325] irqchip/gic-v3-its: Move pending table allocation to +Subject: [PATCH 008/327] irqchip/gic-v3-its: Move pending table allocation to init time -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Signed-off-by: Marc Zyngier Signed-off-by: Sebastian Andrzej Siewior @@ -13,7 +16,7 @@ Signed-off-by: Sebastian Andrzej Siewior 2 files changed, 53 insertions(+), 28 deletions(-) diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c -index f9b73336a39e..0387399054b7 100644 +index fe7d63cdfb1d..937c94625c36 100644 --- a/drivers/irqchip/irq-gic-v3-its.c +++ b/drivers/irqchip/irq-gic-v3-its.c @@ -179,6 +179,7 @@ static DEFINE_RAW_SPINLOCK(vmovp_lock); @@ -107,7 +110,7 @@ index f9b73336a39e..0387399054b7 100644 } static void its_cpu_init_collection(struct its_node *its) -@@ -3585,16 +3607,6 @@ static int redist_disable_lpis(void) +@@ -3591,16 +3613,6 @@ static int redist_disable_lpis(void) u64 timeout = USEC_PER_SEC; u64 val; @@ -124,7 +127,7 @@ index f9b73336a39e..0387399054b7 100644 if (!gic_rdists_supports_plpis()) { pr_info("CPU%d: LPIs not supported\n", smp_processor_id()); return -ENXIO; -@@ -3604,7 +3616,18 @@ static int redist_disable_lpis(void) +@@ -3610,7 +3622,18 @@ static int redist_disable_lpis(void) if (!(val & GICR_CTLR_ENABLE_LPIS)) return 0; @@ -144,7 +147,7 @@ index f9b73336a39e..0387399054b7 100644 smp_processor_id()); add_taint(TAINT_CRAP, LOCKDEP_STILL_OK); -@@ -3860,7 +3883,8 @@ int __init its_init(struct fwnode_handle *handle, struct rdists *rdists, +@@ -3866,7 +3889,8 @@ int __init its_init(struct fwnode_handle *handle, struct rdists *rdists, } gic_rdists = rdists; @@ -167,5 +170,5 @@ index 1d21e98d6854..fdddead7e307 100644 struct page *prop_page; u64 flags; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0009-kthread-convert-worker-lock-to-raw-spinlock.patch b/debian/patches-rt/0009-kthread-convert-worker-lock-to-raw-spinlock.patch index e1ccf0070..705f68ddb 100644 --- a/debian/patches-rt/0009-kthread-convert-worker-lock-to-raw-spinlock.patch +++ b/debian/patches-rt/0009-kthread-convert-worker-lock-to-raw-spinlock.patch @@ -1,8 +1,11 @@ -From 3cf0fcd0004434877a5db97439d4b56e78837a4f Mon Sep 17 00:00:00 2001 +From 7d31f7cf7f58f99e34da1a431615e876dbca1918 Mon Sep 17 00:00:00 2001 +Message-Id: <7d31f7cf7f58f99e34da1a431615e876dbca1918.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 -Subject: [PATCH 009/325] kthread: convert worker lock to raw spinlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 009/327] kthread: convert worker lock to raw spinlock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In order to enable the queuing of kthread work items from hardirq context even when PREEMPT_RT_FULL is enabled, convert the worker @@ -199,5 +202,5 @@ index 087d18d771b5..5641b55783a6 100644 return ret; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0010-crypto-caam-qi-simplify-CGR-allocation-freeing.patch b/debian/patches-rt/0010-crypto-caam-qi-simplify-CGR-allocation-freeing.patch index 0b1e99a3a..07a85f348 100644 --- a/debian/patches-rt/0010-crypto-caam-qi-simplify-CGR-allocation-freeing.patch +++ b/debian/patches-rt/0010-crypto-caam-qi-simplify-CGR-allocation-freeing.patch @@ -1,11 +1,14 @@ -From 222023498c02fbc8c0143bb3237a0e0a674175e5 Mon Sep 17 00:00:00 2001 +From e3dad4d17535d9521beda4efbe2fc44795f67d7a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: =?UTF-8?q?Horia=20Geant=C4=83?= Date: Mon, 8 Oct 2018 14:09:37 +0300 -Subject: [PATCH 010/325] crypto: caam/qi - simplify CGR allocation, freeing +Subject: [PATCH 010/327] crypto: caam/qi - simplify CGR allocation, freeing MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [Upstream commit 29e83c757006fd751966bdc53392bb22d74179c6] @@ -136,5 +139,5 @@ index 357b69f57072..b6c8acc30853 100644 /** * qi_cache_alloc - Allocate buffers from CAAM-QI cache -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0011-sched-fair-Robustify-CFS-bandwidth-timer-locking.patch b/debian/patches-rt/0011-sched-fair-Robustify-CFS-bandwidth-timer-locking.patch index c45ab7726..4a0c331fe 100644 --- a/debian/patches-rt/0011-sched-fair-Robustify-CFS-bandwidth-timer-locking.patch +++ b/debian/patches-rt/0011-sched-fair-Robustify-CFS-bandwidth-timer-locking.patch @@ -1,8 +1,11 @@ -From 698e9d4aa2337745a67cdb0d0130df1851dd9a25 Mon Sep 17 00:00:00 2001 +From 448b243a1fb84f0081f5652354423456e2fc0373 Mon Sep 17 00:00:00 2001 +Message-Id: <448b243a1fb84f0081f5652354423456e2fc0373.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 7 Jan 2019 13:52:31 +0100 -Subject: [PATCH 011/325] sched/fair: Robustify CFS-bandwidth timer locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 011/327] sched/fair: Robustify CFS-bandwidth timer locking +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Traditionally hrtimer callbacks were run with IRQs disabled, but with the introduction of HRTIMER_MODE_SOFT it is possible they run from @@ -144,5 +147,5 @@ index 86ccaaf0c1bf..ded41daf0d73 100644 return idle ? HRTIMER_NORESTART : HRTIMER_RESTART; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0012-arm-Convert-arm-boot_lock-to-raw.patch b/debian/patches-rt/0012-arm-Convert-arm-boot_lock-to-raw.patch index 2509caee5..869dbf530 100644 --- a/debian/patches-rt/0012-arm-Convert-arm-boot_lock-to-raw.patch +++ b/debian/patches-rt/0012-arm-Convert-arm-boot_lock-to-raw.patch @@ -1,8 +1,11 @@ -From a5adb64cd4a86c6fa8bc3b35141ade2fa82d3d27 Mon Sep 17 00:00:00 2001 +From 3564312da18561b00498caa06842ff388bbef279 Mon Sep 17 00:00:00 2001 +Message-Id: <3564312da18561b00498caa06842ff388bbef279.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Frank Rowand Date: Mon, 19 Sep 2011 14:51:14 -0700 -Subject: [PATCH 012/325] arm: Convert arm boot_lock to raw -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 012/327] arm: Convert arm boot_lock to raw +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The arm boot_lock is used by the secondary processor startup code. The locking task is the idle thread, which has idle->sched_class == &idle_sched_class. @@ -428,5 +431,5 @@ index c2366510187a..6b60f582b738 100644 return pen_release != -1 ? -ENOSYS : 0; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0013-x86-ioapic-Don-t-let-setaffinity-unmask-threaded-EOI.patch b/debian/patches-rt/0013-x86-ioapic-Don-t-let-setaffinity-unmask-threaded-EOI.patch index e170fcd98..912e0b723 100644 --- a/debian/patches-rt/0013-x86-ioapic-Don-t-let-setaffinity-unmask-threaded-EOI.patch +++ b/debian/patches-rt/0013-x86-ioapic-Don-t-let-setaffinity-unmask-threaded-EOI.patch @@ -1,9 +1,12 @@ -From 21f4cc8e461111c6918c67c907cb4a8ae8afa936 Mon Sep 17 00:00:00 2001 +From 79aa953ef9dcd175074ab38896df71155ca4fc42 Mon Sep 17 00:00:00 2001 +Message-Id: <79aa953ef9dcd175074ab38896df71155ca4fc42.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 17 Jul 2018 18:25:31 +0200 -Subject: [PATCH 013/325] x86/ioapic: Don't let setaffinity unmask threaded EOI +Subject: [PATCH 013/327] x86/ioapic: Don't let setaffinity unmask threaded EOI interrupt too early -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz There is an issue with threaded interrupts which are marked ONESHOT and using the fasteoi handler. @@ -97,5 +100,5 @@ index fa3b85b222e3..1bdad61a3ef7 100644 static void ioapic_ir_ack_level(struct irq_data *irq_data) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0014-cgroup-use-irqsave-in-cgroup_rstat_flush_locked.patch b/debian/patches-rt/0014-cgroup-use-irqsave-in-cgroup_rstat_flush_locked.patch index f6b4851b5..0e687beee 100644 --- a/debian/patches-rt/0014-cgroup-use-irqsave-in-cgroup_rstat_flush_locked.patch +++ b/debian/patches-rt/0014-cgroup-use-irqsave-in-cgroup_rstat_flush_locked.patch @@ -1,8 +1,11 @@ -From d92527bb24ae4fa57d587ae040d61e04458f59ac Mon Sep 17 00:00:00 2001 +From 7de545a7d799671cc1910dae9275ce7c21e58da7 Mon Sep 17 00:00:00 2001 +Message-Id: <7de545a7d799671cc1910dae9275ce7c21e58da7.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 18:19:48 +0200 -Subject: [PATCH 014/325] cgroup: use irqsave in cgroup_rstat_flush_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 014/327] cgroup: use irqsave in cgroup_rstat_flush_locked() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz All callers of cgroup_rstat_flush_locked() acquire cgroup_rstat_lock either with spin_lock_irq() or spin_lock_irqsave(). @@ -46,5 +49,5 @@ index bb95a35e8c2d..3266a9781b4e 100644 /* if @may_sleep, play nice and yield if necessary */ if (may_sleep && (need_resched() || -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0015-fscache-initialize-cookie-hash-table-raw-spinlocks.patch b/debian/patches-rt/0015-fscache-initialize-cookie-hash-table-raw-spinlocks.patch index e93d53577..945fad8bc 100644 --- a/debian/patches-rt/0015-fscache-initialize-cookie-hash-table-raw-spinlocks.patch +++ b/debian/patches-rt/0015-fscache-initialize-cookie-hash-table-raw-spinlocks.patch @@ -1,8 +1,11 @@ -From 79bc9b1cb45fe96b437ac97ffbbb28c1f02523a9 Mon Sep 17 00:00:00 2001 +From fff6de28ff6dd3522a77ca5c667d20bc9b2086d2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 3 Jul 2018 13:34:30 -0500 -Subject: [PATCH 015/325] fscache: initialize cookie hash table raw spinlocks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 015/327] fscache: initialize cookie hash table raw spinlocks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The fscache cookie mechanism uses a hash table of hlist_bl_head structures. The PREEMPT_RT patcheset adds a raw spinlock to this structure and so on PREEMPT_RT @@ -60,5 +63,5 @@ index 84b90a79d75a..87a9330eafa2 100644 /** * fscache_register_netfs - Register a filesystem as desiring caching services -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0016-Drivers-hv-vmbus-include-header-for-get_irq_regs.patch b/debian/patches-rt/0016-Drivers-hv-vmbus-include-header-for-get_irq_regs.patch index 84cd12be2..3a83eeea9 100644 --- a/debian/patches-rt/0016-Drivers-hv-vmbus-include-header-for-get_irq_regs.patch +++ b/debian/patches-rt/0016-Drivers-hv-vmbus-include-header-for-get_irq_regs.patch @@ -1,11 +1,14 @@ -From 19172d30b8e9f6e2c70d3170a75da4aac327cb9b Mon Sep 17 00:00:00 2001 +From 7b406e85875d67693cecc7cfe09a5e7180af01a5 Mon Sep 17 00:00:00 2001 +Message-Id: <7b406e85875d67693cecc7cfe09a5e7180af01a5.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 Aug 2018 21:59:04 +0200 -Subject: [PATCH 016/325] Drivers: hv: vmbus: include header for get_irq_regs() +Subject: [PATCH 016/327] Drivers: hv: vmbus: include header for get_irq_regs() MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On !RT the header file get_irq_regs() gets pulled in via other header files. On RT it does not and the build fails: @@ -36,5 +39,5 @@ index 87d3d7da78f8..1d2d8a4b837d 100644 #include "hv_trace.h" -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0017-percpu-include-irqflags.h-for-raw_local_irq_save.patch b/debian/patches-rt/0017-percpu-include-irqflags.h-for-raw_local_irq_save.patch index 0d6154f22..e4e59f9fd 100644 --- a/debian/patches-rt/0017-percpu-include-irqflags.h-for-raw_local_irq_save.patch +++ b/debian/patches-rt/0017-percpu-include-irqflags.h-for-raw_local_irq_save.patch @@ -1,8 +1,11 @@ -From ea486c7cc32c9056a03180db47f3710c7fc2052f Mon Sep 17 00:00:00 2001 +From 70614aac8907a90efde502dd5bf9e7916c26afb6 Mon Sep 17 00:00:00 2001 +Message-Id: <70614aac8907a90efde502dd5bf9e7916c26afb6.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 11 Oct 2018 16:39:59 +0200 -Subject: [PATCH 017/325] percpu: include irqflags.h for raw_local_irq_save() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 017/327] percpu: include irqflags.h for raw_local_irq_save() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The header percpu.h header file is using raw_local_irq_save() but does not include irqflags.h for its definition. It compiles because the @@ -29,5 +32,5 @@ index 1817a8415a5e..942d64c0476e 100644 #ifdef CONFIG_SMP -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0018-efi-Allow-efi-runtime.patch b/debian/patches-rt/0018-efi-Allow-efi-runtime.patch index 475a80925..3cb01a658 100644 --- a/debian/patches-rt/0018-efi-Allow-efi-runtime.patch +++ b/debian/patches-rt/0018-efi-Allow-efi-runtime.patch @@ -1,8 +1,11 @@ -From 2d27283a8f76ac017050287c1a62c14cddaf11d4 Mon Sep 17 00:00:00 2001 +From fbe5b00e47354c46adcab1cf9e19a9df96d60e8b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:06:10 +0200 -Subject: [PATCH 018/325] efi: Allow efi=runtime -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 018/327] efi: Allow efi=runtime +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In case the option "efi=noruntime" is default at built-time, the user could overwrite its sate by `efi=runtime' and allow it again. @@ -14,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 3 insertions(+) diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c -index d54fca902e64..5db20908aa9c 100644 +index f1e0a2715269..3d5cbd3eedb4 100644 --- a/drivers/firmware/efi/efi.c +++ b/drivers/firmware/efi/efi.c @@ -113,6 +113,9 @@ static int __init parse_efi_cmdline(char *str) @@ -28,5 +31,5 @@ index d54fca902e64..5db20908aa9c 100644 } early_param("efi", parse_efi_cmdline); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0019-x86-efi-drop-task_lock-from-efi_switch_mm.patch b/debian/patches-rt/0019-x86-efi-drop-task_lock-from-efi_switch_mm.patch index 22c190863..46e1af7ba 100644 --- a/debian/patches-rt/0019-x86-efi-drop-task_lock-from-efi_switch_mm.patch +++ b/debian/patches-rt/0019-x86-efi-drop-task_lock-from-efi_switch_mm.patch @@ -1,8 +1,11 @@ -From 91fec13b5fdf4dce19d23cd229ecfdafcc6f6d22 Mon Sep 17 00:00:00 2001 +From 065037d4d75ed96573ea0c6343fe85f0dc2f83ff Mon Sep 17 00:00:00 2001 +Message-Id: <065037d4d75ed96573ea0c6343fe85f0dc2f83ff.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 24 Jul 2018 14:48:55 +0200 -Subject: [PATCH 019/325] x86/efi: drop task_lock() from efi_switch_mm() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 019/327] x86/efi: drop task_lock() from efi_switch_mm() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz efi_switch_mm() is a wrapper around switch_mm() which saves current's ->active_mm, sets the requests mm as ->active_mm and invokes @@ -24,7 +27,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/arch/x86/platform/efi/efi_64.c b/arch/x86/platform/efi/efi_64.c -index 2a9a703ef4a0..f104c9f2998d 100644 +index 52dd59af873e..04f05173e6ff 100644 --- a/arch/x86/platform/efi/efi_64.c +++ b/arch/x86/platform/efi/efi_64.c @@ -617,18 +617,16 @@ void __init efi_dump_pagetable(void) @@ -51,5 +54,5 @@ index 2a9a703ef4a0..f104c9f2998d 100644 #ifdef CONFIG_EFI_MIXED -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0020-arm64-KVM-compute_layout-before-altenates-are-applie.patch b/debian/patches-rt/0020-arm64-KVM-compute_layout-before-altenates-are-applie.patch index 8f1d81ecc..54ed3d707 100644 --- a/debian/patches-rt/0020-arm64-KVM-compute_layout-before-altenates-are-applie.patch +++ b/debian/patches-rt/0020-arm64-KVM-compute_layout-before-altenates-are-applie.patch @@ -1,9 +1,12 @@ -From 83b8acc7de0d3e2798ec54ba770e14b691202d69 Mon Sep 17 00:00:00 2001 +From 2e4aceaf2bdbd76b1fc8ed5629d29734eb3ca502 Mon Sep 17 00:00:00 2001 +Message-Id: <2e4aceaf2bdbd76b1fc8ed5629d29734eb3ca502.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 09:13:42 +0200 -Subject: [PATCH 020/325] arm64: KVM: compute_layout before altenates are +Subject: [PATCH 020/327] arm64: KVM: compute_layout before altenates are applied -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz compute_layout() is invoked as part of an alternative fixup under stop_machine() and needs a sleeping lock as part of get_random_long(). @@ -79,5 +82,5 @@ index c712a7376bc1..792da0e125de 100644 * Compute HYP VA by using the same computation as kern_hyp_va() */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0021-of-allocate-free-phandle-cache-outside-of-the-devtre.patch b/debian/patches-rt/0021-of-allocate-free-phandle-cache-outside-of-the-devtre.patch index 5615e9004..8f4b112e8 100644 --- a/debian/patches-rt/0021-of-allocate-free-phandle-cache-outside-of-the-devtre.patch +++ b/debian/patches-rt/0021-of-allocate-free-phandle-cache-outside-of-the-devtre.patch @@ -1,9 +1,12 @@ -From 63891871ac6a67c1bae2aa15b3a3aef0f4060b58 Mon Sep 17 00:00:00 2001 +From 09e6d3bbfa22914d304001c21b15f919b330c8d7 Mon Sep 17 00:00:00 2001 +Message-Id: <09e6d3bbfa22914d304001c21b15f919b330c8d7.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 31 Aug 2018 14:16:30 +0200 -Subject: [PATCH 021/325] of: allocate / free phandle cache outside of the +Subject: [PATCH 021/327] of: allocate / free phandle cache outside of the devtree_lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The phandle cache code allocates memory while holding devtree_lock which is a raw_spinlock_t. Memory allocation (and free()) is not possible on @@ -99,5 +102,5 @@ index f0dbb7ad88cf..c59b30bab0e0 100644 void __init of_core_init(void) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0022-mm-kasan-make-quarantine_lock-a-raw_spinlock_t.patch b/debian/patches-rt/0022-mm-kasan-make-quarantine_lock-a-raw_spinlock_t.patch index b5931e50f..1f6c08ee4 100644 --- a/debian/patches-rt/0022-mm-kasan-make-quarantine_lock-a-raw_spinlock_t.patch +++ b/debian/patches-rt/0022-mm-kasan-make-quarantine_lock-a-raw_spinlock_t.patch @@ -1,8 +1,11 @@ -From 2cc8c4e626119389ae39665998b3dede468665e6 Mon Sep 17 00:00:00 2001 +From fbfa89ba167f66519adf09c37d8ba7972cd38e8b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 18 Sep 2018 10:29:31 -0500 -Subject: [PATCH 022/325] mm/kasan: make quarantine_lock a raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 022/327] mm/kasan: make quarantine_lock a raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The static lock quarantine_lock is used in quarantine.c to protect the quarantine queue datastructures. It is taken inside quarantine queue @@ -94,5 +97,5 @@ index 3a8ddf8baf7d..b209dbaefde8 100644 qlist_free_all(&to_free, cache); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0023-EXP-rcu-Revert-expedited-GP-parallelization-cleverne.patch b/debian/patches-rt/0023-EXP-rcu-Revert-expedited-GP-parallelization-cleverne.patch index 8293140ef..306faf3d7 100644 --- a/debian/patches-rt/0023-EXP-rcu-Revert-expedited-GP-parallelization-cleverne.patch +++ b/debian/patches-rt/0023-EXP-rcu-Revert-expedited-GP-parallelization-cleverne.patch @@ -1,9 +1,12 @@ -From ef814d6ef67f5228fd470d84ad33515c6a1efa57 Mon Sep 17 00:00:00 2001 +From f923443ca5a98d8b3208d3f04dca281fea90524d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 29 Oct 2018 11:53:01 +0100 -Subject: [PATCH 023/325] EXP rcu: Revert expedited GP parallelization +Subject: [PATCH 023/327] EXP rcu: Revert expedited GP parallelization cleverness -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz (Commit 258ba8e089db23f760139266c232f01bad73f85c from linux-rcu) @@ -47,5 +50,5 @@ index 0b2c2ad69629..a0486414edb4 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0024-kmemleak-Turn-kmemleak_lock-to-raw-spinlock-on-RT.patch b/debian/patches-rt/0024-kmemleak-Turn-kmemleak_lock-to-raw-spinlock-on-RT.patch index 37b8c30c8..935c9c511 100644 --- a/debian/patches-rt/0024-kmemleak-Turn-kmemleak_lock-to-raw-spinlock-on-RT.patch +++ b/debian/patches-rt/0024-kmemleak-Turn-kmemleak_lock-to-raw-spinlock-on-RT.patch @@ -1,11 +1,14 @@ -From 28341f3661c5c3dac734d973251ad13a637fb0bd Mon Sep 17 00:00:00 2001 +From 5ffb480060a6dfc773ccd3696324297c8754242d Mon Sep 17 00:00:00 2001 +Message-Id: <5ffb480060a6dfc773ccd3696324297c8754242d.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: He Zhe Date: Wed, 19 Dec 2018 16:30:57 +0100 -Subject: [PATCH 024/325] kmemleak: Turn kmemleak_lock to raw spinlock on RT +Subject: [PATCH 024/327] kmemleak: Turn kmemleak_lock to raw spinlock on RT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz kmemleak_lock, as a rwlock on RT, can possibly be held in atomic context and causes the follow BUG. @@ -165,5 +168,5 @@ index 5eeabece0c17..92ce99b15f2b 100644 /* -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0025-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch b/debian/patches-rt/0025-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch index 2c8a72630..1145539da 100644 --- a/debian/patches-rt/0025-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch +++ b/debian/patches-rt/0025-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch @@ -1,8 +1,11 @@ -From 89760c7945fc386046ef15f564d7e91990f88ed8 Mon Sep 17 00:00:00 2001 +From e8b73ba5194e2f3d7d57b665986c8a09406d4483 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 28 Oct 2016 23:05:11 +0200 -Subject: [PATCH 025/325] NFSv4: replace seqcount_t with a seqlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 025/327] NFSv4: replace seqcount_t with a seqlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The raw_write_seqcount_begin() in nfs4_reclaim_open_state() bugs me because it maps to preempt_disable() in -RT which I can't have at this @@ -132,5 +135,5 @@ index b3086e99420c..c9bf1eb7e1b2 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0026-kernel-sched-Provide-a-pointer-to-the-valid-CPU-mask.patch b/debian/patches-rt/0026-kernel-sched-Provide-a-pointer-to-the-valid-CPU-mask.patch index 1c51a8080..0c0b0fb28 100644 --- a/debian/patches-rt/0026-kernel-sched-Provide-a-pointer-to-the-valid-CPU-mask.patch +++ b/debian/patches-rt/0026-kernel-sched-Provide-a-pointer-to-the-valid-CPU-mask.patch @@ -1,12 +1,15 @@ -From afc9cd313faee6faecfc1ab87693f143c9206536 Mon Sep 17 00:00:00 2001 +From c09d1e32b858b93d1a3412ca593e4b2f59218148 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Apr 2017 12:50:16 +0200 -Subject: [PATCH 026/325] kernel: sched: Provide a pointer to the valid CPU +Subject: [PATCH 026/327] kernel: sched: Provide a pointer to the valid CPU mask MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In commit 4b53a3412d66 ("sched/core: Remove the tsk_nr_cpus_allowed() wrapper") the tsk_nr_cpus_allowed() wrapper was removed. There was not @@ -271,7 +274,7 @@ index 9eb99a43f849..e4d0cfebaac5 100644 static inline void task_core_dumping(struct seq_file *m, struct mm_struct *mm) diff --git a/include/linux/sched.h b/include/linux/sched.h -index 0530de9a4efc..4298a87b9de6 100644 +index c69f308f3a53..463c20160105 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -660,7 +660,8 @@ struct task_struct { @@ -781,5 +784,5 @@ index 5522692100ba..8b4be8e1802a 100644 trace_foo_with_template_simple("HELLO", cnt); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0027-kernel-sched-core-add-migrate_disable.patch b/debian/patches-rt/0027-kernel-sched-core-add-migrate_disable.patch index 8e54ba023..f29a4ff3f 100644 --- a/debian/patches-rt/0027-kernel-sched-core-add-migrate_disable.patch +++ b/debian/patches-rt/0027-kernel-sched-core-add-migrate_disable.patch @@ -1,8 +1,11 @@ -From 8ad94df28becac218184cd246b017a0141a46247 Mon Sep 17 00:00:00 2001 +From 139cf7b485c546a3ebe3564e6c1cc1836a992210 Mon Sep 17 00:00:00 2001 +Message-Id: <139cf7b485c546a3ebe3564e6c1cc1836a992210.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 -Subject: [PATCH 027/325] kernel/sched/core: add migrate_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 027/327] kernel/sched/core: add migrate_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz --- include/linux/preempt.h | 23 +++++++ @@ -54,7 +57,7 @@ index c01813c3fbe9..3196d0e76719 100644 #ifdef MODULE diff --git a/include/linux/sched.h b/include/linux/sched.h -index 4298a87b9de6..0489d3e0e78c 100644 +index 463c20160105..3277801f519d 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -662,6 +662,13 @@ struct task_struct { @@ -262,5 +265,5 @@ index 78fadf0438ea..5027158d3908 100644 #undef PN #undef __PN -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0028-sched-migrate_disable-Add-export_symbol_gpl-for-__mi.patch b/debian/patches-rt/0028-sched-migrate_disable-Add-export_symbol_gpl-for-__mi.patch index 838de0605..2866d96dc 100644 --- a/debian/patches-rt/0028-sched-migrate_disable-Add-export_symbol_gpl-for-__mi.patch +++ b/debian/patches-rt/0028-sched-migrate_disable-Add-export_symbol_gpl-for-__mi.patch @@ -1,9 +1,12 @@ -From 8a5a5668c864f35ac4028c8c775918b8bd4fca1c Mon Sep 17 00:00:00 2001 +From 925eb3a76af6bf2409e1a698a16fd635649510fb Mon Sep 17 00:00:00 2001 +Message-Id: <925eb3a76af6bf2409e1a698a16fd635649510fb.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 9 Oct 2018 17:34:50 +0200 -Subject: [PATCH 028/325] sched/migrate_disable: Add export_symbol_gpl for +Subject: [PATCH 028/327] sched/migrate_disable: Add export_symbol_gpl for __migrate_disabled -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Jonathan reported that lttng/modules can't use __migrate_disabled(). This function is only used by sched/core itself and the tracing @@ -34,5 +37,5 @@ index d0450f06612c..e6022cc2605b 100644 static void __do_set_cpus_allowed_tail(struct task_struct *p, -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0029-arm-at91-do-not-disable-enable-clocks-in-a-row.patch b/debian/patches-rt/0029-arm-at91-do-not-disable-enable-clocks-in-a-row.patch index f501c9cbb..bfbfcfc07 100644 --- a/debian/patches-rt/0029-arm-at91-do-not-disable-enable-clocks-in-a-row.patch +++ b/debian/patches-rt/0029-arm-at91-do-not-disable-enable-clocks-in-a-row.patch @@ -1,8 +1,11 @@ -From 097c224348ebf8f796c6f6cd0c2eacf0b63a347b Mon Sep 17 00:00:00 2001 +From a9060ecc13b1730d842179e1e994baef67a67ad9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Mar 2016 10:51:06 +0100 -Subject: [PATCH 029/325] arm: at91: do not disable/enable clocks in a row -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 029/327] arm: at91: do not disable/enable clocks in a row +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Currently the driver will disable the clock and enable it one line later if it is switching from periodic mode into one shot. @@ -94,5 +97,5 @@ index 43f4d5c4d6fa..de6baf564dfe 100644 .set_state_oneshot = tc_set_oneshot, }, -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0030-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch b/debian/patches-rt/0030-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch index 66de0bc54..45536e46d 100644 --- a/debian/patches-rt/0030-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch +++ b/debian/patches-rt/0030-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch @@ -1,12 +1,15 @@ -From b5661f6c782e92843b5e1d081ab704dd3fb79a61 Mon Sep 17 00:00:00 2001 +From 157c4da19a2359aa5f6ad7be90cf289ec0b0563d Mon Sep 17 00:00:00 2001 +Message-Id: <157c4da19a2359aa5f6ad7be90cf289ec0b0563d.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Benedikt Spranger Date: Mon, 8 Mar 2010 18:57:04 +0100 -Subject: [PATCH 030/325] clocksource: TCLIB: Allow higher clock rates for +Subject: [PATCH 030/327] clocksource: TCLIB: Allow higher clock rates for clock events MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz As default the TCLIB uses the 32KiHz base clock rate for clock events. Add a compile time selection to allow higher clock resulution. @@ -166,5 +169,5 @@ index 3726eacdf65d..0900dec7ec04 100644 tristate "Dummy IRQ handler" default n -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch b/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch index e76b7d338..a2f65e162 100644 --- a/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch +++ b/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch @@ -1,8 +1,11 @@ -From 22522352d905d453f9bdc5271ca567d5fafdad16 Mon Sep 17 00:00:00 2001 +From 30643112afa23900442cbdd3189874c02bc5a091 Mon Sep 17 00:00:00 2001 +Message-Id: <30643112afa23900442cbdd3189874c02bc5a091.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 14 Feb 2013 22:36:59 +0100 -Subject: [PATCH 031/325] timekeeping: Split jiffies seqlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 031/327] timekeeping: Split jiffies seqlock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Replace jiffies_lock seqlock with a simple seqcounter and a rawlock so it can be taken in atomic context on RT. @@ -167,5 +170,5 @@ index 141ab3ab0354..099737f6f10c 100644 #define CS_NAME_LEN 32 -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch b/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch index 326f54fea..f3c573d1d 100644 --- a/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch +++ b/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch @@ -1,8 +1,11 @@ -From 4e6ea3956be0848c8a5771c159c7fe513e2dd745 Mon Sep 17 00:00:00 2001 +From cbd9fb5407709f0ec74da747ae0c536695fd99d2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 21 Sep 2011 19:57:12 +0200 -Subject: [PATCH 032/325] signal: Revert ptrace preempt magic -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 032/327] signal: Revert ptrace preempt magic +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Upstream commit '53da1d9456fe7f8 fix ptrace slowness' is nothing more than a bandaid around the ptrace design trainwreck. It's not a @@ -14,7 +17,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 8 deletions(-) diff --git a/kernel/signal.c b/kernel/signal.c -index c42eaf39b572..feeae7177ee1 100644 +index 6a5692118139..f810797e48cb 100644 --- a/kernel/signal.c +++ b/kernel/signal.c @@ -2108,15 +2108,7 @@ static void ptrace_stop(int exit_code, int why, int clear_code, siginfo_t *info) @@ -34,5 +37,5 @@ index c42eaf39b572..feeae7177ee1 100644 } else { /* -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0033-net-sched-Use-msleep-instead-of-yield.patch b/debian/patches-rt/0033-net-sched-Use-msleep-instead-of-yield.patch index 4adedb27a..63d87b2c8 100644 --- a/debian/patches-rt/0033-net-sched-Use-msleep-instead-of-yield.patch +++ b/debian/patches-rt/0033-net-sched-Use-msleep-instead-of-yield.patch @@ -1,8 +1,11 @@ -From 8eed50e0a7fd1ea99c11d47421ca4ea0266c829f Mon Sep 17 00:00:00 2001 +From 5f7256f96320961ff13d7850dced5905b034b306 Mon Sep 17 00:00:00 2001 +Message-Id: <5f7256f96320961ff13d7850dced5905b034b306.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Marc Kleine-Budde Date: Wed, 5 Mar 2014 00:49:47 +0100 -Subject: [PATCH 033/325] net: sched: Use msleep() instead of yield() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 033/327] net: sched: Use msleep() instead of yield() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On PREEMPT_RT enabled systems the interrupt handler run as threads at prio 50 (by default). If a high priority userspace process tries to shut down a busy @@ -60,5 +63,5 @@ index 8a4d01e427a2..4ab20f1138fd 100644 * unwind stale skb lists and qdisc statistics */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0034-dm-rq-remove-BUG_ON-irqs_disabled-check.patch b/debian/patches-rt/0034-dm-rq-remove-BUG_ON-irqs_disabled-check.patch index aea5c1a09..207be2611 100644 --- a/debian/patches-rt/0034-dm-rq-remove-BUG_ON-irqs_disabled-check.patch +++ b/debian/patches-rt/0034-dm-rq-remove-BUG_ON-irqs_disabled-check.patch @@ -1,8 +1,11 @@ -From fada05aa298813af2111a2118e1c1af72332e628 Mon Sep 17 00:00:00 2001 +From 68e48cddc25a2a910412069ffba3ad451852aff9 Mon Sep 17 00:00:00 2001 +Message-Id: <68e48cddc25a2a910412069ffba3ad451852aff9.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 27 Mar 2018 16:24:15 +0200 -Subject: [PATCH 034/325] dm rq: remove BUG_ON(!irqs_disabled) check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 034/327] dm rq: remove BUG_ON(!irqs_disabled) check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In commit 052189a2ec95 ("dm: remove superfluous irq disablement in dm_request_fn") the spin_lock_irq() was replaced with spin_lock() + a @@ -33,5 +36,5 @@ index 4d36373e1c0f..12ed08245130 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0035-usb-do-no-disable-interrupts-in-giveback.patch b/debian/patches-rt/0035-usb-do-no-disable-interrupts-in-giveback.patch index e30f099ac..0e172da77 100644 --- a/debian/patches-rt/0035-usb-do-no-disable-interrupts-in-giveback.patch +++ b/debian/patches-rt/0035-usb-do-no-disable-interrupts-in-giveback.patch @@ -1,8 +1,11 @@ -From 1e7b0ed8d23d5a93afc426a2701805787cb7459a Mon Sep 17 00:00:00 2001 +From 05fc669340e52618fc81f50128bff56b69e76cee Mon Sep 17 00:00:00 2001 +Message-Id: <05fc669340e52618fc81f50128bff56b69e76cee.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 8 Nov 2013 17:34:54 +0100 -Subject: [PATCH 035/325] usb: do no disable interrupts in giveback -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 035/327] usb: do no disable interrupts in giveback +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Since commit 94dfd7ed ("USB: HCD: support giveback of URB in tasklet context") the USB code disables interrupts before invoking the complete @@ -42,5 +45,5 @@ index b82a7d787add..2f3015356124 100644 usb_anchor_resume_wakeups(anchor); atomic_dec(&urb->use_count); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0036-rt-Provide-PREEMPT_RT_BASE-config-switch.patch b/debian/patches-rt/0036-rt-Provide-PREEMPT_RT_BASE-config-switch.patch index f51d28bdc..6ac1da5f7 100644 --- a/debian/patches-rt/0036-rt-Provide-PREEMPT_RT_BASE-config-switch.patch +++ b/debian/patches-rt/0036-rt-Provide-PREEMPT_RT_BASE-config-switch.patch @@ -1,8 +1,11 @@ -From ac2295358559dac261e20522d82cc3896bd63e97 Mon Sep 17 00:00:00 2001 +From 6871a9d9f0f9fb7c1d05fb7a784fa22ea1d4ad79 Mon Sep 17 00:00:00 2001 +Message-Id: <6871a9d9f0f9fb7c1d05fb7a784fa22ea1d4ad79.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 17 Jun 2011 12:39:57 +0200 -Subject: [PATCH 036/325] rt: Provide PREEMPT_RT_BASE config switch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 036/327] rt: Provide PREEMPT_RT_BASE config switch +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Introduce PREEMPT_RT_BASE which enables parts of PREEMPT_RT_FULL. Forces interrupt threading and enables some of the RT @@ -60,5 +63,5 @@ index cd1655122ec0..027db5976c2f 100644 \ No newline at end of file + bool -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0037-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch b/debian/patches-rt/0037-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch index 80c778da4..7bd7102a0 100644 --- a/debian/patches-rt/0037-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch +++ b/debian/patches-rt/0037-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch @@ -1,8 +1,11 @@ -From 267b99f0dfc2274075fc4d4652995fe24311f05b Mon Sep 17 00:00:00 2001 +From 5c4696b4c4304ab06f88521a00124ea89c54c232 Mon Sep 17 00:00:00 2001 +Message-Id: <5c4696b4c4304ab06f88521a00124ea89c54c232.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 14 Dec 2011 01:03:49 +0100 -Subject: [PATCH 037/325] cpumask: Disable CONFIG_CPUMASK_OFFSTACK for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 037/327] cpumask: Disable CONFIG_CPUMASK_OFFSTACK for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz There are "valid" GFP_ATOMIC allocations such as @@ -72,5 +75,5 @@ index a3928d4438b5..a50b2158f7cd 100644 Use dynamic allocation for cpumask_var_t, instead of putting them on the stack. This is a bit more expensive, but avoids -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0038-jump-label-disable-if-stop_machine-is-used.patch b/debian/patches-rt/0038-jump-label-disable-if-stop_machine-is-used.patch index 57e0119e1..c91461279 100644 --- a/debian/patches-rt/0038-jump-label-disable-if-stop_machine-is-used.patch +++ b/debian/patches-rt/0038-jump-label-disable-if-stop_machine-is-used.patch @@ -1,8 +1,11 @@ -From d6d2f824df497fe197e5d2bc268eb4e086935778 Mon Sep 17 00:00:00 2001 +From 4f16dc1b3805c09027ea0a66cb4ce5b1c8728857 Mon Sep 17 00:00:00 2001 +Message-Id: <4f16dc1b3805c09027ea0a66cb4ce5b1c8728857.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Jul 2015 17:14:48 +0200 -Subject: [PATCH 038/325] jump-label: disable if stop_machine() is used -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 038/327] jump-label: disable if stop_machine() is used +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Some architectures are using stop_machine() while switching the opcode which leads to latency spikes. @@ -38,5 +41,5 @@ index e2f7c50dbace..91ba9fe945ff 100644 select HAVE_ARCH_MMAP_RND_BITS if MMU select HAVE_ARCH_SECCOMP_FILTER if (AEABI && !OABI_COMPAT) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0039-kconfig-Disable-config-options-which-are-not-RT-comp.patch b/debian/patches-rt/0039-kconfig-Disable-config-options-which-are-not-RT-comp.patch index ef4a8ec8c..11996526c 100644 --- a/debian/patches-rt/0039-kconfig-Disable-config-options-which-are-not-RT-comp.patch +++ b/debian/patches-rt/0039-kconfig-Disable-config-options-which-are-not-RT-comp.patch @@ -1,9 +1,12 @@ -From b922a824955d554c93823ba2547095def5b87842 Mon Sep 17 00:00:00 2001 +From ebaffcc127b4f2a3a4e8292068d75a6d4d86a4be Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 24 Jul 2011 12:11:43 +0200 -Subject: [PATCH 039/325] kconfig: Disable config options which are not RT +Subject: [PATCH 039/327] kconfig: Disable config options which are not RT compatible -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Disable stuff which is known to have issues on RT @@ -39,5 +42,5 @@ index b457e94ae618..0dddbb2a3282 100644 select RADIX_TREE_MULTIORDER help -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0040-lockdep-disable-self-test.patch b/debian/patches-rt/0040-lockdep-disable-self-test.patch index f3273d6e1..7dbfd4e92 100644 --- a/debian/patches-rt/0040-lockdep-disable-self-test.patch +++ b/debian/patches-rt/0040-lockdep-disable-self-test.patch @@ -1,11 +1,14 @@ -From d503eb089b47efb99b62cfd52744ae0e8522ba67 Mon Sep 17 00:00:00 2001 +From c259ffabcd899b0caa72863f57ac9b48523af9e7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 17 Oct 2017 16:36:18 +0200 -Subject: [PATCH 040/325] lockdep: disable self-test +Subject: [PATCH 040/327] lockdep: disable self-test MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The self-test wasn't always 100% accurate for RT. We disabled a few tests which failed because they had a different semantic for RT. Some @@ -31,5 +34,5 @@ index 46a910acce3f..38cf7f81daa7 100644 Say Y here if you want the kernel to run a short self-test during bootup. The self-test checks whether common types of locking bugs -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0041-mm-Allow-only-slub-on-RT.patch b/debian/patches-rt/0041-mm-Allow-only-slub-on-RT.patch index ca6787cd1..e3fbef51d 100644 --- a/debian/patches-rt/0041-mm-Allow-only-slub-on-RT.patch +++ b/debian/patches-rt/0041-mm-Allow-only-slub-on-RT.patch @@ -1,8 +1,11 @@ -From bf1579f9280b4c92ce6b02c3f014d40eff596b86 Mon Sep 17 00:00:00 2001 +From a344e0d75f6f733c2febd47922a980dd114b6e8c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:44:03 -0500 -Subject: [PATCH 041/325] mm: Allow only slub on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 041/327] mm: Allow only slub on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Disable SLAB and SLOB on -RT. Only SLUB is adopted to -RT needs. @@ -33,5 +36,5 @@ index 47035b5a46f6..ae9a0113a699 100644 SLOB replaces the stock allocator with a drastically simpler allocator. SLOB is generally more space efficient but -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0042-locking-Disable-spin-on-owner-for-RT.patch b/debian/patches-rt/0042-locking-Disable-spin-on-owner-for-RT.patch index 77b412d43..100b47afd 100644 --- a/debian/patches-rt/0042-locking-Disable-spin-on-owner-for-RT.patch +++ b/debian/patches-rt/0042-locking-Disable-spin-on-owner-for-RT.patch @@ -1,11 +1,14 @@ -From f90c261f0738ea136c59392132ba130bad2c03b4 Mon Sep 17 00:00:00 2001 +From 73b8f03591c067230e953f05175d3218bf8286d4 Mon Sep 17 00:00:00 2001 +Message-Id: <73b8f03591c067230e953f05175d3218bf8286d4.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:51:45 +0200 -Subject: [PATCH 042/325] locking: Disable spin on owner for RT +Subject: [PATCH 042/327] locking: Disable spin on owner for RT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Drop spin on owner for mutex / rwsem. We are most likely not using it but… @@ -34,5 +37,5 @@ index 84d882f3e299..af27c4000812 100644 config LOCK_SPIN_ON_OWNER def_bool y -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch b/debian/patches-rt/0043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch index 26ff91080..c4a12b8cd 100644 --- a/debian/patches-rt/0043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch +++ b/debian/patches-rt/0043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch @@ -1,8 +1,11 @@ -From df00a54df3c3cf8857d0f2836e313a11d3c38180 Mon Sep 17 00:00:00 2001 +From 80720135f27a7e65bcdf6e6d8ba6b7aaf92d6f79 Mon Sep 17 00:00:00 2001 +Message-Id: <80720135f27a7e65bcdf6e6d8ba6b7aaf92d6f79.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 13:26:09 +0000 -Subject: [PATCH 043/325] rcu: Disable RCU_FAST_NO_HZ on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 043/327] rcu: Disable RCU_FAST_NO_HZ on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz This uses a timer_list timer from the irq disabled guts of the idle code. Disable it for now to prevent wreckage. @@ -26,5 +29,5 @@ index 9210379c0353..644264be90f0 100644 help This option permits CPUs to enter dynticks-idle state even if -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0044-rcu-make-RCU_BOOST-default-on-RT.patch b/debian/patches-rt/0044-rcu-make-RCU_BOOST-default-on-RT.patch index 84405b468..1bf5945c6 100644 --- a/debian/patches-rt/0044-rcu-make-RCU_BOOST-default-on-RT.patch +++ b/debian/patches-rt/0044-rcu-make-RCU_BOOST-default-on-RT.patch @@ -1,8 +1,11 @@ -From 1b6c39d11d3f8f75251ccbaa4dbbf2db13892023 Mon Sep 17 00:00:00 2001 +From fda6ef2c4bdaedc6cbe018bcfc61ad84d7e94e1e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Mar 2014 20:19:05 +0100 -Subject: [PATCH 044/325] rcu: make RCU_BOOST default on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 044/327] rcu: make RCU_BOOST default on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Since it is no longer invoked from the softirq people run into OOM more often if the priority of the RCU thread is too low. Making boosting @@ -30,5 +33,5 @@ index 644264be90f0..a243a78ff38c 100644 This option boosts the priority of preempted RCU readers that block the current preemptible RCU grace period for too long. -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0045-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch b/debian/patches-rt/0045-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch index 87baac3a1..d464b64f6 100644 --- a/debian/patches-rt/0045-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch +++ b/debian/patches-rt/0045-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch @@ -1,8 +1,11 @@ -From f9726e45c479872aa7380cd7f5190cebcac02c70 Mon Sep 17 00:00:00 2001 +From c628b5bf1ee888f471438a80954d50813a981cb1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:03:52 +0200 -Subject: [PATCH 045/325] sched: Disable CONFIG_RT_GROUP_SCHED on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 045/327] sched: Disable CONFIG_RT_GROUP_SCHED on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Carsten reported problems when running: @@ -31,5 +34,5 @@ index ae9a0113a699..61e8b531649b 100644 help This feature lets you explicitly allocate real CPU bandwidth -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0046-net-core-disable-NET_RX_BUSY_POLL.patch b/debian/patches-rt/0046-net-core-disable-NET_RX_BUSY_POLL.patch index bacd8e8fc..aee720dd2 100644 --- a/debian/patches-rt/0046-net-core-disable-NET_RX_BUSY_POLL.patch +++ b/debian/patches-rt/0046-net-core-disable-NET_RX_BUSY_POLL.patch @@ -1,11 +1,14 @@ -From 996a1b580a6cc76c1463f9f69662448d34ebb398 Mon Sep 17 00:00:00 2001 +From c01244956b4f87fb0eb7384e9f803b2792f456fe Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 -Subject: [PATCH 046/325] net/core: disable NET_RX_BUSY_POLL +Subject: [PATCH 046/327] net/core: disable NET_RX_BUSY_POLL MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz sk_busy_loop() does preempt_disable() followed by a few operations which can take sleeping locks and may get long. @@ -34,5 +37,5 @@ index 228dfa382eec..bc8d01996f22 100644 config BQL bool -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0047-arm-disable-NEON-in-kernel-mode.patch b/debian/patches-rt/0047-arm-disable-NEON-in-kernel-mode.patch index 48e5f504c..0e232a4fd 100644 --- a/debian/patches-rt/0047-arm-disable-NEON-in-kernel-mode.patch +++ b/debian/patches-rt/0047-arm-disable-NEON-in-kernel-mode.patch @@ -1,8 +1,11 @@ -From fe0a55f724947832043b3e9dce548b136de75da7 Mon Sep 17 00:00:00 2001 +From 2380b2865c54f45e1a90d477ca35585171673264 Mon Sep 17 00:00:00 2001 +Message-Id: <2380b2865c54f45e1a90d477ca35585171673264.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 1 Dec 2017 10:42:03 +0100 -Subject: [PATCH 047/325] arm*: disable NEON in kernel mode -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 047/327] arm*: disable NEON in kernel mode +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz NEON in kernel mode is used by the crypto algorithms and raid6 code. While the raid6 code looks okay, the crypto algorithms do not: NEON @@ -162,5 +165,5 @@ index 34b4e3d46aab..ae055cdad8cf 100644 crc32_pmull_algs[1].update = crc32c_pmull_update; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0048-powerpc-Use-generic-rwsem-on-RT.patch b/debian/patches-rt/0048-powerpc-Use-generic-rwsem-on-RT.patch index 2e098832f..ec7abfc96 100644 --- a/debian/patches-rt/0048-powerpc-Use-generic-rwsem-on-RT.patch +++ b/debian/patches-rt/0048-powerpc-Use-generic-rwsem-on-RT.patch @@ -1,8 +1,11 @@ -From f66e42e47b6d784455711d775e0e896078112788 Mon Sep 17 00:00:00 2001 +From 54d3f6184f43d8339af4d52ce2945810f8378a00 Mon Sep 17 00:00:00 2001 +Message-Id: <54d3f6184f43d8339af4d52ce2945810f8378a00.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 048/325] powerpc: Use generic rwsem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 048/327] powerpc: Use generic rwsem on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Use generic code which uses rtmutex @@ -29,5 +32,5 @@ index 6f475dc5829b..3d5c86336072 100644 config GENERIC_LOCKBREAK bool -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0049-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch b/debian/patches-rt/0049-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch index 5d5a1578d..da7be1551 100644 --- a/debian/patches-rt/0049-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch +++ b/debian/patches-rt/0049-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch @@ -1,9 +1,12 @@ -From a0922c5ef203ce1bf241a3189fd9bf2475f7871e Mon Sep 17 00:00:00 2001 +From 380f81e47f4aa5c13aba9365a4653ada7a863f93 Mon Sep 17 00:00:00 2001 +Message-Id: <380f81e47f4aa5c13aba9365a4653ada7a863f93.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Bogdan Purcareata Date: Fri, 24 Apr 2015 15:53:13 +0000 -Subject: [PATCH 049/325] powerpc/kvm: Disable in-kernel MPIC emulation for +Subject: [PATCH 049/327] powerpc/kvm: Disable in-kernel MPIC emulation for PREEMPT_RT_FULL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz While converting the openpic emulation code to use a raw_spinlock_t enables guests to run on RT, there's still a performance issue. For interrupts sent in @@ -41,5 +44,5 @@ index 68a0e9d5b440..6f4d5d7615af 100644 select HAVE_KVM_IRQFD select HAVE_KVM_IRQ_ROUTING -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch b/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch index 8bea76b81..4ef2963c6 100644 --- a/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch +++ b/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch @@ -1,8 +1,11 @@ -From 05259869f3f330c74c6647e1bcceda4f6a17996d Mon Sep 17 00:00:00 2001 +From a87a0a78e22ce91976f859d6674bb3e78e304c92 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:08:34 +0200 -Subject: [PATCH 050/325] powerpc: Disable highmem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 050/327] powerpc: Disable highmem on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The current highmem handling on -RT is not compatible and needs fixups. @@ -25,5 +28,5 @@ index 3d5c86336072..1b332f69dd36 100644 source kernel/Kconfig.hz -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch b/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch index 9455f84b7..f6853f7bd 100644 --- a/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch +++ b/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch @@ -1,8 +1,11 @@ -From 2724f222d99a9ed81df4fa565d6cf82d34259d69 Mon Sep 17 00:00:00 2001 +From 8bb6a4ae52df124954ab3ae4a3f48237a5bc1d69 Mon Sep 17 00:00:00 2001 +Message-Id: <8bb6a4ae52df124954ab3ae4a3f48237a5bc1d69.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:10:12 +0200 -Subject: [PATCH 051/325] mips: Disable highmem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 051/327] mips: Disable highmem on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The current highmem handling on -RT is not compatible and needs fixups. @@ -25,5 +28,5 @@ index a830a9701e50..3d5fae3891be 100644 config CPU_SUPPORTS_HIGHMEM bool -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0052-x86-Use-generic-rwsem_spinlocks-on-rt.patch b/debian/patches-rt/0052-x86-Use-generic-rwsem_spinlocks-on-rt.patch index cbbfeb906..68f421819 100644 --- a/debian/patches-rt/0052-x86-Use-generic-rwsem_spinlocks-on-rt.patch +++ b/debian/patches-rt/0052-x86-Use-generic-rwsem_spinlocks-on-rt.patch @@ -1,8 +1,11 @@ -From 78bb51d4c679626974498c8ae3af2866d451c48b Mon Sep 17 00:00:00 2001 +From 5911e094e0d179e9838030f203dafcb32426c5e9 Mon Sep 17 00:00:00 2001 +Message-Id: <5911e094e0d179e9838030f203dafcb32426c5e9.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 26 Jul 2009 02:21:32 +0200 -Subject: [PATCH 052/325] x86: Use generic rwsem_spinlocks on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 052/327] x86: Use generic rwsem_spinlocks on -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Simplifies the separation of anon_rw_semaphores and rw_semaphores for -rt. @@ -30,5 +33,5 @@ index e40ba59efe7f..f22e787329cf 100644 config GENERIC_CALIBRATE_DELAY def_bool y -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0053-leds-trigger-disable-CPU-trigger-on-RT.patch b/debian/patches-rt/0053-leds-trigger-disable-CPU-trigger-on-RT.patch index a1df87c3c..3a6a614ad 100644 --- a/debian/patches-rt/0053-leds-trigger-disable-CPU-trigger-on-RT.patch +++ b/debian/patches-rt/0053-leds-trigger-disable-CPU-trigger-on-RT.patch @@ -1,8 +1,11 @@ -From 88db50cf7dd13e56c63f264a6bb3763f59ed0795 Mon Sep 17 00:00:00 2001 +From 460db135f97d9a70b2816dd9f144f3f2c35ff377 Mon Sep 17 00:00:00 2001 +Message-Id: <460db135f97d9a70b2816dd9f144f3f2c35ff377.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 23 Jan 2014 14:45:59 +0100 -Subject: [PATCH 053/325] leds: trigger: disable CPU trigger on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 053/327] leds: trigger: disable CPU trigger on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz as it triggers: |CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.8-rt10 #141 @@ -37,5 +40,5 @@ index 4018af769969..b4ce8c115949 100644 This allows LEDs to be controlled by active CPUs. This shows the active CPUs across an array of LEDs so you can see which -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0054-cpufreq-drop-K8-s-driver-from-beeing-selected.patch b/debian/patches-rt/0054-cpufreq-drop-K8-s-driver-from-beeing-selected.patch index ab3fe9d15..aad920201 100644 --- a/debian/patches-rt/0054-cpufreq-drop-K8-s-driver-from-beeing-selected.patch +++ b/debian/patches-rt/0054-cpufreq-drop-K8-s-driver-from-beeing-selected.patch @@ -1,8 +1,11 @@ -From d8c10b642fecafbf8fdcc70eb887ac2b1b2010de Mon Sep 17 00:00:00 2001 +From a93d761262d0879d910b5f5ce26647629208377c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 9 Apr 2015 15:23:01 +0200 -Subject: [PATCH 054/325] cpufreq: drop K8's driver from beeing selected -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 054/327] cpufreq: drop K8's driver from beeing selected +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Ralf posted a picture of a backtrace from @@ -35,5 +38,5 @@ index 35f71825b7f3..bb4a6160d0f7 100644 This adds the CPUFreq driver for K8/early Opteron/Athlon64 processors. Support for K10 and newer processors is now in acpi-cpufreq. -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0055-md-disable-bcache.patch b/debian/patches-rt/0055-md-disable-bcache.patch index 538ca1a4e..acfa852be 100644 --- a/debian/patches-rt/0055-md-disable-bcache.patch +++ b/debian/patches-rt/0055-md-disable-bcache.patch @@ -1,11 +1,14 @@ -From 248d9794b36b5701308e7a624204d116f681240f Mon Sep 17 00:00:00 2001 +From 4577b0695f66714783f37d0405ab0c346b454932 Mon Sep 17 00:00:00 2001 +Message-Id: <4577b0695f66714783f37d0405ab0c346b454932.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 11:48:57 +0200 -Subject: [PATCH 055/325] md: disable bcache +Subject: [PATCH 055/327] md: disable bcache MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz It uses anon semaphores |drivers/md/bcache/request.c: In function ‘cached_dev_write_complete’: @@ -37,5 +40,5 @@ index f6e0a8b3a61e..18c03d79a442 100644 help Allows a block device to be used as cache for other devices; uses -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0056-efi-Disable-runtime-services-on-RT.patch b/debian/patches-rt/0056-efi-Disable-runtime-services-on-RT.patch index 134aeb647..7417d4e1c 100644 --- a/debian/patches-rt/0056-efi-Disable-runtime-services-on-RT.patch +++ b/debian/patches-rt/0056-efi-Disable-runtime-services-on-RT.patch @@ -1,8 +1,11 @@ -From 1bfed58b8d4d1812c80dbd9d096d5e1e011ca0fc Mon Sep 17 00:00:00 2001 +From c62d404a7168f5f8a35b729d4d9c2dd239749d77 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:03:16 +0200 -Subject: [PATCH 056/325] efi: Disable runtime services on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 056/327] efi: Disable runtime services on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Based on meassurements the EFI functions get_variable / get_next_variable take up to 2us which looks okay. @@ -29,7 +32,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c -index 5db20908aa9c..1708505fdf5d 100644 +index 3d5cbd3eedb4..555e45122bf5 100644 --- a/drivers/firmware/efi/efi.c +++ b/drivers/firmware/efi/efi.c @@ -87,7 +87,7 @@ struct mm_struct efi_mm = { @@ -42,5 +45,5 @@ index 5db20908aa9c..1708505fdf5d 100644 { disable_runtime = true; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0057-printk-Add-a-printk-kill-switch.patch b/debian/patches-rt/0057-printk-Add-a-printk-kill-switch.patch index 0719499b6..899b3a425 100644 --- a/debian/patches-rt/0057-printk-Add-a-printk-kill-switch.patch +++ b/debian/patches-rt/0057-printk-Add-a-printk-kill-switch.patch @@ -1,8 +1,11 @@ -From b19916a6a05bf459669c0666d128f744d601c728 Mon Sep 17 00:00:00 2001 +From c52a01426d383f219e672d2467a5c665663be377 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 22 Jul 2011 17:58:40 +0200 -Subject: [PATCH 057/325] printk: Add a printk kill switch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 057/327] printk: Add a printk kill switch +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Add a prinkt-kill-switch. This is used from (NMI) watchdog to ensure that it does not dead-lock with the early printk code. @@ -170,5 +173,5 @@ index 71381168dede..685443375dc0 100644 nmi_panic(regs, "Hard LOCKUP"); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0058-printk-Add-force_early_printk-boot-param-to-help-wit.patch b/debian/patches-rt/0058-printk-Add-force_early_printk-boot-param-to-help-wit.patch index 51a53d72b..2bb599a0e 100644 --- a/debian/patches-rt/0058-printk-Add-force_early_printk-boot-param-to-help-wit.patch +++ b/debian/patches-rt/0058-printk-Add-force_early_printk-boot-param-to-help-wit.patch @@ -1,9 +1,12 @@ -From 435cedf56c779ff8b0aff154014fac752d0cfc53 Mon Sep 17 00:00:00 2001 +From 4bff794a89e6457eb993efdf28add5adc54c7c67 Mon Sep 17 00:00:00 2001 +Message-Id: <4bff794a89e6457eb993efdf28add5adc54c7c67.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Peter Zijlstra Date: Fri, 2 Sep 2011 14:41:29 +0200 -Subject: [PATCH 058/325] printk: Add "force_early_printk" boot param to help +Subject: [PATCH 058/327] printk: Add "force_early_printk" boot param to help with debugging -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Gives me an option to screw printk and actually see what the machine says. @@ -35,5 +38,5 @@ index 29838e532f46..f934baed564d 100644 { printk_killswitch = true; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0059-preempt-Provide-preempt_-_-no-rt-variants.patch b/debian/patches-rt/0059-preempt-Provide-preempt_-_-no-rt-variants.patch index 7219e2187..078b52f90 100644 --- a/debian/patches-rt/0059-preempt-Provide-preempt_-_-no-rt-variants.patch +++ b/debian/patches-rt/0059-preempt-Provide-preempt_-_-no-rt-variants.patch @@ -1,8 +1,11 @@ -From 0f4ab1168734c622efbc4fd6b4def90ab992be6b Mon Sep 17 00:00:00 2001 +From dd900385018514a60bcc9360375c61a5410c61ba Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 24 Jul 2009 12:38:56 +0200 -Subject: [PATCH 059/325] preempt: Provide preempt_*_(no)rt variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 059/327] preempt: Provide preempt_*_(no)rt variants +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz RT needs a few preempt_disable/enable points which are not necessary otherwise. Implement variants to avoid #ifdeffery. @@ -49,5 +52,5 @@ index 3196d0e76719..f7a17fcc3fec 100644 struct preempt_notifier; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0060-futex-workaround-migrate_disable-enable-in-different.patch b/debian/patches-rt/0060-futex-workaround-migrate_disable-enable-in-different.patch index 4cff2aa66..177a2fc02 100644 --- a/debian/patches-rt/0060-futex-workaround-migrate_disable-enable-in-different.patch +++ b/debian/patches-rt/0060-futex-workaround-migrate_disable-enable-in-different.patch @@ -1,9 +1,12 @@ -From f9c934a2065deec2a867e69c90d82e5f01a0031a Mon Sep 17 00:00:00 2001 +From 4167e3164bcb032ee75d8bf13ad7a738efda1089 Mon Sep 17 00:00:00 2001 +Message-Id: <4167e3164bcb032ee75d8bf13ad7a738efda1089.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Mar 2017 14:23:35 +0100 -Subject: [PATCH 060/325] futex: workaround migrate_disable/enable in different +Subject: [PATCH 060/327] futex: workaround migrate_disable/enable in different context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz migrate_disable()/migrate_enable() takes a different path in atomic() vs !atomic() context. These little hacks ensure that we don't underflow / overflow @@ -66,5 +69,5 @@ index 920d853a8e9e..32f9e3fa8c46 100644 /* -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0061-rt-Add-local-irq-locks.patch b/debian/patches-rt/0061-rt-Add-local-irq-locks.patch index 6e4461348..f227b3ac3 100644 --- a/debian/patches-rt/0061-rt-Add-local-irq-locks.patch +++ b/debian/patches-rt/0061-rt-Add-local-irq-locks.patch @@ -1,8 +1,11 @@ -From e14e89e35c111f053cf74355bdc468577cdddf32 Mon Sep 17 00:00:00 2001 +From 9f6ecffc6d635246096f7ec3969d41610a935758 Mon Sep 17 00:00:00 2001 +Message-Id: <9f6ecffc6d635246096f7ec3969d41610a935758.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 20 Jun 2011 09:03:47 +0200 -Subject: [PATCH 061/325] rt: Add local irq locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 061/327] rt: Add local irq locks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Introduce locallock. For !RT this maps to preempt_disable()/ local_irq_disable() so there is not much that changes. For RT this will @@ -337,5 +340,5 @@ index 70b7123f38c7..24421bf8c4b3 100644 #define PCPU_MIN_UNIT_SIZE PFN_ALIGN(32 << 10) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0062-locallock-provide-get-put-_locked_ptr-variants.patch b/debian/patches-rt/0062-locallock-provide-get-put-_locked_ptr-variants.patch index 94fe7a5e7..619d1ab97 100644 --- a/debian/patches-rt/0062-locallock-provide-get-put-_locked_ptr-variants.patch +++ b/debian/patches-rt/0062-locallock-provide-get-put-_locked_ptr-variants.patch @@ -1,8 +1,11 @@ -From 0dc8625af525103cb6b43e7f73288315aa9182c2 Mon Sep 17 00:00:00 2001 +From fb993bc3f80687fab2eeca35f423f962c0b4fab2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:56 -0500 -Subject: [PATCH 062/325] locallock: provide {get,put}_locked_ptr() variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 062/327] locallock: provide {get,put}_locked_ptr() variants +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Provide a set of locallocked accessors for pointers to per-CPU data; this is useful for dynamically-allocated per-CPU regions, for example. @@ -45,5 +48,5 @@ index d658c2552601..921eab83cd34 100644 #define local_lock_cpu(lvar) get_cpu() #define local_unlock_cpu(lvar) put_cpu() -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0063-mm-scatterlist-Do-not-disable-irqs-on-RT.patch b/debian/patches-rt/0063-mm-scatterlist-Do-not-disable-irqs-on-RT.patch index 2ef76c588..3b443393e 100644 --- a/debian/patches-rt/0063-mm-scatterlist-Do-not-disable-irqs-on-RT.patch +++ b/debian/patches-rt/0063-mm-scatterlist-Do-not-disable-irqs-on-RT.patch @@ -1,8 +1,11 @@ -From 9977834321f77cd9919949417d7aff598ed71023 Mon Sep 17 00:00:00 2001 +From e7231e5dd20630c1cafcbd17ac28158f6b83df67 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:34 -0500 -Subject: [PATCH 063/325] mm/scatterlist: Do not disable irqs on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 063/327] mm/scatterlist: Do not disable irqs on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz For -RT it is enough to keep pagefault disabled (which is currently handled by kmap_atomic()). @@ -26,5 +29,5 @@ index 60e7eca2f4be..aad8b9ecd496 100644 } else kunmap(miter->page); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0064-signal-x86-Delay-calling-signals-in-atomic.patch b/debian/patches-rt/0064-signal-x86-Delay-calling-signals-in-atomic.patch index af7c74f71..9194e9a7e 100644 --- a/debian/patches-rt/0064-signal-x86-Delay-calling-signals-in-atomic.patch +++ b/debian/patches-rt/0064-signal-x86-Delay-calling-signals-in-atomic.patch @@ -1,8 +1,11 @@ -From f2ef7528019291f9ad8d4cf90b57d315f8accd38 Mon Sep 17 00:00:00 2001 +From 6142215abb31c009bcb3fade2ad2a2d08e8b83d3 Mon Sep 17 00:00:00 2001 +Message-Id: <6142215abb31c009bcb3fade2ad2a2d08e8b83d3.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Oleg Nesterov Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 064/325] signal/x86: Delay calling signals in atomic -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 064/327] signal/x86: Delay calling signals in atomic +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On x86_64 we must disable preemption before we enable interrupts for stack faults, int3 and debugging, because the current task is using @@ -80,7 +83,7 @@ index 33d3c88a7225..fb0438d06ca7 100644 typedef sigset_t compat_sigset_t; #endif diff --git a/include/linux/sched.h b/include/linux/sched.h -index 0489d3e0e78c..e4af260f81c5 100644 +index 3277801f519d..3b0a95e10939 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -881,6 +881,10 @@ struct task_struct { @@ -95,7 +98,7 @@ index 0489d3e0e78c..e4af260f81c5 100644 size_t sas_ss_size; unsigned int sas_ss_flags; diff --git a/kernel/signal.c b/kernel/signal.c -index feeae7177ee1..d1fa3c405784 100644 +index f810797e48cb..6f7191a72103 100644 --- a/kernel/signal.c +++ b/kernel/signal.c @@ -1282,8 +1282,8 @@ int do_send_sig_info(int sig, struct siginfo *info, struct task_struct *p, @@ -150,5 +153,5 @@ index feeae7177ee1..d1fa3c405784 100644 * Nuke all other threads in the group. */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0065-x86-signal-delay-calling-signals-on-32bit.patch b/debian/patches-rt/0065-x86-signal-delay-calling-signals-on-32bit.patch index e01550a81..f68aa7c57 100644 --- a/debian/patches-rt/0065-x86-signal-delay-calling-signals-on-32bit.patch +++ b/debian/patches-rt/0065-x86-signal-delay-calling-signals-on-32bit.patch @@ -1,8 +1,11 @@ -From ad228035652dbf96f3ee14ca10e14e85fb4e5b3c Mon Sep 17 00:00:00 2001 +From e314282c5471e279928516be35ffa9bb2cc119f6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Yang Shi Date: Thu, 10 Dec 2015 10:58:51 -0800 -Subject: [PATCH 065/325] x86/signal: delay calling signals on 32bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 065/327] x86/signal: delay calling signals on 32bit +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz When running some ptrace single step tests on x86-32 machine, the below problem is triggered: @@ -45,5 +48,5 @@ index fb0438d06ca7..c00e27af2205 100644 #endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0066-buffer_head-Replace-bh_uptodate_lock-for-rt.patch b/debian/patches-rt/0066-buffer_head-Replace-bh_uptodate_lock-for-rt.patch index 2b504b3c5..dc5181d99 100644 --- a/debian/patches-rt/0066-buffer_head-Replace-bh_uptodate_lock-for-rt.patch +++ b/debian/patches-rt/0066-buffer_head-Replace-bh_uptodate_lock-for-rt.patch @@ -1,8 +1,11 @@ -From 9c2e7dffa272d9112c453d37bf48c92bb1b4d287 Mon Sep 17 00:00:00 2001 +From b08a29a9d276cd58847e046d0adc6e8b7870bc67 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 09:18:52 +0100 -Subject: [PATCH 066/325] buffer_head: Replace bh_uptodate_lock for -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 066/327] buffer_head: Replace bh_uptodate_lock for -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Wrap the bit_spin_lock calls into a separate inline and add the RT replacements with a real spinlock. @@ -16,7 +19,7 @@ Signed-off-by: Thomas Gleixner 4 files changed, 46 insertions(+), 25 deletions(-) diff --git a/fs/buffer.c b/fs/buffer.c -index a550e0d8e965..a5b3a456dbff 100644 +index c49fdab5cb36..b649c4d58637 100644 --- a/fs/buffer.c +++ b/fs/buffer.c @@ -274,8 +274,7 @@ static void end_buffer_async_read(struct buffer_head *bh, int uptodate) @@ -78,7 +81,7 @@ index a550e0d8e965..a5b3a456dbff 100644 } EXPORT_SYMBOL(end_buffer_async_write); -@@ -3368,6 +3360,7 @@ struct buffer_head *alloc_buffer_head(gfp_t gfp_flags) +@@ -3379,6 +3371,7 @@ struct buffer_head *alloc_buffer_head(gfp_t gfp_flags) struct buffer_head *ret = kmem_cache_zalloc(bh_cachep, gfp_flags); if (ret) { INIT_LIST_HEAD(&ret->b_assoc_buffers); @@ -146,7 +149,7 @@ index 8946130c87ad..71d0b3ba70f8 100644 /** diff --git a/include/linux/buffer_head.h b/include/linux/buffer_head.h -index 96225a77c112..8a1bcfb145d7 100644 +index 9168fc33a4f7..572541d6cc90 100644 --- a/include/linux/buffer_head.h +++ b/include/linux/buffer_head.h @@ -76,8 +76,42 @@ struct buffer_head { @@ -193,5 +196,5 @@ index 96225a77c112..8a1bcfb145d7 100644 * macro tricks to expand the set_buffer_foo(), clear_buffer_foo() * and buffer_foo() functions. -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0067-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch b/debian/patches-rt/0067-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch index 2a0fa418b..ac76dbd01 100644 --- a/debian/patches-rt/0067-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch +++ b/debian/patches-rt/0067-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch @@ -1,9 +1,12 @@ -From c6247543e73c08256490bf6ccd225a3476eefd3a Mon Sep 17 00:00:00 2001 +From 48ab2622802d5673b7a70938e105302459a1cf0c Mon Sep 17 00:00:00 2001 +Message-Id: <48ab2622802d5673b7a70938e105302459a1cf0c.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 10:11:25 +0100 -Subject: [PATCH 067/325] fs: jbd/jbd2: Make state lock and journal head lock +Subject: [PATCH 067/327] fs: jbd/jbd2: Make state lock and journal head lock rt safe -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz bit_spin_locks break under RT. @@ -19,7 +22,7 @@ Signed-off-by: Thomas Gleixner 2 files changed, 32 insertions(+) diff --git a/include/linux/buffer_head.h b/include/linux/buffer_head.h -index 8a1bcfb145d7..5869330d1f38 100644 +index 572541d6cc90..703bf3335a3d 100644 --- a/include/linux/buffer_head.h +++ b/include/linux/buffer_head.h @@ -78,6 +78,10 @@ struct buffer_head { @@ -106,5 +109,5 @@ index 268f3000d1b3..8f5d6ecb802e 100644 #define J_ASSERT(assert) BUG_ON(!(assert)) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0068-list_bl-Make-list-head-locking-RT-safe.patch b/debian/patches-rt/0068-list_bl-Make-list-head-locking-RT-safe.patch index 48216bb60..713fc5262 100644 --- a/debian/patches-rt/0068-list_bl-Make-list-head-locking-RT-safe.patch +++ b/debian/patches-rt/0068-list_bl-Make-list-head-locking-RT-safe.patch @@ -1,8 +1,11 @@ -From ffb1cb4821d5ac6ec3e2f69dc118584321113848 Mon Sep 17 00:00:00 2001 +From 57cc0b8d65688453d22cf66aba450d1eb5a8c98a Mon Sep 17 00:00:00 2001 +Message-Id: <57cc0b8d65688453d22cf66aba450d1eb5a8c98a.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Paul Gortmaker Date: Fri, 21 Jun 2013 15:07:25 -0400 -Subject: [PATCH 068/325] list_bl: Make list head locking RT safe -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 068/327] list_bl: Make list head locking RT safe +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz As per changes in include/linux/jbd_common.h for avoiding the bit_spin_locks on RT ("fs: jbd/jbd2: Make state lock and journal @@ -117,5 +120,5 @@ index 3fc2cc57ba1b..69b659259bac 100644 static inline bool hlist_bl_is_locked(struct hlist_bl_head *b) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0069-list_bl-fixup-bogus-lockdep-warning.patch b/debian/patches-rt/0069-list_bl-fixup-bogus-lockdep-warning.patch index 5ea2d4cda..b94d61d8b 100644 --- a/debian/patches-rt/0069-list_bl-fixup-bogus-lockdep-warning.patch +++ b/debian/patches-rt/0069-list_bl-fixup-bogus-lockdep-warning.patch @@ -1,8 +1,11 @@ -From bdcdc6774f7346b9302a7cf88c2c6ad00afe3459 Mon Sep 17 00:00:00 2001 +From e3aad949c572926872e1fb2d6c943cc0d74f51ef Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 31 Mar 2016 00:04:25 -0500 -Subject: [PATCH 069/325] list_bl: fixup bogus lockdep warning -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 069/327] list_bl: fixup bogus lockdep warning +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz At first glance, the use of 'static inline' seems appropriate for INIT_HLIST_BL_HEAD(). @@ -100,5 +103,5 @@ index 69b659259bac..0b5de7d9ffcf 100644 static inline void INIT_HLIST_BL_NODE(struct hlist_bl_node *h) { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch b/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch index 585a215c9..83af85af5 100644 --- a/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch +++ b/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch @@ -1,8 +1,11 @@ -From 7cebafc45724ddb601b485b97c0c931378a7d60d Mon Sep 17 00:00:00 2001 +From 2a9efdf100596f35e61e0f712b68f5bda3dc7b99 Mon Sep 17 00:00:00 2001 +Message-Id: <2a9efdf100596f35e61e0f712b68f5bda3dc7b99.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:57 -0500 -Subject: [PATCH 070/325] genirq: Disable irqpoll on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 070/327] genirq: Disable irqpoll on -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Creates long latencies for no value @@ -39,5 +42,5 @@ index d867d6ddafdd..cd12ee86c01e 100644 printk(KERN_WARNING "Misrouted IRQ fixup and polling support " "enabled\n"); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0071-genirq-Force-interrupt-thread-on-RT.patch b/debian/patches-rt/0071-genirq-Force-interrupt-thread-on-RT.patch index 75217ff85..ddb4efe98 100644 --- a/debian/patches-rt/0071-genirq-Force-interrupt-thread-on-RT.patch +++ b/debian/patches-rt/0071-genirq-Force-interrupt-thread-on-RT.patch @@ -1,8 +1,11 @@ -From 7dca342c202dd085c2ed2817d5bf9bdfb8d9fd4b Mon Sep 17 00:00:00 2001 +From 8de462e06c1de7e3cc9b0eaa6d5c6f7368c22b6f Mon Sep 17 00:00:00 2001 +Message-Id: <8de462e06c1de7e3cc9b0eaa6d5c6f7368c22b6f.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 3 Apr 2011 11:57:29 +0200 -Subject: [PATCH 071/325] genirq: Force interrupt thread on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 071/327] genirq: Force interrupt thread on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Force threaded_irqs and optimize the code (force_irqthreads) in regard to this. @@ -50,5 +53,5 @@ index efcb54ee0922..0809bf7743af 100644 static void __synchronize_hardirq(struct irq_desc *desc, bool sync_chip) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0072-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch b/debian/patches-rt/0072-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch index 5fc7f97f9..1d84c43ea 100644 --- a/debian/patches-rt/0072-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch +++ b/debian/patches-rt/0072-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch @@ -1,9 +1,12 @@ -From 2e4f0bf4e4b7f98603bec063dc960b95fd97fbce Mon Sep 17 00:00:00 2001 +From 70454fd8a8f7c8caa65becb67bb179cfe4ebce8a Mon Sep 17 00:00:00 2001 +Message-Id: <70454fd8a8f7c8caa65becb67bb179cfe4ebce8a.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:20 +0200 -Subject: [PATCH 072/325] Split IRQ-off and zone->lock while freeing pages from +Subject: [PATCH 072/327] Split IRQ-off and zone->lock while freeing pages from PCP list #1 -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. @@ -18,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 52 insertions(+), 30 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c -index e5c610d711f3..0cfcd42517a4 100644 +index 57888cedf244..b8138a5d6ef3 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1095,7 +1095,7 @@ static inline void prefetch_buddy(struct page *page) @@ -169,5 +172,5 @@ index e5c610d711f3..0cfcd42517a4 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch b/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch index ac0fe81fe..4253afd62 100644 --- a/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch +++ b/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch @@ -1,9 +1,12 @@ -From e2fc0821dfc12bc01f49756080b4563f0fc2c45c Mon Sep 17 00:00:00 2001 +From 1f4423aeb9a88fef1113af43d1694859d2361e3e Mon Sep 17 00:00:00 2001 +Message-Id: <1f4423aeb9a88fef1113af43d1694859d2361e3e.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:21 +0200 -Subject: [PATCH 073/325] Split IRQ-off and zone->lock while freeing pages from +Subject: [PATCH 073/327] Split IRQ-off and zone->lock while freeing pages from PCP list #2 -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. @@ -18,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 50 insertions(+), 10 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c -index 0cfcd42517a4..9a4d150ea5b7 100644 +index b8138a5d6ef3..19f274de32f0 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1105,8 +1105,8 @@ static inline void prefetch_buddy(struct page *page) @@ -168,5 +171,5 @@ index 0cfcd42517a4..9a4d150ea5b7 100644 /* -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch index dc7cc9639..fb08e4acc 100644 --- a/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch @@ -1,8 +1,11 @@ -From 32c26f054fbd92f8fe27eba2443d9d7490232aa3 Mon Sep 17 00:00:00 2001 +From 70c54093e553bef72c4d5a174f1590eea0e8dfdb Mon Sep 17 00:00:00 2001 +Message-Id: <70c54093e553bef72c4d5a174f1590eea0e8dfdb.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 28 May 2018 15:24:22 +0200 -Subject: [PATCH 074/325] mm/SLxB: change list_lock to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 074/327] mm/SLxB: change list_lock to raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The list_lock is used with used with IRQs off on RT. Make it a raw_spinlock_t otherwise the interrupts won't be disabled on -RT. The locking rules remain @@ -399,7 +402,7 @@ index 9632772e14be..d6b01d61f768 100644 #ifdef CONFIG_SLAB struct list_head slabs_partial; /* partial list first, better asm code */ diff --git a/mm/slub.c b/mm/slub.c -index 9b7b989273d4..a3b4c5c04ffe 100644 +index d8116a43a287..83ca3f1c0d86 100644 --- a/mm/slub.c +++ b/mm/slub.c @@ -1167,7 +1167,7 @@ static noinline int free_debug_processing( @@ -615,5 +618,5 @@ index 9b7b989273d4..a3b4c5c04ffe 100644 for (i = 0; i < t.count; i++) { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0075-mm-SLUB-delay-giving-back-empty-slubs-to-IRQ-enabled.patch b/debian/patches-rt/0075-mm-SLUB-delay-giving-back-empty-slubs-to-IRQ-enabled.patch index 66bdfc1c1..e75b4aa91 100644 --- a/debian/patches-rt/0075-mm-SLUB-delay-giving-back-empty-slubs-to-IRQ-enabled.patch +++ b/debian/patches-rt/0075-mm-SLUB-delay-giving-back-empty-slubs-to-IRQ-enabled.patch @@ -1,9 +1,12 @@ -From 6e725f0366939a0d83764cd8835200cb222bb1af Mon Sep 17 00:00:00 2001 +From 6f6587f18a69bb2cc89c39e1eef158658ef63e62 Mon Sep 17 00:00:00 2001 +Message-Id: <6f6587f18a69bb2cc89c39e1eef158658ef63e62.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 21 Jun 2018 17:29:19 +0200 -Subject: [PATCH 075/325] mm/SLUB: delay giving back empty slubs to IRQ enabled +Subject: [PATCH 075/327] mm/SLUB: delay giving back empty slubs to IRQ enabled regions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz __free_slab() is invoked with disabled interrupts which increases the irq-off time while __free_pages() is doing the work. @@ -18,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 69 insertions(+), 5 deletions(-) diff --git a/mm/slub.c b/mm/slub.c -index a3b4c5c04ffe..19bc021a2726 100644 +index 83ca3f1c0d86..7a0706ccdf30 100644 --- a/mm/slub.c +++ b/mm/slub.c @@ -1330,6 +1330,12 @@ static inline void dec_slabs_node(struct kmem_cache *s, int node, @@ -219,5 +222,5 @@ index a3b4c5c04ffe..19bc021a2726 100644 if (debug_guardpage_minorder()) slub_max_order = 0; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0076-mm-page_alloc-rt-friendly-per-cpu-pages.patch b/debian/patches-rt/0076-mm-page_alloc-rt-friendly-per-cpu-pages.patch index 4307bef11..1d8be3406 100644 --- a/debian/patches-rt/0076-mm-page_alloc-rt-friendly-per-cpu-pages.patch +++ b/debian/patches-rt/0076-mm-page_alloc-rt-friendly-per-cpu-pages.patch @@ -1,8 +1,11 @@ -From 3c705eb7ff76685a9c4b40776b6d975e64cf6df0 Mon Sep 17 00:00:00 2001 +From 5c03bb8685149b61919cf8bf3a273e9a3e4e7634 Mon Sep 17 00:00:00 2001 +Message-Id: <5c03bb8685149b61919cf8bf3a273e9a3e4e7634.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:37 -0500 -Subject: [PATCH 076/325] mm: page_alloc: rt-friendly per-cpu pages -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 076/327] mm: page_alloc: rt-friendly per-cpu pages +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz rt-friendly per-cpu pages: convert the irqs-off per-cpu locking method into a preemptible, explicit-per-cpu-locks method. @@ -18,7 +21,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 43 insertions(+), 20 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c -index 9a4d150ea5b7..d6f9be9c6635 100644 +index 19f274de32f0..4180a5312060 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -60,6 +60,7 @@ @@ -235,5 +238,5 @@ index 9a4d150ea5b7..d6f9be9c6635 100644 #ifdef CONFIG_MEMORY_HOTREMOVE -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch b/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch index 321dfd617..0e8977e20 100644 --- a/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch +++ b/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch @@ -1,8 +1,11 @@ -From c1c0dcf5b79064717f21d1c3d294827591fea472 Mon Sep 17 00:00:00 2001 +From 8db6812f18080154df9d8679ce16af51a8ba4fe3 Mon Sep 17 00:00:00 2001 +Message-Id: <8db6812f18080154df9d8679ce16af51a8ba4fe3.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:51 -0500 -Subject: [PATCH 077/325] mm/swap: Convert to percpu locked -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 077/327] mm/swap: Convert to percpu locked +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Replace global locks (get_cpu + local_irq_save) with "local_locks()". Currently there is one of for "rotate" and one for "swap". @@ -56,7 +59,7 @@ index 5079ddbec8f9..c40d3a13cbbd 100644 cc->last_migrated_pfn = 0; } diff --git a/mm/page_alloc.c b/mm/page_alloc.c -index d6f9be9c6635..a1547f1be42c 100644 +index 4180a5312060..889b4089b289 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -7242,8 +7242,9 @@ void __init free_area_init(unsigned long *zones_size) @@ -207,5 +210,5 @@ index 45fdbfb6b2a6..92f994b962f0 100644 #ifdef CONFIG_SMP -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch b/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch index 3cf9bc424..3c26c0418 100644 --- a/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch +++ b/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch @@ -1,8 +1,11 @@ -From 1025690c55aad067878962af6318286d26c87aaa Mon Sep 17 00:00:00 2001 +From 919fb5c7ab71b28ea96b7f83055b52fcc5c9119c Mon Sep 17 00:00:00 2001 +Message-Id: <919fb5c7ab71b28ea96b7f83055b52fcc5c9119c.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Luiz Capitulino Date: Fri, 27 May 2016 15:03:28 +0200 -Subject: [PATCH 078/325] mm: perform lru_add_drain_all() remotely -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 078/327] mm: perform lru_add_drain_all() remotely +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz lru_add_drain_all() works by scheduling lru_add_drain_cpu() to run on all CPUs that have non-empty LRU pagevecs and then waiting for @@ -105,5 +108,5 @@ index 92f994b962f0..3885645a45ce 100644 mutex_unlock(&lock); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0079-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch b/debian/patches-rt/0079-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch index 6d3942817..e0ac49eb1 100644 --- a/debian/patches-rt/0079-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch +++ b/debian/patches-rt/0079-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch @@ -1,9 +1,12 @@ -From 92905381cb530f0b66c5d80a2877e1994e775676 Mon Sep 17 00:00:00 2001 +From 36be6e4e76ea93741b345abb97d40b48eab57cac Mon Sep 17 00:00:00 2001 +Message-Id: <36be6e4e76ea93741b345abb97d40b48eab57cac.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:30:13 -0500 -Subject: [PATCH 079/325] mm/vmstat: Protect per cpu variables with preempt +Subject: [PATCH 079/327] mm/vmstat: Protect per cpu variables with preempt disable on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Disable preemption on -RT for the vmstat code. On vanila the code runs in IRQ-off regions while on -RT it is not. "preempt_disable" ensures that the @@ -141,5 +144,5 @@ index ce81b0a7d018..cfa2a3bbdf91 100644 void __dec_zone_page_state(struct page *page, enum zone_stat_item item) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0080-ARM-Initialize-split-page-table-locks-for-vector-pag.patch b/debian/patches-rt/0080-ARM-Initialize-split-page-table-locks-for-vector-pag.patch index ed56a8bc3..38fa7c0a6 100644 --- a/debian/patches-rt/0080-ARM-Initialize-split-page-table-locks-for-vector-pag.patch +++ b/debian/patches-rt/0080-ARM-Initialize-split-page-table-locks-for-vector-pag.patch @@ -1,9 +1,12 @@ -From fff91e4cb5539ab6cdd32a15661e2f5354552fdb Mon Sep 17 00:00:00 2001 +From d904f1ae3ddf7b7f19c043f65a1dc8f681cdc4aa Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Frank Rowand Date: Sat, 1 Oct 2011 18:58:13 -0700 -Subject: [PATCH 080/325] ARM: Initialize split page table locks for vector +Subject: [PATCH 080/327] ARM: Initialize split page table locks for vector page -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Without this patch, ARM can not use SPLIT_PTLOCK_CPUS if PREEMPT_RT_FULL=y because vectors_user_mapping() creates a @@ -72,5 +75,5 @@ index 82ab015bf42b..8d3c7ce34c24 100644 /* * The vectors page is always readable from user space for the -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch b/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch index c0e2cc5e9..a8fd25b41 100644 --- a/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch +++ b/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch @@ -1,8 +1,11 @@ -From 82e554da6555d60e1a8e5c390a27a12d338f1b53 Mon Sep 17 00:00:00 2001 +From 43968d25f34cc0c7e453f17c63fa23dc50bccff6 Mon Sep 17 00:00:00 2001 +Message-Id: <43968d25f34cc0c7e453f17c63fa23dc50bccff6.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 25 Oct 2012 10:32:35 +0100 -Subject: [PATCH 081/325] mm: Enable SLUB for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 081/327] mm: Enable SLUB for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Avoid the memory allocation in IRQ section @@ -14,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 6 insertions(+) diff --git a/mm/slub.c b/mm/slub.c -index 19bc021a2726..181b2cb6ffbb 100644 +index 7a0706ccdf30..f3fcb9502093 100644 --- a/mm/slub.c +++ b/mm/slub.c @@ -3699,6 +3699,11 @@ static void list_slab_objects(struct kmem_cache *s, struct page *page, @@ -38,5 +41,5 @@ index 19bc021a2726..181b2cb6ffbb 100644 /* -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0082-slub-Enable-irqs-for-__GFP_WAIT.patch b/debian/patches-rt/0082-slub-Enable-irqs-for-__GFP_WAIT.patch index dfc9852c4..c7eeb73a4 100644 --- a/debian/patches-rt/0082-slub-Enable-irqs-for-__GFP_WAIT.patch +++ b/debian/patches-rt/0082-slub-Enable-irqs-for-__GFP_WAIT.patch @@ -1,8 +1,11 @@ -From a84add7d6794ad6184fc6c5c6fbf63c20c733dac Mon Sep 17 00:00:00 2001 +From ac660441fdc328b4e835f6a2eb15ba2a9ae56a73 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 9 Jan 2013 12:08:15 +0100 -Subject: [PATCH 082/325] slub: Enable irqs for __GFP_WAIT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 082/327] slub: Enable irqs for __GFP_WAIT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz SYSTEM_RUNNING might be too late for enabling interrupts. Allocations with GFP_WAIT can happen before that. So use this as an indicator. @@ -13,7 +16,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/mm/slub.c b/mm/slub.c -index 181b2cb6ffbb..555adbd96356 100644 +index f3fcb9502093..d243c6ef7fc9 100644 --- a/mm/slub.c +++ b/mm/slub.c @@ -1570,10 +1570,17 @@ static struct page *allocate_slab(struct kmem_cache *s, gfp_t flags, int node) @@ -44,5 +47,5 @@ index 181b2cb6ffbb..555adbd96356 100644 if (!page) return NULL; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch b/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch index 783e55e37..fb0f083e0 100644 --- a/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch +++ b/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch @@ -1,8 +1,11 @@ -From 5bface7c2f9af3d585acc7f3ac3e0f8096ec4bf1 Mon Sep 17 00:00:00 2001 +From 3f101e56bfa35092043bc11d64e199792ef0234b Mon Sep 17 00:00:00 2001 +Message-Id: <3f101e56bfa35092043bc11d64e199792ef0234b.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Apr 2015 19:00:47 +0200 -Subject: [PATCH 083/325] slub: Disable SLUB_CPU_PARTIAL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 083/327] slub: Disable SLUB_CPU_PARTIAL +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:915 |in_atomic(): 1, irqs_disabled(): 0, pid: 87, name: rcuop/7 @@ -50,5 +53,5 @@ index 61e8b531649b..b4e88fb19c26 100644 help Per cpu partial caches accellerate objects allocation and freeing -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0084-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch b/debian/patches-rt/0084-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch index 9ef7c1b45..ad9c9c6d7 100644 --- a/debian/patches-rt/0084-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch +++ b/debian/patches-rt/0084-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch @@ -1,9 +1,12 @@ -From 6089b66d138cc77f35c9d6f7d526cc322b295f28 Mon Sep 17 00:00:00 2001 +From 4acb7f24767f76d8499f2818c8c823db0dcaedce Mon Sep 17 00:00:00 2001 +Message-Id: <4acb7f24767f76d8499f2818c8c823db0dcaedce.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Yang Shi Date: Wed, 30 Oct 2013 11:48:33 -0700 -Subject: [PATCH 084/325] mm/memcontrol: Don't call schedule_work_on in +Subject: [PATCH 084/327] mm/memcontrol: Don't call schedule_work_on in preemption disabled context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The following trace is triggered when running ltp oom test cases: @@ -71,5 +74,5 @@ index 3b78b6af353b..1323fa231eed 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0085-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch b/debian/patches-rt/0085-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch index d074c3108..7f16191b7 100644 --- a/debian/patches-rt/0085-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch +++ b/debian/patches-rt/0085-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch @@ -1,9 +1,12 @@ -From 3e3a73ff713a1c57585373ecc40a3079f9baff65 Mon Sep 17 00:00:00 2001 +From a6498df708e70b00c5b0dc27ae24bec3bb4544f8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 28 Jan 2015 17:14:16 +0100 -Subject: [PATCH 085/325] mm/memcontrol: Replace local_irq_disable with local +Subject: [PATCH 085/327] mm/memcontrol: Replace local_irq_disable with local locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz There are a few local_irq_disable() which then take sleeping locks. This patch converts them local locks. @@ -120,5 +123,5 @@ index 1323fa231eed..4156a4e766fb 100644 /** -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0086-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch b/debian/patches-rt/0086-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch index ba5d3cf51..d67b792af 100644 --- a/debian/patches-rt/0086-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch +++ b/debian/patches-rt/0086-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch @@ -1,8 +1,11 @@ -From 9aa358dc71da851d2af3660ac73411ad469a331f Mon Sep 17 00:00:00 2001 +From 5435ab24adf4b67ad5116ebc31ebfaf2ad9dc386 Mon Sep 17 00:00:00 2001 +Message-Id: <5435ab24adf4b67ad5116ebc31ebfaf2ad9dc386.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Tue, 22 Mar 2016 11:16:09 +0100 -Subject: [PATCH 086/325] mm/zsmalloc: copy with get_cpu_var() and locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 086/327] mm/zsmalloc: copy with get_cpu_var() and locking +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz get_cpu_var() disables preemption and triggers a might_sleep() splat later. This is replaced with get_locked_var(). @@ -199,5 +202,5 @@ index 85cc29c93d93..63e83b47fa99 100644 migrate_read_unlock(zspage); unpin_tag(handle); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0087-x86-mm-pat-disable-preemption-__split_large_page-aft.patch b/debian/patches-rt/0087-x86-mm-pat-disable-preemption-__split_large_page-aft.patch index 8d96bd90b..a3249ebe5 100644 --- a/debian/patches-rt/0087-x86-mm-pat-disable-preemption-__split_large_page-aft.patch +++ b/debian/patches-rt/0087-x86-mm-pat-disable-preemption-__split_large_page-aft.patch @@ -1,9 +1,12 @@ -From 27f3206f1c5af4a5290793529fd61d28c347c32f Mon Sep 17 00:00:00 2001 +From ebc47cf9b47497d1cd89845dce7a4a51a6da1f45 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 21:53:43 +0100 -Subject: [PATCH 087/325] x86/mm/pat: disable preemption __split_large_page() +Subject: [PATCH 087/327] x86/mm/pat: disable preemption __split_large_page() after spin_lock() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Commit "x86/mm/pat: Disable preemption around __flush_tlb_all()" added a warning if __flush_tlb_all() is invoked in preemptible context. On !RT @@ -58,5 +61,5 @@ index 101f3ad0d6ad..0b0396261ca1 100644 return 0; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0088-radix-tree-use-local-locks.patch b/debian/patches-rt/0088-radix-tree-use-local-locks.patch index bce79e521..dd2482b17 100644 --- a/debian/patches-rt/0088-radix-tree-use-local-locks.patch +++ b/debian/patches-rt/0088-radix-tree-use-local-locks.patch @@ -1,8 +1,11 @@ -From d1e6ca9dc1adeb9619ee73c22df645243a58833d Mon Sep 17 00:00:00 2001 +From 905387933bea4aee6079cb329a06a8a30481f092 Mon Sep 17 00:00:00 2001 +Message-Id: <905387933bea4aee6079cb329a06a8a30481f092.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jan 2017 16:34:27 +0100 -Subject: [PATCH 088/325] radix-tree: use local locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 088/327] radix-tree: use local locks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The preload functionality uses per-CPU variables and preempt-disable to ensure that it does not switch CPUs during its usage. This patch adds @@ -172,5 +175,5 @@ index e5cab5c4e383..9309e813bc1f 100644 if (!this_cpu_read(ida_bitmap)) { struct ida_bitmap *bitmap = kzalloc(sizeof(*bitmap), gfp); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch b/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch index 6000d0cfa..32abf2aa4 100644 --- a/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch +++ b/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch @@ -1,8 +1,11 @@ -From bf7590c47e53af70146859ca60ae05df521e60e4 Mon Sep 17 00:00:00 2001 +From d4eec20885c0c2a25d3ee5d83464077e0b77ca13 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 -Subject: [PATCH 089/325] timers: Prepare for full preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 089/327] timers: Prepare for full preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz When softirqs can be preempted we need to make sure that cancelling the timer from the active thread can not deadlock vs. a running timer @@ -172,5 +175,5 @@ index ae64cb819a9a..9019c9caf146 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0090-x86-kvm-Require-const-tsc-for-RT.patch b/debian/patches-rt/0090-x86-kvm-Require-const-tsc-for-RT.patch index b6436dc49..172e7cca3 100644 --- a/debian/patches-rt/0090-x86-kvm-Require-const-tsc-for-RT.patch +++ b/debian/patches-rt/0090-x86-kvm-Require-const-tsc-for-RT.patch @@ -1,8 +1,11 @@ -From 9d89b02f01f1b2e5a9eacb0f65b3794aae03a28c Mon Sep 17 00:00:00 2001 +From 17b7ebb5784c83799e57c61008f6f618f901ac3c Mon Sep 17 00:00:00 2001 +Message-Id: <17b7ebb5784c83799e57c61008f6f618f901ac3c.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 6 Nov 2011 12:26:18 +0100 -Subject: [PATCH 090/325] x86: kvm Require const tsc for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 090/327] x86: kvm Require const tsc for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Non constant TSC is a nightmare on bare metal already, but with virtualization it becomes a complete disaster because the workarounds @@ -15,10 +18,10 @@ Signed-off-by: Thomas Gleixner 1 file changed, 7 insertions(+) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c -index 2cb379e261c0..a94c1a01b894 100644 +index 6bfc9eaf8dee..166eaf163324 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c -@@ -6873,6 +6873,13 @@ int kvm_arch_init(void *opaque) +@@ -6877,6 +6877,13 @@ int kvm_arch_init(void *opaque) goto out; } @@ -33,5 +36,5 @@ index 2cb379e261c0..a94c1a01b894 100644 if (r) goto out_free_percpu; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0091-pci-switchtec-Don-t-use-completion-s-wait-queue.patch b/debian/patches-rt/0091-pci-switchtec-Don-t-use-completion-s-wait-queue.patch index e8281a608..0ba343ef1 100644 --- a/debian/patches-rt/0091-pci-switchtec-Don-t-use-completion-s-wait-queue.patch +++ b/debian/patches-rt/0091-pci-switchtec-Don-t-use-completion-s-wait-queue.patch @@ -1,8 +1,11 @@ -From 92f7c935ef1e9ebcae344a957f0f1cf36d9ca182 Mon Sep 17 00:00:00 2001 +From a8dd4b63ac98dd63230cfee544da29c6c7c875e6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Oct 2017 10:24:23 +0200 -Subject: [PATCH 091/325] pci/switchtec: Don't use completion's wait queue -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 091/327] pci/switchtec: Don't use completion's wait queue +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The poll callback is using completion's wait_queue_head_t member and puts it in poll_wait() so the poll() caller gets a wakeup after command @@ -19,15 +22,12 @@ test it. Cc: Kurt Schwemmer Cc: Logan Gunthorpe Signed-off-by: Sebastian Andrzej Siewior -[Salvatore Bonaccorso: Refresh for context changes in 4.19.116 due to -12ce9fd7fc87 ("PCI/switchtec: Fix init_completion race condition with -poll_wait()")] --- drivers/pci/switch/switchtec.c | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-) diff --git a/drivers/pci/switch/switchtec.c b/drivers/pci/switch/switchtec.c -index 43431816412c..a8df847bedee 100644 +index 291c0074ad6f..a8df847bedee 100644 --- a/drivers/pci/switch/switchtec.c +++ b/drivers/pci/switch/switchtec.c @@ -43,10 +43,11 @@ struct switchtec_user { @@ -114,5 +114,5 @@ index 43431816412c..a8df847bedee 100644 stuser_put(stuser); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0092-wait.h-include-atomic.h.patch b/debian/patches-rt/0092-wait.h-include-atomic.h.patch index e5fb3d8ef..1fad8d348 100644 --- a/debian/patches-rt/0092-wait.h-include-atomic.h.patch +++ b/debian/patches-rt/0092-wait.h-include-atomic.h.patch @@ -1,11 +1,14 @@ -From 62300f714d10365c00ac9d0b8b35a79be8f2fd26 Mon Sep 17 00:00:00 2001 +From c0653cc1d3e43bd0e43f3fee9dafb456ed28190a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 28 Oct 2013 12:19:57 +0100 -Subject: [PATCH 092/325] wait.h: include atomic.h +Subject: [PATCH 092/327] wait.h: include atomic.h MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz | CC init/main.o |In file included from include/linux/mmzone.h:9:0, @@ -38,5 +41,5 @@ index ed7c122cb31f..2b5ef8e94d19 100644 typedef struct wait_queue_entry wait_queue_entry_t; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0093-work-simple-Simple-work-queue-implemenation.patch b/debian/patches-rt/0093-work-simple-Simple-work-queue-implemenation.patch index b18f791b0..5ff92fb3b 100644 --- a/debian/patches-rt/0093-work-simple-Simple-work-queue-implemenation.patch +++ b/debian/patches-rt/0093-work-simple-Simple-work-queue-implemenation.patch @@ -1,8 +1,11 @@ -From 1af66c1b241adaee0ae77bcdfb1534a60d08264a Mon Sep 17 00:00:00 2001 +From 9e18254d6c03db9399865a50b4742d362e613d74 Mon Sep 17 00:00:00 2001 +Message-Id: <9e18254d6c03db9399865a50b4742d362e613d74.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Daniel Wagner Date: Fri, 11 Jul 2014 15:26:11 +0200 -Subject: [PATCH 093/325] work-simple: Simple work queue implemenation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 093/327] work-simple: Simple work queue implemenation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Provides a framework for enqueuing callbacks from irq context PREEMPT_RT_FULL safe. The callbacks are executed in kthread context. @@ -242,5 +245,5 @@ index 000000000000..a5b89fdacf19 +} +EXPORT_SYMBOL_GPL(swork_put); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0094-work-simple-drop-a-shit-statement-in-SWORK_EVENT_PEN.patch b/debian/patches-rt/0094-work-simple-drop-a-shit-statement-in-SWORK_EVENT_PEN.patch index 8f1d83b56..48d0efe52 100644 --- a/debian/patches-rt/0094-work-simple-drop-a-shit-statement-in-SWORK_EVENT_PEN.patch +++ b/debian/patches-rt/0094-work-simple-drop-a-shit-statement-in-SWORK_EVENT_PEN.patch @@ -1,9 +1,12 @@ -From 0ec9d3d9509f13ebc479c2de4abd9ba1a50eeef7 Mon Sep 17 00:00:00 2001 +From 8491c30bd13faf3015ca096ea7eb516275f42829 Mon Sep 17 00:00:00 2001 +Message-Id: <8491c30bd13faf3015ca096ea7eb516275f42829.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 10 Sep 2018 18:00:31 +0200 -Subject: [PATCH 094/325] work-simple: drop a shit statement in +Subject: [PATCH 094/327] work-simple: drop a shit statement in SWORK_EVENT_PENDING -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Dan Carpenter reported | smatch warnings: @@ -33,5 +36,5 @@ index a5b89fdacf19..c90d14b9b126 100644 static DEFINE_MUTEX(worker_mutex); static struct sworker *glob_worker; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch b/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch index dc5b72287..281eb0bce 100644 --- a/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch +++ b/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch @@ -1,8 +1,11 @@ -From b44f079dc57b192c97e92355b26180aaf99b6678 Mon Sep 17 00:00:00 2001 +From ff3fe1c0c7ede76e82b6bcae4929af93851e4bbc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 11 Jan 2013 11:23:51 +0100 -Subject: [PATCH 095/325] completion: Use simple wait queues -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 095/327] completion: Use simple wait queues +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Completions have no long lasting callbacks and therefor do not need the complex waitqueue variant. Use simple waitqueues which reduces the @@ -55,10 +58,10 @@ index b704e4bce171..c364abaac548 100644 break; default: diff --git a/drivers/usb/gadget/function/f_fs.c b/drivers/usb/gadget/function/f_fs.c -index a9239455eb6d..ed56d61d888a 100644 +index 11a501d0664c..1fe8a1b359d6 100644 --- a/drivers/usb/gadget/function/f_fs.c +++ b/drivers/usb/gadget/function/f_fs.c -@@ -1627,7 +1627,7 @@ static void ffs_data_put(struct ffs_data *ffs) +@@ -1628,7 +1628,7 @@ static void ffs_data_put(struct ffs_data *ffs) pr_info("%s(): freeing\n", __func__); ffs_data_clear(ffs); BUG_ON(waitqueue_active(&ffs->ev.waitq) || @@ -387,5 +390,5 @@ index 66b59ac77c22..c7cb30cdd1b7 100644 wait->task = current; if (list_empty(&wait->task_list)) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0096-fs-aio-simple-simple-work.patch b/debian/patches-rt/0096-fs-aio-simple-simple-work.patch index 3e4fb38ed..504ede051 100644 --- a/debian/patches-rt/0096-fs-aio-simple-simple-work.patch +++ b/debian/patches-rt/0096-fs-aio-simple-simple-work.patch @@ -1,8 +1,11 @@ -From 0bc73d798d3c94781bed15e4ee21c8de0a616835 Mon Sep 17 00:00:00 2001 +From d559faa98e79d0b61a303cf6d6c537f4d689ab47 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 -Subject: [PATCH 096/325] fs/aio: simple simple work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 096/327] fs/aio: simple simple work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:768 |in_atomic(): 1, irqs_disabled(): 0, pid: 26, name: rcuos/2 @@ -85,5 +88,5 @@ index b5fbf2061868..93f8cf7fdeab 100644 { unsigned i, new_nr; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0097-time-hrtimer-avoid-schedule_work-with-interrupts-dis.patch b/debian/patches-rt/0097-time-hrtimer-avoid-schedule_work-with-interrupts-dis.patch index d12e855a4..65e3476b2 100644 --- a/debian/patches-rt/0097-time-hrtimer-avoid-schedule_work-with-interrupts-dis.patch +++ b/debian/patches-rt/0097-time-hrtimer-avoid-schedule_work-with-interrupts-dis.patch @@ -1,9 +1,12 @@ -From 14c8c3829b5d445e2e8d2d0faa3d5aefffd4057d Mon Sep 17 00:00:00 2001 +From b441e3f0879e664e8a57feb984aca62a3e9fc16a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Nov 2017 17:29:51 +0100 -Subject: [PATCH 097/325] time/hrtimer: avoid schedule_work() with interrupts +Subject: [PATCH 097/327] time/hrtimer: avoid schedule_work() with interrupts disabled -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The NOHZ code tries to schedule a workqueue with interrupts disabled. Since this does not work -RT I am switching it to swork instead. @@ -56,5 +59,5 @@ index 9019c9caf146..3fab1c50bf1b 100644 void __user *buffer, size_t *lenp, loff_t *ppos) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0098-hrtimer-consolidate-hrtimer_init-hrtimer_init_sleepe.patch b/debian/patches-rt/0098-hrtimer-consolidate-hrtimer_init-hrtimer_init_sleepe.patch index fcccb521f..c4d5835c8 100644 --- a/debian/patches-rt/0098-hrtimer-consolidate-hrtimer_init-hrtimer_init_sleepe.patch +++ b/debian/patches-rt/0098-hrtimer-consolidate-hrtimer_init-hrtimer_init_sleepe.patch @@ -1,9 +1,12 @@ -From 9a9c6744f1401c493421737e4069babc9029adb4 Mon Sep 17 00:00:00 2001 +From 9edffccea750b6ec0ab51d8e3937a13fde2cd4da Mon Sep 17 00:00:00 2001 +Message-Id: <9edffccea750b6ec0ab51d8e3937a13fde2cd4da.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 11:25:41 +0200 -Subject: [PATCH 098/325] hrtimer: consolidate hrtimer_init() + +Subject: [PATCH 098/327] hrtimer: consolidate hrtimer_init() + hrtimer_init_sleeper() calls -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz hrtimer_init_sleeper() calls require a prior initialisation of the hrtimer object with hrtimer_init(). Lets make the initialisation of @@ -286,5 +289,5 @@ index 092fa3d75b32..9d472d626aaa 100644 set_current_state(TASK_INTERRUPTIBLE); hrtimer_start_expires(&t.timer, HRTIMER_MODE_ABS); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch b/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch index 50e8920ce..cf84afa87 100644 --- a/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch +++ b/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch @@ -1,8 +1,11 @@ -From 4010d1e594f451d4c3c992238406e1eba5c749e4 Mon Sep 17 00:00:00 2001 +From 06cbb8d5488d87cdbe5aee4ae8a6da12174d6855 Mon Sep 17 00:00:00 2001 +Message-Id: <06cbb8d5488d87cdbe5aee4ae8a6da12174d6855.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 -Subject: [PATCH 099/325] hrtimers: Prepare full preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 099/327] hrtimers: Prepare full preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Make cancellation of a running callback in softirq context safe against preemption. @@ -286,5 +289,5 @@ index 5a01c4fdbfef..a5ec421e3437 100644 } list_del(&timer->list); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0100-hrtimer-by-timers-by-default-into-the-softirq-contex.patch b/debian/patches-rt/0100-hrtimer-by-timers-by-default-into-the-softirq-contex.patch index 202deea82..8556b22eb 100644 --- a/debian/patches-rt/0100-hrtimer-by-timers-by-default-into-the-softirq-contex.patch +++ b/debian/patches-rt/0100-hrtimer-by-timers-by-default-into-the-softirq-contex.patch @@ -1,9 +1,12 @@ -From b09a6ad039102ca18a66df006771be4c9a4679c7 Mon Sep 17 00:00:00 2001 +From 12f39aa1a76582c4859f698a9da3718435915530 Mon Sep 17 00:00:00 2001 +Message-Id: <12f39aa1a76582c4859f698a9da3718435915530.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 3 Jul 2009 08:44:31 -0500 -Subject: [PATCH 100/325] hrtimer: by timers by default into the softirq +Subject: [PATCH 100/327] hrtimer: by timers by default into the softirq context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz We can't have hrtimers callbacks running in hardirq context on RT. Therefore the timers are deferred to the softirq context by default. @@ -66,7 +69,7 @@ index 8714f1a37d84..082147c07831 100644 /* diff --git a/kernel/events/core.c b/kernel/events/core.c -index 8c70ee23fbe9..9804b1a8b0fa 100644 +index 21e3c65abc76..8cf84d6b1dfb 100644 --- a/kernel/events/core.c +++ b/kernel/events/core.c @@ -1102,7 +1102,7 @@ static void __perf_mux_hrtimer_init(struct perf_cpu_context *cpuctx, int cpu) @@ -78,7 +81,7 @@ index 8c70ee23fbe9..9804b1a8b0fa 100644 timer->function = perf_mux_hrtimer_handler; } -@@ -9269,7 +9269,7 @@ static void perf_swevent_init_hrtimer(struct perf_event *event) +@@ -9279,7 +9279,7 @@ static void perf_swevent_init_hrtimer(struct perf_event *event) if (!is_sampling_event(event)) return; @@ -233,5 +236,5 @@ index 6d60701dc636..328620fe85f6 100644 hrtimer_start(hrtimer, ns_to_ktime(sample_period), HRTIMER_MODE_REL_PINNED); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0101-sched-fair-Make-the-hrtimers-non-hard-again.patch b/debian/patches-rt/0101-sched-fair-Make-the-hrtimers-non-hard-again.patch index a4a6e83f6..37cd3a2e6 100644 --- a/debian/patches-rt/0101-sched-fair-Make-the-hrtimers-non-hard-again.patch +++ b/debian/patches-rt/0101-sched-fair-Make-the-hrtimers-non-hard-again.patch @@ -1,8 +1,11 @@ -From 0cf31ad4768bed54a110b2c9bf62827799d41e8a Mon Sep 17 00:00:00 2001 +From b6d871ce2f3bf0aa834270504ea41ce04ffa4568 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 8 Jan 2019 12:31:06 +0100 -Subject: [PATCH 101/325] sched/fair: Make the hrtimers non-hard again -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 101/327] sched/fair: Make the hrtimers non-hard again +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Since commit "sched/fair: Robustify CFS-bandwidth timer locking" both hrtimer can run in softirq context because now interrupts are disabled @@ -30,5 +33,5 @@ index f35eb8130921..fe58e95484cf 100644 cfs_b->distribute_running = 0; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0102-hrtimer-Move-schedule_work-call-to-helper-thread.patch b/debian/patches-rt/0102-hrtimer-Move-schedule_work-call-to-helper-thread.patch index 5cc8d6317..6a742b0d6 100644 --- a/debian/patches-rt/0102-hrtimer-Move-schedule_work-call-to-helper-thread.patch +++ b/debian/patches-rt/0102-hrtimer-Move-schedule_work-call-to-helper-thread.patch @@ -1,8 +1,11 @@ -From 41922c56a8fa6df2534420fe522232d8c448aae2 Mon Sep 17 00:00:00 2001 +From 9077421b81d7d8416255378c63f3af858ccc6a48 Mon Sep 17 00:00:00 2001 +Message-Id: <9077421b81d7d8416255378c63f3af858ccc6a48.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Yang Shi Date: Mon, 16 Sep 2013 14:09:19 -0700 -Subject: [PATCH 102/325] hrtimer: Move schedule_work call to helper thread -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 102/327] hrtimer: Move schedule_work call to helper thread +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz When run ltp leapsec_timer test, the following call trace is caught: @@ -94,5 +97,5 @@ index 1fd5ec39e7f4..9f3412acdb16 100644 #else -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0103-hrtimer-move-state-change-before-hrtimer_cancel-in-d.patch b/debian/patches-rt/0103-hrtimer-move-state-change-before-hrtimer_cancel-in-d.patch index 75e5d5433..3f9b7cbc6 100644 --- a/debian/patches-rt/0103-hrtimer-move-state-change-before-hrtimer_cancel-in-d.patch +++ b/debian/patches-rt/0103-hrtimer-move-state-change-before-hrtimer_cancel-in-d.patch @@ -1,9 +1,12 @@ -From 6b0b0a70d8daac88d3492deb4dfa74c7e232fa8e Mon Sep 17 00:00:00 2001 +From 2b97b3a792f4099621f1986b820650f0a775aff2 Mon Sep 17 00:00:00 2001 +Message-Id: <2b97b3a792f4099621f1986b820650f0a775aff2.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 10:15:13 +0100 -Subject: [PATCH 103/325] hrtimer: move state change before hrtimer_cancel in +Subject: [PATCH 103/327] hrtimer: move state change before hrtimer_cancel in do_nanosleep() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz There is a small window between setting t->task to NULL and waking the task up (which would set TASK_RUNNING). So the timer would fire, run and @@ -47,5 +50,5 @@ index 9f3412acdb16..b800efb64238 100644 if (!t->task) return 0; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0104-posix-timers-Thread-posix-cpu-timers-on-rt.patch b/debian/patches-rt/0104-posix-timers-Thread-posix-cpu-timers-on-rt.patch index 66d027ffd..ca3d5d789 100644 --- a/debian/patches-rt/0104-posix-timers-Thread-posix-cpu-timers-on-rt.patch +++ b/debian/patches-rt/0104-posix-timers-Thread-posix-cpu-timers-on-rt.patch @@ -1,8 +1,11 @@ -From 60c7b398c11f739be117b6e30a9b09f615e406a0 Mon Sep 17 00:00:00 2001 +From 0cb59b04e24b45a80cd395bcdb7816a79005c66a Mon Sep 17 00:00:00 2001 +Message-Id: <0cb59b04e24b45a80cd395bcdb7816a79005c66a.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: John Stultz Date: Fri, 3 Jul 2009 08:29:58 -0500 -Subject: [PATCH 104/325] posix-timers: Thread posix-cpu-timers on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 104/327] posix-timers: Thread posix-cpu-timers on -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz posix-cpu-timer code takes non -rt safe locks in hard irq context. Move it to a thread. @@ -19,7 +22,7 @@ Signed-off-by: Thomas Gleixner 4 files changed, 164 insertions(+), 3 deletions(-) diff --git a/include/linux/sched.h b/include/linux/sched.h -index e4af260f81c5..a90b6be626cd 100644 +index 3b0a95e10939..b6fbc5aa3d5d 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -832,6 +832,9 @@ struct task_struct { @@ -265,5 +268,5 @@ index d62d7ae5201c..8d95e8de98b2 100644 * Set one of the process-wide special case CPU timers or RLIMIT_CPU. * The tsk->sighand->siglock must be held by the caller. -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0105-sched-Move-task_struct-cleanup-to-RCU.patch b/debian/patches-rt/0105-sched-Move-task_struct-cleanup-to-RCU.patch index 7ae7224a1..606b249be 100644 --- a/debian/patches-rt/0105-sched-Move-task_struct-cleanup-to-RCU.patch +++ b/debian/patches-rt/0105-sched-Move-task_struct-cleanup-to-RCU.patch @@ -1,8 +1,11 @@ -From 97846d957dd8a3d2b13c5095b2487c4977f0cb93 Mon Sep 17 00:00:00 2001 +From ac273456b5dd89be9b9b094687bc91fbec5ab7e4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 May 2011 16:59:16 +0200 -Subject: [PATCH 105/325] sched: Move task_struct cleanup to RCU -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 105/327] sched: Move task_struct cleanup to RCU +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz __put_task_struct() does quite some expensive work. We don't want to burden random tasks with that. @@ -15,7 +18,7 @@ Signed-off-by: Thomas Gleixner 3 files changed, 27 insertions(+), 2 deletions(-) diff --git a/include/linux/sched.h b/include/linux/sched.h -index a90b6be626cd..0b8850b6093b 100644 +index b6fbc5aa3d5d..9a0e01e48602 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -1194,6 +1194,9 @@ struct task_struct { @@ -92,5 +95,5 @@ index ccfcd44a370f..309f4a20d4ac 100644 void __init __weak arch_task_cache_init(void) { } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0106-sched-Limit-the-number-of-task-migrations-per-batch.patch b/debian/patches-rt/0106-sched-Limit-the-number-of-task-migrations-per-batch.patch index 1905396ff..3293f0d35 100644 --- a/debian/patches-rt/0106-sched-Limit-the-number-of-task-migrations-per-batch.patch +++ b/debian/patches-rt/0106-sched-Limit-the-number-of-task-migrations-per-batch.patch @@ -1,8 +1,11 @@ -From f7d8e7c485e3b32f915bfdf26698b947abaeaf10 Mon Sep 17 00:00:00 2001 +From 4bd7e2a1c07e3ae8d49fc8b5f45a61dd630a9b45 Mon Sep 17 00:00:00 2001 +Message-Id: <4bd7e2a1c07e3ae8d49fc8b5f45a61dd630a9b45.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:12:51 +0200 -Subject: [PATCH 106/325] sched: Limit the number of task migrations per batch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 106/327] sched: Limit the number of task migrations per batch +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Put an upper limit on the number of tasks which are migrated per batch to avoid large latencies. @@ -29,5 +32,5 @@ index 2f6b4365d070..5c23d1272429 100644 /* * period over which we measure -rt task CPU usage in us. -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0107-sched-Move-mmdrop-to-RCU-on-RT.patch b/debian/patches-rt/0107-sched-Move-mmdrop-to-RCU-on-RT.patch index f5399356d..a39390bc3 100644 --- a/debian/patches-rt/0107-sched-Move-mmdrop-to-RCU-on-RT.patch +++ b/debian/patches-rt/0107-sched-Move-mmdrop-to-RCU-on-RT.patch @@ -1,8 +1,11 @@ -From 9d712d36877d0b56524f63fc76ae36ecfc75ec1e Mon Sep 17 00:00:00 2001 +From e10e3f01658879df9a140ebc1fa6a833306d205b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:20:33 +0200 -Subject: [PATCH 107/325] sched: Move mmdrop to RCU on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 107/327] sched: Move mmdrop to RCU on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Takes sleeping locks and calls into the memory allocator, so nothing we want to do in task switch and oder atomic contexts. @@ -136,5 +139,5 @@ index 5c23d1272429..cb89c90513dd 100644 } #endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0108-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch b/debian/patches-rt/0108-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch index 3f4688ca9..a0e12bf72 100644 --- a/debian/patches-rt/0108-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch +++ b/debian/patches-rt/0108-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch @@ -1,9 +1,12 @@ -From 93d5750f6bd9a39e9e4de3773c7ab669b446e214 Mon Sep 17 00:00:00 2001 +From b130de87f13cecffd99e3bef73cf43e41bf3735f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 21 Nov 2016 19:31:08 +0100 -Subject: [PATCH 108/325] kernel/sched: move stack + kprobe clean up to +Subject: [PATCH 108/327] kernel/sched: move stack + kprobe clean up to __put_task_struct() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz There is no need to free the stack before the task struct (except for reasons mentioned in commit 68f24b08ee89 ("sched/core: Free the stack early if @@ -66,5 +69,5 @@ index cb89c90513dd..79e0d052e848 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0109-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch b/debian/patches-rt/0109-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch index 79c9d7c19..2d87dfa9f 100644 --- a/debian/patches-rt/0109-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch +++ b/debian/patches-rt/0109-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch @@ -1,9 +1,12 @@ -From 59729bf436bda277795b157fd494206ee00a0918 Mon Sep 17 00:00:00 2001 +From 06dbc7b47e3c61b393a1a5d4df735ef17dd71782 Mon Sep 17 00:00:00 2001 +Message-Id: <06dbc7b47e3c61b393a1a5d4df735ef17dd71782.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 25 Jun 2011 09:21:04 +0200 -Subject: [PATCH 109/325] sched: Add saved_state for tasks blocked on sleeping +Subject: [PATCH 109/327] sched: Add saved_state for tasks blocked on sleeping locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Spinlocks are state preserving in !RT. RT changes the state when a task gets blocked on a lock. So we need to remember the state before @@ -19,7 +22,7 @@ Signed-off-by: Thomas Gleixner 3 files changed, 36 insertions(+), 1 deletion(-) diff --git a/include/linux/sched.h b/include/linux/sched.h -index 0b8850b6093b..f180bfadff33 100644 +index 9a0e01e48602..42846a65df9a 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -600,6 +600,8 @@ struct task_struct { @@ -92,10 +95,10 @@ index 79e0d052e848..d1c564acff76 100644 { return try_to_wake_up(p, state, 0); diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h -index 94bec97bd5e2..c79e32488940 100644 +index 5f0eb4565957..96823c632599 100644 --- a/kernel/sched/sched.h +++ b/kernel/sched/sched.h -@@ -1439,6 +1439,7 @@ static inline int task_on_rq_migrating(struct task_struct *p) +@@ -1445,6 +1445,7 @@ static inline int task_on_rq_migrating(struct task_struct *p) #define WF_SYNC 0x01 /* Waker goes to sleep after wakeup */ #define WF_FORK 0x02 /* Child wakeup after fork */ #define WF_MIGRATED 0x4 /* Internal use, task got migrated */ @@ -104,5 +107,5 @@ index 94bec97bd5e2..c79e32488940 100644 /* * To aid in avoiding the subversion of "niceness" due to uneven distribution -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0110-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch b/debian/patches-rt/0110-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch index 1a078d910..29e95dd2a 100644 --- a/debian/patches-rt/0110-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch +++ b/debian/patches-rt/0110-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch @@ -1,9 +1,12 @@ -From ae13a78b6abe7d64003fa44196eeda8814ca4d48 Mon Sep 17 00:00:00 2001 +From 43f68c55c3b13d255be2f0c794673f8e9a7adca0 Mon Sep 17 00:00:00 2001 +Message-Id: <43f68c55c3b13d255be2f0c794673f8e9a7adca0.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 7 Jun 2011 09:19:06 +0200 -Subject: [PATCH 110/325] sched: Do not account rcu_preempt_depth on RT in +Subject: [PATCH 110/327] sched: Do not account rcu_preempt_depth on RT in might_sleep() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz RT changes the rcu_preempt_depth semantics, so we cannot check for it in might_sleep(). @@ -53,5 +56,5 @@ index d1c564acff76..59d43c084023 100644 return (nested == preempt_offset); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0111-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch b/debian/patches-rt/0111-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch index 64156215f..b24d4efb7 100644 --- a/debian/patches-rt/0111-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch +++ b/debian/patches-rt/0111-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch @@ -1,8 +1,11 @@ -From 9774ed0ae21bac1e01f919117ee09f5490d7c7c3 Mon Sep 17 00:00:00 2001 +From c3d5e26fee97bdf9e8f7c6667e4e1a58585b41f5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 22:51:33 +0200 -Subject: [PATCH 111/325] sched: Use the proper LOCK_OFFSET for cond_resched() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 111/327] sched: Use the proper LOCK_OFFSET for cond_resched() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz RT does not increment preempt count when a 'sleeping' spinlock is locked. Update PREEMPT_LOCK_OFFSET for that case. @@ -29,5 +32,5 @@ index f7a17fcc3fec..b7fe717eb1f4 100644 /* * The preempt_count offset needed for things like: -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0112-sched-Disable-TTWU_QUEUE-on-RT.patch b/debian/patches-rt/0112-sched-Disable-TTWU_QUEUE-on-RT.patch index 5939decb4..f78a4f54f 100644 --- a/debian/patches-rt/0112-sched-Disable-TTWU_QUEUE-on-RT.patch +++ b/debian/patches-rt/0112-sched-Disable-TTWU_QUEUE-on-RT.patch @@ -1,8 +1,11 @@ -From d944dd60ea381b06696f77f6900bfad524f0c5b8 Mon Sep 17 00:00:00 2001 +From 736af57f8829849f1b10042f7ed84952e6d13618 Mon Sep 17 00:00:00 2001 +Message-Id: <736af57f8829849f1b10042f7ed84952e6d13618.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Sep 2011 16:42:35 +0200 -Subject: [PATCH 112/325] sched: Disable TTWU_QUEUE on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 112/327] sched: Disable TTWU_QUEUE on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The queued remote wakeup mechanism can introduce rather large latencies if the number of migrated tasks is high. Disable it for RT. @@ -34,5 +37,5 @@ index 85ae8488039c..68de18405857 100644 /* * When doing wakeups, attempt to limit superfluous scans of the LLC domain. -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0113-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch b/debian/patches-rt/0113-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch index 0c9070f42..5f721504c 100644 --- a/debian/patches-rt/0113-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch +++ b/debian/patches-rt/0113-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch @@ -1,9 +1,12 @@ -From 7617fdb778960b1313b4e27bb3429d28c5d42957 Mon Sep 17 00:00:00 2001 +From 84ad34b48591ce857eeef88bf4f16997e18bf143 Mon Sep 17 00:00:00 2001 +Message-Id: <84ad34b48591ce857eeef88bf4f16997e18bf143.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Steven Rostedt Date: Mon, 18 Mar 2013 15:12:49 -0400 -Subject: [PATCH 113/325] sched/workqueue: Only wake up idle workers if not +Subject: [PATCH 113/327] sched/workqueue: Only wake up idle workers if not blocked on sleeping spin lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In -rt, most spin_locks() turn into mutexes. One of these spin_lock conversions is performed on the workqueue gcwq->lock. When the idle @@ -41,5 +44,5 @@ index 59d43c084023..e792543de8eb 100644 to_wakeup = wq_worker_sleeping(prev); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0114-rt-Increase-decrease-the-nr-of-migratory-tasks-when-.patch b/debian/patches-rt/0114-rt-Increase-decrease-the-nr-of-migratory-tasks-when-.patch index d6f4a158d..3ff8af063 100644 --- a/debian/patches-rt/0114-rt-Increase-decrease-the-nr-of-migratory-tasks-when-.patch +++ b/debian/patches-rt/0114-rt-Increase-decrease-the-nr-of-migratory-tasks-when-.patch @@ -1,9 +1,12 @@ -From 418bcb5747f1358c0afc713ba2294fe33b5878de Mon Sep 17 00:00:00 2001 +From 4565f5f72adec71306213058dafdf1cef42ac060 Mon Sep 17 00:00:00 2001 +Message-Id: <4565f5f72adec71306213058dafdf1cef42ac060.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Daniel Bristot de Oliveira Date: Mon, 26 Jun 2017 17:07:15 +0200 -Subject: [PATCH 114/325] rt: Increase/decrease the nr of migratory tasks when +Subject: [PATCH 114/327] rt: Increase/decrease the nr of migratory tasks when enabling/disabling migration -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz There is a problem in the migrate_disable()/enable() implementation regarding the number of migratory tasks in the rt/dl RQs. The problem @@ -158,5 +161,5 @@ index e792543de8eb..57617777c4ba 100644 if (p->migrate_disable_update) { struct rq *rq; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch b/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch index aad469312..c7f812834 100644 --- a/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch +++ b/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch @@ -1,8 +1,11 @@ -From 97c38013b1a149d864cda397094e7038085f4e80 Mon Sep 17 00:00:00 2001 +From 09bf70d9e6db271e5f93dbfbc7f0d8479cccbce3 Mon Sep 17 00:00:00 2001 +Message-Id: <09bf70d9e6db271e5f93dbfbc7f0d8479cccbce3.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 15 Jun 2011 12:36:06 +0200 -Subject: [PATCH 115/325] hotplug: Lightweight get online cpus -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 115/327] hotplug: Lightweight get online cpus +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz get_online_cpus() is a heavy weight function which involves a global mutex. migrate_disable() wants a simpler construct which prevents only @@ -43,7 +46,7 @@ index aab4273810e3..e67645924404 100644 /* Wrappers which go away once all code is converted */ diff --git a/kernel/cpu.c b/kernel/cpu.c -index 2d850eaaf82e..328d7bf67d2f 100644 +index 6d6c106a495c..dc5d1e940e25 100644 --- a/kernel/cpu.c +++ b/kernel/cpu.c @@ -281,6 +281,21 @@ static int cpu_hotplug_disabled; @@ -97,5 +100,5 @@ index 57617777c4ba..42b42ebf52bc 100644 } EXPORT_SYMBOL(migrate_enable); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0116-trace-Add-migrate-disabled-counter-to-tracing-output.patch b/debian/patches-rt/0116-trace-Add-migrate-disabled-counter-to-tracing-output.patch index d40f90557..46e36b9b4 100644 --- a/debian/patches-rt/0116-trace-Add-migrate-disabled-counter-to-tracing-output.patch +++ b/debian/patches-rt/0116-trace-Add-migrate-disabled-counter-to-tracing-output.patch @@ -1,8 +1,11 @@ -From 9ea64a4be6dfb32d2a562b28857bef0ae9fa163b Mon Sep 17 00:00:00 2001 +From 7b1ff832adbdc5ee8eb2f772a90975c9f56bbf14 Mon Sep 17 00:00:00 2001 +Message-Id: <7b1ff832adbdc5ee8eb2f772a90975c9f56bbf14.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:56:42 +0200 -Subject: [PATCH 116/325] trace: Add migrate-disabled counter to tracing output -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 116/327] trace: Add migrate-disabled counter to tracing output +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Signed-off-by: Thomas Gleixner --- @@ -82,5 +85,5 @@ index 6e6cc64faa38..46c96744f09d 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch b/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch index a07c0e974..10840d578 100644 --- a/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch +++ b/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch @@ -1,8 +1,11 @@ -From 8ed2b42d1e41402d585e7907ef754461cda3ff25 Mon Sep 17 00:00:00 2001 +From 8571380c6cad699003ce1b1322bb673e5ee32525 Mon Sep 17 00:00:00 2001 +Message-Id: <8571380c6cad699003ce1b1322bb673e5ee32525.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 18:51:23 +0200 -Subject: [PATCH 117/325] lockdep: Make it RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 117/327] lockdep: Make it RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz teach lockdep that we don't really do softirqs on -RT. @@ -54,10 +57,10 @@ index 21619c92c377..b20eeb25e9fa 100644 defined(CONFIG_PREEMPT_TRACER) extern void stop_critical_timings(void); diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c -index 1e272f6a01e7..1938b4bfb098 100644 +index 8a1758b094b7..376b1ef4396a 100644 --- a/kernel/locking/lockdep.c +++ b/kernel/locking/lockdep.c -@@ -3826,6 +3826,7 @@ static void check_flags(unsigned long flags) +@@ -3830,6 +3830,7 @@ static void check_flags(unsigned long flags) } } @@ -65,7 +68,7 @@ index 1e272f6a01e7..1938b4bfb098 100644 /* * We dont accurately track softirq state in e.g. * hardirq contexts (such as on 4KSTACKS), so only -@@ -3840,6 +3841,7 @@ static void check_flags(unsigned long flags) +@@ -3844,6 +3845,7 @@ static void check_flags(unsigned long flags) DEBUG_LOCKS_WARN_ON(!current->softirqs_enabled); } } @@ -74,5 +77,5 @@ index 1e272f6a01e7..1938b4bfb098 100644 if (!debug_locks) print_irqtrace_events(current); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0118-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch b/debian/patches-rt/0118-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch index dfe5b6955..613d89c0b 100644 --- a/debian/patches-rt/0118-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch +++ b/debian/patches-rt/0118-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch @@ -1,9 +1,12 @@ -From af236a3575387c398e7192cc9f09098679b05e77 Mon Sep 17 00:00:00 2001 +From 0f8c73a41cc21e19f3cd6bf007535734425b6e3e Mon Sep 17 00:00:00 2001 +Message-Id: <0f8c73a41cc21e19f3cd6bf007535734425b6e3e.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Tue, 29 Nov 2011 20:18:22 -0500 -Subject: [PATCH 118/325] tasklet: Prevent tasklets from going into infinite +Subject: [PATCH 118/327] tasklet: Prevent tasklets from going into infinite spin in RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz When CONFIG_PREEMPT_RT_FULL is enabled, tasklets run as threads, and spinlocks turn are mutexes. But this can cause issues with @@ -299,5 +302,5 @@ index 6f584861d329..1d3a482246cc 100644 { return local_softirq_pending(); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0119-softirq-Check-preemption-after-reenabling-interrupts.patch b/debian/patches-rt/0119-softirq-Check-preemption-after-reenabling-interrupts.patch index 2de572682..da89b32a2 100644 --- a/debian/patches-rt/0119-softirq-Check-preemption-after-reenabling-interrupts.patch +++ b/debian/patches-rt/0119-softirq-Check-preemption-after-reenabling-interrupts.patch @@ -1,8 +1,11 @@ -From 3e6511a5a97439410e2888198a743dfe4162bcbc Mon Sep 17 00:00:00 2001 +From f0075d43b45fbc244844c63f364e7b2461e72a0a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 13 Nov 2011 17:17:09 +0100 -Subject: [PATCH 119/325] softirq: Check preemption after reenabling interrupts -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 119/327] softirq: Check preemption after reenabling interrupts +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz raise_softirq_irqoff() disables interrupts and wakes the softirq daemon, but after reenabling interrupts there is no preemption check, @@ -117,7 +120,7 @@ index 86a709954f5a..9c069ef83d6d 100644 return 0; } diff --git a/net/core/dev.c b/net/core/dev.c -index 2f4d35101f4d..626743ea0d53 100644 +index 426635e188fc..e1b0618e231e 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -2727,6 +2727,7 @@ static void __netif_reschedule(struct Qdisc *q) @@ -136,7 +139,7 @@ index 2f4d35101f4d..626743ea0d53 100644 } EXPORT_SYMBOL(__dev_kfree_skb_irq); -@@ -4263,6 +4265,7 @@ static int enqueue_to_backlog(struct sk_buff *skb, int cpu, +@@ -4264,6 +4266,7 @@ static int enqueue_to_backlog(struct sk_buff *skb, int cpu, rps_unlock(sd); local_irq_restore(flags); @@ -144,7 +147,7 @@ index 2f4d35101f4d..626743ea0d53 100644 atomic_long_inc(&skb->dev->rx_dropped); kfree_skb(skb); -@@ -5803,12 +5806,14 @@ static void net_rps_action_and_irq_enable(struct softnet_data *sd) +@@ -5804,12 +5807,14 @@ static void net_rps_action_and_irq_enable(struct softnet_data *sd) sd->rps_ipi_list = NULL; local_irq_enable(); @@ -159,7 +162,7 @@ index 2f4d35101f4d..626743ea0d53 100644 } static bool sd_has_rps_ipi_waiting(struct softnet_data *sd) -@@ -5886,6 +5891,7 @@ void __napi_schedule(struct napi_struct *n) +@@ -5887,6 +5892,7 @@ void __napi_schedule(struct napi_struct *n) local_irq_save(flags); ____napi_schedule(this_cpu_ptr(&softnet_data), n); local_irq_restore(flags); @@ -167,7 +170,7 @@ index 2f4d35101f4d..626743ea0d53 100644 } EXPORT_SYMBOL(__napi_schedule); -@@ -9488,6 +9494,7 @@ static int dev_cpu_dead(unsigned int oldcpu) +@@ -9489,6 +9495,7 @@ static int dev_cpu_dead(unsigned int oldcpu) raise_softirq_irqoff(NET_TX_SOFTIRQ); local_irq_enable(); @@ -176,5 +179,5 @@ index 2f4d35101f4d..626743ea0d53 100644 #ifdef CONFIG_RPS remsd = oldsd->rps_ipi_list; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0120-softirq-Disable-softirq-stacks-for-RT.patch b/debian/patches-rt/0120-softirq-Disable-softirq-stacks-for-RT.patch index 66e000f3a..faf765fda 100644 --- a/debian/patches-rt/0120-softirq-Disable-softirq-stacks-for-RT.patch +++ b/debian/patches-rt/0120-softirq-Disable-softirq-stacks-for-RT.patch @@ -1,8 +1,11 @@ -From 2ed3d0fe9e8b5fea94a4a98b98490353bae4a22b Mon Sep 17 00:00:00 2001 +From 9e86dd147e8ddd3b1ad01b287979c781e4583224 Mon Sep 17 00:00:00 2001 +Message-Id: <9e86dd147e8ddd3b1ad01b287979c781e4583224.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 13:59:17 +0200 -Subject: [PATCH 120/325] softirq: Disable softirq stacks for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 120/327] softirq: Disable softirq stacks for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Disable extra stacks for softirqs. We want to preempt softirqs and having them on special IRQ-stack does not make this easier. @@ -173,5 +176,5 @@ index 35fa335c475b..eec4bec454b5 100644 #else static inline void do_softirq_own_stack(void) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0121-softirq-Split-softirq-locks.patch b/debian/patches-rt/0121-softirq-Split-softirq-locks.patch index 7f241fb18..bf4a96dce 100644 --- a/debian/patches-rt/0121-softirq-Split-softirq-locks.patch +++ b/debian/patches-rt/0121-softirq-Split-softirq-locks.patch @@ -1,8 +1,11 @@ -From 7f588c91c584d17bfab949544912fab8942a5eaf Mon Sep 17 00:00:00 2001 +From b235e2305fdffaf44c89c88e619e3454aa379a5f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 4 Oct 2012 14:20:47 +0100 -Subject: [PATCH 121/325] softirq: Split softirq locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 121/327] softirq: Split softirq locks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The 3.x RT series removed the split softirq implementation in favour of pushing softirq processing into the context of the thread which @@ -178,7 +181,7 @@ index 9984f2b75b73..27c3176d88d2 100644 #define in_task() (!(preempt_count() & \ (NMI_MASK | HARDIRQ_MASK | SOFTIRQ_OFFSET))) diff --git a/include/linux/sched.h b/include/linux/sched.h -index f180bfadff33..f4ff928e6be3 100644 +index 42846a65df9a..30895ae9e82d 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -1198,6 +1198,8 @@ struct task_struct { @@ -828,5 +831,5 @@ index 012bc81879bf..2b0ddd50e879 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0122-net-core-use-local_bh_disable-in-netif_rx_ni.patch b/debian/patches-rt/0122-net-core-use-local_bh_disable-in-netif_rx_ni.patch index eed262bed..37d911ae5 100644 --- a/debian/patches-rt/0122-net-core-use-local_bh_disable-in-netif_rx_ni.patch +++ b/debian/patches-rt/0122-net-core-use-local_bh_disable-in-netif_rx_ni.patch @@ -1,8 +1,11 @@ -From 7686cfd7088430200bd52074427f75462111fe5f Mon Sep 17 00:00:00 2001 +From dddf06fedee6ba0e9cc8d0190602fb8997b02d46 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 16 Jun 2017 19:03:16 +0200 -Subject: [PATCH 122/325] net/core: use local_bh_disable() in netif_rx_ni() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 122/327] net/core: use local_bh_disable() in netif_rx_ni() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In 2004 netif_rx_ni() gained a preempt_disable() section around netif_rx() and its do_softirq() + testing for it. The do_softirq() part @@ -19,10 +22,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/net/core/dev.c b/net/core/dev.c -index 626743ea0d53..655dbfac09fd 100644 +index e1b0618e231e..0285ea11a788 100644 --- a/net/core/dev.c +++ b/net/core/dev.c -@@ -4531,11 +4531,9 @@ int netif_rx_ni(struct sk_buff *skb) +@@ -4532,11 +4532,9 @@ int netif_rx_ni(struct sk_buff *skb) trace_netif_rx_ni_entry(skb); @@ -37,5 +40,5 @@ index 626743ea0d53..655dbfac09fd 100644 return err; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0123-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch b/debian/patches-rt/0123-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch index 301708fdf..c4eb2cdd9 100644 --- a/debian/patches-rt/0123-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch +++ b/debian/patches-rt/0123-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch @@ -1,9 +1,12 @@ -From 563f92a709b074d89146410c177c5e70db3cd3fa Mon Sep 17 00:00:00 2001 +From 674a3349419deac69b7d910ea8b7bc0d1fe74345 Mon Sep 17 00:00:00 2001 +Message-Id: <674a3349419deac69b7d910ea8b7bc0d1fe74345.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 Jan 2012 13:01:27 +0100 -Subject: [PATCH 123/325] genirq: Allow disabling of softirq processing in irq +Subject: [PATCH 123/327] genirq: Allow disabling of softirq processing in irq thread context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The processing of softirqs in irq thread context is a performance gain for the non-rt workloads of a system, but it's counterproductive for @@ -157,5 +160,5 @@ index fd89f8ab85ac..3e9333d148ad 100644 { return current->flags & PF_IN_SOFTIRQ; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0124-softirq-split-timer-softirqs-out-of-ksoftirqd.patch b/debian/patches-rt/0124-softirq-split-timer-softirqs-out-of-ksoftirqd.patch index ad73ed509..1bb7fee7c 100644 --- a/debian/patches-rt/0124-softirq-split-timer-softirqs-out-of-ksoftirqd.patch +++ b/debian/patches-rt/0124-softirq-split-timer-softirqs-out-of-ksoftirqd.patch @@ -1,8 +1,11 @@ -From 5b1827a76c3fd349c3e0f8fcf77c1b054b34aedc Mon Sep 17 00:00:00 2001 +From b0e0ebc73a36ee8775266c92bcfbd7fe099ccac6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 16:34:17 +0100 -Subject: [PATCH 124/325] softirq: split timer softirqs out of ksoftirqd -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 124/327] softirq: split timer softirqs out of ksoftirqd +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The softirqd runs in -RT with SCHED_FIFO (prio 1) and deals mostly with timer wakeup which can not happen in hardirq context. The prio has been @@ -211,5 +214,5 @@ index 3e9333d148ad..fe4e59c80a08 100644 } early_initcall(spawn_ksoftirqd); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0125-softirq-Avoid-local_softirq_pending-messages-if-ksof.patch b/debian/patches-rt/0125-softirq-Avoid-local_softirq_pending-messages-if-ksof.patch index bb59a6bb3..de24cd2d0 100644 --- a/debian/patches-rt/0125-softirq-Avoid-local_softirq_pending-messages-if-ksof.patch +++ b/debian/patches-rt/0125-softirq-Avoid-local_softirq_pending-messages-if-ksof.patch @@ -1,9 +1,12 @@ -From 4d3cb3bcde462ea3b82c902bf79c233e68f7d29a Mon Sep 17 00:00:00 2001 +From 0f2aac697da6c7a4e8c705f76fd9a745c7b8b5a9 Mon Sep 17 00:00:00 2001 +Message-Id: <0f2aac697da6c7a4e8c705f76fd9a745c7b8b5a9.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 13:19:59 +0100 -Subject: [PATCH 125/325] softirq: Avoid "local_softirq_pending" messages if +Subject: [PATCH 125/327] softirq: Avoid "local_softirq_pending" messages if ksoftirqd is blocked -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz If the ksoftirqd thread has a softirq pending and is blocked on the `local_softirq_locks' lock then softirq_check_pending_idle() won't @@ -108,5 +111,5 @@ index fe4e59c80a08..1920985eeb09 100644 if (warnpending) { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0126-softirq-Avoid-local_softirq_pending-messages-if-task.patch b/debian/patches-rt/0126-softirq-Avoid-local_softirq_pending-messages-if-task.patch index 7f707677d..adacb6fa8 100644 --- a/debian/patches-rt/0126-softirq-Avoid-local_softirq_pending-messages-if-task.patch +++ b/debian/patches-rt/0126-softirq-Avoid-local_softirq_pending-messages-if-task.patch @@ -1,9 +1,12 @@ -From 7bf55b1409bf1fdbfd5c017c1fd64129b2f24210 Mon Sep 17 00:00:00 2001 +From f07757f81d35f9cbaee287b5eabb7bbe9e0298d8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:49:29 +0100 -Subject: [PATCH 126/325] softirq: Avoid "local_softirq_pending" messages if +Subject: [PATCH 126/327] softirq: Avoid "local_softirq_pending" messages if task is in cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz If the softirq thread enters cpu_chill() then ->state is UNINTERRUPTIBLE and has no ->pi_blocked_on set and so its mask is not taken into account. @@ -37,5 +40,5 @@ index 1920985eeb09..27a4bb2303d0 100644 *pending &= ~(tsk->softirqs_raised); ret = true; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0127-rtmutex-trylock-is-okay-on-RT.patch b/debian/patches-rt/0127-rtmutex-trylock-is-okay-on-RT.patch index 71dda12b5..5f78cd2e9 100644 --- a/debian/patches-rt/0127-rtmutex-trylock-is-okay-on-RT.patch +++ b/debian/patches-rt/0127-rtmutex-trylock-is-okay-on-RT.patch @@ -1,8 +1,11 @@ -From e3c2fa3a8755063343e3ce1072db61a9044dda46 Mon Sep 17 00:00:00 2001 +From 005706af111e1fc4b9b316e4a6736d0fdb5ea0d9 Mon Sep 17 00:00:00 2001 +Message-Id: <005706af111e1fc4b9b316e4a6736d0fdb5ea0d9.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 2 Dec 2015 11:34:07 +0100 -Subject: [PATCH 127/325] rtmutex: trylock is okay on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 127/327] rtmutex: trylock is okay on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz non-RT kernel could deadlock on rt_mutex_trylock() in softirq context. On -RT we don't run softirqs in IRQ context but in thread context so it is @@ -30,5 +33,5 @@ index 9562aaa2afdc..72abe7c121fa 100644 ret = rt_mutex_fasttrylock(lock, rt_mutex_slowtrylock); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0128-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch b/debian/patches-rt/0128-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch index 53ec82e7f..d508fa8cc 100644 --- a/debian/patches-rt/0128-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch +++ b/debian/patches-rt/0128-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch @@ -1,8 +1,11 @@ -From a519c1de9cb8fa6407865a391460b71b3d9f7ba5 Mon Sep 17 00:00:00 2001 +From e746beb20a46175c355c737e8181f89ecf105400 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 15 Sep 2016 10:51:27 +0200 -Subject: [PATCH 128/325] fs/nfs: turn rmdir_sem into a semaphore -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 128/327] fs/nfs: turn rmdir_sem into a semaphore +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The RW semaphore had a reader side which used the _non_owner version because it most likely took the reader lock in one thread and released it @@ -147,5 +150,5 @@ index a0831e9d19c9..94b6fefd90b0 100644 #if IS_ENABLED(CONFIG_NFS_V4) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0129-rtmutex-Handle-the-various-new-futex-race-conditions.patch b/debian/patches-rt/0129-rtmutex-Handle-the-various-new-futex-race-conditions.patch index 31694932b..01393cf82 100644 --- a/debian/patches-rt/0129-rtmutex-Handle-the-various-new-futex-race-conditions.patch +++ b/debian/patches-rt/0129-rtmutex-Handle-the-various-new-futex-race-conditions.patch @@ -1,8 +1,11 @@ -From 1fa5c17a8433d8aa590a042209a3f2211ec87663 Mon Sep 17 00:00:00 2001 +From a3e55790c1c9490150de3e93b4e2810d7d5eb965 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 10 Jun 2011 11:04:15 +0200 -Subject: [PATCH 129/325] rtmutex: Handle the various new futex race conditions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 129/327] rtmutex: Handle the various new futex race conditions +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz RT opens a few new interesting race conditions in the rtmutex/futex combo due to futex hash bucket lock being a 'sleeping' spinlock and @@ -251,5 +254,5 @@ index d1d62f942be2..f4b6596d224a 100644 extern void rt_mutex_init_proxy_locked(struct rt_mutex *lock, struct task_struct *proxy_owner); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0130-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch b/debian/patches-rt/0130-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch index 954fef61f..1a7339dfd 100644 --- a/debian/patches-rt/0130-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch +++ b/debian/patches-rt/0130-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch @@ -1,8 +1,11 @@ -From 4210e8e1f78fc819dfe27d2918ff33b0f5f6d0df Mon Sep 17 00:00:00 2001 +From f2ca4d9cb2113ba369f0716b2477b913dfcb3543 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 130/325] futex: Fix bug on when a requeued RT task times out -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 130/327] futex: Fix bug on when a requeued RT task times out +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Requeue with timeout causes a bug with PREEMPT_RT_FULL. @@ -117,5 +120,5 @@ index f4b6596d224a..461527f3f7af 100644 extern struct task_struct *rt_mutex_next_owner(struct rt_mutex *lock); extern void rt_mutex_init_proxy_locked(struct rt_mutex *lock, -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0131-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch b/debian/patches-rt/0131-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch index 435c535c6..d824c8187 100644 --- a/debian/patches-rt/0131-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch +++ b/debian/patches-rt/0131-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch @@ -1,9 +1,12 @@ -From ceb4c8f4c8a3887cc786895ea767fa9ad43b2959 Mon Sep 17 00:00:00 2001 +From 1d84f8d3fb288f896e08d93a418892df9e3d910c Mon Sep 17 00:00:00 2001 +Message-Id: <1d84f8d3fb288f896e08d93a418892df9e3d910c.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 1 Mar 2013 11:17:42 +0100 -Subject: [PATCH 131/325] futex: Ensure lock/unlock symetry versus pi_lock and +Subject: [PATCH 131/327] futex: Ensure lock/unlock symetry versus pi_lock and hash bucket lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In exit_pi_state_list() we have the following locking construct: @@ -46,5 +49,5 @@ index c922e994f524..cde7ff6f9a48 100644 continue; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0132-pid.h-include-atomic.h.patch b/debian/patches-rt/0132-pid.h-include-atomic.h.patch index 9aa83f776..22f6b9c8d 100644 --- a/debian/patches-rt/0132-pid.h-include-atomic.h.patch +++ b/debian/patches-rt/0132-pid.h-include-atomic.h.patch @@ -1,8 +1,11 @@ -From a3a3d3d03bfe53c007e888ee891dbd703972d1ea Mon Sep 17 00:00:00 2001 +From 48464789e57bdd127279a41db126d18101581c93 Mon Sep 17 00:00:00 2001 +Message-Id: <48464789e57bdd127279a41db126d18101581c93.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Grygorii Strashko Date: Tue, 21 Jul 2015 19:43:56 +0300 -Subject: [PATCH 132/325] pid.h: include atomic.h -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 132/327] pid.h: include atomic.h +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz This patch fixes build error: CC kernel/pid_namespace.o @@ -39,5 +42,5 @@ index 14a9a39da9c7..a9026a5da196 100644 enum pid_type { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0133-arm-include-definition-for-cpumask_t.patch b/debian/patches-rt/0133-arm-include-definition-for-cpumask_t.patch index f7beaa323..cc2cea2be 100644 --- a/debian/patches-rt/0133-arm-include-definition-for-cpumask_t.patch +++ b/debian/patches-rt/0133-arm-include-definition-for-cpumask_t.patch @@ -1,8 +1,11 @@ -From 1fc05f4412c1b09b10d06886933ba1ccd0e18f33 Mon Sep 17 00:00:00 2001 +From a47ed74947403d7e564ba5f2d6888701ff728b21 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 22 Dec 2016 17:28:33 +0100 -Subject: [PATCH 133/325] arm: include definition for cpumask_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 133/327] arm: include definition for cpumask_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz This definition gets pulled in by other files. With the (later) split of RCU and spinlock.h it won't compile anymore. @@ -27,5 +30,5 @@ index 46d41140df27..c421b5b81946 100644 struct pt_regs; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch b/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch index 51249dc65..b8efe115f 100644 --- a/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch +++ b/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch @@ -1,9 +1,12 @@ -From 1814e9a2c2092f55d4e2fa99192af5eff0c364f3 Mon Sep 17 00:00:00 2001 +From d08a6afe831e619cca789594e8b77bf5f755bd6a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Wolfgang M. Reimer" Date: Tue, 21 Jul 2015 16:20:07 +0200 -Subject: [PATCH 134/325] locking: locktorture: Do NOT include rwlock.h +Subject: [PATCH 134/327] locking: locktorture: Do NOT include rwlock.h directly -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Including rwlock.h directly will cause kernel builds to fail if CONFIG_PREEMPT_RT_FULL is defined. The correct header file @@ -18,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 deletion(-) diff --git a/kernel/locking/locktorture.c b/kernel/locking/locktorture.c -index 7d0b0ed74404..a81e6ef33a04 100644 +index 95395ef5922a..5748c1936edb 100644 --- a/kernel/locking/locktorture.c +++ b/kernel/locking/locktorture.c @@ -29,7 +29,6 @@ @@ -30,5 +33,5 @@ index 7d0b0ed74404..a81e6ef33a04 100644 #include #include -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch b/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch index 0b0a60986..916f297e6 100644 --- a/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch +++ b/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch @@ -1,8 +1,11 @@ -From 468920c7b2db6dba23677a7f6ab507a27cb16d5d Mon Sep 17 00:00:00 2001 +From b73a272cb3b9510c0f8ba239c1d111127edaf442 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 9 Jun 2011 11:43:52 +0200 -Subject: [PATCH 135/325] rtmutex: Add rtmutex_lock_killable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 135/327] rtmutex: Add rtmutex_lock_killable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Add "killable" type to rtmutex. We need this since rtmutex are used as "normal" mutexes which do use this type. @@ -56,5 +59,5 @@ index 1c3f56d3d9b6..a4b2af7718f8 100644 * rt_mutex_timed_lock - lock a rt_mutex interruptible * the timeout structure is provided -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch b/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch index fc97f0d47..5395c21a4 100644 --- a/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch +++ b/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch @@ -1,8 +1,11 @@ -From a83438da0a4366a5f9d3930dec26bd77c5f60a63 Mon Sep 17 00:00:00 2001 +From b2bcd460da9efcea6eb253a42e7b9b40d83f87fe Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 1 Apr 2017 12:50:59 +0200 -Subject: [PATCH 136/325] rtmutex: Make lock_killable work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 136/327] rtmutex: Make lock_killable work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Locking an rt mutex killable does not work because signal handling is restricted to TASK_INTERRUPTIBLE. @@ -47,5 +50,5 @@ index a4b2af7718f8..f058bb976212 100644 raw_spin_unlock_irq(&lock->wait_lock); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0137-spinlock-Split-the-lock-types-header.patch b/debian/patches-rt/0137-spinlock-Split-the-lock-types-header.patch index df15f1b28..eaf7a3006 100644 --- a/debian/patches-rt/0137-spinlock-Split-the-lock-types-header.patch +++ b/debian/patches-rt/0137-spinlock-Split-the-lock-types-header.patch @@ -1,8 +1,11 @@ -From dba0ea2e3bd9761d43099e882fe6e51aa1c77bea Mon Sep 17 00:00:00 2001 +From 052ae080585d0e500348d996348b86711e3747b4 Mon Sep 17 00:00:00 2001 +Message-Id: <052ae080585d0e500348d996348b86711e3747b4.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 19:34:01 +0200 -Subject: [PATCH 137/325] spinlock: Split the lock types header -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 137/327] spinlock: Split the lock types header +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Split raw_spinlock into its own file and the remaining spinlock_t into its own non-RT header. The non-RT header will be replaced later by sleeping @@ -217,5 +220,5 @@ index 000000000000..822bf64a61d3 + +#endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch b/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch index 2063d2b08..84cbf4ef2 100644 --- a/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch +++ b/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch @@ -1,8 +1,11 @@ -From 01781dadb365c4590a6709c8a180b04813ae6e66 Mon Sep 17 00:00:00 2001 +From 058f3288007e8ca9efd8455d8b1d9f9648b2179f Mon Sep 17 00:00:00 2001 +Message-Id: <058f3288007e8ca9efd8455d8b1d9f9648b2179f.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 20:06:39 +0200 -Subject: [PATCH 138/325] rtmutex: Avoid include hell -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 138/327] rtmutex: Avoid include hell +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Include only the required raw types. This avoids pulling in the complete spinlock header which in turn requires rtmutex.h at some point. @@ -26,5 +29,5 @@ index 81ece6a8291a..a355289b1fa1 100644 extern int max_lock_depth; /* for sysctl */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0139-rbtree-don-t-include-the-rcu-header.patch b/debian/patches-rt/0139-rbtree-don-t-include-the-rcu-header.patch index 4e6df93ef..ded122e55 100644 --- a/debian/patches-rt/0139-rbtree-don-t-include-the-rcu-header.patch +++ b/debian/patches-rt/0139-rbtree-don-t-include-the-rcu-header.patch @@ -1,11 +1,14 @@ -From e537e5c666a1da306d036aa5fa1a695c4aaf4163 Mon Sep 17 00:00:00 2001 +From 32ba7416d5cd9967803dab55255f6f11dfddc344 Mon Sep 17 00:00:00 2001 +Message-Id: <32ba7416d5cd9967803dab55255f6f11dfddc344.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 16:56:02 +0100 -Subject: [PATCH 139/325] rbtree: don't include the rcu header +Subject: [PATCH 139/327] rbtree: don't include the rcu header MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The RCU header pulls in spinlock.h and fails due not yet defined types: @@ -171,5 +174,5 @@ index 027c58cdbb6e..e6733d7911e9 100644 * rcu_swap_protected() - swap an RCU and a regular pointer * @rcu_ptr: RCU pointer -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0140-rtmutex-Provide-rt_mutex_slowlock_locked.patch b/debian/patches-rt/0140-rtmutex-Provide-rt_mutex_slowlock_locked.patch index 022cc3c51..8fc89f5fe 100644 --- a/debian/patches-rt/0140-rtmutex-Provide-rt_mutex_slowlock_locked.patch +++ b/debian/patches-rt/0140-rtmutex-Provide-rt_mutex_slowlock_locked.patch @@ -1,8 +1,11 @@ -From 7cb0379b9e963273f1404397480f4b3ba4794553 Mon Sep 17 00:00:00 2001 +From 7ccedbfac836ed42081e1d575cc44efb80e313a5 Mon Sep 17 00:00:00 2001 +Message-Id: <7ccedbfac836ed42081e1d575cc44efb80e313a5.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:14:22 +0200 -Subject: [PATCH 140/325] rtmutex: Provide rt_mutex_slowlock_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 140/327] rtmutex: Provide rt_mutex_slowlock_locked() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz This is the inner-part of rt_mutex_slowlock(), required for rwsem-rt. @@ -141,5 +144,5 @@ index 461527f3f7af..cb9815f0c766 100644 #ifdef CONFIG_DEBUG_RT_MUTEXES # include "rtmutex-debug.h" -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0141-rtmutex-export-lockdep-less-version-of-rt_mutex-s-lo.patch b/debian/patches-rt/0141-rtmutex-export-lockdep-less-version-of-rt_mutex-s-lo.patch index 5fb7115e5..91e1abbe8 100644 --- a/debian/patches-rt/0141-rtmutex-export-lockdep-less-version-of-rt_mutex-s-lo.patch +++ b/debian/patches-rt/0141-rtmutex-export-lockdep-less-version-of-rt_mutex-s-lo.patch @@ -1,9 +1,12 @@ -From 581291e66f417f36ea5d69a433e05c457857868d Mon Sep 17 00:00:00 2001 +From de9c57bfea054f4cc0788a50ab5c0ce7166b59b1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:36:39 +0200 -Subject: [PATCH 141/325] rtmutex: export lockdep-less version of rt_mutex's +Subject: [PATCH 141/327] rtmutex: export lockdep-less version of rt_mutex's lock, trylock and unlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Required for lock implementation ontop of rtmutex. @@ -149,5 +152,5 @@ index cb9815f0c766..5955ad2aa2a8 100644 struct hrtimer_sleeper *timeout, enum rtmutex_chainwalk chwalk, -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch b/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch index f272c82b9..04f0784d8 100644 --- a/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch +++ b/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch @@ -1,8 +1,11 @@ -From 87fd28b5599c18dcef1e63eeb30a5a3bbfcc3ba4 Mon Sep 17 00:00:00 2001 +From 5aa02edaba5d2f35a437de770dac87e498b134c4 Mon Sep 17 00:00:00 2001 +Message-Id: <5aa02edaba5d2f35a437de770dac87e498b134c4.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:11:19 +0200 -Subject: [PATCH 142/325] rtmutex: add sleeping lock implementation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 142/327] rtmutex: add sleeping lock implementation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior @@ -103,7 +106,7 @@ index a355289b1fa1..138bd1e183e0 100644 * rt_mutex_is_locked - is the mutex locked * @lock: the mutex to be queried diff --git a/include/linux/sched.h b/include/linux/sched.h -index f4ff928e6be3..527d04f9163e 100644 +index 30895ae9e82d..a0d1a009aa56 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -134,6 +134,9 @@ struct task_group; @@ -1204,5 +1207,5 @@ index 42b42ebf52bc..6a0ccaea2b42 100644 } } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0143-rtmutex-add-mutex-implementation-based-on-rtmutex.patch b/debian/patches-rt/0143-rtmutex-add-mutex-implementation-based-on-rtmutex.patch index 693bf5ce8..5935a499c 100644 --- a/debian/patches-rt/0143-rtmutex-add-mutex-implementation-based-on-rtmutex.patch +++ b/debian/patches-rt/0143-rtmutex-add-mutex-implementation-based-on-rtmutex.patch @@ -1,8 +1,11 @@ -From 15d28021a92b5a0f1230c2233ae8d4736bef3094 Mon Sep 17 00:00:00 2001 +From 6355bbb9427dc916be52ca71e9e32d33e7fc5bc4 Mon Sep 17 00:00:00 2001 +Message-Id: <6355bbb9427dc916be52ca71e9e32d33e7fc5bc4.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:17:03 +0200 -Subject: [PATCH 143/325] rtmutex: add mutex implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 143/327] rtmutex: add mutex implementation based on rtmutex +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior @@ -379,5 +382,5 @@ index 000000000000..4f81595c0f52 +} +EXPORT_SYMBOL(atomic_dec_and_mutex_lock); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0144-rtmutex-add-rwsem-implementation-based-on-rtmutex.patch b/debian/patches-rt/0144-rtmutex-add-rwsem-implementation-based-on-rtmutex.patch index 5dfc2860d..64ad24122 100644 --- a/debian/patches-rt/0144-rtmutex-add-rwsem-implementation-based-on-rtmutex.patch +++ b/debian/patches-rt/0144-rtmutex-add-rwsem-implementation-based-on-rtmutex.patch @@ -1,8 +1,11 @@ -From fba892eef51771a402f94769548168cd62460a3a Mon Sep 17 00:00:00 2001 +From 72c52b3d53f9a8ffbfaa3820237dd04dd13ab2b7 Mon Sep 17 00:00:00 2001 +Message-Id: <72c52b3d53f9a8ffbfaa3820237dd04dd13ab2b7.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:28:34 +0200 -Subject: [PATCH 144/325] rtmutex: add rwsem implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 144/327] rtmutex: add rwsem implementation based on rtmutex +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The RT specific R/W semaphore implementation restricts the number of readers to one because a writer cannot block on multiple readers and inherit its @@ -423,5 +426,5 @@ index 000000000000..7d3c5cf3d23d + __up_write_unlock(sem, WRITER_BIAS - 1, flags); +} -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0145-rtmutex-add-rwlock-implementation-based-on-rtmutex.patch b/debian/patches-rt/0145-rtmutex-add-rwlock-implementation-based-on-rtmutex.patch index f045d655f..d0d4d848c 100644 --- a/debian/patches-rt/0145-rtmutex-add-rwlock-implementation-based-on-rtmutex.patch +++ b/debian/patches-rt/0145-rtmutex-add-rwlock-implementation-based-on-rtmutex.patch @@ -1,8 +1,11 @@ -From 16054939724213811099f9fdf7071e4cfeb21265 Mon Sep 17 00:00:00 2001 +From 56305d86f046828c4a67051025437ea09a20804d Mon Sep 17 00:00:00 2001 +Message-Id: <56305d86f046828c4a67051025437ea09a20804d.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:18:06 +0200 -Subject: [PATCH 145/325] rtmutex: add rwlock implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 145/327] rtmutex: add rwlock implementation based on rtmutex +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The implementation is bias-based, similar to the rwsem implementation. @@ -578,5 +581,5 @@ index 000000000000..aebb7ce25bc6 +} +EXPORT_SYMBOL(__rt_rwlock_init); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0146-rtmutex-rwlock-preserve-state-like-a-sleeping-lock.patch b/debian/patches-rt/0146-rtmutex-rwlock-preserve-state-like-a-sleeping-lock.patch index a477c48ae..a40cc47fe 100644 --- a/debian/patches-rt/0146-rtmutex-rwlock-preserve-state-like-a-sleeping-lock.patch +++ b/debian/patches-rt/0146-rtmutex-rwlock-preserve-state-like-a-sleeping-lock.patch @@ -1,8 +1,11 @@ -From 227ec3934454027312da6d09e4d5a72ee1109cad Mon Sep 17 00:00:00 2001 +From 54e4d9eea44c2049d36141f662848cc069e0970e Mon Sep 17 00:00:00 2001 +Message-Id: <54e4d9eea44c2049d36141f662848cc069e0970e.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 11 Jan 2019 21:16:31 +0100 -Subject: [PATCH 146/325] rtmutex/rwlock: preserve state like a sleeping lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 146/327] rtmutex/rwlock: preserve state like a sleeping lock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The rwlock is spinning while acquiring a lock. Therefore it must become a sleeping lock on RT and preserve its task state while sleeping and @@ -29,5 +32,5 @@ index aebb7ce25bc6..8f90afe111ce 100644 /* * The slowlock() above is guaranteed to return with the rtmutex is -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0147-rtmutex-wire-up-RT-s-locking.patch b/debian/patches-rt/0147-rtmutex-wire-up-RT-s-locking.patch index b3240c216..9d1ea8b0e 100644 --- a/debian/patches-rt/0147-rtmutex-wire-up-RT-s-locking.patch +++ b/debian/patches-rt/0147-rtmutex-wire-up-RT-s-locking.patch @@ -1,8 +1,11 @@ -From 8c26ff848a29c8a09f12c1ce57133461f07ec3da Mon Sep 17 00:00:00 2001 +From bb46e4ae14099068f1c053ac7ec806290b32cf6d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:31:14 +0200 -Subject: [PATCH 147/325] rtmutex: wire up RT's locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 147/327] rtmutex: wire up RT's locking +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior @@ -267,5 +270,5 @@ index 03595c29c566..d63df281b495 100644 + +#endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0148-rtmutex-add-ww_mutex-addon-for-mutex-rt.patch b/debian/patches-rt/0148-rtmutex-add-ww_mutex-addon-for-mutex-rt.patch index d713b6228..7ba0c6d23 100644 --- a/debian/patches-rt/0148-rtmutex-add-ww_mutex-addon-for-mutex-rt.patch +++ b/debian/patches-rt/0148-rtmutex-add-ww_mutex-addon-for-mutex-rt.patch @@ -1,8 +1,11 @@ -From d6a9cbc956c42c07d71a11067efef3e29237f1e1 Mon Sep 17 00:00:00 2001 +From 276f1bb9886b48d3e86f7cda80f4f5f4955a3c69 Mon Sep 17 00:00:00 2001 +Message-Id: <276f1bb9886b48d3e86f7cda80f4f5f4955a3c69.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 17:34:38 +0200 -Subject: [PATCH 148/325] rtmutex: add ww_mutex addon for mutex-rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 148/327] rtmutex: add ww_mutex addon for mutex-rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Signed-off-by: Sebastian Andrzej Siewior --- @@ -441,5 +444,5 @@ index 7d3c5cf3d23d..660e22caf709 100644 * The slowlock() above is guaranteed to return with the rtmutex (for * ret = 0) is now held, so there can't be a writer active. Increment -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch b/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch index fdaef1334..32a56896f 100644 --- a/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch +++ b/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch @@ -1,8 +1,11 @@ -From 67573be98569ffc12244d2fa84decc676df9728a Mon Sep 17 00:00:00 2001 +From 92a9890eaac73f4208352afb16de0bea72bd4867 Mon Sep 17 00:00:00 2001 +Message-Id: <92a9890eaac73f4208352afb16de0bea72bd4867.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 14:58:57 +0200 -Subject: [PATCH 149/325] kconfig: Add PREEMPT_RT_FULL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 149/327] kconfig: Add PREEMPT_RT_FULL +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Introduce the final symbol for PREEMPT_RT_FULL. @@ -65,5 +68,5 @@ index 87f1fc9801d7..f67b15236936 100755 # Truncate to maximum length -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0150-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch b/debian/patches-rt/0150-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch index 7b26e8e44..c5a1a7160 100644 --- a/debian/patches-rt/0150-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch +++ b/debian/patches-rt/0150-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch @@ -1,9 +1,12 @@ -From 87d8613d1063e08541e25fc170d79d1a675580b8 Mon Sep 17 00:00:00 2001 +From e50dc2d16eb0856f23296afc37c81d056d27be5c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mikulas Patocka Date: Mon, 13 Nov 2017 12:56:53 -0500 -Subject: [PATCH 150/325] locking/rt-mutex: fix deadlock in device mapper / +Subject: [PATCH 150/327] locking/rt-mutex: fix deadlock in device mapper / block-IO -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz When some block device driver creates a bio and submits it to another block device driver, the bio is added to current->bio_list (in order to @@ -77,5 +80,5 @@ index 1f2dc2dfe2e7..b38c3a92dce8 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0151-locking-rt-mutex-Flush-block-plug-on-__down_read.patch b/debian/patches-rt/0151-locking-rt-mutex-Flush-block-plug-on-__down_read.patch index 81a346256..35d57d4d0 100644 --- a/debian/patches-rt/0151-locking-rt-mutex-Flush-block-plug-on-__down_read.patch +++ b/debian/patches-rt/0151-locking-rt-mutex-Flush-block-plug-on-__down_read.patch @@ -1,8 +1,11 @@ -From 0ff5fd365065d431385afd38184b9555c870ce3b Mon Sep 17 00:00:00 2001 +From 5ed8bca72547bc6b4ea93b356bafb784c3c6fd1b Mon Sep 17 00:00:00 2001 +Message-Id: <5ed8bca72547bc6b4ea93b356bafb784c3c6fd1b.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 4 Jan 2019 15:33:21 -0500 -Subject: [PATCH 151/325] locking/rt-mutex: Flush block plug on __down_read() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 151/327] locking/rt-mutex: Flush block plug on __down_read() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz __down_read() bypasses the rtmutex frontend to call rt_mutex_slowlock_locked() directly, and thus it needs to call @@ -42,5 +45,5 @@ index 660e22caf709..f518495bd6cc 100644 might_sleep(); raw_spin_lock_irq(&m->wait_lock); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0152-locking-rtmutex-re-init-the-wait_lock-in-rt_mutex_in.patch b/debian/patches-rt/0152-locking-rtmutex-re-init-the-wait_lock-in-rt_mutex_in.patch index 9d2de957a..2e75daac7 100644 --- a/debian/patches-rt/0152-locking-rtmutex-re-init-the-wait_lock-in-rt_mutex_in.patch +++ b/debian/patches-rt/0152-locking-rtmutex-re-init-the-wait_lock-in-rt_mutex_in.patch @@ -1,9 +1,12 @@ -From ae27c05c699a2836bb476966ecbea706b7f36ea1 Mon Sep 17 00:00:00 2001 +From 8e48bd288e4a0d386891d2a60eb2a2b5d360f2e0 Mon Sep 17 00:00:00 2001 +Message-Id: <8e48bd288e4a0d386891d2a60eb2a2b5d360f2e0.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 16 Nov 2017 16:48:48 +0100 -Subject: [PATCH 152/325] locking/rtmutex: re-init the wait_lock in +Subject: [PATCH 152/327] locking/rtmutex: re-init the wait_lock in rt_mutex_init_proxy_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz We could provide a key-class for the lockdep (and fixup all callers) or move the init to all callers (like it was) in order to avoid lockdep @@ -35,5 +38,5 @@ index b38c3a92dce8..94788662b2f2 100644 rt_mutex_set_owner(lock, proxy_owner); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0153-ptrace-fix-ptrace-vs-tasklist_lock-race.patch b/debian/patches-rt/0153-ptrace-fix-ptrace-vs-tasklist_lock-race.patch index 8a4d7b67d..bb744f928 100644 --- a/debian/patches-rt/0153-ptrace-fix-ptrace-vs-tasklist_lock-race.patch +++ b/debian/patches-rt/0153-ptrace-fix-ptrace-vs-tasklist_lock-race.patch @@ -1,8 +1,11 @@ -From 57eb5afab9ba00a923ba2db4e350e9f5a8c64140 Mon Sep 17 00:00:00 2001 +From 7c8a05b1504ccad35d1c11e58fbcd0ea12f3691c Mon Sep 17 00:00:00 2001 +Message-Id: <7c8a05b1504ccad35d1c11e58fbcd0ea12f3691c.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 18:21:04 +0200 -Subject: [PATCH 153/325] ptrace: fix ptrace vs tasklist_lock race -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 153/327] ptrace: fix ptrace vs tasklist_lock race +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz As explained by Alexander Fyodorov : @@ -31,7 +34,7 @@ Signed-off-by: Sebastian Andrzej Siewior 3 files changed, 68 insertions(+), 7 deletions(-) diff --git a/include/linux/sched.h b/include/linux/sched.h -index 527d04f9163e..dd47fd913997 100644 +index a0d1a009aa56..d207f79c2ecb 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -101,12 +101,8 @@ struct task_group; @@ -162,5 +165,5 @@ index 6a0ccaea2b42..6bab30347081 100644 task_rq_unlock(rq, p, &rf); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch b/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch index a429a37f4..ce5edc5d1 100644 --- a/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch +++ b/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch @@ -1,8 +1,11 @@ -From ead5e97d57b7b8fc9db9448d08de66e482329271 Mon Sep 17 00:00:00 2001 +From 8d309d9cd1061b11cb90cdd581927310e4745c97 Mon Sep 17 00:00:00 2001 +Message-Id: <8d309d9cd1061b11cb90cdd581927310e4745c97.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Sep 2017 14:25:13 +0200 -Subject: [PATCH 154/325] rtmutex: annotate sleeping lock context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 154/327] rtmutex: annotate sleeping lock context +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The RCU code complains on schedule() within a rcu_readlock() section. The valid scenario on -RT is if a sleeping is held. In order to suppress @@ -54,7 +57,7 @@ index 27c3176d88d2..9eafc34898b4 100644 #define migrate_disable() barrier() #define migrate_enable() barrier() diff --git a/include/linux/sched.h b/include/linux/sched.h -index dd47fd913997..682cf84a7e1b 100644 +index d207f79c2ecb..50197f5c4506 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -673,6 +673,15 @@ struct task_struct { @@ -304,5 +307,5 @@ index 6bab30347081..d49580cb0eb2 100644 +EXPORT_SYMBOL(migrate_enable); #endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0155-sched-migrate_disable-fallback-to-preempt_disable-in.patch b/debian/patches-rt/0155-sched-migrate_disable-fallback-to-preempt_disable-in.patch index bcca2e770..4dd76b678 100644 --- a/debian/patches-rt/0155-sched-migrate_disable-fallback-to-preempt_disable-in.patch +++ b/debian/patches-rt/0155-sched-migrate_disable-fallback-to-preempt_disable-in.patch @@ -1,9 +1,12 @@ -From 3e776ffb2eb0413bfae8ab630436d01fc9850ab9 Mon Sep 17 00:00:00 2001 +From 185813801e9ef2197f69582c36fc21dd3b89dddb Mon Sep 17 00:00:00 2001 +Message-Id: <185813801e9ef2197f69582c36fc21dd3b89dddb.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 5 Jul 2018 14:44:51 +0200 -Subject: [PATCH 155/325] sched/migrate_disable: fallback to preempt_disable() +Subject: [PATCH 155/327] sched/migrate_disable: fallback to preempt_disable() instead barrier() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On SMP + !RT migrate_disable() is still around. It is not part of spin_lock() anymore so it has almost no users. However the futex code has a workaround for @@ -71,7 +74,7 @@ index 9eafc34898b4..ed8413e7140f 100644 { return 0; diff --git a/include/linux/sched.h b/include/linux/sched.h -index 682cf84a7e1b..a38a2c2a8fe4 100644 +index 50197f5c4506..4a4f03a8d8d4 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -667,7 +667,7 @@ struct task_struct { @@ -200,5 +203,5 @@ index 5027158d3908..dd6c364d6f01 100644 #endif P(nr_cpus_allowed); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0156-locking-don-t-check-for-__LINUX_SPINLOCK_TYPES_H-on-.patch b/debian/patches-rt/0156-locking-don-t-check-for-__LINUX_SPINLOCK_TYPES_H-on-.patch index 5fd0754d0..6c500b288 100644 --- a/debian/patches-rt/0156-locking-don-t-check-for-__LINUX_SPINLOCK_TYPES_H-on-.patch +++ b/debian/patches-rt/0156-locking-don-t-check-for-__LINUX_SPINLOCK_TYPES_H-on-.patch @@ -1,9 +1,12 @@ -From d11583485bae0e2a7be62d10429e905bcb85966c Mon Sep 17 00:00:00 2001 +From d9ade2d1711540821faa94700e934ba4e8514b7d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 17:40:42 +0200 -Subject: [PATCH 156/325] locking: don't check for __LINUX_SPINLOCK_TYPES_H on +Subject: [PATCH 156/327] locking: don't check for __LINUX_SPINLOCK_TYPES_H on -RT archs -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Upstream uses arch_spinlock_t within spinlock_t and requests that spinlock_types.h header file is included first. @@ -178,5 +181,5 @@ index c09b6407ae1b..b0243ba07fb7 100644 * include/linux/spinlock_types_up.h - spinlock type definitions for UP * -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0157-rcu-Frob-softirq-test.patch b/debian/patches-rt/0157-rcu-Frob-softirq-test.patch index dc711db60..02ebd54b3 100644 --- a/debian/patches-rt/0157-rcu-Frob-softirq-test.patch +++ b/debian/patches-rt/0157-rcu-Frob-softirq-test.patch @@ -1,8 +1,11 @@ -From eb9534a80ffa9abca0340289245a1bdc70bd51b4 Mon Sep 17 00:00:00 2001 +From f349091ea918e71dcabb8ec65ead69b92f7a8669 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Peter Zijlstra Date: Sat, 13 Aug 2011 00:23:17 +0200 -Subject: [PATCH 157/325] rcu: Frob softirq test -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 157/327] rcu: Frob softirq test +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz With RT_FULL we get the below wreckage: @@ -169,5 +172,5 @@ index 35f3552b7463..e9ce51e19e87 100644 "rcu_read_unlock() from irq or softirq with blocking in critical section!!!\n"); pr_alert("->rcu_read_unlock_special: %#x (b: %d, enq: %d nq: %d)\n", -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0158-rcu-Merge-RCU-bh-into-RCU-preempt.patch b/debian/patches-rt/0158-rcu-Merge-RCU-bh-into-RCU-preempt.patch index 1d4a3a6c9..ee928bbd1 100644 --- a/debian/patches-rt/0158-rcu-Merge-RCU-bh-into-RCU-preempt.patch +++ b/debian/patches-rt/0158-rcu-Merge-RCU-bh-into-RCU-preempt.patch @@ -1,8 +1,11 @@ -From 7089cd551063f82f4d753d5ad0b89ce41b44168a Mon Sep 17 00:00:00 2001 +From db28805b69b200f1ca395cb2e93c8430091f5276 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 5 Oct 2011 11:59:38 -0700 -Subject: [PATCH 158/325] rcu: Merge RCU-bh into RCU-preempt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 158/327] rcu: Merge RCU-bh into RCU-preempt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The Linux kernel has long RCU-bh read-side critical sections that intolerably increase scheduling latency under mainline's RCU-bh rules, @@ -347,5 +350,5 @@ index 81688a133552..6ffafb1b1584 100644 #endif /* #ifdef CONFIG_DEBUG_LOCK_ALLOC */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0159-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch b/debian/patches-rt/0159-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch index 249c44875..04f94e2d9 100644 --- a/debian/patches-rt/0159-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch +++ b/debian/patches-rt/0159-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch @@ -1,8 +1,11 @@ -From 64023a5804af7927d9662f817f6949774889b17c Mon Sep 17 00:00:00 2001 +From 8d775d47d5fce590774180cf890951d3d760a04c Mon Sep 17 00:00:00 2001 +Message-Id: <8d775d47d5fce590774180cf890951d3d760a04c.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Wed, 5 Oct 2011 11:45:18 -0700 -Subject: [PATCH 159/325] rcu: Make ksoftirqd do RCU quiescent states -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 159/327] rcu: Make ksoftirqd do RCU quiescent states +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Implementing RCU-bh in terms of RCU-preempt makes the system vulnerable to network-based denial-of-service attacks. This patch therefore @@ -113,5 +116,5 @@ index e9ce51e19e87..938e64c69d18 100644 /* * Prepare a CPU for idle from an RCU perspective. The first major task -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0160-rcu-Eliminate-softirq-processing-from-rcutree.patch b/debian/patches-rt/0160-rcu-Eliminate-softirq-processing-from-rcutree.patch index 823fbb296..6747a451a 100644 --- a/debian/patches-rt/0160-rcu-Eliminate-softirq-processing-from-rcutree.patch +++ b/debian/patches-rt/0160-rcu-Eliminate-softirq-processing-from-rcutree.patch @@ -1,8 +1,11 @@ -From b9089e43759b0d547ad1aefab567bf622e41b560 Mon Sep 17 00:00:00 2001 +From 2af125c8322614ce120f9796a621907f3639ce5c Mon Sep 17 00:00:00 2001 +Message-Id: <2af125c8322614ce120f9796a621907f3639ce5c.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 4 Nov 2013 13:21:10 -0800 -Subject: [PATCH 160/325] rcu: Eliminate softirq processing from rcutree -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 160/327] rcu: Eliminate softirq processing from rcutree +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Running RCU out of softirq is a problem for some workloads that would like to manage RCU core processing independently of other softirq work, @@ -419,5 +422,5 @@ index 938e64c69d18..56639c8ed550 100644 { return false; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0161-srcu-use-cpu_online-instead-custom-check.patch b/debian/patches-rt/0161-srcu-use-cpu_online-instead-custom-check.patch index 4cdc50af0..fef4a4bd9 100644 --- a/debian/patches-rt/0161-srcu-use-cpu_online-instead-custom-check.patch +++ b/debian/patches-rt/0161-srcu-use-cpu_online-instead-custom-check.patch @@ -1,8 +1,11 @@ -From 3202d22e4b6ad35fbe7b617efd78bf1a9a727c5a Mon Sep 17 00:00:00 2001 +From fe13debb17e595e7bf219cb0f43d117b7e20494e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 14:43:41 +0200 -Subject: [PATCH 161/325] srcu: use cpu_online() instead custom check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 161/327] srcu: use cpu_online() instead custom check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The current check via srcu_online is slightly racy because after looking at srcu_online there could be an interrupt that interrupted us long @@ -92,5 +95,5 @@ index ae716ca783bc..f162a4f54b05 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0162-srcu-replace-local_irqsave-with-a-locallock.patch b/debian/patches-rt/0162-srcu-replace-local_irqsave-with-a-locallock.patch index 5263532e5..9015905be 100644 --- a/debian/patches-rt/0162-srcu-replace-local_irqsave-with-a-locallock.patch +++ b/debian/patches-rt/0162-srcu-replace-local_irqsave-with-a-locallock.patch @@ -1,8 +1,11 @@ -From 67e5a1751b9315d556d99ae3a44140d126f2609f Mon Sep 17 00:00:00 2001 +From e485ff43030b7b329d09f41ba72fcc7c19859767 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 18:37:12 +0200 -Subject: [PATCH 162/325] srcu: replace local_irqsave() with a locallock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 162/327] srcu: replace local_irqsave() with a locallock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz There are two instances which disable interrupts in order to become a stable this_cpu_ptr() pointer. The restore part is coupled with @@ -73,5 +76,5 @@ index df0375453ba1..0f09a1a9e17c 100644 srcu_funnel_gp_start(sp, sdp, s, do_norm); else if (needexp) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0163-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch b/debian/patches-rt/0163-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch index 66130d443..3cc160f34 100644 --- a/debian/patches-rt/0163-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch +++ b/debian/patches-rt/0163-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch @@ -1,8 +1,11 @@ -From 724541a3012567e4851d44a94795c42ce9fbc8ab Mon Sep 17 00:00:00 2001 +From bdce9650c14de21dc6f883c78b63cdde85ac104b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julia Cartwright Date: Wed, 12 Oct 2016 11:21:14 -0500 -Subject: [PATCH 163/325] rcu: enable rcu_normal_after_boot by default for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 163/327] rcu: enable rcu_normal_after_boot by default for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The forcing of an expedited grace period is an expensive and very RT-application unfriendly operation, as it forcibly preempts all running @@ -33,5 +36,5 @@ index 6ffafb1b1584..16d8dba23329 100644 #endif /* #ifndef CONFIG_TINY_RCU */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0164-tty-serial-omap-Make-the-locking-RT-aware.patch b/debian/patches-rt/0164-tty-serial-omap-Make-the-locking-RT-aware.patch index 3375865af..d6b97c230 100644 --- a/debian/patches-rt/0164-tty-serial-omap-Make-the-locking-RT-aware.patch +++ b/debian/patches-rt/0164-tty-serial-omap-Make-the-locking-RT-aware.patch @@ -1,8 +1,11 @@ -From 903fb20864016a06c02befdf5331596064256d18 Mon Sep 17 00:00:00 2001 +From 49b86fe86a9000eca1eddd0faf271f5a928711a7 Mon Sep 17 00:00:00 2001 +Message-Id: <49b86fe86a9000eca1eddd0faf271f5a928711a7.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 28 Jul 2011 13:32:57 +0200 -Subject: [PATCH 164/325] tty/serial/omap: Make the locking RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 164/327] tty/serial/omap: Make the locking RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The lock is a sleeping lock and local_irq_save() is not the optimsation we are looking for. Redo it to make it work on -RT and @@ -45,5 +48,5 @@ index 6420ae581a80..0f4f41ed9ffa 100644 static int __init -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0165-tty-serial-pl011-Make-the-locking-work-on-RT.patch b/debian/patches-rt/0165-tty-serial-pl011-Make-the-locking-work-on-RT.patch index 8a2095fb0..744a303d1 100644 --- a/debian/patches-rt/0165-tty-serial-pl011-Make-the-locking-work-on-RT.patch +++ b/debian/patches-rt/0165-tty-serial-pl011-Make-the-locking-work-on-RT.patch @@ -1,8 +1,11 @@ -From 201d2b147cff7ff5557a2b4a60d7b3f609c62b33 Mon Sep 17 00:00:00 2001 +From 136c9182fdb6f6db5ae52d147b50350f745177f6 Mon Sep 17 00:00:00 2001 +Message-Id: <136c9182fdb6f6db5ae52d147b50350f745177f6.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 8 Jan 2013 21:36:51 +0100 -Subject: [PATCH 165/325] tty/serial/pl011: Make the locking work on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 165/327] tty/serial/pl011: Make the locking work on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The lock is a sleeping lock and local_irq_save() is not the optimsation we are looking for. Redo it to make it work on -RT and non-RT. @@ -50,5 +53,5 @@ index af21122dfade..183e8b731d6a 100644 clk_disable(uap->clk); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0166-tty-serial-pl011-explicitly-initialize-the-flags-var.patch b/debian/patches-rt/0166-tty-serial-pl011-explicitly-initialize-the-flags-var.patch index a0054270a..d2da6c520 100644 --- a/debian/patches-rt/0166-tty-serial-pl011-explicitly-initialize-the-flags-var.patch +++ b/debian/patches-rt/0166-tty-serial-pl011-explicitly-initialize-the-flags-var.patch @@ -1,12 +1,15 @@ -From f6bc04fdefa31a35588c0b33de38fd26a8640e38 Mon Sep 17 00:00:00 2001 +From f42cd7c94b862b9618f1488d0bdb886a436a47c9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Kurt Kanzenbach Date: Mon, 24 Sep 2018 10:29:01 +0200 -Subject: [PATCH 166/325] tty: serial: pl011: explicitly initialize the flags +Subject: [PATCH 166/327] tty: serial: pl011: explicitly initialize the flags variable MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Silence the following gcc warning: @@ -41,5 +44,5 @@ index 183e8b731d6a..2cc6b24bc88d 100644 clk_enable(uap->clk); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0167-rt-Improve-the-serial-console-PASS_LIMIT.patch b/debian/patches-rt/0167-rt-Improve-the-serial-console-PASS_LIMIT.patch index 920b4d561..471d94ad4 100644 --- a/debian/patches-rt/0167-rt-Improve-the-serial-console-PASS_LIMIT.patch +++ b/debian/patches-rt/0167-rt-Improve-the-serial-console-PASS_LIMIT.patch @@ -1,11 +1,14 @@ -From b0190da75ae735211f213cfb75ce6fae2ca7af9b Mon Sep 17 00:00:00 2001 +From 076acf7cd2411e5216c03b86d9065e91465502ae Mon Sep 17 00:00:00 2001 +Message-Id: <076acf7cd2411e5216c03b86d9065e91465502ae.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Ingo Molnar Date: Wed, 14 Dec 2011 13:05:54 +0100 -Subject: [PATCH 167/325] rt: Improve the serial console PASS_LIMIT +Subject: [PATCH 167/327] rt: Improve the serial console PASS_LIMIT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Beyond the warning: @@ -43,5 +46,5 @@ index b9567ef843fc..155ee2a54e25 100644 #include /* -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0168-tty-serial-8250-don-t-take-the-trylock-during-oops.patch b/debian/patches-rt/0168-tty-serial-8250-don-t-take-the-trylock-during-oops.patch index a777773d6..92bf6d801 100644 --- a/debian/patches-rt/0168-tty-serial-8250-don-t-take-the-trylock-during-oops.patch +++ b/debian/patches-rt/0168-tty-serial-8250-don-t-take-the-trylock-during-oops.patch @@ -1,8 +1,11 @@ -From 135e815b481b01484f140a639e2482570daa238d Mon Sep 17 00:00:00 2001 +From 04dcace8e4d31440646c49655ffdfc3458feb381 Mon Sep 17 00:00:00 2001 +Message-Id: <04dcace8e4d31440646c49655ffdfc3458feb381.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Apr 2016 16:55:02 +0200 -Subject: [PATCH 168/325] tty: serial: 8250: don't take the trylock during oops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 168/327] tty: serial: 8250: don't take the trylock during oops +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz An oops with irqs off (panic() from irqsafe hrtimer like the watchdog timer) will lead to a lockdep warning on each invocation and as such @@ -31,5 +34,5 @@ index 5a04d4ddca73..79e509468161 100644 spin_lock_irqsave(&port->lock, flags); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0169-locking-percpu-rwsem-Remove-preempt_disable-variants.patch b/debian/patches-rt/0169-locking-percpu-rwsem-Remove-preempt_disable-variants.patch index a8d0fb741..1d349d7da 100644 --- a/debian/patches-rt/0169-locking-percpu-rwsem-Remove-preempt_disable-variants.patch +++ b/debian/patches-rt/0169-locking-percpu-rwsem-Remove-preempt_disable-variants.patch @@ -1,8 +1,11 @@ -From 9c36e91215b7ab35c244cc03986637031183c797 Mon Sep 17 00:00:00 2001 +From 8528a2844b2d0c4d2f5211428d89a883c6aef9a9 Mon Sep 17 00:00:00 2001 +Message-Id: <8528a2844b2d0c4d2f5211428d89a883c6aef9a9.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Peter Zijlstra Date: Wed, 23 Nov 2016 16:29:32 +0100 -Subject: [PATCH 169/325] locking/percpu-rwsem: Remove preempt_disable variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 169/327] locking/percpu-rwsem: Remove preempt_disable variants +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Effective revert commit: @@ -222,5 +225,5 @@ index 79b99d653e03..fb44e237316d 100644 extern void percpu_up_write(struct percpu_rw_semaphore *); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0170-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch b/debian/patches-rt/0170-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch index 1a9831158..7c9899c23 100644 --- a/debian/patches-rt/0170-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch +++ b/debian/patches-rt/0170-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch @@ -1,9 +1,12 @@ -From 4c71d9e6382c1cf6d65629f46dc51039b5c5ca51 Mon Sep 17 00:00:00 2001 +From 2d140e77056f2485d97fc71e86eb4fe88ea9b638 Mon Sep 17 00:00:00 2001 +Message-Id: <2d140e77056f2485d97fc71e86eb4fe88ea9b638.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Yong Zhang Date: Tue, 15 May 2012 13:53:56 +0800 -Subject: [PATCH 170/325] mm: Protect activate_mm() by +Subject: [PATCH 170/327] mm: Protect activate_mm() by preempt_[disable&enable]_rt() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz User preempt_*_rt instead of local_irq_*_rt or otherwise there will be warning on ARM like below: @@ -38,7 +41,7 @@ Signed-off-by: Thomas Gleixner 2 files changed, 4 insertions(+) diff --git a/fs/exec.c b/fs/exec.c -index 561ea64829ec..0d95c6349fb1 100644 +index 3818813d725d..4c7de4ac4302 100644 --- a/fs/exec.c +++ b/fs/exec.c @@ -1028,12 +1028,14 @@ static int exec_mmap(struct mm_struct *mm) @@ -77,5 +80,5 @@ index 3e612ae748e9..d0ccc070979f 100644 #ifdef finish_arch_post_lock_switch finish_arch_post_lock_switch(); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch b/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch index c63e54678..651ece684 100644 --- a/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch +++ b/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch @@ -1,9 +1,12 @@ -From 239c338e19c640a7bbbf54f0d65532dbdff1c655 Mon Sep 17 00:00:00 2001 +From c06901b5bffca9fb653d9b2d9afacb19b0a528a4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 12:32:34 +0200 -Subject: [PATCH 171/325] fs/dcache: bring back explicit INIT_HLIST_BL_HEAD +Subject: [PATCH 171/327] fs/dcache: bring back explicit INIT_HLIST_BL_HEAD init -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Commit 3d375d78593c ("mm: update callers to use HASH_ZERO flag") removed INIT_HLIST_BL_HEAD and uses the ZERO flag instead for the init. However @@ -57,5 +60,5 @@ index 6e0022326afe..10225a9135fb 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0172-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch b/debian/patches-rt/0172-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch index a564da4b5..c98ae716a 100644 --- a/debian/patches-rt/0172-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch +++ b/debian/patches-rt/0172-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch @@ -1,9 +1,12 @@ -From 955db274e65b67831555ae3be55e08c31a431803 Mon Sep 17 00:00:00 2001 +From e5a9997fa04ef53d80f7102e7c27e4797d790ce9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 20 Oct 2017 11:29:53 +0200 -Subject: [PATCH 172/325] fs/dcache: disable preemption on i_dir_seq's write +Subject: [PATCH 172/327] fs/dcache: disable preemption on i_dir_seq's write side -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz i_dir_seq is an opencoded seqcounter. Based on the code it looks like we could have two writers in parallel despite the fact that the d_lock is @@ -95,5 +98,5 @@ index 15b8e02880c3..d27634022105 100644 __u32 i_generation; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch b/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch index 9da5657e2..c337b182e 100644 --- a/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch +++ b/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch @@ -1,9 +1,12 @@ -From faaeaed6663b746f33b73dce36402da1043f70e6 Mon Sep 17 00:00:00 2001 +From 78ec6e98b057176aa4b029dba7e8a4a918b41927 Mon Sep 17 00:00:00 2001 +Message-Id: <78ec6e98b057176aa4b029dba7e8a4a918b41927.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:57 -0500 -Subject: [PATCH 173/325] squashfs: make use of local lock in multi_cpu +Subject: [PATCH 173/327] squashfs: make use of local lock in multi_cpu decompressor -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Currently, the squashfs multi_cpu decompressor makes use of get_cpu_ptr()/put_cpu_ptr(), which unconditionally disable preemption @@ -68,5 +71,5 @@ index 23a9c28ad8ea..6a73c4fa88e7 100644 if (res < 0) ERROR("%s decompression failed, data probably corrupt\n", -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0174-thermal-Defer-thermal-wakups-to-threads.patch b/debian/patches-rt/0174-thermal-Defer-thermal-wakups-to-threads.patch index 2be0e8612..c185e117b 100644 --- a/debian/patches-rt/0174-thermal-Defer-thermal-wakups-to-threads.patch +++ b/debian/patches-rt/0174-thermal-Defer-thermal-wakups-to-threads.patch @@ -1,8 +1,11 @@ -From 6ec6280a8291a12175fe85469e7cd591b3b6aba3 Mon Sep 17 00:00:00 2001 +From 49156a90f418d34f0f6b6911cd3f14b15523ed09 Mon Sep 17 00:00:00 2001 +Message-Id: <49156a90f418d34f0f6b6911cd3f14b15523ed09.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 -Subject: [PATCH 174/325] thermal: Defer thermal wakups to threads -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 174/327] thermal: Defer thermal wakups to threads +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On RT the spin lock in pkg_temp_thermal_platfrom_thermal_notify will call schedule while we run in irq context. @@ -133,5 +136,5 @@ index 1ef937d799e4..a5991cbb408f 100644 module_exit(pkg_temp_thermal_exit) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0175-x86-fpu-Disable-preemption-around-local_bh_disable.patch b/debian/patches-rt/0175-x86-fpu-Disable-preemption-around-local_bh_disable.patch index 90910fba2..d8cc2e703 100644 --- a/debian/patches-rt/0175-x86-fpu-Disable-preemption-around-local_bh_disable.patch +++ b/debian/patches-rt/0175-x86-fpu-Disable-preemption-around-local_bh_disable.patch @@ -1,8 +1,11 @@ -From 51bb97b3e2faccf5e5237a0e4df2b31b2d965a37 Mon Sep 17 00:00:00 2001 +From 70873feadccc7d8297eb626c3ab1ca823cf12bfc Mon Sep 17 00:00:00 2001 +Message-Id: <70873feadccc7d8297eb626c3ab1ca823cf12bfc.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 15:10:33 +0100 -Subject: [PATCH 175/325] x86/fpu: Disable preemption around local_bh_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 175/327] x86/fpu: Disable preemption around local_bh_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz __fpu__restore_sig() restores the content of the FPU state in the CPUs and in order to avoid concurency it disbles BH. On !RT it also disables @@ -34,5 +37,5 @@ index d99a8ee9e185..5e0274a94133 100644 return err; } else { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0176-fs-epoll-Do-not-disable-preemption-on-RT.patch b/debian/patches-rt/0176-fs-epoll-Do-not-disable-preemption-on-RT.patch index c4f356b61..dd65cfcb5 100644 --- a/debian/patches-rt/0176-fs-epoll-Do-not-disable-preemption-on-RT.patch +++ b/debian/patches-rt/0176-fs-epoll-Do-not-disable-preemption-on-RT.patch @@ -1,8 +1,11 @@ -From b5ef225587d776634052edf167298ad29b091b67 Mon Sep 17 00:00:00 2001 +From 8aafb3c9debaf8f93cb0162c38acdeb2b3385421 Mon Sep 17 00:00:00 2001 +Message-Id: <8aafb3c9debaf8f93cb0162c38acdeb2b3385421.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 16:35:35 +0200 -Subject: [PATCH 176/325] fs/epoll: Do not disable preemption on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 176/327] fs/epoll: Do not disable preemption on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz ep_call_nested() takes a sleeping lock so we can't disable preemption. The light version is enough since ep_call_nested() doesn't mind beeing @@ -33,5 +36,5 @@ index 58f48ea0db23..a41120a34e6d 100644 #else -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0177-mm-vmalloc-Another-preempt-disable-region-which-suck.patch b/debian/patches-rt/0177-mm-vmalloc-Another-preempt-disable-region-which-suck.patch index a964a53c4..7f62d8d2b 100644 --- a/debian/patches-rt/0177-mm-vmalloc-Another-preempt-disable-region-which-suck.patch +++ b/debian/patches-rt/0177-mm-vmalloc-Another-preempt-disable-region-which-suck.patch @@ -1,9 +1,12 @@ -From a36f97c1ca6e441ddb3d47465c137d01138549ed Mon Sep 17 00:00:00 2001 +From b8d2101f5c4f2c19e14cf33526b3c56532ac5bdb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 11:39:36 +0200 -Subject: [PATCH 177/325] mm/vmalloc: Another preempt disable region which +Subject: [PATCH 177/327] mm/vmalloc: Another preempt disable region which sucks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Avoid the preempt disable version of get_cpu_var(). The inner-lock should provide enough serialisation. @@ -14,10 +17,10 @@ Signed-off-by: Thomas Gleixner 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c -index 958d6ba9ee2d..ff471d6c350d 100644 +index 11d0f0b6ec79..c6dc3a96e8f3 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c -@@ -852,7 +852,7 @@ static void *new_vmap_block(unsigned int order, gfp_t gfp_mask) +@@ -853,7 +853,7 @@ static void *new_vmap_block(unsigned int order, gfp_t gfp_mask) struct vmap_block *vb; struct vmap_area *va; unsigned long vb_idx; @@ -26,7 +29,7 @@ index 958d6ba9ee2d..ff471d6c350d 100644 void *vaddr; node = numa_node_id(); -@@ -895,11 +895,12 @@ static void *new_vmap_block(unsigned int order, gfp_t gfp_mask) +@@ -896,11 +896,12 @@ static void *new_vmap_block(unsigned int order, gfp_t gfp_mask) BUG_ON(err); radix_tree_preload_end(); @@ -41,7 +44,7 @@ index 958d6ba9ee2d..ff471d6c350d 100644 return vaddr; } -@@ -968,6 +969,7 @@ static void *vb_alloc(unsigned long size, gfp_t gfp_mask) +@@ -969,6 +970,7 @@ static void *vb_alloc(unsigned long size, gfp_t gfp_mask) struct vmap_block *vb; void *vaddr = NULL; unsigned int order; @@ -49,7 +52,7 @@ index 958d6ba9ee2d..ff471d6c350d 100644 BUG_ON(offset_in_page(size)); BUG_ON(size > PAGE_SIZE*VMAP_MAX_ALLOC); -@@ -982,7 +984,8 @@ static void *vb_alloc(unsigned long size, gfp_t gfp_mask) +@@ -983,7 +985,8 @@ static void *vb_alloc(unsigned long size, gfp_t gfp_mask) order = get_order(size); rcu_read_lock(); @@ -59,7 +62,7 @@ index 958d6ba9ee2d..ff471d6c350d 100644 list_for_each_entry_rcu(vb, &vbq->free, free_list) { unsigned long pages_off; -@@ -1005,7 +1008,7 @@ static void *vb_alloc(unsigned long size, gfp_t gfp_mask) +@@ -1006,7 +1009,7 @@ static void *vb_alloc(unsigned long size, gfp_t gfp_mask) break; } @@ -69,5 +72,5 @@ index 958d6ba9ee2d..ff471d6c350d 100644 /* Allocate new block if nothing was found */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0178-block-mq-use-cpu_light.patch b/debian/patches-rt/0178-block-mq-use-cpu_light.patch index 598699935..debad35a5 100644 --- a/debian/patches-rt/0178-block-mq-use-cpu_light.patch +++ b/debian/patches-rt/0178-block-mq-use-cpu_light.patch @@ -1,8 +1,11 @@ -From 48d0958dd08195a8ff4e6b24f5a6107b8664f8b9 Mon Sep 17 00:00:00 2001 +From 0574a9bc12339798fa90b2da8a2a208db018a595 Mon Sep 17 00:00:00 2001 +Message-Id: <0574a9bc12339798fa90b2da8a2a208db018a595.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Apr 2014 10:37:23 +0200 -Subject: [PATCH 178/325] block: mq: use cpu_light() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 178/327] block: mq: use cpu_light() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz there is a might sleep splat because get_cpu() disables preemption and later we grab a lock. As a workaround for this we use get_cpu_light(). @@ -32,5 +35,5 @@ index 5ad9251627f8..5a96c97991b6 100644 struct blk_mq_alloc_data { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0179-block-mq-do-not-invoke-preempt_disable.patch b/debian/patches-rt/0179-block-mq-do-not-invoke-preempt_disable.patch index ce2ae4930..ad8cb6337 100644 --- a/debian/patches-rt/0179-block-mq-do-not-invoke-preempt_disable.patch +++ b/debian/patches-rt/0179-block-mq-do-not-invoke-preempt_disable.patch @@ -1,8 +1,11 @@ -From 47b9729b86adf61e40b4576d3533ae11a283af2f Mon Sep 17 00:00:00 2001 +From 32489808541b98fed062da430dbca78a182e9f0b Mon Sep 17 00:00:00 2001 +Message-Id: <32489808541b98fed062da430dbca78a182e9f0b.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 179/325] block/mq: do not invoke preempt_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 179/327] block/mq: do not invoke preempt_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz preempt_disable() and get_cpu() don't play well together with the sleeping locks it tries to allocate later. @@ -54,5 +57,5 @@ index 4aa3284874f6..376fb90de054 100644 kblockd_mod_delayed_work_on(blk_mq_hctx_next_cpu(hctx), &hctx->run_work, -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0180-block-mq-don-t-complete-requests-via-IPI.patch b/debian/patches-rt/0180-block-mq-don-t-complete-requests-via-IPI.patch index f87759aee..f0788013f 100644 --- a/debian/patches-rt/0180-block-mq-don-t-complete-requests-via-IPI.patch +++ b/debian/patches-rt/0180-block-mq-don-t-complete-requests-via-IPI.patch @@ -1,8 +1,11 @@ -From 7a66ae4854f27f371c06de734ea7541a9e9ec3b6 Mon Sep 17 00:00:00 2001 +From 8bb6d1462d076710f231b5bf4e92e2bc9107be96 Mon Sep 17 00:00:00 2001 +Message-Id: <8bb6d1462d076710f231b5bf4e92e2bc9107be96.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Jan 2015 15:10:08 +0100 -Subject: [PATCH 180/325] block/mq: don't complete requests via IPI -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 180/327] block/mq: don't complete requests via IPI +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The IPI runs in hardirq context and there are sleeping locks. This patch moves the completion into a workqueue. @@ -101,7 +104,7 @@ index 2885dce1ad49..8dbb9ecf9993 100644 void blk_mq_start_request(struct request *rq); void blk_mq_end_request(struct request *rq, blk_status_t error); diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h -index 6e67aeb56928..111ab4209797 100644 +index 745b2d0dcf78..7cd627f2a016 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -149,6 +149,9 @@ enum mq_rq_state { @@ -115,5 +118,5 @@ index 6e67aeb56928..111ab4209797 100644 int cpu; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0181-md-raid5-Make-raid5_percpu-handling-RT-aware.patch b/debian/patches-rt/0181-md-raid5-Make-raid5_percpu-handling-RT-aware.patch index 46eb5bee7..2f9c231c3 100644 --- a/debian/patches-rt/0181-md-raid5-Make-raid5_percpu-handling-RT-aware.patch +++ b/debian/patches-rt/0181-md-raid5-Make-raid5_percpu-handling-RT-aware.patch @@ -1,8 +1,11 @@ -From f157b0b46278489f11209a4147370fc584b2b99d Mon Sep 17 00:00:00 2001 +From db24bcf7ef7994db85d563c384823cb25a9cdd2b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 6 Apr 2010 16:51:31 +0200 -Subject: [PATCH 181/325] md: raid5: Make raid5_percpu handling RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 181/327] md: raid5: Make raid5_percpu handling RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz __raid_run_ops() disables preemption with get_cpu() around the access to the raid5_percpu variables. That causes scheduling while atomic @@ -73,5 +76,5 @@ index 8474c224127b..a3bf907ab2af 100644 struct flex_array *scribble; /* space for constructing buffer * lists and performing address -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch b/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch index 2060df417..ec44b0759 100644 --- a/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch +++ b/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch @@ -1,8 +1,11 @@ -From 733fd0de9c18647a56f62e4b18288a7025cc476a Mon Sep 17 00:00:00 2001 +From b10c792e154c2c9a50625d02ceeb51d35645d3d4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 20:51:03 +0100 -Subject: [PATCH 182/325] rt: Introduce cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 182/327] rt: Introduce cpu_chill() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Retry loops on RT might loop forever when the modifying side was preempted. Add cpu_chill() to replace cpu_relax(). cpu_chill() @@ -109,5 +112,5 @@ index b800efb64238..98a771065818 100644 * Functions related to boot-time initialization: */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0183-hrtimer-Don-t-lose-state-in-cpu_chill.patch b/debian/patches-rt/0183-hrtimer-Don-t-lose-state-in-cpu_chill.patch index a301f083f..3b0031590 100644 --- a/debian/patches-rt/0183-hrtimer-Don-t-lose-state-in-cpu_chill.patch +++ b/debian/patches-rt/0183-hrtimer-Don-t-lose-state-in-cpu_chill.patch @@ -1,8 +1,11 @@ -From 85afc621eb4a204e42836baf2e39a0f0ab1ab150 Mon Sep 17 00:00:00 2001 +From 861e51805cbfdb94f431cb77ce3b956f99072130 Mon Sep 17 00:00:00 2001 +Message-Id: <861e51805cbfdb94f431cb77ce3b956f99072130.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:59:15 +0100 -Subject: [PATCH 183/325] hrtimer: Don't lose state in cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 183/327] hrtimer: Don't lose state in cpu_chill() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In cpu_chill() the state is set to TASK_UNINTERRUPTIBLE and a timer is programmed. On return the state is always TASK_RUNNING which means we @@ -44,5 +47,5 @@ index 98a771065818..21a454557c8a 100644 EXPORT_SYMBOL(cpu_chill); #endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0184-hrtimer-cpu_chill-save-task-state-in-saved_state.patch b/debian/patches-rt/0184-hrtimer-cpu_chill-save-task-state-in-saved_state.patch index e32b2e397..82b9d5f53 100644 --- a/debian/patches-rt/0184-hrtimer-cpu_chill-save-task-state-in-saved_state.patch +++ b/debian/patches-rt/0184-hrtimer-cpu_chill-save-task-state-in-saved_state.patch @@ -1,9 +1,12 @@ -From 9f5be54f1f4d5410605f14e2cfb080ac1dd4d31b Mon Sep 17 00:00:00 2001 +From 51e89a0899c3defe006a25d9121f17dcdcee77a6 Mon Sep 17 00:00:00 2001 +Message-Id: <51e89a0899c3defe006a25d9121f17dcdcee77a6.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 12:31:10 +0100 -Subject: [PATCH 184/325] hrtimer: cpu_chill(): save task state in +Subject: [PATCH 184/327] hrtimer: cpu_chill(): save task state in ->saved_state() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In the previous change I saved the current task state on stack. This was bad because while the task is scheduled-out it might receive a wake-up. @@ -59,5 +62,5 @@ index 21a454557c8a..f16cbc98c47a 100644 EXPORT_SYMBOL(cpu_chill); #endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0185-block-blk-mq-move-blk_queue_usage_counter_release-in.patch b/debian/patches-rt/0185-block-blk-mq-move-blk_queue_usage_counter_release-in.patch index 7905c5660..c6de901b8 100644 --- a/debian/patches-rt/0185-block-blk-mq-move-blk_queue_usage_counter_release-in.patch +++ b/debian/patches-rt/0185-block-blk-mq-move-blk_queue_usage_counter_release-in.patch @@ -1,9 +1,12 @@ -From 477882e8bb18263b11d0a1ef9bfeb405e1c08e52 Mon Sep 17 00:00:00 2001 +From 0cefcdeaa779d1328d15a1ca1ae4fe3eab120370 Mon Sep 17 00:00:00 2001 +Message-Id: <0cefcdeaa779d1328d15a1ca1ae4fe3eab120370.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 -Subject: [PATCH 185/325] block: blk-mq: move blk_queue_usage_counter_release() +Subject: [PATCH 185/327] block: blk-mq: move blk_queue_usage_counter_release() into process context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz | BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914 | in_atomic(): 1, irqs_disabled(): 0, pid: 255, name: kworker/u257:6 @@ -96,7 +99,7 @@ index 4860cd26cd5a..13bf37156bb0 100644 sizeof(struct request), 0, SLAB_PANIC, NULL); diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h -index 111ab4209797..2f3b2e5196eb 100644 +index 7cd627f2a016..cc446661e51e 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -27,6 +27,7 @@ @@ -116,5 +119,5 @@ index 111ab4209797..2f3b2e5196eb 100644 struct list_head all_q_node; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0186-block-Use-cpu_chill-for-retry-loops.patch b/debian/patches-rt/0186-block-Use-cpu_chill-for-retry-loops.patch index 03c7156de..a20b9f283 100644 --- a/debian/patches-rt/0186-block-Use-cpu_chill-for-retry-loops.patch +++ b/debian/patches-rt/0186-block-Use-cpu_chill-for-retry-loops.patch @@ -1,8 +1,11 @@ -From ebf1bbe26f6a3b6b1e785632dc79a9e66e81adc2 Mon Sep 17 00:00:00 2001 +From 388868aedb175c3245a18f5247504248e586ff97 Mon Sep 17 00:00:00 2001 +Message-Id: <388868aedb175c3245a18f5247504248e586ff97.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 20 Dec 2012 18:28:26 +0100 -Subject: [PATCH 186/325] block: Use cpu_chill() for retry loops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 186/327] block: Use cpu_chill() for retry loops +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Retry loops on RT might loop forever when the modifying side was preempted. Steven also observed a live lock when there was a @@ -17,7 +20,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/block/blk-ioc.c b/block/blk-ioc.c -index 01580f88fcb3..98d87e52ccdc 100644 +index 4c810969c3e2..48089f5bcc11 100644 --- a/block/blk-ioc.c +++ b/block/blk-ioc.c @@ -9,6 +9,7 @@ @@ -28,7 +31,7 @@ index 01580f88fcb3..98d87e52ccdc 100644 #include "blk.h" -@@ -118,7 +119,7 @@ static void ioc_release_fn(struct work_struct *work) +@@ -119,7 +120,7 @@ static void ioc_release_fn(struct work_struct *work) spin_unlock(q->queue_lock); } else { spin_unlock_irqrestore(&ioc->lock, flags); @@ -37,7 +40,7 @@ index 01580f88fcb3..98d87e52ccdc 100644 spin_lock_irqsave_nested(&ioc->lock, flags, 1); } } -@@ -202,7 +203,7 @@ void put_io_context_active(struct io_context *ioc) +@@ -203,7 +204,7 @@ void put_io_context_active(struct io_context *ioc) spin_unlock(icq->q->queue_lock); } else { spin_unlock_irqrestore(&ioc->lock, flags); @@ -47,5 +50,5 @@ index 01580f88fcb3..98d87e52ccdc 100644 } } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0187-fs-dcache-Use-cpu_chill-in-trylock-loops.patch b/debian/patches-rt/0187-fs-dcache-Use-cpu_chill-in-trylock-loops.patch index 872c98f4e..b4f884fb8 100644 --- a/debian/patches-rt/0187-fs-dcache-Use-cpu_chill-in-trylock-loops.patch +++ b/debian/patches-rt/0187-fs-dcache-Use-cpu_chill-in-trylock-loops.patch @@ -1,8 +1,11 @@ -From f5454f2bfe74411fddac95ad5c3c8526ad6b28a3 Mon Sep 17 00:00:00 2001 +From 13e35ce47c66c5b2e7feba9b08093e2eaafca8eb Mon Sep 17 00:00:00 2001 +Message-Id: <13e35ce47c66c5b2e7feba9b08093e2eaafca8eb.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:00:34 +0100 -Subject: [PATCH 187/325] fs: dcache: Use cpu_chill() in trylock loops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 187/327] fs: dcache: Use cpu_chill() in trylock loops +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Retry loops on RT might loop forever when the modifying side was preempted. Use cpu_chill() instead of cpu_relax() to let the system @@ -36,7 +39,7 @@ index 70e9afe589fb..1a6b88ad4fe0 100644 } spin_unlock(&p->d_lock); diff --git a/fs/namespace.c b/fs/namespace.c -index 1fce41ba3535..5dc970027e30 100644 +index 741f40cd955e..df83b6e3146f 100644 --- a/fs/namespace.c +++ b/fs/namespace.c @@ -14,6 +14,7 @@ @@ -62,5 +65,5 @@ index 1fce41ba3535..5dc970027e30 100644 * After the slowpath clears MNT_WRITE_HOLD, mnt_is_readonly will * be set to match its requirements. So we must not load that until -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0188-net-Use-cpu_chill-instead-of-cpu_relax.patch b/debian/patches-rt/0188-net-Use-cpu_chill-instead-of-cpu_relax.patch index 0c44ec495..b93694ef1 100644 --- a/debian/patches-rt/0188-net-Use-cpu_chill-instead-of-cpu_relax.patch +++ b/debian/patches-rt/0188-net-Use-cpu_chill-instead-of-cpu_relax.patch @@ -1,8 +1,11 @@ -From c9660b290b88ad7b1e058ecba70708b21eaff85b Mon Sep 17 00:00:00 2001 +From 2ef5814e3af178fcc931b671bd31fdbb874f2c94 Mon Sep 17 00:00:00 2001 +Message-Id: <2ef5814e3af178fcc931b671bd31fdbb874f2c94.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:10:04 +0100 -Subject: [PATCH 188/325] net: Use cpu_chill() instead of cpu_relax() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 188/327] net: Use cpu_chill() instead of cpu_relax() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Retry loops on RT might loop forever when the modifying side was preempted. Use cpu_chill() instead of cpu_relax() to let the system @@ -66,5 +69,5 @@ index 0b347f46b2f4..f395f06031bc 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0189-fs-dcache-use-swait_queue-instead-of-waitqueue.patch b/debian/patches-rt/0189-fs-dcache-use-swait_queue-instead-of-waitqueue.patch index 0b0dde921..9e065caff 100644 --- a/debian/patches-rt/0189-fs-dcache-use-swait_queue-instead-of-waitqueue.patch +++ b/debian/patches-rt/0189-fs-dcache-use-swait_queue-instead-of-waitqueue.patch @@ -1,8 +1,11 @@ -From 44b16a4955e56c4a19b1e22c45172500d8ad261d Mon Sep 17 00:00:00 2001 +From 9871b743e0f6d93cfef299da532d6e33b0c7f2fa Mon Sep 17 00:00:00 2001 +Message-Id: <9871b743e0f6d93cfef299da532d6e33b0c7f2fa.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 14:35:49 +0200 -Subject: [PATCH 189/325] fs/dcache: use swait_queue instead of waitqueue -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 189/327] fs/dcache: use swait_queue instead of waitqueue +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz __d_lookup_done() invokes wake_up_all() while holding a hlist_bl_lock() which disables preemption. As a workaround convert it to swait. @@ -237,5 +240,5 @@ index c7cb30cdd1b7..119a56d7f739 100644 list_splice_init(&q->task_list, &tmp); while (!list_empty(&tmp)) { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch b/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch index f2cfc27c5..cef5d1992 100644 --- a/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch +++ b/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch @@ -1,8 +1,11 @@ -From 0b9664b2a0c21a43367d93c893afe90f7c873b5a Mon Sep 17 00:00:00 2001 +From 73f0f196c0fbc35d972c4ae6d4a8b713cb90156d Mon Sep 17 00:00:00 2001 +Message-Id: <73f0f196c0fbc35d972c4ae6d4a8b713cb90156d.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 24 Jul 2013 15:26:54 +0200 -Subject: [PATCH 190/325] workqueue: Use normal rcu -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 190/327] workqueue: Use normal rcu +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz There is no need for sched_rcu. The undocumented reason why sched_rcu is used is to avoid a few explicit rcu_read_lock()/unlock() pairs by @@ -356,5 +359,5 @@ index eef77c82d2e1..29dc939dad4e 100644 return written; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0191-workqueue-Use-local-irq-lock-instead-of-irq-disable-.patch b/debian/patches-rt/0191-workqueue-Use-local-irq-lock-instead-of-irq-disable-.patch index 7ada3a71e..66e1a34c0 100644 --- a/debian/patches-rt/0191-workqueue-Use-local-irq-lock-instead-of-irq-disable-.patch +++ b/debian/patches-rt/0191-workqueue-Use-local-irq-lock-instead-of-irq-disable-.patch @@ -1,9 +1,12 @@ -From 72906548185c659d4a5693976040709cb5044c1f Mon Sep 17 00:00:00 2001 +From 226f2f0b37980629bafb11fc647d58fb72a8e378 Mon Sep 17 00:00:00 2001 +Message-Id: <226f2f0b37980629bafb11fc647d58fb72a8e378.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:42:26 +0200 -Subject: [PATCH 191/325] workqueue: Use local irq lock instead of irq disable +Subject: [PATCH 191/327] workqueue: Use local irq lock instead of irq disable regions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Use a local_irq_lock as a replacement for irq off regions. We keep the semantic of irq-off in regard to the pool->lock and remain preemptible. @@ -182,5 +185,5 @@ index 29dc939dad4e..f34586370fcb 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0192-workqueue-Prevent-workqueue-versus-ata-piix-livelock.patch b/debian/patches-rt/0192-workqueue-Prevent-workqueue-versus-ata-piix-livelock.patch index 30e15af02..9aec9c24b 100644 --- a/debian/patches-rt/0192-workqueue-Prevent-workqueue-versus-ata-piix-livelock.patch +++ b/debian/patches-rt/0192-workqueue-Prevent-workqueue-versus-ata-piix-livelock.patch @@ -1,8 +1,11 @@ -From 53c5b0958ee67a2e56c5caacd839d18583f12e78 Mon Sep 17 00:00:00 2001 +From 53a76c0acb2fe389e007df6a22af08c78fc36a49 Mon Sep 17 00:00:00 2001 +Message-Id: <53a76c0acb2fe389e007df6a22af08c78fc36a49.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 1 Jul 2013 11:02:42 +0200 -Subject: [PATCH 192/325] workqueue: Prevent workqueue versus ata-piix livelock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 192/327] workqueue: Prevent workqueue versus ata-piix livelock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz An Intel i7 system regularly detected rcu_preempt stalls after the kernel was upgraded from 3.6-rt to 3.8-rt. When the stall happened, disk I/O was no @@ -135,5 +138,5 @@ index f34586370fcb..21484e3938a6 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0193-sched-Distangle-worker-accounting-from-rqlock.patch b/debian/patches-rt/0193-sched-Distangle-worker-accounting-from-rqlock.patch index eea39bcd7..701262869 100644 --- a/debian/patches-rt/0193-sched-Distangle-worker-accounting-from-rqlock.patch +++ b/debian/patches-rt/0193-sched-Distangle-worker-accounting-from-rqlock.patch @@ -1,8 +1,11 @@ -From 6fdac9a09208088f4ed195b86cdadeb37ae5ee1b Mon Sep 17 00:00:00 2001 +From ebeaac812cbd7b7349f59a18d22cd64b704d10f5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Jun 2011 19:47:03 +0200 -Subject: [PATCH 193/325] sched: Distangle worker accounting from rqlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 193/327] sched: Distangle worker accounting from rqlock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The worker accounting for cpu bound workers is plugged into the core scheduler code and the wakeup code. This is not a hard requirement and @@ -287,5 +290,5 @@ index 66fbb5a9e633..30cfed226b39 100644 #endif /* _KERNEL_WORKQUEUE_INTERNAL_H */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch b/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch index 89af74acd..7e4e753b1 100644 --- a/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch +++ b/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch @@ -1,8 +1,11 @@ -From 64a6b61b00e8d28a51171b6461134ce12cb70b28 Mon Sep 17 00:00:00 2001 +From 2fb1b4abf0ad125279cf04ced9e94c086fe9f9cf Mon Sep 17 00:00:00 2001 +Message-Id: <2fb1b4abf0ad125279cf04ced9e94c086fe9f9cf.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:41:35 +0200 -Subject: [PATCH 194/325] debugobjects: Make RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 194/327] debugobjects: Make RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Avoid filling the pool / allocating memory with irqs off(). @@ -28,5 +31,5 @@ index 14afeeb7d6ef..e28481c402ae 100644 db = get_bucket((unsigned long) addr); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch b/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch index 5d329596c..f4e884b17 100644 --- a/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch +++ b/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch @@ -1,8 +1,11 @@ -From df0cac618c41453a2bc5292c8af2ea8e21ee39c1 Mon Sep 17 00:00:00 2001 +From d56d49e0ec841441cf4611f3e4bbd987061bc6cb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Feb 2012 12:03:30 +0100 -Subject: [PATCH 195/325] seqlock: Prevent rt starvation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 195/327] seqlock: Prevent rt starvation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz If a low prio writer gets preempted while holding the seqlock write locked, a high prio reader spins forever on RT. @@ -191,5 +194,5 @@ index 5ce035984a4d..1166fc17b757 100644 { unsigned int seq; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0196-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch b/debian/patches-rt/0196-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch index 234c1acf8..b895e00e3 100644 --- a/debian/patches-rt/0196-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch +++ b/debian/patches-rt/0196-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch @@ -1,9 +1,12 @@ -From 3aac129a44a573f7e78f4f8554d0dee0936e345d Mon Sep 17 00:00:00 2001 +From cfc604a13c627c81a23145d22fac31d31b6f21b3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 18 Feb 2015 16:05:28 +0100 -Subject: [PATCH 196/325] sunrpc: Make svc_xprt_do_enqueue() use +Subject: [PATCH 196/327] sunrpc: Make svc_xprt_do_enqueue() use get_cpu_light() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:915 |in_atomic(): 1, irqs_disabled(): 0, pid: 3194, name: rpc.nfsd @@ -35,7 +38,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/net/sunrpc/svc_xprt.c b/net/sunrpc/svc_xprt.c -index 6cf0fd37cbf0..48c0a0b90946 100644 +index c8ee8e801edb..26fa306c4359 100644 --- a/net/sunrpc/svc_xprt.c +++ b/net/sunrpc/svc_xprt.c @@ -393,7 +393,7 @@ void svc_xprt_do_enqueue(struct svc_xprt *xprt) @@ -57,5 +60,5 @@ index 6cf0fd37cbf0..48c0a0b90946 100644 } EXPORT_SYMBOL_GPL(svc_xprt_do_enqueue); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0197-net-Use-skbufhead-with-raw-lock.patch b/debian/patches-rt/0197-net-Use-skbufhead-with-raw-lock.patch index 1be1a44b0..80a53a0ce 100644 --- a/debian/patches-rt/0197-net-Use-skbufhead-with-raw-lock.patch +++ b/debian/patches-rt/0197-net-Use-skbufhead-with-raw-lock.patch @@ -1,8 +1,11 @@ -From 2ecccb79d16487a93f3885f752f4d03e13b7e308 Mon Sep 17 00:00:00 2001 +From 649410da34cec1ddfcb05a58b0ddfe99a2580f21 Mon Sep 17 00:00:00 2001 +Message-Id: <649410da34cec1ddfcb05a58b0ddfe99a2580f21.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 15:38:34 +0200 -Subject: [PATCH 197/325] net: Use skbufhead with raw lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 197/327] net: Use skbufhead with raw lock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Use the rps lock as rawlock so we can keep irq-off regions. It looks low latency. However we can't kfree() from this context therefore we defer this @@ -53,7 +56,7 @@ index 25407c206e73..d4d7aea13cc6 100644 struct lock_class_key *class) { diff --git a/net/core/dev.c b/net/core/dev.c -index 655dbfac09fd..65eeba4e5eac 100644 +index 0285ea11a788..4c1ee6e8679d 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -218,14 +218,14 @@ static inline struct hlist_head *dev_index_hash(struct net *net, int ifindex) @@ -73,7 +76,7 @@ index 655dbfac09fd..65eeba4e5eac 100644 #endif } -@@ -5248,7 +5248,7 @@ static void flush_backlog(struct work_struct *work) +@@ -5249,7 +5249,7 @@ static void flush_backlog(struct work_struct *work) skb_queue_walk_safe(&sd->input_pkt_queue, skb, tmp) { if (skb->dev->reg_state == NETREG_UNREGISTERING) { __skb_unlink(skb, &sd->input_pkt_queue); @@ -82,7 +85,7 @@ index 655dbfac09fd..65eeba4e5eac 100644 input_queue_head_incr(sd); } } -@@ -5258,11 +5258,14 @@ static void flush_backlog(struct work_struct *work) +@@ -5259,11 +5259,14 @@ static void flush_backlog(struct work_struct *work) skb_queue_walk_safe(&sd->process_queue, skb, tmp) { if (skb->dev->reg_state == NETREG_UNREGISTERING) { __skb_unlink(skb, &sd->process_queue); @@ -98,7 +101,7 @@ index 655dbfac09fd..65eeba4e5eac 100644 } static void flush_all_backlogs(void) -@@ -5841,7 +5844,9 @@ static int process_backlog(struct napi_struct *napi, int quota) +@@ -5842,7 +5845,9 @@ static int process_backlog(struct napi_struct *napi, int quota) while (again) { struct sk_buff *skb; @@ -108,7 +111,7 @@ index 655dbfac09fd..65eeba4e5eac 100644 rcu_read_lock(); __netif_receive_skb(skb); rcu_read_unlock(); -@@ -5849,9 +5854,9 @@ static int process_backlog(struct napi_struct *napi, int quota) +@@ -5850,9 +5855,9 @@ static int process_backlog(struct napi_struct *napi, int quota) if (++work >= quota) return work; @@ -119,7 +122,7 @@ index 655dbfac09fd..65eeba4e5eac 100644 rps_lock(sd); if (skb_queue_empty(&sd->input_pkt_queue)) { /* -@@ -6316,13 +6321,21 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) +@@ -6317,13 +6322,21 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) unsigned long time_limit = jiffies + usecs_to_jiffies(netdev_budget_usecs); int budget = netdev_budget; @@ -141,7 +144,7 @@ index 655dbfac09fd..65eeba4e5eac 100644 for (;;) { struct napi_struct *n; -@@ -9506,10 +9519,13 @@ static int dev_cpu_dead(unsigned int oldcpu) +@@ -9507,10 +9520,13 @@ static int dev_cpu_dead(unsigned int oldcpu) netif_rx_ni(skb); input_queue_head_incr(oldsd); } @@ -156,7 +159,7 @@ index 655dbfac09fd..65eeba4e5eac 100644 return 0; } -@@ -9820,8 +9836,9 @@ static int __init net_dev_init(void) +@@ -9821,8 +9837,9 @@ static int __init net_dev_init(void) INIT_WORK(flush, flush_backlog); @@ -169,5 +172,5 @@ index 655dbfac09fd..65eeba4e5eac 100644 skb_queue_head_init(&sd->xfrm_backlog); #endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0198-net-move-xmit_recursion-to-per-task-variable-on-RT.patch b/debian/patches-rt/0198-net-move-xmit_recursion-to-per-task-variable-on-RT.patch index 9bc143136..2cb071618 100644 --- a/debian/patches-rt/0198-net-move-xmit_recursion-to-per-task-variable-on-RT.patch +++ b/debian/patches-rt/0198-net-move-xmit_recursion-to-per-task-variable-on-RT.patch @@ -1,8 +1,11 @@ -From 333172fb8641ddac36b12e08c4f88892939590d0 Mon Sep 17 00:00:00 2001 +From 72e097fa8ef1fd8ecd84399ddbb74b19e63d164a Mon Sep 17 00:00:00 2001 +Message-Id: <72e097fa8ef1fd8ecd84399ddbb74b19e63d164a.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Jan 2016 15:55:02 +0100 -Subject: [PATCH 198/325] net: move xmit_recursion to per-task variable on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 198/327] net: move xmit_recursion to per-task variable on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz A softirq on -RT can be preempted. That means one task is in __dev_queue_xmit(), gets preempted and another task may enter @@ -184,7 +187,7 @@ index b816eb0bc1c4..5de4b66e11fe 100644 } diff --git a/include/linux/sched.h b/include/linux/sched.h -index a38a2c2a8fe4..756fed8f5994 100644 +index 4a4f03a8d8d4..37334ec1ab3e 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -1216,6 +1216,9 @@ struct task_struct { @@ -198,7 +201,7 @@ index a38a2c2a8fe4..756fed8f5994 100644 int pagefault_disabled; #ifdef CONFIG_MMU diff --git a/net/core/dev.c b/net/core/dev.c -index 65eeba4e5eac..031079f6703b 100644 +index 4c1ee6e8679d..53a86d09f3ca 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -3540,8 +3540,10 @@ static void skb_update_prio(struct sk_buff *skb) @@ -239,7 +242,7 @@ index 65eeba4e5eac..031079f6703b 100644 if (dev_xmit_complete(rc)) { HARD_TX_UNLOCK(dev, txq); goto out; -@@ -8565,7 +8570,7 @@ static void netdev_init_one_queue(struct net_device *dev, +@@ -8566,7 +8571,7 @@ static void netdev_init_one_queue(struct net_device *dev, /* Initialize queue lock */ spin_lock_init(&queue->_xmit_lock); netdev_set_xmit_lockdep_class(&queue->_xmit_lock, dev->type); @@ -274,5 +277,5 @@ index 40b3af05c883..205cd1bb9bc2 100644 return ret; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0199-net-provide-a-way-to-delegate-processing-a-softirq-t.patch b/debian/patches-rt/0199-net-provide-a-way-to-delegate-processing-a-softirq-t.patch index dba5a1018..64929462e 100644 --- a/debian/patches-rt/0199-net-provide-a-way-to-delegate-processing-a-softirq-t.patch +++ b/debian/patches-rt/0199-net-provide-a-way-to-delegate-processing-a-softirq-t.patch @@ -1,9 +1,12 @@ -From af455cf90e7dc741d2f547f1b0920e355053a316 Mon Sep 17 00:00:00 2001 +From 49e52dc25459141a12f80f24b152ed2db30e19ed Mon Sep 17 00:00:00 2001 +Message-Id: <49e52dc25459141a12f80f24b152ed2db30e19ed.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 15:39:05 +0100 -Subject: [PATCH 199/325] net: provide a way to delegate processing a softirq +Subject: [PATCH 199/327] net: provide a way to delegate processing a softirq to ksoftirqd -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz If the NET_RX uses up all of his budget it moves the following NAPI invocations into the `ksoftirqd`. On -RT it does not do so. Instead it @@ -72,10 +75,10 @@ index 27a4bb2303d0..25bcf2f2714b 100644 * This function must run with irqs disabled! */ diff --git a/net/core/dev.c b/net/core/dev.c -index 031079f6703b..f3c394d0037e 100644 +index 53a86d09f3ca..2752a525d57e 100644 --- a/net/core/dev.c +++ b/net/core/dev.c -@@ -6370,7 +6370,7 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) +@@ -6371,7 +6371,7 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) list_splice_tail(&repoll, &list); list_splice(&list, &sd->poll_list); if (!list_empty(&sd->poll_list)) @@ -85,5 +88,5 @@ index 031079f6703b..f3c394d0037e 100644 net_rps_action_and_irq_enable(sd); out: -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0200-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch b/debian/patches-rt/0200-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch index 9c30e6618..5bcf3dd0e 100644 --- a/debian/patches-rt/0200-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch +++ b/debian/patches-rt/0200-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch @@ -1,9 +1,12 @@ -From b06436acd56539e7208907b2c34aa1739e4d7bcb Mon Sep 17 00:00:00 2001 +From 6c5f6a711e2d489bd04217f6103652a6a63bd28b Mon Sep 17 00:00:00 2001 +Message-Id: <6c5f6a711e2d489bd04217f6103652a6a63bd28b.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 30 Mar 2016 13:36:29 +0200 -Subject: [PATCH 200/325] net: dev: always take qdisc's busylock in +Subject: [PATCH 200/327] net: dev: always take qdisc's busylock in __dev_xmit_skb() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The root-lock is dropped before dev_hard_start_xmit() is invoked and after setting the __QDISC___STATE_RUNNING bit. If this task is now pushed away @@ -22,7 +25,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 4 insertions(+) diff --git a/net/core/dev.c b/net/core/dev.c -index f3c394d0037e..ddd65bbfcd3a 100644 +index 2752a525d57e..d8c7c53e1746 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -3468,7 +3468,11 @@ static inline int __dev_xmit_skb(struct sk_buff *skb, struct Qdisc *q, @@ -38,5 +41,5 @@ index f3c394d0037e..ddd65bbfcd3a 100644 spin_lock(&q->busylock); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0201-net-Qdisc-use-a-seqlock-instead-seqcount.patch b/debian/patches-rt/0201-net-Qdisc-use-a-seqlock-instead-seqcount.patch index 6398aef03..8057beb80 100644 --- a/debian/patches-rt/0201-net-Qdisc-use-a-seqlock-instead-seqcount.patch +++ b/debian/patches-rt/0201-net-Qdisc-use-a-seqlock-instead-seqcount.patch @@ -1,8 +1,11 @@ -From 41cf08fe25d006f91cd7ad1a97b7729a4f0c7a20 Mon Sep 17 00:00:00 2001 +From 0c3b73535c653cd8d9086a71a93293af81bb413f Mon Sep 17 00:00:00 2001 +Message-Id: <0c3b73535c653cd8d9086a71a93293af81bb413f.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 17:36:35 +0200 -Subject: [PATCH 201/325] net/Qdisc: use a seqlock instead seqcount -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 201/327] net/Qdisc: use a seqlock instead seqcount +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The seqcount disables preemption on -RT while it is held which can't remove. Also we don't want the reader to spin for ages if the writer is @@ -289,5 +292,5 @@ index 4ab20f1138fd..a9ed58ca3924 100644 sch->ops = ops; sch->flags = ops->static_flags; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0202-net-add-back-the-missing-serialization-in-ip_send_un.patch b/debian/patches-rt/0202-net-add-back-the-missing-serialization-in-ip_send_un.patch index 00436bdd1..38adbc00b 100644 --- a/debian/patches-rt/0202-net-add-back-the-missing-serialization-in-ip_send_un.patch +++ b/debian/patches-rt/0202-net-add-back-the-missing-serialization-in-ip_send_un.patch @@ -1,12 +1,15 @@ -From 933664614b03add80f4578bbb30de2698b553234 Mon Sep 17 00:00:00 2001 +From 926d037cd86721a844c00b3fcf572cdff6ba37de Mon Sep 17 00:00:00 2001 +Message-Id: <926d037cd86721a844c00b3fcf572cdff6ba37de.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:21:56 +0200 -Subject: [PATCH 202/325] net: add back the missing serialization in +Subject: [PATCH 202/327] net: add back the missing serialization in ip_send_unicast_reply() MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Some time ago Sami Pietikäinen reported a crash on -RT in ip_send_unicast_reply() which was later fixed by Nicholas Mc Guire @@ -95,5 +98,5 @@ index 6da393016c11..105e94ff1095 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0203-net-add-a-lock-around-icmp_sk.patch b/debian/patches-rt/0203-net-add-a-lock-around-icmp_sk.patch index edb8e8162..312110ce9 100644 --- a/debian/patches-rt/0203-net-add-a-lock-around-icmp_sk.patch +++ b/debian/patches-rt/0203-net-add-a-lock-around-icmp_sk.patch @@ -1,8 +1,11 @@ -From d379a0b223af3be3d6573649cf5ee15b8e8f9efd Mon Sep 17 00:00:00 2001 +From 0683fd68e530053a37eda2d5c73a7db4a230e6e1 Mon Sep 17 00:00:00 2001 +Message-Id: <0683fd68e530053a37eda2d5c73a7db4a230e6e1.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:54:09 +0200 -Subject: [PATCH 203/325] net: add a lock around icmp_sk() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 203/327] net: add a lock around icmp_sk() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz It looks like the this_cpu_ptr() access in icmp_sk() is protected with local_bh_disable(). To avoid missing serialization in -RT I am adding @@ -61,5 +64,5 @@ index 4efa5e33513e..de67d595e298 100644 int sysctl_icmp_msgs_per_sec __read_mostly = 1000; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0204-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch b/debian/patches-rt/0204-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch index 186a4ea20..0d79ec4a0 100644 --- a/debian/patches-rt/0204-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch +++ b/debian/patches-rt/0204-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch @@ -1,9 +1,12 @@ -From 6d154a08a1e24d7e8cbb139a0b3d72fc211d45bd Mon Sep 17 00:00:00 2001 +From 834e229e50e6c18d38b9c5e66232e2e60f7f9901 Mon Sep 17 00:00:00 2001 +Message-Id: <834e229e50e6c18d38b9c5e66232e2e60f7f9901.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 6 Dec 2016 17:50:30 -0500 -Subject: [PATCH 204/325] net: Have __napi_schedule_irqoff() disable interrupts +Subject: [PATCH 204/327] net: Have __napi_schedule_irqoff() disable interrupts on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz A customer hit a crash where the napi sd->poll_list became corrupted. The customer had the bnx2x driver, which does a @@ -53,10 +56,10 @@ index 5de4b66e11fe..1d6bb0ab437f 100644 static inline bool napi_disable_pending(struct napi_struct *n) { diff --git a/net/core/dev.c b/net/core/dev.c -index ddd65bbfcd3a..efebf78b57b2 100644 +index d8c7c53e1746..40f04f102f20 100644 --- a/net/core/dev.c +++ b/net/core/dev.c -@@ -5940,6 +5940,7 @@ bool napi_schedule_prep(struct napi_struct *n) +@@ -5941,6 +5941,7 @@ bool napi_schedule_prep(struct napi_struct *n) } EXPORT_SYMBOL(napi_schedule_prep); @@ -64,7 +67,7 @@ index ddd65bbfcd3a..efebf78b57b2 100644 /** * __napi_schedule_irqoff - schedule for receive * @n: entry to schedule -@@ -5951,6 +5952,7 @@ void __napi_schedule_irqoff(struct napi_struct *n) +@@ -5952,6 +5953,7 @@ void __napi_schedule_irqoff(struct napi_struct *n) ____napi_schedule(this_cpu_ptr(&softnet_data), n); } EXPORT_SYMBOL(__napi_schedule_irqoff); @@ -73,5 +76,5 @@ index ddd65bbfcd3a..efebf78b57b2 100644 bool napi_complete_done(struct napi_struct *n, int work_done) { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0205-irqwork-push-most-work-into-softirq-context.patch b/debian/patches-rt/0205-irqwork-push-most-work-into-softirq-context.patch index dab5c06e7..60c85572a 100644 --- a/debian/patches-rt/0205-irqwork-push-most-work-into-softirq-context.patch +++ b/debian/patches-rt/0205-irqwork-push-most-work-into-softirq-context.patch @@ -1,8 +1,11 @@ -From 1df56a786174e8a45037c5f0be6c1c34d18162a3 Mon Sep 17 00:00:00 2001 +From bd9134a027f082d0fde6c508f43f1e18895f30d0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 23 Jun 2015 15:32:51 +0200 -Subject: [PATCH 205/325] irqwork: push most work into softirq context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 205/327] irqwork: push most work into softirq context +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Initially we defered all irqwork into softirq because we didn't want the latency spikes if perf or another user was busy and delayed the RT task. @@ -260,5 +263,5 @@ index 3fab1c50bf1b..2fcd56aa6092 100644 if (IS_ENABLED(CONFIG_NO_HZ_COMMON)) __run_timers(this_cpu_ptr(&timer_bases[BASE_DEF])); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0206-printk-Make-rt-aware.patch b/debian/patches-rt/0206-printk-Make-rt-aware.patch index a47bae725..154204227 100644 --- a/debian/patches-rt/0206-printk-Make-rt-aware.patch +++ b/debian/patches-rt/0206-printk-Make-rt-aware.patch @@ -1,8 +1,11 @@ -From ea61badc3b80c688ddb6439a8bd334e111cf6b9f Mon Sep 17 00:00:00 2001 +From 720391fc581c0448db646eba74cce7481ad0db79 Mon Sep 17 00:00:00 2001 +Message-Id: <720391fc581c0448db646eba74cce7481ad0db79.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Sep 2012 14:50:37 +0200 -Subject: [PATCH 206/325] printk: Make rt aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 206/327] printk: Make rt aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Drop the lock before calling the console driver and do not disable interrupts while printing to a serial console. @@ -110,5 +113,5 @@ index f934baed564d..c927f89961a8 100644 if (do_cond_resched) cond_resched(); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0207-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch b/debian/patches-rt/0207-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch index ac9a91664..db559c7f3 100644 --- a/debian/patches-rt/0207-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch +++ b/debian/patches-rt/0207-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch @@ -1,8 +1,11 @@ -From 5791d9898591312bc4dc34c9cb748b2cdfe0026f Mon Sep 17 00:00:00 2001 +From a9a6aadcd03c4b2f49c9712b703214b23099ed5c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 19 May 2016 17:45:27 +0200 -Subject: [PATCH 207/325] kernel/printk: Don't try to print from IRQ/NMI region -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 207/327] kernel/printk: Don't try to print from IRQ/NMI region +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On -RT we try to acquire sleeping locks which might lead to warnings from lockdep or a warn_on() from spin_try_lock() (which is a rtmutex on @@ -44,5 +47,5 @@ index c927f89961a8..49ea374ba8ea 100644 * console_unblank can no longer be called in interrupt context unless * oops_in_progress is set to 1.. -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0208-printk-Drop-the-logbuf_lock-more-often.patch b/debian/patches-rt/0208-printk-Drop-the-logbuf_lock-more-often.patch index 19dec4291..15f5ad77a 100644 --- a/debian/patches-rt/0208-printk-Drop-the-logbuf_lock-more-often.patch +++ b/debian/patches-rt/0208-printk-Drop-the-logbuf_lock-more-often.patch @@ -1,8 +1,11 @@ -From 801157c0e2dc4c9c1a54f714a2f3ac7d2e373e17 Mon Sep 17 00:00:00 2001 +From 25be3b45d50c42251a10913b9c1a14ec64925e56 Mon Sep 17 00:00:00 2001 +Message-Id: <25be3b45d50c42251a10913b9c1a14ec64925e56.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Mar 2013 19:01:05 +0100 -Subject: [PATCH 208/325] printk: Drop the logbuf_lock more often -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 208/327] printk: Drop the logbuf_lock more often +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The lock is hold with irgs off. The latency drops 500us+ on my arm bugs with a "full" buffer after executing "dmesg" on the shell. @@ -79,5 +82,5 @@ index 49ea374ba8ea..acef3657a316 100644 kfree(text); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0209-ARM-enable-irq-in-translation-section-permission-fau.patch b/debian/patches-rt/0209-ARM-enable-irq-in-translation-section-permission-fau.patch index 11faa8e5c..f50de1787 100644 --- a/debian/patches-rt/0209-ARM-enable-irq-in-translation-section-permission-fau.patch +++ b/debian/patches-rt/0209-ARM-enable-irq-in-translation-section-permission-fau.patch @@ -1,12 +1,15 @@ -From 0a08742cc5de665e32bf773748d75ed56e170466 Mon Sep 17 00:00:00 2001 +From efb659c8e2c2664479469b9ade75616201004964 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Yadi.hu" Date: Wed, 10 Dec 2014 10:32:09 +0800 -Subject: [PATCH 209/325] ARM: enable irq in translation/section permission +Subject: [PATCH 209/327] ARM: enable irq in translation/section permission fault handlers MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Probably happens on all ARM, with CONFIG_PREEMPT_RT_FULL @@ -92,5 +95,5 @@ index a9ee0d9dc740..20b0e146de98 100644 return 0; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0210-genirq-update-irq_set_irqchip_state-documentation.patch b/debian/patches-rt/0210-genirq-update-irq_set_irqchip_state-documentation.patch index 2b99280dc..db6ad2162 100644 --- a/debian/patches-rt/0210-genirq-update-irq_set_irqchip_state-documentation.patch +++ b/debian/patches-rt/0210-genirq-update-irq_set_irqchip_state-documentation.patch @@ -1,8 +1,11 @@ -From cd209691e4220adde61d3e0c36179232a565dee3 Mon Sep 17 00:00:00 2001 +From 7a277c502a25ccc72209d2403003df058644f774 Mon Sep 17 00:00:00 2001 +Message-Id: <7a277c502a25ccc72209d2403003df058644f774.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:00 -0600 -Subject: [PATCH 210/325] genirq: update irq_set_irqchip_state documentation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 210/327] genirq: update irq_set_irqchip_state documentation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On -rt kernels, the use of migrate_disable()/migrate_enable() is sufficient to guarantee a task isn't moved to another CPU. Update the @@ -28,5 +31,5 @@ index ccd8af6fe49d..1a3cf77b11f8 100644 */ int irq_set_irqchip_state(unsigned int irq, enum irqchip_irq_state which, -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0211-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch b/debian/patches-rt/0211-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch index 1872322df..a48a7ca4e 100644 --- a/debian/patches-rt/0211-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch +++ b/debian/patches-rt/0211-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch @@ -1,9 +1,12 @@ -From b0db55e7a9eb7ef9e80ffbe089999bf94abe5f52 Mon Sep 17 00:00:00 2001 +From 07ae278abba38ca5193ad0dbeb0f7a44bfa0041a Mon Sep 17 00:00:00 2001 +Message-Id: <07ae278abba38ca5193ad0dbeb0f7a44bfa0041a.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:01 -0600 -Subject: [PATCH 211/325] KVM: arm/arm64: downgrade preempt_disable()d region +Subject: [PATCH 211/327] KVM: arm/arm64: downgrade preempt_disable()d region to migrate_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz kvm_arch_vcpu_ioctl_run() disables the use of preemption when updating the vgic and timer states to prevent the calling task from migrating to @@ -55,5 +58,5 @@ index d982650deb33..efe2d6c0201c 100644 ret = handle_exit(vcpu, run, ret); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0212-arm64-fpsimd-use-preemp_disable-in-addition-to-local.patch b/debian/patches-rt/0212-arm64-fpsimd-use-preemp_disable-in-addition-to-local.patch index 068bcc2f0..f00cf8d7a 100644 --- a/debian/patches-rt/0212-arm64-fpsimd-use-preemp_disable-in-addition-to-local.patch +++ b/debian/patches-rt/0212-arm64-fpsimd-use-preemp_disable-in-addition-to-local.patch @@ -1,9 +1,12 @@ -From 393b855896741c2df780f95d03412417717d4db2 Mon Sep 17 00:00:00 2001 +From e48ab745454fd06631eabb8407fd706741e96842 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jul 2018 14:02:38 +0200 -Subject: [PATCH 212/325] arm64: fpsimd: use preemp_disable in addition to +Subject: [PATCH 212/327] arm64: fpsimd: use preemp_disable in addition to local_bh_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In v4.16-RT I noticed a number of warnings from task_fpsimd_load(). The code disables BH and expects that it is not preemptible. On -RT the @@ -167,5 +170,5 @@ index 14fdbaa6ee3a..7d572175682a 100644 EXPORT_SYMBOL(kernel_neon_begin); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch b/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch index 20f5a3c02..fbef70ce4 100644 --- a/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch +++ b/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch @@ -1,8 +1,11 @@ -From 170661f56dab5575f4fa40a094e2bd185afb3908 Mon Sep 17 00:00:00 2001 +From b03b52a1c0ada966349d978f63694711f4886c0f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Jason Wessel Date: Thu, 28 Jul 2011 12:42:23 -0500 -Subject: [PATCH 213/325] kgdb/serial: Short term workaround -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 213/327] kgdb/serial: Short term workaround +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On 07/27/2011 04:37 PM, Thomas Gleixner wrote: > - KGDB (not yet disabled) is reportedly unusable on -rt right now due @@ -82,5 +85,5 @@ index 6a4b41484afe..197cb422f6e1 100644 return r; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0214-sysfs-Add-sys-kernel-realtime-entry.patch b/debian/patches-rt/0214-sysfs-Add-sys-kernel-realtime-entry.patch index 65c0518ad..ac80e3d20 100644 --- a/debian/patches-rt/0214-sysfs-Add-sys-kernel-realtime-entry.patch +++ b/debian/patches-rt/0214-sysfs-Add-sys-kernel-realtime-entry.patch @@ -1,8 +1,11 @@ -From 8e96037a97736d38d4c47e4e2a01b0d16061467c Mon Sep 17 00:00:00 2001 +From fdeaa601470c87da07098368fb1e024b95cadd3f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Clark Williams Date: Sat, 30 Jul 2011 21:55:53 -0500 -Subject: [PATCH 214/325] sysfs: Add /sys/kernel/realtime entry -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 214/327] sysfs: Add /sys/kernel/realtime entry +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Add a /sys/kernel entry to indicate that the kernel is a realtime kernel. @@ -50,5 +53,5 @@ index 46ba853656f6..9a23632b6294 100644 NULL }; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch b/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch index 1e918bb38..0224f459a 100644 --- a/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch +++ b/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch @@ -1,8 +1,11 @@ -From 93adaef2afa4c9475254580129869286a8dbea03 Mon Sep 17 00:00:00 2001 +From f816993d61b04e5660ec3fbfcf1ee44b76c3fff3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Peter Zijlstra Date: Thu, 28 Jul 2011 10:43:51 +0200 -Subject: [PATCH 215/325] mm, rt: kmap_atomic scheduling -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 215/327] mm, rt: kmap_atomic scheduling +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In fact, with migrate_disable() existing one could play games with kmap_atomic. You could save/restore the kmap_atomic slots on context @@ -248,7 +251,7 @@ index 0690679832d4..1ac89e4718bf 100644 } diff --git a/include/linux/sched.h b/include/linux/sched.h -index 756fed8f5994..dc668524ccff 100644 +index 37334ec1ab3e..f18668e166f2 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -28,6 +28,7 @@ @@ -321,5 +324,5 @@ index 59db3223a5d6..22aa3ddbd87b 100644 unsigned int nr_free_highpages (void) { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0216-x86-highmem-Add-a-already-used-pte-check.patch b/debian/patches-rt/0216-x86-highmem-Add-a-already-used-pte-check.patch index a143efb3a..759ffa025 100644 --- a/debian/patches-rt/0216-x86-highmem-Add-a-already-used-pte-check.patch +++ b/debian/patches-rt/0216-x86-highmem-Add-a-already-used-pte-check.patch @@ -1,8 +1,11 @@ -From e31b99ed8028c6712b1664b2dc50011d9371b0d4 Mon Sep 17 00:00:00 2001 +From b2d1c972af3abf2f0994d969cf968033c569916c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 17:09:55 +0100 -Subject: [PATCH 216/325] x86/highmem: Add a "already used pte" check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 216/327] x86/highmem: Add a "already used pte" check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz This is a copy from kmap_atomic_prot(). @@ -25,5 +28,5 @@ index d5a48210d0f6..c0ec8d430c02 100644 current->kmap_pte[type] = pte; #endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0217-arm-highmem-Flush-tlb-on-unmap.patch b/debian/patches-rt/0217-arm-highmem-Flush-tlb-on-unmap.patch index 6a9b8e721..983083f9b 100644 --- a/debian/patches-rt/0217-arm-highmem-Flush-tlb-on-unmap.patch +++ b/debian/patches-rt/0217-arm-highmem-Flush-tlb-on-unmap.patch @@ -1,8 +1,11 @@ -From e2e2e6bfc0c52d0b6f159920b94e93df8843807d Mon Sep 17 00:00:00 2001 +From 8edc794852167a4e17981e677be5cf82365d85b0 Mon Sep 17 00:00:00 2001 +Message-Id: <8edc794852167a4e17981e677be5cf82365d85b0.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 21:37:27 +0100 -Subject: [PATCH 217/325] arm/highmem: Flush tlb on unmap -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 217/327] arm/highmem: Flush tlb on unmap +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The tlb should be flushed on unmap and thus make the mapping entry invalid. This is only done in the non-debug case which does not look @@ -30,5 +33,5 @@ index d02f8187b1cc..eb4b225d28c9 100644 } else if (vaddr >= PKMAP_ADDR(0) && vaddr < PKMAP_ADDR(LAST_PKMAP)) { /* this address was obtained through kmap_high_get() */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch b/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch index deaf513d9..cec2b1f21 100644 --- a/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch +++ b/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch @@ -1,8 +1,11 @@ -From 7e6c3574daf6585185e8d527a17e98c12b70af8f Mon Sep 17 00:00:00 2001 +From c9eda580e525766a543472623318f020ab73d37f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 13 Feb 2013 11:03:11 +0100 -Subject: [PATCH 218/325] arm: Enable highmem for rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 218/327] arm: Enable highmem for rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz fixup highmem for ARM. @@ -180,5 +183,5 @@ index 1ac89e4718bf..eaa2ef9bc10e 100644 #include -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch b/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch index fcddac9d8..5475f1dcb 100644 --- a/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch +++ b/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch @@ -1,8 +1,11 @@ -From f9942365667b0c9170e0e87b7221705c559683d1 Mon Sep 17 00:00:00 2001 +From 5abb9840afaaa4e3935ac609013c1f28148a7feb Mon Sep 17 00:00:00 2001 +Message-Id: <5abb9840afaaa4e3935ac609013c1f28148a7feb.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 12 Nov 2011 14:00:48 +0100 -Subject: [PATCH 219/325] scsi/fcoe: Make RT aware. -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 219/327] scsi/fcoe: Make RT aware. +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Do not disable preemption while taking sleeping locks. All user look safe for migrate_diable() only. @@ -112,5 +115,5 @@ index 6ba257cbc6d9..d2398a19f84c 100644 /* peek cache of free slot */ if (pool->left != FC_XID_UNKNOWN) { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0220-x86-crypto-Reduce-preempt-disabled-regions.patch b/debian/patches-rt/0220-x86-crypto-Reduce-preempt-disabled-regions.patch index cdd582043..f3a6e2110 100644 --- a/debian/patches-rt/0220-x86-crypto-Reduce-preempt-disabled-regions.patch +++ b/debian/patches-rt/0220-x86-crypto-Reduce-preempt-disabled-regions.patch @@ -1,8 +1,11 @@ -From 70e03d592732e45dfa91ed382404c60a03ad0202 Mon Sep 17 00:00:00 2001 +From 8af4085d71a12122609f5009818af7db77aacf67 Mon Sep 17 00:00:00 2001 +Message-Id: <8af4085d71a12122609f5009818af7db77aacf67.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 14 Nov 2011 18:19:27 +0100 -Subject: [PATCH 220/325] x86: crypto: Reduce preempt disabled regions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 220/327] x86: crypto: Reduce preempt disabled regions +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Restrict the preempt disabled regions to the actual floating point operations and enable preemption for the administrative actions. @@ -114,5 +117,5 @@ index 917f25e4d0a8..58d8c03fc32d 100644 return err; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0221-crypto-Reduce-preempt-disabled-regions-more-algos.patch b/debian/patches-rt/0221-crypto-Reduce-preempt-disabled-regions-more-algos.patch index a57e89702..289d62914 100644 --- a/debian/patches-rt/0221-crypto-Reduce-preempt-disabled-regions-more-algos.patch +++ b/debian/patches-rt/0221-crypto-Reduce-preempt-disabled-regions-more-algos.patch @@ -1,8 +1,11 @@ -From 54513c07d07617c245ba13e2c56c569b1d47eb4d Mon Sep 17 00:00:00 2001 +From 67cdc048042ccfcc95a4c64f47137fd3792abccc Mon Sep 17 00:00:00 2001 +Message-Id: <67cdc048042ccfcc95a4c64f47137fd3792abccc.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2014 17:24:04 +0100 -Subject: [PATCH 221/325] crypto: Reduce preempt disabled regions, more algos -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 221/327] crypto: Reduce preempt disabled regions, more algos +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Don Estabrook reported | kernel: WARNING: CPU: 2 PID: 858 at kernel/sched/core.c:2428 migrate_disable+0xed/0x100() @@ -259,5 +262,5 @@ index a78ef99a9981..dac489a1c4da 100644 } EXPORT_SYMBOL_GPL(glue_xts_req_128bit); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0222-crypto-limit-more-FPU-enabled-sections.patch b/debian/patches-rt/0222-crypto-limit-more-FPU-enabled-sections.patch index 26a684ba9..0644f6c06 100644 --- a/debian/patches-rt/0222-crypto-limit-more-FPU-enabled-sections.patch +++ b/debian/patches-rt/0222-crypto-limit-more-FPU-enabled-sections.patch @@ -1,11 +1,14 @@ -From 5368881693eeb89db040948e8911af5a704debb2 Mon Sep 17 00:00:00 2001 +From 37c6deaa26be42b026c801fd852a5f590c613fc8 Mon Sep 17 00:00:00 2001 +Message-Id: <37c6deaa26be42b026c801fd852a5f590c613fc8.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 30 Nov 2017 13:40:10 +0100 -Subject: [PATCH 222/325] crypto: limit more FPU-enabled sections +Subject: [PATCH 222/327] crypto: limit more FPU-enabled sections MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Those crypto drivers use SSE/AVX/… for their crypto work and in order to do so in kernel they need to enable the "FPU" in kernel mode which @@ -104,5 +107,5 @@ index 2e5003fef51a..768c53767bb2 100644 * Save the FPU state (mark it for reload if necessary): * -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0223-crypto-scompress-serialize-RT-percpu-scratch-buffer-.patch b/debian/patches-rt/0223-crypto-scompress-serialize-RT-percpu-scratch-buffer-.patch index 773926399..b9c6e67a0 100644 --- a/debian/patches-rt/0223-crypto-scompress-serialize-RT-percpu-scratch-buffer-.patch +++ b/debian/patches-rt/0223-crypto-scompress-serialize-RT-percpu-scratch-buffer-.patch @@ -1,9 +1,12 @@ -From 7e78bc20913ad1e15f26623a153852802cec3da6 Mon Sep 17 00:00:00 2001 +From 2b3aab178446471bf8bc15f995b7949360c4786b Mon Sep 17 00:00:00 2001 +Message-Id: <2b3aab178446471bf8bc15f995b7949360c4786b.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 11 Jul 2018 17:14:47 +0200 -Subject: [PATCH 223/325] crypto: scompress - serialize RT percpu scratch +Subject: [PATCH 223/327] crypto: scompress - serialize RT percpu scratch buffer access with a local lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz | BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:974 | in_atomic(): 1, irqs_disabled(): 0, pid: 1401, name: cryptomgr_test @@ -79,5 +82,5 @@ index 968bbcf65c94..c2f0077e0801 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0224-crypto-cryptd-add-a-lock-instead-preempt_disable-loc.patch b/debian/patches-rt/0224-crypto-cryptd-add-a-lock-instead-preempt_disable-loc.patch index 398fdf433..79d5fb8a3 100644 --- a/debian/patches-rt/0224-crypto-cryptd-add-a-lock-instead-preempt_disable-loc.patch +++ b/debian/patches-rt/0224-crypto-cryptd-add-a-lock-instead-preempt_disable-loc.patch @@ -1,9 +1,12 @@ -From 16d33551afe71fce5f6c74376d543ad66293fe9b Mon Sep 17 00:00:00 2001 +From a530d6830e609debd667089469ee1ef5a077084d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 18:52:00 +0200 -Subject: [PATCH 224/325] crypto: cryptd - add a lock instead +Subject: [PATCH 224/327] crypto: cryptd - add a lock instead preempt_disable/local_bh_disable -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz cryptd has a per-CPU lock which protected with local_bh_disable() and preempt_disable(). @@ -81,5 +84,5 @@ index e0c8e907b086..e079f9a70201 100644 if (!req) return; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0225-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch b/debian/patches-rt/0225-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch index 5838bae2a..e92474e37 100644 --- a/debian/patches-rt/0225-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch +++ b/debian/patches-rt/0225-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch @@ -1,9 +1,12 @@ -From d12a028cd42d3b1e973b81f39e15641480bb9ffd Mon Sep 17 00:00:00 2001 +From e6e355f3d19f6889b295b28c534f113255882251 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 225/325] panic: skip get_random_bytes for RT_FULL in +Subject: [PATCH 225/327] panic: skip get_random_bytes for RT_FULL in init_oops_id -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Disable on -RT. If this is invoked from irq-context we will have problems to acquire the sleeping lock. @@ -30,5 +33,5 @@ index 8138a676fb7d..fa114be5c30f 100644 return 0; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0226-x86-stackprotector-Avoid-random-pool-on-rt.patch b/debian/patches-rt/0226-x86-stackprotector-Avoid-random-pool-on-rt.patch index 1c4e0cbdb..1111a38cb 100644 --- a/debian/patches-rt/0226-x86-stackprotector-Avoid-random-pool-on-rt.patch +++ b/debian/patches-rt/0226-x86-stackprotector-Avoid-random-pool-on-rt.patch @@ -1,8 +1,11 @@ -From 4e386d000be9c36e56caa970e99aea818986cbec Mon Sep 17 00:00:00 2001 +From 52fcf66c1b4f281bec1dbfd8daa9669cd67ab610 Mon Sep 17 00:00:00 2001 +Message-Id: <52fcf66c1b4f281bec1dbfd8daa9669cd67ab610.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 16 Dec 2010 14:25:18 +0100 -Subject: [PATCH 226/325] x86: stackprotector: Avoid random pool on rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 226/327] x86: stackprotector: Avoid random pool on rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz CPU bringup calls into the random pool to initialize the stack canary. During boot that works nicely even on RT as the might sleep @@ -47,5 +50,5 @@ index 8ec97a62c245..7bc85841fc56 100644 canary += tsc + (tsc << 32UL); canary &= CANARY_MASK; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0227-random-Make-it-work-on-rt.patch b/debian/patches-rt/0227-random-Make-it-work-on-rt.patch index be81504e8..ca004d61e 100644 --- a/debian/patches-rt/0227-random-Make-it-work-on-rt.patch +++ b/debian/patches-rt/0227-random-Make-it-work-on-rt.patch @@ -1,8 +1,11 @@ -From c6da6886f88cf56b43a37670ec2c12c5d0b58044 Mon Sep 17 00:00:00 2001 +From 218a3a3be9f0a569aadc632ea2cb55badcc66c31 Mon Sep 17 00:00:00 2001 +Message-Id: <218a3a3be9f0a569aadc632ea2cb55badcc66c31.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 21 Aug 2012 20:38:50 +0200 -Subject: [PATCH 227/325] random: Make it work on rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 227/327] random: Make it work on rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Delegate the random insertion to the forced threaded interrupt handler. Store the return IP of the hard interrupt handler in the irq @@ -77,10 +80,10 @@ index 12bc9fa21111..278f03f50147 100644 static int hv_ce_set_next_event(unsigned long delta, diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c -index 9aa18f387a34..39aaa14993cc 100644 +index fb22b72fd535..cfbcc2dce208 100644 --- a/drivers/hv/vmbus_drv.c +++ b/drivers/hv/vmbus_drv.c -@@ -1042,6 +1042,8 @@ static void vmbus_isr(void) +@@ -1070,6 +1070,8 @@ static void vmbus_isr(void) void *page_addr = hv_cpu->synic_event_page; struct hv_message *msg; union hv_synic_event_flags *event; @@ -89,7 +92,7 @@ index 9aa18f387a34..39aaa14993cc 100644 bool handled = false; if (unlikely(page_addr == NULL)) -@@ -1085,7 +1087,7 @@ static void vmbus_isr(void) +@@ -1113,7 +1115,7 @@ static void vmbus_isr(void) tasklet_schedule(&hv_cpu->msg_dpc); } @@ -163,5 +166,5 @@ index 1a3cf77b11f8..9591a451e05a 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch b/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch index b0576a6be..203e8e77a 100644 --- a/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch +++ b/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch @@ -1,8 +1,11 @@ -From 4e82f79ed7a3629248241e307320aa1ba73aeaa2 Mon Sep 17 00:00:00 2001 +From c5190a8398ef2e9ce8dc267ec8a2f27807578989 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Jul 2017 17:31:20 +0200 -Subject: [PATCH 228/325] cpu/hotplug: Implement CPU pinning -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 228/327] cpu/hotplug: Implement CPU pinning +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Signed-off-by: Thomas Gleixner --- @@ -11,7 +14,7 @@ Signed-off-by: Thomas Gleixner 2 files changed, 39 insertions(+) diff --git a/include/linux/sched.h b/include/linux/sched.h -index dc668524ccff..fc9300d0787d 100644 +index f18668e166f2..ff1fe0b3c1e3 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -671,6 +671,7 @@ struct task_struct { @@ -23,7 +26,7 @@ index dc668524ccff..fc9300d0787d 100644 int migrate_disable_atomic; # endif diff --git a/kernel/cpu.c b/kernel/cpu.c -index 328d7bf67d2f..e005e64ae30f 100644 +index dc5d1e940e25..c00eab509c0b 100644 --- a/kernel/cpu.c +++ b/kernel/cpu.c @@ -75,6 +75,11 @@ static DEFINE_PER_CPU(struct cpuhp_cpu_state, cpuhp_state) = { @@ -113,5 +116,5 @@ index 328d7bf67d2f..e005e64ae30f 100644 irq_unlock_sparse(); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0229-sched-Allow-pinned-user-tasks-to-be-awakened-to-the-.patch b/debian/patches-rt/0229-sched-Allow-pinned-user-tasks-to-be-awakened-to-the-.patch index 33c2b9fa4..03c263000 100644 --- a/debian/patches-rt/0229-sched-Allow-pinned-user-tasks-to-be-awakened-to-the-.patch +++ b/debian/patches-rt/0229-sched-Allow-pinned-user-tasks-to-be-awakened-to-the-.patch @@ -1,9 +1,12 @@ -From 6c85c9d14af744f5849d8a712a166b3673f5d2fa Mon Sep 17 00:00:00 2001 +From 3368d2233e8cf9fe184446b68e13215e1c033889 Mon Sep 17 00:00:00 2001 +Message-Id: <3368d2233e8cf9fe184446b68e13215e1c033889.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 19 Aug 2018 08:28:35 +0200 -Subject: [PATCH 229/325] sched: Allow pinned user tasks to be awakened to the +Subject: [PATCH 229/327] sched: Allow pinned user tasks to be awakened to the CPU they pinned -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Since commit 7af443ee16976 ("sched/core: Require cpu_active() in select_task_rq(), for user tasks") select_fallback_rq() will BUG() if @@ -35,5 +38,5 @@ index dcf2deedd3f8..6ef0dcea94d7 100644 return cpu_active(cpu); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0230-hotplug-duct-tape-RT-rwlock-usage-for-non-RT.patch b/debian/patches-rt/0230-hotplug-duct-tape-RT-rwlock-usage-for-non-RT.patch index 10e1d1470..41ade42bb 100644 --- a/debian/patches-rt/0230-hotplug-duct-tape-RT-rwlock-usage-for-non-RT.patch +++ b/debian/patches-rt/0230-hotplug-duct-tape-RT-rwlock-usage-for-non-RT.patch @@ -1,8 +1,11 @@ -From a7ad4f3355c842964614bdfec4ab3c08082dc074 Mon Sep 17 00:00:00 2001 +From 8bd097564d158db7352d7339c5bfd3a774559d27 Mon Sep 17 00:00:00 2001 +Message-Id: <8bd097564d158db7352d7339c5bfd3a774559d27.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 18:31:00 +0200 -Subject: [PATCH 230/325] hotplug: duct-tape RT-rwlock usage for non-RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 230/327] hotplug: duct-tape RT-rwlock usage for non-RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz This type is only available on -RT. We need to craft something for non-RT. Since the only migrate_disable() user is -RT only, there is no @@ -14,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/kernel/cpu.c b/kernel/cpu.c -index e005e64ae30f..948fbcc4d63c 100644 +index c00eab509c0b..4841696b0fc0 100644 --- a/kernel/cpu.c +++ b/kernel/cpu.c @@ -75,7 +75,7 @@ static DEFINE_PER_CPU(struct cpuhp_cpu_state, cpuhp_state) = { @@ -98,5 +101,5 @@ index e005e64ae30f..948fbcc4d63c 100644 irq_unlock_sparse(); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0231-net-Remove-preemption-disabling-in-netif_rx.patch b/debian/patches-rt/0231-net-Remove-preemption-disabling-in-netif_rx.patch index 8ebd4beb3..c232353b8 100644 --- a/debian/patches-rt/0231-net-Remove-preemption-disabling-in-netif_rx.patch +++ b/debian/patches-rt/0231-net-Remove-preemption-disabling-in-netif_rx.patch @@ -1,8 +1,11 @@ -From 49d2a425ffed7592c3ab05c01653311d6f2dc878 Mon Sep 17 00:00:00 2001 +From 71a332a0660d2f29b981dc7a62d62dbc1268e286 Mon Sep 17 00:00:00 2001 +Message-Id: <71a332a0660d2f29b981dc7a62d62dbc1268e286.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Priyanka Jain Date: Thu, 17 May 2012 09:35:11 +0530 -Subject: [PATCH 231/325] net: Remove preemption disabling in netif_rx() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 231/327] net: Remove preemption disabling in netif_rx() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz 1)enqueue_to_backlog() (called from netif_rx) should be bind to a particluar CPU. This can be achieved by @@ -36,10 +39,10 @@ Signed-off-by: Thomas Gleixner 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/net/core/dev.c b/net/core/dev.c -index efebf78b57b2..81174cf6bf9a 100644 +index 40f04f102f20..0544619bf62b 100644 --- a/net/core/dev.c +++ b/net/core/dev.c -@@ -4489,7 +4489,7 @@ static int netif_rx_internal(struct sk_buff *skb) +@@ -4490,7 +4490,7 @@ static int netif_rx_internal(struct sk_buff *skb) struct rps_dev_flow voidflow, *rflow = &voidflow; int cpu; @@ -48,7 +51,7 @@ index efebf78b57b2..81174cf6bf9a 100644 rcu_read_lock(); cpu = get_rps_cpu(skb->dev, skb, &rflow); -@@ -4499,14 +4499,14 @@ static int netif_rx_internal(struct sk_buff *skb) +@@ -4500,14 +4500,14 @@ static int netif_rx_internal(struct sk_buff *skb) ret = enqueue_to_backlog(skb, cpu, &rflow->last_qtail); rcu_read_unlock(); @@ -67,5 +70,5 @@ index efebf78b57b2..81174cf6bf9a 100644 return ret; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0232-net-Another-local_irq_disable-kmalloc-headache.patch b/debian/patches-rt/0232-net-Another-local_irq_disable-kmalloc-headache.patch index 56306a740..1bca2a78c 100644 --- a/debian/patches-rt/0232-net-Another-local_irq_disable-kmalloc-headache.patch +++ b/debian/patches-rt/0232-net-Another-local_irq_disable-kmalloc-headache.patch @@ -1,8 +1,11 @@ -From 0b7fd8c1fb0d391cbb75bf3343f4bb1aade387ad Mon Sep 17 00:00:00 2001 +From 2608599ac9cf769d8a52fcbac2439790f136c966 Mon Sep 17 00:00:00 2001 +Message-Id: <2608599ac9cf769d8a52fcbac2439790f136c966.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Sep 2012 16:21:08 +0200 -Subject: [PATCH 232/325] net: Another local_irq_disable/kmalloc headache -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 232/327] net: Another local_irq_disable/kmalloc headache +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Replace it by a local lock. Though that's pretty inefficient :( @@ -61,5 +64,5 @@ index 0629ca89ab74..6ca7cb2b4364 100644 if (unlikely(!data)) return NULL; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0233-net-core-protect-users-of-napi_alloc_cache-against-r.patch b/debian/patches-rt/0233-net-core-protect-users-of-napi_alloc_cache-against-r.patch index b74bbde4b..2213e6526 100644 --- a/debian/patches-rt/0233-net-core-protect-users-of-napi_alloc_cache-against-r.patch +++ b/debian/patches-rt/0233-net-core-protect-users-of-napi_alloc_cache-against-r.patch @@ -1,9 +1,12 @@ -From 6b203654d8df14f8220b6aca13cea79eca4c401e Mon Sep 17 00:00:00 2001 +From c023a3e44757d028d779a93a150909511e9a583c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 15 Jan 2016 16:33:34 +0100 -Subject: [PATCH 233/325] net/core: protect users of napi_alloc_cache against +Subject: [PATCH 233/327] net/core: protect users of napi_alloc_cache against reentrance -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On -RT the code running in BH can not be moved to another CPU so CPU local variable remain local. However the code can be preempted @@ -115,5 +118,5 @@ index 6ca7cb2b4364..c5c0d2095873 100644 void __kfree_skb_defer(struct sk_buff *skb) { -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0234-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch b/debian/patches-rt/0234-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch index a8cd6ae28..37eb3722f 100644 --- a/debian/patches-rt/0234-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch +++ b/debian/patches-rt/0234-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch @@ -1,9 +1,12 @@ -From 6d3705f90c5a421b590ab921ceec46da6167e5a9 Mon Sep 17 00:00:00 2001 +From 638925d9a73dbee1a98f11df9e3da0e071b3d58b Mon Sep 17 00:00:00 2001 +Message-Id: <638925d9a73dbee1a98f11df9e3da0e071b3d58b.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 11:18:08 +0100 -Subject: [PATCH 234/325] net: netfilter: Serialize xt_write_recseq sections on +Subject: [PATCH 234/327] net: netfilter: Serialize xt_write_recseq sections on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The netfilter code relies only on the implicit semantics of local_bh_disable() for serializing wt_write_recseq sections. RT breaks @@ -80,5 +83,5 @@ index 93aaec3a54ec..b364cf8e5776 100644 EXPORT_SYMBOL_GPL(nf_ipv6_ops); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0235-net-Add-a-mutex-around-devnet_rename_seq.patch b/debian/patches-rt/0235-net-Add-a-mutex-around-devnet_rename_seq.patch index 41a7bbd32..7f52aaeec 100644 --- a/debian/patches-rt/0235-net-Add-a-mutex-around-devnet_rename_seq.patch +++ b/debian/patches-rt/0235-net-Add-a-mutex-around-devnet_rename_seq.patch @@ -1,8 +1,11 @@ -From 10dbf1ed93bf3b5e4708bb97a2d690135db04f70 Mon Sep 17 00:00:00 2001 +From aff8fe96bd1f91327dcc5711c71b8ac9334763d9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Mar 2013 18:06:20 +0100 -Subject: [PATCH 235/325] net: Add a mutex around devnet_rename_seq -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 235/327] net: Add a mutex around devnet_rename_seq +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On RT write_seqcount_begin() disables preemption and device_rename() allocates memory with GFP_KERNEL and grabs later the sysfs_mutex @@ -22,7 +25,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 20 insertions(+), 14 deletions(-) diff --git a/net/core/dev.c b/net/core/dev.c -index 81174cf6bf9a..be33b775565e 100644 +index 0544619bf62b..7be74a0cee23 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -196,6 +196,7 @@ static unsigned int napi_gen_id = NR_CPUS; @@ -109,5 +112,5 @@ index 81174cf6bf9a..be33b775565e 100644 /** -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0236-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch b/debian/patches-rt/0236-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch index 2e54589b2..45dbfb334 100644 --- a/debian/patches-rt/0236-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch +++ b/debian/patches-rt/0236-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch @@ -1,9 +1,12 @@ -From a7433e1568e592ed54f114147646a3ab23d5ce5e Mon Sep 17 00:00:00 2001 +From 8a88f96f8d22784eafd3395e45d7918f7438dedb Mon Sep 17 00:00:00 2001 +Message-Id: <8a88f96f8d22784eafd3395e45d7918f7438dedb.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Yong Zhang Date: Mon, 16 Apr 2012 15:01:56 +0800 -Subject: [PATCH 236/325] lockdep: selftest: Only do hardirq context test for +Subject: [PATCH 236/327] lockdep: selftest: Only do hardirq context test for raw spinlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz On -rt there is no softirq context any more and rwlock is sleepable, disable softirq context test and rwlock+irq test. @@ -58,5 +61,5 @@ index 1e1bbf171eca..5cdf3809905e 100644 ww_tests(); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0237-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch b/debian/patches-rt/0237-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch index be0653bc8..373ca0ff0 100644 --- a/debian/patches-rt/0237-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch +++ b/debian/patches-rt/0237-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch @@ -1,9 +1,12 @@ -From 17d81d48ff86eb0c073d5d52660b57dd2b6a3c4c Mon Sep 17 00:00:00 2001 +From aa8945e200d231bcd73cc4879b95437fde2153de Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Josh Cartwright Date: Wed, 28 Jan 2015 13:08:45 -0600 -Subject: [PATCH 237/325] lockdep: selftest: fix warnings due to missing +Subject: [PATCH 237/327] lockdep: selftest: fix warnings due to missing PREEMPT_RT conditionals -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz "lockdep: Selftest: Only do hardirq context test for raw spinlock" disabled the execution of certain tests with PREEMPT_RT_FULL, but did @@ -145,5 +148,5 @@ index 5cdf3809905e..32db9532ddd4 100644 * read-lock / write-lock recursion that is unsafe. */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0238-sched-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0238-sched-Add-support-for-lazy-preemption.patch index bfb0cfb4a..052c6d0a3 100644 --- a/debian/patches-rt/0238-sched-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0238-sched-Add-support-for-lazy-preemption.patch @@ -1,8 +1,11 @@ -From 457f29371e64b1dbd2b086ba9c2a356d2606ec4a Mon Sep 17 00:00:00 2001 +From 22321605269fd1510f3175f23208cfab0e75a30c Mon Sep 17 00:00:00 2001 +Message-Id: <22321605269fd1510f3175f23208cfab0e75a30c.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 26 Oct 2012 18:50:54 +0100 -Subject: [PATCH 238/325] sched: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 238/327] sched: Add support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz It has become an obsession to mitigate the determinism vs. throughput loss of RT. Looking at the mainline semantics of preemption points @@ -144,7 +147,7 @@ index ed8413e7140f..9c74a019bf57 100644 } while (0) diff --git a/include/linux/sched.h b/include/linux/sched.h -index fc9300d0787d..a8ebd49c4f96 100644 +index ff1fe0b3c1e3..852b1221cd40 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -1733,6 +1733,44 @@ static inline int test_tsk_need_resched(struct task_struct *tsk) @@ -245,7 +248,7 @@ index 907d72b3ba95..306567f72a3e 100644 prompt "Preemption Model" default PREEMPT_NONE diff --git a/kernel/cpu.c b/kernel/cpu.c -index 948fbcc4d63c..1541189f417b 100644 +index 4841696b0fc0..9f2e05b2e65c 100644 --- a/kernel/cpu.c +++ b/kernel/cpu.c @@ -304,11 +304,13 @@ void pin_current_cpu(void) @@ -510,10 +513,10 @@ index 68de18405857..12a12be6770b 100644 /* diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h -index c79e32488940..c90574112bca 100644 +index 96823c632599..005874299b04 100644 --- a/kernel/sched/sched.h +++ b/kernel/sched/sched.h -@@ -1634,6 +1634,15 @@ extern void reweight_task(struct task_struct *p, int prio); +@@ -1640,6 +1640,15 @@ extern void reweight_task(struct task_struct *p, int prio); extern void resched_curr(struct rq *rq); extern void resched_cpu(int cpu); @@ -667,5 +670,5 @@ index 46c96744f09d..3f78b0afb729 100644 trace_seq_printf(s, "%x", entry->migrate_disable); else -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0239-ftrace-Fix-trace-header-alignment.patch b/debian/patches-rt/0239-ftrace-Fix-trace-header-alignment.patch index 9e4c1bf58..6642d5167 100644 --- a/debian/patches-rt/0239-ftrace-Fix-trace-header-alignment.patch +++ b/debian/patches-rt/0239-ftrace-Fix-trace-header-alignment.patch @@ -1,8 +1,11 @@ -From 64b09bacabda019a04a3a3186650578b7a6c9ea6 Mon Sep 17 00:00:00 2001 +From 1f028c3fa41b6d0e061772451c518b4d0ccbd97d Mon Sep 17 00:00:00 2001 +Message-Id: <1f028c3fa41b6d0e061772451c518b4d0ccbd97d.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:08:30 +0200 -Subject: [PATCH 239/325] ftrace: Fix trace header alignment -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 239/327] ftrace: Fix trace header alignment +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Line up helper arrows to the right column. @@ -48,5 +51,5 @@ index 89d54ed4f9a7..1d7fc29ac791 100644 static void print_event_info(struct trace_buffer *buf, struct seq_file *m) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0240-x86-Support-for-lazy-preemption.patch b/debian/patches-rt/0240-x86-Support-for-lazy-preemption.patch index bc03b6787..7a524d66a 100644 --- a/debian/patches-rt/0240-x86-Support-for-lazy-preemption.patch +++ b/debian/patches-rt/0240-x86-Support-for-lazy-preemption.patch @@ -1,8 +1,11 @@ -From 4568f5dff51999abb9a5d5714f7989d5fe3896dd Mon Sep 17 00:00:00 2001 +From a68c49357d823798978eb8648ef51cdd4507aac0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 11:03:47 +0100 -Subject: [PATCH 240/325] x86: Support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 240/327] x86: Support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Implement the x86 pieces for lazy preempt. @@ -52,7 +55,7 @@ index 91676b0d2d4c..3b5e41d9b29d 100644 #ifdef ARCH_RT_DELAYS_SIGNAL_SEND diff --git a/arch/x86/entry/entry_32.S b/arch/x86/entry/entry_32.S -index d07432062ee6..d44f446a0e74 100644 +index 37d9016d4768..324b7539eaab 100644 --- a/arch/x86/entry/entry_32.S +++ b/arch/x86/entry/entry_32.S @@ -750,8 +750,25 @@ END(ret_from_exception) @@ -236,5 +239,5 @@ index 01de31db300d..ce1c5b9fbd8c 100644 /* TLB state for the entry code */ OFFSET(TLB_STATE_user_pcid_flush_mask, tlb_state, user_pcid_flush_mask); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0241-x86-lazy-preempt-properly-check-against-preempt-mask.patch b/debian/patches-rt/0241-x86-lazy-preempt-properly-check-against-preempt-mask.patch index f2b3501a6..5ab7c5bc4 100644 --- a/debian/patches-rt/0241-x86-lazy-preempt-properly-check-against-preempt-mask.patch +++ b/debian/patches-rt/0241-x86-lazy-preempt-properly-check-against-preempt-mask.patch @@ -1,9 +1,12 @@ -From be6b5fb800c318f640ab6ec8eb4d73e6e66eaf40 Mon Sep 17 00:00:00 2001 +From eec11c55311df8e5260514905cb94be65d685f5d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 16:57:09 +0100 -Subject: [PATCH 241/325] x86: lazy-preempt: properly check against +Subject: [PATCH 241/327] x86: lazy-preempt: properly check against preempt-mask -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz should_resched() should check against preempt_offset after unmasking the need-resched-bit. Otherwise should_resched() won't work for @@ -29,5 +32,5 @@ index 22992c837795..f66708779274 100644 if (current_thread_info()->preempt_lazy_count) return false; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0242-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch b/debian/patches-rt/0242-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch index 46d6c907b..eb28fb31d 100644 --- a/debian/patches-rt/0242-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch +++ b/debian/patches-rt/0242-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch @@ -1,9 +1,12 @@ -From 8ffe4b93b950bae866bc4ea9089408f5b8328d5b Mon Sep 17 00:00:00 2001 +From babaa84c4b56177e15c6b292f1a180519eb1d5c0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 14:53:49 +0100 -Subject: [PATCH 242/325] x86: lazy-preempt: use proper return label on +Subject: [PATCH 242/327] x86: lazy-preempt: use proper return label on 32bit-x86 -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The lazy-preempt uses the wrong return label in case preemption isn't possible. This results crash while returning to the kernel. @@ -17,7 +20,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/x86/entry/entry_32.S b/arch/x86/entry/entry_32.S -index d44f446a0e74..56398b07211b 100644 +index 324b7539eaab..d8b40085c2b8 100644 --- a/arch/x86/entry/entry_32.S +++ b/arch/x86/entry/entry_32.S @@ -759,15 +759,15 @@ ENTRY(resume_kernel) @@ -41,5 +44,5 @@ index d44f446a0e74..56398b07211b 100644 testl $X86_EFLAGS_IF, PT_EFLAGS(%esp) # interrupts off (exception path) ? jz restore_all_kernel -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0243-arm-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0243-arm-Add-support-for-lazy-preemption.patch index 7f2ac7827..0655b4d9d 100644 --- a/debian/patches-rt/0243-arm-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0243-arm-Add-support-for-lazy-preemption.patch @@ -1,8 +1,11 @@ -From 43660867519b464d2fe3cda84c73f92020f2bf96 Mon Sep 17 00:00:00 2001 +From 5144a4b80748eee8b8b4501d5139aa9b57cb3a92 Mon Sep 17 00:00:00 2001 +Message-Id: <5144a4b80748eee8b8b4501d5139aa9b57cb3a92.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 31 Oct 2012 12:04:11 +0100 -Subject: [PATCH 243/325] arm: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 243/327] arm: Add support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Implement the arm pieces for lazy preempt. @@ -164,5 +167,5 @@ index b908382b69ff..339fbc281cf1 100644 } else { if (unlikely(!user_mode(regs))) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0244-powerpc-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0244-powerpc-Add-support-for-lazy-preemption.patch index 5d5642f33..b52c3f70f 100644 --- a/debian/patches-rt/0244-powerpc-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0244-powerpc-Add-support-for-lazy-preemption.patch @@ -1,8 +1,11 @@ -From 8e284ba9115056adda44a911dffce7bfa383fb6a Mon Sep 17 00:00:00 2001 +From 5face30891c5ee1313adfabbf77e0cb7c1d06de6 Mon Sep 17 00:00:00 2001 +Message-Id: <5face30891c5ee1313adfabbf77e0cb7c1d06de6.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 10:14:11 +0100 -Subject: [PATCH 244/325] powerpc: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 244/327] powerpc: Add support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Implement the powerpc pieces for lazy preempt. @@ -192,5 +195,5 @@ index 58b50967b3e5..ef02e41d5d96 100644 /* -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0245-arch-arm64-Add-lazy-preempt-support.patch b/debian/patches-rt/0245-arch-arm64-Add-lazy-preempt-support.patch index 998a30032..a941e765e 100644 --- a/debian/patches-rt/0245-arch-arm64-Add-lazy-preempt-support.patch +++ b/debian/patches-rt/0245-arch-arm64-Add-lazy-preempt-support.patch @@ -1,8 +1,11 @@ -From 3dfd8be63b6736541e2c6c0decab854778573c65 Mon Sep 17 00:00:00 2001 +From 6da13f809db48d860b72eaca9fc870c05eeecd03 Mon Sep 17 00:00:00 2001 +Message-Id: <6da13f809db48d860b72eaca9fc870c05eeecd03.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Anders Roxell Date: Thu, 14 May 2015 17:52:17 +0200 -Subject: [PATCH 245/325] arch/arm64: Add lazy preempt support -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 245/327] arch/arm64: Add lazy preempt support +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz arm64 is missing support for PREEMPT_RT. The main feature which is lacking is support for lazy preemption. The arch-specific entry code, @@ -21,7 +24,7 @@ Signed-off-by: Anders Roxell 5 files changed, 17 insertions(+), 5 deletions(-) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig -index 51fe21f5d078..9bf5be2d6024 100644 +index 1fe3e5cb2927..6cbaf00c14ca 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -141,6 +141,7 @@ config ARM64 @@ -129,5 +132,5 @@ index 5dcc942906db..4fec251fe147 100644 local_daif_restore(DAIF_PROCCTX_NOIRQ); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0246-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch b/debian/patches-rt/0246-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch index 3261221ed..c07fca0c9 100644 --- a/debian/patches-rt/0246-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch +++ b/debian/patches-rt/0246-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch @@ -1,9 +1,12 @@ -From 1eed9b912ffd15cfa4b21eed03047caa1a342793 Mon Sep 17 00:00:00 2001 +From c11c7b9369ed010493e8ee6bcdf275566aab8e64 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:11:54 +0200 -Subject: [PATCH 246/325] connector/cn_proc: Protect send_msg() with a local +Subject: [PATCH 246/327] connector/cn_proc: Protect send_msg() with a local lock on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:931 |in_atomic(): 1, irqs_disabled(): 0, pid: 31807, name: sleep @@ -70,5 +73,5 @@ index ad48fd52cb53..c5264b3ee0b0 100644 void proc_fork_connector(struct task_struct *task) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0247-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch b/debian/patches-rt/0247-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch index 308e3c380..4a339180f 100644 --- a/debian/patches-rt/0247-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch +++ b/debian/patches-rt/0247-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch @@ -1,9 +1,12 @@ -From a7c2fa6469af6930d216847445366a31e578c551 Mon Sep 17 00:00:00 2001 +From 6a9f3b3224d6932cbd20176d28645bd9e71da50e Mon Sep 17 00:00:00 2001 +Message-Id: <6a9f3b3224d6932cbd20176d28645bd9e71da50e.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 31 Mar 2016 04:08:28 +0200 -Subject: [PATCH 247/325] drivers/block/zram: Replace bit spinlocks with +Subject: [PATCH 247/327] drivers/block/zram: Replace bit spinlocks with rtmutex for -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz They're nondeterministic, and lead to ___might_sleep() splats in -rt. OTOH, they're a lot less wasteful than an rtmutex per page. @@ -100,5 +103,5 @@ index d1095dfdffa8..144e91061df8 100644 ktime_t ac_time; #endif -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0248-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch b/debian/patches-rt/0248-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch index 0928ea5ee..6a4701f94 100644 --- a/debian/patches-rt/0248-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch +++ b/debian/patches-rt/0248-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch @@ -1,9 +1,12 @@ -From 0df868e81dab3ab27436db83c1c4450762e18732 Mon Sep 17 00:00:00 2001 +From af7f66c685825c4cf835696a0e833fa5dce30ca3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 20 Oct 2016 11:15:22 +0200 -Subject: [PATCH 248/325] drivers/zram: Don't disable preemption in +Subject: [PATCH 248/327] drivers/zram: Don't disable preemption in zcomp_stream_get/put() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz In v4.7, the driver switched to percpu compression streams, disabling preemption via get/put_cpu_ptr(). Use a per-zcomp_strm lock here. We @@ -103,5 +106,5 @@ index d6cf9508b80d..71520199226a 100644 /* Should NEVER happen. Return bio error if it does. */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0249-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch b/debian/patches-rt/0249-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch index f697465da..a6fda9a63 100644 --- a/debian/patches-rt/0249-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch +++ b/debian/patches-rt/0249-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch @@ -1,9 +1,12 @@ -From 44c6e90b8eb58224617f979562d4614543ec3df1 Mon Sep 17 00:00:00 2001 +From fff3d02075c974741a1943f2ce9b4fa3e0f123bb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 23 Aug 2017 11:57:29 +0200 -Subject: [PATCH 249/325] drivers/zram: fix zcomp_stream_get() +Subject: [PATCH 249/327] drivers/zram: fix zcomp_stream_get() smp_processor_id() use in preemptible code -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Use get_local_ptr() instead this_cpu_ptr() to avoid a warning regarding smp_processor_id() in preemptible code. @@ -40,5 +43,5 @@ index dd65a27ae2cc..eece02262000 100644 int zcomp_compress(struct zcomp_strm *zstrm, -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0250-tpm_tis-fix-stall-after-iowrite-s.patch b/debian/patches-rt/0250-tpm_tis-fix-stall-after-iowrite-s.patch index 027838e84..81e8896f1 100644 --- a/debian/patches-rt/0250-tpm_tis-fix-stall-after-iowrite-s.patch +++ b/debian/patches-rt/0250-tpm_tis-fix-stall-after-iowrite-s.patch @@ -1,8 +1,11 @@ -From 2fd4af0cf67e67ff4d6de0cd2302ebf9729c03a9 Mon Sep 17 00:00:00 2001 +From 43974733073ca5b9de9280ec07789fdc89465464 Mon Sep 17 00:00:00 2001 +Message-Id: <43974733073ca5b9de9280ec07789fdc89465464.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Haris Okanovic Date: Tue, 15 Aug 2017 15:13:08 -0500 -Subject: [PATCH 250/325] tpm_tis: fix stall after iowrite*()s -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 250/327] tpm_tis: fix stall after iowrite*()s +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz ioread8() operations to TPM MMIO addresses can stall the cpu when immediately following a sequence of iowrite*()'s to the same region. @@ -80,5 +83,5 @@ index f08949a5f678..9fefcfcae593 100644 return 0; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0251-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch b/debian/patches-rt/0251-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch index f9947ff3f..021779475 100644 --- a/debian/patches-rt/0251-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch +++ b/debian/patches-rt/0251-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch @@ -1,8 +1,11 @@ -From fb131ef07b6163f19997356ad5267dc46fbe0514 Mon Sep 17 00:00:00 2001 +From e36a324a0736f2cba48a43c5b326be8ec4de7062 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 -Subject: [PATCH 251/325] watchdog: prevent deferral of watchdogd wakeup on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 251/327] watchdog: prevent deferral of watchdogd wakeup on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz When PREEMPT_RT_FULL is enabled, all hrtimer expiry functions are deferred for execution into the context of ktimersoftd unless otherwise @@ -37,7 +40,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/watchdog/watchdog_dev.c b/drivers/watchdog/watchdog_dev.c -index e64aa88e99da..11ba2c3b187f 100644 +index 10b2090f3e5e..c04384aa94a5 100644 --- a/drivers/watchdog/watchdog_dev.c +++ b/drivers/watchdog/watchdog_dev.c @@ -145,7 +145,7 @@ static inline void watchdog_update_worker(struct watchdog_device *wdd) @@ -58,7 +61,7 @@ index e64aa88e99da..11ba2c3b187f 100644 return 0; } -@@ -947,7 +947,7 @@ static int watchdog_cdev_register(struct watchdog_device *wdd) +@@ -948,7 +948,7 @@ static int watchdog_cdev_register(struct watchdog_device *wdd) return -ENODEV; kthread_init_work(&wd_data->work, watchdog_ping_work); @@ -67,7 +70,7 @@ index e64aa88e99da..11ba2c3b187f 100644 wd_data->timer.function = watchdog_timer_expired; if (wdd->id == 0) { -@@ -1004,7 +1004,7 @@ static int watchdog_cdev_register(struct watchdog_device *wdd) +@@ -1005,7 +1005,7 @@ static int watchdog_cdev_register(struct watchdog_device *wdd) __module_get(wdd->ops->owner); get_device(&wd_data->dev); if (handle_boot_enabled) @@ -77,5 +80,5 @@ index e64aa88e99da..11ba2c3b187f 100644 pr_info("watchdog%d running and kernel based pre-userspace handler disabled\n", wdd->id); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0252-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch b/debian/patches-rt/0252-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch index 2a8294928..80e21eefa 100644 --- a/debian/patches-rt/0252-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch +++ b/debian/patches-rt/0252-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch @@ -1,9 +1,12 @@ -From fa2aaf043441bd422f017ee044eec3e113cc18b9 Mon Sep 17 00:00:00 2001 +From 2b8d0867028ebb2c534fc4736255a317a2f01c61 Mon Sep 17 00:00:00 2001 +Message-Id: <2b8d0867028ebb2c534fc4736255a317a2f01c61.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 08:09:11 +0100 -Subject: [PATCH 252/325] drm,radeon,i915: Use preempt_disable/enable_rt() +Subject: [PATCH 252/327] drm,radeon,i915: Use preempt_disable/enable_rt() where recommended -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz DRM folks identified the spots, so use them. @@ -57,5 +60,5 @@ index 7d1e14f0140a..bcc3456749d6 100644 /* Decode into vertical and horizontal scanout position. */ *vpos = position & 0x1fff; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0253-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch b/debian/patches-rt/0253-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch index 45c48e14d..3b17da8e0 100644 --- a/debian/patches-rt/0253-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch +++ b/debian/patches-rt/0253-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch @@ -1,9 +1,12 @@ -From c034b59f5f74a92a5f458798943b0d403ec9b6fb Mon Sep 17 00:00:00 2001 +From 710ddc2503ed051fa5343c1eb5b950444b05147b Mon Sep 17 00:00:00 2001 +Message-Id: <710ddc2503ed051fa5343c1eb5b950444b05147b.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 09:01:42 +0100 -Subject: [PATCH 253/325] drm,i915: Use local_lock/unlock_irq() in +Subject: [PATCH 253/327] drm,i915: Use local_lock/unlock_irq() in intel_pipe_update_start/end() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ 8.014039] BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:918 [ 8.014041] in_atomic(): 0, irqs_disabled(): 1, pid: 78, name: kworker/u4:4 @@ -124,5 +127,5 @@ index f7026e887fa9..07e4ddebdd80 100644 if (intel_vgpu_active(dev_priv)) return; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0254-drm-i915-disable-tracing-on-RT.patch b/debian/patches-rt/0254-drm-i915-disable-tracing-on-RT.patch index e632caa7e..9df05c587 100644 --- a/debian/patches-rt/0254-drm-i915-disable-tracing-on-RT.patch +++ b/debian/patches-rt/0254-drm-i915-disable-tracing-on-RT.patch @@ -1,8 +1,11 @@ -From b1e8ce0ff9f46bde59b57c93c8ead49803e285b6 Mon Sep 17 00:00:00 2001 +From 7ed8d38963d1fa985cd15013ed057b4fee4df002 Mon Sep 17 00:00:00 2001 +Message-Id: <7ed8d38963d1fa985cd15013ed057b4fee4df002.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 09:52:20 +0100 -Subject: [PATCH 254/325] drm/i915: disable tracing on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 254/327] drm/i915: disable tracing on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Luca Abeni reported this: | BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003 @@ -43,5 +46,5 @@ index b50c6b829715..cc54ec0ef75c 100644 #include #include -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0255-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch b/debian/patches-rt/0255-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch index 0aecef1c4..e23e32130 100644 --- a/debian/patches-rt/0255-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch +++ b/debian/patches-rt/0255-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch @@ -1,9 +1,12 @@ -From bca71bc9e1a90a3042f05c97da73dfb6320032d6 Mon Sep 17 00:00:00 2001 +From 5ec5b253489612a052795fbf5439c2a00f146c67 Mon Sep 17 00:00:00 2001 +Message-Id: <5ec5b253489612a052795fbf5439c2a00f146c67.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 19 Dec 2018 10:47:02 +0100 -Subject: [PATCH 255/325] drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with +Subject: [PATCH 255/327] drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with NOTRACE -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The order of the header files is important. If this header file is included after tracepoint.h was included then the NOTRACE here becomes a @@ -29,5 +32,5 @@ index cc54ec0ef75c..33028d8f470e 100644 TP_PROTO(struct i915_request *rq), TP_ARGS(rq) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0256-cgroups-use-simple-wait-in-css_release.patch b/debian/patches-rt/0256-cgroups-use-simple-wait-in-css_release.patch index 964521092..9545485a6 100644 --- a/debian/patches-rt/0256-cgroups-use-simple-wait-in-css_release.patch +++ b/debian/patches-rt/0256-cgroups-use-simple-wait-in-css_release.patch @@ -1,8 +1,11 @@ -From 299712e35cd293828bfac75868a4306a17ac365d Mon Sep 17 00:00:00 2001 +From 23f06bf7e786602ab35b4abed68bbe45bec93200 Mon Sep 17 00:00:00 2001 +Message-Id: <23f06bf7e786602ab35b4abed68bbe45bec93200.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 13 Feb 2015 15:52:24 +0100 -Subject: [PATCH 256/325] cgroups: use simple wait in css_release() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 256/327] cgroups: use simple wait in css_release() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz To avoid: |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914 @@ -91,5 +94,5 @@ index 877ba6dacca8..97ff80283248 100644 } core_initcall(cgroup_wq_init); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0257-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0257-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch index 5bb45e41b..0e3e6640e 100644 --- a/debian/patches-rt/0257-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0257-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch @@ -1,8 +1,11 @@ -From fc0fb050aa602ebda16444e1860d24f585ccb2e9 Mon Sep 17 00:00:00 2001 +From c3933176cb4bcaa676a0743119c434f03f4690f8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 8 Jan 2017 09:32:25 +0100 -Subject: [PATCH 257/325] cpuset: Convert callback_lock to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 257/327] cpuset: Convert callback_lock to raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The two commits below add up to a cpuset might_sleep() splat for RT: @@ -289,5 +292,5 @@ index 7bb129c5b412..92575cb9b493 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0258-apparmor-use-a-locallock-instead-preempt_disable.patch b/debian/patches-rt/0258-apparmor-use-a-locallock-instead-preempt_disable.patch index 738418766..aa5340c96 100644 --- a/debian/patches-rt/0258-apparmor-use-a-locallock-instead-preempt_disable.patch +++ b/debian/patches-rt/0258-apparmor-use-a-locallock-instead-preempt_disable.patch @@ -1,8 +1,11 @@ -From 59bd47021b903cbbfbead935035e188e9bf01ef4 Mon Sep 17 00:00:00 2001 +From e7e3512033bbed59bdf83b068c3dd4673a706a5b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 11 Oct 2017 17:43:49 +0200 -Subject: [PATCH 258/325] apparmor: use a locallock instead preempt_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 258/327] apparmor: use a locallock instead preempt_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz get_buffers() disables preemption which acts as a lock for the per-CPU variable. Since we can't disable preemption here on RT, a local_lock is @@ -81,5 +84,5 @@ index 730de4638b4e..edc911ff6a4d 100644 /* * LSM hook functions -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0259-workqueue-Prevent-deadlock-stall-on-RT.patch b/debian/patches-rt/0259-workqueue-Prevent-deadlock-stall-on-RT.patch index 9a0133bcc..f5624b7f4 100644 --- a/debian/patches-rt/0259-workqueue-Prevent-deadlock-stall-on-RT.patch +++ b/debian/patches-rt/0259-workqueue-Prevent-deadlock-stall-on-RT.patch @@ -1,8 +1,11 @@ -From 2d869f40619ff62322b415c543fcb325846fe261 Mon Sep 17 00:00:00 2001 +From aca8bffd46f70f5caad69fc3ba1b7b4875ca4ac0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 27 Jun 2014 16:24:52 +0200 -Subject: [PATCH 259/325] workqueue: Prevent deadlock/stall on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 259/327] workqueue: Prevent deadlock/stall on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Austin reported a XFS deadlock/stall on RT where scheduled work gets never exececuted and tasks are waiting for each other for ever. @@ -203,5 +206,5 @@ index 77ae44a1a9ee..9c10264d2679 100644 wake_up_process(worker->task); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0260-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch b/debian/patches-rt/0260-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch index 3e6e803e3..cbaade945 100644 --- a/debian/patches-rt/0260-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch +++ b/debian/patches-rt/0260-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch @@ -1,8 +1,11 @@ -From 1bbb897c03f7cb3649001d6235621c4097871d52 Mon Sep 17 00:00:00 2001 +From 8f3b2b722f4a5d076cd798d0adffa16bfd554e48 Mon Sep 17 00:00:00 2001 +Message-Id: <8f3b2b722f4a5d076cd798d0adffa16bfd554e48.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:56 -0500 -Subject: [PATCH 260/325] signals: Allow rt tasks to cache one sigqueue struct -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 260/327] signals: Allow rt tasks to cache one sigqueue struct +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz To avoid allocation allow rt tasks to cache one sigqueue struct in task struct. @@ -17,7 +20,7 @@ Signed-off-by: Thomas Gleixner 5 files changed, 70 insertions(+), 5 deletions(-) diff --git a/include/linux/sched.h b/include/linux/sched.h -index a8ebd49c4f96..854a6cb456af 100644 +index 852b1221cd40..bdae37091808 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -895,6 +895,8 @@ struct task_struct { @@ -67,7 +70,7 @@ index ecec0f8bef7e..234e0ca9a74b 100644 p->utime = p->stime = p->gtime = 0; #ifdef CONFIG_ARCH_HAS_SCALED_CPUTIME diff --git a/kernel/signal.c b/kernel/signal.c -index d1fa3c405784..5c04f2891487 100644 +index 6f7191a72103..45748993f777 100644 --- a/kernel/signal.c +++ b/kernel/signal.c @@ -19,6 +19,7 @@ @@ -209,5 +212,5 @@ index d1fa3c405784..5c04f2891487 100644 if (q) q->flags |= SIGQUEUE_PREALLOC; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0261-Add-localversion-for-RT-release.patch b/debian/patches-rt/0261-Add-localversion-for-RT-release.patch index bd5275339..310b4ef8a 100644 --- a/debian/patches-rt/0261-Add-localversion-for-RT-release.patch +++ b/debian/patches-rt/0261-Add-localversion-for-RT-release.patch @@ -1,8 +1,11 @@ -From 1bda071743a7670613cfe289a43ac9db4d6648cc Mon Sep 17 00:00:00 2001 +From c530fcb23cfbb541c2ab38fd262d1be8a787f43c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 20:25:16 +0200 -Subject: [PATCH 261/325] Add localversion for -RT release -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 261/327] Add localversion for -RT release +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Signed-off-by: Thomas Gleixner --- @@ -18,5 +21,5 @@ index 000000000000..1199ebade17b @@ -0,0 +1 @@ +-rt16 -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0262-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch b/debian/patches-rt/0262-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch index 4861f9943..5136768a6 100644 --- a/debian/patches-rt/0262-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch +++ b/debian/patches-rt/0262-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch @@ -1,9 +1,12 @@ -From 1038e9afab3fe09ade4404d6185b1ab081594593 Mon Sep 17 00:00:00 2001 +From 476cebd9d429366f7296fa1dad5d963b3ac7b77a Mon Sep 17 00:00:00 2001 +Message-Id: <476cebd9d429366f7296fa1dad5d963b3ac7b77a.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Mar 2019 18:31:54 +0100 -Subject: [PATCH 262/325] powerpc/pseries/iommu: Use a locallock instead +Subject: [PATCH 262/327] powerpc/pseries/iommu: Use a locallock instead local_irq_save() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The locallock protects the per-CPU variable tce_page. The function attempts to allocate memory while tce_page is protected (by disabling @@ -93,5 +96,5 @@ index b1a08cb760e0..8ef818ad83ec 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0263-powerpc-reshuffle-TIF-bits.patch b/debian/patches-rt/0263-powerpc-reshuffle-TIF-bits.patch index 858ba7cfb..36c32b836 100644 --- a/debian/patches-rt/0263-powerpc-reshuffle-TIF-bits.patch +++ b/debian/patches-rt/0263-powerpc-reshuffle-TIF-bits.patch @@ -1,8 +1,11 @@ -From 88b8c212455534d5cda58f57dd35faa8ce864011 Mon Sep 17 00:00:00 2001 +From 0db09cfa3e5a8117220a0353a02aa10fb4924373 Mon Sep 17 00:00:00 2001 +Message-Id: <0db09cfa3e5a8117220a0353a02aa10fb4924373.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 22 Mar 2019 17:15:58 +0100 -Subject: [PATCH 263/325] powerpc: reshuffle TIF bits -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 263/327] powerpc: reshuffle TIF bits +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Powerpc32/64 does not compile because TIF_SYSCALL_TRACE's bit is higher than 15 and the assembly instructions don't expect that. @@ -148,5 +151,5 @@ index ef02e41d5d96..229cdb04e9b0 100644 3: ldarx r10,0,r12 andc r10,r10,r11 -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0264-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0264-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch index 0a4243b50..8848a03da 100644 --- a/debian/patches-rt/0264-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0264-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch @@ -1,8 +1,11 @@ -From 11cc64f8488856ca21bd2ce62502060ffc5cea52 Mon Sep 17 00:00:00 2001 +From f5c9f0a7737b549b4e439ed591eb7ac113c8b575 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 13 Mar 2019 11:40:34 +0000 -Subject: [PATCH 264/325] tty/sysrq: Convert show_lock to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 264/327] tty/sysrq: Convert show_lock to raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Systems which don't provide arch_trigger_cpumask_backtrace() will invoke showacpu() from a smp_call_function() function which is invoked @@ -59,5 +62,5 @@ index cee0274806c5..f785ca55fb85 100644 static void sysrq_showregs_othercpus(struct work_struct *dummy) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0265-drm-i915-Don-t-disable-interrupts-independently-of-t.patch b/debian/patches-rt/0265-drm-i915-Don-t-disable-interrupts-independently-of-t.patch index d0348d75d..cc0b3dd75 100644 --- a/debian/patches-rt/0265-drm-i915-Don-t-disable-interrupts-independently-of-t.patch +++ b/debian/patches-rt/0265-drm-i915-Don-t-disable-interrupts-independently-of-t.patch @@ -1,9 +1,12 @@ -From 0a78b08d39369e6a8d6092e1e5f1fdb7baf61dbc Mon Sep 17 00:00:00 2001 +From 4b720165d0e03ea4eaf4e00dbf1954384e2a09de Mon Sep 17 00:00:00 2001 +Message-Id: <4b720165d0e03ea4eaf4e00dbf1954384e2a09de.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 10 Apr 2019 11:01:37 +0200 -Subject: [PATCH 265/325] drm/i915: Don't disable interrupts independently of +Subject: [PATCH 265/327] drm/i915: Don't disable interrupts independently of the lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz The locks (timeline->lock and rq->lock) need to be taken with disabled interrupts. This is done in __retire_engine_request() by disabling the @@ -47,5 +50,5 @@ index 5c2c93cbab12..7124510b9131 100644 /* * The backing object for the context is done after switching to the -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0266-sched-completion-Fix-a-lockup-in-wait_for_completion.patch b/debian/patches-rt/0266-sched-completion-Fix-a-lockup-in-wait_for_completion.patch index f53718ca0..02af5a75c 100644 --- a/debian/patches-rt/0266-sched-completion-Fix-a-lockup-in-wait_for_completion.patch +++ b/debian/patches-rt/0266-sched-completion-Fix-a-lockup-in-wait_for_completion.patch @@ -1,9 +1,12 @@ -From 03e061f70cacf8cd22a7d1bc073f9b70e5b85c71 Mon Sep 17 00:00:00 2001 +From bf17ec3875abb55507d2cb7595df233a25c80199 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Corey Minyard Date: Thu, 9 May 2019 14:33:20 -0500 -Subject: [PATCH 266/325] sched/completion: Fix a lockup in +Subject: [PATCH 266/327] sched/completion: Fix a lockup in wait_for_completion() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Consider following race: @@ -65,5 +68,5 @@ index 755a58084978..49c14137988e 100644 raw_spin_unlock_irq(&x->wait.lock); timeout = action(timeout); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0267-kthread-add-a-global-worker-thread.patch b/debian/patches-rt/0267-kthread-add-a-global-worker-thread.patch index 9bdc9cea9..99f096160 100644 --- a/debian/patches-rt/0267-kthread-add-a-global-worker-thread.patch +++ b/debian/patches-rt/0267-kthread-add-a-global-worker-thread.patch @@ -1,8 +1,11 @@ -From a344e1caa7443342c35e83701b2e1abb3124bb99 Mon Sep 17 00:00:00 2001 +From a0ea89698f63ecdd3c04325e9fa053e607bd1c3d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 12 Feb 2019 15:09:38 +0100 -Subject: [PATCH 267/325] kthread: add a global worker thread. -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 267/327] kthread: add a global worker thread. +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 0532e87d9d44795221aa921ba7024bde689cc894 ] @@ -29,7 +32,7 @@ Signed-off-by: Steven Rostedt (VMware) create mode 100644 include/linux/kthread-cgroup.h diff --git a/drivers/block/loop.c b/drivers/block/loop.c -index 9cd231a27328..351ea22ffb56 100644 +index c1341c86bcde..aee44299bd07 100644 --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -70,7 +70,7 @@ @@ -176,5 +179,5 @@ index 5641b55783a6..9db017761a1f 100644 /** * kthread_associate_blkcg - associate blkcg to current kthread -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0268-arm-imx6-cpuidle-Use-raw_spinlock_t.patch b/debian/patches-rt/0268-arm-imx6-cpuidle-Use-raw_spinlock_t.patch index 2b86a1860..80c19e0d2 100644 --- a/debian/patches-rt/0268-arm-imx6-cpuidle-Use-raw_spinlock_t.patch +++ b/debian/patches-rt/0268-arm-imx6-cpuidle-Use-raw_spinlock_t.patch @@ -1,8 +1,11 @@ -From cbc9d01e75de1a578f850190725900af27d430c6 Mon Sep 17 00:00:00 2001 +From f784856a817d703029f506a9546b4b7c4980b240 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 May 2019 17:07:44 +0200 -Subject: [PATCH 268/325] arm: imx6: cpuidle: Use raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 268/327] arm: imx6: cpuidle: Use raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 40d0332ec8312e9c090f0a5414d9c90e12b13611 ] @@ -48,5 +51,5 @@ index 326e870d7123..d9ac80aa1eb0 100644 return index; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0269-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch b/debian/patches-rt/0269-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch index f60788faa..57ed58fbe 100644 --- a/debian/patches-rt/0269-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch +++ b/debian/patches-rt/0269-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch @@ -1,9 +1,12 @@ -From 29483b5cb7e491f38927246ae4b2838bc300f5e8 Mon Sep 17 00:00:00 2001 +From 80fc81c734ab88f202dc415ce5b301276f184f8e Mon Sep 17 00:00:00 2001 +Message-Id: <80fc81c734ab88f202dc415ce5b301276f184f8e.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 18:29:13 +0200 -Subject: [PATCH 269/325] rcu: Don't allow to change rcu_normal_after_boot on +Subject: [PATCH 269/327] rcu: Don't allow to change rcu_normal_after_boot on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit c6c058c10577815a2491ce661876cff00a4c3b15 ] @@ -32,5 +35,5 @@ index 16d8dba23329..ed75addd3ccd 100644 #ifdef CONFIG_DEBUG_LOCK_ALLOC -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0270-pci-switchtec-fix-stream_open.cocci-warnings.patch b/debian/patches-rt/0270-pci-switchtec-fix-stream_open.cocci-warnings.patch index edbd8f9a8..c938bffa3 100644 --- a/debian/patches-rt/0270-pci-switchtec-fix-stream_open.cocci-warnings.patch +++ b/debian/patches-rt/0270-pci-switchtec-fix-stream_open.cocci-warnings.patch @@ -1,8 +1,11 @@ -From 6566c0af08d10f160b57f889133e227a9334f9d4 Mon Sep 17 00:00:00 2001 +From 2899a2c8b2ad6c1ced301bed400ec6286aff59ec Mon Sep 17 00:00:00 2001 +Message-Id: <2899a2c8b2ad6c1ced301bed400ec6286aff59ec.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: kbuild test robot Date: Sat, 13 Apr 2019 11:22:51 +0800 -Subject: [PATCH 270/325] pci/switchtec: fix stream_open.cocci warnings -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 270/327] pci/switchtec: fix stream_open.cocci warnings +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 9462c69e29307adc95c289f50839d5d683973891 ] @@ -36,5 +39,5 @@ index a8df847bedee..25d1f96cddc1 100644 dev_dbg(&stdev->dev, "%s: %p\n", __func__, stuser); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0271-sched-core-Drop-a-preempt_disable_rt-statement.patch b/debian/patches-rt/0271-sched-core-Drop-a-preempt_disable_rt-statement.patch index e7b8a1580..669d0a5f2 100644 --- a/debian/patches-rt/0271-sched-core-Drop-a-preempt_disable_rt-statement.patch +++ b/debian/patches-rt/0271-sched-core-Drop-a-preempt_disable_rt-statement.patch @@ -1,8 +1,11 @@ -From f0b092a791f59beb56cf987be5fbe18bb68df764 Mon Sep 17 00:00:00 2001 +From 5249a037647b59d7001625081ec239e472eeadc2 Mon Sep 17 00:00:00 2001 +Message-Id: <5249a037647b59d7001625081ec239e472eeadc2.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:33:16 +0200 -Subject: [PATCH 271/325] sched/core: Drop a preempt_disable_rt() statement -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 271/327] sched/core: Drop a preempt_disable_rt() statement +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 761126efdcbe3fa3e99c9079fa0ad6eca2f251f2 ] @@ -46,5 +49,5 @@ index cfde725e1017..678c2c4de4f5 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0272-timers-Redo-the-notification-of-canceling-timers-on-.patch b/debian/patches-rt/0272-timers-Redo-the-notification-of-canceling-timers-on-.patch index 0ea8b1cd8..a09b0b91b 100644 --- a/debian/patches-rt/0272-timers-Redo-the-notification-of-canceling-timers-on-.patch +++ b/debian/patches-rt/0272-timers-Redo-the-notification-of-canceling-timers-on-.patch @@ -1,9 +1,12 @@ -From 97fc8e3efcfeae8f91109c03a560a35a2f560985 Mon Sep 17 00:00:00 2001 +From dd509894c7509d682f0aab3909d55ee6c32084e5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:39:06 +0200 -Subject: [PATCH 272/325] timers: Redo the notification of canceling timers on +Subject: [PATCH 272/327] timers: Redo the notification of canceling timers on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit c71273154c2ad12e13333aada340ff30e826a11b ] @@ -646,5 +649,5 @@ index 2fcd56aa6092..1c67aab34ff5 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0273-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch b/debian/patches-rt/0273-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch index a925ef247..ceb59cabf 100644 --- a/debian/patches-rt/0273-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch +++ b/debian/patches-rt/0273-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch @@ -1,9 +1,12 @@ -From e1744f07e1c8a1ac358a3488d40bfc17164dc397 Mon Sep 17 00:00:00 2001 +From fd5dcc82e6e272600097d6ae911aaf6890beb58b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:13 +0200 -Subject: [PATCH 273/325] Revert "futex: Ensure lock/unlock symetry versus +Subject: [PATCH 273/327] Revert "futex: Ensure lock/unlock symetry versus pi_lock and hash bucket lock" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 6a773b70cf105b46298ed3b44e77c102ce31d9ec ] @@ -31,5 +34,5 @@ index 084527af43d4..b99266393c52 100644 continue; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0274-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch b/debian/patches-rt/0274-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch index 793aa67b5..4dd12d8f6 100644 --- a/debian/patches-rt/0274-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch +++ b/debian/patches-rt/0274-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch @@ -1,9 +1,12 @@ -From ce2eb15023161fb6b08da540631b9245997a35ca Mon Sep 17 00:00:00 2001 +From f5552be3656c38e090fe9e94f8d60d42a542a6f7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:18 +0200 -Subject: [PATCH 274/325] Revert "futex: Fix bug on when a requeued RT task +Subject: [PATCH 274/327] Revert "futex: Fix bug on when a requeued RT task times out" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit f1a170cb3289a48df26cae3c60d77608f7a988bb ] @@ -79,5 +82,5 @@ index 546aaf058b9e..a501f3b47081 100644 extern struct task_struct *rt_mutex_next_owner(struct rt_mutex *lock); extern void rt_mutex_init_proxy_locked(struct rt_mutex *lock, -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0275-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch b/debian/patches-rt/0275-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch index a42422c66..76eb3b45f 100644 --- a/debian/patches-rt/0275-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch +++ b/debian/patches-rt/0275-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch @@ -1,9 +1,12 @@ -From 239b06f7ca78e179c96acf891fd3ab78b534f44e Mon Sep 17 00:00:00 2001 +From 1896d1cae8fe2408ea75067287741090d16b85db Mon Sep 17 00:00:00 2001 +Message-Id: <1896d1cae8fe2408ea75067287741090d16b85db.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:21 +0200 -Subject: [PATCH 275/325] Revert "rtmutex: Handle the various new futex race +Subject: [PATCH 275/327] Revert "rtmutex: Handle the various new futex race conditions" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 9e0265c21af4d6388d47dcd5ce20f76ec3a2e468 ] @@ -254,5 +257,5 @@ index a501f3b47081..758dc43872e5 100644 extern void rt_mutex_init_proxy_locked(struct rt_mutex *lock, struct task_struct *proxy_owner); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0276-Revert-futex-workaround-migrate_disable-enable-in-di.patch b/debian/patches-rt/0276-Revert-futex-workaround-migrate_disable-enable-in-di.patch index 65cfae756..9f0853541 100644 --- a/debian/patches-rt/0276-Revert-futex-workaround-migrate_disable-enable-in-di.patch +++ b/debian/patches-rt/0276-Revert-futex-workaround-migrate_disable-enable-in-di.patch @@ -1,9 +1,12 @@ -From 8e9071d524a0b1b0539aba8b3e2e30cba6871be3 Mon Sep 17 00:00:00 2001 +From 9677a2e0da781ad1cfa98e0cd02f4f81fc15086c Mon Sep 17 00:00:00 2001 +Message-Id: <9677a2e0da781ad1cfa98e0cd02f4f81fc15086c.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:27 +0200 -Subject: [PATCH 276/325] Revert "futex: workaround migrate_disable/enable in +Subject: [PATCH 276/327] Revert "futex: workaround migrate_disable/enable in different context" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit a71221d81cc4873891ae44f3aa02df596079b786 ] @@ -66,5 +69,5 @@ index 1f9dd186b00c..9900c3f30124 100644 /* -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0277-futex-Make-the-futex_hash_bucket-lock-raw.patch b/debian/patches-rt/0277-futex-Make-the-futex_hash_bucket-lock-raw.patch index 17f09c5f1..2628eff8d 100644 --- a/debian/patches-rt/0277-futex-Make-the-futex_hash_bucket-lock-raw.patch +++ b/debian/patches-rt/0277-futex-Make-the-futex_hash_bucket-lock-raw.patch @@ -1,8 +1,11 @@ -From 4da5579cff42dcfc92f67bdcff08cdb3c440178b Mon Sep 17 00:00:00 2001 +From 4dc70d7b78801ad210c7e585d1895ee5651f3b0e Mon Sep 17 00:00:00 2001 +Message-Id: <4dc70d7b78801ad210c7e585d1895ee5651f3b0e.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 11:59:44 +0200 -Subject: [PATCH 277/325] futex: Make the futex_hash_bucket lock raw -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 277/327] futex: Make the futex_hash_bucket lock raw +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit f646521aadedab78801c9befe193e2e8a0c99298 ] @@ -345,5 +348,5 @@ index 9900c3f30124..8e8658df69d9 100644 return 0; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0278-futex-Delay-deallocation-of-pi_state.patch b/debian/patches-rt/0278-futex-Delay-deallocation-of-pi_state.patch index 174aaa572..9da2b1dcf 100644 --- a/debian/patches-rt/0278-futex-Delay-deallocation-of-pi_state.patch +++ b/debian/patches-rt/0278-futex-Delay-deallocation-of-pi_state.patch @@ -1,8 +1,11 @@ -From e66a69b90bc31990bfb8bff7b02090e7664cf97b Mon Sep 17 00:00:00 2001 +From 0538c9acfdb919e72b2fd2660cee77b589bcc18b Mon Sep 17 00:00:00 2001 +Message-Id: <0538c9acfdb919e72b2fd2660cee77b589bcc18b.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Jun 2019 13:35:36 +0200 -Subject: [PATCH 278/325] futex: Delay deallocation of pi_state -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 278/327] futex: Delay deallocation of pi_state +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit d7c7cf8cb68b7df17e6e50be1f25f35d83e686c7 ] @@ -179,5 +182,5 @@ index 8e8658df69d9..3c604e3eb20a 100644 } else { struct rt_mutex *pi_mutex; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0279-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch b/debian/patches-rt/0279-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch index 268d7d7d7..a7df49f62 100644 --- a/debian/patches-rt/0279-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch +++ b/debian/patches-rt/0279-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch @@ -1,9 +1,12 @@ -From 46c3a76e3d5c44d8f02e3aa42b0a8c34aae326a1 Mon Sep 17 00:00:00 2001 +From 3d2c756141f1e830f68fe6b8aa27ba395f72c02f Mon Sep 17 00:00:00 2001 +Message-Id: <3d2c756141f1e830f68fe6b8aa27ba395f72c02f.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Luis Claudio R. Goncalves" Date: Tue, 25 Jun 2019 11:28:04 -0300 -Subject: [PATCH 279/325] mm/zswap: Do not disable preemption in +Subject: [PATCH 279/327] mm/zswap: Do not disable preemption in zswap_frontswap_store() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 4e4cf4be79635e67144632d9135286381acbc95a ] @@ -123,5 +126,5 @@ index cd91fd9d96b8..420225d3ff0b 100644 freepage: zswap_entry_cache_free(entry); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0280-revert-aio.patch b/debian/patches-rt/0280-revert-aio.patch index 3cb1b4e4c..3cb973809 100644 --- a/debian/patches-rt/0280-revert-aio.patch +++ b/debian/patches-rt/0280-revert-aio.patch @@ -1,8 +1,11 @@ -From 7a9d62da76af5ba2a2a0002d4955115fa7e2c018 Mon Sep 17 00:00:00 2001 +From 4bad7a9c1c1747bf47f5ef2a0d9e73ec114345bc Mon Sep 17 00:00:00 2001 +Message-Id: <4bad7a9c1c1747bf47f5ef2a0d9e73ec114345bc.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 -Subject: [PATCH 280/325] revert-aio -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 280/327] revert-aio +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz revert: fs/aio: simple simple work @@ -67,5 +70,5 @@ index 93f8cf7fdeab..b5fbf2061868 100644 { unsigned i, new_nr; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0281-fs-aio-simple-simple-work.patch b/debian/patches-rt/0281-fs-aio-simple-simple-work.patch index c5389ab3a..f8d83d16f 100644 --- a/debian/patches-rt/0281-fs-aio-simple-simple-work.patch +++ b/debian/patches-rt/0281-fs-aio-simple-simple-work.patch @@ -1,8 +1,11 @@ -From 4bb78531ae9d77ab3d0b681c733db6e53eb754a4 Mon Sep 17 00:00:00 2001 +From 1cc75eebd2107911c948e07f921dc73befb80609 Mon Sep 17 00:00:00 2001 +Message-Id: <1cc75eebd2107911c948e07f921dc73befb80609.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 -Subject: [PATCH 281/325] fs/aio: simple simple work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 281/327] fs/aio: simple simple work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 1a142116f6435ef070ecebb66d2d599507c10601 ] @@ -72,5 +75,5 @@ index b5fbf2061868..a92119e05869 100644 { unsigned i, new_nr; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0282-revert-thermal.patch b/debian/patches-rt/0282-revert-thermal.patch index 6ec050aa8..917e755b9 100644 --- a/debian/patches-rt/0282-revert-thermal.patch +++ b/debian/patches-rt/0282-revert-thermal.patch @@ -1,8 +1,11 @@ -From 267418caf8f37f685310bb311fe5fa28e3e25dfe Mon Sep 17 00:00:00 2001 +From c3c4fea752b256b173678612d1c848bd76710d25 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 -Subject: [PATCH 282/325] revert-thermal -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 282/327] revert-thermal +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Revert: thermal: Defer thermal wakups to threads @@ -116,5 +119,5 @@ index a5991cbb408f..1ef937d799e4 100644 module_exit(pkg_temp_thermal_exit) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0283-thermal-Defer-thermal-wakups-to-threads.patch b/debian/patches-rt/0283-thermal-Defer-thermal-wakups-to-threads.patch index d7e338d96..b53b9afc0 100644 --- a/debian/patches-rt/0283-thermal-Defer-thermal-wakups-to-threads.patch +++ b/debian/patches-rt/0283-thermal-Defer-thermal-wakups-to-threads.patch @@ -1,8 +1,11 @@ -From bba3e5357a4fc4ecfbee11c3bd4d20f790ef81f3 Mon Sep 17 00:00:00 2001 +From b572ed9793f7a54696726f5b9d38a977900ac0c9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 -Subject: [PATCH 283/325] thermal: Defer thermal wakups to threads -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 283/327] thermal: Defer thermal wakups to threads +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit ad2408dc248fe58536eef5b2b5734d8f9d3a280b ] @@ -94,5 +97,5 @@ index 1ef937d799e4..82f21fd4afb0 100644 kfree(packages); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0284-revert-block.patch b/debian/patches-rt/0284-revert-block.patch index 15518f752..261741b0e 100644 --- a/debian/patches-rt/0284-revert-block.patch +++ b/debian/patches-rt/0284-revert-block.patch @@ -1,8 +1,11 @@ -From 171ac6b8fbc78b0623d086b254df171edb190cbe Mon Sep 17 00:00:00 2001 +From ef5a3ea0768019ea8fe629118a47088f3d650be2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:54 -0400 -Subject: [PATCH 284/325] revert-block -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 284/327] revert-block +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Revert swork version of: block: blk-mq: move blk_queue_usage_counter_release() into process context @@ -59,7 +62,7 @@ index 13bf37156bb0..4860cd26cd5a 100644 sizeof(struct request), 0, SLAB_PANIC, NULL); diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h -index 2f3b2e5196eb..111ab4209797 100644 +index cc446661e51e..7cd627f2a016 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -27,7 +27,6 @@ @@ -79,5 +82,5 @@ index 2f3b2e5196eb..111ab4209797 100644 struct list_head all_q_node; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0285-block-blk-mq-move-blk_queue_usage_counter_release-in.patch b/debian/patches-rt/0285-block-blk-mq-move-blk_queue_usage_counter_release-in.patch index 2d38a8a08..e804c3ad1 100644 --- a/debian/patches-rt/0285-block-blk-mq-move-blk_queue_usage_counter_release-in.patch +++ b/debian/patches-rt/0285-block-blk-mq-move-blk_queue_usage_counter_release-in.patch @@ -1,9 +1,12 @@ -From 4621d1e6d5d9c259cd3fc808ea502b2fdaf859f6 Mon Sep 17 00:00:00 2001 +From 95afd918acf568a8a130cf4eb9c32fa3aaafaf0b Mon Sep 17 00:00:00 2001 +Message-Id: <95afd918acf568a8a130cf4eb9c32fa3aaafaf0b.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 -Subject: [PATCH 285/325] block: blk-mq: move blk_queue_usage_counter_release() +Subject: [PATCH 285/327] block: blk-mq: move blk_queue_usage_counter_release() into process context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 61c928ecf4fe200bda9b49a0813b5ba0f43995b5 ] @@ -90,7 +93,7 @@ index 4860cd26cd5a..7d709465876e 100644 /* * Init percpu_ref in atomic mode so that it's faster to shutdown. diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h -index 111ab4209797..981103415cd8 100644 +index 7cd627f2a016..066b59dc380f 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -13,6 +13,7 @@ @@ -110,5 +113,5 @@ index 111ab4209797..981103415cd8 100644 struct list_head all_q_node; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0286-workqueue-rework.patch b/debian/patches-rt/0286-workqueue-rework.patch index 1c78b445a..c72ba2097 100644 --- a/debian/patches-rt/0286-workqueue-rework.patch +++ b/debian/patches-rt/0286-workqueue-rework.patch @@ -1,8 +1,11 @@ -From 9fff0e73dcf79af1aab70aae151379fe86845cff Mon Sep 17 00:00:00 2001 +From 4d2d7e60f7fcf4dbf22b7e125f8633c8d5901fae Mon Sep 17 00:00:00 2001 +Message-Id: <4d2d7e60f7fcf4dbf22b7e125f8633c8d5901fae.1588797587.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 May 2019 18:52:27 +0200 -Subject: [PATCH 286/325] workqueue: rework -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 286/327] workqueue: rework +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit d15a862f24df983458533aebd6fa207ecdd1095a ] @@ -66,7 +69,7 @@ index 7d709465876e..752c9e754509 100644 /* * Init percpu_ref in atomic mode so that it's faster to shutdown. diff --git a/drivers/block/loop.c b/drivers/block/loop.c -index 351ea22ffb56..9cd231a27328 100644 +index aee44299bd07..c1341c86bcde 100644 --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -70,7 +70,7 @@ @@ -202,7 +205,7 @@ index 0473efda4c65..da587e60fe86 100644 #include #include diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h -index 981103415cd8..6a0bfa0a2c52 100644 +index 066b59dc380f..59763af05194 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -656,7 +656,7 @@ struct request_queue { @@ -1460,5 +1463,5 @@ index 9c10264d2679..e6a96fe8896b 100644 attrs->no_numa = true; ordered_wq_attrs[i] = attrs; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0287-i2c-exynos5-Remove-IRQF_ONESHOT.patch b/debian/patches-rt/0287-i2c-exynos5-Remove-IRQF_ONESHOT.patch index 6587cba8e..28e1ec9f3 100644 --- a/debian/patches-rt/0287-i2c-exynos5-Remove-IRQF_ONESHOT.patch +++ b/debian/patches-rt/0287-i2c-exynos5-Remove-IRQF_ONESHOT.patch @@ -1,8 +1,11 @@ -From a6f963a5d04359e6b27fc6a6ec9da5754729d0e0 Mon Sep 17 00:00:00 2001 +From 1d1b6053f05dd32a49f9c85fda37e0a60a156c79 Mon Sep 17 00:00:00 2001 +Message-Id: <1d1b6053f05dd32a49f9c85fda37e0a60a156c79.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:12 +0200 -Subject: [PATCH 287/325] i2c: exynos5: Remove IRQF_ONESHOT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 287/327] i2c: exynos5: Remove IRQF_ONESHOT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 4b217df0ab3f7910c96e42091cc7d9f221d05f01 ] @@ -44,5 +47,5 @@ index c1ce2299a76e..5c57ecf4b79e 100644 dev_err(&pdev->dev, "cannot request HS-I2C IRQ %d\n", i2c->irq); goto err_clk; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0288-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch b/debian/patches-rt/0288-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch index 8829b6154..18e9466d5 100644 --- a/debian/patches-rt/0288-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch +++ b/debian/patches-rt/0288-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch @@ -1,8 +1,11 @@ -From 3b4a2b1bd8409f08d5a027e51b14fd5e6eb31708 Mon Sep 17 00:00:00 2001 +From ec731db4eae02d57a8d9b2caaecaf5f37fa7768c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:37 +0200 -Subject: [PATCH 288/325] i2c: hix5hd2: Remove IRQF_ONESHOT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 288/327] i2c: hix5hd2: Remove IRQF_ONESHOT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit e88b481f3f86f11e3243e0808a830e5ca5782a9d ] @@ -38,5 +41,5 @@ index b5ad7696adf9..0f08ef1f7f41 100644 dev_err(&pdev->dev, "cannot request HS-I2C IRQ %d\n", irq); goto err_clk; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0289-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch b/debian/patches-rt/0289-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch index 6f42cb4cc..ee1ff5f43 100644 --- a/debian/patches-rt/0289-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch +++ b/debian/patches-rt/0289-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch @@ -1,9 +1,12 @@ -From 7775d07be42794e09d02410ecec003db98b79c44 Mon Sep 17 00:00:00 2001 +From cc107e8351dec73ed4f52a3e5df1267ce51a04a2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Juri Lelli Date: Wed, 31 Jul 2019 12:37:15 +0200 -Subject: [PATCH 289/325] sched/deadline: Ensure inactive_timer runs in hardirq +Subject: [PATCH 289/327] sched/deadline: Ensure inactive_timer runs in hardirq context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit ba94e7aed7405c58251b1380e6e7d73aa8284b41 ] @@ -46,5 +49,5 @@ index 974a8f9b615a..929167a1d991 100644 } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0290-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch b/debian/patches-rt/0290-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch index 091d31ecb..87bdad615 100644 --- a/debian/patches-rt/0290-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch +++ b/debian/patches-rt/0290-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch @@ -1,9 +1,12 @@ -From 9af59981c8191547bb127a9be2984f0009085b2e Mon Sep 17 00:00:00 2001 +From 1025cefe767bf870e57c02f9907413d04c1b0c5f Mon Sep 17 00:00:00 2001 +Message-Id: <1025cefe767bf870e57c02f9907413d04c1b0c5f.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Clark Williams Date: Mon, 15 Jul 2019 15:25:00 -0500 -Subject: [PATCH 290/325] thermal/x86_pkg_temp: make pkg_temp_lock a raw +Subject: [PATCH 290/327] thermal/x86_pkg_temp: make pkg_temp_lock a raw spinlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 8b03bb3ea7861b70b506199a69b1c8f81fe2d4d0 ] @@ -116,5 +119,5 @@ index 1ef937d799e4..540becb78a0f 100644 /* Final cleanup if this is the last cpu */ if (lastcpu) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0291-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch b/debian/patches-rt/0291-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch index 0acfba85b..7a7de1f40 100644 --- a/debian/patches-rt/0291-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch +++ b/debian/patches-rt/0291-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch @@ -1,8 +1,11 @@ -From fc310572745c255840931c77c058698ed0ee811c Mon Sep 17 00:00:00 2001 +From ace9a654bb67fb7d66327244d09b9668113aa449 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 16:38:43 +0200 -Subject: [PATCH 291/325] dma-buf: Use seqlock_t instread disabling preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 291/327] dma-buf: Use seqlock_t instread disabling preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 240610aa31094f51f299f06eb8dae8d4cd8d4500 ] @@ -292,5 +295,5 @@ index 02166e815afb..0b31df1af698 100644 RCU_INIT_POINTER(obj->fence_excl, NULL); obj->staged = NULL; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0292-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch b/debian/patches-rt/0292-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch index f9ce98627..6ea375e35 100644 --- a/debian/patches-rt/0292-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch +++ b/debian/patches-rt/0292-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch @@ -1,9 +1,12 @@ -From 92af1484300b2fb481fb3cde9f813abebc1b9fd2 Mon Sep 17 00:00:00 2001 +From 19529328ab32e8fb204571c9db204936c151f214 Mon Sep 17 00:00:00 2001 +Message-Id: <19529328ab32e8fb204571c9db204936c151f214.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Aug 2019 14:29:41 +0200 -Subject: [PATCH 292/325] KVM: arm/arm64: Let the timer expire in hardirq +Subject: [PATCH 292/327] KVM: arm/arm64: Let the timer expire in hardirq context on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 719cc080c914045a6e35787bf4dc3ba91cfd3efb ] @@ -50,5 +53,5 @@ index 17cecc96f735..217d39f40393 100644 vtimer->irq.irq = default_vtimer_irq.irq; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0293-x86-preempt-Check-preemption-level-before-looking-at.patch b/debian/patches-rt/0293-x86-preempt-Check-preemption-level-before-looking-at.patch index 9edd25af5..577397ec1 100644 --- a/debian/patches-rt/0293-x86-preempt-Check-preemption-level-before-looking-at.patch +++ b/debian/patches-rt/0293-x86-preempt-Check-preemption-level-before-looking-at.patch @@ -1,9 +1,12 @@ -From b7ae4952818be75c5a6069dd33747475b78ecf6c Mon Sep 17 00:00:00 2001 +From 777c5bbf8cd5ffb6fff8fcc2ce5c919f1c40f765 Mon Sep 17 00:00:00 2001 +Message-Id: <777c5bbf8cd5ffb6fff8fcc2ce5c919f1c40f765.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 17:08:58 +0200 -Subject: [PATCH 293/325] x86: preempt: Check preemption level before looking +Subject: [PATCH 293/327] x86: preempt: Check preemption level before looking at lazy-preempt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 19fc8557f2323c52b26561651ed4d51fc688a740 ] @@ -30,5 +33,5 @@ index f66708779274..afa0e42ccdd1 100644 return false; return test_thread_flag(TIF_NEED_RESCHED_LAZY); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0294-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch b/debian/patches-rt/0294-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch index c1b472cdd..dffb52c6f 100644 --- a/debian/patches-rt/0294-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch +++ b/debian/patches-rt/0294-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch @@ -1,9 +1,12 @@ -From e7c83855d0557c416f5940cc7c57095b166f993f Mon Sep 17 00:00:00 2001 +From fcbf301bbdad4ed46684e9805ad9d6ac5f1ac669 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:07 +0100 -Subject: [PATCH 294/325] hrtimer: Use READ_ONCE to access timer->base in +Subject: [PATCH 294/327] hrtimer: Use READ_ONCE to access timer->base in hrimer_grab_expiry_lock() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 2c8fdbe7ef0ad06c1a326886c5954e117b5657d6 ] @@ -38,5 +41,5 @@ index 94d97eae0a46..d6026c170c2d 100644 if (base && base->cpu_base) { spin_lock(&base->cpu_base->softirq_expiry_lock); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0295-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch b/debian/patches-rt/0295-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch index 61490c32f..75ee23daf 100644 --- a/debian/patches-rt/0295-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch +++ b/debian/patches-rt/0295-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch @@ -1,9 +1,12 @@ -From 37beb738da51dc49fd9ffe9bfa816a6f6429fe45 Mon Sep 17 00:00:00 2001 +From fee308ee0c3ef4d90276bb692a31b3c639f4817f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:08 +0100 -Subject: [PATCH 295/325] hrtimer: Don't grab the expiry lock for non-soft +Subject: [PATCH 295/327] hrtimer: Don't grab the expiry lock for non-soft hrtimer -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit fd420354bea2f57c11f3de191dffdeea76531e76 ] @@ -37,5 +40,5 @@ index d6026c170c2d..49d20fe8570f 100644 spin_unlock(&base->cpu_base->softirq_expiry_lock); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0296-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch b/debian/patches-rt/0296-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch index fca3b84e1..4339f12bc 100644 --- a/debian/patches-rt/0296-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch +++ b/debian/patches-rt/0296-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch @@ -1,9 +1,12 @@ -From 4d9809e6dfca5b4213ff9fae00819c0af0d4f15d Mon Sep 17 00:00:00 2001 +From 71608ca953e7884a5b61055b0c97a4dd63313586 Mon Sep 17 00:00:00 2001 +Message-Id: <71608ca953e7884a5b61055b0c97a4dd63313586.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:09 +0100 -Subject: [PATCH 296/325] hrtimer: Prevent using hrtimer_grab_expiry_lock() on +Subject: [PATCH 296/327] hrtimer: Prevent using hrtimer_grab_expiry_lock() on migration_base -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit cef1b87f98823af923a386f3f69149acb212d4a1 ] @@ -39,5 +42,5 @@ index 49d20fe8570f..1a5167c68310 100644 spin_unlock(&base->cpu_base->softirq_expiry_lock); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0297-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch b/debian/patches-rt/0297-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch index f5d3f182a..0a18d04dc 100644 --- a/debian/patches-rt/0297-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch +++ b/debian/patches-rt/0297-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch @@ -1,9 +1,12 @@ -From 40b9a01ca24b87e815110263dc6a8d4d23618a57 Mon Sep 17 00:00:00 2001 +From d5f7eeb5eef02de850fdf4723e90f694c76308eb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Sep 2019 16:55:27 +0200 -Subject: [PATCH 297/325] hrtimer: Add a missing bracket and hide +Subject: [PATCH 297/327] hrtimer: Add a missing bracket and hide `migration_base' on !SMP -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 47b6de0b7f22c28b40275aeede3993d807668c3b ] @@ -71,5 +74,5 @@ index 1a5167c68310..e54a95de8b79 100644 spin_unlock(&base->cpu_base->softirq_expiry_lock); } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0298-posix-timers-Unlock-expiry-lock-in-the-early-return.patch b/debian/patches-rt/0298-posix-timers-Unlock-expiry-lock-in-the-early-return.patch index 85fb83dc8..35ab7a9f4 100644 --- a/debian/patches-rt/0298-posix-timers-Unlock-expiry-lock-in-the-early-return.patch +++ b/debian/patches-rt/0298-posix-timers-Unlock-expiry-lock-in-the-early-return.patch @@ -1,8 +1,11 @@ -From f411ec1b4e6bd2f4b4448fa25f79a55478fa3b45 Mon Sep 17 00:00:00 2001 +From c6a286eb70e14effea5ef6dce7b90ea60b52bab7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Sep 2019 12:33:59 +0200 -Subject: [PATCH 298/325] posix-timers: Unlock expiry lock in the early return -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 298/327] posix-timers: Unlock expiry lock in the early return +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 356a2781375ec58521a9bc3f500488745990c242 ] @@ -37,5 +40,5 @@ index 765e700962ab..c9964dc3276b 100644 * Here we take off tsk->signal->cpu_timers[N] and * tsk->cpu_timers[N] all the timers that are firing, and -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0299-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch b/debian/patches-rt/0299-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch index 8b9472d18..e415089cd 100644 --- a/debian/patches-rt/0299-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch +++ b/debian/patches-rt/0299-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch @@ -1,12 +1,15 @@ -From d7ead78411ba51a030468c6baaedb44999852db5 Mon Sep 17 00:00:00 2001 +From c5709957ae653dd7d880138b09c7af210f4a1529 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Tue, 24 Sep 2019 14:36:41 +0200 -Subject: [PATCH 299/325] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= +Subject: [PATCH 299/327] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= =?UTF-8?q?sleeping=5Flock=E2=80=A6()=20to=20annotate=20sleeping=20points?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 4230dd3824c3e1785504e6f757ce79a4b55651fa ] @@ -25,7 +28,7 @@ Signed-off-by: Sebastian Andrzej Siewior 2 files changed, 5 insertions(+) diff --git a/kernel/cpu.c b/kernel/cpu.c -index 1541189f417b..0d50ae262898 100644 +index 9f2e05b2e65c..27fe7c8185c9 100644 --- a/kernel/cpu.c +++ b/kernel/cpu.c @@ -307,7 +307,9 @@ void pin_current_cpu(void) @@ -54,5 +57,5 @@ index a1c0123e7636..3413b9ebef1f 100644 return; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0300-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch b/debian/patches-rt/0300-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch index 3ad68add3..9fbd74f85 100644 --- a/debian/patches-rt/0300-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch +++ b/debian/patches-rt/0300-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch @@ -1,9 +1,12 @@ -From 1c66a5b365296bd3b4ebb2be7eef2d8ba7688414 Mon Sep 17 00:00:00 2001 +From e4cfc5e5a879ac24d491760291475ab58d7a0c6d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:32 -0500 -Subject: [PATCH 300/325] sched: __set_cpus_allowed_ptr: Check cpus_mask, not +Subject: [PATCH 300/327] sched: __set_cpus_allowed_ptr: Check cpus_mask, not cpus_ptr -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit e5606fb7b042db634ed62b4dd733d62e050e468f ] @@ -35,5 +38,5 @@ index 3413b9ebef1f..d6bd8129a390 100644 dest_cpu = cpumask_any_and(cpu_valid_mask, new_mask); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0301-sched-Remove-dead-__migrate_disabled-check.patch b/debian/patches-rt/0301-sched-Remove-dead-__migrate_disabled-check.patch index f8acb3503..dd9e4d931 100644 --- a/debian/patches-rt/0301-sched-Remove-dead-__migrate_disabled-check.patch +++ b/debian/patches-rt/0301-sched-Remove-dead-__migrate_disabled-check.patch @@ -1,8 +1,11 @@ -From f46e960055b6cbc8a2b26fef4edad0c1b7d3770a Mon Sep 17 00:00:00 2001 +From 04ea3d30f7001d150698a624217e5b0ecbbb4145 Mon Sep 17 00:00:00 2001 +Message-Id: <04ea3d30f7001d150698a624217e5b0ecbbb4145.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:33 -0500 -Subject: [PATCH 301/325] sched: Remove dead __migrate_disabled() check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 301/327] sched: Remove dead __migrate_disabled() check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 14d9272d534ea91262e15db99443fc5995c7c016 ] @@ -35,5 +38,5 @@ index d6bd8129a390..a29f33e776d0 100644 struct migration_arg arg = { p, dest_cpu }; /* Need help from migration thread: drop lock and wait. */ -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0302-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch b/debian/patches-rt/0302-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch index b47281312..8547a0e02 100644 --- a/debian/patches-rt/0302-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch +++ b/debian/patches-rt/0302-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch @@ -1,8 +1,11 @@ -From e55dacd743cbf8cee043aab134f975732e2c7c3b Mon Sep 17 00:00:00 2001 +From 7f5e600685c5df3c778beae852093327bc83978b Mon Sep 17 00:00:00 2001 +Message-Id: <7f5e600685c5df3c778beae852093327bc83978b.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:34 -0500 -Subject: [PATCH 302/325] sched: migrate disable: Protect cpus_ptr with lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 302/327] sched: migrate disable: Protect cpus_ptr with lock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 27ee52a891ed2c7e2e2c8332ccae0de7c2674b09 ] @@ -43,5 +46,5 @@ index a29f33e776d0..d9a3f88508ee 100644 update_nr_migratory(p, 1); task_rq_unlock(rq, p, &rf); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0303-lib-smp_processor_id-Don-t-use-cpumask_equal.patch b/debian/patches-rt/0303-lib-smp_processor_id-Don-t-use-cpumask_equal.patch index d50979312..cc7e6008c 100644 --- a/debian/patches-rt/0303-lib-smp_processor_id-Don-t-use-cpumask_equal.patch +++ b/debian/patches-rt/0303-lib-smp_processor_id-Don-t-use-cpumask_equal.patch @@ -1,8 +1,11 @@ -From 2a8268e1b24351654fff43cf71aef1206aebeaf0 Mon Sep 17 00:00:00 2001 +From d481be6a8ec2e68abc2a2a9aa5ffeead29b8f1e6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Waiman Long Date: Thu, 3 Oct 2019 16:36:08 -0400 -Subject: [PATCH 303/325] lib/smp_processor_id: Don't use cpumask_equal() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 303/327] lib/smp_processor_id: Don't use cpumask_equal() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 659252061477862f45b79e1de169e6030f5c8918 ] @@ -41,5 +44,5 @@ index fb35c45b9421..b8a8a8db2d75 100644 /* -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0304-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch b/debian/patches-rt/0304-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch index 01dae0bb1..73d62c4f9 100644 --- a/debian/patches-rt/0304-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch +++ b/debian/patches-rt/0304-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch @@ -1,9 +1,12 @@ -From adad7dbe4e54e932da34439e96166729050fbdc1 Mon Sep 17 00:00:00 2001 +From ceaa27c1dae4bdd9eea6c3bb5bec59694645a1f9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 7 Oct 2019 16:45:18 +0200 -Subject: [PATCH 304/325] futex: Make the futex_hash_bucket spinlock_t again +Subject: [PATCH 304/327] futex: Make the futex_hash_bucket spinlock_t again and bring back its old state -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 954ad80c23edfe71f4e8ce70b961eac884320c3a ] @@ -734,5 +737,5 @@ index 758dc43872e5..546aaf058b9e 100644 extern void rt_mutex_init_proxy_locked(struct rt_mutex *lock, struct task_struct *proxy_owner); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0305-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch b/debian/patches-rt/0305-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch index 97635bb9e..aab984095 100644 --- a/debian/patches-rt/0305-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch +++ b/debian/patches-rt/0305-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch @@ -1,9 +1,12 @@ -From 7a56801d0e3c06595886dde9df739f3c9a8b1b03 Mon Sep 17 00:00:00 2001 +From 8e1caa450f6713822afba2aafcc5b1cc3162b0fa Mon Sep 17 00:00:00 2001 +Message-Id: <8e1caa450f6713822afba2aafcc5b1cc3162b0fa.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 30 Sep 2019 18:15:44 +0200 -Subject: [PATCH 305/325] locking/rtmutex: Clean ->pi_blocked_on in the error +Subject: [PATCH 305/327] locking/rtmutex: Clean ->pi_blocked_on in the error case -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 0be4ea6e3ce693101be0fbd55a0cc7ce238ab2eb ] @@ -98,5 +101,5 @@ index 2a9bf2443acc..63b3d6f306fa 100644 raw_spin_unlock_irq(&lock->wait_lock); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0306-lib-ubsan-Don-t-seralize-UBSAN-report.patch b/debian/patches-rt/0306-lib-ubsan-Don-t-seralize-UBSAN-report.patch index 3821379a5..4c8634c75 100644 --- a/debian/patches-rt/0306-lib-ubsan-Don-t-seralize-UBSAN-report.patch +++ b/debian/patches-rt/0306-lib-ubsan-Don-t-seralize-UBSAN-report.patch @@ -1,8 +1,11 @@ -From 698de15ca2f181483753c9f60b88cb548479f803 Mon Sep 17 00:00:00 2001 +From 0b8b8cee2a83a8974149a59ebd44def7899b0637 Mon Sep 17 00:00:00 2001 +Message-Id: <0b8b8cee2a83a8974149a59ebd44def7899b0637.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Julien Grall Date: Fri, 20 Sep 2019 11:08:35 +0100 -Subject: [PATCH 306/325] lib/ubsan: Don't seralize UBSAN report -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 306/327] lib/ubsan: Don't seralize UBSAN report +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 4702c28ac777b27acb499cbd5e8e787ce1a7d82d ] @@ -304,5 +307,5 @@ index 1e9e2ab25539..5830cc9a2164 100644 } EXPORT_SYMBOL(__ubsan_handle_load_invalid_value); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0307-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch b/debian/patches-rt/0307-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch index 7c5696a4f..86949fd6f 100644 --- a/debian/patches-rt/0307-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch +++ b/debian/patches-rt/0307-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch @@ -1,9 +1,12 @@ -From db9ad49e0819b8bc8cfbad6008ac0f52d5e168e1 Mon Sep 17 00:00:00 2001 +From e912714873cfc2f9b790d5353c2a3a036b9a9009 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Liu Haitao Date: Fri, 27 Sep 2019 16:22:30 +0800 -Subject: [PATCH 307/325] kmemleak: Change the lock of kmemleak_object to +Subject: [PATCH 307/327] kmemleak: Change the lock of kmemleak_object to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 217847f57119b5fdd377bfa3d344613ddb98d9fc ] @@ -289,5 +292,5 @@ index 92ce99b15f2b..e5f5eeed338d 100644 rcu_read_unlock(); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0308-sched-migrate_enable-Use-select_fallback_rq.patch b/debian/patches-rt/0308-sched-migrate_enable-Use-select_fallback_rq.patch index cc54b2d4e..8d6c15edf 100644 --- a/debian/patches-rt/0308-sched-migrate_enable-Use-select_fallback_rq.patch +++ b/debian/patches-rt/0308-sched-migrate_enable-Use-select_fallback_rq.patch @@ -1,8 +1,11 @@ -From 4c2c29a788e99fba068a36c7a2db2a51ff1f0eda Mon Sep 17 00:00:00 2001 +From f94c66add46088b6083b57d104c6c7c8577cc981 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:12 -0500 -Subject: [PATCH 308/325] sched: migrate_enable: Use select_fallback_rq() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 308/327] sched: migrate_enable: Use select_fallback_rq() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit adfa969d4cfcc995a9d866020124e50f1827d2d1 ] @@ -62,5 +65,5 @@ index d9a3f88508ee..6fd3f7b4d7d8 100644 unpin_current_cpu(); preempt_lazy_enable(); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0309-sched-Lazy-migrate_disable-processing.patch b/debian/patches-rt/0309-sched-Lazy-migrate_disable-processing.patch index 64a58b254..b026fee19 100644 --- a/debian/patches-rt/0309-sched-Lazy-migrate_disable-processing.patch +++ b/debian/patches-rt/0309-sched-Lazy-migrate_disable-processing.patch @@ -1,8 +1,11 @@ -From 74e387d61b063ceb45e370bc75b3f0d76bd51061 Mon Sep 17 00:00:00 2001 +From 5384dc959a29567748c81a3c3f33190ea34fc20e Mon Sep 17 00:00:00 2001 +Message-Id: <5384dc959a29567748c81a3c3f33190ea34fc20e.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:13 -0500 -Subject: [PATCH 309/325] sched: Lazy migrate_disable processing -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 309/327] sched: Lazy migrate_disable processing +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 425c5b38779a860062aa62219dc920d374b13c17 ] @@ -67,7 +70,7 @@ index e67645924404..87347ccbba0c 100644 #endif /* !CONFIG_HOTPLUG_CPU */ diff --git a/include/linux/sched.h b/include/linux/sched.h -index 854a6cb456af..60ac271472aa 100644 +index bdae37091808..729127d0e536 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -227,6 +227,8 @@ extern void io_schedule_finish(int token); @@ -121,7 +124,7 @@ index 9e3362748214..4e5af4616dbd 100644 .active_mm = &init_mm, .restart_block = { diff --git a/kernel/cpu.c b/kernel/cpu.c -index 0d50ae262898..2834eed32b55 100644 +index 27fe7c8185c9..cb446db5790c 100644 --- a/kernel/cpu.c +++ b/kernel/cpu.c @@ -75,11 +75,6 @@ static DEFINE_PER_CPU(struct cpuhp_cpu_state, cpuhp_state) = { @@ -583,10 +586,10 @@ index 6fd3f7b4d7d8..e97ac751aad2 100644 +} #endif diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h -index c90574112bca..78fa5911dd55 100644 +index 005874299b04..8b0c0b63ab22 100644 --- a/kernel/sched/sched.h +++ b/kernel/sched/sched.h -@@ -913,6 +913,10 @@ struct rq { +@@ -919,6 +919,10 @@ struct rq { /* Must be inspected within a rcu lock section */ struct cpuidle_state *idle_state; #endif @@ -612,5 +615,5 @@ index b8a8a8db2d75..0c80992aa337 100644 goto out; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0310-sched-migrate_enable-Use-stop_one_cpu_nowait.patch b/debian/patches-rt/0310-sched-migrate_enable-Use-stop_one_cpu_nowait.patch index 70e049efd..c081599bd 100644 --- a/debian/patches-rt/0310-sched-migrate_enable-Use-stop_one_cpu_nowait.patch +++ b/debian/patches-rt/0310-sched-migrate_enable-Use-stop_one_cpu_nowait.patch @@ -1,8 +1,11 @@ -From b18b09e0eb93eaff554f8b9ddf8be859ceea079f Mon Sep 17 00:00:00 2001 +From 878918a0eb2f8d15c795728687a5137671a7c4e2 Mon Sep 17 00:00:00 2001 +Message-Id: <878918a0eb2f8d15c795728687a5137671a7c4e2.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:14 -0500 -Subject: [PATCH 310/325] sched: migrate_enable: Use stop_one_cpu_nowait() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 310/327] sched: migrate_enable: Use stop_one_cpu_nowait() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 6b39a1fa8c53cae08dc03afdae193b7d3a78a173 ] @@ -117,5 +120,5 @@ index 067cb83f37ea..2d15c0d50625 100644 wake_up_q(&wakeq); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0311-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch b/debian/patches-rt/0311-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch index 8c761c657..dba0499a5 100644 --- a/debian/patches-rt/0311-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch +++ b/debian/patches-rt/0311-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch @@ -1,9 +1,12 @@ -From 0a88cdae392aebfc8444d6c038aa0e5fbfa4f3f5 Mon Sep 17 00:00:00 2001 +From 71ed8c2ce0e4186e19236547d35702003a92fad5 Mon Sep 17 00:00:00 2001 +Message-Id: <71ed8c2ce0e4186e19236547d35702003a92fad5.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 18 Oct 2019 13:04:15 +0200 -Subject: [PATCH 311/325] Revert "ARM: Initialize split page table locks for +Subject: [PATCH 311/327] Revert "ARM: Initialize split page table locks for vector page" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 247074c44d8c3e619dfde6404a52295d8d671d38 ] @@ -83,5 +86,5 @@ index 8d3c7ce34c24..82ab015bf42b 100644 /* * The vectors page is always readable from user space for the -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0312-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch b/debian/patches-rt/0312-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch index 56aef004b..bde23505b 100644 --- a/debian/patches-rt/0312-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch +++ b/debian/patches-rt/0312-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch @@ -1,9 +1,12 @@ -From 146edf2faa6c91a7c60ed338adbe4112c0a655bb Mon Sep 17 00:00:00 2001 +From 6763f583ac0514fcceec18f3b6d24501229829c8 Mon Sep 17 00:00:00 2001 +Message-Id: <6763f583ac0514fcceec18f3b6d24501229829c8.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Nov 2019 09:25:04 +0100 -Subject: [PATCH 312/325] locking: Make spinlock_t and rwlock_t a RCU section +Subject: [PATCH 312/327] locking: Make spinlock_t and rwlock_t a RCU section on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 84440022a0e1c8c936d61f8f97593674a295d409 ] @@ -125,5 +128,5 @@ index c3b91205161c..0ae8c62ea832 100644 } EXPORT_SYMBOL(rt_write_unlock); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0313-sched-core-migrate_enable-must-access-takedown_cpu_t.patch b/debian/patches-rt/0313-sched-core-migrate_enable-must-access-takedown_cpu_t.patch index 868f3b1d9..3c7303f0a 100644 --- a/debian/patches-rt/0313-sched-core-migrate_enable-must-access-takedown_cpu_t.patch +++ b/debian/patches-rt/0313-sched-core-migrate_enable-must-access-takedown_cpu_t.patch @@ -1,9 +1,12 @@ -From b36ee36f5d6230ea331f5999401df432180eb114 Mon Sep 17 00:00:00 2001 +From d75f580250a6bee8aeb4153e051153e167a6a17a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 29 Nov 2019 17:24:55 +0100 -Subject: [PATCH 313/325] sched/core: migrate_enable() must access +Subject: [PATCH 313/327] sched/core: migrate_enable() must access takedown_cpu_task on !HOTPLUG_CPU -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit a61d1977f692e46bad99a100f264981ba08cb4bd ] @@ -21,7 +24,7 @@ Signed-off-by: Steven Rostedt (VMware) 2 files changed, 4 insertions(+) diff --git a/kernel/cpu.c b/kernel/cpu.c -index 2834eed32b55..d28254597f59 100644 +index cb446db5790c..6876436155eb 100644 --- a/kernel/cpu.c +++ b/kernel/cpu.c @@ -845,7 +845,9 @@ static int take_cpu_down(void *_param) @@ -51,5 +54,5 @@ index e465381b464d..cbd76324babd 100644 if (!p->migrate_disable_scheduled) goto out; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0314-lib-smp_processor_id-Adjust-check_preemption_disable.patch b/debian/patches-rt/0314-lib-smp_processor_id-Adjust-check_preemption_disable.patch index bd104473a..09646d740 100644 --- a/debian/patches-rt/0314-lib-smp_processor_id-Adjust-check_preemption_disable.patch +++ b/debian/patches-rt/0314-lib-smp_processor_id-Adjust-check_preemption_disable.patch @@ -1,9 +1,12 @@ -From feb825b2c5296319abdfa796acf01d481332b6a1 Mon Sep 17 00:00:00 2001 +From 3e022d320cb74a5770778b069a80ad7a1899cfb8 Mon Sep 17 00:00:00 2001 +Message-Id: <3e022d320cb74a5770778b069a80ad7a1899cfb8.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Daniel Wagner Date: Mon, 16 Dec 2019 16:15:57 +0100 -Subject: [PATCH 314/325] lib/smp_processor_id: Adjust +Subject: [PATCH 314/327] lib/smp_processor_id: Adjust check_preemption_disabled() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit af3c1c5fdf177870fb5e6e16b24e374696ab28f5 ] @@ -37,5 +40,5 @@ index 0c80992aa337..2e7398534b66 100644 if (current->nr_cpus_allowed == 1) goto out; -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0315-sched-migrate_enable-Busy-loop-until-the-migration-r.patch b/debian/patches-rt/0315-sched-migrate_enable-Busy-loop-until-the-migration-r.patch index f99dcb6af..d8f53c088 100644 --- a/debian/patches-rt/0315-sched-migrate_enable-Busy-loop-until-the-migration-r.patch +++ b/debian/patches-rt/0315-sched-migrate_enable-Busy-loop-until-the-migration-r.patch @@ -1,9 +1,12 @@ -From 61c8b73bfa540c2d761e691f2b52b74e7af0cab3 Mon Sep 17 00:00:00 2001 +From 15f182fdbb462481876d5cbaf57f8b85e6b06c2c Mon Sep 17 00:00:00 2001 +Message-Id: <15f182fdbb462481876d5cbaf57f8b85e6b06c2c.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Dec 2019 10:53:59 +0100 -Subject: [PATCH 315/325] sched: migrate_enable: Busy loop until the migration +Subject: [PATCH 315/327] sched: migrate_enable: Busy loop until the migration request is completed -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 140d7f54a5fff02898d2ca9802b39548bf7455f1 ] @@ -53,5 +56,5 @@ index cbd76324babd..4616c086dd26 100644 out: -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0316-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch b/debian/patches-rt/0316-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch index 0cef6870d..188384ef8 100644 --- a/debian/patches-rt/0316-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch +++ b/debian/patches-rt/0316-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch @@ -1,8 +1,11 @@ -From 4f66ae2e8860bf4d6272dffff2e66f0f28e726b0 Mon Sep 17 00:00:00 2001 +From 3a17364c0fc5f24a827c869cf451a86f0c300b43 Mon Sep 17 00:00:00 2001 +Message-Id: <3a17364c0fc5f24a827c869cf451a86f0c300b43.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 18 Dec 2019 12:25:09 +0100 -Subject: [PATCH 316/325] userfaultfd: Use a seqlock instead of seqcount -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 316/327] userfaultfd: Use a seqlock instead of seqcount +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit dc952a564d02997330654be9628bbe97ba2a05d3 ] @@ -76,5 +79,5 @@ index d269d1139f7f..ff6be687f68e 100644 SYSCALL_DEFINE1(userfaultfd, int, flags) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0317-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch b/debian/patches-rt/0317-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch index fdafbd7a4..66cb31003 100644 --- a/debian/patches-rt/0317-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch +++ b/debian/patches-rt/0317-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch @@ -1,8 +1,11 @@ -From 5ae09731e6eef2497166c6c3520e1537dde2bc31 Mon Sep 17 00:00:00 2001 +From 47459b060c4eb4be038a5623bc07cb91e75afacd Mon Sep 17 00:00:00 2001 +Message-Id: <47459b060c4eb4be038a5623bc07cb91e75afacd.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:46 -0500 -Subject: [PATCH 317/325] sched: migrate_enable: Use per-cpu cpu_stop_work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 317/327] sched: migrate_enable: Use per-cpu cpu_stop_work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 2dcd94b443c5dcbc20281666321b7f025f9cc85c ] @@ -79,5 +82,5 @@ index 4616c086dd26..c4290fa5c0b6 100644 out: -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0318-sched-migrate_enable-Remove-__schedule-call.patch b/debian/patches-rt/0318-sched-migrate_enable-Remove-__schedule-call.patch index 4a523606d..7c77ffd93 100644 --- a/debian/patches-rt/0318-sched-migrate_enable-Remove-__schedule-call.patch +++ b/debian/patches-rt/0318-sched-migrate_enable-Remove-__schedule-call.patch @@ -1,8 +1,11 @@ -From 73dfb6f21b436b1f96516f951ca173e0828562c6 Mon Sep 17 00:00:00 2001 +From 20c2500d81b2da25336c3c4a629a09d3b3043c1e Mon Sep 17 00:00:00 2001 +Message-Id: <20c2500d81b2da25336c3c4a629a09d3b3043c1e.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:47 -0500 -Subject: [PATCH 318/325] sched: migrate_enable: Remove __schedule() call -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 318/327] sched: migrate_enable: Remove __schedule() call +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit b8162e61e9a33bd1de6452eb838fbf50a93ddd9a ] @@ -37,5 +40,5 @@ index c4290fa5c0b6..02e51c74e0bf 100644 out: -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0319-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch b/debian/patches-rt/0319-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch index 2c464a0ba..431900a95 100644 --- a/debian/patches-rt/0319-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch +++ b/debian/patches-rt/0319-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch @@ -1,9 +1,12 @@ -From f7888a980c01a83b9589e0a56b38997f29ba207d Mon Sep 17 00:00:00 2001 +From 3a9891960143566efeccaf7363b2f0602abba5b3 Mon Sep 17 00:00:00 2001 +Message-Id: <3a9891960143566efeccaf7363b2f0602abba5b3.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Matt Fleming Date: Sun, 26 Jan 2020 21:19:45 +0000 -Subject: [PATCH 319/325] mm/memcontrol: Move misplaced +Subject: [PATCH 319/327] mm/memcontrol: Move misplaced local_unlock_irqrestore() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit 071a1d6a6e14d0dec240a8c67b425140d7f92f6a ] @@ -38,5 +41,5 @@ index 4156a4e766fb..d059e2a99441 100644 /** -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0320-locallock-Include-header-for-the-current-macro.patch b/debian/patches-rt/0320-locallock-Include-header-for-the-current-macro.patch index a47c7aaad..76ec4d690 100644 --- a/debian/patches-rt/0320-locallock-Include-header-for-the-current-macro.patch +++ b/debian/patches-rt/0320-locallock-Include-header-for-the-current-macro.patch @@ -1,8 +1,11 @@ -From 455f22d624a5ef6344c8ff69a8d65ff71bc65672 Mon Sep 17 00:00:00 2001 +From 76281d7c00b4156764f2a77b03b1ddea772132b9 Mon Sep 17 00:00:00 2001 +Message-Id: <76281d7c00b4156764f2a77b03b1ddea772132b9.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Feb 2020 13:29:50 +0100 -Subject: [PATCH 320/325] locallock: Include header for the `current' macro -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Subject: [PATCH 320/327] locallock: Include header for the `current' macro +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit e693075a5fd852043fa8d2b0467e078d9e5cb782 ] @@ -28,5 +31,5 @@ index 921eab83cd34..81c89d87723b 100644 #ifdef CONFIG_PREEMPT_RT_BASE -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0321-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch b/debian/patches-rt/0321-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch index b5b549a61..a4ad9e05c 100644 --- a/debian/patches-rt/0321-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch +++ b/debian/patches-rt/0321-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch @@ -1,9 +1,12 @@ -From a6f7c997fb02c34d3cffdffcba7d1c98ae91d171 Mon Sep 17 00:00:00 2001 +From ef924f91f05eae6fcb1c1c9969d363b255289854 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:57:11 +0100 -Subject: [PATCH 321/325] drm/vmwgfx: Drop preempt_disable() in +Subject: [PATCH 321/327] drm/vmwgfx: Drop preempt_disable() in vmw_fifo_ping_host() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit b901491e7b9b7a676818d84e482b69be72fc142f ] @@ -41,5 +44,5 @@ index d0fd147ef75f..fb5a3461bb8c 100644 void vmw_fifo_release(struct vmw_private *dev_priv, struct vmw_fifo_state *fifo) -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0322-tracing-make-preempt_lazy-and-migrate_disable-counte.patch b/debian/patches-rt/0322-tracing-make-preempt_lazy-and-migrate_disable-counte.patch index 8f9eb5aa9..675fe378d 100644 --- a/debian/patches-rt/0322-tracing-make-preempt_lazy-and-migrate_disable-counte.patch +++ b/debian/patches-rt/0322-tracing-make-preempt_lazy-and-migrate_disable-counte.patch @@ -1,9 +1,12 @@ -From 6ef292c7e5f32959f6677108998c006ffd625694 Mon Sep 17 00:00:00 2001 +From fb0b75771dbf1c10f0923035b67390100054a136 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:15:15 +0100 -Subject: [PATCH 322/325] tracing: make preempt_lazy and migrate_disable +Subject: [PATCH 322/327] tracing: make preempt_lazy and migrate_disable counter smaller -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz [ Upstream commit dd430bf5ecb40f9a89679c85868826475d71de54 ] @@ -52,5 +55,5 @@ index 1febb0ca4c81..07b8f5bfd263 100644 return ret; } -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0323-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch b/debian/patches-rt/0323-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch index 276305ca1..c71f3f104 100644 --- a/debian/patches-rt/0323-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch +++ b/debian/patches-rt/0323-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch @@ -1,9 +1,12 @@ -From 126be7dbd1b1466d09a2314fd0d24af2e72f319d Mon Sep 17 00:00:00 2001 +From 71da8e9b9157813ec898f01fff08a38fdebaf510 Mon Sep 17 00:00:00 2001 +Message-Id: <71da8e9b9157813ec898f01fff08a38fdebaf510.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: Tiejun Chen Date: Mon, 30 Mar 2020 18:45:23 -0400 -Subject: [PATCH 323/325] lib/ubsan: Remove flags parameter from calls to +Subject: [PATCH 323/327] lib/ubsan: Remove flags parameter from calls to ubsan_prologue() and ubsan_epilogue() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz Fails to build with CONFIG_UBSAN=y @@ -53,5 +56,5 @@ index 5830cc9a2164..199c75e03469 100644 EXPORT_SYMBOL(__ubsan_handle_vla_bound_not_positive); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch b/debian/patches-rt/0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch index 5fc71975b..e4e0a6c88 100644 --- a/debian/patches-rt/0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch +++ b/debian/patches-rt/0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch @@ -1,9 +1,12 @@ -From 91565eecad8c73f52ef0c7fef8bfb042f142e2e2 Mon Sep 17 00:00:00 2001 +From 9632a622d8f957d390d1ea53a0d5eaaeb0f27370 Mon Sep 17 00:00:00 2001 +Message-Id: <9632a622d8f957d390d1ea53a0d5eaaeb0f27370.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Sun, 22 Mar 2020 00:00:28 +0100 -Subject: [PATCH 324/325] irq_work: Fix checking of IRQ_WORK_LAZY flag set on +Subject: [PATCH 324/327] irq_work: Fix checking of IRQ_WORK_LAZY flag set on non PREEMPT_RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz When CONFIG_PREEMPT_RT_FULL is not set, some of the checks for using lazy_list are not properly made as the IRQ_WORK_LAZY is not checked. There's @@ -68,5 +71,5 @@ index 2940622da5b3..b6d9d35941ac 100644 else list = &per_cpu(raised_list, cpu); -- -2.25.1 +2.17.1 diff --git a/debian/patches-rt/0325-Linux-4.19.115-rt48-REBASE.patch b/debian/patches-rt/0325-Linux-4.19.115-rt48-REBASE.patch deleted file mode 100644 index 1a0001487..000000000 --- a/debian/patches-rt/0325-Linux-4.19.115-rt48-REBASE.patch +++ /dev/null @@ -1,20 +0,0 @@ -From 03030c7da51669f16a21bd1c99bbf8b8ed2cefea Mon Sep 17 00:00:00 2001 -From: "Steven Rostedt (VMware)" -Date: Tue, 31 Mar 2020 12:32:04 -0400 -Subject: [PATCH 325/325] Linux 4.19.115-rt48 REBASE -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.115-rt48.tar.xz - ---- - localversion-rt | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/localversion-rt b/localversion-rt -index 1199ebade17b..24707986c321 100644 ---- a/localversion-rt -+++ b/localversion-rt -@@ -1 +1 @@ ---rt16 -+-rt48 --- -2.25.1 - diff --git a/debian/patches-rt/0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch b/debian/patches-rt/0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch new file mode 100644 index 000000000..553d98f92 --- /dev/null +++ b/debian/patches-rt/0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch @@ -0,0 +1,123 @@ +From bb278370b5b74a9f82eddc685ece70e9858ef58f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +From: Zhang Xiao +Date: Tue, 17 Mar 2020 12:47:43 +0100 +Subject: [PATCH 325/327] tasklet: Address a race resulting in double-enqueue +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz + +The kernel bugzilla has the following race condition reported: + +CPU0 CPU1 CPU2 +------------------------------------------------ +test_set SCHED + test_set RUN + if SCHED + add_list + raise + clear RUN + +test_set RUN +test_clear SCHED + ->func + test_set SCHED +tasklet_try_unlock ->0 +test_clear SCHED + test_set SCHED + ->func +tasklet_try_unlock ->1 + test_set RUN + if SCHED + add list + raise + clear RUN + test_set RUN + if SCHED + add list + raise + clear RUN + +As a result the tasklet is enqueued on both CPUs and run on both CPUs. Due +to the nature of the list used here, it is possible that further +(different) tasklets, which are enqueued after this double-enqueued +tasklet, are scheduled on CPU2 but invoked on CPU1. It is also possible +that these tasklets won't be invoked at all, because during the second +enqueue process the t->next pointer is set to NULL - dropping everything +from the list. + +This race will trigger one or two of the WARN_ON() in +tasklet_action_common(). +The problem is that the tasklet may be invoked multiple times and clear +SCHED bit on each invocation. This makes it possible to enqueue the +very same tasklet on different CPUs. + +Current RT-devel is using the upstream implementation which does not +re-run tasklets if they have SCHED set again and so it does not clear +the SCHED bit multiple times on a single invocation. + +Introduce the CHAINED flag. The tasklet will only be enqueued if the +CHAINED flag has been set successfully. +If it is possible to exchange the flags (CHAINED | RUN) -> 0 then the +tasklet won't be re-run. Otherwise the possible SCHED flag is removed +and the tasklet is re-run again. + +Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=61451 +Not-signed-off-by: Zhang Xiao +[bigeasy: patch description] +Signed-off-by: Sebastian Andrzej Siewior + +Signed-off-by: Tom Zanussi +--- + include/linux/interrupt.h | 5 ++++- + kernel/softirq.c | 6 +++++- + 2 files changed, 9 insertions(+), 2 deletions(-) + +diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h +index 97d9ba26915e..a3b5edb26bc5 100644 +--- a/include/linux/interrupt.h ++++ b/include/linux/interrupt.h +@@ -579,12 +579,15 @@ enum + { + TASKLET_STATE_SCHED, /* Tasklet is scheduled for execution */ + TASKLET_STATE_RUN, /* Tasklet is running (SMP only) */ +- TASKLET_STATE_PENDING /* Tasklet is pending */ ++ TASKLET_STATE_PENDING, /* Tasklet is pending */ ++ TASKLET_STATE_CHAINED /* Tasklet is chained */ + }; + + #define TASKLET_STATEF_SCHED (1 << TASKLET_STATE_SCHED) + #define TASKLET_STATEF_RUN (1 << TASKLET_STATE_RUN) + #define TASKLET_STATEF_PENDING (1 << TASKLET_STATE_PENDING) ++#define TASKLET_STATEF_CHAINED (1 << TASKLET_STATE_CHAINED) ++#define TASKLET_STATEF_RC (TASKLET_STATEF_RUN | TASKLET_STATEF_CHAINED) + + #if defined(CONFIG_SMP) || defined(CONFIG_PREEMPT_RT_FULL) + static inline int tasklet_trylock(struct tasklet_struct *t) +diff --git a/kernel/softirq.c b/kernel/softirq.c +index 25bcf2f2714b..73dae64bfc9c 100644 +--- a/kernel/softirq.c ++++ b/kernel/softirq.c +@@ -947,6 +947,10 @@ static void __tasklet_schedule_common(struct tasklet_struct *t, + * is locked before adding it to the list. + */ + if (test_bit(TASKLET_STATE_SCHED, &t->state)) { ++ if (test_and_set_bit(TASKLET_STATE_CHAINED, &t->state)) { ++ tasklet_unlock(t); ++ return; ++ } + t->next = NULL; + *head->tail = t; + head->tail = &(t->next); +@@ -1040,7 +1044,7 @@ static void tasklet_action_common(struct softirq_action *a, + again: + t->func(t->data); + +- while (!tasklet_tryunlock(t)) { ++ while (cmpxchg(&t->state, TASKLET_STATEF_RC, 0) != TASKLET_STATEF_RC) { + /* + * If it got disabled meanwhile, bail out: + */ +-- +2.17.1 + diff --git a/debian/patches-rt/0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch b/debian/patches-rt/0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch new file mode 100644 index 000000000..dc0920416 --- /dev/null +++ b/debian/patches-rt/0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch @@ -0,0 +1,53 @@ +From 87f9b21f14403942c6d2ccc92ab978f3d364e53d Mon Sep 17 00:00:00 2001 +Message-Id: <87f9b21f14403942c6d2ccc92ab978f3d364e53d.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +From: Rasmus Villemoes +Date: Tue, 28 Apr 2020 16:40:26 +0200 +Subject: [PATCH 326/327] hrtimer: fix logic for when grabbing + softirq_expiry_lock can be elided +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz + +Commit + + hrtimer: Add a missing bracket and hide `migration_base' on !SMP + +which is 47b6de0b7f22 in 5.2-rt and 40aae5708e7a in 4.19-rt, +inadvertently changed the logic from base != &migration_base to base +== &migration_base. + +On !CONFIG_SMP, the effect was to effectively always elide this +lock/unlock pair (since is_migration_base() is unconditionally false), +which for me consistently causes lockups during reboot, and reportedly +also often causes a hang during boot. + +Adding this logical negation (or, what is effectively the same thing +on !CONFIG_SMP, reverting the above commit as well as "hrtimer: +Prevent using hrtimer_grab_expiry_lock() on migration_base") fixes +that lockup. + +Fixes: 40aae5708e7a (hrtimer: Add a missing bracket and hide `migration_base' on !SMP) # 4.19-rt +Fixes: 47b6de0b7f22 (hrtimer: Add a missing bracket and hide `migration_base' on !SMP) # 5.2-rt +Signed-off-by: Rasmus Villemoes +Reviewed-by: Steven Rostedt (VMware) +Signed-off-by: Tom Zanussi +--- + kernel/time/hrtimer.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c +index e54a95de8b79..c3966c090246 100644 +--- a/kernel/time/hrtimer.c ++++ b/kernel/time/hrtimer.c +@@ -953,7 +953,7 @@ void hrtimer_grab_expiry_lock(const struct hrtimer *timer) + { + struct hrtimer_clock_base *base = READ_ONCE(timer->base); + +- if (timer->is_soft && is_migration_base(base)) { ++ if (timer->is_soft && !is_migration_base(base)) { + spin_lock(&base->cpu_base->softirq_expiry_lock); + spin_unlock(&base->cpu_base->softirq_expiry_lock); + } +-- +2.17.1 + diff --git a/debian/patches-rt/0327-Linux-4.19.120-rt52-REBASE.patch b/debian/patches-rt/0327-Linux-4.19.120-rt52-REBASE.patch new file mode 100644 index 000000000..ac5d60285 --- /dev/null +++ b/debian/patches-rt/0327-Linux-4.19.120-rt52-REBASE.patch @@ -0,0 +1,24 @@ +From 7c005718e34690dcb3eec30a9e4b9e3920a14064 Mon Sep 17 00:00:00 2001 +Message-Id: <7c005718e34690dcb3eec30a9e4b9e3920a14064.1588797588.git.zanussi@kernel.org> +In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +From: Tom Zanussi +Date: Wed, 6 May 2020 15:31:36 -0500 +Subject: [PATCH 327/327] Linux 4.19.120-rt52 REBASE +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz + +Signed-off-by: Tom Zanussi +--- + localversion-rt | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/localversion-rt b/localversion-rt +index 1199ebade17b..66a5ed8bf3d7 100644 +--- a/localversion-rt ++++ b/localversion-rt +@@ -1 +1 @@ +--rt16 ++-rt52 +-- +2.17.1 + diff --git a/debian/patches-rt/series b/debian/patches-rt/series index 14f63a8ff..068d47e34 100644 --- a/debian/patches-rt/series +++ b/debian/patches-rt/series @@ -322,4 +322,6 @@ 0322-tracing-make-preempt_lazy-and-migrate_disable-counte.patch 0323-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch 0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch -0325-Linux-4.19.115-rt48-REBASE.patch +0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch +0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch +0327-Linux-4.19.120-rt52-REBASE.patch