From 321776dd0e630e8f534edc581eff01381bcdd60d Mon Sep 17 00:00:00 2001 From: Salvatore Bonaccorso Date: Fri, 4 Sep 2020 22:10:21 +0200 Subject: [PATCH] [rt] Update to 4.19.142-rt63 --- debian/changelog | 1 + ...M-at91-add-TCB-registers-definitions.patch | 8 +- ...ers-Add-a-new-driver-for-the-Atmel-A.patch | 12 +- ...ers-timer-atmel-tcb-add-clockevent-d.patch | 12 +- ...drivers-atmel-pit-make-option-silent.patch | 12 +- ...at91-Implement-clocksource-selection.patch | 12 +- ...onfigs-at91-use-new-TCB-timer-driver.patch | 12 +- .../0007-ARM-configs-at91-unselect-PIT.patch | 12 +- ...ts-Move-pending-table-allocation-to-.patch | 20 +- ...-convert-worker-lock-to-raw-spinlock.patch | 40 +-- ...m-qi-simplify-CGR-allocation-freeing.patch | 12 +- ...obustify-CFS-bandwidth-timer-locking.patch | 14 +- ...012-arm-Convert-arm-boot_lock-to-raw.patch | 12 +- ...-let-setaffinity-unmask-threaded-EOI.patch | 14 +- ...irqsave-in-cgroup_rstat_flush_locked.patch | 12 +- ...lize-cookie-hash-table-raw-spinlocks.patch | 12 +- ...mbus-include-header-for-get_irq_regs.patch | 12 +- ...de-irqflags.h-for-raw_local_irq_save.patch | 12 +- .../0018-efi-Allow-efi-runtime.patch | 14 +- ...fi-drop-task_lock-from-efi_switch_mm.patch | 12 +- ...e_layout-before-altenates-are-applie.patch | 14 +- ...-phandle-cache-outside-of-the-devtre.patch | 12 +- ...ake-quarantine_lock-a-raw_spinlock_t.patch | 12 +- ...xpedited-GP-parallelization-cleverne.patch | 12 +- ...-kmemleak_lock-to-raw-spinlock-on-RT.patch | 12 +- ...-replace-seqcount_t-with-a-seqlock_t.patch | 14 +- ...vide-a-pointer-to-the-valid-CPU-mask.patch | 18 +- ...ernel-sched-core-add-migrate_disable.patch | 12 +- ...sable-Add-export_symbol_gpl-for-__mi.patch | 12 +- ...o-not-disable-enable-clocks-in-a-row.patch | 12 +- ...B-Allow-higher-clock-rates-for-clock.patch | 12 +- ...31-timekeeping-Split-jiffies-seqlock.patch | 12 +- ...2-signal-Revert-ptrace-preempt-magic.patch | 12 +- ...et-sched-Use-msleep-instead-of-yield.patch | 12 +- ...rq-remove-BUG_ON-irqs_disabled-check.patch | 16 +- ...do-no-disable-interrupts-in-giveback.patch | 12 +- ...rovide-PREEMPT_RT_BASE-config-switch.patch | 12 +- ...sable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch | 12 +- ...abel-disable-if-stop_machine-is-used.patch | 12 +- ...config-options-which-are-not-RT-comp.patch | 12 +- .../0040-lockdep-disable-self-test.patch | 12 +- .../0041-mm-Allow-only-slub-on-RT.patch | 12 +- ...locking-Disable-spin-on-owner-for-RT.patch | 12 +- ...043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch | 12 +- ...044-rcu-make-RCU_BOOST-default-on-RT.patch | 12 +- ...-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch | 12 +- ...46-net-core-disable-NET_RX_BUSY_POLL.patch | 12 +- ...0047-arm-disable-NEON-in-kernel-mode.patch | 12 +- ...0048-powerpc-Use-generic-rwsem-on-RT.patch | 12 +- ...ble-in-kernel-MPIC-emulation-for-PRE.patch | 12 +- .../0050-powerpc-Disable-highmem-on-RT.patch | 12 +- .../0051-mips-Disable-highmem-on-RT.patch | 12 +- ...86-Use-generic-rwsem_spinlocks-on-rt.patch | 12 +- ...ds-trigger-disable-CPU-trigger-on-RT.patch | 12 +- ...rop-K8-s-driver-from-beeing-selected.patch | 12 +- .../patches-rt/0055-md-disable-bcache.patch | 12 +- ...6-efi-Disable-runtime-services-on-RT.patch | 14 +- ...0057-printk-Add-a-printk-kill-switch.patch | 12 +- ..._early_printk-boot-param-to-help-wit.patch | 12 +- ...pt-Provide-preempt_-_-no-rt-variants.patch | 12 +- ...-migrate_disable-enable-in-different.patch | 12 +- .../0061-rt-Add-local-irq-locks.patch | 12 +- ...provide-get-put-_locked_ptr-variants.patch | 12 +- ...catterlist-Do-not-disable-irqs-on-RT.patch | 12 +- ...-x86-Delay-calling-signals-in-atomic.patch | 12 +- ...ignal-delay-calling-signals-on-32bit.patch | 12 +- ...head-Replace-bh_uptodate_lock-for-rt.patch | 12 +- ...-state-lock-and-journal-head-lock-rt.patch | 12 +- ...st_bl-Make-list-head-locking-RT-safe.patch | 12 +- ...-list_bl-fixup-bogus-lockdep-warning.patch | 12 +- .../0070-genirq-Disable-irqpoll-on-rt.patch | 12 +- ...-genirq-Force-interrupt-thread-on-RT.patch | 14 +- ...d-zone-lock-while-freeing-pages-from.patch | 31 ++- ...d-zone-lock-while-freeing-pages-from.patch | 30 +- ...B-change-list_lock-to-raw_spinlock_t.patch | 12 +- ...ving-back-empty-slubs-to-IRQ-enabled.patch | 12 +- ...page_alloc-rt-friendly-per-cpu-pages.patch | 48 ++-- ...077-mm-swap-Convert-to-percpu-locked.patch | 16 +- ...m-perform-lru_add_drain_all-remotely.patch | 12 +- ...t-per-cpu-variables-with-preempt-dis.patch | 12 +- ...plit-page-table-locks-for-vector-pag.patch | 12 +- .../0081-mm-Enable-SLUB-for-RT.patch | 12 +- ...0082-slub-Enable-irqs-for-__GFP_WAIT.patch | 12 +- .../0083-slub-Disable-SLUB_CPU_PARTIAL.patch | 12 +- ...n-t-call-schedule_work_on-in-preempt.patch | 12 +- ...place-local_irq_disable-with-local-l.patch | 12 +- ...oc-copy-with-get_cpu_var-and-locking.patch | 12 +- ...le-preemption-__split_large_page-aft.patch | 12 +- .../0088-radix-tree-use-local-locks.patch | 12 +- ...9-timers-Prepare-for-full-preemption.patch | 41 +-- ...090-x86-kvm-Require-const-tsc-for-RT.patch | 14 +- ...ec-Don-t-use-completion-s-wait-queue.patch | 12 +- .../0092-wait.h-include-atomic.h.patch | 12 +- ...mple-Simple-work-queue-implemenation.patch | 12 +- ...-a-shit-statement-in-SWORK_EVENT_PEN.patch | 12 +- ...95-completion-Use-simple-wait-queues.patch | 12 +- .../0096-fs-aio-simple-simple-work.patch | 12 +- ...id-schedule_work-with-interrupts-dis.patch | 20 +- ...ate-hrtimer_init-hrtimer_init_sleepe.patch | 12 +- ...099-hrtimers-Prepare-full-preemption.patch | 12 +- ...s-by-default-into-the-softirq-contex.patch | 16 +- ...air-Make-the-hrtimers-non-hard-again.patch | 14 +- ...-schedule_work-call-to-helper-thread.patch | 12 +- ...te-change-before-hrtimer_cancel-in-d.patch | 12 +- ...timers-Thread-posix-cpu-timers-on-rt.patch | 12 +- ...ched-Move-task_struct-cleanup-to-RCU.patch | 12 +- ...-number-of-task-migrations-per-batch.patch | 12 +- .../0107-sched-Move-mmdrop-to-RCU-on-RT.patch | 12 +- ...e-stack-kprobe-clean-up-to-__put_tas.patch | 12 +- ...state-for-tasks-blocked-on-sleeping-.patch | 12 +- ...ount-rcu_preempt_depth-on-RT-in-migh.patch | 12 +- ...-proper-LOCK_OFFSET-for-cond_resched.patch | 12 +- .../0112-sched-Disable-TTWU_QUEUE-on-RT.patch | 12 +- ...Only-wake-up-idle-workers-if-not-blo.patch | 12 +- ...ease-the-nr-of-migratory-tasks-when-.patch | 12 +- ...-hotplug-Lightweight-get-online-cpus.patch | 12 +- ...e-disabled-counter-to-tracing-output.patch | 14 +- .../0117-lockdep-Make-it-RT-aware.patch | 12 +- ...tasklets-from-going-into-infinite-sp.patch | 12 +- ...eemption-after-reenabling-interrupts.patch | 14 +- ...oftirq-Disable-softirq-stacks-for-RT.patch | 12 +- .../0121-softirq-Split-softirq-locks.patch | 12 +- ...-use-local_bh_disable-in-netif_rx_ni.patch | 14 +- ...abling-of-softirq-processing-in-irq-.patch | 20 +- ...plit-timer-softirqs-out-of-ksoftirqd.patch | 12 +- ...cal_softirq_pending-messages-if-ksof.patch | 12 +- ...cal_softirq_pending-messages-if-task.patch | 12 +- .../0127-rtmutex-trylock-is-okay-on-RT.patch | 12 +- ...-nfs-turn-rmdir_sem-into-a-semaphore.patch | 12 +- ...he-various-new-futex-race-conditions.patch | 12 +- ...on-when-a-requeued-RT-task-times-out.patch | 12 +- ...k-unlock-symetry-versus-pi_lock-and-.patch | 12 +- .../0132-pid.h-include-atomic.h.patch | 12 +- ...arm-include-definition-for-cpumask_t.patch | 12 +- ...ure-Do-NOT-include-rwlock.h-directly.patch | 12 +- ...35-rtmutex-Add-rtmutex_lock_killable.patch | 12 +- ...0136-rtmutex-Make-lock_killable-work.patch | 12 +- ...spinlock-Split-the-lock-types-header.patch | 12 +- .../0138-rtmutex-Avoid-include-hell.patch | 12 +- ...-rbtree-don-t-include-the-rcu-header.patch | 12 +- ...tex-Provide-rt_mutex_slowlock_locked.patch | 12 +- ...ockdep-less-version-of-rt_mutex-s-lo.patch | 12 +- ...tex-add-sleeping-lock-implementation.patch | 12 +- ...utex-implementation-based-on-rtmutex.patch | 12 +- ...wsem-implementation-based-on-rtmutex.patch | 12 +- ...lock-implementation-based-on-rtmutex.patch | 12 +- ...-preserve-state-like-a-sleeping-lock.patch | 12 +- .../0147-rtmutex-wire-up-RT-s-locking.patch | 12 +- ...utex-add-ww_mutex-addon-for-mutex-rt.patch | 12 +- .../0149-kconfig-Add-PREEMPT_RT_FULL.patch | 12 +- ...-fix-deadlock-in-device-mapper-block.patch | 12 +- ...utex-Flush-block-plug-on-__down_read.patch | 12 +- ...re-init-the-wait_lock-in-rt_mutex_in.patch | 12 +- ...ace-fix-ptrace-vs-tasklist_lock-race.patch | 12 +- ...mutex-annotate-sleeping-lock-context.patch | 12 +- ...sable-fallback-to-preempt_disable-in.patch | 12 +- ...eck-for-__LINUX_SPINLOCK_TYPES_H-on-.patch | 12 +- .../0157-rcu-Frob-softirq-test.patch | 12 +- ...58-rcu-Merge-RCU-bh-into-RCU-preempt.patch | 12 +- ...ke-ksoftirqd-do-RCU-quiescent-states.patch | 12 +- ...nate-softirq-processing-from-rcutree.patch | 12 +- ...-use-cpu_online-instead-custom-check.patch | 12 +- ...place-local_irqsave-with-a-locallock.patch | 12 +- ..._normal_after_boot-by-default-for-RT.patch | 12 +- ...erial-omap-Make-the-locking-RT-aware.patch | 12 +- ...al-pl011-Make-the-locking-work-on-RT.patch | 12 +- ...-explicitly-initialize-the-flags-var.patch | 12 +- ...mprove-the-serial-console-PASS_LIMIT.patch | 12 +- ...0-don-t-take-the-trylock-during-oops.patch | 12 +- ...wsem-Remove-preempt_disable-variants.patch | 12 +- ...ate_mm-by-preempt_-disable-enable-_r.patch | 12 +- ...back-explicit-INIT_HLIST_BL_HEAD-ini.patch | 12 +- ...e-preemption-on-i_dir_seq-s-write-si.patch | 12 +- ...e-of-local-lock-in-multi_cpu-decompr.patch | 12 +- ...rmal-Defer-thermal-wakups-to-threads.patch | 12 +- ...e-preemption-around-local_bh_disable.patch | 12 +- ...poll-Do-not-disable-preemption-on-RT.patch | 14 +- ...er-preempt-disable-region-which-suck.patch | 12 +- .../0178-block-mq-use-cpu_light.patch | 12 +- ...ock-mq-do-not-invoke-preempt_disable.patch | 12 +- ...k-mq-don-t-complete-requests-via-IPI.patch | 12 +- ...-Make-raid5_percpu-handling-RT-aware.patch | 18 +- .../0182-rt-Introduce-cpu_chill.patch | 12 +- ...rtimer-Don-t-lose-state-in-cpu_chill.patch | 12 +- ...chill-save-task-state-in-saved_state.patch | 12 +- ...e-blk_queue_usage_counter_release-in.patch | 12 +- ...-block-Use-cpu_chill-for-retry-loops.patch | 12 +- ...cache-Use-cpu_chill-in-trylock-loops.patch | 12 +- ...t-Use-cpu_chill-instead-of-cpu_relax.patch | 14 +- ...use-swait_queue-instead-of-waitqueue.patch | 12 +- .../0190-workqueue-Use-normal-rcu.patch | 12 +- ...cal-irq-lock-instead-of-irq-disable-.patch | 12 +- ...t-workqueue-versus-ata-piix-livelock.patch | 12 +- ...tangle-worker-accounting-from-rqlock.patch | 12 +- .../0194-debugobjects-Make-RT-aware.patch | 12 +- .../0195-seqlock-Prevent-rt-starvation.patch | 12 +- ...vc_xprt_do_enqueue-use-get_cpu_light.patch | 12 +- ...0197-net-Use-skbufhead-with-raw-lock.patch | 53 +--- ...recursion-to-per-task-variable-on-RT.patch | 16 +- ...y-to-delegate-processing-a-softirq-t.patch | 16 +- ...ake-qdisc-s-busylock-in-__dev_xmit_s.patch | 14 +- ...Qdisc-use-a-seqlock-instead-seqcount.patch | 12 +- ...-missing-serialization-in-ip_send_un.patch | 12 +- .../0203-net-add-a-lock-around-icmp_sk.patch | 12 +- ...schedule_irqoff-disable-interrupts-o.patch | 18 +- ...-push-most-work-into-softirq-context.patch | 18 +- .../0206-printk-Make-rt-aware.patch | 12 +- ...n-t-try-to-print-from-IRQ-NMI-region.patch | 12 +- ...intk-Drop-the-logbuf_lock-more-often.patch | 12 +- ...n-translation-section-permission-fau.patch | 12 +- ...-irq_set_irqchip_state-documentation.patch | 16 +- ...wngrade-preempt_disable-d-region-to-.patch | 12 +- ...-preemp_disable-in-addition-to-local.patch | 12 +- ...13-kgdb-serial-Short-term-workaround.patch | 12 +- ...-sysfs-Add-sys-kernel-realtime-entry.patch | 12 +- .../0215-mm-rt-kmap_atomic-scheduling.patch | 12 +- ...highmem-Add-a-already-used-pte-check.patch | 12 +- .../0217-arm-highmem-Flush-tlb-on-unmap.patch | 12 +- .../0218-arm-Enable-highmem-for-rt.patch | 12 +- .../0219-scsi-fcoe-Make-RT-aware.patch | 12 +- ...ypto-Reduce-preempt-disabled-regions.patch | 12 +- ...-preempt-disabled-regions-more-algos.patch | 12 +- ...ypto-limit-more-FPU-enabled-sections.patch | 12 +- ...-serialize-RT-percpu-scratch-buffer-.patch | 12 +- ...d-a-lock-instead-preempt_disable-loc.patch | 12 +- ...andom_bytes-for-RT_FULL-in-init_oops.patch | 12 +- ...ackprotector-Avoid-random-pool-on-rt.patch | 12 +- .../0227-random-Make-it-work-on-rt.patch | 26 +- ...28-cpu-hotplug-Implement-CPU-pinning.patch | 12 +- ...ed-user-tasks-to-be-awakened-to-the-.patch | 12 +- ...duct-tape-RT-rwlock-usage-for-non-RT.patch | 12 +- ...ove-preemption-disabling-in-netif_rx.patch | 14 +- ...r-local_irq_disable-kmalloc-headache.patch | 12 +- ...-users-of-napi_alloc_cache-against-r.patch | 12 +- ...rialize-xt_write_recseq-sections-on-.patch | 12 +- ...-Only-do-hardirq-context-test-for-ra.patch | 12 +- ...-fix-warnings-due-to-missing-PREEMPT.patch | 12 +- ...ched-Add-support-for-lazy-preemption.patch | 18 +- ...38-ftrace-Fix-trace-header-alignment.patch | 12 +- ...0239-x86-Support-for-lazy-preemption.patch | 12 +- ...-properly-check-against-preempt-mask.patch | 12 +- ...-use-proper-return-label-on-32bit-x8.patch | 12 +- ...-arm-Add-support-for-lazy-preemption.patch | 12 +- ...erpc-Add-support-for-lazy-preemption.patch | 12 +- ...-arch-arm64-Add-lazy-preempt-support.patch | 12 +- ...c-Protect-send_msg-with-a-local-lock.patch | 12 +- ...am-Replace-bit-spinlocks-with-rtmute.patch | 12 +- ...-t-disable-preemption-in-zcomp_strea.patch | 12 +- ...-zcomp_stream_get-smp_processor_id-u.patch | 12 +- ...49-tpm_tis-fix-stall-after-iowrite-s.patch | 12 +- ...t-deferral-of-watchdogd-wakeup-on-RT.patch | 25 +- ...Use-preempt_disable-enable_rt-where-.patch | 18 +- ...al_lock-unlock_irq-in-intel_pipe_upd.patch | 12 +- .../0253-drm-i915-disable-tracing-on-RT.patch | 12 +- ...M_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch | 12 +- ...roups-use-simple-wait-in-css_release.patch | 14 +- ...vert-callback_lock-to-raw_spinlock_t.patch | 12 +- ...-a-locallock-instead-preempt_disable.patch | 12 +- ...rkqueue-Prevent-deadlock-stall-on-RT.patch | 12 +- ...t-tasks-to-cache-one-sigqueue-struct.patch | 12 +- ...0260-Add-localversion-for-RT-release.patch | 12 +- ...iommu-Use-a-locallock-instead-local_.patch | 12 +- .../0262-powerpc-reshuffle-TIF-bits.patch | 12 +- ...-Convert-show_lock-to-raw_spinlock_t.patch | 12 +- ...isable-interrupts-independently-of-t.patch | 12 +- ...-Fix-a-lockup-in-wait_for_completion.patch | 12 +- ...6-kthread-add-a-global-worker-thread.patch | 18 +- ...-arm-imx6-cpuidle-Use-raw_spinlock_t.patch | 12 +- ...to-change-rcu_normal_after_boot-on-R.patch | 12 +- ...chtec-fix-stream_open.cocci-warnings.patch | 12 +- ...-Drop-a-preempt_disable_rt-statement.patch | 12 +- ...notification-of-canceling-timers-on-.patch | 262 +++++++++++++++--- ...ure-lock-unlock-symetry-versus-pi_lo.patch | 12 +- ...-bug-on-when-a-requeued-RT-task-time.patch | 12 +- ...andle-the-various-new-futex-race-con.patch | 12 +- ...karound-migrate_disable-enable-in-di.patch | 12 +- ...-Make-the-futex_hash_bucket-lock-raw.patch | 12 +- ...futex-Delay-deallocation-of-pi_state.patch | 12 +- ...disable-preemption-in-zswap_frontswa.patch | 12 +- debian/patches-rt/0279-revert-aio.patch | 12 +- .../0280-fs-aio-simple-simple-work.patch | 12 +- debian/patches-rt/0281-revert-thermal.patch | 12 +- ...rmal-Defer-thermal-wakups-to-threads.patch | 12 +- debian/patches-rt/0283-revert-block.patch | 12 +- ...e-blk_queue_usage_counter_release-in.patch | 12 +- debian/patches-rt/0285-workqueue-rework.patch | 18 +- ...0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch | 12 +- ...0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch | 12 +- ...nsure-inactive_timer-runs-in-hardirq.patch | 12 +- ...temp-make-pkg_temp_lock-a-raw-spinlo.patch | 12 +- ...lock_t-instread-disabling-preemption.patch | 12 +- ...t-the-timer-expire-in-hardirq-contex.patch | 12 +- ...k-preemption-level-before-looking-at.patch | 12 +- ..._ONCE-to-access-timer-base-in-hrimer.patch | 12 +- ...ab-the-expiry-lock-for-non-soft-hrti.patch | 12 +- ...using-hrtimer_grab_expiry_lock-on-mi.patch | 12 +- ...ssing-bracket-and-hide-migration_bas.patch | 12 +- ...lock-expiry-lock-in-the-early-return.patch | 12 +- ...s-enable-Use-sleeping_lock-to-annota.patch | 12 +- ..._allowed_ptr-Check-cpus_mask-not-cpu.patch | 12 +- ...Remove-dead-__migrate_disabled-check.patch | 12 +- ...e-disable-Protect-cpus_ptr-with-lock.patch | 12 +- ...processor_id-Don-t-use-cpumask_equal.patch | 12 +- ...utex_hash_bucket-spinlock_t-again-an.patch | 12 +- ...Clean-pi_blocked_on-in-the-error-cas.patch | 12 +- ...ib-ubsan-Don-t-seralize-UBSAN-report.patch | 12 +- ...the-lock-of-kmemleak_object-to-raw_s.patch | 12 +- ...igrate_enable-Use-select_fallback_rq.patch | 12 +- ...ched-Lazy-migrate_disable-processing.patch | 12 +- ...grate_enable-Use-stop_one_cpu_nowait.patch | 12 +- ...alize-split-page-table-locks-for-vec.patch | 12 +- ...nlock_t-and-rwlock_t-a-RCU-section-o.patch | 12 +- ...te_enable-must-access-takedown_cpu_t.patch | 12 +- ...r_id-Adjust-check_preemption_disable.patch | 12 +- ...able-Busy-loop-until-the-migration-r.patch | 12 +- ...fd-Use-a-seqlock-instead-of-seqcount.patch | 12 +- ...ate_enable-Use-per-cpu-cpu_stop_work.patch | 12 +- ...igrate_enable-Remove-__schedule-call.patch | 12 +- ...ve-misplaced-local_unlock_irqrestore.patch | 12 +- ...Include-header-for-the-current-macro.patch | 12 +- ...preempt_disable-in-vmw_fifo_ping_hos.patch | 12 +- ...empt_lazy-and-migrate_disable-counte.patch | 14 +- ...-flags-parameter-from-calls-to-ubsan.patch | 12 +- ...cking-of-IRQ_WORK_LAZY-flag-set-on-n.patch | 12 +- ...s-a-race-resulting-in-double-enqueue.patch | 12 +- ...c-for-when-grabbing-softirq_expiry_l.patch | 12 +- ...326-fs-dcache-Include-swait.h-header.patch | 12 +- ...lush-the-delayed-empty-slubs-in-flus.patch | 12 +- ...ix-UP-case-for-tasklet-CHAINED-state.patch | 12 +- .../0329-Linux-4.19.135-rt60-REBASE.patch | 24 -- ...l-Prevent-double-free-of-user-struct.patch | 58 ++++ ...e-sk_lock.slock-without-disabling-in.patch | 68 +++++ ...phy-fixed_phy-Remove-unused-seqcount.patch | 92 ++++++ ...compress-vs-decompress-serialization.patch | 105 +++++++ .../0333-Linux-4.19.142-rt63-REBASE.patch | 24 ++ debian/patches-rt/series | 6 +- 336 files changed, 2704 insertions(+), 2186 deletions(-) delete mode 100644 debian/patches-rt/0329-Linux-4.19.135-rt60-REBASE.patch create mode 100644 debian/patches-rt/0329-signal-Prevent-double-free-of-user-struct.patch create mode 100644 debian/patches-rt/0330-Bluetooth-Acquire-sk_lock.slock-without-disabling-in.patch create mode 100644 debian/patches-rt/0331-net-phy-fixed_phy-Remove-unused-seqcount.patch create mode 100644 debian/patches-rt/0332-net-xfrm-fix-compress-vs-decompress-serialization.patch create mode 100644 debian/patches-rt/0333-Linux-4.19.142-rt63-REBASE.patch diff --git a/debian/changelog b/debian/changelog index ed4281c21..27fe54e7f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -622,6 +622,7 @@ linux (4.19.142-1) UNRELEASED; urgency=medium list #1" for context changes in 4.19.142 * ACPI: configfs: Disallow loading ACPI tables when locked down (CVE-2020-15780) + * [rt] Update to 4.19.142-rt63 -- Salvatore Bonaccorso Tue, 04 Aug 2020 16:33:40 +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 54d806862..be56a77bd 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,9 +1,9 @@ -From 378ee68279f6a7631221f2670a9298620148690d Mon Sep 17 00:00:00 2001 -Message-Id: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 56457dc415803c8abc5acb513ada877a79596f05 Mon Sep 17 00:00:00 2001 +Message-Id: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:18 +0200 -Subject: [PATCH 001/329] ARM: at91: add TCB registers definitions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 001/333] ARM: at91: add TCB registers definitions +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Add registers and bits definitions for the timer counter blocks found on Atmel ARM SoCs. 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 c54f62fab..9ab026de7 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,12 +1,12 @@ -From 965acd390f989c4828cc2c363c5d2b5ba13788b7 Mon Sep 17 00:00:00 2001 -Message-Id: <965acd390f989c4828cc2c363c5d2b5ba13788b7.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1386a9166d814e8e5e8668ada3c3e00f997349aa Mon Sep 17 00:00:00 2001 +Message-Id: <1386a9166d814e8e5e8668ada3c3e00f997349aa.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:19 +0200 -Subject: [PATCH 002/329] clocksource/drivers: Add a new driver for the Atmel +Subject: [PATCH 002/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Add a driver for the Atmel Timer Counter Blocks. This driver provides a clocksource and two clockevent devices. 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 ab757fe1e..69c2d25ff 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,12 +1,12 @@ -From a4837437e5d30cac40a7601e491f2f2d39204d6a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f10cd782df082b35e5630ad1d91c9b396bdb40f6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:20 +0200 -Subject: [PATCH 003/329] clocksource/drivers: timer-atmel-tcb: add clockevent +Subject: [PATCH 003/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Add an other clockevent device that uses a separate TCB channel when available. 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 0aba26caa..a6e928050 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,11 +1,11 @@ -From 93345e1b63b69cd0c590ce777e203b06cf7bcb69 Mon Sep 17 00:00:00 2001 -Message-Id: <93345e1b63b69cd0c590ce777e203b06cf7bcb69.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 44798f501242577d14cb71a200a07359b48aaf04 Mon Sep 17 00:00:00 2001 +Message-Id: <44798f501242577d14cb71a200a07359b48aaf04.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:21 +0200 -Subject: [PATCH 004/329] clocksource/drivers: atmel-pit: make option silent -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 004/333] clocksource/drivers: atmel-pit: make option silent +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz To conform with the other option, make the ATMEL_PIT option silent so it can be selected from the platform 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 3d899b2c7..3db3fc0bb 100644 --- a/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch +++ b/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch @@ -1,11 +1,11 @@ -From f7c582cf48ef62e26df4240e10321a1e47ade705 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a281b6474c54382a42744ca86d1566ea5482950f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:22 +0200 -Subject: [PATCH 005/329] ARM: at91: Implement clocksource selection -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 005/333] ARM: at91: Implement clocksource selection +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Allow selecting and unselecting the PIT clocksource driver so it doesn't have to be compile when unused. 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 55c2cddb3..43b282f09 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,11 +1,11 @@ -From c90cec3fe051b5fdafcc85ebd1c51348ce7a37a0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1e235cc037da3ebb2c2e7c03a5b03b6dd927bed2 Mon Sep 17 00:00:00 2001 +Message-Id: <1e235cc037da3ebb2c2e7c03a5b03b6dd927bed2.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:23 +0200 -Subject: [PATCH 006/329] ARM: configs: at91: use new TCB timer driver -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 006/333] ARM: configs: at91: use new TCB timer driver +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Unselecting ATMEL_TCLIB switches the TCB timer driver from tcb_clksrc to timer-atmel-tcb. 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 e011dafa7..15b125ff6 100644 --- a/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch +++ b/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch @@ -1,11 +1,11 @@ -From f07baa3335ef764494f3f554e26878349a8ff49d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 751b975c1bf921792e1e9343571b04505615f7f7 Mon Sep 17 00:00:00 2001 +Message-Id: <751b975c1bf921792e1e9343571b04505615f7f7.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:24 +0200 -Subject: [PATCH 007/329] ARM: configs: at91: unselect PIT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 007/333] ARM: configs: at91: unselect PIT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 edd33d825..ba3d8d058 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,12 +1,12 @@ -From 5bd91a93666e2e1332ef72277afcf35207ba24f6 Mon Sep 17 00:00:00 2001 -Message-Id: <5bd91a93666e2e1332ef72277afcf35207ba24f6.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 92eb32113e64d756f7ea3b1e1c0c9c419e68ec6c Mon Sep 17 00:00:00 2001 +Message-Id: <92eb32113e64d756f7ea3b1e1c0c9c419e68ec6c.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Marc Zyngier Date: Fri, 27 Jul 2018 13:38:54 +0100 -Subject: [PATCH 008/329] irqchip/gic-v3-its: Move pending table allocation to +Subject: [PATCH 008/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Signed-off-by: Marc Zyngier Signed-off-by: Sebastian Andrzej Siewior @@ -16,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 fe7d63cdfb1d..937c94625c36 100644 +index d5cc32e80f5e..07a6ade2b39e 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); @@ -110,7 +110,7 @@ index fe7d63cdfb1d..937c94625c36 100644 } static void its_cpu_init_collection(struct its_node *its) -@@ -3591,16 +3613,6 @@ static int redist_disable_lpis(void) +@@ -3594,16 +3616,6 @@ static int redist_disable_lpis(void) u64 timeout = USEC_PER_SEC; u64 val; @@ -127,7 +127,7 @@ index fe7d63cdfb1d..937c94625c36 100644 if (!gic_rdists_supports_plpis()) { pr_info("CPU%d: LPIs not supported\n", smp_processor_id()); return -ENXIO; -@@ -3610,7 +3622,18 @@ static int redist_disable_lpis(void) +@@ -3613,7 +3625,18 @@ static int redist_disable_lpis(void) if (!(val & GICR_CTLR_ENABLE_LPIS)) return 0; @@ -147,7 +147,7 @@ index fe7d63cdfb1d..937c94625c36 100644 smp_processor_id()); add_taint(TAINT_CRAP, LOCKDEP_STILL_OK); -@@ -3866,7 +3889,8 @@ int __init its_init(struct fwnode_handle *handle, struct rdists *rdists, +@@ -3869,7 +3892,8 @@ int __init its_init(struct fwnode_handle *handle, struct rdists *rdists, } gic_rdists = rdists; 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 e170dff6c..0902e5617 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,11 +1,11 @@ -From 436c3539b5d3b39dccf769a3627cb94ecb075698 Mon Sep 17 00:00:00 2001 -Message-Id: <436c3539b5d3b39dccf769a3627cb94ecb075698.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f2e676094d02b759c2b71d4e059e7dbf254ef3c4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 -Subject: [PATCH 009/329] kthread: convert worker lock to raw spinlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 009/333] kthread: convert worker lock to raw spinlock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -39,10 +39,10 @@ index c1961761311d..ad292898f7f2 100644 struct list_head delayed_work_list; struct task_struct *task; diff --git a/kernel/kthread.c b/kernel/kthread.c -index 087d18d771b5..5641b55783a6 100644 +index b786eda90bb5..81aa14daa5fe 100644 --- a/kernel/kthread.c +++ b/kernel/kthread.c -@@ -599,7 +599,7 @@ void __kthread_init_worker(struct kthread_worker *worker, +@@ -612,7 +612,7 @@ void __kthread_init_worker(struct kthread_worker *worker, struct lock_class_key *key) { memset(worker, 0, sizeof(struct kthread_worker)); @@ -51,7 +51,7 @@ index 087d18d771b5..5641b55783a6 100644 lockdep_set_class_and_name(&worker->lock, key, name); INIT_LIST_HEAD(&worker->work_list); INIT_LIST_HEAD(&worker->delayed_work_list); -@@ -641,21 +641,21 @@ int kthread_worker_fn(void *worker_ptr) +@@ -654,21 +654,21 @@ int kthread_worker_fn(void *worker_ptr) if (kthread_should_stop()) { __set_current_state(TASK_RUNNING); @@ -77,7 +77,7 @@ index 087d18d771b5..5641b55783a6 100644 if (work) { __set_current_state(TASK_RUNNING); -@@ -812,12 +812,12 @@ bool kthread_queue_work(struct kthread_worker *worker, +@@ -825,12 +825,12 @@ bool kthread_queue_work(struct kthread_worker *worker, bool ret = false; unsigned long flags; @@ -92,7 +92,7 @@ index 087d18d771b5..5641b55783a6 100644 return ret; } EXPORT_SYMBOL_GPL(kthread_queue_work); -@@ -843,7 +843,7 @@ void kthread_delayed_work_timer_fn(struct timer_list *t) +@@ -856,7 +856,7 @@ void kthread_delayed_work_timer_fn(struct timer_list *t) if (WARN_ON_ONCE(!worker)) return; @@ -101,7 +101,7 @@ index 087d18d771b5..5641b55783a6 100644 /* Work must not be used with >1 worker, see kthread_queue_work(). */ WARN_ON_ONCE(work->worker != worker); -@@ -852,7 +852,7 @@ void kthread_delayed_work_timer_fn(struct timer_list *t) +@@ -865,7 +865,7 @@ void kthread_delayed_work_timer_fn(struct timer_list *t) list_del_init(&work->node); kthread_insert_work(worker, work, &worker->work_list); @@ -110,7 +110,7 @@ index 087d18d771b5..5641b55783a6 100644 } EXPORT_SYMBOL(kthread_delayed_work_timer_fn); -@@ -908,14 +908,14 @@ bool kthread_queue_delayed_work(struct kthread_worker *worker, +@@ -921,14 +921,14 @@ bool kthread_queue_delayed_work(struct kthread_worker *worker, unsigned long flags; bool ret = false; @@ -127,7 +127,7 @@ index 087d18d771b5..5641b55783a6 100644 return ret; } EXPORT_SYMBOL_GPL(kthread_queue_delayed_work); -@@ -951,7 +951,7 @@ void kthread_flush_work(struct kthread_work *work) +@@ -964,7 +964,7 @@ void kthread_flush_work(struct kthread_work *work) if (!worker) return; @@ -136,7 +136,7 @@ index 087d18d771b5..5641b55783a6 100644 /* Work must not be used with >1 worker, see kthread_queue_work(). */ WARN_ON_ONCE(work->worker != worker); -@@ -963,7 +963,7 @@ void kthread_flush_work(struct kthread_work *work) +@@ -976,7 +976,7 @@ void kthread_flush_work(struct kthread_work *work) else noop = true; @@ -145,7 +145,7 @@ index 087d18d771b5..5641b55783a6 100644 if (!noop) wait_for_completion(&fwork.done); -@@ -996,9 +996,9 @@ static bool __kthread_cancel_work(struct kthread_work *work, bool is_dwork, +@@ -1009,9 +1009,9 @@ static bool __kthread_cancel_work(struct kthread_work *work, bool is_dwork, * any queuing is blocked by setting the canceling counter. */ work->canceling++; @@ -157,7 +157,7 @@ index 087d18d771b5..5641b55783a6 100644 work->canceling--; } -@@ -1045,7 +1045,7 @@ bool kthread_mod_delayed_work(struct kthread_worker *worker, +@@ -1058,7 +1058,7 @@ bool kthread_mod_delayed_work(struct kthread_worker *worker, unsigned long flags; int ret = false; @@ -166,7 +166,7 @@ index 087d18d771b5..5641b55783a6 100644 /* Do not bother with canceling when never queued. */ if (!work->worker) -@@ -1062,7 +1062,7 @@ bool kthread_mod_delayed_work(struct kthread_worker *worker, +@@ -1075,7 +1075,7 @@ bool kthread_mod_delayed_work(struct kthread_worker *worker, fast_queue: __kthread_queue_delayed_work(worker, dwork, delay); out: @@ -175,7 +175,7 @@ index 087d18d771b5..5641b55783a6 100644 return ret; } EXPORT_SYMBOL_GPL(kthread_mod_delayed_work); -@@ -1076,7 +1076,7 @@ static bool __kthread_cancel_work_sync(struct kthread_work *work, bool is_dwork) +@@ -1089,7 +1089,7 @@ static bool __kthread_cancel_work_sync(struct kthread_work *work, bool is_dwork) if (!worker) goto out; @@ -184,7 +184,7 @@ index 087d18d771b5..5641b55783a6 100644 /* Work must not be used with >1 worker, see kthread_queue_work(). */ WARN_ON_ONCE(work->worker != worker); -@@ -1090,13 +1090,13 @@ static bool __kthread_cancel_work_sync(struct kthread_work *work, bool is_dwork) +@@ -1103,13 +1103,13 @@ static bool __kthread_cancel_work_sync(struct kthread_work *work, bool is_dwork) * In the meantime, block any queuing by setting the canceling counter. */ work->canceling++; 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 cf7f9b08b..743451644 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,14 +1,14 @@ -From d95c42605a6295992e066a29cb8e7ec96d58978f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 84cdd070b9fb0b9c7f4bb65488f762fa2dafda23 Mon Sep 17 00:00:00 2001 +Message-Id: <84cdd070b9fb0b9c7f4bb65488f762fa2dafda23.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: =?UTF-8?q?Horia=20Geant=C4=83?= Date: Mon, 8 Oct 2018 14:09:37 +0300 -Subject: [PATCH 010/329] crypto: caam/qi - simplify CGR allocation, freeing +Subject: [PATCH 010/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [Upstream commit 29e83c757006fd751966bdc53392bb22d74179c6] 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 e9d151ae1..1f533e815 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,11 +1,11 @@ -From 4e2c3189e75ee0f047d79efd36f66b7fdcc65504 Mon Sep 17 00:00:00 2001 -Message-Id: <4e2c3189e75ee0f047d79efd36f66b7fdcc65504.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From bcaca4b50d79502c7c866224a456cbeaf0a12985 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 7 Jan 2019 13:52:31 +0100 -Subject: [PATCH 011/329] sched/fair: Robustify CFS-bandwidth timer locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 011/333] sched/fair: Robustify CFS-bandwidth timer locking +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Traditionally hrtimer callbacks were run with IRQs disabled, but with the introduction of HRTIMER_MODE_SOFT it is possible they run from @@ -33,7 +33,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index d8c249e6dcb7..4665c6c03292 100644 +index 696d08a4593e..63a630f8dd1e 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4597,7 +4597,7 @@ static u64 distribute_cfs_runtime(struct cfs_bandwidth *cfs_b, u64 remaining) 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 dd4854d5a..d8abc6ddd 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,11 +1,11 @@ -From 865f8ddda5b9fc471bbf7c080c06e72062b9dc36 Mon Sep 17 00:00:00 2001 -Message-Id: <865f8ddda5b9fc471bbf7c080c06e72062b9dc36.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 442c231ef3f6c252ecc0852dba6371ce1af38943 Mon Sep 17 00:00:00 2001 +Message-Id: <442c231ef3f6c252ecc0852dba6371ce1af38943.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Frank Rowand Date: Mon, 19 Sep 2011 14:51:14 -0700 -Subject: [PATCH 012/329] arm: Convert arm boot_lock to raw -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 012/333] arm: Convert arm boot_lock to raw +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 e649ba69e..fb7f39541 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,12 +1,12 @@ -From 9862698c10d9149c9a71c22c0f34ffd4781143c6 Mon Sep 17 00:00:00 2001 -Message-Id: <9862698c10d9149c9a71c22c0f34ffd4781143c6.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8c88968fef0adbe6298376208fdf9ac5ad03a2f9 Mon Sep 17 00:00:00 2001 +Message-Id: <8c88968fef0adbe6298376208fdf9ac5ad03a2f9.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 17 Jul 2018 18:25:31 +0200 -Subject: [PATCH 013/329] x86/ioapic: Don't let setaffinity unmask threaded EOI +Subject: [PATCH 013/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz There is an issue with threaded interrupts which are marked ONESHOT and using the fasteoi handler. @@ -38,7 +38,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c -index 08e2f3a5f124..c3978452c49b 100644 +index 95e21c438012..53590eea257b 100644 --- a/arch/x86/kernel/apic/io_apic.c +++ b/arch/x86/kernel/apic/io_apic.c @@ -1722,7 +1722,7 @@ static bool io_apic_level_ack_pending(struct mp_chip_data *data) 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 c404b5669..1c7c9a476 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,11 +1,11 @@ -From 0f967f53b47a147c58857b9e76845cc842377c4f Mon Sep 17 00:00:00 2001 -Message-Id: <0f967f53b47a147c58857b9e76845cc842377c4f.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3f210fbaeb5391ebe07fc41c9033f363059c724e Mon Sep 17 00:00:00 2001 +Message-Id: <3f210fbaeb5391ebe07fc41c9033f363059c724e.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 18:19:48 +0200 -Subject: [PATCH 014/329] cgroup: use irqsave in cgroup_rstat_flush_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 014/333] cgroup: use irqsave in cgroup_rstat_flush_locked() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz All callers of cgroup_rstat_flush_locked() acquire cgroup_rstat_lock either with spin_lock_irq() or spin_lock_irqsave(). 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 665cc76fc..3e867d154 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,11 +1,11 @@ -From 0051d62d6d49a02db52d948335e9f5024cf73fa6 Mon Sep 17 00:00:00 2001 -Message-Id: <0051d62d6d49a02db52d948335e9f5024cf73fa6.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8cc9dad85fa770aa977dd40a32d1c3035f382464 Mon Sep 17 00:00:00 2001 +Message-Id: <8cc9dad85fa770aa977dd40a32d1c3035f382464.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 3 Jul 2018 13:34:30 -0500 -Subject: [PATCH 015/329] fscache: initialize cookie hash table raw spinlocks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 015/333] fscache: initialize cookie hash table raw spinlocks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 6d0321433..b46fa76ab 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,14 +1,14 @@ -From c19335c8a6df13f2b73b8abf58d9f14ca725715f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a9d3e70754106d9ac97545cdee07fc314d8d1bdb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 Aug 2018 21:59:04 +0200 -Subject: [PATCH 016/329] Drivers: hv: vmbus: include header for get_irq_regs() +Subject: [PATCH 016/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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: 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 30631b457..e93c9f72c 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,11 +1,11 @@ -From f2b2f9460d69551ea290a63a7e45e017b04add58 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 07c81c26e9fcf6e4e726398981a575b84e11d114 Mon Sep 17 00:00:00 2001 +Message-Id: <07c81c26e9fcf6e4e726398981a575b84e11d114.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 11 Oct 2018 16:39:59 +0200 -Subject: [PATCH 017/329] 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.135-rt60.tar.xz +Subject: [PATCH 017/333] 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.142-rt63.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 diff --git a/debian/patches-rt/0018-efi-Allow-efi-runtime.patch b/debian/patches-rt/0018-efi-Allow-efi-runtime.patch index 7a319f62d..e1fa1b989 100644 --- a/debian/patches-rt/0018-efi-Allow-efi-runtime.patch +++ b/debian/patches-rt/0018-efi-Allow-efi-runtime.patch @@ -1,11 +1,11 @@ -From 75f0aa39a3a6ffc854e325be51913e161dc7b10a Mon Sep 17 00:00:00 2001 -Message-Id: <75f0aa39a3a6ffc854e325be51913e161dc7b10a.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8eb70a9382b675bcaa2018d7f3a4258a8df2a5cc Mon Sep 17 00:00:00 2001 +Message-Id: <8eb70a9382b675bcaa2018d7f3a4258a8df2a5cc.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:06:10 +0200 -Subject: [PATCH 018/329] efi: Allow efi=runtime -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 018/333] efi: Allow efi=runtime +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. @@ -17,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 de1bc38ab39f..22cf4dd07b03 100644 +index a8180f9090fa..263459bc4d14 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) 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 de3f00741..ea0be78ef 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,11 +1,11 @@ -From 28a1e1b3e8ec3632df3d230bcfd2bc885a4c8512 Mon Sep 17 00:00:00 2001 -Message-Id: <28a1e1b3e8ec3632df3d230bcfd2bc885a4c8512.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f2bcb7af52876669f929624f5d9971cf942cf3fc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 24 Jul 2018 14:48:55 +0200 -Subject: [PATCH 019/329] 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.135-rt60.tar.xz +Subject: [PATCH 019/333] 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.142-rt63.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 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 14e134305..a67d315a0 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,12 +1,12 @@ -From 7130507c8f5a29402c5361c526def1ea1c492e5f Mon Sep 17 00:00:00 2001 -Message-Id: <7130507c8f5a29402c5361c526def1ea1c492e5f.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ce3aeb76f778a401f356a534e77d0964a5f3b2cb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 09:13:42 +0200 -Subject: [PATCH 020/329] arm64: KVM: compute_layout before altenates are +Subject: [PATCH 020/333] arm64: KVM: compute_layout before altenates are applied -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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(). @@ -21,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 3 files changed, 8 insertions(+), 6 deletions(-) diff --git a/arch/arm64/include/asm/alternative.h b/arch/arm64/include/asm/alternative.h -index 849d891c60a8..02064155e1b3 100644 +index 844f05b23115..04b950d4c7f5 100644 --- a/arch/arm64/include/asm/alternative.h +++ b/arch/arm64/include/asm/alternative.h @@ -35,6 +35,12 @@ void apply_alternatives_module(void *start, size_t length); 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 3f516e175..438317364 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,12 +1,12 @@ -From 09fb2688bce798d653e25c1d01566b4490b544eb Mon Sep 17 00:00:00 2001 -Message-Id: <09fb2688bce798d653e25c1d01566b4490b544eb.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9d829d94da0a654cb00678e64c3ef938ad6163ec Mon Sep 17 00:00:00 2001 +Message-Id: <9d829d94da0a654cb00678e64c3ef938ad6163ec.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 31 Aug 2018 14:16:30 +0200 -Subject: [PATCH 021/329] of: allocate / free phandle cache outside of the +Subject: [PATCH 021/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 8bab04800..804ea392b 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,11 +1,11 @@ -From 8ef99f3b1883c99b24bb07d010ff17bf045c8bf5 Mon Sep 17 00:00:00 2001 -Message-Id: <8ef99f3b1883c99b24bb07d010ff17bf045c8bf5.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 596e4af88ce09c8ce25db296e97b85e6efc9c4d5 Mon Sep 17 00:00:00 2001 +Message-Id: <596e4af88ce09c8ce25db296e97b85e6efc9c4d5.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 18 Sep 2018 10:29:31 -0500 -Subject: [PATCH 022/329] 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.135-rt60.tar.xz +Subject: [PATCH 022/333] 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.142-rt63.tar.xz The static lock quarantine_lock is used in quarantine.c to protect the quarantine queue datastructures. It is taken inside quarantine queue 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 4a8acaa06..f8fc22f99 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,12 +1,12 @@ -From dd173d3ecc5f2d30bb8563ff03ad65cc424b7a59 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From af4a2e46155433d2bedb18552ce8ed7ff6e36c02 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 29 Oct 2018 11:53:01 +0100 -Subject: [PATCH 023/329] EXP rcu: Revert expedited GP parallelization +Subject: [PATCH 023/333] EXP rcu: Revert expedited GP parallelization cleverness -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz (Commit 258ba8e089db23f760139266c232f01bad73f85c from linux-rcu) 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 dca3fb848..7ec284b6b 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,14 +1,14 @@ -From 0c800bec45fabc7662e22ff337d1771b183e893e Mon Sep 17 00:00:00 2001 -Message-Id: <0c800bec45fabc7662e22ff337d1771b183e893e.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a29374fce5fdeb9b1694be13e5a287657b71683c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: He Zhe Date: Wed, 19 Dec 2018 16:30:57 +0100 -Subject: [PATCH 024/329] kmemleak: Turn kmemleak_lock to raw spinlock on RT +Subject: [PATCH 024/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz kmemleak_lock, as a rwlock on RT, can possibly be held in atomic context and causes the follow BUG. 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 fc17c5541..f93ad2ccc 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,11 +1,11 @@ -From c873c16b68def8fbba678def5b7bd2712e826f83 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8489411ca761c3decfbe15f177d17ffe92bd0679 Mon Sep 17 00:00:00 2001 +Message-Id: <8489411ca761c3decfbe15f177d17ffe92bd0679.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 28 Oct 2016 23:05:11 +0200 -Subject: [PATCH 025/329] NFSv4: replace seqcount_t with a seqlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 025/333] NFSv4: replace seqcount_t with a seqlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -61,7 +61,7 @@ index 5b61520dce88..2771aafaca19 100644 }; diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c -index 05cb68ca1ba1..3e8666aa6829 100644 +index 1ef75b1deffa..44438814b662 100644 --- a/fs/nfs/nfs4proc.c +++ b/fs/nfs/nfs4proc.c @@ -2870,7 +2870,7 @@ static int _nfs4_open_and_get_state(struct nfs4_opendata *opendata, 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 db7251578..51cbe1c82 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,15 +1,15 @@ -From 88f6158fd18709b5d03549be2807845859394129 Mon Sep 17 00:00:00 2001 -Message-Id: <88f6158fd18709b5d03549be2807845859394129.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e0d5cb4f381bc31eea602eda721126a0a09c2e2f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Apr 2017 12:50:16 +0200 -Subject: [PATCH 026/329] kernel: sched: Provide a pointer to the valid CPU +Subject: [PATCH 026/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -576,7 +576,7 @@ index 8aecfb143859..311b3cf1270e 100644 !dl_task(task) || !task_on_rq_queued(task))) { diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index 4665c6c03292..80289617ce3d 100644 +index 63a630f8dd1e..2443f921b19f 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -1691,7 +1691,7 @@ static void task_numa_compare(struct task_numa_env *env, @@ -745,10 +745,10 @@ index b980cc96604f..b6ca4a630050 100644 !rt_task(task) || !task_on_rq_queued(task))) { diff --git a/kernel/trace/trace_hwlat.c b/kernel/trace/trace_hwlat.c -index 8030e24dbf14..862f4b0139fc 100644 +index 568918fae8d4..35512ed26d9f 100644 --- a/kernel/trace/trace_hwlat.c +++ b/kernel/trace/trace_hwlat.c -@@ -279,7 +279,7 @@ static void move_to_next_cpu(void) +@@ -280,7 +280,7 @@ static void move_to_next_cpu(void) * of this thread, than stop migrating for the duration * of the current test. */ 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 a713622f4..03e2c31af 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,11 +1,11 @@ -From c6aabaf2f8225455297c0309233fa485c8bc7fd3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 03c40b401fbbb4ea7bbc4bc90e62dce5ba2521ae Mon Sep 17 00:00:00 2001 +Message-Id: <03c40b401fbbb4ea7bbc4bc90e62dce5ba2521ae.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 -Subject: [PATCH 027/329] kernel/sched/core: add migrate_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 027/333] kernel/sched/core: add migrate_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz --- include/linux/preempt.h | 23 +++++++ 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 7764ecd9a..1536c26cd 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,12 +1,12 @@ -From 327d4be878fe3153861c000211b5b7dad3c91111 Mon Sep 17 00:00:00 2001 -Message-Id: <327d4be878fe3153861c000211b5b7dad3c91111.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9d392927a31ae6d07d33380430eacb483eac1f3f Mon Sep 17 00:00:00 2001 +Message-Id: <9d392927a31ae6d07d33380430eacb483eac1f3f.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 9 Oct 2018 17:34:50 +0200 -Subject: [PATCH 028/329] sched/migrate_disable: Add export_symbol_gpl for +Subject: [PATCH 028/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Jonathan reported that lttng/modules can't use __migrate_disabled(). This function is only used by sched/core itself and the tracing 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 a04d08395..c9334cfd3 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,11 +1,11 @@ -From 21a8607e3ac87d41524400aa9e076db312e261ff Mon Sep 17 00:00:00 2001 -Message-Id: <21a8607e3ac87d41524400aa9e076db312e261ff.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 16e7a58f46f74dcc5d206bb48fa3b3abd7aef5b3 Mon Sep 17 00:00:00 2001 +Message-Id: <16e7a58f46f74dcc5d206bb48fa3b3abd7aef5b3.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Mar 2016 10:51:06 +0100 -Subject: [PATCH 029/329] 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.135-rt60.tar.xz +Subject: [PATCH 029/333] 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.142-rt63.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. 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 b8b5b6036..25dbe15bc 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,15 +1,15 @@ -From 6cbc59ebdedbb6bd37674dbb550981dcc81ba140 Mon Sep 17 00:00:00 2001 -Message-Id: <6cbc59ebdedbb6bd37674dbb550981dcc81ba140.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1407a2d6268fc6167191af84956c83362741db73 Mon Sep 17 00:00:00 2001 +Message-Id: <1407a2d6268fc6167191af84956c83362741db73.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Benedikt Spranger Date: Mon, 8 Mar 2010 18:57:04 +0100 -Subject: [PATCH 030/329] clocksource: TCLIB: Allow higher clock rates for +Subject: [PATCH 030/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. diff --git a/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch b/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch index 867927d93..4cf73ed3c 100644 --- a/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch +++ b/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch @@ -1,11 +1,11 @@ -From c7b1c3d119e7b79eff59e2e1d7ad37e563dfd44d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b04eca645fe46127aa5b7f300bfd6b0be614a899 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 14 Feb 2013 22:36:59 +0100 -Subject: [PATCH 031/329] timekeeping: Split jiffies seqlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 031/333] timekeeping: Split jiffies seqlock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Replace jiffies_lock seqlock with a simple seqcounter and a rawlock so it can be taken in atomic context on RT. 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 b2acee166..1c32824b1 100644 --- a/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch +++ b/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch @@ -1,11 +1,11 @@ -From 84a22c05e9c7875ad6465dd1e4960fb7f263fd0c Mon Sep 17 00:00:00 2001 -Message-Id: <84a22c05e9c7875ad6465dd1e4960fb7f263fd0c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9534050d3bbfbdc09211434ea2557770502bfcd9 Mon Sep 17 00:00:00 2001 +Message-Id: <9534050d3bbfbdc09211434ea2557770502bfcd9.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 21 Sep 2011 19:57:12 +0200 -Subject: [PATCH 032/329] signal: Revert ptrace preempt magic -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 032/333] signal: Revert ptrace preempt magic +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Upstream commit '53da1d9456fe7f8 fix ptrace slowness' is nothing more than a bandaid around the ptrace design trainwreck. It's not a 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 b960cfbee..35c8321a5 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,11 +1,11 @@ -From c110ab27bbd2b2c2eac4ded87343ee5d42346b54 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9011d119566cab11d71a676c0243b775f4e812c1 Mon Sep 17 00:00:00 2001 +Message-Id: <9011d119566cab11d71a676c0243b775f4e812c1.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Marc Kleine-Budde Date: Wed, 5 Mar 2014 00:49:47 +0100 -Subject: [PATCH 033/329] net: sched: Use msleep() instead of yield() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 033/333] net: sched: Use msleep() instead of yield() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 0e0b4816f..c28056fe1 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,11 +1,11 @@ -From cc7b16e6616fa85c9349dd2eb9799b3748863aac Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f5e867d66ac23b11e8c7fbcc178fa5b58102b702 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 27 Mar 2018 16:24:15 +0200 -Subject: [PATCH 034/329] dm rq: remove BUG_ON(!irqs_disabled) check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 034/333] dm rq: remove BUG_ON(!irqs_disabled) check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz In commit 052189a2ec95 ("dm: remove superfluous irq disablement in dm_request_fn") the spin_lock_irq() was replaced with spin_lock() + a @@ -24,10 +24,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 deletion(-) diff --git a/drivers/md/dm-rq.c b/drivers/md/dm-rq.c -index 4d36373e1c0f..12ed08245130 100644 +index 9fde174ce396..e6bffe4b9439 100644 --- a/drivers/md/dm-rq.c +++ b/drivers/md/dm-rq.c -@@ -692,7 +692,6 @@ static void dm_old_request_fn(struct request_queue *q) +@@ -689,7 +689,6 @@ static void dm_old_request_fn(struct request_queue *q) /* Establish tio->ti before queuing work (map_tio_request) */ tio->ti = ti; kthread_queue_work(&md->kworker, &tio->work); 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 9341cca3f..66909c9f5 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,11 +1,11 @@ -From 552d07429e80cd7b1d6d87fe0d61bdd35a9d5a5f Mon Sep 17 00:00:00 2001 -Message-Id: <552d07429e80cd7b1d6d87fe0d61bdd35a9d5a5f.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From c3164dc24e24917688c9873da74a822427f3e855 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 8 Nov 2013 17:34:54 +0100 -Subject: [PATCH 035/329] usb: do no disable interrupts in giveback -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 035/333] usb: do no disable interrupts in giveback +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Since commit 94dfd7ed ("USB: HCD: support giveback of URB in tasklet context") the USB code disables interrupts before invoking the complete 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 5f403ea27..8984c74c9 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,11 +1,11 @@ -From 82f11a5600cdb8585441eeced935fd48121a2ea7 Mon Sep 17 00:00:00 2001 -Message-Id: <82f11a5600cdb8585441eeced935fd48121a2ea7.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8a0bb4073247b199c6fb755b2bda41e635bdf97d Mon Sep 17 00:00:00 2001 +Message-Id: <8a0bb4073247b199c6fb755b2bda41e635bdf97d.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 17 Jun 2011 12:39:57 +0200 -Subject: [PATCH 036/329] rt: Provide PREEMPT_RT_BASE config switch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 036/333] rt: Provide PREEMPT_RT_BASE config switch +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Introduce PREEMPT_RT_BASE which enables parts of PREEMPT_RT_FULL. Forces interrupt threading and enables some of the RT 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 1001cd83c..bacb0a755 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,11 +1,11 @@ -From 69dd1016823043f0c84a17ec7ecf0d684cdd6f95 Mon Sep 17 00:00:00 2001 -Message-Id: <69dd1016823043f0c84a17ec7ecf0d684cdd6f95.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2331c2c20cae90d621093ce304b3531dfd853d7e Mon Sep 17 00:00:00 2001 +Message-Id: <2331c2c20cae90d621093ce304b3531dfd853d7e.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 14 Dec 2011 01:03:49 +0100 -Subject: [PATCH 037/329] cpumask: Disable CONFIG_CPUMASK_OFFSTACK for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 037/333] cpumask: Disable CONFIG_CPUMASK_OFFSTACK for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz There are "valid" GFP_ATOMIC allocations such as 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 e133b2e6d..65c974136 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,11 +1,11 @@ -From 14aff7b583613ece34543f3458216a94c1a0df0c Mon Sep 17 00:00:00 2001 -Message-Id: <14aff7b583613ece34543f3458216a94c1a0df0c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 7a3061c4f862b69c736af01c0db821498af332c1 Mon Sep 17 00:00:00 2001 +Message-Id: <7a3061c4f862b69c736af01c0db821498af332c1.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Jul 2015 17:14:48 +0200 -Subject: [PATCH 038/329] jump-label: disable if stop_machine() is used -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 038/333] jump-label: disable if stop_machine() is used +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Some architectures are using stop_machine() while switching the opcode which leads to latency spikes. 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 714daa2b4..d23b0b369 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,12 +1,12 @@ -From e015cf61deaff432c4c48275a462077c72df3c3e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 983f8298c5f0779a7634fa352e342a4ce7ad4a0a Mon Sep 17 00:00:00 2001 +Message-Id: <983f8298c5f0779a7634fa352e342a4ce7ad4a0a.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 24 Jul 2011 12:11:43 +0200 -Subject: [PATCH 039/329] kconfig: Disable config options which are not RT +Subject: [PATCH 039/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Disable stuff which is known to have issues on RT diff --git a/debian/patches-rt/0040-lockdep-disable-self-test.patch b/debian/patches-rt/0040-lockdep-disable-self-test.patch index 97885185f..d5444a63d 100644 --- a/debian/patches-rt/0040-lockdep-disable-self-test.patch +++ b/debian/patches-rt/0040-lockdep-disable-self-test.patch @@ -1,14 +1,14 @@ -From 5eb5969abd57284025ae4254d3903db0dd6358b0 Mon Sep 17 00:00:00 2001 -Message-Id: <5eb5969abd57284025ae4254d3903db0dd6358b0.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ba6a1434bba9d9e31eade3e876bd0832f0947e98 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 17 Oct 2017 16:36:18 +0200 -Subject: [PATCH 040/329] lockdep: disable self-test +Subject: [PATCH 040/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 5965be45e..93e0438d3 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,11 +1,11 @@ -From 75e8e99566245484bb4121f470e15b5de738afde Mon Sep 17 00:00:00 2001 -Message-Id: <75e8e99566245484bb4121f470e15b5de738afde.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 4e96a586e2aea42f3b1bf47333d9b3c208f49687 Mon Sep 17 00:00:00 2001 +Message-Id: <4e96a586e2aea42f3b1bf47333d9b3c208f49687.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:44:03 -0500 -Subject: [PATCH 041/329] mm: Allow only slub on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 041/333] mm: Allow only slub on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Disable SLAB and SLOB on -RT. Only SLUB is adopted to -RT needs. 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 e729676f9..cc192393e 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,14 +1,14 @@ -From 456301f31a3d91d8a89c8b2b3c8f9c7ffeb332b8 Mon Sep 17 00:00:00 2001 -Message-Id: <456301f31a3d91d8a89c8b2b3c8f9c7ffeb332b8.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3c2fbe75f8d09dfb0df20db0768d8c3f5263a92f Mon Sep 17 00:00:00 2001 +Message-Id: <3c2fbe75f8d09dfb0df20db0768d8c3f5263a92f.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:51:45 +0200 -Subject: [PATCH 042/329] locking: Disable spin on owner for RT +Subject: [PATCH 042/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Drop spin on owner for mutex / rwsem. We are most likely not using it but… 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 cea8007fb..9f82de543 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,11 +1,11 @@ -From 1fd9b737374cbbc250831d4a21e8def84743299c Mon Sep 17 00:00:00 2001 -Message-Id: <1fd9b737374cbbc250831d4a21e8def84743299c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 790b2ab08c1c29364fe55eff153eb15cc8434526 Mon Sep 17 00:00:00 2001 +Message-Id: <790b2ab08c1c29364fe55eff153eb15cc8434526.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 13:26:09 +0000 -Subject: [PATCH 043/329] rcu: Disable RCU_FAST_NO_HZ on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 043/333] rcu: Disable RCU_FAST_NO_HZ on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz This uses a timer_list timer from the irq disabled guts of the idle code. Disable it for now to prevent wreckage. 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 e7a2b60ce..72dc16296 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,11 +1,11 @@ -From 9c14b48cadd85fa31494520009df855bf2b4d6a9 Mon Sep 17 00:00:00 2001 -Message-Id: <9c14b48cadd85fa31494520009df855bf2b4d6a9.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 82a2f625d9adc2a557c6b4dbe4a4ea50849723c6 Mon Sep 17 00:00:00 2001 +Message-Id: <82a2f625d9adc2a557c6b4dbe4a4ea50849723c6.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Mar 2014 20:19:05 +0100 -Subject: [PATCH 044/329] rcu: make RCU_BOOST default on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 044/333] rcu: make RCU_BOOST default on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 258060923..52548276f 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,11 +1,11 @@ -From 09cf710fc64a9e6c7d99ccdb3e3e10f3b86e5eb7 Mon Sep 17 00:00:00 2001 -Message-Id: <09cf710fc64a9e6c7d99ccdb3e3e10f3b86e5eb7.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 7260840414de5a8eb26961a63ac061869a5d309d Mon Sep 17 00:00:00 2001 +Message-Id: <7260840414de5a8eb26961a63ac061869a5d309d.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:03:52 +0200 -Subject: [PATCH 045/329] sched: Disable CONFIG_RT_GROUP_SCHED on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 045/333] sched: Disable CONFIG_RT_GROUP_SCHED on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Carsten reported problems when running: 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 8d4bdb6c6..7ba520e07 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,14 +1,14 @@ -From 77683e414fc9fa4cb544f1ceb6ea8907d4622d20 Mon Sep 17 00:00:00 2001 -Message-Id: <77683e414fc9fa4cb544f1ceb6ea8907d4622d20.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8d2cc068eb55d96f11cfe642d8f54aa89e086926 Mon Sep 17 00:00:00 2001 +Message-Id: <8d2cc068eb55d96f11cfe642d8f54aa89e086926.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 -Subject: [PATCH 046/329] net/core: disable NET_RX_BUSY_POLL +Subject: [PATCH 046/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz sk_busy_loop() does preempt_disable() followed by a few operations which can take sleeping locks and may get long. 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 c004d90e9..b986ba061 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,11 +1,11 @@ -From c2bf4d4aecad7e710c7f723a4a0a00144e8a9bab Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 75e6d90b48d2ef29c1930c9a40f8b5c53d93af26 Mon Sep 17 00:00:00 2001 +Message-Id: <75e6d90b48d2ef29c1930c9a40f8b5c53d93af26.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 1 Dec 2017 10:42:03 +0100 -Subject: [PATCH 047/329] arm*: disable NEON in kernel mode -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 047/333] arm*: disable NEON in kernel mode +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 7e74ac96b..3660414b1 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,11 +1,11 @@ -From 90fcc4e0f87316ecc6d872f902dbd6f67e250c97 Mon Sep 17 00:00:00 2001 -Message-Id: <90fcc4e0f87316ecc6d872f902dbd6f67e250c97.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From cc87ebe7ce9ea8f54cb9524de1633d5b94316192 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 048/329] powerpc: Use generic rwsem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 048/333] powerpc: Use generic rwsem on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Use generic code which uses rtmutex 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 930ea6fa2..54f21b50b 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,12 +1,12 @@ -From 78ee7dff849f0262f8f0f33501bfaac8c6b26b3b Mon Sep 17 00:00:00 2001 -Message-Id: <78ee7dff849f0262f8f0f33501bfaac8c6b26b3b.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2568914c2ca6334d11c456003a5490189894e3b8 Mon Sep 17 00:00:00 2001 +Message-Id: <2568914c2ca6334d11c456003a5490189894e3b8.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Bogdan Purcareata Date: Fri, 24 Apr 2015 15:53:13 +0000 -Subject: [PATCH 049/329] powerpc/kvm: Disable in-kernel MPIC emulation for +Subject: [PATCH 049/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 9b6eca9f8..8d6f0a3b7 100644 --- a/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch +++ b/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch @@ -1,11 +1,11 @@ -From be153791bdf7b8518d51beb1a5984ccba801fac6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 735573207ecf07b4f01fe908ba436371813ee40e Mon Sep 17 00:00:00 2001 +Message-Id: <735573207ecf07b4f01fe908ba436371813ee40e.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:08:34 +0200 -Subject: [PATCH 050/329] powerpc: Disable highmem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 050/333] powerpc: Disable highmem on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The current highmem handling on -RT is not compatible and needs fixups. 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 c3ab83944..c90dbf709 100644 --- a/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch +++ b/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch @@ -1,11 +1,11 @@ -From dfc9c5288d3cb0f41eaebde9e37efa4ecb646fbe Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From af4c5a7abec8d63afc15afa550baf8e1c93f06f5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:10:12 +0200 -Subject: [PATCH 051/329] mips: Disable highmem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 051/333] mips: Disable highmem on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The current highmem handling on -RT is not compatible and needs fixups. 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 1b6ce10d1..5523fb947 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,11 +1,11 @@ -From ad23b6483e30d8483a7afd6a6ee001fe2f4b54dc Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 38611b201948427fb4c20c4606940efebf433271 Mon Sep 17 00:00:00 2001 +Message-Id: <38611b201948427fb4c20c4606940efebf433271.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 26 Jul 2009 02:21:32 +0200 -Subject: [PATCH 052/329] x86: Use generic rwsem_spinlocks on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 052/333] x86: Use generic rwsem_spinlocks on -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Simplifies the separation of anon_rw_semaphores and rw_semaphores for -rt. 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 b18de95d2..729e5150d 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,11 +1,11 @@ -From faa3dca80a4355c6531b06794a1857d389ef7287 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2147fa4095bfd794ddb11fdfe437db8e6476872a Mon Sep 17 00:00:00 2001 +Message-Id: <2147fa4095bfd794ddb11fdfe437db8e6476872a.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 23 Jan 2014 14:45:59 +0100 -Subject: [PATCH 053/329] leds: trigger: disable CPU trigger on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 053/333] leds: trigger: disable CPU trigger on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz as it triggers: |CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.8-rt10 #141 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 473814bca..4a9f358be 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,11 +1,11 @@ -From b29a1a6addff932e6d55f0515790f56603381fc6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8d8cb80f52aced6cbf75b3a5dfdb90278dbb56d1 Mon Sep 17 00:00:00 2001 +Message-Id: <8d8cb80f52aced6cbf75b3a5dfdb90278dbb56d1.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 9 Apr 2015 15:23:01 +0200 -Subject: [PATCH 054/329] cpufreq: drop K8's driver from beeing selected -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 054/333] cpufreq: drop K8's driver from beeing selected +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Ralf posted a picture of a backtrace from diff --git a/debian/patches-rt/0055-md-disable-bcache.patch b/debian/patches-rt/0055-md-disable-bcache.patch index 62a4f4309..b1e45cfa9 100644 --- a/debian/patches-rt/0055-md-disable-bcache.patch +++ b/debian/patches-rt/0055-md-disable-bcache.patch @@ -1,14 +1,14 @@ -From 041479007eb05b08b7275d0deba18bdeb6870905 Mon Sep 17 00:00:00 2001 -Message-Id: <041479007eb05b08b7275d0deba18bdeb6870905.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 47ece03b0e12c858b418f764b438f1d10fe8bfa7 Mon Sep 17 00:00:00 2001 +Message-Id: <47ece03b0e12c858b418f764b438f1d10fe8bfa7.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 11:48:57 +0200 -Subject: [PATCH 055/329] md: disable bcache +Subject: [PATCH 055/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz It uses anon semaphores |drivers/md/bcache/request.c: In function ‘cached_dev_write_complete’: 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 1bab24bd9..0511dfd87 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,11 +1,11 @@ -From 92130515a97aabba57c55ae1632b5f2e248a7055 Mon Sep 17 00:00:00 2001 -Message-Id: <92130515a97aabba57c55ae1632b5f2e248a7055.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 42374e49bc3bdfd501038d1da1e88735b23fdbb0 Mon Sep 17 00:00:00 2001 +Message-Id: <42374e49bc3bdfd501038d1da1e88735b23fdbb0.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:03:16 +0200 -Subject: [PATCH 056/329] efi: Disable runtime services on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 056/333] efi: Disable runtime services on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Based on meassurements the EFI functions get_variable / get_next_variable take up to 2us which looks okay. @@ -32,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 22cf4dd07b03..a2e3e3b34562 100644 +index 263459bc4d14..e03e37a053f2 100644 --- a/drivers/firmware/efi/efi.c +++ b/drivers/firmware/efi/efi.c @@ -87,7 +87,7 @@ struct mm_struct efi_mm = { 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 6df17abf7..168f9ce69 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,11 +1,11 @@ -From db6223c7072c86363a0817ffb9328cc9ed85996d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 13543539475b324b9c47601e2be5d071e0dbaa5c Mon Sep 17 00:00:00 2001 +Message-Id: <13543539475b324b9c47601e2be5d071e0dbaa5c.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 22 Jul 2011 17:58:40 +0200 -Subject: [PATCH 057/329] printk: Add a printk kill switch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 057/333] printk: Add a printk kill switch +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 5dac0ac23..f20db26af 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,12 +1,12 @@ -From 630e29fe03ffcbb3ccd8e7d0fd82f106d786571e Mon Sep 17 00:00:00 2001 -Message-Id: <630e29fe03ffcbb3ccd8e7d0fd82f106d786571e.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ae4726a22a1bbcb3bdfc67de9e90f9695e1b1079 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Peter Zijlstra Date: Fri, 2 Sep 2011 14:41:29 +0200 -Subject: [PATCH 058/329] printk: Add "force_early_printk" boot param to help +Subject: [PATCH 058/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Gives me an option to screw printk and actually see what the machine says. 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 150fe875f..8c7be2c08 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,11 +1,11 @@ -From 254e10dd953adfcab9a52a9ca628feb74be83087 Mon Sep 17 00:00:00 2001 -Message-Id: <254e10dd953adfcab9a52a9ca628feb74be83087.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b866405729e234026124ab0576e4cd9d849bbd3c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 24 Jul 2009 12:38:56 +0200 -Subject: [PATCH 059/329] preempt: Provide preempt_*_(no)rt variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 059/333] preempt: Provide preempt_*_(no)rt variants +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz RT needs a few preempt_disable/enable points which are not necessary otherwise. Implement variants to avoid #ifdeffery. 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 ab84ec695..52b2ebbd7 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,12 +1,12 @@ -From 6ba1c5e4cd013bee8cee0cc93451dd6cdf18ffdc Mon Sep 17 00:00:00 2001 -Message-Id: <6ba1c5e4cd013bee8cee0cc93451dd6cdf18ffdc.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 43e13dce1ce2cd65962515717aeb360dcc4f5377 Mon Sep 17 00:00:00 2001 +Message-Id: <43e13dce1ce2cd65962515717aeb360dcc4f5377.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Mar 2017 14:23:35 +0100 -Subject: [PATCH 060/329] futex: workaround migrate_disable/enable in different +Subject: [PATCH 060/333] futex: workaround migrate_disable/enable in different context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 0152c1c44..fde9dd5fc 100644 --- a/debian/patches-rt/0061-rt-Add-local-irq-locks.patch +++ b/debian/patches-rt/0061-rt-Add-local-irq-locks.patch @@ -1,11 +1,11 @@ -From 4bbaefcae2f5afe88738712a4d007e178bc67b3c Mon Sep 17 00:00:00 2001 -Message-Id: <4bbaefcae2f5afe88738712a4d007e178bc67b3c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5d5c579866d6b36bf81556252d545fdd67ca35f5 Mon Sep 17 00:00:00 2001 +Message-Id: <5d5c579866d6b36bf81556252d545fdd67ca35f5.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 20 Jun 2011 09:03:47 +0200 -Subject: [PATCH 061/329] rt: Add local irq locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 061/333] rt: Add local irq locks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 cfbf49e3b..b2330ca38 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,11 +1,11 @@ -From dc6d393bb513f3c2466b2ea4b55d4f26e71ef900 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 4d7f9bb9c71326b8513644baa157010c7d1c6fc9 Mon Sep 17 00:00:00 2001 +Message-Id: <4d7f9bb9c71326b8513644baa157010c7d1c6fc9.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:56 -0500 -Subject: [PATCH 062/329] locallock: provide {get,put}_locked_ptr() variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 062/333] locallock: provide {get,put}_locked_ptr() variants +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 b21963a81..a17d8444b 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,11 +1,11 @@ -From d4b8c181b8f5f2ba6edbf89abfcb5320cf73fa78 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0bf3b10d37ad5526e70f44665d6728e3945dd746 Mon Sep 17 00:00:00 2001 +Message-Id: <0bf3b10d37ad5526e70f44665d6728e3945dd746.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:34 -0500 -Subject: [PATCH 063/329] mm/scatterlist: Do not disable irqs on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 063/333] mm/scatterlist: Do not disable irqs on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz For -RT it is enough to keep pagefault disabled (which is currently handled by kmap_atomic()). 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 fe146c434..743dfec6d 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,11 +1,11 @@ -From baec3246ff6f71b863cabd866d8471b3dd772236 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 78fd6c5797a3744a009cf39aa2a42e7781a0c3c6 Mon Sep 17 00:00:00 2001 +Message-Id: <78fd6c5797a3744a009cf39aa2a42e7781a0c3c6.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Oleg Nesterov Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 064/329] signal/x86: Delay calling signals in atomic -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 064/333] signal/x86: Delay calling signals in atomic +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 62f3dca69..d62d1b301 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,11 +1,11 @@ -From 7a87b78c64bc3cf8343852b447d78cf6ae106b87 Mon Sep 17 00:00:00 2001 -Message-Id: <7a87b78c64bc3cf8343852b447d78cf6ae106b87.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3b7c39e29951ebd9c20f2d4b87abe19cb63039da Mon Sep 17 00:00:00 2001 +Message-Id: <3b7c39e29951ebd9c20f2d4b87abe19cb63039da.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Yang Shi Date: Thu, 10 Dec 2015 10:58:51 -0800 -Subject: [PATCH 065/329] x86/signal: delay calling signals on 32bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 065/333] x86/signal: delay calling signals on 32bit +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz When running some ptrace single step tests on x86-32 machine, the below problem is triggered: 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 3b7f18b88..1fd7db1ad 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,11 +1,11 @@ -From 8ccfb80f356bcdc7939cfd20b82977096f52019c Mon Sep 17 00:00:00 2001 -Message-Id: <8ccfb80f356bcdc7939cfd20b82977096f52019c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e50f5996603fbf4fa4e225165ffbb898630ce917 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 09:18:52 +0100 -Subject: [PATCH 066/329] buffer_head: Replace bh_uptodate_lock for -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 066/333] buffer_head: Replace bh_uptodate_lock for -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Wrap the bit_spin_lock calls into a separate inline and add the RT replacements with a real spinlock. 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 d4557c83d..9cf59d443 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,12 +1,12 @@ -From 5c0e35ebae1e5e08ab49e72aefb76de3969de85f Mon Sep 17 00:00:00 2001 -Message-Id: <5c0e35ebae1e5e08ab49e72aefb76de3969de85f.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 778be4ab97f5646c2ad095f22205b787e50bddab Mon Sep 17 00:00:00 2001 +Message-Id: <778be4ab97f5646c2ad095f22205b787e50bddab.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 10:11:25 +0100 -Subject: [PATCH 067/329] fs: jbd/jbd2: Make state lock and journal head lock +Subject: [PATCH 067/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz bit_spin_locks break under RT. 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 1a43ccad8..7a9aa947b 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,11 +1,11 @@ -From 59b96aa2d57b0cbfcb7d10b46ecd17f4e364b6c0 Mon Sep 17 00:00:00 2001 -Message-Id: <59b96aa2d57b0cbfcb7d10b46ecd17f4e364b6c0.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3a2b60b5f35ab25ab5d6e8763284d60dd775fe57 Mon Sep 17 00:00:00 2001 +Message-Id: <3a2b60b5f35ab25ab5d6e8763284d60dd775fe57.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Paul Gortmaker Date: Fri, 21 Jun 2013 15:07:25 -0400 -Subject: [PATCH 068/329] list_bl: Make list head locking RT safe -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 068/333] list_bl: Make list head locking RT safe +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 f1c541e92..83a987de0 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,11 +1,11 @@ -From 5658c126fee12d5c478ad9d45be3ad0fb718c332 Mon Sep 17 00:00:00 2001 -Message-Id: <5658c126fee12d5c478ad9d45be3ad0fb718c332.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5ac4bc4faeca63c74c4a768c4b92c0861a16135a Mon Sep 17 00:00:00 2001 +Message-Id: <5ac4bc4faeca63c74c4a768c4b92c0861a16135a.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 31 Mar 2016 00:04:25 -0500 -Subject: [PATCH 069/329] list_bl: fixup bogus lockdep warning -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 069/333] list_bl: fixup bogus lockdep warning +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz At first glance, the use of 'static inline' seems appropriate for INIT_HLIST_BL_HEAD(). 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 bd68fc088..bf1345654 100644 --- a/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch +++ b/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch @@ -1,11 +1,11 @@ -From 1a66c09be3bc7fdf90e0267de627a4b888bd765d Mon Sep 17 00:00:00 2001 -Message-Id: <1a66c09be3bc7fdf90e0267de627a4b888bd765d.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a669c7f6749b209860bdd82f6d21fb1c540a999a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:57 -0500 -Subject: [PATCH 070/329] genirq: Disable irqpoll on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 070/333] genirq: Disable irqpoll on -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Creates long latencies for no value 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 cb4fff88e..e74448e67 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,11 +1,11 @@ -From 956db5b60cab8cdc9eb1876da6836cf2e3e9cb38 Mon Sep 17 00:00:00 2001 -Message-Id: <956db5b60cab8cdc9eb1876da6836cf2e3e9cb38.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From eb31d921bdfba8bc6fa501962d5c13d2c4f9747d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 3 Apr 2011 11:57:29 +0200 -Subject: [PATCH 071/329] genirq: Force interrupt thread on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 071/333] genirq: Force interrupt thread on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Force threaded_irqs and optimize the code (force_irqthreads) in regard to this. @@ -33,7 +33,7 @@ index eeceac3376fc..315f852b4981 100644 #define force_irqthreads (0) #endif diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c -index 025fcd029f83..b57d1a2d4d79 100644 +index 3b66c77670d9..98f9bb27ce37 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c @@ -24,6 +24,7 @@ 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 0070a2d2b..dd804cc91 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,12 +1,12 @@ -From 532c38e1e5fb5c27b6574adbd5ec0abafa87e590 Mon Sep 17 00:00:00 2001 -Message-Id: <532c38e1e5fb5c27b6574adbd5ec0abafa87e590.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From bad6f6554b001b698abe1b5b5ac4181a235ba188 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:20 +0200 -Subject: [PATCH 072/329] Split IRQ-off and zone->lock while freeing pages from +Subject: [PATCH 072/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. @@ -20,9 +20,11 @@ Signed-off-by: Sebastian Andrzej Siewior mm/page_alloc.c | 82 +++++++++++++++++++++++++++++++------------------ 1 file changed, 52 insertions(+), 30 deletions(-) +diff --git a/mm/page_alloc.c b/mm/page_alloc.c +index 5717ee66c8b3..47732cad4a51 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c -@@ -1095,7 +1095,7 @@ +@@ -1095,7 +1095,7 @@ static inline void prefetch_buddy(struct page *page) } /* @@ -31,7 +33,7 @@ Signed-off-by: Sebastian Andrzej Siewior * Assumes all pages on list are in same zone, and of same order. * count is the number of pages to free. * -@@ -1106,14 +1106,41 @@ +@@ -1106,14 +1106,41 @@ static inline void prefetch_buddy(struct page *page) * pinned" detection logic. */ static void free_pcppages_bulk(struct zone *zone, int count, @@ -77,7 +79,7 @@ Signed-off-by: Sebastian Andrzej Siewior /* * Ensure proper count is passed which otherwise would stuck in the -@@ -1150,7 +1177,7 @@ +@@ -1150,7 +1177,7 @@ static void free_pcppages_bulk(struct zone *zone, int count, if (bulkfree_pcp_prepare(page)) continue; @@ -86,7 +88,7 @@ Signed-off-by: Sebastian Andrzej Siewior /* * We are going to put the page back to the global -@@ -1165,26 +1192,6 @@ +@@ -1165,26 +1192,6 @@ static void free_pcppages_bulk(struct zone *zone, int count, prefetch_buddy(page); } while (--count && --batch_free && !list_empty(list)); } @@ -113,7 +115,7 @@ Signed-off-by: Sebastian Andrzej Siewior } static void free_one_page(struct zone *zone, -@@ -2545,13 +2552,18 @@ +@@ -2545,13 +2552,18 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) { unsigned long flags; int to_drain, batch; @@ -133,7 +135,7 @@ Signed-off-by: Sebastian Andrzej Siewior } #endif -@@ -2567,14 +2579,21 @@ +@@ -2567,14 +2579,21 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) unsigned long flags; struct per_cpu_pageset *pset; struct per_cpu_pages *pcp; @@ -157,7 +159,7 @@ Signed-off-by: Sebastian Andrzej Siewior } /* -@@ -2796,7 +2815,10 @@ +@@ -2796,7 +2815,10 @@ static void free_unref_page_commit(struct page *page, unsigned long pfn) pcp->count++; if (pcp->count >= pcp->high) { unsigned long batch = READ_ONCE(pcp->batch); @@ -169,3 +171,6 @@ Signed-off-by: Sebastian Andrzej Siewior } } +-- +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 f56d95d58..ed58e8578 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,12 +1,12 @@ -From d72a0b854a4bc197365cac871e1051f1c21f170a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5de327261c8d96d3da74a89d108a2385119f45fa Mon Sep 17 00:00:00 2001 +Message-Id: <5de327261c8d96d3da74a89d108a2385119f45fa.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:21 +0200 -Subject: [PATCH 073/329] Split IRQ-off and zone->lock while freeing pages from +Subject: [PATCH 073/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. @@ -21,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 bab65ef53eda..6c45b7713e56 100644 +index 47732cad4a51..e43e374a9415 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1105,8 +1105,8 @@ static inline void prefetch_buddy(struct page *page) @@ -63,7 +63,7 @@ index bab65ef53eda..6c45b7713e56 100644 __free_one_page(page, page_to_pfn(page), zone, 0, mt); trace_mm_page_pcpu_drain(page, 0, mt); } -@@ -2558,7 +2573,7 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) +@@ -2563,7 +2578,7 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) local_irq_restore(flags); if (to_drain > 0) @@ -72,7 +72,7 @@ index bab65ef53eda..6c45b7713e56 100644 } #endif -@@ -2588,7 +2603,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) +@@ -2593,7 +2608,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) local_irq_restore(flags); if (count) @@ -81,7 +81,7 @@ index bab65ef53eda..6c45b7713e56 100644 } /* -@@ -2781,7 +2796,8 @@ static bool free_unref_page_prepare(struct page *page, unsigned long pfn) +@@ -2786,7 +2801,8 @@ static bool free_unref_page_prepare(struct page *page, unsigned long pfn) return true; } @@ -91,7 +91,7 @@ index bab65ef53eda..6c45b7713e56 100644 { struct zone *zone = page_zone(page); struct per_cpu_pages *pcp; -@@ -2810,10 +2826,8 @@ static void free_unref_page_commit(struct page *page, unsigned long pfn) +@@ -2815,10 +2831,8 @@ static void free_unref_page_commit(struct page *page, unsigned long pfn) pcp->count++; if (pcp->count >= pcp->high) { unsigned long batch = READ_ONCE(pcp->batch); @@ -103,7 +103,7 @@ index bab65ef53eda..6c45b7713e56 100644 } } -@@ -2824,13 +2838,17 @@ void free_unref_page(struct page *page) +@@ -2829,13 +2843,17 @@ void free_unref_page(struct page *page) { unsigned long flags; unsigned long pfn = page_to_pfn(page); @@ -122,7 +122,7 @@ index bab65ef53eda..6c45b7713e56 100644 } /* -@@ -2841,6 +2859,11 @@ void free_unref_page_list(struct list_head *list) +@@ -2846,6 +2864,11 @@ void free_unref_page_list(struct list_head *list) struct page *page, *next; unsigned long flags, pfn; int batch_count = 0; @@ -134,7 +134,7 @@ index bab65ef53eda..6c45b7713e56 100644 /* Prepare pages for freeing */ list_for_each_entry_safe(page, next, list, lru) { -@@ -2853,10 +2876,12 @@ void free_unref_page_list(struct list_head *list) +@@ -2858,10 +2881,12 @@ void free_unref_page_list(struct list_head *list) local_irq_save(flags); list_for_each_entry_safe(page, next, list, lru) { unsigned long pfn = page_private(page); @@ -148,7 +148,7 @@ index bab65ef53eda..6c45b7713e56 100644 /* * Guard against excessive IRQ disabled times when we get -@@ -2869,6 +2894,21 @@ void free_unref_page_list(struct list_head *list) +@@ -2874,6 +2899,21 @@ void free_unref_page_list(struct list_head *list) } } local_irq_restore(flags); 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 784133a17..cf9eeecea 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,11 +1,11 @@ -From dd386f034c72580313da947e4d61291caec56ddf Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8b9475846c26d3e6aced54766155b64adb6e0573 Mon Sep 17 00:00:00 2001 +Message-Id: <8b9475846c26d3e6aced54766155b64adb6e0573.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 28 May 2018 15:24:22 +0200 -Subject: [PATCH 074/329] 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.135-rt60.tar.xz +Subject: [PATCH 074/333] 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.142-rt63.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 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 2d96d628f..861352e19 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,12 +1,12 @@ -From 814fd358ca735f82d5c61ef025e930407b323939 Mon Sep 17 00:00:00 2001 -Message-Id: <814fd358ca735f82d5c61ef025e930407b323939.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 54aab23b5557eda17033a5d020be3eada6493aa4 Mon Sep 17 00:00:00 2001 +Message-Id: <54aab23b5557eda17033a5d020be3eada6493aa4.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 21 Jun 2018 17:29:19 +0200 -Subject: [PATCH 075/329] mm/SLUB: delay giving back empty slubs to IRQ enabled +Subject: [PATCH 075/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz __free_slab() is invoked with disabled interrupts which increases the irq-off time while __free_pages() is doing the work. 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 969cfd8b4..63e19fcbd 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,11 +1,11 @@ -From d22cba7e76710f715c9096a58b3bb0ce8b58640a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2cdc3cbaae6968d52c6996f70be372f72bb6151f Mon Sep 17 00:00:00 2001 +Message-Id: <2cdc3cbaae6968d52c6996f70be372f72bb6151f.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:37 -0500 -Subject: [PATCH 076/329] mm: page_alloc: rt-friendly per-cpu pages -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 076/333] mm: page_alloc: rt-friendly per-cpu pages +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz rt-friendly per-cpu pages: convert the irqs-off per-cpu locking method into a preemptible, explicit-per-cpu-locks method. @@ -21,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 6c45b7713e56..63bf99bdcabc 100644 +index e43e374a9415..f6f11e22970e 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -60,6 +60,7 @@ @@ -51,7 +51,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 int page_group_by_mobility_disabled __read_mostly; #ifdef CONFIG_DEFERRED_STRUCT_PAGE_INIT -@@ -1296,10 +1309,10 @@ static void __free_pages_ok(struct page *page, unsigned int order) +@@ -1301,10 +1314,10 @@ static void __free_pages_ok(struct page *page, unsigned int order) return; migratetype = get_pfnblock_migratetype(page, pfn); @@ -64,7 +64,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 } static void __init __free_pages_boot_core(struct page *page, unsigned int order) -@@ -2564,13 +2577,13 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) +@@ -2569,13 +2582,13 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) int to_drain, batch; LIST_HEAD(dst); @@ -80,7 +80,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 if (to_drain > 0) free_pcppages_bulk(zone, &dst, false); -@@ -2592,7 +2605,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) +@@ -2597,7 +2610,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) LIST_HEAD(dst); int count; @@ -89,7 +89,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 pset = per_cpu_ptr(zone->pageset, cpu); pcp = &pset->pcp; -@@ -2600,7 +2613,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) +@@ -2605,7 +2618,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) if (count) isolate_pcp_pages(count, pcp, &dst); @@ -98,7 +98,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 if (count) free_pcppages_bulk(zone, &dst, false); -@@ -2638,6 +2651,7 @@ void drain_local_pages(struct zone *zone) +@@ -2643,6 +2656,7 @@ void drain_local_pages(struct zone *zone) drain_pages(cpu); } @@ -106,7 +106,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 static void drain_local_pages_wq(struct work_struct *work) { /* -@@ -2651,6 +2665,7 @@ static void drain_local_pages_wq(struct work_struct *work) +@@ -2656,6 +2670,7 @@ static void drain_local_pages_wq(struct work_struct *work) drain_local_pages(NULL); preempt_enable(); } @@ -114,7 +114,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 /* * Spill all the per-cpu pages from all CPUs back into the buddy allocator. -@@ -2717,7 +2732,14 @@ void drain_all_pages(struct zone *zone) +@@ -2722,7 +2737,14 @@ void drain_all_pages(struct zone *zone) else cpumask_clear_cpu(cpu, &cpus_with_pcps); } @@ -130,7 +130,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 for_each_cpu(cpu, &cpus_with_pcps) { struct work_struct *work = per_cpu_ptr(&pcpu_drain, cpu); INIT_WORK(work, drain_local_pages_wq); -@@ -2725,6 +2747,7 @@ void drain_all_pages(struct zone *zone) +@@ -2730,6 +2752,7 @@ void drain_all_pages(struct zone *zone) } for_each_cpu(cpu, &cpus_with_pcps) flush_work(per_cpu_ptr(&pcpu_drain, cpu)); @@ -138,7 +138,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 mutex_unlock(&pcpu_drain_mutex); } -@@ -2844,9 +2867,9 @@ void free_unref_page(struct page *page) +@@ -2849,9 +2872,9 @@ void free_unref_page(struct page *page) if (!free_unref_page_prepare(page, pfn)) return; @@ -150,7 +150,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 if (!list_empty(&dst)) free_pcppages_bulk(zone, &dst, false); } -@@ -2873,7 +2896,7 @@ void free_unref_page_list(struct list_head *list) +@@ -2878,7 +2901,7 @@ void free_unref_page_list(struct list_head *list) set_page_private(page, pfn); } @@ -159,7 +159,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 list_for_each_entry_safe(page, next, list, lru) { unsigned long pfn = page_private(page); enum zone_type type; -@@ -2888,12 +2911,12 @@ void free_unref_page_list(struct list_head *list) +@@ -2893,12 +2916,12 @@ void free_unref_page_list(struct list_head *list) * a large list of pages to free. */ if (++batch_count == SWAP_CLUSTER_MAX) { @@ -175,7 +175,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 for (i = 0; i < __MAX_NR_ZONES; ) { struct page *page; -@@ -3042,7 +3065,7 @@ static struct page *rmqueue_pcplist(struct zone *preferred_zone, +@@ -3047,7 +3070,7 @@ static struct page *rmqueue_pcplist(struct zone *preferred_zone, struct page *page; unsigned long flags; @@ -184,7 +184,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 pcp = &this_cpu_ptr(zone->pageset)->pcp; list = &pcp->lists[migratetype]; page = __rmqueue_pcplist(zone, migratetype, pcp, list); -@@ -3050,7 +3073,7 @@ static struct page *rmqueue_pcplist(struct zone *preferred_zone, +@@ -3055,7 +3078,7 @@ static struct page *rmqueue_pcplist(struct zone *preferred_zone, __count_zid_vm_events(PGALLOC, page_zonenum(page), 1 << order); zone_statistics(preferred_zone, zone); } @@ -193,7 +193,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 return page; } -@@ -3077,7 +3100,7 @@ struct page *rmqueue(struct zone *preferred_zone, +@@ -3082,7 +3105,7 @@ struct page *rmqueue(struct zone *preferred_zone, * allocate greater than order-1 page units with __GFP_NOFAIL. */ WARN_ON_ONCE((gfp_flags & __GFP_NOFAIL) && (order > 1)); @@ -202,7 +202,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 do { page = NULL; -@@ -3097,14 +3120,14 @@ struct page *rmqueue(struct zone *preferred_zone, +@@ -3102,14 +3125,14 @@ struct page *rmqueue(struct zone *preferred_zone, __count_zid_vm_events(PGALLOC, page_zonenum(page), 1 << order); zone_statistics(preferred_zone, zone); @@ -219,7 +219,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 return NULL; } -@@ -8125,7 +8148,7 @@ void zone_pcp_reset(struct zone *zone) +@@ -8130,7 +8153,7 @@ void zone_pcp_reset(struct zone *zone) struct per_cpu_pageset *pset; /* avoid races with drain_pages() */ @@ -228,7 +228,7 @@ index 6c45b7713e56..63bf99bdcabc 100644 if (zone->pageset != &boot_pageset) { for_each_online_cpu(cpu) { pset = per_cpu_ptr(zone->pageset, cpu); -@@ -8134,7 +8157,7 @@ void zone_pcp_reset(struct zone *zone) +@@ -8139,7 +8162,7 @@ void zone_pcp_reset(struct zone *zone) free_percpu(zone->pageset); zone->pageset = &boot_pageset; } 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 b03b8ebb7..4fe65a657 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,11 +1,11 @@ -From bb9ad4172a3a877e89400822d859b6bfd8bb9f48 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 119379713401cbbc6e85d31a53eff0fac5eebbce Mon Sep 17 00:00:00 2001 +Message-Id: <119379713401cbbc6e85d31a53eff0fac5eebbce.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:51 -0500 -Subject: [PATCH 077/329] mm/swap: Convert to percpu locked -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 077/333] mm/swap: Convert to percpu locked +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Replace global locks (get_cpu + local_irq_save) with "local_locks()". Currently there is one of for "rotate" and one for "swap". @@ -59,10 +59,10 @@ index 5079ddbec8f9..c40d3a13cbbd 100644 cc->last_migrated_pfn = 0; } diff --git a/mm/page_alloc.c b/mm/page_alloc.c -index 63bf99bdcabc..1d25236411a7 100644 +index f6f11e22970e..c80714992781 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c -@@ -7238,8 +7238,9 @@ void __init free_area_init(unsigned long *zones_size) +@@ -7243,8 +7243,9 @@ void __init free_area_init(unsigned long *zones_size) static int page_alloc_cpu_dead(unsigned int cpu) { 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 b75d22683..6d7d9cf41 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,11 +1,11 @@ -From 16d32cb8fdd33bacf654c4a7bb0774ec6d48fbc4 Mon Sep 17 00:00:00 2001 -Message-Id: <16d32cb8fdd33bacf654c4a7bb0774ec6d48fbc4.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e0404fa2e07bd2d4c44ca88db8eed00cb5b4d434 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Luiz Capitulino Date: Fri, 27 May 2016 15:03:28 +0200 -Subject: [PATCH 078/329] mm: perform lru_add_drain_all() remotely -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 078/333] mm: perform lru_add_drain_all() remotely +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 887572ff1..9ad11c77c 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,12 +1,12 @@ -From d9de2b64e27437cb8cd89fedebd0d0048f5340b7 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 35edae1ccefb0cfffb4b439708bce25ac7eaf524 Mon Sep 17 00:00:00 2001 +Message-Id: <35edae1ccefb0cfffb4b439708bce25ac7eaf524.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:30:13 -0500 -Subject: [PATCH 079/329] mm/vmstat: Protect per cpu variables with preempt +Subject: [PATCH 079/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 9fd7d0799..fe05ab855 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,12 +1,12 @@ -From 1f9ecc22bc3d924555ae11dbe0ddeab01952a512 Mon Sep 17 00:00:00 2001 -Message-Id: <1f9ecc22bc3d924555ae11dbe0ddeab01952a512.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From bcdffe5ae983c29e10b837d0d0aa81ba1707522f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Frank Rowand Date: Sat, 1 Oct 2011 18:58:13 -0700 -Subject: [PATCH 080/329] ARM: Initialize split page table locks for vector +Subject: [PATCH 080/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Without this patch, ARM can not use SPLIT_PTLOCK_CPUS if PREEMPT_RT_FULL=y because vectors_user_mapping() creates a 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 5a67dff03..4253ef827 100644 --- a/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch +++ b/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch @@ -1,11 +1,11 @@ -From ed3c40729340989bec3949fc03ecefb279f16084 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 080b2c8d81078acabc300033620a22a408c7909a Mon Sep 17 00:00:00 2001 +Message-Id: <080b2c8d81078acabc300033620a22a408c7909a.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 25 Oct 2012 10:32:35 +0100 -Subject: [PATCH 081/329] mm: Enable SLUB for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 081/333] mm: Enable SLUB for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Avoid the memory allocation in IRQ section 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 2b3b15944..d79ff2b92 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,11 +1,11 @@ -From 3e9e31775846ca871bff4cfe9e435b325b36cfee Mon Sep 17 00:00:00 2001 -Message-Id: <3e9e31775846ca871bff4cfe9e435b325b36cfee.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ed692d1c5c78c4e42398936b657dd52b6070865c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 9 Jan 2013 12:08:15 +0100 -Subject: [PATCH 082/329] slub: Enable irqs for __GFP_WAIT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 082/333] slub: Enable irqs for __GFP_WAIT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 ddf742f65..cdb7d7ae5 100644 --- a/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch +++ b/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch @@ -1,11 +1,11 @@ -From d241c137df7f939bfb97b53197bd348d328dc6b0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 78805dc2fea3579b7cdb8bb1f25ebf9aa147af81 Mon Sep 17 00:00:00 2001 +Message-Id: <78805dc2fea3579b7cdb8bb1f25ebf9aa147af81.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Apr 2015 19:00:47 +0200 -Subject: [PATCH 083/329] slub: Disable SLUB_CPU_PARTIAL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 083/333] slub: Disable SLUB_CPU_PARTIAL +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 e001189df..19028dbf2 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,12 +1,12 @@ -From b48a83eb78e110ba650dc000f03d8e010b3bfb93 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2c43e6323d26840e86b3eac8e417df83b2420f4a Mon Sep 17 00:00:00 2001 +Message-Id: <2c43e6323d26840e86b3eac8e417df83b2420f4a.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Yang Shi Date: Wed, 30 Oct 2013 11:48:33 -0700 -Subject: [PATCH 084/329] mm/memcontrol: Don't call schedule_work_on in +Subject: [PATCH 084/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The following trace is triggered when running ltp oom test cases: 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 5244ba6d8..c4e30a82e 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,12 +1,12 @@ -From 46cd5bef5cbeef69430f8243dffad3d6bf4d5f60 Mon Sep 17 00:00:00 2001 -Message-Id: <46cd5bef5cbeef69430f8243dffad3d6bf4d5f60.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8550a07330a14f76ace74d423da03e02855055d3 Mon Sep 17 00:00:00 2001 +Message-Id: <8550a07330a14f76ace74d423da03e02855055d3.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 28 Jan 2015 17:14:16 +0100 -Subject: [PATCH 085/329] mm/memcontrol: Replace local_irq_disable with local +Subject: [PATCH 085/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz There are a few local_irq_disable() which then take sleeping locks. This patch converts them local locks. 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 97728572e..711b4d0c3 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,11 +1,11 @@ -From b43b38e7434705ca1df250741a943f22c3aa3c4b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 29754917123a140f972a15b6385d91d7b3a7d684 Mon Sep 17 00:00:00 2001 +Message-Id: <29754917123a140f972a15b6385d91d7b3a7d684.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Tue, 22 Mar 2016 11:16:09 +0100 -Subject: [PATCH 086/329] 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.135-rt60.tar.xz +Subject: [PATCH 086/333] 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.142-rt63.tar.xz get_cpu_var() disables preemption and triggers a might_sleep() splat later. This is replaced with get_locked_var(). 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 fdc0760e8..562e2e2f9 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,12 +1,12 @@ -From 618330e49648f0851200b9e4ca83e18dd4d07131 Mon Sep 17 00:00:00 2001 -Message-Id: <618330e49648f0851200b9e4ca83e18dd4d07131.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3c521ba0f590185c472ef4d2b0ded435cfd9d135 Mon Sep 17 00:00:00 2001 +Message-Id: <3c521ba0f590185c472ef4d2b0ded435cfd9d135.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 21:53:43 +0100 -Subject: [PATCH 087/329] x86/mm/pat: disable preemption __split_large_page() +Subject: [PATCH 087/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 7385c8544..b06e2ce34 100644 --- a/debian/patches-rt/0088-radix-tree-use-local-locks.patch +++ b/debian/patches-rt/0088-radix-tree-use-local-locks.patch @@ -1,11 +1,11 @@ -From 4ca4b11d8f733ff4a065686ddcb1221d5f4fbe21 Mon Sep 17 00:00:00 2001 -Message-Id: <4ca4b11d8f733ff4a065686ddcb1221d5f4fbe21.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From caff1ae037c683a77f3435dd72f4e1fd752ff574 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jan 2017 16:34:27 +0100 -Subject: [PATCH 088/329] radix-tree: use local locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 088/333] radix-tree: use local locks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 89102c52c..c85f33623 100644 --- a/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch +++ b/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch @@ -1,11 +1,11 @@ -From a3af87bbfafb04784c4c873c21c5aa1458ba7483 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1515fae666ef12f51f8f87243ca51cc4ee5590b3 Mon Sep 17 00:00:00 2001 +Message-Id: <1515fae666ef12f51f8f87243ca51cc4ee5590b3.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 -Subject: [PATCH 089/329] timers: Prepare for full preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 089/333] timers: Prepare for full preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -19,9 +19,11 @@ Signed-off-by: Thomas Gleixner kernel/time/timer.c | 45 +++++++++++++++++++++++++++++++++++++++---- 3 files changed, 49 insertions(+), 7 deletions(-) +diff --git a/include/linux/timer.h b/include/linux/timer.h +index 7b066fd38248..54627d046b3a 100644 --- a/include/linux/timer.h +++ b/include/linux/timer.h -@@ -172,7 +172,7 @@ +@@ -172,7 +172,7 @@ extern void add_timer(struct timer_list *timer); extern int try_to_del_timer_sync(struct timer_list *timer); @@ -30,9 +32,11 @@ Signed-off-by: Thomas Gleixner extern int del_timer_sync(struct timer_list *timer); #else # define del_timer_sync(t) del_timer(t) +diff --git a/kernel/sched/core.c b/kernel/sched/core.c +index 541c7222ffc2..c0058e62a3fc 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -498,11 +498,14 @@ +@@ -498,11 +498,14 @@ void resched_cpu(int cpu) */ int get_nohz_timer_target(void) { @@ -49,7 +53,7 @@ Signed-off-by: Thomas Gleixner rcu_read_lock(); for_each_domain(cpu, sd) { -@@ -521,6 +524,8 @@ +@@ -521,6 +524,8 @@ int get_nohz_timer_target(void) cpu = housekeeping_any_cpu(HK_FLAG_TIMER); unlock: rcu_read_unlock(); @@ -58,6 +62,8 @@ Signed-off-by: Thomas Gleixner return cpu; } +diff --git a/kernel/time/timer.c b/kernel/time/timer.c +index 61e41ea3a96e..ecc23d2c21a9 100644 --- a/kernel/time/timer.c +++ b/kernel/time/timer.c @@ -45,6 +45,7 @@ @@ -68,7 +74,7 @@ Signed-off-by: Thomas Gleixner #include #include -@@ -198,6 +199,9 @@ +@@ -198,6 +199,9 @@ EXPORT_SYMBOL(jiffies_64); struct timer_base { raw_spinlock_t lock; struct timer_list *running_timer; @@ -78,7 +84,7 @@ Signed-off-by: Thomas Gleixner unsigned long clk; unsigned long next_expiry; unsigned int cpu; -@@ -1190,6 +1194,33 @@ +@@ -1190,6 +1194,33 @@ void add_timer_on(struct timer_list *timer, int cpu) } EXPORT_SYMBOL_GPL(add_timer_on); @@ -112,7 +118,7 @@ Signed-off-by: Thomas Gleixner /** * del_timer - deactivate a timer. * @timer: the timer to be deactivated -@@ -1245,7 +1276,7 @@ +@@ -1245,7 +1276,7 @@ int try_to_del_timer_sync(struct timer_list *timer) } EXPORT_SYMBOL(try_to_del_timer_sync); @@ -121,7 +127,7 @@ Signed-off-by: Thomas Gleixner /** * del_timer_sync - deactivate a timer and wait for the handler to finish. * @timer: the timer to be deactivated -@@ -1305,7 +1336,7 @@ +@@ -1305,7 +1336,7 @@ int del_timer_sync(struct timer_list *timer) int ret = try_to_del_timer_sync(timer); if (ret >= 0) return ret; @@ -130,7 +136,7 @@ Signed-off-by: Thomas Gleixner } } EXPORT_SYMBOL(del_timer_sync); -@@ -1366,13 +1397,16 @@ +@@ -1366,13 +1397,16 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head) fn = timer->function; @@ -148,7 +154,7 @@ Signed-off-by: Thomas Gleixner raw_spin_lock_irq(&base->lock); } } -@@ -1702,8 +1736,8 @@ +@@ -1702,8 +1736,8 @@ static inline void __run_timers(struct timer_base *base) while (levels--) expire_timers(base, heads + levels); } @@ -158,7 +164,7 @@ Signed-off-by: Thomas Gleixner } /* -@@ -1948,6 +1982,9 @@ +@@ -1948,6 +1982,9 @@ static void __init init_timer_cpu(int cpu) base->cpu = cpu; raw_spin_lock_init(&base->lock); base->clk = jiffies; @@ -168,3 +174,6 @@ Signed-off-by: Thomas Gleixner } } +-- +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 bff86b45f..bc3223b66 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,11 +1,11 @@ -From 80718f0b78e1f76c9b8937257215b63ed4355e23 Mon Sep 17 00:00:00 2001 -Message-Id: <80718f0b78e1f76c9b8937257215b63ed4355e23.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a37950118e086bbf324f26f9f39999022d523548 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 6 Nov 2011 12:26:18 +0100 -Subject: [PATCH 090/329] x86: kvm Require const tsc for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 090/333] x86: kvm Require const tsc for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Non constant TSC is a nightmare on bare metal already, but with virtualization it becomes a complete disaster because the workarounds @@ -18,7 +18,7 @@ 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 5b2440e591fc..9fc847c237da 100644 +index 430a4bc66f60..1711b12d934c 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -6850,6 +6850,13 @@ int kvm_arch_init(void *opaque) 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 f877131ad..b5f5b6993 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,11 +1,11 @@ -From 22fd004a43ed16303a43545c0d993ef12e1e5351 Mon Sep 17 00:00:00 2001 -Message-Id: <22fd004a43ed16303a43545c0d993ef12e1e5351.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 917b1d297504ab2942aa7ef6f6d2c9c72ad8aba9 Mon Sep 17 00:00:00 2001 +Message-Id: <917b1d297504ab2942aa7ef6f6d2c9c72ad8aba9.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Oct 2017 10:24:23 +0200 -Subject: [PATCH 091/329] 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.135-rt60.tar.xz +Subject: [PATCH 091/333] 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.142-rt63.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 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 20bed05f6..0d6187927 100644 --- a/debian/patches-rt/0092-wait.h-include-atomic.h.patch +++ b/debian/patches-rt/0092-wait.h-include-atomic.h.patch @@ -1,14 +1,14 @@ -From f441a761836590a8dfa82a921ab4940a1afae6f5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From bb47a5cc110ed88e0e58a30c483c2182136c22ea Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 28 Oct 2013 12:19:57 +0100 -Subject: [PATCH 092/329] wait.h: include atomic.h +Subject: [PATCH 092/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz | CC init/main.o |In file included from include/linux/mmzone.h:9:0, 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 a02178675..3e57516ae 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,11 +1,11 @@ -From 5790c349caf92d7ae4663edbdf52dc8cc479ab24 Mon Sep 17 00:00:00 2001 -Message-Id: <5790c349caf92d7ae4663edbdf52dc8cc479ab24.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From cb5623059d756c1c23dc84d7cf3c3987b61ed6bc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Daniel Wagner Date: Fri, 11 Jul 2014 15:26:11 +0200 -Subject: [PATCH 093/329] work-simple: Simple work queue implemenation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 093/333] work-simple: Simple work queue implemenation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Provides a framework for enqueuing callbacks from irq context PREEMPT_RT_FULL safe. The callbacks are executed in kthread context. 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 f2b5bc391..68134fc6e 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,12 +1,12 @@ -From 954eccfdee5c112121d31d3e5ed0732d7978155a Mon Sep 17 00:00:00 2001 -Message-Id: <954eccfdee5c112121d31d3e5ed0732d7978155a.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1a296b998f09990cbac50043460df6dd31505812 Mon Sep 17 00:00:00 2001 +Message-Id: <1a296b998f09990cbac50043460df6dd31505812.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 10 Sep 2018 18:00:31 +0200 -Subject: [PATCH 094/329] work-simple: drop a shit statement in +Subject: [PATCH 094/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Dan Carpenter reported | smatch warnings: 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 9dd61f461..7cd933860 100644 --- a/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch +++ b/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch @@ -1,11 +1,11 @@ -From 86023a52a1a1fd6885aca43b9e40ac1e7c2ae6f5 Mon Sep 17 00:00:00 2001 -Message-Id: <86023a52a1a1fd6885aca43b9e40ac1e7c2ae6f5.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8b2a22ad4eab11c51afe125ab7e813b57897d001 Mon Sep 17 00:00:00 2001 +Message-Id: <8b2a22ad4eab11c51afe125ab7e813b57897d001.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 11 Jan 2013 11:23:51 +0100 -Subject: [PATCH 095/329] completion: Use simple wait queues -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 095/333] completion: Use simple wait queues +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Completions have no long lasting callbacks and therefor do not need the complex waitqueue variant. Use simple waitqueues which reduces the 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 1b1a52c65..7321693d2 100644 --- a/debian/patches-rt/0096-fs-aio-simple-simple-work.patch +++ b/debian/patches-rt/0096-fs-aio-simple-simple-work.patch @@ -1,11 +1,11 @@ -From ac293d2dacfe32627d56a7b5a926b134f703e50c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1a841488ca7f62b71a500186ad419d6090b929bc Mon Sep 17 00:00:00 2001 +Message-Id: <1a841488ca7f62b71a500186ad419d6090b929bc.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 -Subject: [PATCH 096/329] fs/aio: simple simple work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 096/333] fs/aio: simple simple work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 099394a06..cdbc35f7a 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,12 +1,12 @@ -From c577359102ed6ef26386114e4ec850d686c8eb4e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From da619e2c9a6272d7e6507460e3f38d20fbaa7393 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Nov 2017 17:29:51 +0100 -Subject: [PATCH 097/329] time/hrtimer: avoid schedule_work() with interrupts +Subject: [PATCH 097/333] time/hrtimer: avoid schedule_work() with interrupts disabled -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. @@ -17,10 +17,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/kernel/time/timer.c b/kernel/time/timer.c -index 458fa0189514..845f687d2d1c 100644 +index ecc23d2c21a9..753b75751f0a 100644 --- a/kernel/time/timer.c +++ b/kernel/time/timer.c -@@ -217,8 +217,7 @@ static DEFINE_PER_CPU(struct timer_base, timer_bases[NR_BASES]); +@@ -218,8 +218,7 @@ static DEFINE_PER_CPU(struct timer_base, timer_bases[NR_BASES]); static DEFINE_STATIC_KEY_FALSE(timers_nohz_active); static DEFINE_MUTEX(timer_keys_mutex); @@ -30,7 +30,7 @@ index 458fa0189514..845f687d2d1c 100644 #ifdef CONFIG_SMP unsigned int sysctl_timer_migration = 1; -@@ -236,7 +235,7 @@ static void timers_update_migration(void) +@@ -237,7 +236,7 @@ static void timers_update_migration(void) static inline void timers_update_migration(void) { } #endif /* !CONFIG_SMP */ @@ -39,7 +39,7 @@ index 458fa0189514..845f687d2d1c 100644 { mutex_lock(&timer_keys_mutex); timers_update_migration(); -@@ -246,9 +245,17 @@ static void timer_update_keys(struct work_struct *work) +@@ -247,9 +246,17 @@ static void timer_update_keys(struct work_struct *work) void timers_update_nohz(void) { 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 6d457241e..23cd11d60 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,12 +1,12 @@ -From a3e30f6b6a09d8c3ea8c0c96cc0cfc6cebdb6804 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 68790f3d4f992f2410f9b8c2dd98874d07eee4ce Mon Sep 17 00:00:00 2001 +Message-Id: <68790f3d4f992f2410f9b8c2dd98874d07eee4ce.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 11:25:41 +0200 -Subject: [PATCH 098/329] hrtimer: consolidate hrtimer_init() + +Subject: [PATCH 098/333] hrtimer: consolidate hrtimer_init() + hrtimer_init_sleeper() calls -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz hrtimer_init_sleeper() calls require a prior initialisation of the hrtimer object with hrtimer_init(). Lets make the initialisation of diff --git a/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch b/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch index 641ef5990..48d232fa0 100644 --- a/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch +++ b/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch @@ -1,11 +1,11 @@ -From 21f166a2b78dcb4b748826540d1bdd84f0a164b3 Mon Sep 17 00:00:00 2001 -Message-Id: <21f166a2b78dcb4b748826540d1bdd84f0a164b3.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 116fd08767bc0bfe1df50417612622aa46928199 Mon Sep 17 00:00:00 2001 +Message-Id: <116fd08767bc0bfe1df50417612622aa46928199.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 -Subject: [PATCH 099/329] hrtimers: Prepare full preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 099/333] hrtimers: Prepare full preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Make cancellation of a running callback in softirq context safe against preemption. 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 7f79fc69f..6212916aa 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,12 +1,12 @@ -From 6c626da3237f042b61b9a0b31e7c73ac41842b08 Mon Sep 17 00:00:00 2001 -Message-Id: <6c626da3237f042b61b9a0b31e7c73ac41842b08.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d285b697ccc1a44bb4508fa6144c36d3f3c8980e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 3 Jul 2009 08:44:31 -0500 -Subject: [PATCH 100/329] hrtimer: by timers by default into the softirq +Subject: [PATCH 100/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. @@ -32,7 +32,7 @@ Signed-off-by: Sebastian Andrzej Siewior 11 files changed, 37 insertions(+), 14 deletions(-) diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c -index 8c6392534d14..d64ca45f5db6 100644 +index bba2f76c356d..790b5e90426d 100644 --- a/arch/x86/kvm/lapic.c +++ b/arch/x86/kvm/lapic.c @@ -2261,7 +2261,7 @@ int kvm_create_lapic(struct kvm_vcpu *vcpu) @@ -117,7 +117,7 @@ index 311b3cf1270e..7d47c9b9726e 100644 } diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index 80289617ce3d..661b5d6d4197 100644 +index 2443f921b19f..22b8ce4bb107 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4951,9 +4951,9 @@ void init_cfs_bandwidth(struct cfs_bandwidth *cfs_b) 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 f074e8e1f..6214d199e 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,11 +1,11 @@ -From c7bb69d07655a229ad8ef92b216062c4d3bc11c2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 43f1c18878ae682064da14ba2b0c9a51b69de7a1 Mon Sep 17 00:00:00 2001 +Message-Id: <43f1c18878ae682064da14ba2b0c9a51b69de7a1.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 8 Jan 2019 12:31:06 +0100 -Subject: [PATCH 101/329] sched/fair: Make the hrtimers non-hard again -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 101/333] sched/fair: Make the hrtimers non-hard again +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Since commit "sched/fair: Robustify CFS-bandwidth timer locking" both hrtimer can run in softirq context because now interrupts are disabled @@ -17,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index 661b5d6d4197..80289617ce3d 100644 +index 22b8ce4bb107..2443f921b19f 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4951,9 +4951,9 @@ void init_cfs_bandwidth(struct cfs_bandwidth *cfs_b) 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 0a61a63b8..167793047 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,11 +1,11 @@ -From 3f9e3faece468f4feca7178ff48f4cc39dcc6226 Mon Sep 17 00:00:00 2001 -Message-Id: <3f9e3faece468f4feca7178ff48f4cc39dcc6226.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From fd0a8aeb00f06be3a71bca56ed37fb24c27e5382 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Yang Shi Date: Mon, 16 Sep 2013 14:09:19 -0700 -Subject: [PATCH 102/329] hrtimer: Move schedule_work call to helper thread -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 102/333] hrtimer: Move schedule_work call to helper thread +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz When run ltp leapsec_timer test, the following call trace is caught: 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 3050ed6d9..e37c92b29 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,12 +1,12 @@ -From c6453deecbd7587b3ac13b1d97df049d73b95b1d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 299bbb7c83c79dec62877fe5da162aa76dc732b4 Mon Sep 17 00:00:00 2001 +Message-Id: <299bbb7c83c79dec62877fe5da162aa76dc732b4.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 10:15:13 +0100 -Subject: [PATCH 103/329] hrtimer: move state change before hrtimer_cancel in +Subject: [PATCH 103/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 1df70c790..825bbfeb1 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,11 +1,11 @@ -From a9c2c94b513530408d0bce3997002b5a1d0d89b2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 91de2da511e4b8566ae886af68c6a1c13ae03155 Mon Sep 17 00:00:00 2001 +Message-Id: <91de2da511e4b8566ae886af68c6a1c13ae03155.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: John Stultz Date: Fri, 3 Jul 2009 08:29:58 -0500 -Subject: [PATCH 104/329] posix-timers: Thread posix-cpu-timers on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 104/333] posix-timers: Thread posix-cpu-timers on -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz posix-cpu-timer code takes non -rt safe locks in hard irq context. Move it to a thread. 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 e9c92f182..6c9311f71 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,11 +1,11 @@ -From 37348ea2aae637f955a889e33b3ed77b3580b7ca Mon Sep 17 00:00:00 2001 -Message-Id: <37348ea2aae637f955a889e33b3ed77b3580b7ca.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8ebd7e49e0b2aa11da15e78cba4b81a2b2ffb917 Mon Sep 17 00:00:00 2001 +Message-Id: <8ebd7e49e0b2aa11da15e78cba4b81a2b2ffb917.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 May 2011 16:59:16 +0200 -Subject: [PATCH 105/329] sched: Move task_struct cleanup to RCU -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 105/333] sched: Move task_struct cleanup to RCU +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz __put_task_struct() does quite some expensive work. We don't want to burden random tasks with that. 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 39dead58f..572f97b03 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,11 +1,11 @@ -From bd488cd482611dcd51a961890ebd452844fba7ee Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3caee531ffc9042e63f99196f78030aac87d23d6 Mon Sep 17 00:00:00 2001 +Message-Id: <3caee531ffc9042e63f99196f78030aac87d23d6.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:12:51 +0200 -Subject: [PATCH 106/329] 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.135-rt60.tar.xz +Subject: [PATCH 106/333] 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.142-rt63.tar.xz Put an upper limit on the number of tasks which are migrated per batch to avoid large latencies. 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 503d0de3c..6d2233e82 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,11 +1,11 @@ -From 7f1ff4cd6b39bf6153ba39335d5554d843345d68 Mon Sep 17 00:00:00 2001 -Message-Id: <7f1ff4cd6b39bf6153ba39335d5554d843345d68.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 134c4605689b383f718c944bfa6b5882013e758c Mon Sep 17 00:00:00 2001 +Message-Id: <134c4605689b383f718c944bfa6b5882013e758c.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:20:33 +0200 -Subject: [PATCH 107/329] sched: Move mmdrop to RCU on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 107/333] sched: Move mmdrop to RCU on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Takes sleeping locks and calls into the memory allocator, so nothing we want to do in task switch and oder atomic contexts. 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 d0d076211..f85da1aa5 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,12 +1,12 @@ -From d0c187421ce1a2cb768296a6079d1914f00e1bf9 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From fd4b3b2570f723d23a6b0e88abb99ffe2cebf3a3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 21 Nov 2016 19:31:08 +0100 -Subject: [PATCH 108/329] kernel/sched: move stack + kprobe clean up to +Subject: [PATCH 108/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 c16361476..b5f4495a9 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,12 +1,12 @@ -From 100c0ec5ffe14f7b9c0afb47d8cb6c08f249466c Mon Sep 17 00:00:00 2001 -Message-Id: <100c0ec5ffe14f7b9c0afb47d8cb6c08f249466c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a275c27647d9d5ab9af837365cfd8bb49b90d5f9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 25 Jun 2011 09:21:04 +0200 -Subject: [PATCH 109/329] sched: Add saved_state for tasks blocked on sleeping +Subject: [PATCH 109/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 1ad2e33c7..4bab9b375 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,12 +1,12 @@ -From 6b607c25ac8447822464e1b4d8a0c038d729bd88 Mon Sep 17 00:00:00 2001 -Message-Id: <6b607c25ac8447822464e1b4d8a0c038d729bd88.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 21b901c5402bba76c8411b9b847a9963003213b2 Mon Sep 17 00:00:00 2001 +Message-Id: <21b901c5402bba76c8411b9b847a9963003213b2.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 7 Jun 2011 09:19:06 +0200 -Subject: [PATCH 110/329] sched: Do not account rcu_preempt_depth on RT in +Subject: [PATCH 110/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz RT changes the rcu_preempt_depth semantics, so we cannot check for it in might_sleep(). 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 258f1286d..5719f7383 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,11 +1,11 @@ -From 776bb8cf3dc2e9af29075edc62e3d77709248eb0 Mon Sep 17 00:00:00 2001 -Message-Id: <776bb8cf3dc2e9af29075edc62e3d77709248eb0.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b63cd21ec112a059fe8acbab6214652a21b8fb73 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 22:51:33 +0200 -Subject: [PATCH 111/329] 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.135-rt60.tar.xz +Subject: [PATCH 111/333] 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.142-rt63.tar.xz RT does not increment preempt count when a 'sleeping' spinlock is locked. Update PREEMPT_LOCK_OFFSET for that case. 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 6b2fce293..51143d158 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,11 +1,11 @@ -From bc161171317ea0f7b246b0b110d3ebf1161c8230 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From cca041a6802efd54134929454a54bfa6205d5e7d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Sep 2011 16:42:35 +0200 -Subject: [PATCH 112/329] sched: Disable TTWU_QUEUE on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 112/333] sched: Disable TTWU_QUEUE on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The queued remote wakeup mechanism can introduce rather large latencies if the number of migrated tasks is high. Disable it for RT. 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 663d39a5a..63299d290 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,12 +1,12 @@ -From a879ff2aabb742224696f251c36fb20327e91899 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 738ced8ceb96a865a03bcec44f511e144282deb6 Mon Sep 17 00:00:00 2001 +Message-Id: <738ced8ceb96a865a03bcec44f511e144282deb6.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Steven Rostedt Date: Mon, 18 Mar 2013 15:12:49 -0400 -Subject: [PATCH 113/329] sched/workqueue: Only wake up idle workers if not +Subject: [PATCH 113/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 e118f2db0..f442faa10 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,12 +1,12 @@ -From 460bf827ec9fafd856dda44b73ed5634efe3345e Mon Sep 17 00:00:00 2001 -Message-Id: <460bf827ec9fafd856dda44b73ed5634efe3345e.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 7de5d7ddf7407ec92f38959cb6e3eef2c9c1e5a7 Mon Sep 17 00:00:00 2001 +Message-Id: <7de5d7ddf7407ec92f38959cb6e3eef2c9c1e5a7.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Daniel Bristot de Oliveira Date: Mon, 26 Jun 2017 17:07:15 +0200 -Subject: [PATCH 114/329] rt: Increase/decrease the nr of migratory tasks when +Subject: [PATCH 114/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 77db3e571..a061b2cda 100644 --- a/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch +++ b/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch @@ -1,11 +1,11 @@ -From f1067b9d89bf2cca29e379c63773afec076b85a4 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0fcd7f389a9d372c650540b6a611a48f203f9f35 Mon Sep 17 00:00:00 2001 +Message-Id: <0fcd7f389a9d372c650540b6a611a48f203f9f35.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 15 Jun 2011 12:36:06 +0200 -Subject: [PATCH 115/329] hotplug: Lightweight get online cpus -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 115/333] hotplug: Lightweight get online cpus +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz get_online_cpus() is a heavy weight function which involves a global mutex. migrate_disable() wants a simpler construct which prevents only 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 f15e27ae3..6c8a8956a 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,11 +1,11 @@ -From 0234a180c95c0b984b9eeca98ba314996616e9a9 Mon Sep 17 00:00:00 2001 -Message-Id: <0234a180c95c0b984b9eeca98ba314996616e9a9.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 38b6536f258dae17efb329a826c4aa4cf375c43a Mon Sep 17 00:00:00 2001 +Message-Id: <38b6536f258dae17efb329a826c4aa4cf375c43a.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:56:42 +0200 -Subject: [PATCH 116/329] trace: Add migrate-disabled counter to tracing output -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 116/333] trace: Add migrate-disabled counter to tracing output +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Signed-off-by: Thomas Gleixner --- @@ -56,7 +56,7 @@ index 4966410bb0f4..a7b187f74f34 100644 static void print_event_info(struct trace_buffer *buf, struct seq_file *m) diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c -index ec340e1cbffc..1febb0ca4c81 100644 +index 27726121d332..7b59bc9077de 100644 --- a/kernel/trace/trace_events.c +++ b/kernel/trace/trace_events.c @@ -188,6 +188,8 @@ static int trace_define_common_fields(void) 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 9b26abb2a..49bb43808 100644 --- a/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch +++ b/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch @@ -1,11 +1,11 @@ -From d458fcd39ec186a4b8de8c0d4c94a2a6bee11606 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 008f0b26a2129d4e443e077773c3418c2232c592 Mon Sep 17 00:00:00 2001 +Message-Id: <008f0b26a2129d4e443e077773c3418c2232c592.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 18:51:23 +0200 -Subject: [PATCH 117/329] lockdep: Make it RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 117/333] lockdep: Make it RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz teach lockdep that we don't really do softirqs on -RT. 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 72d0df6a8..62b62ed7a 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,12 +1,12 @@ -From c8bb4949b65dad2103f2829601ae7c4e4f45743f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From dce3b749647b1914d5eeb02967be4216716a839c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Tue, 29 Nov 2011 20:18:22 -0500 -Subject: [PATCH 118/329] tasklet: Prevent tasklets from going into infinite +Subject: [PATCH 118/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz When CONFIG_PREEMPT_RT_FULL is enabled, tasklets run as threads, and spinlocks turn are mutexes. But this can cause issues with 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 ed231e39d..80fa57228 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,11 +1,11 @@ -From 0718290d49d6f2ab8780c85b474f04aef7a460be Mon Sep 17 00:00:00 2001 -Message-Id: <0718290d49d6f2ab8780c85b474f04aef7a460be.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From bd59e79bda09bb9577a33887cc1554ef32006551 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 13 Nov 2011 17:17:09 +0100 -Subject: [PATCH 119/329] softirq: Check preemption after reenabling interrupts -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 119/333] softirq: Check preemption after reenabling interrupts +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz raise_softirq_irqoff() disables interrupts and wakes the softirq daemon, but after reenabling interrupts there is no preemption check, @@ -120,7 +120,7 @@ index 86a709954f5a..9c069ef83d6d 100644 return 0; } diff --git a/net/core/dev.c b/net/core/dev.c -index 4b1053057ca6..1f221e369032 100644 +index 42ba150fa18d..4ae89dc192d9 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -2723,6 +2723,7 @@ static void __netif_reschedule(struct Qdisc *q) 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 96deb4911..8b3454d6e 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,11 +1,11 @@ -From fcf6b88da10c62871f28956a0390a19e3379b42e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9520b077f06313eb86a23ae52d847ac5104ca122 Mon Sep 17 00:00:00 2001 +Message-Id: <9520b077f06313eb86a23ae52d847ac5104ca122.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 13:59:17 +0200 -Subject: [PATCH 120/329] softirq: Disable softirq stacks for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 120/333] softirq: Disable softirq stacks for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Disable extra stacks for softirqs. We want to preempt softirqs and having them on special IRQ-stack does not make this easier. diff --git a/debian/patches-rt/0121-softirq-Split-softirq-locks.patch b/debian/patches-rt/0121-softirq-Split-softirq-locks.patch index 8522e93ae..5d226e269 100644 --- a/debian/patches-rt/0121-softirq-Split-softirq-locks.patch +++ b/debian/patches-rt/0121-softirq-Split-softirq-locks.patch @@ -1,11 +1,11 @@ -From c82069adfa44bb0c556ddb4e90b5c0b241366694 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 492bfe973a1387e719d2a17a35248c4523c2144d Mon Sep 17 00:00:00 2001 +Message-Id: <492bfe973a1387e719d2a17a35248c4523c2144d.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 4 Oct 2012 14:20:47 +0100 -Subject: [PATCH 121/329] softirq: Split softirq locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 121/333] softirq: Split softirq locks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 00700b1d9..a29983a30 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,11 +1,11 @@ -From 740e990c07d7bbe8c56b3e0a8b24e11795958190 Mon Sep 17 00:00:00 2001 -Message-Id: <740e990c07d7bbe8c56b3e0a8b24e11795958190.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0b733133303f8c4ad3019801c331009bdb1a4c8c Mon Sep 17 00:00:00 2001 +Message-Id: <0b733133303f8c4ad3019801c331009bdb1a4c8c.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 16 Jun 2017 19:03:16 +0200 -Subject: [PATCH 122/329] 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.135-rt60.tar.xz +Subject: [PATCH 122/333] 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.142-rt63.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 @@ -22,7 +22,7 @@ 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 1f221e369032..2bfd79026bb3 100644 +index 4ae89dc192d9..e89ae804e68a 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -4526,11 +4526,9 @@ int netif_rx_ni(struct sk_buff *skb) 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 b18962ca0..91d26a22a 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,12 +1,12 @@ -From b3780ae29e481b63d9dfe2ddb6cea8535e27d188 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e354e8b0935d35f74ae2d7943401b63082113c79 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 Jan 2012 13:01:27 +0100 -Subject: [PATCH 123/329] genirq: Allow disabling of softirq processing in irq +Subject: [PATCH 123/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -44,7 +44,7 @@ index cf9860d49d57..e1438fe66467 100644 #define IRQF_TIMER (__IRQF_TIMER | IRQF_NO_SUSPEND | IRQF_NO_THREAD) diff --git a/include/linux/irq.h b/include/linux/irq.h -index 6ecaf056ab63..d2487df7ae89 100644 +index a042faefb9b7..e3ed5e02605f 100644 --- a/include/linux/irq.h +++ b/include/linux/irq.h @@ -69,6 +69,7 @@ enum irqchip_irq_state; @@ -72,10 +72,10 @@ index 6ecaf056ab63..d2487df7ae89 100644 #define IRQ_NO_BALANCING_MASK (IRQ_PER_CPU | IRQ_NO_BALANCING) diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c -index b57d1a2d4d79..44ee91ca0088 100644 +index 98f9bb27ce37..bb2825ed4bf0 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c -@@ -990,7 +990,15 @@ irq_forced_thread_fn(struct irq_desc *desc, struct irqaction *action) +@@ -994,7 +994,15 @@ irq_forced_thread_fn(struct irq_desc *desc, struct irqaction *action) atomic_inc(&desc->threads_handled); irq_finalize_oneshot(desc, action); @@ -92,7 +92,7 @@ index b57d1a2d4d79..44ee91ca0088 100644 return ret; } -@@ -1500,6 +1508,9 @@ __setup_irq(unsigned int irq, struct irq_desc *desc, struct irqaction *new) +@@ -1504,6 +1512,9 @@ __setup_irq(unsigned int irq, struct irq_desc *desc, struct irqaction *new) irqd_set(&desc->irq_data, IRQD_NO_BALANCING); } 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 76373adb4..1dc698c0b 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,11 +1,11 @@ -From 3533db89c1aea4df835e65d57b772b401072c661 Mon Sep 17 00:00:00 2001 -Message-Id: <3533db89c1aea4df835e65d57b772b401072c661.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ee908489662aded68ae324c777e748d562ef0f81 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 16:34:17 +0100 -Subject: [PATCH 124/329] softirq: split timer softirqs out of ksoftirqd -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 124/333] softirq: split timer softirqs out of ksoftirqd +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 ec782600d..5c46ebad7 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,12 +1,12 @@ -From 459bfeb44aa76d1d7baf88d6ba0c1f4b766405ee Mon Sep 17 00:00:00 2001 -Message-Id: <459bfeb44aa76d1d7baf88d6ba0c1f4b766405ee.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 4cda3be0432217f57bf6550767ac2cea1832a169 Mon Sep 17 00:00:00 2001 +Message-Id: <4cda3be0432217f57bf6550767ac2cea1832a169.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 13:19:59 +0100 -Subject: [PATCH 125/329] softirq: Avoid "local_softirq_pending" messages if +Subject: [PATCH 125/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 48f4d8839..c4d402c8c 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,12 +1,12 @@ -From 4eb4b9fdcc6c1cc28976d3b3a95a24a0c2af8229 Mon Sep 17 00:00:00 2001 -Message-Id: <4eb4b9fdcc6c1cc28976d3b3a95a24a0c2af8229.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 025c5c2cce5efd9e9e7bbd510ed7044ba8df97b4 Mon Sep 17 00:00:00 2001 +Message-Id: <025c5c2cce5efd9e9e7bbd510ed7044ba8df97b4.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:49:29 +0100 -Subject: [PATCH 126/329] softirq: Avoid "local_softirq_pending" messages if +Subject: [PATCH 126/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 bf7f6059b..69644642c 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,11 +1,11 @@ -From eaf38ce6817d9bc5517e9dede4ab98547f530d04 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ad0a4901f2ae71a2c87dc318b9b4273c38879607 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 2 Dec 2015 11:34:07 +0100 -Subject: [PATCH 127/329] rtmutex: trylock is okay on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 127/333] rtmutex: trylock is okay on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 43ab74998..0ab5b09b2 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,11 +1,11 @@ -From 21e6449d0b679f7ab9210981b73cd02ee9a037d3 Mon Sep 17 00:00:00 2001 -Message-Id: <21e6449d0b679f7ab9210981b73cd02ee9a037d3.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 61ade7401ba060b26212bfa052d6b051c811ba2c Mon Sep 17 00:00:00 2001 +Message-Id: <61ade7401ba060b26212bfa052d6b051c811ba2c.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 15 Sep 2016 10:51:27 +0200 -Subject: [PATCH 128/329] fs/nfs: turn rmdir_sem into a semaphore -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 128/333] fs/nfs: turn rmdir_sem into a semaphore +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 15b1bf16e..735c4ba09 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,11 +1,11 @@ -From 3f1a27b090d37cf4986c1588c14aa22737213e9d Mon Sep 17 00:00:00 2001 -Message-Id: <3f1a27b090d37cf4986c1588c14aa22737213e9d.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From c37efa4711b712a297aaafed9d8ecbcae2a691a6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 10 Jun 2011 11:04:15 +0200 -Subject: [PATCH 129/329] rtmutex: Handle the various new futex race conditions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 129/333] rtmutex: Handle the various new futex race conditions +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 dfb02ec4e..073fb6c5a 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,11 +1,11 @@ -From 44218ed88f0073fad6c8de029a1b14ef6a704714 Mon Sep 17 00:00:00 2001 -Message-Id: <44218ed88f0073fad6c8de029a1b14ef6a704714.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3ddab0575b3a30f09b2eb14dfecf7ee717381e34 Mon Sep 17 00:00:00 2001 +Message-Id: <3ddab0575b3a30f09b2eb14dfecf7ee717381e34.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 130/329] 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.135-rt60.tar.xz +Subject: [PATCH 130/333] 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.142-rt63.tar.xz Requeue with timeout causes a bug with PREEMPT_RT_FULL. 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 736a3cb7e..2e2e663dd 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,12 +1,12 @@ -From f615fa327f051cb858d6ff6c56a9993fbd566219 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0e286eeb58e0fabef5a7569cc460d46294a140b5 Mon Sep 17 00:00:00 2001 +Message-Id: <0e286eeb58e0fabef5a7569cc460d46294a140b5.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 1 Mar 2013 11:17:42 +0100 -Subject: [PATCH 131/329] futex: Ensure lock/unlock symetry versus pi_lock and +Subject: [PATCH 131/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz In exit_pi_state_list() we have the following locking construct: 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 2e465401a..6abd2863b 100644 --- a/debian/patches-rt/0132-pid.h-include-atomic.h.patch +++ b/debian/patches-rt/0132-pid.h-include-atomic.h.patch @@ -1,11 +1,11 @@ -From 38e6ad787f77a62534738eca0093d24df844f869 Mon Sep 17 00:00:00 2001 -Message-Id: <38e6ad787f77a62534738eca0093d24df844f869.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8ff56ec5165db1745893222f05707118a8e52b07 Mon Sep 17 00:00:00 2001 +Message-Id: <8ff56ec5165db1745893222f05707118a8e52b07.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Grygorii Strashko Date: Tue, 21 Jul 2015 19:43:56 +0300 -Subject: [PATCH 132/329] pid.h: include atomic.h -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 132/333] pid.h: include atomic.h +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz This patch fixes build error: CC kernel/pid_namespace.o 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 9b8cb6dc5..45dcb1218 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,11 +1,11 @@ -From 275b49dcdf8d653c81c2d1e0bd159aabb887d672 Mon Sep 17 00:00:00 2001 -Message-Id: <275b49dcdf8d653c81c2d1e0bd159aabb887d672.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 49b2cb8ee0d5cf4a22b3b67e08ed1a29f8a2090e Mon Sep 17 00:00:00 2001 +Message-Id: <49b2cb8ee0d5cf4a22b3b67e08ed1a29f8a2090e.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 22 Dec 2016 17:28:33 +0100 -Subject: [PATCH 133/329] arm: include definition for cpumask_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 133/333] arm: include definition for cpumask_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz This definition gets pulled in by other files. With the (later) split of RCU and spinlock.h it won't compile anymore. 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 81c4199c7..6fd776bd6 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,12 +1,12 @@ -From 99cd2070e221ec9d05b1918031951ff9cdefa221 Mon Sep 17 00:00:00 2001 -Message-Id: <99cd2070e221ec9d05b1918031951ff9cdefa221.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0360d5fc6a654880d467cf9b9145efe1275ab0a1 Mon Sep 17 00:00:00 2001 +Message-Id: <0360d5fc6a654880d467cf9b9145efe1275ab0a1.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Wolfgang M. Reimer" Date: Tue, 21 Jul 2015 16:20:07 +0200 -Subject: [PATCH 134/329] locking: locktorture: Do NOT include rwlock.h +Subject: [PATCH 134/333] locking: locktorture: Do NOT include rwlock.h directly -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Including rwlock.h directly will cause kernel builds to fail if CONFIG_PREEMPT_RT_FULL is defined. The correct header file 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 63c911849..231fdd5cc 100644 --- a/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch +++ b/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch @@ -1,11 +1,11 @@ -From 6df4846a6a073e53b0fbb0f66e595b9027c04915 Mon Sep 17 00:00:00 2001 -Message-Id: <6df4846a6a073e53b0fbb0f66e595b9027c04915.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ef5bd7add518caa468c1bc25c4fecf46fef3156f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 9 Jun 2011 11:43:52 +0200 -Subject: [PATCH 135/329] rtmutex: Add rtmutex_lock_killable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 135/333] rtmutex: Add rtmutex_lock_killable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Add "killable" type to rtmutex. We need this since rtmutex are used as "normal" mutexes which do use this type. 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 96e46154a..403158c39 100644 --- a/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch +++ b/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch @@ -1,11 +1,11 @@ -From c0d925808e62d8cdd687069c3d5e349ecc66803f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e16950b4e8739f72860ae776569daa8e09e823f6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 1 Apr 2017 12:50:59 +0200 -Subject: [PATCH 136/329] rtmutex: Make lock_killable work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 136/333] rtmutex: Make lock_killable work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Locking an rt mutex killable does not work because signal handling is restricted to TASK_INTERRUPTIBLE. 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 7c101eeee..f239385f9 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,11 +1,11 @@ -From 01bba13d3844991e6086214cb2c2481265dd50bb Mon Sep 17 00:00:00 2001 -Message-Id: <01bba13d3844991e6086214cb2c2481265dd50bb.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 723ef2ac2d169242575ff981f0efee6e71bfc4e0 Mon Sep 17 00:00:00 2001 +Message-Id: <723ef2ac2d169242575ff981f0efee6e71bfc4e0.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 19:34:01 +0200 -Subject: [PATCH 137/329] spinlock: Split the lock types header -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 137/333] spinlock: Split the lock types header +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 diff --git a/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch b/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch index 56ad55fe0..410d57d63 100644 --- a/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch +++ b/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch @@ -1,11 +1,11 @@ -From 6d84cc2aff3c518753ade35902f64968cf928527 Mon Sep 17 00:00:00 2001 -Message-Id: <6d84cc2aff3c518753ade35902f64968cf928527.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 838f57264a5ebf0c0fa0047fe2bda8fc71e4ec26 Mon Sep 17 00:00:00 2001 +Message-Id: <838f57264a5ebf0c0fa0047fe2bda8fc71e4ec26.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 20:06:39 +0200 -Subject: [PATCH 138/329] rtmutex: Avoid include hell -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 138/333] rtmutex: Avoid include hell +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 802118650..384dae893 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,14 +1,14 @@ -From b778a880184bc3cc5338bbaed65315dc3a1b5e6d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 70932c995739d44411bf615a7ea194c294275105 Mon Sep 17 00:00:00 2001 +Message-Id: <70932c995739d44411bf615a7ea194c294275105.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 16:56:02 +0100 -Subject: [PATCH 139/329] rbtree: don't include the rcu header +Subject: [PATCH 139/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The RCU header pulls in spinlock.h and fails due not yet defined types: 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 06a7cc0fc..d6d1a5472 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,11 +1,11 @@ -From ae7ac78b4107170bec606678c9da742bd26d53a2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d8a5876053cd27ba25b1c784e2517c35c7dbc1ac Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:14:22 +0200 -Subject: [PATCH 140/329] rtmutex: Provide rt_mutex_slowlock_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 140/333] rtmutex: Provide rt_mutex_slowlock_locked() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz This is the inner-part of rt_mutex_slowlock(), required for rwsem-rt. 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 426c41ddb..d8bcb211c 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,12 +1,12 @@ -From 0146796c4aec3c2be0dfa1587a466e7c7a8ea21e Mon Sep 17 00:00:00 2001 -Message-Id: <0146796c4aec3c2be0dfa1587a466e7c7a8ea21e.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 6881457c721ed3ee6ba1e57a20e24e5da50f6b2a Mon Sep 17 00:00:00 2001 +Message-Id: <6881457c721ed3ee6ba1e57a20e24e5da50f6b2a.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:36:39 +0200 -Subject: [PATCH 141/329] rtmutex: export lockdep-less version of rt_mutex's +Subject: [PATCH 141/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Required for lock implementation ontop of rtmutex. 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 e0ff1e46a..27fd200a1 100644 --- a/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch +++ b/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch @@ -1,11 +1,11 @@ -From 1d24f62a58831696d65827e9e59fd3723edca08f Mon Sep 17 00:00:00 2001 -Message-Id: <1d24f62a58831696d65827e9e59fd3723edca08f.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8995742f3f92b7f78eb22e83fb04d716115d7314 Mon Sep 17 00:00:00 2001 +Message-Id: <8995742f3f92b7f78eb22e83fb04d716115d7314.1599166690.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:11:19 +0200 -Subject: [PATCH 142/329] rtmutex: add sleeping lock implementation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 142/333] rtmutex: add sleeping lock implementation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior 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 2fd5887df..b82ad9c37 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,11 +1,11 @@ -From f4009c56f911f54e3e60e7f2bd6e3c124213078a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1eec264a80b19b45955007000d0228b576c2c2c8 Mon Sep 17 00:00:00 2001 +Message-Id: <1eec264a80b19b45955007000d0228b576c2c2c8.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:17:03 +0200 -Subject: [PATCH 143/329] rtmutex: add mutex implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 143/333] rtmutex: add mutex implementation based on rtmutex +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior 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 649dfd8f4..20f9ad1f3 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,11 +1,11 @@ -From acb23c1b1a68937154eb5467e2e6007fef19194f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0c5335fdd3e8f49c694e6f613251ad018ec1e74b Mon Sep 17 00:00:00 2001 +Message-Id: <0c5335fdd3e8f49c694e6f613251ad018ec1e74b.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:28:34 +0200 -Subject: [PATCH 144/329] rtmutex: add rwsem implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 144/333] rtmutex: add rwsem implementation based on rtmutex +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 1741a203d..09bc52ff5 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,11 +1,11 @@ -From d3a7157a94f3deb3010258fba05c16227c43f98e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1281ba28493dfd84187fbf5485be4372d6e8420f Mon Sep 17 00:00:00 2001 +Message-Id: <1281ba28493dfd84187fbf5485be4372d6e8420f.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:18:06 +0200 -Subject: [PATCH 145/329] rtmutex: add rwlock implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 145/333] rtmutex: add rwlock implementation based on rtmutex +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The implementation is bias-based, similar to the rwsem implementation. 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 4d85c7aaa..ba571d843 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,11 +1,11 @@ -From 1bf646bbe988fa7df03bc28495b7c1d741936dc6 Mon Sep 17 00:00:00 2001 -Message-Id: <1bf646bbe988fa7df03bc28495b7c1d741936dc6.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 562b9e1e592b03a33734b74286a03ffc480a27bc Mon Sep 17 00:00:00 2001 +Message-Id: <562b9e1e592b03a33734b74286a03ffc480a27bc.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 11 Jan 2019 21:16:31 +0100 -Subject: [PATCH 146/329] rtmutex/rwlock: preserve state like a sleeping lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 146/333] rtmutex/rwlock: preserve state like a sleeping lock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 626098595..c607d9702 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,11 +1,11 @@ -From 4d135acef36b84effe3d80323633a89735197d83 Mon Sep 17 00:00:00 2001 -Message-Id: <4d135acef36b84effe3d80323633a89735197d83.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e9d6b751fa363a8e4a8a897c2a9c47f9431e8239 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:31:14 +0200 -Subject: [PATCH 147/329] rtmutex: wire up RT's locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 147/333] rtmutex: wire up RT's locking +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior 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 aff409152..c65980624 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,11 +1,11 @@ -From 23e3e9450b17f5fc8e296f1c867a7389f97262a6 Mon Sep 17 00:00:00 2001 -Message-Id: <23e3e9450b17f5fc8e296f1c867a7389f97262a6.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 437897d38181ac9ea208438f3528cdf4c3131632 Mon Sep 17 00:00:00 2001 +Message-Id: <437897d38181ac9ea208438f3528cdf4c3131632.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 17:34:38 +0200 -Subject: [PATCH 148/329] rtmutex: add ww_mutex addon for mutex-rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 148/333] rtmutex: add ww_mutex addon for mutex-rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Signed-off-by: Sebastian Andrzej Siewior --- 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 296362f4d..13928f45f 100644 --- a/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch +++ b/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch @@ -1,11 +1,11 @@ -From 0b16103582e7b3af05eef69306659b23027db026 Mon Sep 17 00:00:00 2001 -Message-Id: <0b16103582e7b3af05eef69306659b23027db026.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0cd89697723650359c87725e7dc20841ade4bba0 Mon Sep 17 00:00:00 2001 +Message-Id: <0cd89697723650359c87725e7dc20841ade4bba0.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 14:58:57 +0200 -Subject: [PATCH 149/329] kconfig: Add PREEMPT_RT_FULL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 149/333] kconfig: Add PREEMPT_RT_FULL +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Introduce the final symbol for PREEMPT_RT_FULL. 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 40a03156a..4cdc019c1 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,12 +1,12 @@ -From 064f3508fa2222f59ae1db5a54d62aed64c8774f Mon Sep 17 00:00:00 2001 -Message-Id: <064f3508fa2222f59ae1db5a54d62aed64c8774f.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From c777449f38433b285f537400e7cfed771da37dd2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mikulas Patocka Date: Mon, 13 Nov 2017 12:56:53 -0500 -Subject: [PATCH 150/329] locking/rt-mutex: fix deadlock in device mapper / +Subject: [PATCH 150/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 babc24ebb..62b2d60ff 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,11 +1,11 @@ -From 9a632f48608316f87e79b4c50c8fec1a0923f59f Mon Sep 17 00:00:00 2001 -Message-Id: <9a632f48608316f87e79b4c50c8fec1a0923f59f.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3a32a25b1568a31ff6b596aae816fdfaa38c0b08 Mon Sep 17 00:00:00 2001 +Message-Id: <3a32a25b1568a31ff6b596aae816fdfaa38c0b08.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 4 Jan 2019 15:33:21 -0500 -Subject: [PATCH 151/329] 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.135-rt60.tar.xz +Subject: [PATCH 151/333] 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.142-rt63.tar.xz __down_read() bypasses the rtmutex frontend to call rt_mutex_slowlock_locked() directly, and thus it needs to call 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 392e12514..a9fd533d3 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,12 +1,12 @@ -From 5b9a5316691f167599f18843a8e146af2e795f21 Mon Sep 17 00:00:00 2001 -Message-Id: <5b9a5316691f167599f18843a8e146af2e795f21.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2cc1b43b5583d99c7a7293fa0681529722382901 Mon Sep 17 00:00:00 2001 +Message-Id: <2cc1b43b5583d99c7a7293fa0681529722382901.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 16 Nov 2017 16:48:48 +0100 -Subject: [PATCH 152/329] locking/rtmutex: re-init the wait_lock in +Subject: [PATCH 152/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 8f4e30cfe..2dcdecdf7 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,11 +1,11 @@ -From b951831b474dba307b7a0e2a8df3f9636526348c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2e84fde1605de2122b8c01f2878f0d12448e1b95 Mon Sep 17 00:00:00 2001 +Message-Id: <2e84fde1605de2122b8c01f2878f0d12448e1b95.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 18:21:04 +0200 -Subject: [PATCH 153/329] ptrace: fix ptrace vs tasklist_lock race -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 153/333] ptrace: fix ptrace vs tasklist_lock race +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz As explained by Alexander Fyodorov : 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 92c1927d3..5adcecd00 100644 --- a/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch +++ b/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch @@ -1,11 +1,11 @@ -From 076f3d83dbde0ce989d16b9fe260dd19abad7b1c Mon Sep 17 00:00:00 2001 -Message-Id: <076f3d83dbde0ce989d16b9fe260dd19abad7b1c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 05d70eb28e951f4f19037250e589c85532b12836 Mon Sep 17 00:00:00 2001 +Message-Id: <05d70eb28e951f4f19037250e589c85532b12836.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Sep 2017 14:25:13 +0200 -Subject: [PATCH 154/329] rtmutex: annotate sleeping lock context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 154/333] rtmutex: annotate sleeping lock context +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 84174336d..271dfcb93 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,12 +1,12 @@ -From 810aea0ca134ee70c3386044bfa564eec19cd6bf Mon Sep 17 00:00:00 2001 -Message-Id: <810aea0ca134ee70c3386044bfa564eec19cd6bf.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1b8fe659df64e431894e6b47a3b18a228f622bb1 Mon Sep 17 00:00:00 2001 +Message-Id: <1b8fe659df64e431894e6b47a3b18a228f622bb1.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 5 Jul 2018 14:44:51 +0200 -Subject: [PATCH 155/329] sched/migrate_disable: fallback to preempt_disable() +Subject: [PATCH 155/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 7d2913998..c04d3a8ea 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,12 +1,12 @@ -From 3614213f60d3663b42b126bddd58028115a446ca Mon Sep 17 00:00:00 2001 -Message-Id: <3614213f60d3663b42b126bddd58028115a446ca.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3ca29d5a3a9c3e1b194296b991643ba122d694ac Mon Sep 17 00:00:00 2001 +Message-Id: <3ca29d5a3a9c3e1b194296b991643ba122d694ac.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 17:40:42 +0200 -Subject: [PATCH 156/329] locking: don't check for __LINUX_SPINLOCK_TYPES_H on +Subject: [PATCH 156/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Upstream uses arch_spinlock_t within spinlock_t and requests that spinlock_types.h header file is included first. diff --git a/debian/patches-rt/0157-rcu-Frob-softirq-test.patch b/debian/patches-rt/0157-rcu-Frob-softirq-test.patch index 912eeee48..94e34c038 100644 --- a/debian/patches-rt/0157-rcu-Frob-softirq-test.patch +++ b/debian/patches-rt/0157-rcu-Frob-softirq-test.patch @@ -1,11 +1,11 @@ -From 7bd62defa46ace7255f7b62bc28863c1bb1d44e1 Mon Sep 17 00:00:00 2001 -Message-Id: <7bd62defa46ace7255f7b62bc28863c1bb1d44e1.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ff33b0e8ed0549f1a9c8344bd6d3137dfc0f25d4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Peter Zijlstra Date: Sat, 13 Aug 2011 00:23:17 +0200 -Subject: [PATCH 157/329] rcu: Frob softirq test -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 157/333] rcu: Frob softirq test +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz With RT_FULL we get the below wreckage: 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 2bb48a58c..892ed5774 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,11 +1,11 @@ -From 9118ae152c3ef6428fce024051c2eed3b0e1b1ce Mon Sep 17 00:00:00 2001 -Message-Id: <9118ae152c3ef6428fce024051c2eed3b0e1b1ce.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5681e204713950bb03fa2bd3438190deaa7af51a Mon Sep 17 00:00:00 2001 +Message-Id: <5681e204713950bb03fa2bd3438190deaa7af51a.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 5 Oct 2011 11:59:38 -0700 -Subject: [PATCH 158/329] rcu: Merge RCU-bh into RCU-preempt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 158/333] rcu: Merge RCU-bh into RCU-preempt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The Linux kernel has long RCU-bh read-side critical sections that intolerably increase scheduling latency under mainline's RCU-bh rules, 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 bf9de54f7..0644043be 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,11 +1,11 @@ -From 3f287b9dab00c201ffe7712b2070c8d3532b51de Mon Sep 17 00:00:00 2001 -Message-Id: <3f287b9dab00c201ffe7712b2070c8d3532b51de.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ecb6f10df4f23e573758171266abb5e071001f05 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Wed, 5 Oct 2011 11:45:18 -0700 -Subject: [PATCH 159/329] rcu: Make ksoftirqd do RCU quiescent states -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 159/333] rcu: Make ksoftirqd do RCU quiescent states +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Implementing RCU-bh in terms of RCU-preempt makes the system vulnerable to network-based denial-of-service attacks. This patch therefore 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 865a71289..c6ca36060 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,11 +1,11 @@ -From ecca310500e8f26b98c45931b09a60141db87b87 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From eb33b320bbbda32bbb909c965c4901fa7398a2ae Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 4 Nov 2013 13:21:10 -0800 -Subject: [PATCH 160/329] rcu: Eliminate softirq processing from rcutree -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 160/333] rcu: Eliminate softirq processing from rcutree +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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, 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 79e569d27..8354f328f 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,11 +1,11 @@ -From 2c38ac8778a152f8f7bb227416c86efe5898ecbc Mon Sep 17 00:00:00 2001 -Message-Id: <2c38ac8778a152f8f7bb227416c86efe5898ecbc.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 4df2566ff0bf03e45cec7b83599e95147cde3a76 Mon Sep 17 00:00:00 2001 +Message-Id: <4df2566ff0bf03e45cec7b83599e95147cde3a76.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 14:43:41 +0200 -Subject: [PATCH 161/329] srcu: use cpu_online() instead custom check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 161/333] srcu: use cpu_online() instead custom check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 8a025e885..53e4782f8 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,11 +1,11 @@ -From 3431f65041d5f4a33169c2acf14ba2157d546f7b Mon Sep 17 00:00:00 2001 -Message-Id: <3431f65041d5f4a33169c2acf14ba2157d546f7b.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 75bdd0f27581cd157073ef3f67d360fa219c9256 Mon Sep 17 00:00:00 2001 +Message-Id: <75bdd0f27581cd157073ef3f67d360fa219c9256.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 18:37:12 +0200 -Subject: [PATCH 162/329] srcu: replace local_irqsave() with a locallock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 162/333] srcu: replace local_irqsave() with a locallock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 d671c2b51..8cebc0625 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,11 +1,11 @@ -From 65160311d558fbe5d0aaae8a03ecbf56a42ff10c Mon Sep 17 00:00:00 2001 -Message-Id: <65160311d558fbe5d0aaae8a03ecbf56a42ff10c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 02a06f1173e825d9aefe8549c713a9a00d0172ce Mon Sep 17 00:00:00 2001 +Message-Id: <02a06f1173e825d9aefe8549c713a9a00d0172ce.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julia Cartwright Date: Wed, 12 Oct 2016 11:21:14 -0500 -Subject: [PATCH 163/329] 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.135-rt60.tar.xz +Subject: [PATCH 163/333] 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.142-rt63.tar.xz The forcing of an expedited grace period is an expensive and very RT-application unfriendly operation, as it forcibly preempts all running 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 fbc93cbb0..d8906fe04 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,11 +1,11 @@ -From 837f9ac5cf843158a80eed6d60166ee7c9716c1a Mon Sep 17 00:00:00 2001 -Message-Id: <837f9ac5cf843158a80eed6d60166ee7c9716c1a.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 6b1db457140e7796db237a79620c5aaebc717c35 Mon Sep 17 00:00:00 2001 +Message-Id: <6b1db457140e7796db237a79620c5aaebc717c35.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 28 Jul 2011 13:32:57 +0200 -Subject: [PATCH 164/329] tty/serial/omap: Make the locking RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 164/333] tty/serial/omap: Make the locking RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 3b9c4a09f..91b419d79 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,11 +1,11 @@ -From 36ca3c9c25fab5bab99fc8d570a19957883cf187 Mon Sep 17 00:00:00 2001 -Message-Id: <36ca3c9c25fab5bab99fc8d570a19957883cf187.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 54b2a30553b0d471b3e6ef3993004831ef60a5fd Mon Sep 17 00:00:00 2001 +Message-Id: <54b2a30553b0d471b3e6ef3993004831ef60a5fd.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 8 Jan 2013 21:36:51 +0100 -Subject: [PATCH 165/329] 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.135-rt60.tar.xz +Subject: [PATCH 165/333] 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.142-rt63.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. 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 69df58018..3295307d2 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,15 +1,15 @@ -From 5efe8f58b68a6c29e56e1f8d2ee649f9fd51556c Mon Sep 17 00:00:00 2001 -Message-Id: <5efe8f58b68a6c29e56e1f8d2ee649f9fd51556c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b12623d1f1f51dd08880e56741f9fda2af4c1a39 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Kurt Kanzenbach Date: Mon, 24 Sep 2018 10:29:01 +0200 -Subject: [PATCH 166/329] tty: serial: pl011: explicitly initialize the flags +Subject: [PATCH 166/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Silence the following gcc warning: 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 8df01ace6..e30bc89ad 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,14 +1,14 @@ -From d3da9ac80ca53a41300046b8235d29328fbc0679 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9c8a1f057ad620e0aeec26656823a43c7c769cb7 Mon Sep 17 00:00:00 2001 +Message-Id: <9c8a1f057ad620e0aeec26656823a43c7c769cb7.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Ingo Molnar Date: Wed, 14 Dec 2011 13:05:54 +0100 -Subject: [PATCH 167/329] rt: Improve the serial console PASS_LIMIT +Subject: [PATCH 167/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Beyond the warning: 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 74d59cc90..9bf74ae85 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,11 +1,11 @@ -From a68d879da540e988c941ac8378c651d3c016d365 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d901b86539efde0474129016eb7d00e4dd709461 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Apr 2016 16:55:02 +0200 -Subject: [PATCH 168/329] 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.135-rt60.tar.xz +Subject: [PATCH 168/333] 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.142-rt63.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 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 15e99ef8b..567c89e6f 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,11 +1,11 @@ -From 3b4b838f82c5d2d97cb8b4b8f076171728bfdf16 Mon Sep 17 00:00:00 2001 -Message-Id: <3b4b838f82c5d2d97cb8b4b8f076171728bfdf16.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0c78c826722df4f2724ba6e4c293f404743f7d18 Mon Sep 17 00:00:00 2001 +Message-Id: <0c78c826722df4f2724ba6e4c293f404743f7d18.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Peter Zijlstra Date: Wed, 23 Nov 2016 16:29:32 +0100 -Subject: [PATCH 169/329] locking/percpu-rwsem: Remove preempt_disable variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 169/333] locking/percpu-rwsem: Remove preempt_disable variants +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Effective revert commit: 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 fbc8540ca..93e3be92d 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,12 +1,12 @@ -From 7cc501339a265ddc15181e7a2ef2a02fe41dcda2 Mon Sep 17 00:00:00 2001 -Message-Id: <7cc501339a265ddc15181e7a2ef2a02fe41dcda2.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a91081d973896af982616563bb8f39fa38f46699 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Yong Zhang Date: Tue, 15 May 2012 13:53:56 +0800 -Subject: [PATCH 170/329] mm: Protect activate_mm() by +Subject: [PATCH 170/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz User preempt_*_rt instead of local_irq_*_rt or otherwise there will be warning on ARM like below: 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 0f54ef72d..e3374f993 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,12 +1,12 @@ -From 4ce6c433bcbb3858fcb29399ff85bdec545ee086 Mon Sep 17 00:00:00 2001 -Message-Id: <4ce6c433bcbb3858fcb29399ff85bdec545ee086.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 60ce3790104726c39388b113bf9c9f022770eaa8 Mon Sep 17 00:00:00 2001 +Message-Id: <60ce3790104726c39388b113bf9c9f022770eaa8.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 12:32:34 +0200 -Subject: [PATCH 171/329] fs/dcache: bring back explicit INIT_HLIST_BL_HEAD +Subject: [PATCH 171/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 747951b49..c1b2b3ea5 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,12 +1,12 @@ -From 8a569194eac8203dcaf7b82b233db67ecd27ee3d Mon Sep 17 00:00:00 2001 -Message-Id: <8a569194eac8203dcaf7b82b233db67ecd27ee3d.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 985a0260ccd8020cbbf65780120f1528e5e7aa2e Mon Sep 17 00:00:00 2001 +Message-Id: <985a0260ccd8020cbbf65780120f1528e5e7aa2e.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 20 Oct 2017 11:29:53 +0200 -Subject: [PATCH 172/329] fs/dcache: disable preemption on i_dir_seq's write +Subject: [PATCH 172/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 fb416f002..01064f8cb 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,12 +1,12 @@ -From 52ac8bec759bebef11e9f40442b77963632790e7 Mon Sep 17 00:00:00 2001 -Message-Id: <52ac8bec759bebef11e9f40442b77963632790e7.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2ab847f8db9da25be9941d44db417c3f15995e0a Mon Sep 17 00:00:00 2001 +Message-Id: <2ab847f8db9da25be9941d44db417c3f15995e0a.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:57 -0500 -Subject: [PATCH 173/329] squashfs: make use of local lock in multi_cpu +Subject: [PATCH 173/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Currently, the squashfs multi_cpu decompressor makes use of get_cpu_ptr()/put_cpu_ptr(), which unconditionally disable preemption 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 602c0aa1a..c537ff3b6 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,11 +1,11 @@ -From 8af460950014ad92c770eb80d2ecb12033a60462 Mon Sep 17 00:00:00 2001 -Message-Id: <8af460950014ad92c770eb80d2ecb12033a60462.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b581682b7dc0131e8d52e9ff404a13005f4b00f4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 -Subject: [PATCH 174/329] thermal: Defer thermal wakups to threads -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 174/333] thermal: Defer thermal wakups to threads +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz On RT the spin lock in pkg_temp_thermal_platfrom_thermal_notify will call schedule while we run in irq context. 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 744fb3120..6cd518949 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,11 +1,11 @@ -From 464c8fff871a40fb5eee0b896bc42d7d82249e1d Mon Sep 17 00:00:00 2001 -Message-Id: <464c8fff871a40fb5eee0b896bc42d7d82249e1d.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a8a5de903659159f5de58c8a0bc4dffbe6bc2f44 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 15:10:33 +0100 -Subject: [PATCH 175/329] x86/fpu: Disable preemption around local_bh_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 175/333] x86/fpu: Disable preemption around local_bh_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 7ecf159a2..fc2564609 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,11 +1,11 @@ -From 788d683b8d541f598c2897f18a334fb760a490a3 Mon Sep 17 00:00:00 2001 -Message-Id: <788d683b8d541f598c2897f18a334fb760a490a3.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 11001b5efd2e0b0f6c9dc1aec84927943f08ce46 Mon Sep 17 00:00:00 2001 +Message-Id: <11001b5efd2e0b0f6c9dc1aec84927943f08ce46.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 16:35:35 +0200 -Subject: [PATCH 176/329] fs/epoll: Do not disable preemption on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 176/333] fs/epoll: Do not disable preemption on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -17,7 +17,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/eventpoll.c b/fs/eventpoll.c -index 58f48ea0db23..a41120a34e6d 100644 +index f988ccd064a2..57026699b442 100644 --- a/fs/eventpoll.c +++ b/fs/eventpoll.c @@ -571,12 +571,12 @@ static int ep_poll_wakeup_proc(void *priv, void *cookie, int call_nests) 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 acf713029..e7fa1d810 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,12 +1,12 @@ -From b78529ca6a695c4b328e2cb24eb16b3d8dfe0b27 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d2661fc4061c4e4191c9eecedb94fa337085dd64 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 11:39:36 +0200 -Subject: [PATCH 177/329] mm/vmalloc: Another preempt disable region which +Subject: [PATCH 177/333] mm/vmalloc: Another preempt disable region which sucks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Avoid the preempt disable version of get_cpu_var(). The inner-lock should provide enough serialisation. 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 b9dd26142..a54bd765e 100644 --- a/debian/patches-rt/0178-block-mq-use-cpu_light.patch +++ b/debian/patches-rt/0178-block-mq-use-cpu_light.patch @@ -1,11 +1,11 @@ -From 5e14cf2663847cee57f9a268fd3bebd21c472c9c Mon Sep 17 00:00:00 2001 -Message-Id: <5e14cf2663847cee57f9a268fd3bebd21c472c9c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 7e39f210ab881892496da51592a4b5d21eb21008 Mon Sep 17 00:00:00 2001 +Message-Id: <7e39f210ab881892496da51592a4b5d21eb21008.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Apr 2014 10:37:23 +0200 -Subject: [PATCH 178/329] block: mq: use cpu_light() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 178/333] block: mq: use cpu_light() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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(). 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 b964d614d..547322311 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,11 +1,11 @@ -From 677ff20989e2beb0c44e527e4afdc6546184b114 Mon Sep 17 00:00:00 2001 -Message-Id: <677ff20989e2beb0c44e527e4afdc6546184b114.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b25f6cfcb6f662d6a621d33ffd0f09fa7fc1d918 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 179/329] block/mq: do not invoke preempt_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 179/333] block/mq: do not invoke preempt_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz preempt_disable() and get_cpu() don't play well together with the sleeping locks it tries to allocate later. 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 25b5f7f3b..70f8231ba 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,11 +1,11 @@ -From 721e60329048d1c2fda3de758e76658ea5d5dc37 Mon Sep 17 00:00:00 2001 -Message-Id: <721e60329048d1c2fda3de758e76658ea5d5dc37.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 61406ce72c3330865f9bc993eec1e916813356d1 Mon Sep 17 00:00:00 2001 +Message-Id: <61406ce72c3330865f9bc993eec1e916813356d1.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Jan 2015 15:10:08 +0100 -Subject: [PATCH 180/329] block/mq: don't complete requests via IPI -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 180/333] block/mq: don't complete requests via IPI +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The IPI runs in hardirq context and there are sleeping locks. This patch moves the completion into a workqueue. 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 16e4a1f67..f41c86446 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,11 +1,11 @@ -From b2aeaa1a249302dd3bc1766644f1f74ec75bbcfa Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From eaa87b73758b2a7b445e7d71fc3d7418179ea2b0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 6 Apr 2010 16:51:31 +0200 -Subject: [PATCH 181/329] md: raid5: Make raid5_percpu handling RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 181/333] md: raid5: Make raid5_percpu handling RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz __raid_run_ops() disables preemption with get_cpu() around the access to the raid5_percpu variables. That causes scheduling while atomic @@ -23,7 +23,7 @@ Tested-by: Udo van den Heuvel 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c -index 01021382131b..379ce2f57512 100644 +index d91154d65455..8d571170cb89 100644 --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -2069,8 +2069,9 @@ static void raid_run_ops(struct stripe_head *sh, unsigned long ops_request) @@ -47,7 +47,7 @@ index 01021382131b..379ce2f57512 100644 } static void free_stripe(struct kmem_cache *sc, struct stripe_head *sh) -@@ -6815,6 +6817,7 @@ static int raid456_cpu_up_prepare(unsigned int cpu, struct hlist_node *node) +@@ -6816,6 +6818,7 @@ static int raid456_cpu_up_prepare(unsigned int cpu, struct hlist_node *node) __func__, cpu); return -ENOMEM; } @@ -55,7 +55,7 @@ index 01021382131b..379ce2f57512 100644 return 0; } -@@ -6825,7 +6828,6 @@ static int raid5_alloc_percpu(struct r5conf *conf) +@@ -6826,7 +6829,6 @@ static int raid5_alloc_percpu(struct r5conf *conf) conf->percpu = alloc_percpu(struct raid5_percpu); if (!conf->percpu) return -ENOMEM; diff --git a/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch b/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch index 303bcf307..25cc60092 100644 --- a/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch +++ b/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch @@ -1,11 +1,11 @@ -From 79310ccfbc479a33513e1d64bbc830a5232a2a55 Mon Sep 17 00:00:00 2001 -Message-Id: <79310ccfbc479a33513e1d64bbc830a5232a2a55.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5655e13ac98d9ba142238b6781085a6a5bf6695d Mon Sep 17 00:00:00 2001 +Message-Id: <5655e13ac98d9ba142238b6781085a6a5bf6695d.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 20:51:03 +0100 -Subject: [PATCH 182/329] rt: Introduce cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 182/333] rt: Introduce cpu_chill() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Retry loops on RT might loop forever when the modifying side was preempted. Add cpu_chill() to replace cpu_relax(). cpu_chill() 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 6e8a521bd..43b1ae3cc 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,11 +1,11 @@ -From 709122e50c844dce09298e7854c1481f09354625 Mon Sep 17 00:00:00 2001 -Message-Id: <709122e50c844dce09298e7854c1481f09354625.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d55abcb924c6f372406f82c16fd16dc0308407f2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:59:15 +0100 -Subject: [PATCH 183/329] hrtimer: Don't lose state in cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 183/333] hrtimer: Don't lose state in cpu_chill() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 34e8b393a..550792656 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,12 +1,12 @@ -From 8dc2cf0ef8a9324af222b8dbe2a3ca02a50963a8 Mon Sep 17 00:00:00 2001 -Message-Id: <8dc2cf0ef8a9324af222b8dbe2a3ca02a50963a8.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 41e892b9d24ac5a90c195670cdf5063e2487a773 Mon Sep 17 00:00:00 2001 +Message-Id: <41e892b9d24ac5a90c195670cdf5063e2487a773.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 12:31:10 +0100 -Subject: [PATCH 184/329] hrtimer: cpu_chill(): save task state in +Subject: [PATCH 184/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 bcf172b44..062e40f7e 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,12 +1,12 @@ -From 0b6eefa7f5c4c981e7c755ef69e6f365954e4092 Mon Sep 17 00:00:00 2001 -Message-Id: <0b6eefa7f5c4c981e7c755ef69e6f365954e4092.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2c55b251962f6626b8c86f5220e7897827fd4a83 Mon Sep 17 00:00:00 2001 +Message-Id: <2c55b251962f6626b8c86f5220e7897827fd4a83.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 -Subject: [PATCH 185/329] block: blk-mq: move blk_queue_usage_counter_release() +Subject: [PATCH 185/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 e330f0f32..a47221419 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,11 +1,11 @@ -From 18910a5357a094c2633239a2f877b65d5ab09c88 Mon Sep 17 00:00:00 2001 -Message-Id: <18910a5357a094c2633239a2f877b65d5ab09c88.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From cafb748003e99b72641ba46b7139b33cc1dd264d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 20 Dec 2012 18:28:26 +0100 -Subject: [PATCH 186/329] block: Use cpu_chill() for retry loops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 186/333] block: Use cpu_chill() for retry loops +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 b719aae99..9d8fd8334 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,11 +1,11 @@ -From c082103a839ea32123df10e13e1e40a70034d4d8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From cfacd4668d3f6ea970b9b5c6a3e1004dff4f2b08 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:00:34 +0100 -Subject: [PATCH 187/329] fs: dcache: Use cpu_chill() in trylock loops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 187/333] fs: dcache: Use cpu_chill() in trylock loops +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 81ae4f79a..0833816ab 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,11 +1,11 @@ -From ea7fc68722cbdf96fc7ff457f7da14a3a1a8d15d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a8ba24a5bb6552c3a6cc316f3b09432649e8ac17 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:10:04 +0100 -Subject: [PATCH 188/329] net: Use cpu_chill() instead of cpu_relax() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 188/333] net: Use cpu_chill() instead of cpu_relax() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -18,7 +18,7 @@ Signed-off-by: Thomas Gleixner 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c -index 0e029aefa707..74e78df6cdf8 100644 +index b3caf1eac6af..7d58aa1a3fa2 100644 --- a/net/packet/af_packet.c +++ b/net/packet/af_packet.c @@ -63,6 +63,7 @@ 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 aa8bb4101..437f1ae49 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,11 +1,11 @@ -From 9b95ce168a72f1f027fa44e3c906746c97713422 Mon Sep 17 00:00:00 2001 -Message-Id: <9b95ce168a72f1f027fa44e3c906746c97713422.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 45ddc97d426c9426ba58fa1fa953d5fde6ccd8c1 Mon Sep 17 00:00:00 2001 +Message-Id: <45ddc97d426c9426ba58fa1fa953d5fde6ccd8c1.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 14:35:49 +0200 -Subject: [PATCH 189/329] fs/dcache: use swait_queue instead of waitqueue -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 189/333] fs/dcache: use swait_queue instead of waitqueue +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. diff --git a/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch b/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch index f0b92e1e3..975aa9ba1 100644 --- a/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch +++ b/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch @@ -1,11 +1,11 @@ -From b81673e7d867b1cea414f6eac4999b4800a35954 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From db4dc54d7dfbbc44ad802f20aa9494ba4c373d95 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 24 Jul 2013 15:26:54 +0200 -Subject: [PATCH 190/329] workqueue: Use normal rcu -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 190/333] workqueue: Use normal rcu +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 5de3010e1..1235bc0ed 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,12 +1,12 @@ -From a37af2de095fe55ea6ed55df2a3887795f35f46e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a3e37a2d98132a499e9a17f71cb2b3ef0a1f9c2e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:42:26 +0200 -Subject: [PATCH 191/329] workqueue: Use local irq lock instead of irq disable +Subject: [PATCH 191/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 02645571b..b5b2e361b 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,11 +1,11 @@ -From c8558170db4f3c1bba19fcfe00524e64c5591697 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f385da894412142977507afb7b5e9a042549f9dd Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 1 Jul 2013 11:02:42 +0200 -Subject: [PATCH 192/329] workqueue: Prevent workqueue versus ata-piix livelock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 192/333] workqueue: Prevent workqueue versus ata-piix livelock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 49d883f70..1e60781cf 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,11 +1,11 @@ -From 97664a8a1bc64c04079d93ee8aaa75191067f57a Mon Sep 17 00:00:00 2001 -Message-Id: <97664a8a1bc64c04079d93ee8aaa75191067f57a.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9fd6eba617c2bf6f06c4fa4f860e2cefaf4bb6ea Mon Sep 17 00:00:00 2001 +Message-Id: <9fd6eba617c2bf6f06c4fa4f860e2cefaf4bb6ea.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Jun 2011 19:47:03 +0200 -Subject: [PATCH 193/329] sched: Distangle worker accounting from rqlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 193/333] sched: Distangle worker accounting from rqlock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 diff --git a/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch b/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch index 6196c1ce1..aa21f8b5f 100644 --- a/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch +++ b/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch @@ -1,11 +1,11 @@ -From e7072860b9c7a16ca8c94ee50df14e16360fbda0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 95652cba61d4816ec09e6756a7c23a6f9f99b7bb Mon Sep 17 00:00:00 2001 +Message-Id: <95652cba61d4816ec09e6756a7c23a6f9f99b7bb.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:41:35 +0200 -Subject: [PATCH 194/329] debugobjects: Make RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 194/333] debugobjects: Make RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Avoid filling the pool / allocating memory with irqs off(). diff --git a/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch b/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch index f53719122..e9ed3e998 100644 --- a/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch +++ b/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch @@ -1,11 +1,11 @@ -From f3e78f2a54c0638b47530adea622dd556b3a5f99 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a8f6ea9b401073080888155b72c2fec72cdfdf21 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Feb 2012 12:03:30 +0100 -Subject: [PATCH 195/329] seqlock: Prevent rt starvation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 195/333] seqlock: Prevent rt starvation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz If a low prio writer gets preempted while holding the seqlock write locked, a high prio reader spins forever on RT. 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 79078e979..13ce7ac99 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,12 +1,12 @@ -From 60ebd21c82b8a2b837e17e68e1efb49f47b2eac8 Mon Sep 17 00:00:00 2001 -Message-Id: <60ebd21c82b8a2b837e17e68e1efb49f47b2eac8.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 706fceb1ab566895dce3aaf6422e6f928a46a755 Mon Sep 17 00:00:00 2001 +Message-Id: <706fceb1ab566895dce3aaf6422e6f928a46a755.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 18 Feb 2015 16:05:28 +0100 -Subject: [PATCH 196/329] sunrpc: Make svc_xprt_do_enqueue() use +Subject: [PATCH 196/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 fc2c42e4b..e330b6735 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,11 +1,11 @@ -From 7fe369968dc32769c83f1b4ac3951b64dd72f608 Mon Sep 17 00:00:00 2001 -Message-Id: <7fe369968dc32769c83f1b4ac3951b64dd72f608.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0b7b0ae1cb92088c9c727f09ac7a95c2667e3d3e Mon Sep 17 00:00:00 2001 +Message-Id: <0b7b0ae1cb92088c9c727f09ac7a95c2667e3d3e.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 15:38:34 +0200 -Subject: [PATCH 197/329] net: Use skbufhead with raw lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 197/333] net: Use skbufhead with raw lock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -15,8 +15,8 @@ Signed-off-by: Thomas Gleixner --- include/linux/netdevice.h | 1 + include/linux/skbuff.h | 7 +++++++ - net/core/dev.c | 33 +++++++++++++++++++++++++-------- - 3 files changed, 33 insertions(+), 8 deletions(-) + net/core/dev.c | 26 ++++++++++++++++++++------ + 3 files changed, 28 insertions(+), 6 deletions(-) diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h index 4e14926433ed..8fff010fff6e 100644 @@ -56,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 2bfd79026bb3..598398e3c841 100644 +index e89ae804e68a..44210413bf63 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -219,14 +219,14 @@ static inline struct hlist_head *dev_index_hash(struct net *net, int ifindex) @@ -76,32 +76,7 @@ index 2bfd79026bb3..598398e3c841 100644 #endif } -@@ -5253,7 +5253,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); -- dev_kfree_skb_irq(skb); -+ __skb_queue_tail(&sd->tofree_queue, skb); - input_queue_head_incr(sd); - } - } -@@ -5263,11 +5263,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); -- kfree_skb(skb); -+ __skb_queue_tail(&sd->tofree_queue, skb); - input_queue_head_incr(sd); - } - } -+ if (!skb_queue_empty(&sd->tofree_queue)) -+ raise_softirq_irqoff(NET_RX_SOFTIRQ); - local_bh_enable(); -+ - } - - static void flush_all_backlogs(void) -@@ -5846,7 +5849,9 @@ static int process_backlog(struct napi_struct *napi, int quota) +@@ -5846,7 +5846,9 @@ static int process_backlog(struct napi_struct *napi, int quota) while (again) { struct sk_buff *skb; @@ -111,7 +86,7 @@ index 2bfd79026bb3..598398e3c841 100644 rcu_read_lock(); __netif_receive_skb(skb); rcu_read_unlock(); -@@ -5854,9 +5859,9 @@ static int process_backlog(struct napi_struct *napi, int quota) +@@ -5854,9 +5856,9 @@ static int process_backlog(struct napi_struct *napi, int quota) if (++work >= quota) return work; @@ -122,7 +97,7 @@ index 2bfd79026bb3..598398e3c841 100644 rps_lock(sd); if (skb_queue_empty(&sd->input_pkt_queue)) { /* -@@ -6321,13 +6326,21 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) +@@ -6321,13 +6323,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; @@ -144,7 +119,7 @@ index 2bfd79026bb3..598398e3c841 100644 for (;;) { struct napi_struct *n; -@@ -9520,10 +9533,13 @@ static int dev_cpu_dead(unsigned int oldcpu) +@@ -9520,10 +9530,13 @@ static int dev_cpu_dead(unsigned int oldcpu) netif_rx_ni(skb); input_queue_head_incr(oldsd); } @@ -159,7 +134,7 @@ index 2bfd79026bb3..598398e3c841 100644 return 0; } -@@ -9834,8 +9850,9 @@ static int __init net_dev_init(void) +@@ -9834,8 +9847,9 @@ static int __init net_dev_init(void) INIT_WORK(flush, flush_backlog); 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 130ab6e38..fce8ad1cb 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,11 +1,11 @@ -From c0bfbcad9424479746dc43df9e6ebc33a184a039 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0690f41eaf2e7b1a58969a5646ec99fed2c9dd73 Mon Sep 17 00:00:00 2001 +Message-Id: <0690f41eaf2e7b1a58969a5646ec99fed2c9dd73.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Jan 2016 15:55:02 +0100 -Subject: [PATCH 198/329] 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.135-rt60.tar.xz +Subject: [PATCH 198/333] 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.142-rt63.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 @@ -193,7 +193,7 @@ index 4a4f03a8d8d4..37334ec1ab3e 100644 int pagefault_disabled; #ifdef CONFIG_MMU diff --git a/net/core/dev.c b/net/core/dev.c -index 598398e3c841..bb93ab3f0b1f 100644 +index 44210413bf63..e9594b1e0d44 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -3825,7 +3825,11 @@ static int __dev_queue_xmit(struct sk_buff *skb, struct net_device *sb_dev) @@ -208,7 +208,7 @@ index 598398e3c841..bb93ab3f0b1f 100644 if (dev_xmit_recursion()) goto recursion_alert; -@@ -8572,7 +8576,7 @@ static void netdev_init_one_queue(struct net_device *dev, +@@ -8569,7 +8573,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); 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 9aeb54554..d022853c7 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,12 +1,12 @@ -From 302b4d04008563db6601953efc2267fb2b5f2d63 Mon Sep 17 00:00:00 2001 -Message-Id: <302b4d04008563db6601953efc2267fb2b5f2d63.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a5dd87cb4638b481a2cdbbfb98b2aea089864126 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 15:39:05 +0100 -Subject: [PATCH 199/329] net: provide a way to delegate processing a softirq +Subject: [PATCH 199/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -75,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 bb93ab3f0b1f..bd2d4195d238 100644 +index e9594b1e0d44..4926ba054f62 100644 --- a/net/core/dev.c +++ b/net/core/dev.c -@@ -6374,7 +6374,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)) 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 e784b233c..a5282119b 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,12 +1,12 @@ -From bf1b7f42bc9f739693ff39eb8fc4cc2acb239c0b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0679c2e127afaadc8a819eef7f495efaa8052b2b Mon Sep 17 00:00:00 2001 +Message-Id: <0679c2e127afaadc8a819eef7f495efaa8052b2b.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 30 Mar 2016 13:36:29 +0200 -Subject: [PATCH 200/329] net: dev: always take qdisc's busylock in +Subject: [PATCH 200/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -25,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 bd2d4195d238..fcaef21a42c3 100644 +index 4926ba054f62..4dff7edb5200 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -3464,7 +3464,11 @@ static inline int __dev_xmit_skb(struct sk_buff *skb, struct Qdisc *q, 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 3b6bced7f..9c1f06257 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,11 +1,11 @@ -From 307d91a60bbff9f248431ca7631279e7c8b10780 Mon Sep 17 00:00:00 2001 -Message-Id: <307d91a60bbff9f248431ca7631279e7c8b10780.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 97ee56713bd357e7cfc9560148236a0fef713377 Mon Sep 17 00:00:00 2001 +Message-Id: <97ee56713bd357e7cfc9560148236a0fef713377.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 17:36:35 +0200 -Subject: [PATCH 201/329] net/Qdisc: use a seqlock instead seqcount -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 201/333] net/Qdisc: use a seqlock instead seqcount +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 4ab70384f..f32d0f2d5 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,15 +1,15 @@ -From 75ab59215ef16d8816003c3ae3f11c25bcee980f Mon Sep 17 00:00:00 2001 -Message-Id: <75ab59215ef16d8816003c3ae3f11c25bcee980f.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e916be072e7cbd7bcce49fc1f0f21f1e780530a1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:21:56 +0200 -Subject: [PATCH 202/329] net: add back the missing serialization in +Subject: [PATCH 202/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 7ecd41d6c..0d25900cb 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,11 +1,11 @@ -From 4187c597c0695b2c1b8d8d8d41c36fd92a5ae958 Mon Sep 17 00:00:00 2001 -Message-Id: <4187c597c0695b2c1b8d8d8d41c36fd92a5ae958.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From c9eb57127331f638a03b5426fa129c2078c9304e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:54:09 +0200 -Subject: [PATCH 203/329] net: add a lock around icmp_sk() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 203/333] net: add a lock around icmp_sk() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 fb1f0f714..ff75c0dcd 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,12 +1,12 @@ -From aa23415173800a6c4d7352d5c14fd59562015bd6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 16a49e1fd2b8fcd07b0f5b142ba60dabdf80732d Mon Sep 17 00:00:00 2001 +Message-Id: <16a49e1fd2b8fcd07b0f5b142ba60dabdf80732d.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 6 Dec 2016 17:50:30 -0500 -Subject: [PATCH 204/329] net: Have __napi_schedule_irqoff() disable interrupts +Subject: [PATCH 204/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz A customer hit a crash where the napi sd->poll_list became corrupted. The customer had the bnx2x driver, which does a @@ -56,10 +56,10 @@ index 7bf58533f955..0e34e8051ac2 100644 static inline bool napi_disable_pending(struct napi_struct *n) { diff --git a/net/core/dev.c b/net/core/dev.c -index fcaef21a42c3..1e58809817b2 100644 +index 4dff7edb5200..a26ed30641b0 100644 --- a/net/core/dev.c +++ b/net/core/dev.c -@@ -5944,6 +5944,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); @@ -67,7 +67,7 @@ index fcaef21a42c3..1e58809817b2 100644 /** * __napi_schedule_irqoff - schedule for receive * @n: entry to schedule -@@ -5955,6 +5956,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); 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 ad8ee3605..fa8143a3d 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,11 +1,11 @@ -From c599564b3ab6da0f861bcbae9b50ea2eb810ff0f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From fe4be261731592b78156956954fdd7cc030e6234 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 23 Jun 2015 15:32:51 +0200 -Subject: [PATCH 205/329] irqwork: push most work into softirq context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 205/333] irqwork: push most work into softirq context +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. @@ -226,7 +226,7 @@ index f162a4f54b05..278fe66bfb70 100644 rdp->rcu_iw_gp_seq = rnp->gp_seq; irq_work_queue_on(&rdp->rcu_iw, rdp->cpu); diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c -index 74b694392f2f..fb4d11bab6b7 100644 +index f58efa5cc647..963961c26d17 100644 --- a/kernel/sched/topology.c +++ b/kernel/sched/topology.c @@ -279,6 +279,7 @@ static int init_rootdomain(struct root_domain *rd) @@ -250,10 +250,10 @@ index 2b0ddd50e879..4d31ec98e968 100644 /* diff --git a/kernel/time/timer.c b/kernel/time/timer.c -index 845f687d2d1c..a4279d24b438 100644 +index 753b75751f0a..bdbfd52b1cfd 100644 --- a/kernel/time/timer.c +++ b/kernel/time/timer.c -@@ -1746,6 +1746,8 @@ static __latent_entropy void run_timer_softirq(struct softirq_action *h) +@@ -1754,6 +1754,8 @@ static __latent_entropy void run_timer_softirq(struct softirq_action *h) { struct timer_base *base = this_cpu_ptr(&timer_bases[BASE_STD]); diff --git a/debian/patches-rt/0206-printk-Make-rt-aware.patch b/debian/patches-rt/0206-printk-Make-rt-aware.patch index ae432fc1f..b1719b972 100644 --- a/debian/patches-rt/0206-printk-Make-rt-aware.patch +++ b/debian/patches-rt/0206-printk-Make-rt-aware.patch @@ -1,11 +1,11 @@ -From c294bdb762f1c945845389df3e0f803a9a3f2c52 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a487ef0ffa767dbacd7caacf92220200ee54ba31 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Sep 2012 14:50:37 +0200 -Subject: [PATCH 206/329] printk: Make rt aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 206/333] printk: Make rt aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Drop the lock before calling the console driver and do not disable interrupts while printing to a serial console. 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 003db606f..2fb12e79a 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,11 +1,11 @@ -From 0b98bff7eda15d4a236d8587b6baab352fd5facd Mon Sep 17 00:00:00 2001 -Message-Id: <0b98bff7eda15d4a236d8587b6baab352fd5facd.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b77b453462f42415c6a6ae5361e2015715497d61 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 19 May 2016 17:45:27 +0200 -Subject: [PATCH 207/329] 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.135-rt60.tar.xz +Subject: [PATCH 207/333] 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.142-rt63.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 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 bab07ebaf..a7ba41769 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,11 +1,11 @@ -From 897315108800613002880d07fd0a2eb085146696 Mon Sep 17 00:00:00 2001 -Message-Id: <897315108800613002880d07fd0a2eb085146696.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a39b767fed2c7ee3b6a58b23e3996e8a189377f1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Mar 2013 19:01:05 +0100 -Subject: [PATCH 208/329] printk: Drop the logbuf_lock more often -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 208/333] printk: Drop the logbuf_lock more often +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. 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 70b251b16..43b46b2f0 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,15 +1,15 @@ -From 5f72f11e2a069acf5de031f6179b02ac5a016817 Mon Sep 17 00:00:00 2001 -Message-Id: <5f72f11e2a069acf5de031f6179b02ac5a016817.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 355d48b702d20048a540e9a0a5de685e59c6a793 Mon Sep 17 00:00:00 2001 +Message-Id: <355d48b702d20048a540e9a0a5de685e59c6a793.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Yadi.hu" Date: Wed, 10 Dec 2014 10:32:09 +0800 -Subject: [PATCH 209/329] ARM: enable irq in translation/section permission +Subject: [PATCH 209/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Probably happens on all ARM, with CONFIG_PREEMPT_RT_FULL 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 c8a9182b0..f14043cf6 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,11 +1,11 @@ -From 16775ca6e980eaa415c3e9b3df3027832ed0d91b Mon Sep 17 00:00:00 2001 -Message-Id: <16775ca6e980eaa415c3e9b3df3027832ed0d91b.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d6db17021019e048775636f1557462fbb271ab75 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:00 -0600 -Subject: [PATCH 210/329] genirq: update irq_set_irqchip_state documentation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 210/333] genirq: update irq_set_irqchip_state documentation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 @@ -18,10 +18,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c -index 44ee91ca0088..09147749657f 100644 +index bb2825ed4bf0..a68fec893dbf 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c -@@ -2316,7 +2316,7 @@ EXPORT_SYMBOL_GPL(irq_get_irqchip_state); +@@ -2320,7 +2320,7 @@ EXPORT_SYMBOL_GPL(irq_get_irqchip_state); * This call sets the internal irqchip state of an interrupt, * depending on the value of @which. * 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 183ea733d..27b8a1222 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,12 +1,12 @@ -From 951d0da6fc249f03da0113a4b571d04be867ea80 Mon Sep 17 00:00:00 2001 -Message-Id: <951d0da6fc249f03da0113a4b571d04be867ea80.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 577f4f471e11185a77f3e65586d70e1f37bada89 Mon Sep 17 00:00:00 2001 +Message-Id: <577f4f471e11185a77f3e65586d70e1f37bada89.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:01 -0600 -Subject: [PATCH 211/329] KVM: arm/arm64: downgrade preempt_disable()d region +Subject: [PATCH 211/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 77ade08d0..a92d0569e 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,12 +1,12 @@ -From 39d41edf73a8f9e1e705f64bc12e033d2d03f3d7 Mon Sep 17 00:00:00 2001 -Message-Id: <39d41edf73a8f9e1e705f64bc12e033d2d03f3d7.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From be02aec36e38152c42cd01344a5d02cce54853df Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jul 2018 14:02:38 +0200 -Subject: [PATCH 212/329] arm64: fpsimd: use preemp_disable in addition to +Subject: [PATCH 212/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 3927b0c57..bd97cfafc 100644 --- a/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch +++ b/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch @@ -1,11 +1,11 @@ -From 545e447ad9fe203b26f09142f9c30d4691b3e503 Mon Sep 17 00:00:00 2001 -Message-Id: <545e447ad9fe203b26f09142f9c30d4691b3e503.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5b301c2aea7296ed7fcf5d292e163dc53294e194 Mon Sep 17 00:00:00 2001 +Message-Id: <5b301c2aea7296ed7fcf5d292e163dc53294e194.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Jason Wessel Date: Thu, 28 Jul 2011 12:42:23 -0500 -Subject: [PATCH 213/329] kgdb/serial: Short term workaround -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 213/333] kgdb/serial: Short term workaround +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz On 07/27/2011 04:37 PM, Thomas Gleixner wrote: > - KGDB (not yet disabled) is reportedly unusable on -rt right now due 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 f8be9a117..9c111d224 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,11 +1,11 @@ -From 2eecd7a65459b0ccdc26142cf47005022c38f903 Mon Sep 17 00:00:00 2001 -Message-Id: <2eecd7a65459b0ccdc26142cf47005022c38f903.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5b7aeaffe1d40614c1ff8df62748e04b186d18e0 Mon Sep 17 00:00:00 2001 +Message-Id: <5b7aeaffe1d40614c1ff8df62748e04b186d18e0.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Clark Williams Date: Sat, 30 Jul 2011 21:55:53 -0500 -Subject: [PATCH 214/329] sysfs: Add /sys/kernel/realtime entry -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 214/333] sysfs: Add /sys/kernel/realtime entry +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Add a /sys/kernel entry to indicate that the kernel is a realtime kernel. 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 aa7bf6cd2..1d85c704b 100644 --- a/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch +++ b/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch @@ -1,11 +1,11 @@ -From 00a85fc7a892ec7212dd0059a4f4fcab888a7ab6 Mon Sep 17 00:00:00 2001 -Message-Id: <00a85fc7a892ec7212dd0059a4f4fcab888a7ab6.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 29109e6f1f9c08c9032f5f9ea3b61ef0b922b61f Mon Sep 17 00:00:00 2001 +Message-Id: <29109e6f1f9c08c9032f5f9ea3b61ef0b922b61f.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Peter Zijlstra Date: Thu, 28 Jul 2011 10:43:51 +0200 -Subject: [PATCH 215/329] mm, rt: kmap_atomic scheduling -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 215/333] mm, rt: kmap_atomic scheduling +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 7d3d607ae..ca0b5f5d6 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,11 +1,11 @@ -From 4234f529d91f856a90ed13d0c337fa18b8ae5723 Mon Sep 17 00:00:00 2001 -Message-Id: <4234f529d91f856a90ed13d0c337fa18b8ae5723.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b3c4a7f13224b7ed3888c719c1676a0ea198e9f4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 17:09:55 +0100 -Subject: [PATCH 216/329] x86/highmem: Add a "already used pte" check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 216/333] x86/highmem: Add a "already used pte" check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz This is a copy from kmap_atomic_prot(). 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 a728fb84b..2472e307c 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,11 +1,11 @@ -From 9b59ba6c7b0a844b03878eda2b6cf8cd46655af5 Mon Sep 17 00:00:00 2001 -Message-Id: <9b59ba6c7b0a844b03878eda2b6cf8cd46655af5.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a4e6e431747f1916bbe828a973fc7d6d676d1a78 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 21:37:27 +0100 -Subject: [PATCH 217/329] arm/highmem: Flush tlb on unmap -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 217/333] arm/highmem: Flush tlb on unmap +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 ba5f25961..d660e423e 100644 --- a/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch +++ b/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch @@ -1,11 +1,11 @@ -From 0af49b5bd27c7cd6162d3aae8b725e3326cfa61c Mon Sep 17 00:00:00 2001 -Message-Id: <0af49b5bd27c7cd6162d3aae8b725e3326cfa61c.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e55c589f53ce73a6721f5570cbf787cd739ad101 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 13 Feb 2013 11:03:11 +0100 -Subject: [PATCH 218/329] arm: Enable highmem for rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 218/333] arm: Enable highmem for rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz fixup highmem for ARM. 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 814770d8c..1f76290db 100644 --- a/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch +++ b/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch @@ -1,11 +1,11 @@ -From fb2ca2f8dd0beedbe0243207adb1d39453e67ff2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d2d892192c552af1d09ea34d6e613b36a490370a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 12 Nov 2011 14:00:48 +0100 -Subject: [PATCH 219/329] scsi/fcoe: Make RT aware. -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 219/333] scsi/fcoe: Make RT aware. +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Do not disable preemption while taking sleeping locks. All user look safe for migrate_diable() only. 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 c1c4770c3..040dd7380 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,11 +1,11 @@ -From b78cffc4084058a9d449692c7464f86d3ff85e8d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0f8453ee78231bbca074944df49bc8b34baf3c78 Mon Sep 17 00:00:00 2001 +Message-Id: <0f8453ee78231bbca074944df49bc8b34baf3c78.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 14 Nov 2011 18:19:27 +0100 -Subject: [PATCH 220/329] x86: crypto: Reduce preempt disabled regions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 220/333] x86: crypto: Reduce preempt disabled regions +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Restrict the preempt disabled regions to the actual floating point operations and enable preemption for the administrative actions. 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 b0e30b4d2..4c4ee2bde 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,11 +1,11 @@ -From 96985e31d9bc25b62a3b93b24529d87a5c776eab Mon Sep 17 00:00:00 2001 -Message-Id: <96985e31d9bc25b62a3b93b24529d87a5c776eab.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e20966be8f60cd556430b1eaa3a8cfb9455922c3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2014 17:24:04 +0100 -Subject: [PATCH 221/329] crypto: Reduce preempt disabled regions, more algos -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 221/333] crypto: Reduce preempt disabled regions, more algos +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Don Estabrook reported | kernel: WARNING: CPU: 2 PID: 858 at kernel/sched/core.c:2428 migrate_disable+0xed/0x100() 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 ecd1bb413..b62a24865 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,14 +1,14 @@ -From 024d112320340c333d6cab3cf22ffd0be7c05c9d Mon Sep 17 00:00:00 2001 -Message-Id: <024d112320340c333d6cab3cf22ffd0be7c05c9d.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d191b91aa1860dae76957c01906d1c1f92191f08 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 30 Nov 2017 13:40:10 +0100 -Subject: [PATCH 222/329] crypto: limit more FPU-enabled sections +Subject: [PATCH 222/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 15dd9f8f4..da0b28bfa 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,12 +1,12 @@ -From 299f82e40eca11d9634aa6ceb0f82fc77beab2db Mon Sep 17 00:00:00 2001 -Message-Id: <299f82e40eca11d9634aa6ceb0f82fc77beab2db.1596234183.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From cc3c028dd09050e4de50571e49d6f86116a181c3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 11 Jul 2018 17:14:47 +0200 -Subject: [PATCH 223/329] crypto: scompress - serialize RT percpu scratch +Subject: [PATCH 223/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 5741b69ce..2f5077e78 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,12 +1,12 @@ -From a9e4f25711136eee5cc164319c127617c034fe3c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 4c23a25de4b275143199cc8c1b17f356a37cc95d Mon Sep 17 00:00:00 2001 +Message-Id: <4c23a25de4b275143199cc8c1b17f356a37cc95d.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 18:52:00 +0200 -Subject: [PATCH 224/329] crypto: cryptd - add a lock instead +Subject: [PATCH 224/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz cryptd has a per-CPU lock which protected with local_bh_disable() and preempt_disable(). 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 fab569347..1108ec54c 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,12 +1,12 @@ -From 0dde5f058582ef2cd8c77c6802ad36e5cbc3f660 Mon Sep 17 00:00:00 2001 -Message-Id: <0dde5f058582ef2cd8c77c6802ad36e5cbc3f660.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 7ee811cf4553273a0516143009ef16bec5ebef68 Mon Sep 17 00:00:00 2001 +Message-Id: <7ee811cf4553273a0516143009ef16bec5ebef68.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 225/329] panic: skip get_random_bytes for RT_FULL in +Subject: [PATCH 225/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Disable on -RT. If this is invoked from irq-context we will have problems to acquire the sleeping lock. 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 87834b345..dab0f25ea 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,11 +1,11 @@ -From f44b5e07c4f50ed3bfd80541ebf701a40dc4bf13 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a3bd388c543d94e77067436e30ef9404175f2a4d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 16 Dec 2010 14:25:18 +0100 -Subject: [PATCH 226/329] x86: stackprotector: Avoid random pool on rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 226/333] x86: stackprotector: Avoid random pool on rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 9d5ab233e..2aaec0caa 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,11 +1,11 @@ -From d783906c07ac0e58cfedb0067b6e9f7b8274157c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f31b73a0acb2035df87b1795db1d1f1c92c69058 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 21 Aug 2012 20:38:50 +0200 -Subject: [PATCH 227/329] random: Make it work on rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 227/333] random: Make it work on rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Delegate the random insertion to the forced threaded interrupt handler. Store the return IP of the hard interrupt handler in the irq @@ -24,7 +24,7 @@ Signed-off-by: Thomas Gleixner 7 files changed, 26 insertions(+), 10 deletions(-) diff --git a/drivers/char/random.c b/drivers/char/random.c -index d5f970d039bb..838950ff569f 100644 +index 6a5d4dfafc47..d10779c769b5 100644 --- a/drivers/char/random.c +++ b/drivers/char/random.c @@ -1232,28 +1232,27 @@ static __u32 get_reg(struct fast_pool *f, struct pt_regs *regs) @@ -80,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 fb22b72fd535..cfbcc2dce208 100644 +index 0699c6018889..cb106e256fc6 100644 --- a/drivers/hv/vmbus_drv.c +++ b/drivers/hv/vmbus_drv.c -@@ -1070,6 +1070,8 @@ static void vmbus_isr(void) +@@ -1074,6 +1074,8 @@ static void vmbus_isr(void) void *page_addr = hv_cpu->synic_event_page; struct hv_message *msg; union hv_synic_event_flags *event; @@ -92,7 +92,7 @@ index fb22b72fd535..cfbcc2dce208 100644 bool handled = false; if (unlikely(page_addr == NULL)) -@@ -1113,7 +1115,7 @@ static void vmbus_isr(void) +@@ -1117,7 +1119,7 @@ static void vmbus_isr(void) tasklet_schedule(&hv_cpu->msg_dpc); } @@ -114,7 +114,7 @@ index 875c41b23f20..ff5eb8d1ede4 100644 struct cpumask *percpu_enabled; const struct cpumask *percpu_affinity; diff --git a/include/linux/random.h b/include/linux/random.h -index 445a0ea4ff49..a7b7d9f97580 100644 +index 37209b3b22ae..c4342f7658cd 100644 --- a/include/linux/random.h +++ b/include/linux/random.h @@ -32,7 +32,7 @@ static inline void add_latent_entropy(void) {} @@ -149,10 +149,10 @@ index 38554bc35375..06a80bbf78af 100644 if (!noirqdebug) note_interrupt(desc, retval); diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c -index 09147749657f..81434d90786f 100644 +index a68fec893dbf..4051708339a3 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c -@@ -1096,6 +1096,12 @@ static int irq_thread(void *data) +@@ -1100,6 +1100,12 @@ static int irq_thread(void *data) if (action_ret == IRQ_WAKE_THREAD) irq_wake_secondary(desc, action); 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 453499a19..826732519 100644 --- a/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch +++ b/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch @@ -1,11 +1,11 @@ -From 7f59f74c91f59c1fd2eb43ca335a841592fb2002 Mon Sep 17 00:00:00 2001 -Message-Id: <7f59f74c91f59c1fd2eb43ca335a841592fb2002.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f69ca6511d2668ca91728c537bd9658a0bbc2908 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Jul 2017 17:31:20 +0200 -Subject: [PATCH 228/329] cpu/hotplug: Implement CPU pinning -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 228/333] cpu/hotplug: Implement CPU pinning +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Signed-off-by: Thomas Gleixner --- 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 ea367111c..76e4d5042 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,12 +1,12 @@ -From bb2fa11047eb9b638f318dbca6d46c8abdae5931 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 4e1d41caa53b0a39c5cbaca61ee33048e54454ae Mon Sep 17 00:00:00 2001 +Message-Id: <4e1d41caa53b0a39c5cbaca61ee33048e54454ae.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 19 Aug 2018 08:28:35 +0200 -Subject: [PATCH 229/329] sched: Allow pinned user tasks to be awakened to the +Subject: [PATCH 229/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Since commit 7af443ee16976 ("sched/core: Require cpu_active() in select_task_rq(), for user tasks") select_fallback_rq() will BUG() if 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 be0e1e75f..4fa055f6e 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,11 +1,11 @@ -From cc724c29d2cb4ced6712c1d3d72e6dc0a142c765 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9ffac8e24e3ab1a567b172c452cd4b23cf10c759 Mon Sep 17 00:00:00 2001 +Message-Id: <9ffac8e24e3ab1a567b172c452cd4b23cf10c759.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 18:31:00 +0200 -Subject: [PATCH 230/329] 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.135-rt60.tar.xz +Subject: [PATCH 230/333] 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.142-rt63.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 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 ec316b34f..3ebabadcd 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,11 +1,11 @@ -From d2d996436a3b96c91964a8e728bfe926824e63a8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From c32027acb5862d1974fbe6e72f2ab9c390e2166f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Priyanka Jain Date: Thu, 17 May 2012 09:35:11 +0530 -Subject: [PATCH 231/329] net: Remove preemption disabling in netif_rx() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 231/333] net: Remove preemption disabling in netif_rx() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz 1)enqueue_to_backlog() (called from netif_rx) should be bind to a particluar CPU. This can be achieved by @@ -39,7 +39,7 @@ 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 1e58809817b2..2e69aded30e7 100644 +index a26ed30641b0..aa5e5abb7b1d 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -4483,7 +4483,7 @@ static int netif_rx_internal(struct sk_buff *skb) 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 537ee5599..215f893ef 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,11 +1,11 @@ -From 2368c6033f87efcb5b6a0ce41578038b648ec2c0 Mon Sep 17 00:00:00 2001 -Message-Id: <2368c6033f87efcb5b6a0ce41578038b648ec2c0.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b3a6bbc58177cc4497a684f609f0d96c95e9ac68 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Sep 2012 16:21:08 +0200 -Subject: [PATCH 232/329] net: Another local_irq_disable/kmalloc headache -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 232/333] net: Another local_irq_disable/kmalloc headache +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Replace it by a local lock. Though that's pretty inefficient :( 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 316498132..45cf61481 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,12 +1,12 @@ -From d68c697225a753c6cbfbd8ac77a77b6d0f47d688 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9b365f78bd1c31c6c02bd77c4470328985ce06e9 Mon Sep 17 00:00:00 2001 +Message-Id: <9b365f78bd1c31c6c02bd77c4470328985ce06e9.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 15 Jan 2016 16:33:34 +0100 -Subject: [PATCH 233/329] net/core: protect users of napi_alloc_cache against +Subject: [PATCH 233/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 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 d9cf081ff..afd307ec3 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,12 +1,12 @@ -From 08ccb72c4947bcf731754a2a2bab816a4bbbe39c Mon Sep 17 00:00:00 2001 -Message-Id: <08ccb72c4947bcf731754a2a2bab816a4bbbe39c.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 32d005e0390f7eddfc191374488361d75ab61866 Mon Sep 17 00:00:00 2001 +Message-Id: <32d005e0390f7eddfc191374488361d75ab61866.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 11:18:08 +0100 -Subject: [PATCH 234/329] net: netfilter: Serialize xt_write_recseq sections on +Subject: [PATCH 234/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The netfilter code relies only on the implicit semantics of local_bh_disable() for serializing wt_write_recseq sections. RT breaks diff --git a/debian/patches-rt/0235-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch b/debian/patches-rt/0235-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch index a814b95d0..215e6873e 100644 --- a/debian/patches-rt/0235-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch +++ b/debian/patches-rt/0235-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch @@ -1,12 +1,12 @@ -From 450945cde1764a9faad30035c50d3b004038a593 Mon Sep 17 00:00:00 2001 -Message-Id: <450945cde1764a9faad30035c50d3b004038a593.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d14aedcec6c2f9064f56bc486cb44a6dfaf7a411 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Yong Zhang Date: Mon, 16 Apr 2012 15:01:56 +0800 -Subject: [PATCH 235/329] lockdep: selftest: Only do hardirq context test for +Subject: [PATCH 235/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz On -rt there is no softirq context any more and rwlock is sleepable, disable softirq context test and rwlock+irq test. diff --git a/debian/patches-rt/0236-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch b/debian/patches-rt/0236-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch index 1ad20bfa3..27aa0116f 100644 --- a/debian/patches-rt/0236-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch +++ b/debian/patches-rt/0236-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch @@ -1,12 +1,12 @@ -From de78b9d4720eb62b7b56177ed994451d340b8480 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3967f2bcf324167b489b43b455a11add3611cf09 Mon Sep 17 00:00:00 2001 +Message-Id: <3967f2bcf324167b489b43b455a11add3611cf09.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Josh Cartwright Date: Wed, 28 Jan 2015 13:08:45 -0600 -Subject: [PATCH 236/329] lockdep: selftest: fix warnings due to missing +Subject: [PATCH 236/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz "lockdep: Selftest: Only do hardirq context test for raw spinlock" disabled the execution of certain tests with PREEMPT_RT_FULL, but did diff --git a/debian/patches-rt/0237-sched-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0237-sched-Add-support-for-lazy-preemption.patch index c1105bf5b..f78b92cb4 100644 --- a/debian/patches-rt/0237-sched-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0237-sched-Add-support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From 2c07898b589abf34dde2538a5c56bedf99533dab Mon Sep 17 00:00:00 2001 -Message-Id: <2c07898b589abf34dde2538a5c56bedf99533dab.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 091492e9dcff0975b11d7a66e19b0fb44abe7963 Mon Sep 17 00:00:00 2001 +Message-Id: <091492e9dcff0975b11d7a66e19b0fb44abe7963.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 26 Oct 2012 18:50:54 +0100 -Subject: [PATCH 237/329] sched: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 237/333] sched: Add support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz It has become an obsession to mitigate the determinism vs. throughput loss of RT. Looking at the mainline semantics of preemption points @@ -423,7 +423,7 @@ index 297934719db9..64edaf6fe151 100644 } EXPORT_SYMBOL(migrate_enable); diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index 80289617ce3d..627cd3961268 100644 +index 2443f921b19f..304a36c029cc 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4104,7 +4104,7 @@ check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr) @@ -480,7 +480,7 @@ index 80289617ce3d..627cd3961268 100644 /* * Only set the backward buddy when the current task is still * on the rq. This can happen when a wakeup gets interleaved -@@ -9834,7 +9834,7 @@ static void task_fork_fair(struct task_struct *p) +@@ -9839,7 +9839,7 @@ static void task_fork_fair(struct task_struct *p) * 'current' within the tree based on its new key value. */ swap(curr->vruntime, se->vruntime); @@ -489,7 +489,7 @@ index 80289617ce3d..627cd3961268 100644 } se->vruntime -= cfs_rq->min_vruntime; -@@ -9858,7 +9858,7 @@ prio_changed_fair(struct rq *rq, struct task_struct *p, int oldprio) +@@ -9863,7 +9863,7 @@ prio_changed_fair(struct rq *rq, struct task_struct *p, int oldprio) */ if (rq->curr == p) { if (p->prio > oldprio) diff --git a/debian/patches-rt/0238-ftrace-Fix-trace-header-alignment.patch b/debian/patches-rt/0238-ftrace-Fix-trace-header-alignment.patch index 9f9dcfdde..b79ae332e 100644 --- a/debian/patches-rt/0238-ftrace-Fix-trace-header-alignment.patch +++ b/debian/patches-rt/0238-ftrace-Fix-trace-header-alignment.patch @@ -1,11 +1,11 @@ -From 4b94593405e073b8c06f10adcf8b18ee59c856df Mon Sep 17 00:00:00 2001 -Message-Id: <4b94593405e073b8c06f10adcf8b18ee59c856df.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 66aa9988da587ce89de83de3e76f6dab04cdac7f Mon Sep 17 00:00:00 2001 +Message-Id: <66aa9988da587ce89de83de3e76f6dab04cdac7f.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:08:30 +0200 -Subject: [PATCH 238/329] ftrace: Fix trace header alignment -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 238/333] ftrace: Fix trace header alignment +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Line up helper arrows to the right column. diff --git a/debian/patches-rt/0239-x86-Support-for-lazy-preemption.patch b/debian/patches-rt/0239-x86-Support-for-lazy-preemption.patch index c99134d2d..4f7073241 100644 --- a/debian/patches-rt/0239-x86-Support-for-lazy-preemption.patch +++ b/debian/patches-rt/0239-x86-Support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From 20b11bc2d3602b8b334aa82b0e9567fe42c45747 Mon Sep 17 00:00:00 2001 -Message-Id: <20b11bc2d3602b8b334aa82b0e9567fe42c45747.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1473057c36e2d3a208ae26ac02657669cc263ba7 Mon Sep 17 00:00:00 2001 +Message-Id: <1473057c36e2d3a208ae26ac02657669cc263ba7.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 11:03:47 +0100 -Subject: [PATCH 239/329] x86: Support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 239/333] x86: Support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Implement the x86 pieces for lazy preempt. diff --git a/debian/patches-rt/0240-x86-lazy-preempt-properly-check-against-preempt-mask.patch b/debian/patches-rt/0240-x86-lazy-preempt-properly-check-against-preempt-mask.patch index ef5f3df52..031bb60a2 100644 --- a/debian/patches-rt/0240-x86-lazy-preempt-properly-check-against-preempt-mask.patch +++ b/debian/patches-rt/0240-x86-lazy-preempt-properly-check-against-preempt-mask.patch @@ -1,12 +1,12 @@ -From b1ee2a3de2cff388f708279f7f832ba76782e9ef Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 43146f6ab3cb9531145aa0e3a7531b595188aeac Mon Sep 17 00:00:00 2001 +Message-Id: <43146f6ab3cb9531145aa0e3a7531b595188aeac.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 16:57:09 +0100 -Subject: [PATCH 240/329] x86: lazy-preempt: properly check against +Subject: [PATCH 240/333] x86: lazy-preempt: properly check against preempt-mask -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz should_resched() should check against preempt_offset after unmasking the need-resched-bit. Otherwise should_resched() won't work for diff --git a/debian/patches-rt/0241-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch b/debian/patches-rt/0241-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch index d09b2946d..ff84de2ab 100644 --- a/debian/patches-rt/0241-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch +++ b/debian/patches-rt/0241-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch @@ -1,12 +1,12 @@ -From afdfaa64a3ab73b35cf0f8dc9d7345eaaa61fe75 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 560c5b5ded7acf42284cc899650b4b15741c05c3 Mon Sep 17 00:00:00 2001 +Message-Id: <560c5b5ded7acf42284cc899650b4b15741c05c3.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 14:53:49 +0100 -Subject: [PATCH 241/329] x86: lazy-preempt: use proper return label on +Subject: [PATCH 241/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The lazy-preempt uses the wrong return label in case preemption isn't possible. This results crash while returning to the kernel. diff --git a/debian/patches-rt/0242-arm-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0242-arm-Add-support-for-lazy-preemption.patch index 934e1af03..460513614 100644 --- a/debian/patches-rt/0242-arm-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0242-arm-Add-support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From 012d63f25f97a06484e0f04b545cac31c34c39c1 Mon Sep 17 00:00:00 2001 -Message-Id: <012d63f25f97a06484e0f04b545cac31c34c39c1.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ba2b6b0e799ace1d9d01104c828912ecb3c4c2e3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 31 Oct 2012 12:04:11 +0100 -Subject: [PATCH 242/329] arm: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 242/333] arm: Add support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Implement the arm pieces for lazy preempt. diff --git a/debian/patches-rt/0243-powerpc-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0243-powerpc-Add-support-for-lazy-preemption.patch index dcbbe66bc..00d43a58e 100644 --- a/debian/patches-rt/0243-powerpc-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0243-powerpc-Add-support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From b92073bdc2225792633135f50dd9122ccdb5e326 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 11be08c0c8e5775853e211f4701474c8a0d61bec Mon Sep 17 00:00:00 2001 +Message-Id: <11be08c0c8e5775853e211f4701474c8a0d61bec.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 10:14:11 +0100 -Subject: [PATCH 243/329] powerpc: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 243/333] powerpc: Add support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Implement the powerpc pieces for lazy preempt. diff --git a/debian/patches-rt/0244-arch-arm64-Add-lazy-preempt-support.patch b/debian/patches-rt/0244-arch-arm64-Add-lazy-preempt-support.patch index 113be6ccc..7b624b98b 100644 --- a/debian/patches-rt/0244-arch-arm64-Add-lazy-preempt-support.patch +++ b/debian/patches-rt/0244-arch-arm64-Add-lazy-preempt-support.patch @@ -1,11 +1,11 @@ -From 13a39715a42e35d2c746f27c7393b833270b2605 Mon Sep 17 00:00:00 2001 -Message-Id: <13a39715a42e35d2c746f27c7393b833270b2605.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0a0c4686c4e3cd2ff185d16cc0f0c7268c0ff5e5 Mon Sep 17 00:00:00 2001 +Message-Id: <0a0c4686c4e3cd2ff185d16cc0f0c7268c0ff5e5.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Anders Roxell Date: Thu, 14 May 2015 17:52:17 +0200 -Subject: [PATCH 244/329] arch/arm64: Add lazy preempt support -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 244/333] arch/arm64: Add lazy preempt support +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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, diff --git a/debian/patches-rt/0245-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch b/debian/patches-rt/0245-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch index ca1969797..6a8e476d9 100644 --- a/debian/patches-rt/0245-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch +++ b/debian/patches-rt/0245-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch @@ -1,12 +1,12 @@ -From 832390aa2ac43656ac56b1966a21c93616650b3b Mon Sep 17 00:00:00 2001 -Message-Id: <832390aa2ac43656ac56b1966a21c93616650b3b.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 04bdd32917bf0d666aa1cc62e32a14f347a73ad4 Mon Sep 17 00:00:00 2001 +Message-Id: <04bdd32917bf0d666aa1cc62e32a14f347a73ad4.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:11:54 +0200 -Subject: [PATCH 245/329] connector/cn_proc: Protect send_msg() with a local +Subject: [PATCH 245/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 diff --git a/debian/patches-rt/0246-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch b/debian/patches-rt/0246-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch index 18e81ecc8..5d9aa9549 100644 --- a/debian/patches-rt/0246-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch +++ b/debian/patches-rt/0246-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch @@ -1,12 +1,12 @@ -From ce6f30f35d4a32ddcea1038f5940d07dbebbab4c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 721b3640f6a1bdd80f620490e1102f925204ece0 Mon Sep 17 00:00:00 2001 +Message-Id: <721b3640f6a1bdd80f620490e1102f925204ece0.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 31 Mar 2016 04:08:28 +0200 -Subject: [PATCH 246/329] drivers/block/zram: Replace bit spinlocks with +Subject: [PATCH 246/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. diff --git a/debian/patches-rt/0247-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch b/debian/patches-rt/0247-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch index 48b8d9ece..93a9055ef 100644 --- a/debian/patches-rt/0247-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch +++ b/debian/patches-rt/0247-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch @@ -1,12 +1,12 @@ -From f85ce070074ba7b5622da31d4053eb15bca8e873 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 9456bda5b204aaf8bd2a31866555af3f51023f2d Mon Sep 17 00:00:00 2001 +Message-Id: <9456bda5b204aaf8bd2a31866555af3f51023f2d.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 20 Oct 2016 11:15:22 +0200 -Subject: [PATCH 247/329] drivers/zram: Don't disable preemption in +Subject: [PATCH 247/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 diff --git a/debian/patches-rt/0248-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch b/debian/patches-rt/0248-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch index 2cd30b797..fcff6f1f4 100644 --- a/debian/patches-rt/0248-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch +++ b/debian/patches-rt/0248-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch @@ -1,12 +1,12 @@ -From 25b5849184aea44973866a18fef8361277469583 Mon Sep 17 00:00:00 2001 -Message-Id: <25b5849184aea44973866a18fef8361277469583.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1514f26f34851da5cebf51c0b56bb30445b42147 Mon Sep 17 00:00:00 2001 +Message-Id: <1514f26f34851da5cebf51c0b56bb30445b42147.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 23 Aug 2017 11:57:29 +0200 -Subject: [PATCH 248/329] drivers/zram: fix zcomp_stream_get() +Subject: [PATCH 248/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Use get_local_ptr() instead this_cpu_ptr() to avoid a warning regarding smp_processor_id() in preemptible code. diff --git a/debian/patches-rt/0249-tpm_tis-fix-stall-after-iowrite-s.patch b/debian/patches-rt/0249-tpm_tis-fix-stall-after-iowrite-s.patch index 207d4802d..f59396d36 100644 --- a/debian/patches-rt/0249-tpm_tis-fix-stall-after-iowrite-s.patch +++ b/debian/patches-rt/0249-tpm_tis-fix-stall-after-iowrite-s.patch @@ -1,11 +1,11 @@ -From 3062d321fb92c454c4d6faffe10fe4b56dbf8d07 Mon Sep 17 00:00:00 2001 -Message-Id: <3062d321fb92c454c4d6faffe10fe4b56dbf8d07.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 46e2169761357ca46b9cd8021900d7e71ba3f74c Mon Sep 17 00:00:00 2001 +Message-Id: <46e2169761357ca46b9cd8021900d7e71ba3f74c.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Haris Okanovic Date: Tue, 15 Aug 2017 15:13:08 -0500 -Subject: [PATCH 249/329] tpm_tis: fix stall after iowrite*()s -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 249/333] tpm_tis: fix stall after iowrite*()s +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz ioread8() operations to TPM MMIO addresses can stall the cpu when immediately following a sequence of iowrite*()'s to the same region. diff --git a/debian/patches-rt/0250-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch b/debian/patches-rt/0250-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch index 0fc1cbcef..b1c195bff 100644 --- a/debian/patches-rt/0250-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch +++ b/debian/patches-rt/0250-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch @@ -1,11 +1,11 @@ -From d6406eb550b1c69e5082bd418ff0fd43ef572436 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 0e639dcb6fcfa7ce6b8aa8b6125c8a277435d121 Mon Sep 17 00:00:00 2001 +Message-Id: <0e639dcb6fcfa7ce6b8aa8b6125c8a277435d121.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 -Subject: [PATCH 250/329] watchdog: prevent deferral of watchdogd wakeup on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 250/333] watchdog: prevent deferral of watchdogd wakeup on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz When PREEMPT_RT_FULL is enabled, all hrtimer expiry functions are deferred for execution into the context of ktimersoftd unless otherwise @@ -39,9 +39,11 @@ Signed-off-by: Sebastian Andrzej Siewior drivers/watchdog/watchdog_dev.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) +diff --git a/drivers/watchdog/watchdog_dev.c b/drivers/watchdog/watchdog_dev.c +index 1c322caecf7f..822a0a20da2e 100644 --- a/drivers/watchdog/watchdog_dev.c +++ b/drivers/watchdog/watchdog_dev.c -@@ -145,7 +145,7 @@ +@@ -145,7 +145,7 @@ static inline void watchdog_update_worker(struct watchdog_device *wdd) ktime_t t = watchdog_next_keepalive(wdd); if (t > 0) @@ -50,7 +52,7 @@ Signed-off-by: Sebastian Andrzej Siewior } else { hrtimer_cancel(&wd_data->timer); } -@@ -164,7 +164,7 @@ +@@ -164,7 +164,7 @@ static int __watchdog_ping(struct watchdog_device *wdd) if (ktime_after(earliest_keepalive, now)) { hrtimer_start(&wd_data->timer, ktime_sub(earliest_keepalive, now), @@ -59,7 +61,7 @@ Signed-off-by: Sebastian Andrzej Siewior return 0; } -@@ -957,7 +957,7 @@ +@@ -957,7 +957,7 @@ static int watchdog_cdev_register(struct watchdog_device *wdd) dev_set_name(&wd_data->dev, "watchdog%d", wdd->id); kthread_init_work(&wd_data->work, watchdog_ping_work); @@ -68,7 +70,7 @@ Signed-off-by: Sebastian Andrzej Siewior wd_data->timer.function = watchdog_timer_expired; if (wdd->id == 0) { -@@ -1005,7 +1005,7 @@ +@@ -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,3 +79,6 @@ Signed-off-by: Sebastian Andrzej Siewior else pr_info("watchdog%d running and kernel based pre-userspace handler disabled\n", wdd->id); +-- +2.17.1 + diff --git a/debian/patches-rt/0251-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch b/debian/patches-rt/0251-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch index 7155afd31..ff30d1494 100644 --- a/debian/patches-rt/0251-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch +++ b/debian/patches-rt/0251-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch @@ -1,12 +1,12 @@ -From 97ccfd88d0c6abe6c94a4bef6322da580f960e5f Mon Sep 17 00:00:00 2001 -Message-Id: <97ccfd88d0c6abe6c94a4bef6322da580f960e5f.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a5c293836315eb4a5993582e3b6f192cc1f917e0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 08:09:11 +0100 -Subject: [PATCH 251/329] drm,radeon,i915: Use preempt_disable/enable_rt() +Subject: [PATCH 251/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz DRM folks identified the spots, so use them. @@ -40,10 +40,10 @@ index b7c398232136..eed1ba3009c6 100644 spin_unlock_irqrestore(&dev_priv->uncore.lock, irqflags); diff --git a/drivers/gpu/drm/radeon/radeon_display.c b/drivers/gpu/drm/radeon/radeon_display.c -index 7d1e14f0140a..bcc3456749d6 100644 +index 3f0f3a578ddf..7aab36714b28 100644 --- a/drivers/gpu/drm/radeon/radeon_display.c +++ b/drivers/gpu/drm/radeon/radeon_display.c -@@ -1815,6 +1815,7 @@ int radeon_get_crtc_scanoutpos(struct drm_device *dev, unsigned int pipe, +@@ -1817,6 +1817,7 @@ int radeon_get_crtc_scanoutpos(struct drm_device *dev, unsigned int pipe, struct radeon_device *rdev = dev->dev_private; /* preempt_disable_rt() should go right here in PREEMPT_RT patchset. */ @@ -51,7 +51,7 @@ index 7d1e14f0140a..bcc3456749d6 100644 /* Get optional system timestamp before query. */ if (stime) -@@ -1907,6 +1908,7 @@ int radeon_get_crtc_scanoutpos(struct drm_device *dev, unsigned int pipe, +@@ -1909,6 +1910,7 @@ int radeon_get_crtc_scanoutpos(struct drm_device *dev, unsigned int pipe, *etime = ktime_get(); /* preempt_enable_rt() should go right here in PREEMPT_RT patchset. */ diff --git a/debian/patches-rt/0252-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch b/debian/patches-rt/0252-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch index 702bc3d9e..0e8510d9a 100644 --- a/debian/patches-rt/0252-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch +++ b/debian/patches-rt/0252-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch @@ -1,12 +1,12 @@ -From cbcedbe458c342c08552f499f686b0f78db20c57 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8693ba302fd124165c7faaabad16cf4f1d5a1e94 Mon Sep 17 00:00:00 2001 +Message-Id: <8693ba302fd124165c7faaabad16cf4f1d5a1e94.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 09:01:42 +0100 -Subject: [PATCH 252/329] drm,i915: Use local_lock/unlock_irq() in +Subject: [PATCH 252/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 diff --git a/debian/patches-rt/0253-drm-i915-disable-tracing-on-RT.patch b/debian/patches-rt/0253-drm-i915-disable-tracing-on-RT.patch index 941d79085..5b99cd147 100644 --- a/debian/patches-rt/0253-drm-i915-disable-tracing-on-RT.patch +++ b/debian/patches-rt/0253-drm-i915-disable-tracing-on-RT.patch @@ -1,11 +1,11 @@ -From 57ba9581c24d9a89c0e2c95bb5ce60905f7fdc27 Mon Sep 17 00:00:00 2001 -Message-Id: <57ba9581c24d9a89c0e2c95bb5ce60905f7fdc27.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1b1b71728e76bfa53ff622fc1cfbb4aa198f0f75 Mon Sep 17 00:00:00 2001 +Message-Id: <1b1b71728e76bfa53ff622fc1cfbb4aa198f0f75.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 09:52:20 +0100 -Subject: [PATCH 253/329] drm/i915: disable tracing on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 253/333] drm/i915: disable tracing on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Luca Abeni reported this: | BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003 diff --git a/debian/patches-rt/0254-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch b/debian/patches-rt/0254-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch index 679b66bdb..e32681239 100644 --- a/debian/patches-rt/0254-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch +++ b/debian/patches-rt/0254-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch @@ -1,12 +1,12 @@ -From dea92d5c52462df2f9d8a27620bffb0460010d0a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5c5e7266cbb4cf96d89ba8205c0a01d9f74737e9 Mon Sep 17 00:00:00 2001 +Message-Id: <5c5e7266cbb4cf96d89ba8205c0a01d9f74737e9.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 19 Dec 2018 10:47:02 +0100 -Subject: [PATCH 254/329] drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with +Subject: [PATCH 254/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 diff --git a/debian/patches-rt/0255-cgroups-use-simple-wait-in-css_release.patch b/debian/patches-rt/0255-cgroups-use-simple-wait-in-css_release.patch index 521c06967..6144b77d6 100644 --- a/debian/patches-rt/0255-cgroups-use-simple-wait-in-css_release.patch +++ b/debian/patches-rt/0255-cgroups-use-simple-wait-in-css_release.patch @@ -1,11 +1,11 @@ -From efea562234e9594e7ef12a742934c2cef5a02880 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8555748fa72e318d1ff9aae254938a5f2e937828 Mon Sep 17 00:00:00 2001 +Message-Id: <8555748fa72e318d1ff9aae254938a5f2e937828.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 13 Feb 2015 15:52:24 +0100 -Subject: [PATCH 255/329] cgroups: use simple wait in css_release() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 255/333] cgroups: use simple wait in css_release() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz To avoid: |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914 @@ -58,7 +58,7 @@ index f92264d1ed4f..cc912f3dc203 100644 /* diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c -index 6ae98c714edd..32a4b0e73ed0 100644 +index 2a879d34bbe5..35a4efda98f7 100644 --- a/kernel/cgroup/cgroup.c +++ b/kernel/cgroup/cgroup.c @@ -4680,10 +4680,10 @@ static void css_free_rwork_fn(struct work_struct *work) diff --git a/debian/patches-rt/0256-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0256-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch index 44ef42789..e728264b5 100644 --- a/debian/patches-rt/0256-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0256-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From ccaeee7e528b0640b85ed16bf3e904813007359d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 574cb22c45ec4a876cc7d5bb974b2182c51b105e Mon Sep 17 00:00:00 2001 +Message-Id: <574cb22c45ec4a876cc7d5bb974b2182c51b105e.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 8 Jan 2017 09:32:25 +0100 -Subject: [PATCH 256/329] cpuset: Convert callback_lock to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 256/333] cpuset: Convert callback_lock to raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The two commits below add up to a cpuset might_sleep() splat for RT: diff --git a/debian/patches-rt/0257-apparmor-use-a-locallock-instead-preempt_disable.patch b/debian/patches-rt/0257-apparmor-use-a-locallock-instead-preempt_disable.patch index b26c9acad..e3f606212 100644 --- a/debian/patches-rt/0257-apparmor-use-a-locallock-instead-preempt_disable.patch +++ b/debian/patches-rt/0257-apparmor-use-a-locallock-instead-preempt_disable.patch @@ -1,11 +1,11 @@ -From 8f87d239f6657f4d4b44d4416acf227ea03ed64c Mon Sep 17 00:00:00 2001 -Message-Id: <8f87d239f6657f4d4b44d4416acf227ea03ed64c.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From cc27650286075053b720294b5e23a40b4ffc101c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 11 Oct 2017 17:43:49 +0200 -Subject: [PATCH 257/329] apparmor: use a locallock instead preempt_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 257/333] apparmor: use a locallock instead preempt_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 diff --git a/debian/patches-rt/0258-workqueue-Prevent-deadlock-stall-on-RT.patch b/debian/patches-rt/0258-workqueue-Prevent-deadlock-stall-on-RT.patch index 3b899cba8..84ff433c0 100644 --- a/debian/patches-rt/0258-workqueue-Prevent-deadlock-stall-on-RT.patch +++ b/debian/patches-rt/0258-workqueue-Prevent-deadlock-stall-on-RT.patch @@ -1,11 +1,11 @@ -From 34b852bfa79162dde3e9eda062390595365df54a Mon Sep 17 00:00:00 2001 -Message-Id: <34b852bfa79162dde3e9eda062390595365df54a.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8feeb4585aaf716ac3728b50a7b1b5a3ed54ae36 Mon Sep 17 00:00:00 2001 +Message-Id: <8feeb4585aaf716ac3728b50a7b1b5a3ed54ae36.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 27 Jun 2014 16:24:52 +0200 -Subject: [PATCH 258/329] workqueue: Prevent deadlock/stall on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 258/333] workqueue: Prevent deadlock/stall on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. diff --git a/debian/patches-rt/0259-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch b/debian/patches-rt/0259-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch index ac8937c15..df486b88a 100644 --- a/debian/patches-rt/0259-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch +++ b/debian/patches-rt/0259-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch @@ -1,11 +1,11 @@ -From bc0a957ff263743367ac579797050dd0d424512b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d23194475f30cbe5bc9dd84735a66cec5954972d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:56 -0500 -Subject: [PATCH 259/329] 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.135-rt60.tar.xz +Subject: [PATCH 259/333] 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.142-rt63.tar.xz To avoid allocation allow rt tasks to cache one sigqueue struct in task struct. diff --git a/debian/patches-rt/0260-Add-localversion-for-RT-release.patch b/debian/patches-rt/0260-Add-localversion-for-RT-release.patch index dee6ba302..456f28a07 100644 --- a/debian/patches-rt/0260-Add-localversion-for-RT-release.patch +++ b/debian/patches-rt/0260-Add-localversion-for-RT-release.patch @@ -1,11 +1,11 @@ -From cb3085166d917b84231899ebe30c352c766e8da2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8bb3188957630f451060955ac31ef6c8e4f66133 Mon Sep 17 00:00:00 2001 +Message-Id: <8bb3188957630f451060955ac31ef6c8e4f66133.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 20:25:16 +0200 -Subject: [PATCH 260/329] Add localversion for -RT release -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 260/333] Add localversion for -RT release +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Signed-off-by: Thomas Gleixner --- diff --git a/debian/patches-rt/0261-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch b/debian/patches-rt/0261-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch index 39d4d1e3b..80658134e 100644 --- a/debian/patches-rt/0261-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch +++ b/debian/patches-rt/0261-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch @@ -1,12 +1,12 @@ -From 8c54cb57167c953f8fbe9f9fd297ac9763591d74 Mon Sep 17 00:00:00 2001 -Message-Id: <8c54cb57167c953f8fbe9f9fd297ac9763591d74.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 38f04487bf7f726d2580a33d5ed11fc1c4cf48a0 Mon Sep 17 00:00:00 2001 +Message-Id: <38f04487bf7f726d2580a33d5ed11fc1c4cf48a0.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Mar 2019 18:31:54 +0100 -Subject: [PATCH 261/329] powerpc/pseries/iommu: Use a locallock instead +Subject: [PATCH 261/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The locallock protects the per-CPU variable tce_page. The function attempts to allocate memory while tce_page is protected (by disabling diff --git a/debian/patches-rt/0262-powerpc-reshuffle-TIF-bits.patch b/debian/patches-rt/0262-powerpc-reshuffle-TIF-bits.patch index f13f838d3..b9c325d61 100644 --- a/debian/patches-rt/0262-powerpc-reshuffle-TIF-bits.patch +++ b/debian/patches-rt/0262-powerpc-reshuffle-TIF-bits.patch @@ -1,11 +1,11 @@ -From 37a56eaba0c00116aa3d3130200ae6d5d3561ca8 Mon Sep 17 00:00:00 2001 -Message-Id: <37a56eaba0c00116aa3d3130200ae6d5d3561ca8.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 292cbb4d659fba9222397b15374292d7228cc327 Mon Sep 17 00:00:00 2001 +Message-Id: <292cbb4d659fba9222397b15374292d7228cc327.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 22 Mar 2019 17:15:58 +0100 -Subject: [PATCH 262/329] powerpc: reshuffle TIF bits -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 262/333] powerpc: reshuffle TIF bits +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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. diff --git a/debian/patches-rt/0263-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0263-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch index 875e16b9f..ec05e4775 100644 --- a/debian/patches-rt/0263-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0263-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From ea3af8328b32575df8c85280eae6bedadd942e2f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d8523fad15187a82770cc560bcc454855ecb40ee Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 13 Mar 2019 11:40:34 +0000 -Subject: [PATCH 263/329] 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.135-rt60.tar.xz +Subject: [PATCH 263/333] 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.142-rt63.tar.xz Systems which don't provide arch_trigger_cpumask_backtrace() will invoke showacpu() from a smp_call_function() function which is invoked diff --git a/debian/patches-rt/0264-drm-i915-Don-t-disable-interrupts-independently-of-t.patch b/debian/patches-rt/0264-drm-i915-Don-t-disable-interrupts-independently-of-t.patch index 9db34c8d1..01bffd977 100644 --- a/debian/patches-rt/0264-drm-i915-Don-t-disable-interrupts-independently-of-t.patch +++ b/debian/patches-rt/0264-drm-i915-Don-t-disable-interrupts-independently-of-t.patch @@ -1,12 +1,12 @@ -From 99725bf891380f1d31ccb9a0cd85e686d8c1fffc Mon Sep 17 00:00:00 2001 -Message-Id: <99725bf891380f1d31ccb9a0cd85e686d8c1fffc.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e8f64f55f1dab003349825781f5baa1537fcf7bc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 10 Apr 2019 11:01:37 +0200 -Subject: [PATCH 264/329] drm/i915: Don't disable interrupts independently of +Subject: [PATCH 264/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 diff --git a/debian/patches-rt/0265-sched-completion-Fix-a-lockup-in-wait_for_completion.patch b/debian/patches-rt/0265-sched-completion-Fix-a-lockup-in-wait_for_completion.patch index 3f2ff3243..410079875 100644 --- a/debian/patches-rt/0265-sched-completion-Fix-a-lockup-in-wait_for_completion.patch +++ b/debian/patches-rt/0265-sched-completion-Fix-a-lockup-in-wait_for_completion.patch @@ -1,12 +1,12 @@ -From 5ad84d4b59fd5dac1aebc8c300a707baba9d1498 Mon Sep 17 00:00:00 2001 -Message-Id: <5ad84d4b59fd5dac1aebc8c300a707baba9d1498.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 6dc7943d18c67e3ed723cac7e4ea01f6fcd44e9d Mon Sep 17 00:00:00 2001 +Message-Id: <6dc7943d18c67e3ed723cac7e4ea01f6fcd44e9d.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Corey Minyard Date: Thu, 9 May 2019 14:33:20 -0500 -Subject: [PATCH 265/329] sched/completion: Fix a lockup in +Subject: [PATCH 265/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Consider following race: diff --git a/debian/patches-rt/0266-kthread-add-a-global-worker-thread.patch b/debian/patches-rt/0266-kthread-add-a-global-worker-thread.patch index 9a87e4182..f4ce30008 100644 --- a/debian/patches-rt/0266-kthread-add-a-global-worker-thread.patch +++ b/debian/patches-rt/0266-kthread-add-a-global-worker-thread.patch @@ -1,11 +1,11 @@ -From 2be03ce4173c7b8223c55b2a37708463ffd169f4 Mon Sep 17 00:00:00 2001 -Message-Id: <2be03ce4173c7b8223c55b2a37708463ffd169f4.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 97d6e0ff7b496cd049c76204c58ba5439089574f Mon Sep 17 00:00:00 2001 +Message-Id: <97d6e0ff7b496cd049c76204c58ba5439089574f.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 12 Feb 2019 15:09:38 +0100 -Subject: [PATCH 266/329] kthread: add a global worker thread. -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 266/333] kthread: add a global worker thread. +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 0532e87d9d44795221aa921ba7024bde689cc894 ] @@ -32,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 728681a20b7f..ec7442545b84 100644 +index da68c42aed68..5f07061c4087 100644 --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -70,7 +70,7 @@ @@ -147,7 +147,7 @@ index 2180c6388eb9..7b173ca08e22 100644 init_mm_internals(); diff --git a/kernel/kthread.c b/kernel/kthread.c -index 5641b55783a6..9db017761a1f 100644 +index 81aa14daa5fe..42294c806ad0 100644 --- a/kernel/kthread.c +++ b/kernel/kthread.c @@ -20,6 +20,7 @@ @@ -158,7 +158,7 @@ index 5641b55783a6..9db017761a1f 100644 #include static DEFINE_SPINLOCK(kthread_create_lock); -@@ -1180,6 +1181,19 @@ void kthread_destroy_worker(struct kthread_worker *worker) +@@ -1193,6 +1194,19 @@ void kthread_destroy_worker(struct kthread_worker *worker) } EXPORT_SYMBOL(kthread_destroy_worker); diff --git a/debian/patches-rt/0267-arm-imx6-cpuidle-Use-raw_spinlock_t.patch b/debian/patches-rt/0267-arm-imx6-cpuidle-Use-raw_spinlock_t.patch index 5655363bb..c82e76cf5 100644 --- a/debian/patches-rt/0267-arm-imx6-cpuidle-Use-raw_spinlock_t.patch +++ b/debian/patches-rt/0267-arm-imx6-cpuidle-Use-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From 486078890cca7e30efddb5383879ad96aae8f0bf Mon Sep 17 00:00:00 2001 -Message-Id: <486078890cca7e30efddb5383879ad96aae8f0bf.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 552f780b71cc9cc54aff7beca8412c06c95a9f82 Mon Sep 17 00:00:00 2001 +Message-Id: <552f780b71cc9cc54aff7beca8412c06c95a9f82.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 May 2019 17:07:44 +0200 -Subject: [PATCH 267/329] arm: imx6: cpuidle: Use raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 267/333] arm: imx6: cpuidle: Use raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 40d0332ec8312e9c090f0a5414d9c90e12b13611 ] diff --git a/debian/patches-rt/0268-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch b/debian/patches-rt/0268-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch index 859357b7d..3148e802e 100644 --- a/debian/patches-rt/0268-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch +++ b/debian/patches-rt/0268-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch @@ -1,12 +1,12 @@ -From debddd2c9f8b9b92a77b4e692564a08b21571a51 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 40063fce95967cf318dabcb7ebbf702f446c7cc0 Mon Sep 17 00:00:00 2001 +Message-Id: <40063fce95967cf318dabcb7ebbf702f446c7cc0.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 18:29:13 +0200 -Subject: [PATCH 268/329] rcu: Don't allow to change rcu_normal_after_boot on +Subject: [PATCH 268/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit c6c058c10577815a2491ce661876cff00a4c3b15 ] diff --git a/debian/patches-rt/0269-pci-switchtec-fix-stream_open.cocci-warnings.patch b/debian/patches-rt/0269-pci-switchtec-fix-stream_open.cocci-warnings.patch index 56472e54d..aa663ccd2 100644 --- a/debian/patches-rt/0269-pci-switchtec-fix-stream_open.cocci-warnings.patch +++ b/debian/patches-rt/0269-pci-switchtec-fix-stream_open.cocci-warnings.patch @@ -1,11 +1,11 @@ -From 139fcd6df14d4169fd00bb504ebb202fe4167c94 Mon Sep 17 00:00:00 2001 -Message-Id: <139fcd6df14d4169fd00bb504ebb202fe4167c94.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From c7f5d95b2a5a283d20f9ea61f6a2136b73b79877 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: kbuild test robot Date: Sat, 13 Apr 2019 11:22:51 +0800 -Subject: [PATCH 269/329] pci/switchtec: fix stream_open.cocci warnings -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 269/333] pci/switchtec: fix stream_open.cocci warnings +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 9462c69e29307adc95c289f50839d5d683973891 ] diff --git a/debian/patches-rt/0270-sched-core-Drop-a-preempt_disable_rt-statement.patch b/debian/patches-rt/0270-sched-core-Drop-a-preempt_disable_rt-statement.patch index fd9859f50..a23796eeb 100644 --- a/debian/patches-rt/0270-sched-core-Drop-a-preempt_disable_rt-statement.patch +++ b/debian/patches-rt/0270-sched-core-Drop-a-preempt_disable_rt-statement.patch @@ -1,11 +1,11 @@ -From 06c646b5acbda25c7ebb05d9cf4f2de77a534a23 Mon Sep 17 00:00:00 2001 -Message-Id: <06c646b5acbda25c7ebb05d9cf4f2de77a534a23.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 95a0e13d19f8fddf4496929e878e6f23be633538 Mon Sep 17 00:00:00 2001 +Message-Id: <95a0e13d19f8fddf4496929e878e6f23be633538.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:33:16 +0200 -Subject: [PATCH 270/329] sched/core: Drop a preempt_disable_rt() statement -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 270/333] sched/core: Drop a preempt_disable_rt() statement +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 761126efdcbe3fa3e99c9079fa0ad6eca2f251f2 ] diff --git a/debian/patches-rt/0271-timers-Redo-the-notification-of-canceling-timers-on-.patch b/debian/patches-rt/0271-timers-Redo-the-notification-of-canceling-timers-on-.patch index 64e0c8f53..b9f2e9af8 100644 --- a/debian/patches-rt/0271-timers-Redo-the-notification-of-canceling-timers-on-.patch +++ b/debian/patches-rt/0271-timers-Redo-the-notification-of-canceling-timers-on-.patch @@ -1,12 +1,12 @@ -From 50c77b51735c142605d4621a971453a3705eb233 Mon Sep 17 00:00:00 2001 -Message-Id: <50c77b51735c142605d4621a971453a3705eb233.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 749ec0a0974045425f2cdd69002251900a3cc046 Mon Sep 17 00:00:00 2001 +Message-Id: <749ec0a0974045425f2cdd69002251900a3cc046.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:39:06 +0200 -Subject: [PATCH 271/329] timers: Redo the notification of canceling timers on +Subject: [PATCH 271/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit c71273154c2ad12e13333aada340ff30e826a11b ] @@ -42,9 +42,11 @@ Signed-off-by: Steven Rostedt (VMware) kernel/time/timer.c | 96 ++++++++++++++++------------------ 10 files changed, 118 insertions(+), 135 deletions(-) +diff --git a/fs/timerfd.c b/fs/timerfd.c +index 82d0f52414a6..f845093466be 100644 --- a/fs/timerfd.c +++ b/fs/timerfd.c -@@ -471,10 +471,11 @@ +@@ -471,10 +471,11 @@ static int do_timerfd_settime(int ufd, int flags, break; } spin_unlock_irq(&ctx->wqh.lock); @@ -58,6 +60,8 @@ Signed-off-by: Steven Rostedt (VMware) } /* +diff --git a/include/linux/hrtimer.h b/include/linux/hrtimer.h +index 082147c07831..aee31b1f0cc3 100644 --- a/include/linux/hrtimer.h +++ b/include/linux/hrtimer.h @@ -22,7 +22,6 @@ @@ -68,7 +72,7 @@ Signed-off-by: Steven Rostedt (VMware) struct hrtimer_clock_base; struct hrtimer_cpu_base; -@@ -193,6 +192,8 @@ +@@ -193,6 +192,8 @@ enum hrtimer_base_type { * @nr_retries: Total number of hrtimer interrupt retries * @nr_hangs: Total number of hrtimer interrupt hangs * @max_hang_time: Maximum time spent in hrtimer_interrupt @@ -77,7 +81,7 @@ Signed-off-by: Steven Rostedt (VMware) * @expires_next: absolute time of the next event, is required for remote * hrtimer enqueue; it is the total first expiry time (hard * and soft hrtimer are taken into account) -@@ -220,12 +221,10 @@ +@@ -220,12 +221,10 @@ struct hrtimer_cpu_base { unsigned short nr_hangs; unsigned int max_hang_time; #endif @@ -91,7 +95,7 @@ Signed-off-by: Steven Rostedt (VMware) struct hrtimer *softirq_next_timer; struct hrtimer_clock_base clock_base[HRTIMER_MAX_CLOCK_BASES]; } ____cacheline_aligned; -@@ -426,6 +425,7 @@ +@@ -426,6 +425,7 @@ static inline void hrtimer_start(struct hrtimer *timer, ktime_t tim, extern int hrtimer_cancel(struct hrtimer *timer); extern int hrtimer_try_to_cancel(struct hrtimer *timer); @@ -99,7 +103,7 @@ Signed-off-by: Steven Rostedt (VMware) static inline void hrtimer_start_expires(struct hrtimer *timer, enum hrtimer_mode mode) -@@ -443,13 +443,6 @@ +@@ -443,13 +443,6 @@ static inline void hrtimer_restart(struct hrtimer *timer) hrtimer_start_expires(timer, HRTIMER_MODE_ABS); } @@ -113,7 +117,7 @@ Signed-off-by: Steven Rostedt (VMware) /* Query timers: */ extern ktime_t __hrtimer_get_remaining(const struct hrtimer *timer, bool adjust); -@@ -481,7 +474,7 @@ +@@ -481,7 +474,7 @@ static inline bool hrtimer_is_queued(struct hrtimer *timer) * Helper function to check, whether the timer is running the callback * function */ @@ -122,9 +126,11 @@ Signed-off-by: Steven Rostedt (VMware) { return timer->base->running == timer; } +diff --git a/include/linux/posix-timers.h b/include/linux/posix-timers.h +index 0571b498db73..3e6c91bdf2ef 100644 --- a/include/linux/posix-timers.h +++ b/include/linux/posix-timers.h -@@ -15,6 +15,7 @@ +@@ -15,6 +15,7 @@ struct cpu_timer_list { u64 expires, incr; struct task_struct *task; int firing; @@ -132,9 +138,11 @@ Signed-off-by: Steven Rostedt (VMware) }; /* +diff --git a/kernel/time/alarmtimer.c b/kernel/time/alarmtimer.c +index a465564367ec..dcf0204264f1 100644 --- a/kernel/time/alarmtimer.c +++ b/kernel/time/alarmtimer.c -@@ -438,7 +438,7 @@ +@@ -438,7 +438,7 @@ int alarm_cancel(struct alarm *alarm) int ret = alarm_try_to_cancel(alarm); if (ret >= 0) return ret; @@ -143,9 +151,11 @@ Signed-off-by: Steven Rostedt (VMware) } } EXPORT_SYMBOL_GPL(alarm_cancel); +diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c +index f16cbc98c47a..ed5d8d51ca91 100644 --- a/kernel/time/hrtimer.c +++ b/kernel/time/hrtimer.c -@@ -963,33 +963,16 @@ +@@ -963,33 +963,16 @@ u64 hrtimer_forward(struct hrtimer *timer, ktime_t now, ktime_t interval) } EXPORT_SYMBOL_GPL(hrtimer_forward); @@ -184,7 +194,7 @@ Signed-off-by: Steven Rostedt (VMware) /* * enqueue_hrtimer - internal function to (re)start a timer * -@@ -1227,7 +1210,7 @@ +@@ -1227,7 +1210,7 @@ int hrtimer_cancel(struct hrtimer *timer) if (ret >= 0) return ret; @@ -193,7 +203,7 @@ Signed-off-by: Steven Rostedt (VMware) } } EXPORT_SYMBOL_GPL(hrtimer_cancel); -@@ -1531,6 +1514,7 @@ +@@ -1531,6 +1514,7 @@ static __latent_entropy void hrtimer_run_softirq(struct softirq_action *h) unsigned long flags; ktime_t now; @@ -201,7 +211,7 @@ Signed-off-by: Steven Rostedt (VMware) raw_spin_lock_irqsave(&cpu_base->lock, flags); now = hrtimer_update_base(cpu_base); -@@ -1540,7 +1524,7 @@ +@@ -1540,7 +1524,7 @@ static __latent_entropy void hrtimer_run_softirq(struct softirq_action *h) hrtimer_update_softirq_timer(cpu_base, true); raw_spin_unlock_irqrestore(&cpu_base->lock, flags); @@ -210,7 +220,7 @@ Signed-off-by: Steven Rostedt (VMware) } #ifdef CONFIG_HIGH_RES_TIMERS -@@ -1950,9 +1934,7 @@ +@@ -1950,9 +1934,7 @@ int hrtimers_prepare_cpu(unsigned int cpu) cpu_base->softirq_next_timer = NULL; cpu_base->expires_next = KTIME_MAX; cpu_base->softirq_expires_next = KTIME_MAX; @@ -221,9 +231,11 @@ Signed-off-by: Steven Rostedt (VMware) return 0; } +diff --git a/kernel/time/itimer.c b/kernel/time/itimer.c +index 55b0e58368bf..a5ff222df4c7 100644 --- a/kernel/time/itimer.c +++ b/kernel/time/itimer.c -@@ -215,7 +215,7 @@ +@@ -215,7 +215,7 @@ int do_setitimer(int which, struct itimerval *value, struct itimerval *ovalue) /* We are sharing ->siglock with it_real_fn() */ if (hrtimer_try_to_cancel(timer) < 0) { spin_unlock_irq(&tsk->sighand->siglock); @@ -232,9 +244,11 @@ Signed-off-by: Steven Rostedt (VMware) goto again; } expires = timeval_to_ktime(value->it_value); +diff --git a/kernel/time/posix-cpu-timers.c b/kernel/time/posix-cpu-timers.c +index 8d95e8de98b2..765e700962ab 100644 --- a/kernel/time/posix-cpu-timers.c +++ b/kernel/time/posix-cpu-timers.c -@@ -792,6 +792,7 @@ +@@ -792,6 +792,7 @@ check_timers_list(struct list_head *timers, return t->expires; t->firing = 1; @@ -242,7 +256,7 @@ Signed-off-by: Steven Rostedt (VMware) list_move_tail(&t->entry, firing); } -@@ -1138,6 +1139,20 @@ +@@ -1138,6 +1139,20 @@ static inline int fastpath_timer_check(struct task_struct *tsk) return 0; } @@ -263,7 +277,7 @@ Signed-off-by: Steven Rostedt (VMware) /* * This is called from the timer interrupt handler. The irq handler has * already updated our counts. We need to check if any timers fire now. -@@ -1148,6 +1163,7 @@ +@@ -1148,6 +1163,7 @@ static void __run_posix_cpu_timers(struct task_struct *tsk) LIST_HEAD(firing); struct k_itimer *timer, *next; unsigned long flags; @@ -271,7 +285,7 @@ Signed-off-by: Steven Rostedt (VMware) /* * The fast path checks that there are no expired thread or thread -@@ -1156,6 +1172,9 @@ +@@ -1156,6 +1172,9 @@ static void __run_posix_cpu_timers(struct task_struct *tsk) if (!fastpath_timer_check(tsk)) return; @@ -281,7 +295,7 @@ Signed-off-by: Steven Rostedt (VMware) if (!lock_task_sighand(tsk, &flags)) return; /* -@@ -1190,6 +1209,7 @@ +@@ -1190,6 +1209,7 @@ static void __run_posix_cpu_timers(struct task_struct *tsk) list_del_init(&timer->it.cpu.entry); cpu_firing = timer->it.cpu.firing; timer->it.cpu.firing = 0; @@ -289,7 +303,7 @@ Signed-off-by: Steven Rostedt (VMware) /* * The firing flag is -1 if we collided with a reset * of the timer, which already reported this -@@ -1199,6 +1219,7 @@ +@@ -1199,6 +1219,7 @@ static void __run_posix_cpu_timers(struct task_struct *tsk) cpu_timer_fire(timer); spin_unlock(&timer->it_lock); } @@ -297,7 +311,7 @@ Signed-off-by: Steven Rostedt (VMware) } #ifdef CONFIG_PREEMPT_RT_BASE -@@ -1466,6 +1487,8 @@ +@@ -1466,6 +1487,8 @@ static int do_cpu_nanosleep(const clockid_t which_clock, int flags, spin_unlock_irq(&timer.it_lock); while (error == TIMER_RETRY) { @@ -306,9 +320,11 @@ Signed-off-by: Steven Rostedt (VMware) /* * We need to handle case when timer was or is in the * middle of firing. In other cases we already freed +diff --git a/kernel/time/posix-timers.c b/kernel/time/posix-timers.c +index a5ec421e3437..c7e97d421590 100644 --- a/kernel/time/posix-timers.c +++ b/kernel/time/posix-timers.c -@@ -821,25 +821,20 @@ +@@ -821,25 +821,20 @@ static void common_hrtimer_arm(struct k_itimer *timr, ktime_t expires, hrtimer_start_expires(timer, HRTIMER_MODE_ABS); } @@ -344,7 +360,7 @@ Signed-off-by: Steven Rostedt (VMware) } /* Set a POSIX.1b interval timer. */ -@@ -901,21 +896,21 @@ +@@ -901,21 +896,21 @@ static int do_timer_settime(timer_t timer_id, int flags, if (!timr) return -EINVAL; @@ -370,7 +386,7 @@ Signed-off-by: Steven Rostedt (VMware) return error; } -@@ -977,13 +972,21 @@ +@@ -977,13 +972,21 @@ int common_timer_del(struct k_itimer *timer) return 0; } @@ -394,7 +410,7 @@ Signed-off-by: Steven Rostedt (VMware) } /* Delete a POSIX.1b interval timer. */ -@@ -997,15 +1000,8 @@ +@@ -997,15 +1000,8 @@ SYSCALL_DEFINE1(timer_delete, timer_t, timer_id) if (!timer) return -EINVAL; @@ -411,7 +427,7 @@ Signed-off-by: Steven Rostedt (VMware) spin_lock(¤t->sighand->siglock); list_del(&timer->list); -@@ -1031,20 +1027,9 @@ +@@ -1031,20 +1027,9 @@ static void itimer_delete(struct k_itimer *timer) retry_delete: spin_lock_irqsave(&timer->it_lock, flags); @@ -434,9 +450,11 @@ Signed-off-by: Steven Rostedt (VMware) list_del(&timer->list); /* * This keeps any tasks waiting on the spin lock from thinking +diff --git a/kernel/time/posix-timers.h b/kernel/time/posix-timers.h +index ddb21145211a..725bd230a8db 100644 --- a/kernel/time/posix-timers.h +++ b/kernel/time/posix-timers.h -@@ -32,6 +32,8 @@ +@@ -32,6 +32,8 @@ extern const struct k_clock clock_process; extern const struct k_clock clock_thread; extern const struct k_clock alarm_clock; @@ -445,6 +463,8 @@ Signed-off-by: Steven Rostedt (VMware) int posix_timer_event(struct k_itimer *timr, int si_private); void common_timer_get(struct k_itimer *timr, struct itimerspec64 *cur_setting); +diff --git a/kernel/time/timer.c b/kernel/time/timer.c +index bdbfd52b1cfd..716364bbe5be 100644 --- a/kernel/time/timer.c +++ b/kernel/time/timer.c @@ -45,7 +45,6 @@ @@ -455,3 +475,179 @@ Signed-off-by: Steven Rostedt (VMware) #include #include +@@ -199,9 +198,7 @@ EXPORT_SYMBOL(jiffies_64); + struct timer_base { + raw_spinlock_t lock; + struct timer_list *running_timer; +-#ifdef CONFIG_PREEMPT_RT_FULL +- struct swait_queue_head wait_for_running_timer; +-#endif ++ spinlock_t expiry_lock; + unsigned long clk; + unsigned long next_expiry; + unsigned int cpu; +@@ -1201,33 +1198,6 @@ void add_timer_on(struct timer_list *timer, int cpu) + } + EXPORT_SYMBOL_GPL(add_timer_on); + +-#ifdef CONFIG_PREEMPT_RT_FULL +-/* +- * Wait for a running timer +- */ +-static void wait_for_running_timer(struct timer_list *timer) +-{ +- struct timer_base *base; +- u32 tf = timer->flags; +- +- if (tf & TIMER_MIGRATING) +- return; +- +- base = get_timer_base(tf); +- swait_event_exclusive(base->wait_for_running_timer, +- base->running_timer != timer); +-} +- +-# define wakeup_timer_waiters(b) swake_up_all(&(b)->wait_for_running_timer) +-#else +-static inline void wait_for_running_timer(struct timer_list *timer) +-{ +- cpu_relax(); +-} +- +-# define wakeup_timer_waiters(b) do { } while (0) +-#endif +- + /** + * del_timer - deactivate a timer. + * @timer: the timer to be deactivated +@@ -1257,14 +1227,8 @@ int del_timer(struct timer_list *timer) + } + EXPORT_SYMBOL(del_timer); + +-/** +- * try_to_del_timer_sync - Try to deactivate a timer +- * @timer: timer to delete +- * +- * This function tries to deactivate a timer. Upon successful (ret >= 0) +- * exit the timer is not queued and the handler is not running on any CPU. +- */ +-int try_to_del_timer_sync(struct timer_list *timer) ++static int __try_to_del_timer_sync(struct timer_list *timer, ++ struct timer_base **basep) + { + struct timer_base *base; + unsigned long flags; +@@ -1272,7 +1236,7 @@ int try_to_del_timer_sync(struct timer_list *timer) + + debug_assert_init(timer); + +- base = lock_timer_base(timer, &flags); ++ *basep = base = lock_timer_base(timer, &flags); + + if (base->running_timer != timer) + ret = detach_if_pending(timer, base, true); +@@ -1281,9 +1245,42 @@ int try_to_del_timer_sync(struct timer_list *timer) + + return ret; + } ++ ++/** ++ * try_to_del_timer_sync - Try to deactivate a timer ++ * @timer: timer to delete ++ * ++ * This function tries to deactivate a timer. Upon successful (ret >= 0) ++ * exit the timer is not queued and the handler is not running on any CPU. ++ */ ++int try_to_del_timer_sync(struct timer_list *timer) ++{ ++ struct timer_base *base; ++ ++ return __try_to_del_timer_sync(timer, &base); ++} + EXPORT_SYMBOL(try_to_del_timer_sync); + + #if defined(CONFIG_SMP) || defined(CONFIG_PREEMPT_RT_FULL) ++static int __del_timer_sync(struct timer_list *timer) ++{ ++ struct timer_base *base; ++ int ret; ++ ++ for (;;) { ++ ret = __try_to_del_timer_sync(timer, &base); ++ if (ret >= 0) ++ return ret; ++ ++ /* ++ * When accessing the lock, timers of base are no longer expired ++ * and so timer is no longer running. ++ */ ++ spin_lock(&base->expiry_lock); ++ spin_unlock(&base->expiry_lock); ++ } ++} ++ + /** + * del_timer_sync - deactivate a timer and wait for the handler to finish. + * @timer: the timer to be deactivated +@@ -1339,12 +1336,8 @@ int del_timer_sync(struct timer_list *timer) + * could lead to deadlock. + */ + WARN_ON(in_irq() && !(timer->flags & TIMER_IRQSAFE)); +- for (;;) { +- int ret = try_to_del_timer_sync(timer); +- if (ret >= 0) +- return ret; +- wait_for_running_timer(timer); +- } ++ ++ return __del_timer_sync(timer); + } + EXPORT_SYMBOL(del_timer_sync); + #endif +@@ -1409,11 +1402,15 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head) + raw_spin_unlock(&base->lock); + call_timer_fn(timer, fn); + base->running_timer = NULL; ++ spin_unlock(&base->expiry_lock); ++ spin_lock(&base->expiry_lock); + raw_spin_lock(&base->lock); + } else { + raw_spin_unlock_irq(&base->lock); + call_timer_fn(timer, fn); + base->running_timer = NULL; ++ spin_unlock(&base->expiry_lock); ++ spin_lock(&base->expiry_lock); + raw_spin_lock_irq(&base->lock); + } + } +@@ -1717,6 +1714,7 @@ static inline void __run_timers(struct timer_base *base) + if (!time_after_eq(jiffies, base->clk)) + return; + ++ spin_lock(&base->expiry_lock); + raw_spin_lock_irq(&base->lock); + + /* +@@ -1744,7 +1742,7 @@ static inline void __run_timers(struct timer_base *base) + expire_timers(base, heads + levels); + } + raw_spin_unlock_irq(&base->lock); +- wakeup_timer_waiters(base); ++ spin_unlock(&base->expiry_lock); + } + + /* +@@ -1991,9 +1989,7 @@ static void __init init_timer_cpu(int cpu) + base->cpu = cpu; + raw_spin_lock_init(&base->lock); + base->clk = jiffies; +-#ifdef CONFIG_PREEMPT_RT_FULL +- init_swait_queue_head(&base->wait_for_running_timer); +-#endif ++ spin_lock_init(&base->expiry_lock); + } + } + +-- +2.17.1 + diff --git a/debian/patches-rt/0272-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch b/debian/patches-rt/0272-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch index 45311289e..d7d1b462b 100644 --- a/debian/patches-rt/0272-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch +++ b/debian/patches-rt/0272-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch @@ -1,12 +1,12 @@ -From 238295e1edf9f6aba72d570e8afee2ecec56a1fc Mon Sep 17 00:00:00 2001 -Message-Id: <238295e1edf9f6aba72d570e8afee2ecec56a1fc.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From eedeea14e5093454e68765d1af0a558b35ea5aa5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:13 +0200 -Subject: [PATCH 272/329] Revert "futex: Ensure lock/unlock symetry versus +Subject: [PATCH 272/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 6a773b70cf105b46298ed3b44e77c102ce31d9ec ] diff --git a/debian/patches-rt/0273-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch b/debian/patches-rt/0273-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch index de4d9f2d1..54518ec34 100644 --- a/debian/patches-rt/0273-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch +++ b/debian/patches-rt/0273-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch @@ -1,12 +1,12 @@ -From ec233e4cdfa4650c3fe7354d1c4bb3e0917a5adc Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 94f67085f95630af30726edb3a6351aa2497d995 Mon Sep 17 00:00:00 2001 +Message-Id: <94f67085f95630af30726edb3a6351aa2497d995.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:18 +0200 -Subject: [PATCH 273/329] Revert "futex: Fix bug on when a requeued RT task +Subject: [PATCH 273/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit f1a170cb3289a48df26cae3c60d77608f7a988bb ] diff --git a/debian/patches-rt/0274-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch b/debian/patches-rt/0274-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch index eb06ca485..de8f6913b 100644 --- a/debian/patches-rt/0274-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch +++ b/debian/patches-rt/0274-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch @@ -1,12 +1,12 @@ -From 874b31bc115070b4ba01c5f28b9625cf48df4b84 Mon Sep 17 00:00:00 2001 -Message-Id: <874b31bc115070b4ba01c5f28b9625cf48df4b84.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e7318b6d510c5aa1ff1104855a59e68e3b9ceb49 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:21 +0200 -Subject: [PATCH 274/329] Revert "rtmutex: Handle the various new futex race +Subject: [PATCH 274/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 9e0265c21af4d6388d47dcd5ce20f76ec3a2e468 ] diff --git a/debian/patches-rt/0275-Revert-futex-workaround-migrate_disable-enable-in-di.patch b/debian/patches-rt/0275-Revert-futex-workaround-migrate_disable-enable-in-di.patch index 3f89abfa7..a95ed10c4 100644 --- a/debian/patches-rt/0275-Revert-futex-workaround-migrate_disable-enable-in-di.patch +++ b/debian/patches-rt/0275-Revert-futex-workaround-migrate_disable-enable-in-di.patch @@ -1,12 +1,12 @@ -From 531431494e1213abbd6a92a48b448fdd3df28433 Mon Sep 17 00:00:00 2001 -Message-Id: <531431494e1213abbd6a92a48b448fdd3df28433.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d90aaa0388b133d510b0f4c2a2cbc62a2201cdb0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:27 +0200 -Subject: [PATCH 275/329] Revert "futex: workaround migrate_disable/enable in +Subject: [PATCH 275/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit a71221d81cc4873891ae44f3aa02df596079b786 ] diff --git a/debian/patches-rt/0276-futex-Make-the-futex_hash_bucket-lock-raw.patch b/debian/patches-rt/0276-futex-Make-the-futex_hash_bucket-lock-raw.patch index a08a6db63..6b3ea1b2f 100644 --- a/debian/patches-rt/0276-futex-Make-the-futex_hash_bucket-lock-raw.patch +++ b/debian/patches-rt/0276-futex-Make-the-futex_hash_bucket-lock-raw.patch @@ -1,11 +1,11 @@ -From ad8b2825cc455ee16207c3fa6d9ed361b6abb69b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f39fa87dcab83d6422f07fd00eac53449b93caf1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 11:59:44 +0200 -Subject: [PATCH 276/329] futex: Make the futex_hash_bucket lock raw -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 276/333] futex: Make the futex_hash_bucket lock raw +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit f646521aadedab78801c9befe193e2e8a0c99298 ] diff --git a/debian/patches-rt/0277-futex-Delay-deallocation-of-pi_state.patch b/debian/patches-rt/0277-futex-Delay-deallocation-of-pi_state.patch index 4865ce6bd..7c280d646 100644 --- a/debian/patches-rt/0277-futex-Delay-deallocation-of-pi_state.patch +++ b/debian/patches-rt/0277-futex-Delay-deallocation-of-pi_state.patch @@ -1,11 +1,11 @@ -From be64455cbe25f39319588bbcd8a3807a9c3041cd Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2e8ff8693e0aae91a226f0dc09cd2f98d774f97b Mon Sep 17 00:00:00 2001 +Message-Id: <2e8ff8693e0aae91a226f0dc09cd2f98d774f97b.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Jun 2019 13:35:36 +0200 -Subject: [PATCH 277/329] futex: Delay deallocation of pi_state -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 277/333] futex: Delay deallocation of pi_state +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit d7c7cf8cb68b7df17e6e50be1f25f35d83e686c7 ] diff --git a/debian/patches-rt/0278-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch b/debian/patches-rt/0278-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch index 56c04c1ce..25a5b00cd 100644 --- a/debian/patches-rt/0278-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch +++ b/debian/patches-rt/0278-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch @@ -1,12 +1,12 @@ -From 50d889cc089b60e7b0e3074cc4aba0c34edad9e8 Mon Sep 17 00:00:00 2001 -Message-Id: <50d889cc089b60e7b0e3074cc4aba0c34edad9e8.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 10065059708399e3689a1a075b34ec10f04dee1a Mon Sep 17 00:00:00 2001 +Message-Id: <10065059708399e3689a1a075b34ec10f04dee1a.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Luis Claudio R. Goncalves" Date: Tue, 25 Jun 2019 11:28:04 -0300 -Subject: [PATCH 278/329] mm/zswap: Do not disable preemption in +Subject: [PATCH 278/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 4e4cf4be79635e67144632d9135286381acbc95a ] diff --git a/debian/patches-rt/0279-revert-aio.patch b/debian/patches-rt/0279-revert-aio.patch index 3fd23267c..bd860dc3f 100644 --- a/debian/patches-rt/0279-revert-aio.patch +++ b/debian/patches-rt/0279-revert-aio.patch @@ -1,11 +1,11 @@ -From ecfc93f81c64db7dd6a1afc3ca455826dc3da90c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 06297220e2f3a96af5ef217dfbbb4aaaac233c15 Mon Sep 17 00:00:00 2001 +Message-Id: <06297220e2f3a96af5ef217dfbbb4aaaac233c15.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 -Subject: [PATCH 279/329] revert-aio -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 279/333] revert-aio +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz revert: fs/aio: simple simple work diff --git a/debian/patches-rt/0280-fs-aio-simple-simple-work.patch b/debian/patches-rt/0280-fs-aio-simple-simple-work.patch index ec83cc412..2406ae48b 100644 --- a/debian/patches-rt/0280-fs-aio-simple-simple-work.patch +++ b/debian/patches-rt/0280-fs-aio-simple-simple-work.patch @@ -1,11 +1,11 @@ -From cfe97d98afc97b52fdf8b31f2533822c43cb7d99 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 03eed771e0b1bf6b0f3a273801134822ff725772 Mon Sep 17 00:00:00 2001 +Message-Id: <03eed771e0b1bf6b0f3a273801134822ff725772.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 -Subject: [PATCH 280/329] fs/aio: simple simple work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 280/333] fs/aio: simple simple work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 1a142116f6435ef070ecebb66d2d599507c10601 ] diff --git a/debian/patches-rt/0281-revert-thermal.patch b/debian/patches-rt/0281-revert-thermal.patch index 3f678bcb9..17cb9b4b6 100644 --- a/debian/patches-rt/0281-revert-thermal.patch +++ b/debian/patches-rt/0281-revert-thermal.patch @@ -1,11 +1,11 @@ -From 827e824dc6fb2dc5565ce71889e5b536bf0bcef5 Mon Sep 17 00:00:00 2001 -Message-Id: <827e824dc6fb2dc5565ce71889e5b536bf0bcef5.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From b66f9d389cf8c54afa6448867fb7cecc50c70e97 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 -Subject: [PATCH 281/329] revert-thermal -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 281/333] revert-thermal +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Revert: thermal: Defer thermal wakups to threads diff --git a/debian/patches-rt/0282-thermal-Defer-thermal-wakups-to-threads.patch b/debian/patches-rt/0282-thermal-Defer-thermal-wakups-to-threads.patch index 56871fc0a..f674dbe91 100644 --- a/debian/patches-rt/0282-thermal-Defer-thermal-wakups-to-threads.patch +++ b/debian/patches-rt/0282-thermal-Defer-thermal-wakups-to-threads.patch @@ -1,11 +1,11 @@ -From 4d078a228363c14bf55bf35f93a8a792e934e2d5 Mon Sep 17 00:00:00 2001 -Message-Id: <4d078a228363c14bf55bf35f93a8a792e934e2d5.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From dbbd35b51018e3e2e9c0fcca57380c7cbeb59843 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 -Subject: [PATCH 282/329] thermal: Defer thermal wakups to threads -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 282/333] thermal: Defer thermal wakups to threads +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit ad2408dc248fe58536eef5b2b5734d8f9d3a280b ] diff --git a/debian/patches-rt/0283-revert-block.patch b/debian/patches-rt/0283-revert-block.patch index c8c381bc2..d973c6b28 100644 --- a/debian/patches-rt/0283-revert-block.patch +++ b/debian/patches-rt/0283-revert-block.patch @@ -1,11 +1,11 @@ -From 8f06e654ed2fb162be1139cc81a0ad83d93d5e4c Mon Sep 17 00:00:00 2001 -Message-Id: <8f06e654ed2fb162be1139cc81a0ad83d93d5e4c.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8170b6ed7b032659167e08dde994bbb64b776951 Mon Sep 17 00:00:00 2001 +Message-Id: <8170b6ed7b032659167e08dde994bbb64b776951.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:54 -0400 -Subject: [PATCH 283/329] revert-block -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 283/333] revert-block +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Revert swork version of: block: blk-mq: move blk_queue_usage_counter_release() into process context diff --git a/debian/patches-rt/0284-block-blk-mq-move-blk_queue_usage_counter_release-in.patch b/debian/patches-rt/0284-block-blk-mq-move-blk_queue_usage_counter_release-in.patch index 2768e92fd..8a1819053 100644 --- a/debian/patches-rt/0284-block-blk-mq-move-blk_queue_usage_counter_release-in.patch +++ b/debian/patches-rt/0284-block-blk-mq-move-blk_queue_usage_counter_release-in.patch @@ -1,12 +1,12 @@ -From b0fdee1cb6e573830e4d6b87aa23beaa4e011be6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 4a3bf71bc48df0c126b5fc02dc369a20c328cea2 Mon Sep 17 00:00:00 2001 +Message-Id: <4a3bf71bc48df0c126b5fc02dc369a20c328cea2.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 -Subject: [PATCH 284/329] block: blk-mq: move blk_queue_usage_counter_release() +Subject: [PATCH 284/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 61c928ecf4fe200bda9b49a0813b5ba0f43995b5 ] diff --git a/debian/patches-rt/0285-workqueue-rework.patch b/debian/patches-rt/0285-workqueue-rework.patch index f02b7ef9a..c9f52ad64 100644 --- a/debian/patches-rt/0285-workqueue-rework.patch +++ b/debian/patches-rt/0285-workqueue-rework.patch @@ -1,11 +1,11 @@ -From c299ecfceaecc3c8f2f73a87329f827d35bd675d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 560b964b74c268f15f5e9034a288df7cb80f0c7e Mon Sep 17 00:00:00 2001 +Message-Id: <560b964b74c268f15f5e9034a288df7cb80f0c7e.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 May 2019 18:52:27 +0200 -Subject: [PATCH 285/329] workqueue: rework -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 285/333] workqueue: rework +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit d15a862f24df983458533aebd6fa207ecdd1095a ] @@ -69,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 ec7442545b84..728681a20b7f 100644 +index 5f07061c4087..da68c42aed68 100644 --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -70,7 +70,7 @@ @@ -324,7 +324,7 @@ index 7b173ca08e22..2180c6388eb9 100644 init_mm_internals(); diff --git a/kernel/kthread.c b/kernel/kthread.c -index 9db017761a1f..5641b55783a6 100644 +index 42294c806ad0..81aa14daa5fe 100644 --- a/kernel/kthread.c +++ b/kernel/kthread.c @@ -20,7 +20,6 @@ @@ -335,7 +335,7 @@ index 9db017761a1f..5641b55783a6 100644 #include static DEFINE_SPINLOCK(kthread_create_lock); -@@ -1181,19 +1180,6 @@ void kthread_destroy_worker(struct kthread_worker *worker) +@@ -1194,19 +1193,6 @@ void kthread_destroy_worker(struct kthread_worker *worker) } EXPORT_SYMBOL(kthread_destroy_worker); diff --git a/debian/patches-rt/0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch b/debian/patches-rt/0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch index f3205a25d..dd031a3b3 100644 --- a/debian/patches-rt/0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch +++ b/debian/patches-rt/0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch @@ -1,11 +1,11 @@ -From a5b3c13b8b07661c1ab1ae30a568f361272e4145 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 7addf401f0a94341ae5c02a36e5a14b4bde53e28 Mon Sep 17 00:00:00 2001 +Message-Id: <7addf401f0a94341ae5c02a36e5a14b4bde53e28.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:12 +0200 -Subject: [PATCH 286/329] i2c: exynos5: Remove IRQF_ONESHOT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 286/333] i2c: exynos5: Remove IRQF_ONESHOT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 4b217df0ab3f7910c96e42091cc7d9f221d05f01 ] diff --git a/debian/patches-rt/0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch b/debian/patches-rt/0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch index 92945b1fc..4f3ffcc02 100644 --- a/debian/patches-rt/0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch +++ b/debian/patches-rt/0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch @@ -1,11 +1,11 @@ -From 5df2eda24988ceace781372da79730c8bbe39808 Mon Sep 17 00:00:00 2001 -Message-Id: <5df2eda24988ceace781372da79730c8bbe39808.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 59460f475358984f7cb7a5b1aa906373834950d7 Mon Sep 17 00:00:00 2001 +Message-Id: <59460f475358984f7cb7a5b1aa906373834950d7.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:37 +0200 -Subject: [PATCH 287/329] i2c: hix5hd2: Remove IRQF_ONESHOT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 287/333] i2c: hix5hd2: Remove IRQF_ONESHOT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit e88b481f3f86f11e3243e0808a830e5ca5782a9d ] diff --git a/debian/patches-rt/0288-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch b/debian/patches-rt/0288-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch index 21f6d77b5..3aaa64488 100644 --- a/debian/patches-rt/0288-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch +++ b/debian/patches-rt/0288-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch @@ -1,12 +1,12 @@ -From b01de7d61b20c86fad00d89bd7a5505f546a5dcc Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From fce08853223f11638c0de30e8c4b30aa6b4bf16b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Juri Lelli Date: Wed, 31 Jul 2019 12:37:15 +0200 -Subject: [PATCH 288/329] sched/deadline: Ensure inactive_timer runs in hardirq +Subject: [PATCH 288/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit ba94e7aed7405c58251b1380e6e7d73aa8284b41 ] diff --git a/debian/patches-rt/0289-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch b/debian/patches-rt/0289-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch index 51a958e2d..0a87a88b6 100644 --- a/debian/patches-rt/0289-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch +++ b/debian/patches-rt/0289-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch @@ -1,12 +1,12 @@ -From 220a9e0e5624b02be7ffbb9bd0db1812d5841417 Mon Sep 17 00:00:00 2001 -Message-Id: <220a9e0e5624b02be7ffbb9bd0db1812d5841417.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ae31fd9a0273879286664d3eefb41c9feefc489f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Clark Williams Date: Mon, 15 Jul 2019 15:25:00 -0500 -Subject: [PATCH 289/329] thermal/x86_pkg_temp: make pkg_temp_lock a raw +Subject: [PATCH 289/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 8b03bb3ea7861b70b506199a69b1c8f81fe2d4d0 ] diff --git a/debian/patches-rt/0290-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch b/debian/patches-rt/0290-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch index c0b09c969..b6cf8c142 100644 --- a/debian/patches-rt/0290-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch +++ b/debian/patches-rt/0290-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch @@ -1,11 +1,11 @@ -From c29a897e88337a1bdb5c51e37c00006bc25b9fb8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1d4e4dbe619d31405289663c27b8a12541634254 Mon Sep 17 00:00:00 2001 +Message-Id: <1d4e4dbe619d31405289663c27b8a12541634254.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 16:38:43 +0200 -Subject: [PATCH 290/329] dma-buf: Use seqlock_t instread disabling preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 290/333] dma-buf: Use seqlock_t instread disabling preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 240610aa31094f51f299f06eb8dae8d4cd8d4500 ] diff --git a/debian/patches-rt/0291-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch b/debian/patches-rt/0291-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch index 4c287b436..42863d5cb 100644 --- a/debian/patches-rt/0291-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch +++ b/debian/patches-rt/0291-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch @@ -1,12 +1,12 @@ -From cfc38e9c7db1a17a4542c4b10acbc963225db908 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 97c83f2f80ecd70655a5b4f74684b43863b28cec Mon Sep 17 00:00:00 2001 +Message-Id: <97c83f2f80ecd70655a5b4f74684b43863b28cec.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Aug 2019 14:29:41 +0200 -Subject: [PATCH 291/329] KVM: arm/arm64: Let the timer expire in hardirq +Subject: [PATCH 291/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 719cc080c914045a6e35787bf4dc3ba91cfd3efb ] diff --git a/debian/patches-rt/0292-x86-preempt-Check-preemption-level-before-looking-at.patch b/debian/patches-rt/0292-x86-preempt-Check-preemption-level-before-looking-at.patch index 66c45aa47..d726b2b28 100644 --- a/debian/patches-rt/0292-x86-preempt-Check-preemption-level-before-looking-at.patch +++ b/debian/patches-rt/0292-x86-preempt-Check-preemption-level-before-looking-at.patch @@ -1,12 +1,12 @@ -From a3e7fef6c2dbb2a0819df49bf67439311afc5316 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a769390470af537f5781ae96582fa77182b00317 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 17:08:58 +0200 -Subject: [PATCH 292/329] x86: preempt: Check preemption level before looking +Subject: [PATCH 292/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 19fc8557f2323c52b26561651ed4d51fc688a740 ] diff --git a/debian/patches-rt/0293-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch b/debian/patches-rt/0293-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch index 4872cb8c4..79e6c254c 100644 --- a/debian/patches-rt/0293-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch +++ b/debian/patches-rt/0293-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch @@ -1,12 +1,12 @@ -From 6c5cfa0b2bf6c2aee38e6fe0d3ea198eeda6332f Mon Sep 17 00:00:00 2001 -Message-Id: <6c5cfa0b2bf6c2aee38e6fe0d3ea198eeda6332f.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ad58f79c6be0b5f5f87e3091df879ade06578e8f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:07 +0100 -Subject: [PATCH 293/329] hrtimer: Use READ_ONCE to access timer->base in +Subject: [PATCH 293/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 2c8fdbe7ef0ad06c1a326886c5954e117b5657d6 ] diff --git a/debian/patches-rt/0294-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch b/debian/patches-rt/0294-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch index c0e59e91e..aa46961da 100644 --- a/debian/patches-rt/0294-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch +++ b/debian/patches-rt/0294-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch @@ -1,12 +1,12 @@ -From bae02b374cefc85b456d4f78b380baf045d8cb44 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 228bd179f1d21fab82184d6c9f48b0e04f79ed91 Mon Sep 17 00:00:00 2001 +Message-Id: <228bd179f1d21fab82184d6c9f48b0e04f79ed91.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:08 +0100 -Subject: [PATCH 294/329] hrtimer: Don't grab the expiry lock for non-soft +Subject: [PATCH 294/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit fd420354bea2f57c11f3de191dffdeea76531e76 ] diff --git a/debian/patches-rt/0295-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch b/debian/patches-rt/0295-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch index 937da7f3d..6eee15464 100644 --- a/debian/patches-rt/0295-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch +++ b/debian/patches-rt/0295-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch @@ -1,12 +1,12 @@ -From a2596b6ffdfe09b8fe9acdf939d4d52a56c0d8f8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From abcf00b506c386ae4586c56bd731324a2b44a4e4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:09 +0100 -Subject: [PATCH 295/329] hrtimer: Prevent using hrtimer_grab_expiry_lock() on +Subject: [PATCH 295/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit cef1b87f98823af923a386f3f69149acb212d4a1 ] diff --git a/debian/patches-rt/0296-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch b/debian/patches-rt/0296-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch index 572447835..1b6fbe8e7 100644 --- a/debian/patches-rt/0296-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch +++ b/debian/patches-rt/0296-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch @@ -1,12 +1,12 @@ -From 95c322dc50246713694a3901e2e8a23886c68e85 Mon Sep 17 00:00:00 2001 -Message-Id: <95c322dc50246713694a3901e2e8a23886c68e85.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 865d38f0b21223b24dbaaa1f788e290b7ae89f9b Mon Sep 17 00:00:00 2001 +Message-Id: <865d38f0b21223b24dbaaa1f788e290b7ae89f9b.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Sep 2019 16:55:27 +0200 -Subject: [PATCH 296/329] hrtimer: Add a missing bracket and hide +Subject: [PATCH 296/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 47b6de0b7f22c28b40275aeede3993d807668c3b ] diff --git a/debian/patches-rt/0297-posix-timers-Unlock-expiry-lock-in-the-early-return.patch b/debian/patches-rt/0297-posix-timers-Unlock-expiry-lock-in-the-early-return.patch index 70e6191a2..90e70de7a 100644 --- a/debian/patches-rt/0297-posix-timers-Unlock-expiry-lock-in-the-early-return.patch +++ b/debian/patches-rt/0297-posix-timers-Unlock-expiry-lock-in-the-early-return.patch @@ -1,11 +1,11 @@ -From cd3d3f85e82d6ce73b27aee9a55556bed8003e2d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From e5bbfd8e0ccc67a4e1cdc573ef377879824a7c80 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Sep 2019 12:33:59 +0200 -Subject: [PATCH 297/329] 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.135-rt60.tar.xz +Subject: [PATCH 297/333] 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.142-rt63.tar.xz [ Upstream commit 356a2781375ec58521a9bc3f500488745990c242 ] diff --git a/debian/patches-rt/0298-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch b/debian/patches-rt/0298-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch index 45f073d8d..2846901a5 100644 --- a/debian/patches-rt/0298-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch +++ b/debian/patches-rt/0298-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch @@ -1,15 +1,15 @@ -From 0ad2bb6569107bdd69298922a9beb905f629637d Mon Sep 17 00:00:00 2001 -Message-Id: <0ad2bb6569107bdd69298922a9beb905f629637d.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5adb1f85d03142ce26c30d99528ec040af27d8a8 Mon Sep 17 00:00:00 2001 +Message-Id: <5adb1f85d03142ce26c30d99528ec040af27d8a8.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Tue, 24 Sep 2019 14:36:41 +0200 -Subject: [PATCH 298/329] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= +Subject: [PATCH 298/333] =?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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 4230dd3824c3e1785504e6f757ce79a4b55651fa ] diff --git a/debian/patches-rt/0299-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch b/debian/patches-rt/0299-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch index 566735f47..b0dac69e6 100644 --- a/debian/patches-rt/0299-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch +++ b/debian/patches-rt/0299-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch @@ -1,12 +1,12 @@ -From 0635a14374a6d7f32aeca74959baf1f0062b06d9 Mon Sep 17 00:00:00 2001 -Message-Id: <0635a14374a6d7f32aeca74959baf1f0062b06d9.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From a94c041c328f00ac87354afd9d584cb8a967d86c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:32 -0500 -Subject: [PATCH 299/329] sched: __set_cpus_allowed_ptr: Check cpus_mask, not +Subject: [PATCH 299/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit e5606fb7b042db634ed62b4dd733d62e050e468f ] diff --git a/debian/patches-rt/0300-sched-Remove-dead-__migrate_disabled-check.patch b/debian/patches-rt/0300-sched-Remove-dead-__migrate_disabled-check.patch index b16915286..e068e022b 100644 --- a/debian/patches-rt/0300-sched-Remove-dead-__migrate_disabled-check.patch +++ b/debian/patches-rt/0300-sched-Remove-dead-__migrate_disabled-check.patch @@ -1,11 +1,11 @@ -From 80c7dc1ac20f64951c4b5590b65b0db2a5b20880 Mon Sep 17 00:00:00 2001 -Message-Id: <80c7dc1ac20f64951c4b5590b65b0db2a5b20880.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f87bed33e138726ebee9b6200840ffdd912bbf97 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:33 -0500 -Subject: [PATCH 300/329] sched: Remove dead __migrate_disabled() check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 300/333] sched: Remove dead __migrate_disabled() check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 14d9272d534ea91262e15db99443fc5995c7c016 ] diff --git a/debian/patches-rt/0301-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch b/debian/patches-rt/0301-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch index f4a6ce140..6961e821e 100644 --- a/debian/patches-rt/0301-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch +++ b/debian/patches-rt/0301-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch @@ -1,11 +1,11 @@ -From ae143b3d8ef01a023b736cd5c959b3c6ec78c362 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From bcf69cd6fee09f02b6e8bd38b1850090298a5e73 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:34 -0500 -Subject: [PATCH 301/329] sched: migrate disable: Protect cpus_ptr with lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 301/333] sched: migrate disable: Protect cpus_ptr with lock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 27ee52a891ed2c7e2e2c8332ccae0de7c2674b09 ] diff --git a/debian/patches-rt/0302-lib-smp_processor_id-Don-t-use-cpumask_equal.patch b/debian/patches-rt/0302-lib-smp_processor_id-Don-t-use-cpumask_equal.patch index 4f7cdac76..4c90bc532 100644 --- a/debian/patches-rt/0302-lib-smp_processor_id-Don-t-use-cpumask_equal.patch +++ b/debian/patches-rt/0302-lib-smp_processor_id-Don-t-use-cpumask_equal.patch @@ -1,11 +1,11 @@ -From c9bb6d07b4c6dd5039684c55f1d7d0689e754e88 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 8fcb1e2d5ce403604b7c103763665a345fcaa5a9 Mon Sep 17 00:00:00 2001 +Message-Id: <8fcb1e2d5ce403604b7c103763665a345fcaa5a9.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Waiman Long Date: Thu, 3 Oct 2019 16:36:08 -0400 -Subject: [PATCH 302/329] 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.135-rt60.tar.xz +Subject: [PATCH 302/333] 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.142-rt63.tar.xz [ Upstream commit 659252061477862f45b79e1de169e6030f5c8918 ] diff --git a/debian/patches-rt/0303-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch b/debian/patches-rt/0303-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch index 71dc74199..141df485e 100644 --- a/debian/patches-rt/0303-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch +++ b/debian/patches-rt/0303-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch @@ -1,12 +1,12 @@ -From 94d05b44a1358e4c36ebeb94f70e92c96fee93c2 Mon Sep 17 00:00:00 2001 -Message-Id: <94d05b44a1358e4c36ebeb94f70e92c96fee93c2.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 77ad48e7eab231be14e87055b17a9682dcc17e51 Mon Sep 17 00:00:00 2001 +Message-Id: <77ad48e7eab231be14e87055b17a9682dcc17e51.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 7 Oct 2019 16:45:18 +0200 -Subject: [PATCH 303/329] futex: Make the futex_hash_bucket spinlock_t again +Subject: [PATCH 303/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 954ad80c23edfe71f4e8ce70b961eac884320c3a ] diff --git a/debian/patches-rt/0304-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch b/debian/patches-rt/0304-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch index cd56fbdf3..6a4fba429 100644 --- a/debian/patches-rt/0304-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch +++ b/debian/patches-rt/0304-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch @@ -1,12 +1,12 @@ -From b25448c96680e78daea8fa6f29c51dde80b7652b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 79966d337c17b8e63e32463bb34cb64402a95d11 Mon Sep 17 00:00:00 2001 +Message-Id: <79966d337c17b8e63e32463bb34cb64402a95d11.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 30 Sep 2019 18:15:44 +0200 -Subject: [PATCH 304/329] locking/rtmutex: Clean ->pi_blocked_on in the error +Subject: [PATCH 304/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 0be4ea6e3ce693101be0fbd55a0cc7ce238ab2eb ] diff --git a/debian/patches-rt/0305-lib-ubsan-Don-t-seralize-UBSAN-report.patch b/debian/patches-rt/0305-lib-ubsan-Don-t-seralize-UBSAN-report.patch index 6722d4b22..e3558bf95 100644 --- a/debian/patches-rt/0305-lib-ubsan-Don-t-seralize-UBSAN-report.patch +++ b/debian/patches-rt/0305-lib-ubsan-Don-t-seralize-UBSAN-report.patch @@ -1,11 +1,11 @@ -From c1ae4b6599bc5dbcae80dc79e16f5e409be3d901 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1c01975c971f72cf7587343901eb3d2838bcccfe Mon Sep 17 00:00:00 2001 +Message-Id: <1c01975c971f72cf7587343901eb3d2838bcccfe.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Julien Grall Date: Fri, 20 Sep 2019 11:08:35 +0100 -Subject: [PATCH 305/329] lib/ubsan: Don't seralize UBSAN report -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 305/333] lib/ubsan: Don't seralize UBSAN report +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 4702c28ac777b27acb499cbd5e8e787ce1a7d82d ] diff --git a/debian/patches-rt/0306-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch b/debian/patches-rt/0306-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch index 8084b0ad1..1f0884e34 100644 --- a/debian/patches-rt/0306-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch +++ b/debian/patches-rt/0306-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch @@ -1,12 +1,12 @@ -From 4c11da463b4e3bbc6b6cfffefdae8e856de7175e Mon Sep 17 00:00:00 2001 -Message-Id: <4c11da463b4e3bbc6b6cfffefdae8e856de7175e.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 49fd147d17128bb6af673255fbc0ae9d08b42898 Mon Sep 17 00:00:00 2001 +Message-Id: <49fd147d17128bb6af673255fbc0ae9d08b42898.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Liu Haitao Date: Fri, 27 Sep 2019 16:22:30 +0800 -Subject: [PATCH 306/329] kmemleak: Change the lock of kmemleak_object to +Subject: [PATCH 306/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 217847f57119b5fdd377bfa3d344613ddb98d9fc ] diff --git a/debian/patches-rt/0307-sched-migrate_enable-Use-select_fallback_rq.patch b/debian/patches-rt/0307-sched-migrate_enable-Use-select_fallback_rq.patch index a70632d17..e5f72b741 100644 --- a/debian/patches-rt/0307-sched-migrate_enable-Use-select_fallback_rq.patch +++ b/debian/patches-rt/0307-sched-migrate_enable-Use-select_fallback_rq.patch @@ -1,11 +1,11 @@ -From 982b58008d818a65ebb1aec041f55448f0a25074 Mon Sep 17 00:00:00 2001 -Message-Id: <982b58008d818a65ebb1aec041f55448f0a25074.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 6cc7c9c902726655ee7844aba14a3fb1cb3f8889 Mon Sep 17 00:00:00 2001 +Message-Id: <6cc7c9c902726655ee7844aba14a3fb1cb3f8889.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:12 -0500 -Subject: [PATCH 307/329] sched: migrate_enable: Use select_fallback_rq() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 307/333] sched: migrate_enable: Use select_fallback_rq() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit adfa969d4cfcc995a9d866020124e50f1827d2d1 ] diff --git a/debian/patches-rt/0308-sched-Lazy-migrate_disable-processing.patch b/debian/patches-rt/0308-sched-Lazy-migrate_disable-processing.patch index 79f23734f..1559ffc40 100644 --- a/debian/patches-rt/0308-sched-Lazy-migrate_disable-processing.patch +++ b/debian/patches-rt/0308-sched-Lazy-migrate_disable-processing.patch @@ -1,11 +1,11 @@ -From ffad6ee3464e615d4a7df13467c6082f5feca3b6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2b70dfb45684c91bd0f9089ddc4a79750f5a3ed3 Mon Sep 17 00:00:00 2001 +Message-Id: <2b70dfb45684c91bd0f9089ddc4a79750f5a3ed3.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:13 -0500 -Subject: [PATCH 308/329] sched: Lazy migrate_disable processing -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 308/333] sched: Lazy migrate_disable processing +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 425c5b38779a860062aa62219dc920d374b13c17 ] diff --git a/debian/patches-rt/0309-sched-migrate_enable-Use-stop_one_cpu_nowait.patch b/debian/patches-rt/0309-sched-migrate_enable-Use-stop_one_cpu_nowait.patch index 4681f5e7a..a0ac5c0fa 100644 --- a/debian/patches-rt/0309-sched-migrate_enable-Use-stop_one_cpu_nowait.patch +++ b/debian/patches-rt/0309-sched-migrate_enable-Use-stop_one_cpu_nowait.patch @@ -1,11 +1,11 @@ -From 3f33033a2b5811104fb7eb031ec18c15b71b6485 Mon Sep 17 00:00:00 2001 -Message-Id: <3f33033a2b5811104fb7eb031ec18c15b71b6485.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 3fee95997b9c1ef0ff2c58ac38954f073e42ac2b Mon Sep 17 00:00:00 2001 +Message-Id: <3fee95997b9c1ef0ff2c58ac38954f073e42ac2b.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:14 -0500 -Subject: [PATCH 309/329] sched: migrate_enable: Use stop_one_cpu_nowait() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 309/333] sched: migrate_enable: Use stop_one_cpu_nowait() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 6b39a1fa8c53cae08dc03afdae193b7d3a78a173 ] diff --git a/debian/patches-rt/0310-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch b/debian/patches-rt/0310-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch index ecbec9f1b..f5de0013a 100644 --- a/debian/patches-rt/0310-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch +++ b/debian/patches-rt/0310-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch @@ -1,12 +1,12 @@ -From 9b3236a5554beebe5de6c21cda4f225b289b8fd1 Mon Sep 17 00:00:00 2001 -Message-Id: <9b3236a5554beebe5de6c21cda4f225b289b8fd1.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 955ff233de51e2345514c979558fd2ea4251b8b3 Mon Sep 17 00:00:00 2001 +Message-Id: <955ff233de51e2345514c979558fd2ea4251b8b3.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 18 Oct 2019 13:04:15 +0200 -Subject: [PATCH 310/329] Revert "ARM: Initialize split page table locks for +Subject: [PATCH 310/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 247074c44d8c3e619dfde6404a52295d8d671d38 ] diff --git a/debian/patches-rt/0311-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch b/debian/patches-rt/0311-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch index 44ea563bd..91e84f888 100644 --- a/debian/patches-rt/0311-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch +++ b/debian/patches-rt/0311-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch @@ -1,12 +1,12 @@ -From b47230da29518bb738c585cc695cea8aaf2c7d9d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 14be2f4fd499ec8f935d2eff1b1a88939f7b69fa Mon Sep 17 00:00:00 2001 +Message-Id: <14be2f4fd499ec8f935d2eff1b1a88939f7b69fa.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Nov 2019 09:25:04 +0100 -Subject: [PATCH 311/329] locking: Make spinlock_t and rwlock_t a RCU section +Subject: [PATCH 311/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 84440022a0e1c8c936d61f8f97593674a295d409 ] diff --git a/debian/patches-rt/0312-sched-core-migrate_enable-must-access-takedown_cpu_t.patch b/debian/patches-rt/0312-sched-core-migrate_enable-must-access-takedown_cpu_t.patch index cfdfb6c89..7e22ffc37 100644 --- a/debian/patches-rt/0312-sched-core-migrate_enable-must-access-takedown_cpu_t.patch +++ b/debian/patches-rt/0312-sched-core-migrate_enable-must-access-takedown_cpu_t.patch @@ -1,12 +1,12 @@ -From 534b0ff2eae518304d125c3f0076f11807576eec Mon Sep 17 00:00:00 2001 -Message-Id: <534b0ff2eae518304d125c3f0076f11807576eec.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 987a27d0b26e7ad8c980992ff957a607055e0e89 Mon Sep 17 00:00:00 2001 +Message-Id: <987a27d0b26e7ad8c980992ff957a607055e0e89.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 29 Nov 2019 17:24:55 +0100 -Subject: [PATCH 312/329] sched/core: migrate_enable() must access +Subject: [PATCH 312/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit a61d1977f692e46bad99a100f264981ba08cb4bd ] diff --git a/debian/patches-rt/0313-lib-smp_processor_id-Adjust-check_preemption_disable.patch b/debian/patches-rt/0313-lib-smp_processor_id-Adjust-check_preemption_disable.patch index 5ef17848e..ee5429e28 100644 --- a/debian/patches-rt/0313-lib-smp_processor_id-Adjust-check_preemption_disable.patch +++ b/debian/patches-rt/0313-lib-smp_processor_id-Adjust-check_preemption_disable.patch @@ -1,12 +1,12 @@ -From 828eac8d8bfdf4a596da67680c29e5477b6557b5 Mon Sep 17 00:00:00 2001 -Message-Id: <828eac8d8bfdf4a596da67680c29e5477b6557b5.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5da2c8f11e89601eea38cb9f3302f930c60806e7 Mon Sep 17 00:00:00 2001 +Message-Id: <5da2c8f11e89601eea38cb9f3302f930c60806e7.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Daniel Wagner Date: Mon, 16 Dec 2019 16:15:57 +0100 -Subject: [PATCH 313/329] lib/smp_processor_id: Adjust +Subject: [PATCH 313/333] lib/smp_processor_id: Adjust check_preemption_disabled() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit af3c1c5fdf177870fb5e6e16b24e374696ab28f5 ] diff --git a/debian/patches-rt/0314-sched-migrate_enable-Busy-loop-until-the-migration-r.patch b/debian/patches-rt/0314-sched-migrate_enable-Busy-loop-until-the-migration-r.patch index 99a4859ec..446698826 100644 --- a/debian/patches-rt/0314-sched-migrate_enable-Busy-loop-until-the-migration-r.patch +++ b/debian/patches-rt/0314-sched-migrate_enable-Busy-loop-until-the-migration-r.patch @@ -1,12 +1,12 @@ -From e5b5609c5e20caa3855d7d984bbde3981cb40280 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f18664825ba891cf54d1b2df85b0661f25cdccb9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Dec 2019 10:53:59 +0100 -Subject: [PATCH 314/329] sched: migrate_enable: Busy loop until the migration +Subject: [PATCH 314/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 140d7f54a5fff02898d2ca9802b39548bf7455f1 ] diff --git a/debian/patches-rt/0315-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch b/debian/patches-rt/0315-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch index f64766d5f..7a417f287 100644 --- a/debian/patches-rt/0315-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch +++ b/debian/patches-rt/0315-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch @@ -1,11 +1,11 @@ -From 7ad42fb21af7d2c868e03da21a2843444fcde799 Mon Sep 17 00:00:00 2001 -Message-Id: <7ad42fb21af7d2c868e03da21a2843444fcde799.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ac14e901f5d4d496a16402571bd4166b1a75996e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 18 Dec 2019 12:25:09 +0100 -Subject: [PATCH 315/329] userfaultfd: Use a seqlock instead of seqcount -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 315/333] userfaultfd: Use a seqlock instead of seqcount +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit dc952a564d02997330654be9628bbe97ba2a05d3 ] diff --git a/debian/patches-rt/0316-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch b/debian/patches-rt/0316-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch index 2dfa37f85..fe41613df 100644 --- a/debian/patches-rt/0316-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch +++ b/debian/patches-rt/0316-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch @@ -1,11 +1,11 @@ -From 949f595834ceeed4fca1778592017a0e1257ad98 Mon Sep 17 00:00:00 2001 -Message-Id: <949f595834ceeed4fca1778592017a0e1257ad98.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 54b1967d10355a74b7cdfa78a26e9d4a9ae36187 Mon Sep 17 00:00:00 2001 +Message-Id: <54b1967d10355a74b7cdfa78a26e9d4a9ae36187.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:46 -0500 -Subject: [PATCH 316/329] 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.135-rt60.tar.xz +Subject: [PATCH 316/333] 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.142-rt63.tar.xz [ Upstream commit 2dcd94b443c5dcbc20281666321b7f025f9cc85c ] diff --git a/debian/patches-rt/0317-sched-migrate_enable-Remove-__schedule-call.patch b/debian/patches-rt/0317-sched-migrate_enable-Remove-__schedule-call.patch index 2bb03405e..4becbb1d5 100644 --- a/debian/patches-rt/0317-sched-migrate_enable-Remove-__schedule-call.patch +++ b/debian/patches-rt/0317-sched-migrate_enable-Remove-__schedule-call.patch @@ -1,11 +1,11 @@ -From 14901df46a327f7b019ebd9897e5adabf6e08fff Mon Sep 17 00:00:00 2001 -Message-Id: <14901df46a327f7b019ebd9897e5adabf6e08fff.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 2b571943b0de69229d8b4bd12b59a8a2518e69da Mon Sep 17 00:00:00 2001 +Message-Id: <2b571943b0de69229d8b4bd12b59a8a2518e69da.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:47 -0500 -Subject: [PATCH 317/329] sched: migrate_enable: Remove __schedule() call -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 317/333] sched: migrate_enable: Remove __schedule() call +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit b8162e61e9a33bd1de6452eb838fbf50a93ddd9a ] diff --git a/debian/patches-rt/0318-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch b/debian/patches-rt/0318-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch index 25ffe16f4..c8bf07df0 100644 --- a/debian/patches-rt/0318-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch +++ b/debian/patches-rt/0318-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch @@ -1,12 +1,12 @@ -From eda7bf1eb4235f95f7b9a7c6f1b16ce0c2aea8cc Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 89359abb03085a37091da76ad6dc84edb3e5ec03 Mon Sep 17 00:00:00 2001 +Message-Id: <89359abb03085a37091da76ad6dc84edb3e5ec03.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Matt Fleming Date: Sun, 26 Jan 2020 21:19:45 +0000 -Subject: [PATCH 318/329] mm/memcontrol: Move misplaced +Subject: [PATCH 318/333] mm/memcontrol: Move misplaced local_unlock_irqrestore() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 071a1d6a6e14d0dec240a8c67b425140d7f92f6a ] diff --git a/debian/patches-rt/0319-locallock-Include-header-for-the-current-macro.patch b/debian/patches-rt/0319-locallock-Include-header-for-the-current-macro.patch index 2c417b236..784cee415 100644 --- a/debian/patches-rt/0319-locallock-Include-header-for-the-current-macro.patch +++ b/debian/patches-rt/0319-locallock-Include-header-for-the-current-macro.patch @@ -1,11 +1,11 @@ -From 0c141dbe4d90b21c4b7d25f14f300ad5a4e2f2c3 Mon Sep 17 00:00:00 2001 -Message-Id: <0c141dbe4d90b21c4b7d25f14f300ad5a4e2f2c3.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 10208f4f5718bef83d3b56a415e2d5eae8be9fcb Mon Sep 17 00:00:00 2001 +Message-Id: <10208f4f5718bef83d3b56a415e2d5eae8be9fcb.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Feb 2020 13:29:50 +0100 -Subject: [PATCH 319/329] locallock: Include header for the `current' macro -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 319/333] locallock: Include header for the `current' macro +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit e693075a5fd852043fa8d2b0467e078d9e5cb782 ] diff --git a/debian/patches-rt/0320-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch b/debian/patches-rt/0320-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch index 73cfc79fd..3e158ff9a 100644 --- a/debian/patches-rt/0320-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch +++ b/debian/patches-rt/0320-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch @@ -1,12 +1,12 @@ -From 8005272375459065fb1c2210b7c638d2efca9be6 Mon Sep 17 00:00:00 2001 -Message-Id: <8005272375459065fb1c2210b7c638d2efca9be6.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 59163bc6589fed0c9fcf3f1763f34aca057e5b69 Mon Sep 17 00:00:00 2001 +Message-Id: <59163bc6589fed0c9fcf3f1763f34aca057e5b69.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:57:11 +0100 -Subject: [PATCH 320/329] drm/vmwgfx: Drop preempt_disable() in +Subject: [PATCH 320/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit b901491e7b9b7a676818d84e482b69be72fc142f ] diff --git a/debian/patches-rt/0321-tracing-make-preempt_lazy-and-migrate_disable-counte.patch b/debian/patches-rt/0321-tracing-make-preempt_lazy-and-migrate_disable-counte.patch index 4be82e037..e221878ea 100644 --- a/debian/patches-rt/0321-tracing-make-preempt_lazy-and-migrate_disable-counte.patch +++ b/debian/patches-rt/0321-tracing-make-preempt_lazy-and-migrate_disable-counte.patch @@ -1,12 +1,12 @@ -From 72f14300c084d95060cc958277f83f2f15f88de3 Mon Sep 17 00:00:00 2001 -Message-Id: <72f14300c084d95060cc958277f83f2f15f88de3.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From ab1ae727cf16331057704e2b02403ec469fcdbbf Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:15:15 +0100 -Subject: [PATCH 321/329] tracing: make preempt_lazy and migrate_disable +Subject: [PATCH 321/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit dd430bf5ecb40f9a89679c85868826475d71de54 ] @@ -40,7 +40,7 @@ index 72864a11cec0..e26a85c1b7ba 100644 }; diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c -index 1febb0ca4c81..07b8f5bfd263 100644 +index 7b59bc9077de..f1ca52d19b7a 100644 --- a/kernel/trace/trace_events.c +++ b/kernel/trace/trace_events.c @@ -188,8 +188,8 @@ static int trace_define_common_fields(void) diff --git a/debian/patches-rt/0322-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch b/debian/patches-rt/0322-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch index b34fcb39c..6440349fb 100644 --- a/debian/patches-rt/0322-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch +++ b/debian/patches-rt/0322-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch @@ -1,12 +1,12 @@ -From ac710d63435b035c7ba9f2a384ccc67a86f8531e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From f883273afd6c3b32cf98960991c1f9b816f03a65 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Tiejun Chen Date: Mon, 30 Mar 2020 18:45:23 -0400 -Subject: [PATCH 322/329] lib/ubsan: Remove flags parameter from calls to +Subject: [PATCH 322/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Fails to build with CONFIG_UBSAN=y diff --git a/debian/patches-rt/0323-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch b/debian/patches-rt/0323-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch index dca5ac602..0c6b76c6a 100644 --- a/debian/patches-rt/0323-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch +++ b/debian/patches-rt/0323-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch @@ -1,12 +1,12 @@ -From fdc910588fec4961eec90c82c6278bf4ff2aba4a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From d23d658736d37e541d262808a4c63d4745d4aa9b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Sun, 22 Mar 2020 00:00:28 +0100 -Subject: [PATCH 323/329] irq_work: Fix checking of IRQ_WORK_LAZY flag set on +Subject: [PATCH 323/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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 diff --git a/debian/patches-rt/0324-tasklet-Address-a-race-resulting-in-double-enqueue.patch b/debian/patches-rt/0324-tasklet-Address-a-race-resulting-in-double-enqueue.patch index 72165918c..72015b3da 100644 --- a/debian/patches-rt/0324-tasklet-Address-a-race-resulting-in-double-enqueue.patch +++ b/debian/patches-rt/0324-tasklet-Address-a-race-resulting-in-double-enqueue.patch @@ -1,11 +1,11 @@ -From 601fd52f2bc463a20024b3c51bde9aa111815a2f Mon Sep 17 00:00:00 2001 -Message-Id: <601fd52f2bc463a20024b3c51bde9aa111815a2f.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 1718bf876df66e632411416b1c5b20a484f5a2e2 Mon Sep 17 00:00:00 2001 +Message-Id: <1718bf876df66e632411416b1c5b20a484f5a2e2.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Zhang Xiao Date: Tue, 17 Mar 2020 12:47:43 +0100 -Subject: [PATCH 324/329] tasklet: Address a race resulting in double-enqueue -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 324/333] tasklet: Address a race resulting in double-enqueue +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz The kernel bugzilla has the following race condition reported: diff --git a/debian/patches-rt/0325-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch b/debian/patches-rt/0325-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch index 49575e13a..4137654a3 100644 --- a/debian/patches-rt/0325-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch +++ b/debian/patches-rt/0325-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch @@ -1,12 +1,12 @@ -From 44cbc6f537c24d27d6e1b7544ac5138fa6707e1c Mon Sep 17 00:00:00 2001 -Message-Id: <44cbc6f537c24d27d6e1b7544ac5138fa6707e1c.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From fce85b372ad4709202789969e1b53532ab5fe6df Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Rasmus Villemoes Date: Tue, 28 Apr 2020 16:40:26 +0200 -Subject: [PATCH 325/329] hrtimer: fix logic for when grabbing +Subject: [PATCH 325/333] 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.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz Commit diff --git a/debian/patches-rt/0326-fs-dcache-Include-swait.h-header.patch b/debian/patches-rt/0326-fs-dcache-Include-swait.h-header.patch index 1abbc7169..799113b33 100644 --- a/debian/patches-rt/0326-fs-dcache-Include-swait.h-header.patch +++ b/debian/patches-rt/0326-fs-dcache-Include-swait.h-header.patch @@ -1,11 +1,11 @@ -From ae11303b32f822790ea5838254b2231882515f06 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 90ada573e9c82808f6ed6fb2c5f6c297d67b227b Mon Sep 17 00:00:00 2001 +Message-Id: <90ada573e9c82808f6ed6fb2c5f6c297d67b227b.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 16 Apr 2020 12:42:15 +0200 -Subject: [PATCH 326/329] fs/dcache: Include swait.h header -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 326/333] fs/dcache: Include swait.h header +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 279f90ddf53cd6bd3c203fbbf488d642ea2603de ] diff --git a/debian/patches-rt/0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch b/debian/patches-rt/0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch index ebf4cb1a5..f5adf2a9c 100644 --- a/debian/patches-rt/0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch +++ b/debian/patches-rt/0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch @@ -1,12 +1,12 @@ -From b83418550e2a28c5378d9067977963137c0c7901 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 5a6a7a1c5194d16216bb14c0cfd595e0ffb83b18 Mon Sep 17 00:00:00 2001 +Message-Id: <5a6a7a1c5194d16216bb14c0cfd595e0ffb83b18.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Kevin Hao Date: Mon, 4 May 2020 11:34:07 +0800 -Subject: [PATCH 327/329] mm: slub: Always flush the delayed empty slubs in +Subject: [PATCH 327/333] mm: slub: Always flush the delayed empty slubs in flush_all() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz [ Upstream commit 23a2c31b19e99beaf5107071b0f32a596202cdae ] diff --git a/debian/patches-rt/0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch b/debian/patches-rt/0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch index 497731b46..dd404caa9 100644 --- a/debian/patches-rt/0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch +++ b/debian/patches-rt/0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch @@ -1,11 +1,11 @@ -From f5e1979b23fc83cc6f9b42871b103613bf3196e3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From 459686cb14f442d4264633148c1febd2c7e75f50 Mon Sep 17 00:00:00 2001 +Message-Id: <459686cb14f442d4264633148c1febd2c7e75f50.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> From: Tom Zanussi Date: Tue, 9 Jun 2020 11:04:08 -0500 -Subject: [PATCH 328/329] tasklet: Fix UP case for tasklet CHAINED state -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz +Subject: [PATCH 328/333] tasklet: Fix UP case for tasklet CHAINED state +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz commit 62d0a2a30cd0 (tasklet: Address a race resulting in double-enqueue) addresses a problem that can result in a tasklet being diff --git a/debian/patches-rt/0329-Linux-4.19.135-rt60-REBASE.patch b/debian/patches-rt/0329-Linux-4.19.135-rt60-REBASE.patch deleted file mode 100644 index 222c8fcab..000000000 --- a/debian/patches-rt/0329-Linux-4.19.135-rt60-REBASE.patch +++ /dev/null @@ -1,24 +0,0 @@ -From 3b8f4a03dd51a7974cc8fae71168fc50965ac3b3 Mon Sep 17 00:00:00 2001 -Message-Id: <3b8f4a03dd51a7974cc8fae71168fc50965ac3b3.1596234184.git.zanussi@kernel.org> -In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> -From: Tom Zanussi -Date: Fri, 31 Jul 2020 17:18:15 -0500 -Subject: [PATCH 329/329] Linux 4.19.135-rt60 REBASE -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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..66fa05e70f29 100644 ---- a/localversion-rt -+++ b/localversion-rt -@@ -1 +1 @@ ---rt16 -+-rt60 --- -2.17.1 - diff --git a/debian/patches-rt/0329-signal-Prevent-double-free-of-user-struct.patch b/debian/patches-rt/0329-signal-Prevent-double-free-of-user-struct.patch new file mode 100644 index 000000000..f22cec829 --- /dev/null +++ b/debian/patches-rt/0329-signal-Prevent-double-free-of-user-struct.patch @@ -0,0 +1,58 @@ +From 8e2028c4cbc41caae5551c2cd8cd0d7533bf1749 Mon Sep 17 00:00:00 2001 +Message-Id: <8e2028c4cbc41caae5551c2cd8cd0d7533bf1749.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +From: Matt Fleming +Date: Tue, 7 Apr 2020 10:54:13 +0100 +Subject: [PATCH 329/333] signal: Prevent double-free of user struct +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz + +[ Upsteam commit 9567db2ebe566a93485e1a27d8759969d0002d7a ] + +The way user struct reference counting works changed significantly with, + + fda31c50292a ("signal: avoid double atomic counter increments for user accounting") + +Now user structs are only freed once the last pending signal is +dequeued. Make sigqueue_free_current() follow this new convention to +avoid freeing the user struct multiple times and triggering this +warning: + + refcount_t: underflow; use-after-free. + WARNING: CPU: 0 PID: 6794 at lib/refcount.c:288 refcount_dec_not_one+0x45/0x50 + Call Trace: + refcount_dec_and_lock_irqsave+0x16/0x60 + free_uid+0x31/0xa0 + __dequeue_signal+0x17c/0x190 + dequeue_signal+0x5a/0x1b0 + do_sigtimedwait+0x208/0x250 + __x64_sys_rt_sigtimedwait+0x6f/0xd0 + do_syscall_64+0x72/0x200 + entry_SYSCALL_64_after_hwframe+0x49/0xbe + +Signed-off-by: Matt Fleming +Reported-by: Daniel Wagner +Signed-off-by: Sebastian Andrzej Siewior +Signed-off-by: Tom Zanussi +--- + kernel/signal.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/kernel/signal.c b/kernel/signal.c +index 45748993f777..05c9b5a6b3ae 100644 +--- a/kernel/signal.c ++++ b/kernel/signal.c +@@ -488,8 +488,8 @@ static void sigqueue_free_current(struct sigqueue *q) + + up = q->user; + if (rt_prio(current->normal_prio) && !put_task_cache(current, q)) { +- atomic_dec(&up->sigpending); +- free_uid(up); ++ if (atomic_dec_and_test(&up->sigpending)) ++ free_uid(up); + } else + __sigqueue_free(q); + } +-- +2.17.1 + diff --git a/debian/patches-rt/0330-Bluetooth-Acquire-sk_lock.slock-without-disabling-in.patch b/debian/patches-rt/0330-Bluetooth-Acquire-sk_lock.slock-without-disabling-in.patch new file mode 100644 index 000000000..dafb7df86 --- /dev/null +++ b/debian/patches-rt/0330-Bluetooth-Acquire-sk_lock.slock-without-disabling-in.patch @@ -0,0 +1,68 @@ +From a03b37742905a9179db8c1ac35f345ba109e3fe5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +From: Sebastian Andrzej Siewior +Date: Thu, 28 May 2020 14:35:12 +0200 +Subject: [PATCH 330/333] Bluetooth: Acquire sk_lock.slock without disabling + interrupts +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz + +[ Upstream commit e6da0edc24eecef2f6964d92fa9044e1821deace ] + +There was a lockdep which led to commit + fad003b6c8e3d ("Bluetooth: Fix inconsistent lock state with RFCOMM") + +Lockdep noticed that `sk->sk_lock.slock' was acquired without disabling +the softirq while the lock was also used in softirq context. +Unfortunately the solution back then was to disable interrupts before +acquiring the lock which however made lockdep happy. +It would have been enough to simply disable the softirq. Disabling +interrupts before acquiring a spinlock_t is not allowed on PREEMPT_RT +because these locks are converted to 'sleeping' spinlocks. + +Use spin_lock_bh() in order to acquire the `sk_lock.slock'. + +Reported-by: Luis Claudio R. Goncalves +Reported-by: kbuild test robot [missing unlock] +Signed-off-by: Sebastian Andrzej Siewior +Signed-off-by: Marcel Holtmann +Signed-off-by: Tom Zanussi +--- + net/bluetooth/rfcomm/sock.c | 7 ++----- + 1 file changed, 2 insertions(+), 5 deletions(-) + +diff --git a/net/bluetooth/rfcomm/sock.c b/net/bluetooth/rfcomm/sock.c +index c044ff2f73e6..75bc8102cdd7 100644 +--- a/net/bluetooth/rfcomm/sock.c ++++ b/net/bluetooth/rfcomm/sock.c +@@ -64,15 +64,13 @@ static void rfcomm_sk_data_ready(struct rfcomm_dlc *d, struct sk_buff *skb) + static void rfcomm_sk_state_change(struct rfcomm_dlc *d, int err) + { + struct sock *sk = d->owner, *parent; +- unsigned long flags; + + if (!sk) + return; + + BT_DBG("dlc %p state %ld err %d", d, d->state, err); + +- local_irq_save(flags); +- bh_lock_sock(sk); ++ spin_lock_bh(&sk->sk_lock.slock); + + if (err) + sk->sk_err = err; +@@ -93,8 +91,7 @@ static void rfcomm_sk_state_change(struct rfcomm_dlc *d, int err) + sk->sk_state_change(sk); + } + +- bh_unlock_sock(sk); +- local_irq_restore(flags); ++ spin_unlock_bh(&sk->sk_lock.slock); + + if (parent && sock_flag(sk, SOCK_ZAPPED)) { + /* We have to drop DLC lock here, otherwise +-- +2.17.1 + diff --git a/debian/patches-rt/0331-net-phy-fixed_phy-Remove-unused-seqcount.patch b/debian/patches-rt/0331-net-phy-fixed_phy-Remove-unused-seqcount.patch new file mode 100644 index 000000000..1782cc915 --- /dev/null +++ b/debian/patches-rt/0331-net-phy-fixed_phy-Remove-unused-seqcount.patch @@ -0,0 +1,92 @@ +From c59087757e2b4761644edd592ec7d1f4eaeccbb6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +From: "Ahmed S. Darwish" +Date: Wed, 10 Jun 2020 12:53:00 +0200 +Subject: [PATCH 331/333] net: phy: fixed_phy: Remove unused seqcount +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz + +[ Upstream commit 6554eac9ef2bd1c968886b31cc7266b49258a463 ] + +Commit bf7afb29d545 ("phy: improve safety of fixed-phy MII register +reading") protected the fixed PHY status with a sequence counter. + +Two years later, commit d2b977939b18 ("net: phy: fixed-phy: remove +fixed_phy_update_state()") removed the sequence counter's write side +critical section -- neutralizing its read side retry loop. + +Remove the unused seqcount. + +Signed-off-by: Ahmed S. Darwish +Reviewed-by: Sebastian Andrzej Siewior +Reviewed-by: Andrew Lunn +Signed-off-by: David S. Miller +(cherry picked from v5.8-rc1 commit 79cbb6bc3332da7162c2581e151659ab8ebaa528) +Signed-off-by: Ahmed S. Darwish +Signed-off-by: Sebastian Andrzej Siewior +Signed-off-by: Tom Zanussi +--- + drivers/net/phy/fixed_phy.c | 25 +++++++++---------------- + 1 file changed, 9 insertions(+), 16 deletions(-) + +diff --git a/drivers/net/phy/fixed_phy.c b/drivers/net/phy/fixed_phy.c +index 59820164502e..953ff54dd5df 100644 +--- a/drivers/net/phy/fixed_phy.c ++++ b/drivers/net/phy/fixed_phy.c +@@ -23,7 +23,6 @@ + #include + #include + #include +-#include + #include + + #include "swphy.h" +@@ -36,7 +35,6 @@ struct fixed_mdio_bus { + struct fixed_phy { + int addr; + struct phy_device *phydev; +- seqcount_t seqcount; + struct fixed_phy_status status; + int (*link_update)(struct net_device *, struct fixed_phy_status *); + struct list_head node; +@@ -62,18 +60,15 @@ static int fixed_mdio_read(struct mii_bus *bus, int phy_addr, int reg_num) + list_for_each_entry(fp, &fmb->phys, node) { + if (fp->addr == phy_addr) { + struct fixed_phy_status state; +- int s; +- +- do { +- s = read_seqcount_begin(&fp->seqcount); +- /* Issue callback if user registered it. */ +- if (fp->link_update) +- fp->link_update(fp->phydev->attached_dev, +- &fp->status); +- /* Check the GPIO for change in status */ +- fixed_phy_update(fp); +- state = fp->status; +- } while (read_seqcount_retry(&fp->seqcount, s)); ++ ++ /* Issue callback if user registered it. */ ++ if (fp->link_update) ++ fp->link_update(fp->phydev->attached_dev, ++ &fp->status); ++ ++ /* Check the GPIO for change in status */ ++ fixed_phy_update(fp); ++ state = fp->status; + + return swphy_read_reg(reg_num, &state); + } +@@ -131,8 +126,6 @@ int fixed_phy_add(unsigned int irq, int phy_addr, + if (!fp) + return -ENOMEM; + +- seqcount_init(&fp->seqcount); +- + if (irq != PHY_POLL) + fmb->mii_bus->irq[phy_addr] = irq; + +-- +2.17.1 + diff --git a/debian/patches-rt/0332-net-xfrm-fix-compress-vs-decompress-serialization.patch b/debian/patches-rt/0332-net-xfrm-fix-compress-vs-decompress-serialization.patch new file mode 100644 index 000000000..e22096c99 --- /dev/null +++ b/debian/patches-rt/0332-net-xfrm-fix-compress-vs-decompress-serialization.patch @@ -0,0 +1,105 @@ +From f80230af6609b80d3352d14ac5a4f53329fad376 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +From: Davidlohr Bueso +Date: Tue, 18 Aug 2020 09:20:53 -0700 +Subject: [PATCH 332/333] net: xfrm: fix compress vs decompress serialization +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.tar.xz + +A crash was seen in xfrm when running ltp's 'tcp4_ipsec06' stresser on v4.x +based RT kernels. + +ipcomp_compress() will serialize access to the ipcomp_scratches percpu buffer by +disabling BH and preventing a softirq from coming in and running ipcom_decompress(), +which is never called from process context. This of course won't work on RT and +the buffer can get corrupted; there have been similar issues with in the past with +such assumptions, ie: ebf255ed6c44 (net: add back the missing serialization in +ip_send_unicast_reply()). + +Similarly, this patch addresses the issue with locallocks allowing RT to have a +percpu spinlock and do the correct serialization. + +Signed-off-by: Davidlohr Bueso +Signed-off-by: Tom Zanussi +--- + net/xfrm/xfrm_ipcomp.c | 21 +++++++++++++++------ + 1 file changed, 15 insertions(+), 6 deletions(-) + +diff --git a/net/xfrm/xfrm_ipcomp.c b/net/xfrm/xfrm_ipcomp.c +index a00ec715aa46..a97997385423 100644 +--- a/net/xfrm/xfrm_ipcomp.c ++++ b/net/xfrm/xfrm_ipcomp.c +@@ -20,6 +20,7 @@ + #include + #include + #include ++#include + #include + #include + #include +@@ -36,6 +37,7 @@ struct ipcomp_tfms { + + static DEFINE_MUTEX(ipcomp_resource_mutex); + static void * __percpu *ipcomp_scratches; ++static DEFINE_LOCAL_IRQ_LOCK(ipcomp_scratches_lock); + static int ipcomp_scratch_users; + static LIST_HEAD(ipcomp_tfms_list); + +@@ -45,12 +47,15 @@ static int ipcomp_decompress(struct xfrm_state *x, struct sk_buff *skb) + const int plen = skb->len; + int dlen = IPCOMP_SCRATCH_SIZE; + const u8 *start = skb->data; +- const int cpu = get_cpu(); +- u8 *scratch = *per_cpu_ptr(ipcomp_scratches, cpu); +- struct crypto_comp *tfm = *per_cpu_ptr(ipcd->tfms, cpu); +- int err = crypto_comp_decompress(tfm, start, plen, scratch, &dlen); +- int len; ++ u8 *scratch; ++ struct crypto_comp *tfm; ++ int err, len; ++ ++ local_lock(ipcomp_scratches_lock); + ++ scratch = *this_cpu_ptr(ipcomp_scratches); ++ tfm = *this_cpu_ptr(ipcd->tfms); ++ err = crypto_comp_decompress(tfm, start, plen, scratch, &dlen); + if (err) + goto out; + +@@ -103,7 +108,7 @@ static int ipcomp_decompress(struct xfrm_state *x, struct sk_buff *skb) + err = 0; + + out: +- put_cpu(); ++ local_unlock(ipcomp_scratches_lock); + return err; + } + +@@ -146,6 +151,8 @@ static int ipcomp_compress(struct xfrm_state *x, struct sk_buff *skb) + int err; + + local_bh_disable(); ++ local_lock(ipcomp_scratches_lock); ++ + scratch = *this_cpu_ptr(ipcomp_scratches); + tfm = *this_cpu_ptr(ipcd->tfms); + err = crypto_comp_compress(tfm, start, plen, scratch, &dlen); +@@ -158,12 +165,14 @@ static int ipcomp_compress(struct xfrm_state *x, struct sk_buff *skb) + } + + memcpy(start + sizeof(struct ip_comp_hdr), scratch, dlen); ++ local_unlock(ipcomp_scratches_lock); + local_bh_enable(); + + pskb_trim(skb, dlen + sizeof(struct ip_comp_hdr)); + return 0; + + out: ++ local_unlock(ipcomp_scratches_lock); + local_bh_enable(); + return err; + } +-- +2.17.1 + diff --git a/debian/patches-rt/0333-Linux-4.19.142-rt63-REBASE.patch b/debian/patches-rt/0333-Linux-4.19.142-rt63-REBASE.patch new file mode 100644 index 000000000..c014ca21a --- /dev/null +++ b/debian/patches-rt/0333-Linux-4.19.142-rt63-REBASE.patch @@ -0,0 +1,24 @@ +From 7242d3d469f4634a955870633416179e66ffda84 Mon Sep 17 00:00:00 2001 +Message-Id: <7242d3d469f4634a955870633416179e66ffda84.1599166691.git.zanussi@kernel.org> +In-Reply-To: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +References: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +From: Tom Zanussi +Date: Wed, 2 Sep 2020 13:53:19 -0500 +Subject: [PATCH 333/333] Linux 4.19.142-rt63 REBASE +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.142-rt63.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..b0e8dd7bd707 100644 +--- a/localversion-rt ++++ b/localversion-rt +@@ -1 +1 @@ +--rt16 ++-rt63 +-- +2.17.1 + diff --git a/debian/patches-rt/series b/debian/patches-rt/series index 85c588b37..beb92e8c9 100644 --- a/debian/patches-rt/series +++ b/debian/patches-rt/series @@ -326,4 +326,8 @@ 0326-fs-dcache-Include-swait.h-header.patch 0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch 0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch -0329-Linux-4.19.135-rt60-REBASE.patch +0329-signal-Prevent-double-free-of-user-struct.patch +0330-Bluetooth-Acquire-sk_lock.slock-without-disabling-in.patch +0331-net-phy-fixed_phy-Remove-unused-seqcount.patch +0332-net-xfrm-fix-compress-vs-decompress-serialization.patch +0333-Linux-4.19.142-rt63-REBASE.patch