From 8229f60bca67459e0235729272db22a15c79128e Mon Sep 17 00:00:00 2001 From: Salvatore Bonaccorso Date: Mon, 12 Oct 2020 14:52:06 +0200 Subject: [PATCH] [rt] Update to 4.19.148-rt64 --- debian/changelog | 3 +++ ...M-at91-add-TCB-registers-definitions.patch | 6 ++--- ...ers-Add-a-new-driver-for-the-Atmel-A.patch | 10 ++++---- ...ers-timer-atmel-tcb-add-clockevent-d.patch | 10 ++++---- ...drivers-atmel-pit-make-option-silent.patch | 10 ++++---- ...at91-Implement-clocksource-selection.patch | 10 ++++---- ...onfigs-at91-use-new-TCB-timer-driver.patch | 10 ++++---- .../0007-ARM-configs-at91-unselect-PIT.patch | 10 ++++---- ...ts-Move-pending-table-allocation-to-.patch | 10 ++++---- ...-convert-worker-lock-to-raw-spinlock.patch | 10 ++++---- ...m-qi-simplify-CGR-allocation-freeing.patch | 10 ++++---- ...obustify-CFS-bandwidth-timer-locking.patch | 10 ++++---- ...012-arm-Convert-arm-boot_lock-to-raw.patch | 10 ++++---- ...-let-setaffinity-unmask-threaded-EOI.patch | 10 ++++---- ...irqsave-in-cgroup_rstat_flush_locked.patch | 10 ++++---- ...lize-cookie-hash-table-raw-spinlocks.patch | 10 ++++---- ...mbus-include-header-for-get_irq_regs.patch | 10 ++++---- ...de-irqflags.h-for-raw_local_irq_save.patch | 10 ++++---- .../0018-efi-Allow-efi-runtime.patch | 10 ++++---- ...fi-drop-task_lock-from-efi_switch_mm.patch | 10 ++++---- ...e_layout-before-altenates-are-applie.patch | 10 ++++---- ...-phandle-cache-outside-of-the-devtre.patch | 10 ++++---- ...ake-quarantine_lock-a-raw_spinlock_t.patch | 10 ++++---- ...xpedited-GP-parallelization-cleverne.patch | 10 ++++---- ...-kmemleak_lock-to-raw-spinlock-on-RT.patch | 10 ++++---- ...-replace-seqcount_t-with-a-seqlock_t.patch | 12 +++++----- ...vide-a-pointer-to-the-valid-CPU-mask.patch | 10 ++++---- ...ernel-sched-core-add-migrate_disable.patch | 10 ++++---- ...sable-Add-export_symbol_gpl-for-__mi.patch | 10 ++++---- ...o-not-disable-enable-clocks-in-a-row.patch | 10 ++++---- ...B-Allow-higher-clock-rates-for-clock.patch | 10 ++++---- ...31-timekeeping-Split-jiffies-seqlock.patch | 10 ++++---- ...2-signal-Revert-ptrace-preempt-magic.patch | 10 ++++---- ...et-sched-Use-msleep-instead-of-yield.patch | 14 +++++------ ...rq-remove-BUG_ON-irqs_disabled-check.patch | 10 ++++---- ...do-no-disable-interrupts-in-giveback.patch | 10 ++++---- ...rovide-PREEMPT_RT_BASE-config-switch.patch | 10 ++++---- ...sable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch | 10 ++++---- ...abel-disable-if-stop_machine-is-used.patch | 10 ++++---- ...config-options-which-are-not-RT-comp.patch | 10 ++++---- .../0040-lockdep-disable-self-test.patch | 10 ++++---- .../0041-mm-Allow-only-slub-on-RT.patch | 10 ++++---- ...locking-Disable-spin-on-owner-for-RT.patch | 10 ++++---- ...043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch | 10 ++++---- ...044-rcu-make-RCU_BOOST-default-on-RT.patch | 10 ++++---- ...-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch | 10 ++++---- ...46-net-core-disable-NET_RX_BUSY_POLL.patch | 10 ++++---- ...0047-arm-disable-NEON-in-kernel-mode.patch | 10 ++++---- ...0048-powerpc-Use-generic-rwsem-on-RT.patch | 10 ++++---- ...ble-in-kernel-MPIC-emulation-for-PRE.patch | 10 ++++---- .../0050-powerpc-Disable-highmem-on-RT.patch | 10 ++++---- .../0051-mips-Disable-highmem-on-RT.patch | 14 +++++------ ...86-Use-generic-rwsem_spinlocks-on-rt.patch | 10 ++++---- ...ds-trigger-disable-CPU-trigger-on-RT.patch | 10 ++++---- ...rop-K8-s-driver-from-beeing-selected.patch | 10 ++++---- .../patches-rt/0055-md-disable-bcache.patch | 10 ++++---- ...6-efi-Disable-runtime-services-on-RT.patch | 10 ++++---- ...0057-printk-Add-a-printk-kill-switch.patch | 10 ++++---- ..._early_printk-boot-param-to-help-wit.patch | 10 ++++---- ...pt-Provide-preempt_-_-no-rt-variants.patch | 10 ++++---- ...-migrate_disable-enable-in-different.patch | 10 ++++---- .../0061-rt-Add-local-irq-locks.patch | 10 ++++---- ...provide-get-put-_locked_ptr-variants.patch | 10 ++++---- ...catterlist-Do-not-disable-irqs-on-RT.patch | 10 ++++---- ...-x86-Delay-calling-signals-in-atomic.patch | 10 ++++---- ...ignal-delay-calling-signals-on-32bit.patch | 10 ++++---- ...head-Replace-bh_uptodate_lock-for-rt.patch | 14 +++++------ ...-state-lock-and-journal-head-lock-rt.patch | 10 ++++---- ...st_bl-Make-list-head-locking-RT-safe.patch | 10 ++++---- ...-list_bl-fixup-bogus-lockdep-warning.patch | 10 ++++---- .../0070-genirq-Disable-irqpoll-on-rt.patch | 10 ++++---- ...-genirq-Force-interrupt-thread-on-RT.patch | 10 ++++---- ...d-zone-lock-while-freeing-pages-from.patch | 10 ++++---- ...d-zone-lock-while-freeing-pages-from.patch | 10 ++++---- ...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 | 10 ++++---- ...077-mm-swap-Convert-to-percpu-locked.patch | 10 ++++---- ...m-perform-lru_add_drain_all-remotely.patch | 10 ++++---- ...t-per-cpu-variables-with-preempt-dis.patch | 10 ++++---- ...plit-page-table-locks-for-vector-pag.patch | 10 ++++---- .../0081-mm-Enable-SLUB-for-RT.patch | 12 +++++----- ...0082-slub-Enable-irqs-for-__GFP_WAIT.patch | 12 +++++----- .../0083-slub-Disable-SLUB_CPU_PARTIAL.patch | 10 ++++---- ...n-t-call-schedule_work_on-in-preempt.patch | 10 ++++---- ...place-local_irq_disable-with-local-l.patch | 10 ++++---- ...oc-copy-with-get_cpu_var-and-locking.patch | 10 ++++---- ...le-preemption-__split_large_page-aft.patch | 10 ++++---- .../0088-radix-tree-use-local-locks.patch | 10 ++++---- ...9-timers-Prepare-for-full-preemption.patch | 10 ++++---- ...090-x86-kvm-Require-const-tsc-for-RT.patch | 10 ++++---- ...ec-Don-t-use-completion-s-wait-queue.patch | 10 ++++---- .../0092-wait.h-include-atomic.h.patch | 10 ++++---- ...mple-Simple-work-queue-implemenation.patch | 10 ++++---- ...-a-shit-statement-in-SWORK_EVENT_PEN.patch | 10 ++++---- ...95-completion-Use-simple-wait-queues.patch | 10 ++++---- .../0096-fs-aio-simple-simple-work.patch | 10 ++++---- ...id-schedule_work-with-interrupts-dis.patch | 10 ++++---- ...ate-hrtimer_init-hrtimer_init_sleepe.patch | 14 +++++------ ...099-hrtimers-Prepare-full-preemption.patch | 10 ++++---- ...s-by-default-into-the-softirq-contex.patch | 10 ++++---- ...air-Make-the-hrtimers-non-hard-again.patch | 10 ++++---- ...-schedule_work-call-to-helper-thread.patch | 10 ++++---- ...te-change-before-hrtimer_cancel-in-d.patch | 10 ++++---- ...timers-Thread-posix-cpu-timers-on-rt.patch | 10 ++++---- ...ched-Move-task_struct-cleanup-to-RCU.patch | 10 ++++---- ...-number-of-task-migrations-per-batch.patch | 10 ++++---- .../0107-sched-Move-mmdrop-to-RCU-on-RT.patch | 10 ++++---- ...e-stack-kprobe-clean-up-to-__put_tas.patch | 10 ++++---- ...state-for-tasks-blocked-on-sleeping-.patch | 10 ++++---- ...ount-rcu_preempt_depth-on-RT-in-migh.patch | 10 ++++---- ...-proper-LOCK_OFFSET-for-cond_resched.patch | 10 ++++---- .../0112-sched-Disable-TTWU_QUEUE-on-RT.patch | 10 ++++---- ...Only-wake-up-idle-workers-if-not-blo.patch | 10 ++++---- ...ease-the-nr-of-migratory-tasks-when-.patch | 10 ++++---- ...-hotplug-Lightweight-get-online-cpus.patch | 10 ++++---- ...e-disabled-counter-to-tracing-output.patch | 10 ++++---- .../0117-lockdep-Make-it-RT-aware.patch | 10 ++++---- ...tasklets-from-going-into-infinite-sp.patch | 10 ++++---- ...eemption-after-reenabling-interrupts.patch | 14 +++++------ ...oftirq-Disable-softirq-stacks-for-RT.patch | 10 ++++---- .../0121-softirq-Split-softirq-locks.patch | 10 ++++---- ...-use-local_bh_disable-in-netif_rx_ni.patch | 12 +++++----- ...abling-of-softirq-processing-in-irq-.patch | 10 ++++---- ...plit-timer-softirqs-out-of-ksoftirqd.patch | 10 ++++---- ...cal_softirq_pending-messages-if-ksof.patch | 10 ++++---- ...cal_softirq_pending-messages-if-task.patch | 10 ++++---- .../0127-rtmutex-trylock-is-okay-on-RT.patch | 10 ++++---- ...-nfs-turn-rmdir_sem-into-a-semaphore.patch | 10 ++++---- ...he-various-new-futex-race-conditions.patch | 10 ++++---- ...on-when-a-requeued-RT-task-times-out.patch | 10 ++++---- ...k-unlock-symetry-versus-pi_lock-and-.patch | 10 ++++---- .../0132-pid.h-include-atomic.h.patch | 10 ++++---- ...arm-include-definition-for-cpumask_t.patch | 10 ++++---- ...ure-Do-NOT-include-rwlock.h-directly.patch | 10 ++++---- ...35-rtmutex-Add-rtmutex_lock_killable.patch | 10 ++++---- ...0136-rtmutex-Make-lock_killable-work.patch | 10 ++++---- ...spinlock-Split-the-lock-types-header.patch | 10 ++++---- .../0138-rtmutex-Avoid-include-hell.patch | 10 ++++---- ...-rbtree-don-t-include-the-rcu-header.patch | 10 ++++---- ...tex-Provide-rt_mutex_slowlock_locked.patch | 10 ++++---- ...ockdep-less-version-of-rt_mutex-s-lo.patch | 10 ++++---- ...tex-add-sleeping-lock-implementation.patch | 10 ++++---- ...utex-implementation-based-on-rtmutex.patch | 10 ++++---- ...wsem-implementation-based-on-rtmutex.patch | 10 ++++---- ...lock-implementation-based-on-rtmutex.patch | 10 ++++---- ...-preserve-state-like-a-sleeping-lock.patch | 10 ++++---- .../0147-rtmutex-wire-up-RT-s-locking.patch | 10 ++++---- ...utex-add-ww_mutex-addon-for-mutex-rt.patch | 10 ++++---- .../0149-kconfig-Add-PREEMPT_RT_FULL.patch | 10 ++++---- ...-fix-deadlock-in-device-mapper-block.patch | 10 ++++---- ...utex-Flush-block-plug-on-__down_read.patch | 10 ++++---- ...re-init-the-wait_lock-in-rt_mutex_in.patch | 10 ++++---- ...ace-fix-ptrace-vs-tasklist_lock-race.patch | 10 ++++---- ...mutex-annotate-sleeping-lock-context.patch | 10 ++++---- ...sable-fallback-to-preempt_disable-in.patch | 10 ++++---- ...eck-for-__LINUX_SPINLOCK_TYPES_H-on-.patch | 10 ++++---- .../0157-rcu-Frob-softirq-test.patch | 10 ++++---- ...58-rcu-Merge-RCU-bh-into-RCU-preempt.patch | 10 ++++---- ...ke-ksoftirqd-do-RCU-quiescent-states.patch | 10 ++++---- ...nate-softirq-processing-from-rcutree.patch | 10 ++++---- ...-use-cpu_online-instead-custom-check.patch | 10 ++++---- ...place-local_irqsave-with-a-locallock.patch | 10 ++++---- ..._normal_after_boot-by-default-for-RT.patch | 10 ++++---- ...erial-omap-Make-the-locking-RT-aware.patch | 10 ++++---- ...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 | 14 +++++------ ...wsem-Remove-preempt_disable-variants.patch | 10 ++++---- ...ate_mm-by-preempt_-disable-enable-_r.patch | 10 ++++---- ...back-explicit-INIT_HLIST_BL_HEAD-ini.patch | 10 ++++---- ...e-preemption-on-i_dir_seq-s-write-si.patch | 12 +++++----- ...e-of-local-lock-in-multi_cpu-decompr.patch | 10 ++++---- ...rmal-Defer-thermal-wakups-to-threads.patch | 10 ++++---- ...e-preemption-around-local_bh_disable.patch | 10 ++++---- ...poll-Do-not-disable-preemption-on-RT.patch | 12 +++++----- ...er-preempt-disable-region-which-suck.patch | 10 ++++---- .../0178-block-mq-use-cpu_light.patch | 10 ++++---- ...ock-mq-do-not-invoke-preempt_disable.patch | 14 +++++------ ...k-mq-don-t-complete-requests-via-IPI.patch | 14 +++++------ ...-Make-raid5_percpu-handling-RT-aware.patch | 10 ++++---- .../0182-rt-Introduce-cpu_chill.patch | 10 ++++---- ...rtimer-Don-t-lose-state-in-cpu_chill.patch | 10 ++++---- ...chill-save-task-state-in-saved_state.patch | 10 ++++---- ...e-blk_queue_usage_counter_release-in.patch | 16 ++++++------- ...-block-Use-cpu_chill-for-retry-loops.patch | 10 ++++---- ...cache-Use-cpu_chill-in-trylock-loops.patch | 10 ++++---- ...t-Use-cpu_chill-instead-of-cpu_relax.patch | 10 ++++---- ...use-swait_queue-instead-of-waitqueue.patch | 10 ++++---- .../0190-workqueue-Use-normal-rcu.patch | 10 ++++---- ...cal-irq-lock-instead-of-irq-disable-.patch | 10 ++++---- ...t-workqueue-versus-ata-piix-livelock.patch | 10 ++++---- ...tangle-worker-accounting-from-rqlock.patch | 10 ++++---- .../0194-debugobjects-Make-RT-aware.patch | 10 ++++---- .../0195-seqlock-Prevent-rt-starvation.patch | 10 ++++---- ...vc_xprt_do_enqueue-use-get_cpu_light.patch | 10 ++++---- ...0197-net-Use-skbufhead-with-raw-lock.patch | 20 ++++++++-------- ...recursion-to-per-task-variable-on-RT.patch | 14 +++++------ ...y-to-delegate-processing-a-softirq-t.patch | 14 +++++------ ...ake-qdisc-s-busylock-in-__dev_xmit_s.patch | 12 +++++----- ...Qdisc-use-a-seqlock-instead-seqcount.patch | 12 +++++----- ...-missing-serialization-in-ip_send_un.patch | 10 ++++---- .../0203-net-add-a-lock-around-icmp_sk.patch | 10 ++++---- ...schedule_irqoff-disable-interrupts-o.patch | 12 +++++----- ...-push-most-work-into-softirq-context.patch | 10 ++++---- .../0206-printk-Make-rt-aware.patch | 10 ++++---- ...n-t-try-to-print-from-IRQ-NMI-region.patch | 10 ++++---- ...intk-Drop-the-logbuf_lock-more-often.patch | 10 ++++---- ...n-translation-section-permission-fau.patch | 10 ++++---- ...-irq_set_irqchip_state-documentation.patch | 10 ++++---- ...wngrade-preempt_disable-d-region-to-.patch | 10 ++++---- ...-preemp_disable-in-addition-to-local.patch | 10 ++++---- ...13-kgdb-serial-Short-term-workaround.patch | 14 +++++------ ...-sysfs-Add-sys-kernel-realtime-entry.patch | 10 ++++---- .../0215-mm-rt-kmap_atomic-scheduling.patch | 12 +++++----- ...highmem-Add-a-already-used-pte-check.patch | 10 ++++---- .../0217-arm-highmem-Flush-tlb-on-unmap.patch | 10 ++++---- .../0218-arm-Enable-highmem-for-rt.patch | 10 ++++---- .../0219-scsi-fcoe-Make-RT-aware.patch | 12 +++++----- ...ypto-Reduce-preempt-disabled-regions.patch | 10 ++++---- ...-preempt-disabled-regions-more-algos.patch | 10 ++++---- ...ypto-limit-more-FPU-enabled-sections.patch | 10 ++++---- ...-serialize-RT-percpu-scratch-buffer-.patch | 10 ++++---- ...d-a-lock-instead-preempt_disable-loc.patch | 10 ++++---- ...andom_bytes-for-RT_FULL-in-init_oops.patch | 10 ++++---- ...ackprotector-Avoid-random-pool-on-rt.patch | 10 ++++---- .../0227-random-Make-it-work-on-rt.patch | 10 ++++---- ...28-cpu-hotplug-Implement-CPU-pinning.patch | 10 ++++---- ...ed-user-tasks-to-be-awakened-to-the-.patch | 10 ++++---- ...duct-tape-RT-rwlock-usage-for-non-RT.patch | 10 ++++---- ...ove-preemption-disabling-in-netif_rx.patch | 12 +++++----- ...r-local_irq_disable-kmalloc-headache.patch | 12 +++++----- ...-users-of-napi_alloc_cache-against-r.patch | 12 +++++----- ...rialize-xt_write_recseq-sections-on-.patch | 10 ++++---- ...-Only-do-hardirq-context-test-for-ra.patch | 10 ++++---- ...-fix-warnings-due-to-missing-PREEMPT.patch | 10 ++++---- ...ched-Add-support-for-lazy-preemption.patch | 10 ++++---- ...38-ftrace-Fix-trace-header-alignment.patch | 10 ++++---- ...0239-x86-Support-for-lazy-preemption.patch | 10 ++++---- ...-properly-check-against-preempt-mask.patch | 10 ++++---- ...-use-proper-return-label-on-32bit-x8.patch | 10 ++++---- ...-arm-Add-support-for-lazy-preemption.patch | 10 ++++---- ...erpc-Add-support-for-lazy-preemption.patch | 10 ++++---- ...-arch-arm64-Add-lazy-preempt-support.patch | 10 ++++---- ...c-Protect-send_msg-with-a-local-lock.patch | 10 ++++---- ...am-Replace-bit-spinlocks-with-rtmute.patch | 10 ++++---- ...-t-disable-preemption-in-zcomp_strea.patch | 10 ++++---- ...-zcomp_stream_get-smp_processor_id-u.patch | 10 ++++---- ...49-tpm_tis-fix-stall-after-iowrite-s.patch | 10 ++++---- ...t-deferral-of-watchdogd-wakeup-on-RT.patch | 10 ++++---- ...Use-preempt_disable-enable_rt-where-.patch | 10 ++++---- ...al_lock-unlock_irq-in-intel_pipe_upd.patch | 10 ++++---- .../0253-drm-i915-disable-tracing-on-RT.patch | 10 ++++---- ...M_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch | 10 ++++---- ...roups-use-simple-wait-in-css_release.patch | 10 ++++---- ...vert-callback_lock-to-raw_spinlock_t.patch | 10 ++++---- ...-a-locallock-instead-preempt_disable.patch | 10 ++++---- ...rkqueue-Prevent-deadlock-stall-on-RT.patch | 10 ++++---- ...t-tasks-to-cache-one-sigqueue-struct.patch | 10 ++++---- ...0260-Add-localversion-for-RT-release.patch | 10 ++++---- ...iommu-Use-a-locallock-instead-local_.patch | 10 ++++---- .../0262-powerpc-reshuffle-TIF-bits.patch | 10 ++++---- ...-Convert-show_lock-to-raw_spinlock_t.patch | 10 ++++---- ...isable-interrupts-independently-of-t.patch | 10 ++++---- ...-Fix-a-lockup-in-wait_for_completion.patch | 10 ++++---- ...6-kthread-add-a-global-worker-thread.patch | 12 +++++----- ...-arm-imx6-cpuidle-Use-raw_spinlock_t.patch | 10 ++++---- ...to-change-rcu_normal_after_boot-on-R.patch | 10 ++++---- ...chtec-fix-stream_open.cocci-warnings.patch | 10 ++++---- ...-Drop-a-preempt_disable_rt-statement.patch | 10 ++++---- ...notification-of-canceling-timers-on-.patch | 10 ++++---- ...ure-lock-unlock-symetry-versus-pi_lo.patch | 10 ++++---- ...-bug-on-when-a-requeued-RT-task-time.patch | 10 ++++---- ...andle-the-various-new-futex-race-con.patch | 10 ++++---- ...karound-migrate_disable-enable-in-di.patch | 10 ++++---- ...-Make-the-futex_hash_bucket-lock-raw.patch | 10 ++++---- ...futex-Delay-deallocation-of-pi_state.patch | 10 ++++---- ...disable-preemption-in-zswap_frontswa.patch | 10 ++++---- debian/patches-rt/0279-revert-aio.patch | 10 ++++---- .../0280-fs-aio-simple-simple-work.patch | 10 ++++---- debian/patches-rt/0281-revert-thermal.patch | 10 ++++---- ...rmal-Defer-thermal-wakups-to-threads.patch | 10 ++++---- debian/patches-rt/0283-revert-block.patch | 16 ++++++------- ...e-blk_queue_usage_counter_release-in.patch | 14 +++++------ debian/patches-rt/0285-workqueue-rework.patch | 16 ++++++------- ...0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch | 10 ++++---- ...0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch | 10 ++++---- ...nsure-inactive_timer-runs-in-hardirq.patch | 10 ++++---- ...temp-make-pkg_temp_lock-a-raw-spinlo.patch | 10 ++++---- ...lock_t-instread-disabling-preemption.patch | 10 ++++---- ...t-the-timer-expire-in-hardirq-contex.patch | 10 ++++---- ...k-preemption-level-before-looking-at.patch | 10 ++++---- ..._ONCE-to-access-timer-base-in-hrimer.patch | 10 ++++---- ...ab-the-expiry-lock-for-non-soft-hrti.patch | 10 ++++---- ...using-hrtimer_grab_expiry_lock-on-mi.patch | 10 ++++---- ...ssing-bracket-and-hide-migration_bas.patch | 10 ++++---- ...lock-expiry-lock-in-the-early-return.patch | 10 ++++---- ...s-enable-Use-sleeping_lock-to-annota.patch | 10 ++++---- ..._allowed_ptr-Check-cpus_mask-not-cpu.patch | 10 ++++---- ...Remove-dead-__migrate_disabled-check.patch | 10 ++++---- ...e-disable-Protect-cpus_ptr-with-lock.patch | 10 ++++---- ...processor_id-Don-t-use-cpumask_equal.patch | 10 ++++---- ...utex_hash_bucket-spinlock_t-again-an.patch | 10 ++++---- ...Clean-pi_blocked_on-in-the-error-cas.patch | 10 ++++---- ...ib-ubsan-Don-t-seralize-UBSAN-report.patch | 10 ++++---- ...the-lock-of-kmemleak_object-to-raw_s.patch | 10 ++++---- ...igrate_enable-Use-select_fallback_rq.patch | 10 ++++---- ...ched-Lazy-migrate_disable-processing.patch | 10 ++++---- ...grate_enable-Use-stop_one_cpu_nowait.patch | 10 ++++---- ...alize-split-page-table-locks-for-vec.patch | 10 ++++---- ...nlock_t-and-rwlock_t-a-RCU-section-o.patch | 10 ++++---- ...te_enable-must-access-takedown_cpu_t.patch | 10 ++++---- ...r_id-Adjust-check_preemption_disable.patch | 10 ++++---- ...able-Busy-loop-until-the-migration-r.patch | 10 ++++---- ...fd-Use-a-seqlock-instead-of-seqcount.patch | 10 ++++---- ...ate_enable-Use-per-cpu-cpu_stop_work.patch | 10 ++++---- ...igrate_enable-Remove-__schedule-call.patch | 10 ++++---- ...ve-misplaced-local_unlock_irqrestore.patch | 10 ++++---- ...Include-header-for-the-current-macro.patch | 10 ++++---- ...preempt_disable-in-vmw_fifo_ping_hos.patch | 10 ++++---- ...empt_lazy-and-migrate_disable-counte.patch | 10 ++++---- ...-flags-parameter-from-calls-to-ubsan.patch | 10 ++++---- ...cking-of-IRQ_WORK_LAZY-flag-set-on-n.patch | 10 ++++---- ...s-a-race-resulting-in-double-enqueue.patch | 10 ++++---- ...c-for-when-grabbing-softirq_expiry_l.patch | 10 ++++---- ...326-fs-dcache-Include-swait.h-header.patch | 10 ++++---- ...lush-the-delayed-empty-slubs-in-flus.patch | 12 +++++----- ...ix-UP-case-for-tasklet-CHAINED-state.patch | 10 ++++---- ...l-Prevent-double-free-of-user-struct.patch | 10 ++++---- ...e-sk_lock.slock-without-disabling-in.patch | 10 ++++---- ...phy-fixed_phy-Remove-unused-seqcount.patch | 10 ++++---- ...compress-vs-decompress-serialization.patch | 10 ++++---- .../0333-Linux-4.19.142-rt63-REBASE.patch | 24 ------------------- .../0333-Linux-4.19.148-rt64-REBASE.patch | 24 +++++++++++++++++++ debian/patches-rt/series | 2 +- 336 files changed, 1745 insertions(+), 1742 deletions(-) delete mode 100644 debian/patches-rt/0333-Linux-4.19.142-rt63-REBASE.patch create mode 100644 debian/patches-rt/0333-Linux-4.19.148-rt64-REBASE.patch diff --git a/debian/changelog b/debian/changelog index 3d4eec855..da90f42d6 100644 --- a/debian/changelog +++ b/debian/changelog @@ -316,6 +316,9 @@ linux (4.19.150-1) UNRELEASED; urgency=medium - netfilter: ctnetlink: add a range check for l3/l4 protonum (CVE-2020-25211) + [ Salvatore Bonaccorso ] + * [rt] Update to 4.19.148-rt64 + -- Salvatore Bonaccorso Sat, 26 Sep 2020 11:17:48 +0200 linux (4.19.146-1) buster; urgency=medium 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 be56a77bd..cc0142d0d 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 56457dc415803c8abc5acb513ada877a79596f05 Mon Sep 17 00:00:00 2001 -Message-Id: <56457dc415803c8abc5acb513ada877a79596f05.1599166690.git.zanussi@kernel.org> +From 5b5a156f9808b1acf1205606e03da117214549ea Mon Sep 17 00:00:00 2001 +Message-Id: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:18 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 9ab026de7..b9bf38d19 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 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 9601c73e796836f0e4995b3a8878c070fa14a426 Mon Sep 17 00:00:00 2001 +Message-Id: <9601c73e796836f0e4995b3a8878c070fa14a426.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:19 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 69c2d25ff..37eb643fe 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 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 42b40e1d3e5f024a54a52ca2d75f870856eb2883 Mon Sep 17 00:00:00 2001 +Message-Id: <42b40e1d3e5f024a54a52ca2d75f870856eb2883.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:20 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a6e928050..44267bdda 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 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 1cb03d0be840a377a276fcb93af00ca14e368ea3 Mon Sep 17 00:00:00 2001 +Message-Id: <1cb03d0be840a377a276fcb93af00ca14e368ea3.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:21 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 3db3fc0bb..a2fdc6787 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 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 f2388033261d286dab250792486ac6d35ef4debd Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:22 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 43b282f09..5e5756c95 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 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 cd51dd875a7890a01521872cff7c77fedc388d5d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:23 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 15b125ff6..55efabc48 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 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 a7cf71c310899fcf7ccb497523c3dbabe0d33e29 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:24 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 ba3d8d058..fe47913d1 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 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 893750b4d975db6ff5027e83b0b074d80e7e4b21 Mon Sep 17 00:00:00 2001 +Message-Id: <893750b4d975db6ff5027e83b0b074d80e7e4b21.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Marc Zyngier Date: Fri, 27 Jul 2018 13:38:54 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Signed-off-by: Marc Zyngier Signed-off-by: Sebastian Andrzej Siewior 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 0902e5617..6db5ad7cf 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 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 7acaf06745854341663cd864cfb9937b6dfa9191 Mon Sep 17 00:00:00 2001 +Message-Id: <7acaf06745854341663cd864cfb9937b6dfa9191.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 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 743451644..75948cf10 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 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 d3f7d145813c4f6653077757406b14c29e4602b4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: =?UTF-8?q?Horia=20Geant=C4=83?= Date: Mon, 8 Oct 2018 14:09:37 +0300 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1f533e815..f8cd08246 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 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 02ad2dc7b3e7455fff589d535860a01158187c44 Mon Sep 17 00:00:00 2001 +Message-Id: <02ad2dc7b3e7455fff589d535860a01158187c44.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 7 Jan 2019 13:52:31 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Traditionally hrtimer callbacks were run with IRQs disabled, but with the introduction of HRTIMER_MODE_SOFT it is possible they run from 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 d8abc6ddd..20bdf676c 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 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 1eb5155fc4010bc58095552970d78a0431a1ab6e Mon Sep 17 00:00:00 2001 +Message-Id: <1eb5155fc4010bc58095552970d78a0431a1ab6e.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Frank Rowand Date: Mon, 19 Sep 2011 14:51:14 -0700 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 fb7f39541..ec7af0966 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 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 7b86b7671128097bf9b6263e1adf0da06473a421 Mon Sep 17 00:00:00 2001 +Message-Id: <7b86b7671128097bf9b6263e1adf0da06473a421.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 17 Jul 2018 18:25:31 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz There is an issue with threaded interrupts which are marked ONESHOT and using the fasteoi handler. 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 1c7c9a476..b7c7db579 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 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 113b6618daafc3b405c7a605deaca3ece1dde64a Mon Sep 17 00:00:00 2001 +Message-Id: <113b6618daafc3b405c7a605deaca3ece1dde64a.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 18:19:48 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 3e867d154..062eafb5f 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 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 907edfcfd11e6d0abd649bec0ae245bf4b1360b7 Mon Sep 17 00:00:00 2001 +Message-Id: <907edfcfd11e6d0abd649bec0ae245bf4b1360b7.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 3 Jul 2018 13:34:30 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b46fa76ab..8d7eea61c 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 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 4eceb5976ca54ea43b1923f2963aaf5403241d03 Mon Sep 17 00:00:00 2001 +Message-Id: <4eceb5976ca54ea43b1923f2963aaf5403241d03.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 Aug 2018 21:59:04 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e93c9f72c..3d957d013 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 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 7d5f7a3f81e5f57fa225a75a6c74dbc75bff84c7 Mon Sep 17 00:00:00 2001 +Message-Id: <7d5f7a3f81e5f57fa225a75a6c74dbc75bff84c7.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 11 Oct 2018 16:39:59 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e1fa1b989..eb0c070dd 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 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 80801fff1262ef4fa587e9feb60b309244245d06 Mon Sep 17 00:00:00 2001 +Message-Id: <80801fff1262ef4fa587e9feb60b309244245d06.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:06:10 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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. 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 ea0be78ef..92332b4f6 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 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 37508b63607f0b631e77f9a60516ff1c6ac2c5a7 Mon Sep 17 00:00:00 2001 +Message-Id: <37508b63607f0b631e77f9a60516ff1c6ac2c5a7.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 24 Jul 2018 14:48:55 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a67d315a0..46eb41dfe 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 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 5be04164d1f7df6a214d2c3d2b5b7e07c7f259fb Mon Sep 17 00:00:00 2001 +Message-Id: <5be04164d1f7df6a214d2c3d2b5b7e07c7f259fb.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 09:13:42 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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(). 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 438317364..9b406cf9d 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 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 f2cacc38f730e9018d79d3c821b9a8af300a7ac2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 31 Aug 2018 14:16:30 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 804ea392b..285044d59 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 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 68d33342fc14ecd6e87ecbd0aea1573c0a3d88ce Mon Sep 17 00:00:00 2001 +Message-Id: <68d33342fc14ecd6e87ecbd0aea1573c0a3d88ce.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 18 Sep 2018 10:29:31 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f8fc22f99..9db2810c6 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 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 826426c0daabf1e601bbe81b30be496da4248e89 Mon Sep 17 00:00:00 2001 +Message-Id: <826426c0daabf1e601bbe81b30be496da4248e89.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 29 Oct 2018 11:53:01 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 7ec284b6b..d44e6cd94 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 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 0581998243c3cbcc9e83a2d234e9384a3732063b Mon Sep 17 00:00:00 2001 +Message-Id: <0581998243c3cbcc9e83a2d234e9384a3732063b.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: He Zhe Date: Wed, 19 Dec 2018 16:30:57 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f93ad2ccc..e3db5bd20 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 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 0c73de7e09baee2b357c00545e1cd953b2894b8b Mon Sep 17 00:00:00 2001 +Message-Id: <0c73de7e09baee2b357c00545e1cd953b2894b8b.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 28 Oct 2016 23:05:11 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1ef75b1deffa..44438814b662 100644 +index b2a2ff3f22a4..9af972fd1260 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 51cbe1c82..ae3db1547 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,7 +1,7 @@ -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 9c54177a10dfa0874eed8214a9c125fc872a0da4 Mon Sep 17 00:00:00 2001 +Message-Id: <9c54177a10dfa0874eed8214a9c125fc872a0da4.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Apr 2017 12:50:16 +0200 Subject: [PATCH 026/333] kernel: sched: Provide a pointer to the valid CPU @@ -9,7 +9,7 @@ Subject: [PATCH 026/333] kernel: sched: Provide a pointer to the valid CPU 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 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 03e2c31af..30c871870 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 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 53f10af8e401301257ec2ee11638597f7fce2b04 Mon Sep 17 00:00:00 2001 +Message-Id: <53f10af8e401301257ec2ee11638597f7fce2b04.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1536c26cd..c21d58c7e 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 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 22aac3ed2b0414b1acd6c8638532c632a1486dc4 Mon Sep 17 00:00:00 2001 +Message-Id: <22aac3ed2b0414b1acd6c8638532c632a1486dc4.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 9 Oct 2018 17:34:50 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c9334cfd3..fdf451705 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 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 46cd243e812d50776438c4e4be19343985b58511 Mon Sep 17 00:00:00 2001 +Message-Id: <46cd243e812d50776438c4e4be19343985b58511.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Mar 2016 10:51:06 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 25dbe15bc..51a875150 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,7 +1,7 @@ -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 0a04e69e05ac7eec96dfe1714aa636c2bf8fa8e1 Mon Sep 17 00:00:00 2001 +Message-Id: <0a04e69e05ac7eec96dfe1714aa636c2bf8fa8e1.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Benedikt Spranger Date: Mon, 8 Mar 2010 18:57:04 +0100 Subject: [PATCH 030/333] clocksource: TCLIB: Allow higher clock rates for @@ -9,7 +9,7 @@ Subject: [PATCH 030/333] clocksource: TCLIB: Allow higher clock rates for 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4cf73ed3c..dfb67abb7 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 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 0bda092df133445692f77e6eb13149493b3464a2 Mon Sep 17 00:00:00 2001 +Message-Id: <0bda092df133445692f77e6eb13149493b3464a2.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 14 Feb 2013 22:36:59 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1c32824b1..d73e708e0 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 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 e87e30a754eaaeae393934e4d25104a8739a4b20 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 21 Sep 2011 19:57:12 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 35c8321a5..a51ef2e60 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 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 36f709429024a0e49967d177b45571c03ce08224 Mon Sep 17 00:00:00 2001 +Message-Id: <36f709429024a0e49967d177b45571c03ce08224.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Marc Kleine-Budde Date: Wed, 5 Mar 2014 00:49:47 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 @@ -50,10 +50,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c -index 119e20cad662..49d60ae006ed 100644 +index bd96fd261dba..06681749e736 100644 --- a/net/sched/sch_generic.c +++ b/net/sched/sch_generic.c -@@ -1205,7 +1205,7 @@ void dev_deactivate_many(struct list_head *head) +@@ -1222,7 +1222,7 @@ void dev_deactivate_many(struct list_head *head) /* Wait for outstanding qdisc_run calls. */ list_for_each_entry(dev, head, close_list) { while (some_qdisc_is_busy(dev)) 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 c28056fe1..2673f513c 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 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 0b2ecf29a3e8d184251a5103ef5bf728da1b45d5 Mon Sep 17 00:00:00 2001 +Message-Id: <0b2ecf29a3e8d184251a5103ef5bf728da1b45d5.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 27 Mar 2018 16:24:15 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz In commit 052189a2ec95 ("dm: remove superfluous irq disablement in dm_request_fn") the spin_lock_irq() was replaced with spin_lock() + a 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 66909c9f5..6b1481003 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 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 3254821606ce89fd2a2d2bbd115d6b4e61f7cd9b Mon Sep 17 00:00:00 2001 +Message-Id: <3254821606ce89fd2a2d2bbd115d6b4e61f7cd9b.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 8 Nov 2013 17:34:54 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 8984c74c9..7b8069946 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 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 b67f13e65cdfce55fab8dec3f7d102bf90e0fff3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 17 Jun 2011 12:39:57 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 bacb0a755..ddaad65b9 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 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 7217f43a5aaf863ebd4df662f4d2453562c8721a Mon Sep 17 00:00:00 2001 +Message-Id: <7217f43a5aaf863ebd4df662f4d2453562c8721a.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 14 Dec 2011 01:03:49 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 65c974136..214cae22b 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 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 f4cfac959fba1f75f59bb559f5035aa5bde2fbb5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Jul 2015 17:14:48 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 d23b0b369..e486fe9f2 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 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 eaa408409fc872f1733be1d947694d0cc9dda051 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 24 Jul 2011 12:11:43 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 d5444a63d..cf55a8ae7 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 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 e873744bd9dbed2fe6adbc9564523ce662a411aa Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 17 Oct 2017 16:36:18 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 93e0438d3..775cb01db 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 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 f6ed1d9c5fd3121b1cf5bb8420a4c65f98368d01 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:44:03 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 cc192393e..dbfbf955a 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 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 228791648695b2759d55863d0e829300e310d40c Mon Sep 17 00:00:00 2001 +Message-Id: <228791648695b2759d55863d0e829300e310d40c.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:51:45 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 9f82de543..6c560d5ef 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 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 4464f6a0589d85537759211cb2306c57b3a40486 Mon Sep 17 00:00:00 2001 +Message-Id: <4464f6a0589d85537759211cb2306c57b3a40486.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 13:26:09 +0000 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 72dc16296..a807cc950 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 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 4f6896ee6bf4db91d7fc81932bf1ca231229040b Mon Sep 17 00:00:00 2001 +Message-Id: <4f6896ee6bf4db91d7fc81932bf1ca231229040b.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Mar 2014 20:19:05 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 52548276f..4cd145d50 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 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 2669d27db140f86ef0c46ef918410177f47972ba Mon Sep 17 00:00:00 2001 +Message-Id: <2669d27db140f86ef0c46ef918410177f47972ba.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:03:52 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 7ba520e07..d100d7202 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 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 38f41dbb9b916164ca83db92c6860ab954a58cd1 Mon Sep 17 00:00:00 2001 +Message-Id: <38f41dbb9b916164ca83db92c6860ab954a58cd1.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b986ba061..763ed162e 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 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 97d941c3c75bfd4f49bcd1b2603dd84425bdc0eb Mon Sep 17 00:00:00 2001 +Message-Id: <97d941c3c75bfd4f49bcd1b2603dd84425bdc0eb.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 1 Dec 2017 10:42:03 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 3660414b1..731438cc6 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 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 1e2d0fb0b52481f5994e5b507f55e9d1068c37ea Mon Sep 17 00:00:00 2001 +Message-Id: <1e2d0fb0b52481f5994e5b507f55e9d1068c37ea.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 54f21b50b..9b1575077 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 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 d36893e7a64c088079862d7349e04eacdfc81158 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Bogdan Purcareata Date: Fri, 24 Apr 2015 15:53:13 +0000 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 8d6f0a3b7..3df28a15b 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 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 89b72036770c4fa874e51ba6f1f89533902784ba Mon Sep 17 00:00:00 2001 +Message-Id: <89b72036770c4fa874e51ba6f1f89533902784ba.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:08:34 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c90dbf709..04574c167 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 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 cb00db21219a3e808f12dff1ed229b5bbce58ad7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:10:12 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz The current highmem handling on -RT is not compatible and needs fixups. @@ -15,10 +15,10 @@ Signed-off-by: Thomas Gleixner 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig -index a830a9701e50..3d5fae3891be 100644 +index cc8c8d22afaf..9f9e8fae334d 100644 --- a/arch/mips/Kconfig +++ b/arch/mips/Kconfig -@@ -2518,7 +2518,7 @@ config MIPS_CRC_SUPPORT +@@ -2519,7 +2519,7 @@ config MIPS_CRC_SUPPORT # config HIGHMEM bool "High Memory Support" 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 5523fb947..bd76a1010 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 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 e71d45902a41d30eabcc83a39243440f76d610f0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 26 Jul 2009 02:21:32 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 729e5150d..0e6e674ac 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 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 534e3497ce877345f3f2a93a090f164eec826d10 Mon Sep 17 00:00:00 2001 +Message-Id: <534e3497ce877345f3f2a93a090f164eec826d10.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 23 Jan 2014 14:45:59 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4a9f358be..b21266ab3 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 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 4358b17e5f47fc4b999796c3593a865a8e41507a Mon Sep 17 00:00:00 2001 +Message-Id: <4358b17e5f47fc4b999796c3593a865a8e41507a.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 9 Apr 2015 15:23:01 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b1e45cfa9..b61d830b4 100644 --- a/debian/patches-rt/0055-md-disable-bcache.patch +++ b/debian/patches-rt/0055-md-disable-bcache.patch @@ -1,14 +1,14 @@ -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 179303a9c436686b3229b062198ea9e188b1d2ec Mon Sep 17 00:00:00 2001 +Message-Id: <179303a9c436686b3229b062198ea9e188b1d2ec.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 11:48:57 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 0511dfd87..048094017 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 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 72502cdee1e1aa8c752321e8932d33aba10ba327 Mon Sep 17 00:00:00 2001 +Message-Id: <72502cdee1e1aa8c752321e8932d33aba10ba327.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:03:16 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Based on meassurements the EFI functions get_variable / get_next_variable take up to 2us which looks okay. 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 168f9ce69..0efbc371b 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 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 63e0e7b2d6fd6bf9ec8e39c77fd05349fc6f5833 Mon Sep 17 00:00:00 2001 +Message-Id: <63e0e7b2d6fd6bf9ec8e39c77fd05349fc6f5833.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 22 Jul 2011 17:58:40 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f20db26af..d9c2b3b85 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 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 41b78fc339260091839e54f53feaa80d2551486d Mon Sep 17 00:00:00 2001 +Message-Id: <41b78fc339260091839e54f53feaa80d2551486d.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Peter Zijlstra Date: Fri, 2 Sep 2011 14:41:29 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 8c7be2c08..7aba89711 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 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 8e0731033be0ec76e778f8842bc560171c0c2706 Mon Sep 17 00:00:00 2001 +Message-Id: <8e0731033be0ec76e778f8842bc560171c0c2706.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 24 Jul 2009 12:38:56 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 52b2ebbd7..9d1be5da1 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 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 072768e7c1a02d208981cf6084b03594c1e10b81 Mon Sep 17 00:00:00 2001 +Message-Id: <072768e7c1a02d208981cf6084b03594c1e10b81.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Mar 2017 14:23:35 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 fde9dd5fc..6cb55294b 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 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 2efff859badb5a9faaf8d305286f0640530b6b04 Mon Sep 17 00:00:00 2001 +Message-Id: <2efff859badb5a9faaf8d305286f0640530b6b04.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 20 Jun 2011 09:03:47 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b2330ca38..804440b36 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 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 911aaa10543fb610a948db94025c5c2a337b3c0a Mon Sep 17 00:00:00 2001 +Message-Id: <911aaa10543fb610a948db94025c5c2a337b3c0a.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:56 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a17d8444b..f5994369b 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 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 16afa640570f09ecf21c1aac9404030304439bb4 Mon Sep 17 00:00:00 2001 +Message-Id: <16afa640570f09ecf21c1aac9404030304439bb4.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:34 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 743dfec6d..b02ee3d99 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 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 c57001cf8ea1948b070218f85ba09f0ec0dae47b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Oleg Nesterov Date: Tue, 14 Jul 2015 14:26:34 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 d62d1b301..e49cfa405 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 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 28030eba61e8c4a4dd506cb8066b0dc0c3936edd Mon Sep 17 00:00:00 2001 +Message-Id: <28030eba61e8c4a4dd506cb8066b0dc0c3936edd.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Yang Shi Date: Thu, 10 Dec 2015 10:58:51 -0800 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1fd7db1ad..d9900f5ce 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 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 0234ffb83adb4ab4ccc78264e5c22edaa67bb110 Mon Sep 17 00:00:00 2001 +Message-Id: <0234ffb83adb4ab4ccc78264e5c22edaa67bb110.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 09:18:52 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Wrap the bit_spin_lock calls into a separate inline and add the RT replacements with a real spinlock. @@ -19,7 +19,7 @@ Signed-off-by: Thomas Gleixner 4 files changed, 46 insertions(+), 25 deletions(-) diff --git a/fs/buffer.c b/fs/buffer.c -index c49fdab5cb36..b649c4d58637 100644 +index 362a86876459..87e38a32306f 100644 --- a/fs/buffer.c +++ b/fs/buffer.c @@ -274,8 +274,7 @@ static void end_buffer_async_read(struct buffer_head *bh, int uptodate) @@ -81,7 +81,7 @@ index c49fdab5cb36..b649c4d58637 100644 } EXPORT_SYMBOL(end_buffer_async_write); -@@ -3379,6 +3371,7 @@ struct buffer_head *alloc_buffer_head(gfp_t gfp_flags) +@@ -3388,6 +3380,7 @@ struct buffer_head *alloc_buffer_head(gfp_t gfp_flags) struct buffer_head *ret = kmem_cache_zalloc(bh_cachep, gfp_flags); if (ret) { INIT_LIST_HEAD(&ret->b_assoc_buffers); 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 9cf59d443..3edbcecce 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 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 534f9a4f05a4c9a53245b93eb3db2e4fe1d48307 Mon Sep 17 00:00:00 2001 +Message-Id: <534f9a4f05a4c9a53245b93eb3db2e4fe1d48307.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 10:11:25 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 7a9aa947b..ed254e396 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 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 5285cd46bea76913bdc462813c1be23a338d0550 Mon Sep 17 00:00:00 2001 +Message-Id: <5285cd46bea76913bdc462813c1be23a338d0550.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Paul Gortmaker Date: Fri, 21 Jun 2013 15:07:25 -0400 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 83a987de0..d1e8651ed 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 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 4302701f88b3dc4409cb42c9c72ccec51636b3b8 Mon Sep 17 00:00:00 2001 +Message-Id: <4302701f88b3dc4409cb42c9c72ccec51636b3b8.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 31 Mar 2016 00:04:25 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 bf1345654..3388fc1d3 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 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 52108bd55c31c7031f0cc8905fe05b3169d1e8e7 Mon Sep 17 00:00:00 2001 +Message-Id: <52108bd55c31c7031f0cc8905fe05b3169d1e8e7.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:57 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e74448e67..967dcd8a7 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 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 c1b28bb8f50094efbe5559063497ea1f27c33672 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 3 Apr 2011 11:57:29 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Force threaded_irqs and optimize the code (force_irqthreads) in regard to this. 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 dd804cc91..8cceb2a4d 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 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 1480ec4e31aa27432f04bd35c1b7eea2c53386b3 Mon Sep 17 00:00:00 2001 +Message-Id: <1480ec4e31aa27432f04bd35c1b7eea2c53386b3.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:20 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. 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 ed58e8578..0382ff233 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 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 0ef546de30c37e30a0236aeb1732dd95ed8bd26e Mon Sep 17 00:00:00 2001 +Message-Id: <0ef546de30c37e30a0236aeb1732dd95ed8bd26e.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:21 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. 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 cf9eeecea..f2969cf3c 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 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 97e80225ca2121e87f135c067204234ac6a33dc5 Mon Sep 17 00:00:00 2001 +Message-Id: <97e80225ca2121e87f135c067204234ac6a33dc5.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 28 May 2018 15:24:22 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 @@ -402,7 +402,7 @@ index 9632772e14be..d6b01d61f768 100644 #ifdef CONFIG_SLAB struct list_head slabs_partial; /* partial list first, better asm code */ diff --git a/mm/slub.c b/mm/slub.c -index 882a1e0ae89c..66416eff4818 100644 +index dfc9b4267603..0e391657e6ba 100644 --- a/mm/slub.c +++ b/mm/slub.c @@ -1181,7 +1181,7 @@ static noinline int free_debug_processing( 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 861352e19..3fe75fc68 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 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 728f5b03cee94e1fe198bf2e59a6b8211e9322e6 Mon Sep 17 00:00:00 2001 +Message-Id: <728f5b03cee94e1fe198bf2e59a6b8211e9322e6.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 21 Jun 2018 17:29:19 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz __free_slab() is invoked with disabled interrupts which increases the irq-off time while __free_pages() is doing the work. @@ -21,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 69 insertions(+), 5 deletions(-) diff --git a/mm/slub.c b/mm/slub.c -index 66416eff4818..b890fe5f9cd3 100644 +index 0e391657e6ba..f613c501ccbf 100644 --- a/mm/slub.c +++ b/mm/slub.c @@ -1349,6 +1349,12 @@ static bool freelist_corrupted(struct kmem_cache *s, struct page *page, 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 63e19fcbd..b3018702f 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 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 bba668c3f3b781ed69a6664b3f53634c778d4fc0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:37 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz rt-friendly per-cpu pages: convert the irqs-off per-cpu locking method into a preemptible, explicit-per-cpu-locks method. 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 4fe65a657..487937b94 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 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 586f9ddaabc928736127ef2dd08127ab71596283 Mon Sep 17 00:00:00 2001 +Message-Id: <586f9ddaabc928736127ef2dd08127ab71596283.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:51 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Replace global locks (get_cpu + local_irq_save) with "local_locks()". Currently there is one of for "rotate" and one for "swap". 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 6d7d9cf41..538c6c565 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 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 2550950c6c0faba9185504e84e2712df5b653b9c Mon Sep 17 00:00:00 2001 +Message-Id: <2550950c6c0faba9185504e84e2712df5b653b9c.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Luiz Capitulino Date: Fri, 27 May 2016 15:03:28 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 9ad11c77c..509017ead 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 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 f578676705cfd5a2faed7544dcb2973c46bc2c71 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:30:13 -0500 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 fe05ab855..706e0df57 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 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 2ce88b0fa9e476ef69ea181dbd71e56e59f84f38 Mon Sep 17 00:00:00 2001 +Message-Id: <2ce88b0fa9e476ef69ea181dbd71e56e59f84f38.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Frank Rowand Date: Sat, 1 Oct 2011 18:58:13 -0700 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4253ef827..890c5954b 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 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 c9de59c5101c541781f89f8078ad9096044722ca Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 25 Oct 2012 10:32:35 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Avoid the memory allocation in IRQ section @@ -17,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 6 insertions(+) diff --git a/mm/slub.c b/mm/slub.c -index b890fe5f9cd3..d33c04a0e5da 100644 +index f613c501ccbf..b1201a491169 100644 --- a/mm/slub.c +++ b/mm/slub.c @@ -3726,6 +3726,11 @@ static void list_slab_objects(struct kmem_cache *s, struct page *page, 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 d79ff2b92..4c1906982 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 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 28b059934bf7e456de1f9388d3bb08544243ac57 Mon Sep 17 00:00:00 2001 +Message-Id: <28b059934bf7e456de1f9388d3bb08544243ac57.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 9 Jan 2013 12:08:15 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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. @@ -16,7 +16,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/mm/slub.c b/mm/slub.c -index d33c04a0e5da..af485aba93ec 100644 +index b1201a491169..362ec0e00f89 100644 --- a/mm/slub.c +++ b/mm/slub.c @@ -1589,10 +1589,17 @@ static struct page *allocate_slab(struct kmem_cache *s, gfp_t flags, int node) 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 cdb7d7ae5..32cb03978 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 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 cafe55a662d439fb2d2d632518fc7eb2bb3d2ec1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Apr 2015 19:00:47 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 19028dbf2..1a9c6a544 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 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 e9b26e53036739f1afc417a458a2e6e29aa1c44c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Yang Shi Date: Wed, 30 Oct 2013 11:48:33 -0700 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c4e30a82e..0abb82520 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 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 c4d4433e8168725733a13aa4cdd13c5c424c307e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 28 Jan 2015 17:14:16 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 711b4d0c3..51cf53bfa 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 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 90dd974e68bca3011ed396fbf8d95bdc8ecdb5a6 Mon Sep 17 00:00:00 2001 +Message-Id: <90dd974e68bca3011ed396fbf8d95bdc8ecdb5a6.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Tue, 22 Mar 2016 11:16:09 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 562e2e2f9..141f23b0a 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 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 4dd5348c4bdfbc53044d46d1d9ffb628b317576b Mon Sep 17 00:00:00 2001 +Message-Id: <4dd5348c4bdfbc53044d46d1d9ffb628b317576b.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 21:53:43 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b06e2ce34..c16cfa37a 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 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 3137cff0109270859340ddeba6762658e7e3ed2c Mon Sep 17 00:00:00 2001 +Message-Id: <3137cff0109270859340ddeba6762658e7e3ed2c.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jan 2017 16:34:27 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c85f33623..4100ceea0 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 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 f5b8bffc2c6c9158ce9618fa1240c9fe03a321ab Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 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 bc3223b66..949c3cc03 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 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 9222ac2b775d574c69517691181d8e090cddaf98 Mon Sep 17 00:00:00 2001 +Message-Id: <9222ac2b775d574c69517691181d8e090cddaf98.1601675151.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 6 Nov 2011 12:26:18 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Non constant TSC is a nightmare on bare metal already, but with virtualization it becomes a complete disaster because the workarounds 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 b5f5b6993..43e00db4c 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 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 ba2727eeebcfa7443347cf6d1370979a821329f0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Oct 2017 10:24:23 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 0d6187927..f61b11fe3 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 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 b99bdc942f3823ba51d43e3b85f4fb5f4612e97d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 28 Oct 2013 12:19:57 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 3e57516ae..e1a320996 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 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 601b58fabd7dfaaafd57b272afe30ffa3fc58046 Mon Sep 17 00:00:00 2001 +Message-Id: <601b58fabd7dfaaafd57b272afe30ffa3fc58046.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Daniel Wagner Date: Fri, 11 Jul 2014 15:26:11 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 68134fc6e..68d37d969 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 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 a17768fa198546bd6c3937a75fd397309ccfc634 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 10 Sep 2018 18:00:31 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 7cd933860..ae3a24e2b 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 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 e2f5989ceb39d5a71dcfdadfed1cfc80f8ed65e0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 11 Jan 2013 11:23:51 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 7321693d2..f2eebef15 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 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 fd6441bf26dd614b3e814278771bc0d9268cffab Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 cdbc35f7a..08b50b180 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 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 544072d53620d0328b2aa9e5c0c337e516a797eb Mon Sep 17 00:00:00 2001 +Message-Id: <544072d53620d0328b2aa9e5c0c337e516a797eb.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Nov 2017 17:29:51 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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. 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 23cd11d60..0b0cb97bd 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 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 a612ff27292016e74ec5c87f49b663429de4d84b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 11:25:41 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz hrtimer_init_sleeper() calls require a prior initialisation of the hrtimer object with hrtimer_init(). Lets make the initialisation of @@ -31,10 +31,10 @@ Signed-off-by: Anna-Maria Gleixner 7 files changed, 67 insertions(+), 34 deletions(-) diff --git a/block/blk-mq.c b/block/blk-mq.c -index 684acaa96db7..4aa3284874f6 100644 +index db2db0b70d34..eae78363c036 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c -@@ -3128,10 +3128,9 @@ static bool blk_mq_poll_hybrid_sleep(struct request_queue *q, +@@ -3137,10 +3137,9 @@ static bool blk_mq_poll_hybrid_sleep(struct request_queue *q, kt = nsecs; mode = HRTIMER_MODE_REL; diff --git a/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch b/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch index 48d232fa0..8346c1c8f 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 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 f1557c3fccc7df9a610f2467f3e48701c03267f8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6212916aa..d6faf3c20 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 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 bef74767e6804ec7b1cda2a131895c35a6496de7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 3 Jul 2009 08:44:31 -0500 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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. 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 6214d199e..c24a22caf 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 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 13f1c058e87c10e20a3a71ae4b264739b6dc2759 Mon Sep 17 00:00:00 2001 +Message-Id: <13f1c058e87c10e20a3a71ae4b264739b6dc2759.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 8 Jan 2019 12:31:06 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Since commit "sched/fair: Robustify CFS-bandwidth timer locking" both hrtimer can run in softirq context because now interrupts are disabled 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 167793047..ffbfe7d84 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 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 c85867b46de81ad6b5de153743cf4cfc42814d3b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Yang Shi Date: Mon, 16 Sep 2013 14:09:19 -0700 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e37c92b29..33f1ea3f5 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 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 9cd956207af8d33ed94d04f5da3094abe522da4a Mon Sep 17 00:00:00 2001 +Message-Id: <9cd956207af8d33ed94d04f5da3094abe522da4a.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 10:15:13 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 825bbfeb1..55a5f15c9 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 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 236db40535158dec4a4181b1de982e0f3eeb81bf Mon Sep 17 00:00:00 2001 +Message-Id: <236db40535158dec4a4181b1de982e0f3eeb81bf.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: John Stultz Date: Fri, 3 Jul 2009 08:29:58 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6c9311f71..6e5b19aac 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 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 3370c869acd8725ed7ff841e822277d85c74f3fb Mon Sep 17 00:00:00 2001 +Message-Id: <3370c869acd8725ed7ff841e822277d85c74f3fb.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 May 2011 16:59:16 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 572f97b03..9113b62c4 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 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 87b9a848137c6f7340c4b6de4672f88f0f21753c Mon Sep 17 00:00:00 2001 +Message-Id: <87b9a848137c6f7340c4b6de4672f88f0f21753c.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:12:51 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6d2233e82..43e1c9292 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 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 c3c52cd587d395b046d02e9abbc0569b66f78ade Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:20:33 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f85da1aa5..cd10d7051 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 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 e71acb0a092bf3c2381586a3f9368df59ed9ce0b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 21 Nov 2016 19:31:08 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b5f4495a9..4efb75a4c 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 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 3dc003deb62cfddd8cfe666440d10e8abaa9e136 Mon Sep 17 00:00:00 2001 +Message-Id: <3dc003deb62cfddd8cfe666440d10e8abaa9e136.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 25 Jun 2011 09:21:04 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4bab9b375..a8acc9348 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 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 c1079fcb888f7bbdef9e2d4cc03c1d4eb26e4dd5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 7 Jun 2011 09:19:06 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 5719f7383..2bd4a67e4 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 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 5c6b0c3cb093782507f05fbbe7e070641a69ab45 Mon Sep 17 00:00:00 2001 +Message-Id: <5c6b0c3cb093782507f05fbbe7e070641a69ab45.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 22:51:33 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 51143d158..6cf9e2920 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 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 2da008bff531c75e9350d50965f3f40c98666141 Mon Sep 17 00:00:00 2001 +Message-Id: <2da008bff531c75e9350d50965f3f40c98666141.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Sep 2011 16:42:35 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 63299d290..ca39f8539 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 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 8d1a7c12a52fa392744d952a28ff00f63fbc9acf Mon Sep 17 00:00:00 2001 +Message-Id: <8d1a7c12a52fa392744d952a28ff00f63fbc9acf.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Steven Rostedt Date: Mon, 18 Mar 2013 15:12:49 -0400 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f442faa10..58eaeef55 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 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 f059bfda07206762f855a897add57bace1d1d804 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Daniel Bristot de Oliveira Date: Mon, 26 Jun 2017 17:07:15 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a061b2cda..0844ab309 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 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 b3a7ab13e3187b7ea588dac54fff962b61f6fc44 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 15 Jun 2011 12:36:06 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6c8a8956a..249fa2b2c 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 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 241f130e3d3edb242e471114b6c994f98c32abf2 Mon Sep 17 00:00:00 2001 +Message-Id: <241f130e3d3edb242e471114b6c994f98c32abf2.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:56:42 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Signed-off-by: Thomas Gleixner --- 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 49bb43808..1291aa2ac 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 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 7edb870b3cb0a0754dba67e4d755931b5fd9b05a Mon Sep 17 00:00:00 2001 +Message-Id: <7edb870b3cb0a0754dba67e4d755931b5fd9b05a.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 18:51:23 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 62b62ed7a..5594b233c 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 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 7496fadd5f981a9e7bbb38380d561448307988b1 Mon Sep 17 00:00:00 2001 +Message-Id: <7496fadd5f981a9e7bbb38380d561448307988b1.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Tue, 29 Nov 2011 20:18:22 -0500 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 80fa57228..9fad0ac83 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 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 b8da8f10f28090fcdfddedacbdd1de2a1f0a661c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 13 Nov 2011 17:17:09 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 42ba150fa18d..4ae89dc192d9 100644 +index c77d12a35f92..ccedc620795c 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -2723,6 +2723,7 @@ static void __netif_reschedule(struct Qdisc *q) @@ -170,7 +170,7 @@ index 42ba150fa18d..4ae89dc192d9 100644 } EXPORT_SYMBOL(__napi_schedule); -@@ -9502,6 +9508,7 @@ static int dev_cpu_dead(unsigned int oldcpu) +@@ -9503,6 +9509,7 @@ static int dev_cpu_dead(unsigned int oldcpu) raise_softirq_irqoff(NET_TX_SOFTIRQ); local_irq_enable(); 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 8b3454d6e..21345a0c4 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 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 853cef9f353435f2935dcc1e8b749db3f52f7931 Mon Sep 17 00:00:00 2001 +Message-Id: <853cef9f353435f2935dcc1e8b749db3f52f7931.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 13:59:17 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 5d226e269..7d47fe101 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 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 cce5eefc8e4fa9f0d3196fa267c8fab21b013944 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 4 Oct 2012 14:20:47 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a29983a30..bb47c0eb1 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 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 5140dcf50322edf0cdf99c17c7f83650a11b20bd Mon Sep 17 00:00:00 2001 +Message-Id: <5140dcf50322edf0cdf99c17c7f83650a11b20bd.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 16 Jun 2017 19:03:16 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4ae89dc192d9..e89ae804e68a 100644 +index ccedc620795c..414e4d7e2082 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 91d26a22a..956e5cabd 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 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 5c4e6f2122b008584d40bb4407ea17ed73f2bb71 Mon Sep 17 00:00:00 2001 +Message-Id: <5c4e6f2122b008584d40bb4407ea17ed73f2bb71.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 Jan 2012 13:01:27 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 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 1dc698c0b..31e0a0a08 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 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 49f18e2c713b8436eeca3e512a1140a5cbf8a410 Mon Sep 17 00:00:00 2001 +Message-Id: <49f18e2c713b8436eeca3e512a1140a5cbf8a410.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 16:34:17 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 5c46ebad7..049991065 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 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 4896dd79dae04b0e05c498f65d29484e736ec6d9 Mon Sep 17 00:00:00 2001 +Message-Id: <4896dd79dae04b0e05c498f65d29484e736ec6d9.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 13:19:59 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c4d402c8c..01a3169ca 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 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 7b2253e18e2c8432070fd4e2278c0759ca420b6d Mon Sep 17 00:00:00 2001 +Message-Id: <7b2253e18e2c8432070fd4e2278c0759ca420b6d.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:49:29 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 69644642c..423bfc531 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 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 e0b7d6339dd96e6b9922048da85540479e5615aa Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 2 Dec 2015 11:34:07 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 0ab5b09b2..e4544f1a3 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 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 3b7df566d21ac5302a371ca594ce659071abcbeb Mon Sep 17 00:00:00 2001 +Message-Id: <3b7df566d21ac5302a371ca594ce659071abcbeb.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 15 Sep 2016 10:51:27 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 735c4ba09..b4b750fd1 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 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 e0380df606a5e9e6d2d260f3e2d4155a7b6cc2a8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 10 Jun 2011 11:04:15 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 073fb6c5a..bbe6e2f23 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 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 d3b65f7cdd105c7cb4cc45916133c90dc33a392a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 14 Jul 2015 14:26:34 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 2e2e663dd..021f43e61 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 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 6eafea725b5f152e852f61bc367309f61e586217 Mon Sep 17 00:00:00 2001 +Message-Id: <6eafea725b5f152e852f61bc367309f61e586217.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 1 Mar 2013 11:17:42 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6abd2863b..6a701bf7e 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 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 37d9448e73791c1d15bdbd914a228972dff7bba9 Mon Sep 17 00:00:00 2001 +Message-Id: <37d9448e73791c1d15bdbd914a228972dff7bba9.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Grygorii Strashko Date: Tue, 21 Jul 2015 19:43:56 +0300 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 45dcb1218..f7773fe28 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 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 1559f50a96f5dd8ef4a3a5eb882e9570d0127c18 Mon Sep 17 00:00:00 2001 +Message-Id: <1559f50a96f5dd8ef4a3a5eb882e9570d0127c18.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 22 Dec 2016 17:28:33 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6fd776bd6..b522d5420 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 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 9bfffdb255bc8445c01e10430429afccdfd6907c Mon Sep 17 00:00:00 2001 +Message-Id: <9bfffdb255bc8445c01e10430429afccdfd6907c.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Wolfgang M. Reimer" Date: Tue, 21 Jul 2015 16:20:07 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 231fdd5cc..f1d7d22bc 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 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 bea8b6bd7eb5c825f9bda45b062e7f646eb96514 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 9 Jun 2011 11:43:52 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 403158c39..96bc50d5f 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 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 69f3eefe8e71ce7848f534eaa6c3811c82de607c Mon Sep 17 00:00:00 2001 +Message-Id: <69f3eefe8e71ce7848f534eaa6c3811c82de607c.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 1 Apr 2017 12:50:59 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f239385f9..fca28298e 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 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 511d9edc185a5cee805f29901abcafb55dc1cb7b Mon Sep 17 00:00:00 2001 +Message-Id: <511d9edc185a5cee805f29901abcafb55dc1cb7b.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 19:34:01 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 410d57d63..159e9fd86 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 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 9fed1bc29a9ebe11efc83c5dc068a45fa7d0c3c8 Mon Sep 17 00:00:00 2001 +Message-Id: <9fed1bc29a9ebe11efc83c5dc068a45fa7d0c3c8.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 20:06:39 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 384dae893..5ec110601 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 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 ba1606a46ad4d99deaf51539cd49b3fe67f8900f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 16:56:02 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 d6d1a5472..54cfcf5f7 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 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 0c616224baf33cb87b0484aa64f638777e6b3e7f Mon Sep 17 00:00:00 2001 +Message-Id: <0c616224baf33cb87b0484aa64f638777e6b3e7f.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:14:22 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 d8bcb211c..73380e7b9 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 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 09a21f06ec0147ccc3d5b06bf8f7af99468beff7 Mon Sep 17 00:00:00 2001 +Message-Id: <09a21f06ec0147ccc3d5b06bf8f7af99468beff7.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:36:39 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 27fd200a1..0ac344b23 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 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 d926dc2fb25d9379235944ce4c4224792a270a53 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:11:19 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b82ad9c37..49d249218 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 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 40674f4a9187e29b9fbdd64eb3dd28985ea962bf Mon Sep 17 00:00:00 2001 +Message-Id: <40674f4a9187e29b9fbdd64eb3dd28985ea962bf.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:17:03 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 20f9ad1f3..5b62b9909 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 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 054e5c19f97d2aa98d33e7eca70ce606266f0332 Mon Sep 17 00:00:00 2001 +Message-Id: <054e5c19f97d2aa98d33e7eca70ce606266f0332.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:28:34 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 09bc52ff5..5a5c7b7ac 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 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 bc2be884b9e65027e15fca661a311a10dd18b3c7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:18:06 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 ba571d843..7bf009a80 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 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 e4589e51a1cfc859492c0a47c62637e8ada67310 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 11 Jan 2019 21:16:31 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c607d9702..51b787793 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 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 7ab019e69efcb009127d1e22c6bb2d8a665a98cb Mon Sep 17 00:00:00 2001 +Message-Id: <7ab019e69efcb009127d1e22c6bb2d8a665a98cb.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:31:14 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c65980624..187f9fcf3 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 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 9dab673128676751184ca2e3ee8ab002f19cd5e4 Mon Sep 17 00:00:00 2001 +Message-Id: <9dab673128676751184ca2e3ee8ab002f19cd5e4.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 17:34:38 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 13928f45f..b21e9395b 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 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 2cd0bb6d108ca44cae2b4e97d9948b005b98f4e4 Mon Sep 17 00:00:00 2001 +Message-Id: <2cd0bb6d108ca44cae2b4e97d9948b005b98f4e4.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 14:58:57 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4cdc019c1..e6abed9cc 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 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 31dab97ff138fe413355fcf23f5d72149243e0fa Mon Sep 17 00:00:00 2001 +Message-Id: <31dab97ff138fe413355fcf23f5d72149243e0fa.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mikulas Patocka Date: Mon, 13 Nov 2017 12:56:53 -0500 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 62b2d60ff..b6ed8ad84 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 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 cc22a86536b24b1e8dba3b1dc7db99ba7161cc00 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 4 Jan 2019 15:33:21 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a9fd533d3..60442658e 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 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 bf66e1b2e893b51c1298013bb82ed083f495d292 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 16 Nov 2017 16:48:48 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 2dcdecdf7..9ee901ea7 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 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 55c6ef74987f9b95f4551dfad13bc1bae0c74ea8 Mon Sep 17 00:00:00 2001 +Message-Id: <55c6ef74987f9b95f4551dfad13bc1bae0c74ea8.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 18:21:04 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 5adcecd00..bcec65de1 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 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 3b5e53770c3aff121339c47e7fe3888ee6ffef7c Mon Sep 17 00:00:00 2001 +Message-Id: <3b5e53770c3aff121339c47e7fe3888ee6ffef7c.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Sep 2017 14:25:13 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 271dfcb93..f587776d1 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 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 18a0067164c6c0628df5ba671c6da15120c2334a Mon Sep 17 00:00:00 2001 +Message-Id: <18a0067164c6c0628df5ba671c6da15120c2334a.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 5 Jul 2018 14:44:51 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c04d3a8ea..12e18375a 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 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 bc75231f5bf2a3820fcab8fdc7b9686f8352d04e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 17:40:42 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 94e34c038..ef0818ffe 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 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 ab8545db22a85d60bcc140f9fd4bade01c456f07 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Peter Zijlstra Date: Sat, 13 Aug 2011 00:23:17 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 892ed5774..5a8e15394 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 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 9326920fb1109b15fe28d8e033a8dd78c4e24718 Mon Sep 17 00:00:00 2001 +Message-Id: <9326920fb1109b15fe28d8e033a8dd78c4e24718.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 5 Oct 2011 11:59:38 -0700 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 0644043be..f7ca79127 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 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 d8013f2182d632f63ac3aa45d37a9a1f2806037a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Wed, 5 Oct 2011 11:45:18 -0700 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c6ca36060..f9a71241b 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 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 dd27786eda3184d4b9e304d8d0db0437e77e9d84 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 4 Nov 2013 13:21:10 -0800 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 8354f328f..f3c00fe3f 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 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 703a8021c5f883562373916d9b0996ce8df8f66d Mon Sep 17 00:00:00 2001 +Message-Id: <703a8021c5f883562373916d9b0996ce8df8f66d.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 14:43:41 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 53e4782f8..81ef787ba 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 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 59b3b252a8cb61232283dabf05fd284deffb8365 Mon Sep 17 00:00:00 2001 +Message-Id: <59b3b252a8cb61232283dabf05fd284deffb8365.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 18:37:12 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 8cebc0625..00bf68702 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 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 cb33ed06ee657fc2ea1e9968a7184aefcb701cbb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julia Cartwright Date: Wed, 12 Oct 2016 11:21:14 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 d8906fe04..6c91911d3 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 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 a302770bfedc850e9cca7d4334d15bc0c5076eb6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 28 Jul 2011 13:32:57 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 91b419d79..b5fae2e43 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 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 ae9e3f8cfe11f06deac2238dfc419d9b202ea1c2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 8 Jan 2013 21:36:51 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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. @@ -16,7 +16,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c -index 1d501154e9f7..e00b8b6fdae1 100644 +index 45e4f2952143..f4a01c7909fb 100644 --- a/drivers/tty/serial/amba-pl011.c +++ b/drivers/tty/serial/amba-pl011.c @@ -2214,13 +2214,19 @@ pl011_console_write(struct console *co, const char *s, unsigned int count) 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 3295307d2..67b554aca 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,7 +1,7 @@ -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 6c3a754ac2c37c2783ab8f72cedd3bd0917fbe21 Mon Sep 17 00:00:00 2001 +Message-Id: <6c3a754ac2c37c2783ab8f72cedd3bd0917fbe21.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Kurt Kanzenbach Date: Mon, 24 Sep 2018 10:29:01 +0200 Subject: [PATCH 166/333] tty: serial: pl011: explicitly initialize the flags @@ -9,7 +9,7 @@ Subject: [PATCH 166/333] tty: serial: pl011: explicitly initialize the flags 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Silence the following gcc warning: @@ -31,7 +31,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c -index e00b8b6fdae1..55adaabb71ad 100644 +index f4a01c7909fb..0b535a85d282 100644 --- a/drivers/tty/serial/amba-pl011.c +++ b/drivers/tty/serial/amba-pl011.c @@ -2209,7 +2209,7 @@ pl011_console_write(struct console *co, const char *s, unsigned int count) 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 e30bc89ad..7fe5b7427 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 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 e782955f6e1a30256713780608c672a4f31c9911 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Ingo Molnar Date: Wed, 14 Dec 2011 13:05:54 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Beyond the warning: @@ -24,7 +24,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c -index e1a5887b6d91..129c9383f96c 100644 +index d2df7d71d666..57fd29b2ddf5 100644 --- a/drivers/tty/serial/8250/8250_core.c +++ b/drivers/tty/serial/8250/8250_core.c @@ -54,7 +54,16 @@ static struct uart_driver serial8250_reg; 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 9bf74ae85..8a74aed5a 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 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 8719ee0dff01da88df6077f0f5d8b56117272de7 Mon Sep 17 00:00:00 2001 +Message-Id: <8719ee0dff01da88df6077f0f5d8b56117272de7.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Apr 2016 16:55:02 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 @@ -18,10 +18,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c -index 20b799219826..48c9574362c5 100644 +index 09f0dc3b967b..620cc8ee9828 100644 --- a/drivers/tty/serial/8250/8250_port.c +++ b/drivers/tty/serial/8250/8250_port.c -@@ -3245,10 +3245,8 @@ void serial8250_console_write(struct uart_8250_port *up, const char *s, +@@ -3248,10 +3248,8 @@ void serial8250_console_write(struct uart_8250_port *up, const char *s, serial8250_rpm_get(up); 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 567c89e6f..15bea8d26 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 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 8c483ffd92859fd107920da9ad66af72570ac0bf Mon Sep 17 00:00:00 2001 +Message-Id: <8c483ffd92859fd107920da9ad66af72570ac0bf.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Peter Zijlstra Date: Wed, 23 Nov 2016 16:29:32 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 93e3be92d..ed33e0464 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 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 b55d483e29d60df8474df1967ca72fe18677650d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Yong Zhang Date: Tue, 15 May 2012 13:53:56 +0800 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e3374f993..b9bd2b126 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 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 69ca2dbfbb7c19d8b42bb361a06f9a669cf700c1 Mon Sep 17 00:00:00 2001 +Message-Id: <69ca2dbfbb7c19d8b42bb361a06f9a669cf700c1.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 12:32:34 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c1b2b3ea5..fcddd2c26 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 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 0ae9b536ab4d44793251987a5c540feae252b40d Mon Sep 17 00:00:00 2001 +Message-Id: <0ae9b536ab4d44793251987a5c540feae252b40d.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 20 Oct 2017 11:29:53 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 @@ -85,7 +85,7 @@ index c9eb5041ffae..e1fb0b743c96 100644 inode->dirtied_when = 0; diff --git a/include/linux/fs.h b/include/linux/fs.h -index 8d568b51778b..f964aeac78bd 100644 +index 876bfb6df06a..0b102f962518 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h @@ -679,7 +679,7 @@ struct inode { 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 01064f8cb..917910c6d 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 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 e83f0c4544588f4005996af78a1cd7fde26ddee0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:57 -0500 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c537ff3b6..19d0c7b76 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 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 bd5029c17ae293f93f7d4584df7d7d30e6a7067b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6cd518949..4f61b01ba 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 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 b445dff39ed67e6976db044b302b42bdfaf1d423 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 15:10:33 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 fc2564609..c84040d83 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 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 887fdc51db7b73d22860a6846ee9a0a51566654b Mon Sep 17 00:00:00 2001 +Message-Id: <887fdc51db7b73d22860a6846ee9a0a51566654b.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 16:35:35 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f988ccd064a2..57026699b442 100644 +index 61a52bb26d12..87022491d5f6 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 e7fa1d810..1691624d5 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 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 32dcb68778d490393e793053f19a2bf407762aec Mon Sep 17 00:00:00 2001 +Message-Id: <32dcb68778d490393e793053f19a2bf407762aec.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 11:39:36 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a54bd765e..bb29297be 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 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 20c5815cb5b0c5791b0a8744b9960025ea2bba62 Mon Sep 17 00:00:00 2001 +Message-Id: <20c5815cb5b0c5791b0a8744b9960025ea2bba62.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Apr 2014 10:37:23 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 547322311..c5793de64 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 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 693f3a3441b78284a309d854f118832a0735d4b3 Mon Sep 17 00:00:00 2001 +Message-Id: <693f3a3441b78284a309d854f118832a0735d4b3.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 Jul 2015 14:26:34 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz preempt_disable() and get_cpu() don't play well together with the sleeping locks it tries to allocate later. @@ -17,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/block/blk-mq.c b/block/blk-mq.c -index 4aa3284874f6..376fb90de054 100644 +index eae78363c036..830944372d51 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c @@ -570,7 +570,7 @@ static void __blk_mq_complete_request(struct request *rq) @@ -38,7 +38,7 @@ index 4aa3284874f6..376fb90de054 100644 } static void hctx_unlock(struct blk_mq_hw_ctx *hctx, int srcu_idx) -@@ -1371,14 +1371,14 @@ static void __blk_mq_delay_run_hw_queue(struct blk_mq_hw_ctx *hctx, bool async, +@@ -1380,14 +1380,14 @@ static void __blk_mq_delay_run_hw_queue(struct blk_mq_hw_ctx *hctx, bool async, return; if (!async && !(hctx->flags & BLK_MQ_F_BLOCKING)) { 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 70f8231ba..d2712d5d6 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 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 42c577ea7a4354ce8a63cfc11579a99a9a8d60c2 Mon Sep 17 00:00:00 2001 +Message-Id: <42c577ea7a4354ce8a63cfc11579a99a9a8d60c2.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Jan 2015 15:10:08 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz The IPI runs in hardirq context and there are sleeping locks. This patch moves the completion into a workqueue. @@ -19,7 +19,7 @@ Signed-off-by: Sebastian Andrzej Siewior 4 files changed, 30 insertions(+), 1 deletion(-) diff --git a/block/blk-core.c b/block/blk-core.c -index ea33d6abdcfc..4860cd26cd5a 100644 +index ce3710404544..8926b5d998fa 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -189,6 +189,9 @@ void blk_rq_init(struct request_queue *q, struct request *rq) @@ -33,7 +33,7 @@ index ea33d6abdcfc..4860cd26cd5a 100644 rq->q = q; rq->__sector = (sector_t) -1; diff --git a/block/blk-mq.c b/block/blk-mq.c -index 376fb90de054..5808446e4758 100644 +index 830944372d51..f73b111a4d8f 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c @@ -320,6 +320,9 @@ static struct request *blk_mq_rq_ctx_init(struct blk_mq_alloc_data *data, 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 f41c86446..5fca91612 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 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 b27255be28c01c02934220c8e255bbe8bea6e3d7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 6 Apr 2010 16:51:31 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz __raid_run_ops() disables preemption with get_cpu() around the access to the raid5_percpu variables. That causes scheduling while atomic diff --git a/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch b/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch index 25cc60092..49cf7a3c7 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 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 d28abb43b0c0945556828845b30fb0b0f63eae02 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 20:51:03 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 43b1ae3cc..a9f6b4e6b 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 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 c088ed4daeabc07f8c6965869c812d90f6105e15 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:59:15 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 550792656..0623d534b 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 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 d492b7faafe42ccd5cde1ff1f9c06b35bc7f601b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 12:31:10 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 062e40f7e..6b65d7cff 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 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 f51da28ba69261a43aee45020828096b355819f8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 @@ -55,7 +55,7 @@ Signed-off-by: Sebastian Andrzej Siewior 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/block/blk-core.c b/block/blk-core.c -index 4860cd26cd5a..13bf37156bb0 100644 +index 8926b5d998fa..964da7e39870 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -973,12 +973,21 @@ void blk_queue_exit(struct request_queue *q) @@ -81,7 +81,7 @@ index 4860cd26cd5a..13bf37156bb0 100644 } static void blk_rq_timed_out_timer(struct timer_list *t) -@@ -1075,6 +1084,7 @@ struct request_queue *blk_alloc_queue_node(gfp_t gfp_mask, int node_id, +@@ -1077,6 +1086,7 @@ struct request_queue *blk_alloc_queue_node(gfp_t gfp_mask, int node_id, queue_flag_set_unlocked(QUEUE_FLAG_BYPASS, q); init_waitqueue_head(&q->mq_freeze_wq); @@ -89,7 +89,7 @@ index 4860cd26cd5a..13bf37156bb0 100644 /* * Init percpu_ref in atomic mode so that it's faster to shutdown. -@@ -3964,6 +3974,8 @@ int __init blk_dev_init(void) +@@ -3966,6 +3976,8 @@ int __init blk_dev_init(void) if (!kblockd_workqueue) panic("Failed to create kblockd\n"); 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 a47221419..e405051a3 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 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 2a5b12519a1a127f899d6d98799bd42a2fbf5674 Mon Sep 17 00:00:00 2001 +Message-Id: <2a5b12519a1a127f899d6d98799bd42a2fbf5674.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 20 Dec 2012 18:28:26 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 9d8fd8334..fc9bd3d70 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 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 d3156e6f8e6eb8ffe5ba865612ceae9ce2bd4abc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:00:34 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 0833816ab..8e964695c 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 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 90c6aad822ad054d318d291ff811dbf02633070a Mon Sep 17 00:00:00 2001 +Message-Id: <90c6aad822ad054d318d291ff811dbf02633070a.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:10:04 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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/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 437f1ae49..285f42226 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 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 e4caae8cd260d60e1239f6bb9163fae545360e90 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 14:35:49 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 975aa9ba1..11e184b79 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 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 e4cd05a3420e6c3cefca3fd575d1c0b318afa60b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 24 Jul 2013 15:26:54 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1235bc0ed..d80dcdcca 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 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 09f0e99c07775b5e1f04241a951402fcd9906fb8 Mon Sep 17 00:00:00 2001 +Message-Id: <09f0e99c07775b5e1f04241a951402fcd9906fb8.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:42:26 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b5b2e361b..a016012ea 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 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 db39b43108051044286d3a8c772995c84408d46e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 1 Jul 2013 11:02:42 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1e60781cf..e6c14766e 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 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 f9f3ba088cc7194e973a94033a7e3168dc7c803d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Jun 2011 19:47:03 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 aa21f8b5f..83302edad 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 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 448b9b989ad53c93f9826add2bbd630e092c4fc2 Mon Sep 17 00:00:00 2001 +Message-Id: <448b9b989ad53c93f9826add2bbd630e092c4fc2.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:41:35 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e9ed3e998..d746cbf33 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 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 5d67b6df1840dc09f2377137df24cf0830324714 Mon Sep 17 00:00:00 2001 +Message-Id: <5d67b6df1840dc09f2377137df24cf0830324714.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Feb 2012 12:03:30 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 13ce7ac99..06f350fc6 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 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 def7282894d8119dd99c1633c7a427a69b969de1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 18 Feb 2015 16:05:28 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e330b6735..7cd0ddaed 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 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 e55bc3b0e8dd9e6a902ab14916f8e4f142ef1c49 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 15:38:34 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 @@ -31,7 +31,7 @@ index 4e14926433ed..8fff010fff6e 100644 }; diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h -index 25407c206e73..d4d7aea13cc6 100644 +index cbc0294f3989..1054741c9233 100644 --- a/include/linux/skbuff.h +++ b/include/linux/skbuff.h @@ -287,6 +287,7 @@ struct sk_buff_head { @@ -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 e89ae804e68a..44210413bf63 100644 +index 414e4d7e2082..fc1dfd57d4c0 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) @@ -97,7 +97,7 @@ index e89ae804e68a..44210413bf63 100644 rps_lock(sd); if (skb_queue_empty(&sd->input_pkt_queue)) { /* -@@ -6321,13 +6323,21 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) +@@ -6322,13 +6324,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; @@ -119,7 +119,7 @@ index e89ae804e68a..44210413bf63 100644 for (;;) { struct napi_struct *n; -@@ -9520,10 +9530,13 @@ static int dev_cpu_dead(unsigned int oldcpu) +@@ -9521,10 +9531,13 @@ static int dev_cpu_dead(unsigned int oldcpu) netif_rx_ni(skb); input_queue_head_incr(oldsd); } @@ -134,7 +134,7 @@ index e89ae804e68a..44210413bf63 100644 return 0; } -@@ -9834,8 +9847,9 @@ static int __init net_dev_init(void) +@@ -9835,8 +9848,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 fce8ad1cb..f3a3f7eda 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 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 4045ef54237d468b1594d2ce78dd9643bc3a91f0 Mon Sep 17 00:00:00 2001 +Message-Id: <4045ef54237d468b1594d2ce78dd9643bc3a91f0.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Jan 2016 15:55:02 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 44210413bf63..e9594b1e0d44 100644 +index fc1dfd57d4c0..03572f1205c6 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 44210413bf63..e9594b1e0d44 100644 if (dev_xmit_recursion()) goto recursion_alert; -@@ -8569,7 +8573,7 @@ static void netdev_init_one_queue(struct net_device *dev, +@@ -8570,7 +8574,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 d022853c7..b2175fbe7 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 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 6719a0bea159f38b4d3d21a2f83ca46beb63eadb Mon Sep 17 00:00:00 2001 +Message-Id: <6719a0bea159f38b4d3d21a2f83ca46beb63eadb.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 15:39:05 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e9594b1e0d44..4926ba054f62 100644 +index 03572f1205c6..91040933006b 100644 --- a/net/core/dev.c +++ b/net/core/dev.c -@@ -6371,7 +6371,7 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) +@@ -6372,7 +6372,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 a5282119b..2fda0e710 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 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 cbff1538328ab180c65cc18c936e598c927cd88b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 30 Mar 2016 13:36:29 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4926ba054f62..4dff7edb5200 100644 +index 91040933006b..9b15c663b3f8 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 9c1f06257..d2a7adf9e 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 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 4e5189dc9a6f1bbd366639b099b5ebc9b3226587 Mon Sep 17 00:00:00 2001 +Message-Id: <4e5189dc9a6f1bbd366639b099b5ebc9b3226587.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 17:36:35 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 @@ -258,7 +258,7 @@ index 39e319d04bb8..fe99928aff78 100644 err = -EOPNOTSUPP; if (sch->flags & TCQ_F_MQROOT) { diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c -index 49d60ae006ed..c2ee9d1c3770 100644 +index 06681749e736..f1762079365e 100644 --- a/net/sched/sch_generic.c +++ b/net/sched/sch_generic.c @@ -576,7 +576,11 @@ struct Qdisc noop_qdisc = { 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 f32d0f2d5..63aac1b75 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,7 +1,7 @@ -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 c27d99338d0dd1efc0c3c3a8daa0290809cfa91d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:21:56 +0200 Subject: [PATCH 202/333] net: add back the missing serialization in @@ -9,7 +9,7 @@ Subject: [PATCH 202/333] net: add back the missing serialization in 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 0d25900cb..bb577decd 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 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 de690194a7a7cd35cd96bb30fd4a709567239146 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:54:09 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 ff75c0dcd..9c81033e3 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 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 6a6cb0fc2f428550eb6dca1204695cc7f0e00a54 Mon Sep 17 00:00:00 2001 +Message-Id: <6a6cb0fc2f428550eb6dca1204695cc7f0e00a54.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 6 Dec 2016 17:50:30 -0500 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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,7 +56,7 @@ 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 4dff7edb5200..a26ed30641b0 100644 +index 9b15c663b3f8..b73cbe6c8096 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -5941,6 +5941,7 @@ bool napi_schedule_prep(struct napi_struct *n) 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 fa8143a3d..878bfcb41 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 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 9c12b9232c5300062d4b23552cd915307626d399 Mon Sep 17 00:00:00 2001 +Message-Id: <9c12b9232c5300062d4b23552cd915307626d399.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 23 Jun 2015 15:32:51 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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. diff --git a/debian/patches-rt/0206-printk-Make-rt-aware.patch b/debian/patches-rt/0206-printk-Make-rt-aware.patch index b1719b972..ed9530ef9 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 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 99abb977ad29a00172612acdcd8cf3fbe95470b4 Mon Sep 17 00:00:00 2001 +Message-Id: <99abb977ad29a00172612acdcd8cf3fbe95470b4.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Sep 2012 14:50:37 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 2fb12e79a..b76474314 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 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 7c89ab27e0ed2ad5af47ddd8275cf32c681b64d1 Mon Sep 17 00:00:00 2001 +Message-Id: <7c89ab27e0ed2ad5af47ddd8275cf32c681b64d1.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 19 May 2016 17:45:27 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a7ba41769..67d3e644a 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 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 e4e671838ea60af90e00b14e9877e9cc6d2a9476 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Mar 2013 19:01:05 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 43b46b2f0..205ae403c 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,7 +1,7 @@ -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 89e801c3fa3cfc0d7e0fecde8b4f758810e1677c Mon Sep 17 00:00:00 2001 +Message-Id: <89e801c3fa3cfc0d7e0fecde8b4f758810e1677c.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Yadi.hu" Date: Wed, 10 Dec 2014 10:32:09 +0800 Subject: [PATCH 209/333] ARM: enable irq in translation/section permission @@ -9,7 +9,7 @@ Subject: [PATCH 209/333] ARM: enable irq in translation/section permission 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f14043cf6..827bbdc84 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 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 b112a6d4ca4eb87cd875c8a2152ed4df22ad2413 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:00 -0600 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 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 27b8a1222..918da7e26 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 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 2c288b2f8e53f55e82d3f3f70338789a828233bf Mon Sep 17 00:00:00 2001 +Message-Id: <2c288b2f8e53f55e82d3f3f70338789a828233bf.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:01 -0600 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a92d0569e..1f4019817 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 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 cfbe235174fa2db1961ea91d3c9f495c930493b9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jul 2018 14:02:38 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 bd97cfafc..9ab42ed82 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 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 1822291e9247afa91b6f259f602964f1ac285553 Mon Sep 17 00:00:00 2001 +Message-Id: <1822291e9247afa91b6f259f602964f1ac285553.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Jason Wessel Date: Thu, 28 Jul 2011 12:42:23 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz On 07/27/2011 04:37 PM, Thomas Gleixner wrote: > - KGDB (not yet disabled) is reportedly unusable on -rt right now due @@ -28,7 +28,7 @@ Jason. 3 files changed, 7 insertions(+) diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c -index 48c9574362c5..2568fd8e2837 100644 +index 620cc8ee9828..0dec1d548a28 100644 --- a/drivers/tty/serial/8250/8250_port.c +++ b/drivers/tty/serial/8250/8250_port.c @@ -31,6 +31,7 @@ @@ -39,7 +39,7 @@ index 48c9574362c5..2568fd8e2837 100644 #include #include #include -@@ -3247,6 +3248,8 @@ void serial8250_console_write(struct uart_8250_port *up, const char *s, +@@ -3250,6 +3251,8 @@ void serial8250_console_write(struct uart_8250_port *up, const char *s, if (port->sysrq || oops_in_progress) locked = 0; 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 9c111d224..b5a1f94fe 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 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 a1b31592c1c157323136e9da313d515bc1acb091 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Clark Williams Date: Sat, 30 Jul 2011 21:55:53 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1d85c704b..b08cd76d1 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 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 9af5d342669e13a31566e0f1ce94f71607a23306 Mon Sep 17 00:00:00 2001 +Message-Id: <9af5d342669e13a31566e0f1ce94f71607a23306.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Peter Zijlstra Date: Thu, 28 Jul 2011 10:43:51 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 @@ -276,7 +276,7 @@ index 37334ec1ab3e..f18668e166f2 100644 unsigned long task_state_change; #endif diff --git a/include/linux/uaccess.h b/include/linux/uaccess.h -index d55b68b113de..fdbb3511fe9a 100644 +index db9b0dd0a7a3..e151bd0f6d49 100644 --- a/include/linux/uaccess.h +++ b/include/linux/uaccess.h @@ -185,6 +185,7 @@ static __always_inline void pagefault_disabled_dec(void) 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 ca0b5f5d6..0b2020dc8 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 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 2f48962671b202b0a0098bbae2171a8ce78e6609 Mon Sep 17 00:00:00 2001 +Message-Id: <2f48962671b202b0a0098bbae2171a8ce78e6609.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 17:09:55 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 2472e307c..15f4d6f7e 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 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 db7c5370db29b95dd5d04b681d3cdeb80ce53cdb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 21:37:27 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 d660e423e..d44bfb4f3 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 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 4325ecdd115e311a7e560f914dc8727928745c79 Mon Sep 17 00:00:00 2001 +Message-Id: <4325ecdd115e311a7e560f914dc8727928745c79.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 13 Feb 2013 11:03:11 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1f76290db..a134790a7 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 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 efb2d05f214542f105b831807c676dedc74f0e4c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 12 Nov 2011 14:00:48 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Do not disable preemption while taking sleeping locks. All user look safe for migrate_diable() only. @@ -76,7 +76,7 @@ index 6768b2e8148a..c20f51af6bdf 100644 } diff --git a/drivers/scsi/fcoe/fcoe_ctlr.c b/drivers/scsi/fcoe/fcoe_ctlr.c -index 24cbd0a2cc69..ccf60801fe9d 100644 +index 658c0726581f..bceab74eecf7 100644 --- a/drivers/scsi/fcoe/fcoe_ctlr.c +++ b/drivers/scsi/fcoe/fcoe_ctlr.c @@ -838,7 +838,7 @@ static unsigned long fcoe_ctlr_age_fcfs(struct fcoe_ctlr *fip) 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 040dd7380..92f18b26a 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 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 9ace77c8672b423eef50044f9efe3fe02a1e138c Mon Sep 17 00:00:00 2001 +Message-Id: <9ace77c8672b423eef50044f9efe3fe02a1e138c.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 14 Nov 2011 18:19:27 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4c4ee2bde..0af956e54 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 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 82eda2c33b5d4ac34e36e020ba2c86df91861381 Mon Sep 17 00:00:00 2001 +Message-Id: <82eda2c33b5d4ac34e36e020ba2c86df91861381.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2014 17:24:04 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b62a24865..8f3c73528 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 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 ca72e3b523e41094bb28df0710e5a25384f9b30c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 30 Nov 2017 13:40:10 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 da0b28bfa..c0e46c6f7 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 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 0ebb0148fd2c4a94b1b4f69b4f5c88c4d6ab6acf Mon Sep 17 00:00:00 2001 +Message-Id: <0ebb0148fd2c4a94b1b4f69b4f5c88c4d6ab6acf.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 11 Jul 2018 17:14:47 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 2f5077e78..8c9723d4d 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 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 7a5c1b3238277af06e1ee8d6f127679bc66e26d5 Mon Sep 17 00:00:00 2001 +Message-Id: <7a5c1b3238277af06e1ee8d6f127679bc66e26d5.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 18:52:00 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1108ec54c..7bf3e5aa2 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 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 340f4b392711cbe438ad5706cd90ba5263fcd0db Mon Sep 17 00:00:00 2001 +Message-Id: <340f4b392711cbe438ad5706cd90ba5263fcd0db.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 dab0f25ea..81ce8802f 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 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 056bc582753699901a534e8546f2829f6ae36497 Mon Sep 17 00:00:00 2001 +Message-Id: <056bc582753699901a534e8546f2829f6ae36497.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 16 Dec 2010 14:25:18 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 2aaec0caa..8e03a1da1 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 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 bd9e4bb9cf662ec8cd59267b1943032225619404 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 21 Aug 2012 20:38:50 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Delegate the random insertion to the forced threaded interrupt handler. Store the return IP of the hard interrupt handler in the irq 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 826732519..32d347be5 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 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 32d07c91c3f116cf5dd6e5326d978018d48615d5 Mon Sep 17 00:00:00 2001 +Message-Id: <32d07c91c3f116cf5dd6e5326d978018d48615d5.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Jul 2017 17:31:20 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 76e4d5042..e4fffcc28 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 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 f8b5196327b0e22ac852740408737cb40515c72c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 19 Aug 2018 08:28:35 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4fa055f6e..bdf1f366e 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 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 a17b5611f5341b5e99a9cbd6db86ba7dd7e95266 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 18:31:00 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 3ebabadcd..04e01ad12 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 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 11f3ac0c2a15d8e9bd58f10641e0ed6d8c8bfc37 Mon Sep 17 00:00:00 2001 +Message-Id: <11f3ac0c2a15d8e9bd58f10641e0ed6d8c8bfc37.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Priyanka Jain Date: Thu, 17 May 2012 09:35:11 +0530 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a26ed30641b0..aa5e5abb7b1d 100644 +index b73cbe6c8096..18035fec5766 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 215f893ef..0b7dd3c9e 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 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 ab8ccfd2553bcf89215561a581249d591822442d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Sep 2012 16:21:08 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Replace it by a local lock. Though that's pretty inefficient :( @@ -15,7 +15,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/net/core/skbuff.c b/net/core/skbuff.c -index 0629ca89ab74..6ca7cb2b4364 100644 +index be4bc833c28a..6cd78c85a1ea 100644 --- a/net/core/skbuff.c +++ b/net/core/skbuff.c @@ -63,6 +63,7 @@ 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 45cf61481..e7e096e2a 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 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 d75bbb4414b71e89f0ce0ee32e6385e91d33042d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 15 Jan 2016 16:33:34 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 @@ -21,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/net/core/skbuff.c b/net/core/skbuff.c -index 6ca7cb2b4364..c5c0d2095873 100644 +index 6cd78c85a1ea..c09dc024ca56 100644 --- a/net/core/skbuff.c +++ b/net/core/skbuff.c @@ -332,6 +332,7 @@ struct napi_alloc_cache { 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 afd307ec3..e1e4bcf6d 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 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 50b16d1ddb28fd72581e1a4467e4d444b6d4cf68 Mon Sep 17 00:00:00 2001 +Message-Id: <50b16d1ddb28fd72581e1a4467e4d444b6d4cf68.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 11:18:08 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 215e6873e..52a8f036f 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 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 5d97b3a36b15d89c690396bf6cfdc173dca99f0d Mon Sep 17 00:00:00 2001 +Message-Id: <5d97b3a36b15d89c690396bf6cfdc173dca99f0d.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Yong Zhang Date: Mon, 16 Apr 2012 15:01:56 +0800 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 27aa0116f..441f64b95 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 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 77760b0d25195f4d364b33f9d2f5bc49c89b355a Mon Sep 17 00:00:00 2001 +Message-Id: <77760b0d25195f4d364b33f9d2f5bc49c89b355a.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Josh Cartwright Date: Wed, 28 Jan 2015 13:08:45 -0600 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f78b92cb4..0ccc5496e 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 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 46c13ac5bf3e07408071eeac823042e5e887530f Mon Sep 17 00:00:00 2001 +Message-Id: <46c13ac5bf3e07408071eeac823042e5e887530f.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 26 Oct 2012 18:50:54 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz It has become an obsession to mitigate the determinism vs. throughput loss of RT. Looking at the mainline semantics of preemption points 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 b79ae332e..9a6513a42 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 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 b49db3be25b3c3ddfbaa4be08f0c2b64a5ce1728 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:08:30 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4f7073241..dfaf86562 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 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 738b35f813ba0b68cb2f04ce52a09236ed80bf0a Mon Sep 17 00:00:00 2001 +Message-Id: <738b35f813ba0b68cb2f04ce52a09236ed80bf0a.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 11:03:47 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 031bb60a2..5849b9af6 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 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 148cdab3ace63f2ec560f4aa496a0910e85cac12 Mon Sep 17 00:00:00 2001 +Message-Id: <148cdab3ace63f2ec560f4aa496a0910e85cac12.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 16:57:09 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 ff84de2ab..94ce5d7ed 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 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 c7caac7131763a2c0b09587010acd14798810502 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 14:53:49 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 460513614..6f1dd590b 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 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 45291ecfd9fcf31cd18a76c385d84082be6304c6 Mon Sep 17 00:00:00 2001 +Message-Id: <45291ecfd9fcf31cd18a76c385d84082be6304c6.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 31 Oct 2012 12:04:11 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 00d43a58e..f92b2962c 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 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 458a4683ec709ab526ba6f9112eb96b234b70593 Mon Sep 17 00:00:00 2001 +Message-Id: <458a4683ec709ab526ba6f9112eb96b234b70593.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 10:14:11 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 7b624b98b..1e13380d0 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 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 ea9b7de100fafa360831531e58151875918bbbba Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Anders Roxell Date: Thu, 14 May 2015 17:52:17 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6a8e476d9..a7007b3ba 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 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 85d8de326e1ace824f3cc022f10d9f6079e032bd Mon Sep 17 00:00:00 2001 +Message-Id: <85d8de326e1ace824f3cc022f10d9f6079e032bd.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:11:54 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 5d9aa9549..672c82ae9 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 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 4926f38dfba703bae5ff718dabfb1502e7b16281 Mon Sep 17 00:00:00 2001 +Message-Id: <4926f38dfba703bae5ff718dabfb1502e7b16281.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 31 Mar 2016 04:08:28 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 93a9055ef..fe1050040 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 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 baa2300f62d4a20b94791de1a7fbbb32063ddbb2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 20 Oct 2016 11:15:22 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 fcff6f1f4..8a56eafd3 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 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 a59a1afa0b2b3b350daaf85858889bcdeec01607 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 23 Aug 2017 11:57:29 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f59396d36..e13c63b14 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 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 0249842554e776541173cf005b179a2c38955b19 Mon Sep 17 00:00:00 2001 +Message-Id: <0249842554e776541173cf005b179a2c38955b19.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Haris Okanovic Date: Tue, 15 Aug 2017 15:13:08 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b1c195bff..fd6c86381 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 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 ab12f11f91cd6dac5fc01c2fb7e28a1911fca274 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz When PREEMPT_RT_FULL is enabled, all hrtimer expiry functions are deferred for execution into the context of ktimersoftd unless otherwise 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 ff30d1494..5d0086334 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 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 3750a91a15e9fbc64e8001433b0da93ad7dbd097 Mon Sep 17 00:00:00 2001 +Message-Id: <3750a91a15e9fbc64e8001433b0da93ad7dbd097.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 08:09:11 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz DRM folks identified the spots, so use them. 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 0e8510d9a..5bba64bea 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 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 6a5a0719cb37a83619d3a910b2211a6aa7dc92ff Mon Sep 17 00:00:00 2001 +Message-Id: <6a5a0719cb37a83619d3a910b2211a6aa7dc92ff.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 09:01:42 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 5b99cd147..87bdf6566 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 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 93086274d30c39bc6a378c958a209213d388de33 Mon Sep 17 00:00:00 2001 +Message-Id: <93086274d30c39bc6a378c958a209213d388de33.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 09:52:20 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e32681239..3dee0320a 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 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 a95f9bdf51bc729a57da7e366550dffd92b90f4d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 19 Dec 2018 10:47:02 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6144b77d6..675f8a2c6 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 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 a4e1c827f636c27c8ff1bcf53da692d73f2a3ad5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 13 Feb 2015 15:52:24 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz To avoid: |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914 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 e728264b5..79d44de36 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 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 5704567df863ac4ee72aefc7980e9a0c0298ab2a Mon Sep 17 00:00:00 2001 +Message-Id: <5704567df863ac4ee72aefc7980e9a0c0298ab2a.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 8 Jan 2017 09:32:25 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e3f606212..fc4abb3c9 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 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 702be07f09ca2df069d95b4f607e0614171d5261 Mon Sep 17 00:00:00 2001 +Message-Id: <702be07f09ca2df069d95b4f607e0614171d5261.1601675152.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 11 Oct 2017 17:43:49 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 84ff433c0..17223e7f9 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 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 e9c2038f7faa234dc61ec827acf0fe0d63d2b480 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 27 Jun 2014 16:24:52 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 df486b88a..92b116672 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 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 b97a75529d82eea987e2255c04cea2518da8b82f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:56 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 456f28a07..c020d7d70 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 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 713f37677b0530f6169256ddd0cbb375a54c9959 Mon Sep 17 00:00:00 2001 +Message-Id: <713f37677b0530f6169256ddd0cbb375a54c9959.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 20:25:16 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 80658134e..8a5a7a9fb 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 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 dd0d56cb4d2cafeedbb850448b6fe7cd5e954fbb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Mar 2019 18:31:54 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b9c325d61..76414550d 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 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 b6282e8ff92d3a755c367b7dacf2e5138bda08b3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 22 Mar 2019 17:15:58 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 ec05e4775..3501e3a76 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 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 7f46ed1d1e09f1df4574e0b269dc620bfe04827a Mon Sep 17 00:00:00 2001 +Message-Id: <7f46ed1d1e09f1df4574e0b269dc620bfe04827a.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 13 Mar 2019 11:40:34 +0000 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 01bffd977..4b8871713 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 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 625c98af6dc1e1d58f784f1756b4a136a7b580b8 Mon Sep 17 00:00:00 2001 +Message-Id: <625c98af6dc1e1d58f784f1756b4a136a7b580b8.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 10 Apr 2019 11:01:37 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 410079875..1c9518382 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 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 77d0dc893dbaff42a88a991dff2fceb801ae5a2f Mon Sep 17 00:00:00 2001 +Message-Id: <77d0dc893dbaff42a88a991dff2fceb801ae5a2f.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Corey Minyard Date: Thu, 9 May 2019 14:33:20 -0500 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f4ce30008..8ee634d7b 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 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 08e6459b307f6968fca717fd462585d5929cd147 Mon Sep 17 00:00:00 2001 +Message-Id: <08e6459b307f6968fca717fd462585d5929cd147.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 12 Feb 2019 15:09:38 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 da68c42aed68..5f07061c4087 100644 +index 19042b42a8ba..629589a36b0a 100644 --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -70,7 +70,7 @@ 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 c82e76cf5..bf3018f60 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 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 93809b10fcffc172653eb85776b6b7033609f2b6 Mon Sep 17 00:00:00 2001 +Message-Id: <93809b10fcffc172653eb85776b6b7033609f2b6.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 May 2019 17:07:44 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 3148e802e..58f705b36 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 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 3bfdfec08eb8a94a4247c3bebcead5ca5ce116d0 Mon Sep 17 00:00:00 2001 +Message-Id: <3bfdfec08eb8a94a4247c3bebcead5ca5ce116d0.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 18:29:13 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 aa663ccd2..3e688afed 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 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 ea6f063a5e21de7e3278c1eda75905203ae80ecb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: kbuild test robot Date: Sat, 13 Apr 2019 11:22:51 +0800 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a23796eeb..65f4825b3 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 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 49513378252da42b8022bcf5849a99df771f0e63 Mon Sep 17 00:00:00 2001 +Message-Id: <49513378252da42b8022bcf5849a99df771f0e63.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:33:16 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b9f2e9af8..fdc3daf08 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 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 176747a96def566e078f910ffa33b15c07a96b6d Mon Sep 17 00:00:00 2001 +Message-Id: <176747a96def566e078f910ffa33b15c07a96b6d.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:39:06 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit c71273154c2ad12e13333aada340ff30e826a11b ] 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 d7d1b462b..a77271921 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 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 6f1cd1d4fc326ff505151c9cea6df15f8a322b4e Mon Sep 17 00:00:00 2001 +Message-Id: <6f1cd1d4fc326ff505151c9cea6df15f8a322b4e.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:13 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 54518ec34..cf9e39e8e 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 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 15abc655043f26817b3bf2bd43c8cd1c9d0821d6 Mon Sep 17 00:00:00 2001 +Message-Id: <15abc655043f26817b3bf2bd43c8cd1c9d0821d6.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:18 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 de8f6913b..7ec9794e1 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 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 1b392743b3e2d284bb8a83b954d939790c80cb38 Mon Sep 17 00:00:00 2001 +Message-Id: <1b392743b3e2d284bb8a83b954d939790c80cb38.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:21 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a95ed10c4..3faef78b8 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 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 f9031ff7ec4df88f9c03e01ec116914c446bc7ed Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:27 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6b3ea1b2f..a1f6e202a 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 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 70506d966f14b76fc42746009b663a48cd7e2287 Mon Sep 17 00:00:00 2001 +Message-Id: <70506d966f14b76fc42746009b663a48cd7e2287.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 11:59:44 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 7c280d646..834171b3c 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 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 183118d6b4d9dff19ec1a98dcb70bcd7fbe04adf Mon Sep 17 00:00:00 2001 +Message-Id: <183118d6b4d9dff19ec1a98dcb70bcd7fbe04adf.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Jun 2019 13:35:36 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 25a5b00cd..d1e977db3 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 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 240c8e20079c36d1891ac5ba5bcfa80f9a6cb62f Mon Sep 17 00:00:00 2001 +Message-Id: <240c8e20079c36d1891ac5ba5bcfa80f9a6cb62f.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Luis Claudio R. Goncalves" Date: Tue, 25 Jun 2019 11:28:04 -0300 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit 4e4cf4be79635e67144632d9135286381acbc95a ] diff --git a/debian/patches-rt/0279-revert-aio.patch b/debian/patches-rt/0279-revert-aio.patch index bd860dc3f..4eb46ac95 100644 --- a/debian/patches-rt/0279-revert-aio.patch +++ b/debian/patches-rt/0279-revert-aio.patch @@ -1,11 +1,11 @@ -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 f83ada274dea8d2f4bcd5a1080a46900725b3880 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 2406ae48b..232316005 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 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 4af13d32a498a81c54232ae5cd0d059712bb06e2 Mon Sep 17 00:00:00 2001 +Message-Id: <4af13d32a498a81c54232ae5cd0d059712bb06e2.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit 1a142116f6435ef070ecebb66d2d599507c10601 ] diff --git a/debian/patches-rt/0281-revert-thermal.patch b/debian/patches-rt/0281-revert-thermal.patch index 17cb9b4b6..09c8e0a74 100644 --- a/debian/patches-rt/0281-revert-thermal.patch +++ b/debian/patches-rt/0281-revert-thermal.patch @@ -1,11 +1,11 @@ -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 9de0906424f6042c06a68fce58560a6437e8d418 Mon Sep 17 00:00:00 2001 +Message-Id: <9de0906424f6042c06a68fce58560a6437e8d418.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f674dbe91..29f16a4a5 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 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 c62dfb4104de740edf17882cfd1f212f31d08f00 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit ad2408dc248fe58536eef5b2b5734d8f9d3a280b ] diff --git a/debian/patches-rt/0283-revert-block.patch b/debian/patches-rt/0283-revert-block.patch index d973c6b28..39cff6e76 100644 --- a/debian/patches-rt/0283-revert-block.patch +++ b/debian/patches-rt/0283-revert-block.patch @@ -1,11 +1,11 @@ -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 c25259438bc98c7192ee119152b6516dbf1866a1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:54 -0400 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz Revert swork version of: block: blk-mq: move blk_queue_usage_counter_release() into process context @@ -18,7 +18,7 @@ Signed-off-by: Steven Rostedt (VMware) 2 files changed, 1 insertion(+), 15 deletions(-) diff --git a/block/blk-core.c b/block/blk-core.c -index 13bf37156bb0..4860cd26cd5a 100644 +index 964da7e39870..8926b5d998fa 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -973,21 +973,12 @@ void blk_queue_exit(struct request_queue *q) @@ -44,7 +44,7 @@ index 13bf37156bb0..4860cd26cd5a 100644 } static void blk_rq_timed_out_timer(struct timer_list *t) -@@ -1084,7 +1075,6 @@ struct request_queue *blk_alloc_queue_node(gfp_t gfp_mask, int node_id, +@@ -1086,7 +1077,6 @@ struct request_queue *blk_alloc_queue_node(gfp_t gfp_mask, int node_id, queue_flag_set_unlocked(QUEUE_FLAG_BYPASS, q); init_waitqueue_head(&q->mq_freeze_wq); @@ -52,7 +52,7 @@ index 13bf37156bb0..4860cd26cd5a 100644 /* * Init percpu_ref in atomic mode so that it's faster to shutdown. -@@ -3974,8 +3964,6 @@ int __init blk_dev_init(void) +@@ -3976,8 +3966,6 @@ int __init blk_dev_init(void) if (!kblockd_workqueue) panic("Failed to create kblockd\n"); 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 8a1819053..de62f7e52 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 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 4428ce765717ea9eb1eb39b7535a5a17e46839af Mon Sep 17 00:00:00 2001 +Message-Id: <4428ce765717ea9eb1eb39b7535a5a17e46839af.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit 61c928ecf4fe200bda9b49a0813b5ba0f43995b5 ] @@ -58,7 +58,7 @@ Signed-off-by: Steven Rostedt (VMware) 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/block/blk-core.c b/block/blk-core.c -index 4860cd26cd5a..7d709465876e 100644 +index 8926b5d998fa..1a2ec9f3323a 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -973,12 +973,21 @@ void blk_queue_exit(struct request_queue *q) @@ -84,7 +84,7 @@ index 4860cd26cd5a..7d709465876e 100644 } static void blk_rq_timed_out_timer(struct timer_list *t) -@@ -1075,6 +1084,7 @@ struct request_queue *blk_alloc_queue_node(gfp_t gfp_mask, int node_id, +@@ -1077,6 +1086,7 @@ struct request_queue *blk_alloc_queue_node(gfp_t gfp_mask, int node_id, queue_flag_set_unlocked(QUEUE_FLAG_BYPASS, q); init_waitqueue_head(&q->mq_freeze_wq); diff --git a/debian/patches-rt/0285-workqueue-rework.patch b/debian/patches-rt/0285-workqueue-rework.patch index c9f52ad64..b4a938f99 100644 --- a/debian/patches-rt/0285-workqueue-rework.patch +++ b/debian/patches-rt/0285-workqueue-rework.patch @@ -1,11 +1,11 @@ -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 62a1275f96f99d9eba5dcf763609bcb9b5a0a41e Mon Sep 17 00:00:00 2001 +Message-Id: <62a1275f96f99d9eba5dcf763609bcb9b5a0a41e.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 May 2019 18:52:27 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit d15a862f24df983458533aebd6fa207ecdd1095a ] @@ -38,7 +38,7 @@ Signed-off-by: Steven Rostedt (VMware) delete mode 100644 include/linux/kthread-cgroup.h diff --git a/block/blk-core.c b/block/blk-core.c -index 7d709465876e..752c9e754509 100644 +index 1a2ec9f3323a..77596d604867 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -973,7 +973,7 @@ void blk_queue_exit(struct request_queue *q) @@ -59,7 +59,7 @@ index 7d709465876e..752c9e754509 100644 } static void blk_rq_timed_out_timer(struct timer_list *t) -@@ -1084,7 +1084,7 @@ struct request_queue *blk_alloc_queue_node(gfp_t gfp_mask, int node_id, +@@ -1086,7 +1086,7 @@ struct request_queue *blk_alloc_queue_node(gfp_t gfp_mask, int node_id, queue_flag_set_unlocked(QUEUE_FLAG_BYPASS, q); init_waitqueue_head(&q->mq_freeze_wq); @@ -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 5f07061c4087..da68c42aed68 100644 +index 629589a36b0a..19042b42a8ba 100644 --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -70,7 +70,7 @@ 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 dd031a3b3..f1eb368f2 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 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 62acf66b08656cb7a216aef627c97328a0b17276 Mon Sep 17 00:00:00 2001 +Message-Id: <62acf66b08656cb7a216aef627c97328a0b17276.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:12 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4f3ffcc02..04edbea62 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 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 2a2fd0aa8ea798a57965adc41d840d4de7e4fbf9 Mon Sep 17 00:00:00 2001 +Message-Id: <2a2fd0aa8ea798a57965adc41d840d4de7e4fbf9.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:37 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 3aaa64488..c2f38e262 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 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 2044cb95e057d622dbda2409f360a941ad2bf9d4 Mon Sep 17 00:00:00 2001 +Message-Id: <2044cb95e057d622dbda2409f360a941ad2bf9d4.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Juri Lelli Date: Wed, 31 Jul 2019 12:37:15 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 0a87a88b6..bb5470b9e 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 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 3b181fc1462d7c01ab9a3357a6636b59213a21b5 Mon Sep 17 00:00:00 2001 +Message-Id: <3b181fc1462d7c01ab9a3357a6636b59213a21b5.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Clark Williams Date: Mon, 15 Jul 2019 15:25:00 -0500 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b6cf8c142..1c5746674 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 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 3d06ef72e7334ee3c00fbf1c5a27650501872aef Mon Sep 17 00:00:00 2001 +Message-Id: <3d06ef72e7334ee3c00fbf1c5a27650501872aef.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 16:38:43 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 42863d5cb..a8be14110 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 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 5e5e79ef61becfd811e3e3237ba1574472643196 Mon Sep 17 00:00:00 2001 +Message-Id: <5e5e79ef61becfd811e3e3237ba1574472643196.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Aug 2019 14:29:41 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 d726b2b28..182270eaa 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 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 8df0bbe7b80926027d51e888f6490c62864675ad Mon Sep 17 00:00:00 2001 +Message-Id: <8df0bbe7b80926027d51e888f6490c62864675ad.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 17:08:58 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 79e6c254c..41a243335 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 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 5efd46d0f1390fe3f13f0597832fb87dfe62eecd Mon Sep 17 00:00:00 2001 +Message-Id: <5efd46d0f1390fe3f13f0597832fb87dfe62eecd.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:07 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 aa46961da..109537da4 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 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 6fc5e9ec34e6b95824eeda47bd80c6e920f6ca61 Mon Sep 17 00:00:00 2001 +Message-Id: <6fc5e9ec34e6b95824eeda47bd80c6e920f6ca61.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:08 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6eee15464..a9674e315 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 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 0a4ffc921c8c63dbbc2ee27eb7a18549692bf2e4 Mon Sep 17 00:00:00 2001 +Message-Id: <0a4ffc921c8c63dbbc2ee27eb7a18549692bf2e4.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:09 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1b6fbe8e7..3b589484b 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 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 07fd62c856db23982a2a6752801401de5c205e13 Mon Sep 17 00:00:00 2001 +Message-Id: <07fd62c856db23982a2a6752801401de5c205e13.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Sep 2019 16:55:27 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 90e70de7a..9a2743318 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 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 7fd7ef2936478f58bb576d298f1995dcd4a7068b Mon Sep 17 00:00:00 2001 +Message-Id: <7fd7ef2936478f58bb576d298f1995dcd4a7068b.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Sep 2019 12:33:59 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 2846901a5..af9ef587d 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,7 +1,7 @@ -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 d770574c2e7cbe8be529f1ebcbca273c431820b2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Tue, 24 Sep 2019 14:36:41 +0200 Subject: [PATCH 298/333] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= @@ -9,7 +9,7 @@ Subject: [PATCH 298/333] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 b0dac69e6..cf1172e53 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 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 e3a5dc29e8b77b705b1c3483d9c88a635b0b5e5b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:32 -0500 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e068e022b..f3d8a4570 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 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 21e0b28571016d773437dd56a61ed62bc81eb4c6 Mon Sep 17 00:00:00 2001 +Message-Id: <21e0b28571016d773437dd56a61ed62bc81eb4c6.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:33 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6961e821e..1f49b47e2 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 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 bccdf34a949d258f53d3105e474254bbd22ac075 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:34 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4c90bc532..4e3507f6a 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 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 b842642f2c9c33d6d0430314326f0f0df15ac0a3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Waiman Long Date: Thu, 3 Oct 2019 16:36:08 -0400 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 141df485e..070d77749 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 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 16ddd30d330d85720eb336315778820e0cbe37e7 Mon Sep 17 00:00:00 2001 +Message-Id: <16ddd30d330d85720eb336315778820e0cbe37e7.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 7 Oct 2019 16:45:18 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 6a4fba429..07ecad229 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 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 31aee2dc5cb0dde7da5a2cad0631c2ff64889b81 Mon Sep 17 00:00:00 2001 +Message-Id: <31aee2dc5cb0dde7da5a2cad0631c2ff64889b81.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 30 Sep 2019 18:15:44 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e3558bf95..24c94c990 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 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 536b5ac71e48f040860f2d5ed873c21eb7b1df4d Mon Sep 17 00:00:00 2001 +Message-Id: <536b5ac71e48f040860f2d5ed873c21eb7b1df4d.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Julien Grall Date: Fri, 20 Sep 2019 11:08:35 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1f0884e34..ec8cc68c1 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 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 214863e94c87110d920650d09b26ed428069fb2e Mon Sep 17 00:00:00 2001 +Message-Id: <214863e94c87110d920650d09b26ed428069fb2e.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Liu Haitao Date: Fri, 27 Sep 2019 16:22:30 +0800 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e5f72b741..25b71cb0a 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 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 45936427790b2e486dfb2262dfa3bc0ac82d8922 Mon Sep 17 00:00:00 2001 +Message-Id: <45936427790b2e486dfb2262dfa3bc0ac82d8922.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:12 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 1559ffc40..978854a2b 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 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 8ecc03deb59a69cbe1470f50affb5d40c9a1d273 Mon Sep 17 00:00:00 2001 +Message-Id: <8ecc03deb59a69cbe1470f50affb5d40c9a1d273.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:13 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 a0ac5c0fa..49f53e3d4 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 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 c6ef1b9d671a2002356c0e5fda09dafb37b3dd20 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:14 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f5de0013a..f909c3b73 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 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 5e806505660ca40376088d44e1720ddee3c953f5 Mon Sep 17 00:00:00 2001 +Message-Id: <5e806505660ca40376088d44e1720ddee3c953f5.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 18 Oct 2019 13:04:15 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 91e84f888..c9d3743f3 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 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 7b9bd3a70ec2f8e37ae56250752926873d2169f1 Mon Sep 17 00:00:00 2001 +Message-Id: <7b9bd3a70ec2f8e37ae56250752926873d2169f1.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Nov 2019 09:25:04 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 7e22ffc37..80bfe5688 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 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 542037f313bfa2842d2733780cb6c9d57f451ddf Mon Sep 17 00:00:00 2001 +Message-Id: <542037f313bfa2842d2733780cb6c9d57f451ddf.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 29 Nov 2019 17:24:55 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 ee5429e28..49de9565c 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 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 511a64eb8b324b9a5a4e1048b3a5d62a90fd01c2 Mon Sep 17 00:00:00 2001 +Message-Id: <511a64eb8b324b9a5a4e1048b3a5d62a90fd01c2.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Daniel Wagner Date: Mon, 16 Dec 2019 16:15:57 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 446698826..e6c3ee404 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 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 c5ff1b44f7c634d4ebf49eb0c8930c944c20eb09 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Dec 2019 10:53:59 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 7a417f287..90cba590f 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 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 b76ddf8d3da1a33cc7c81c4459cf26c4741cf5e2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 18 Dec 2019 12:25:09 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 fe41613df..0cb670cc7 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 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 cee66e3557735609a551656c2bda190fa2470207 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:46 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4becbb1d5..a1cd82c49 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 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 a1926e9d19f77f7f6c0f0528f1ef3a2886bb3407 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:47 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 c8bf07df0..62f78691b 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 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 0d65d04f961014c84ab5bd939a0605147ccdec9c Mon Sep 17 00:00:00 2001 +Message-Id: <0d65d04f961014c84ab5bd939a0605147ccdec9c.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Matt Fleming Date: Sun, 26 Jan 2020 21:19:45 +0000 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 784cee415..0bc4bdfbe 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 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 2dae1452f67bb52f711505aa751312630e270065 Mon Sep 17 00:00:00 2001 +Message-Id: <2dae1452f67bb52f711505aa751312630e270065.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Feb 2020 13:29:50 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 3e158ff9a..210e176f8 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 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 1f738998f8e1a6962ff73d192b2d578631792cdd Mon Sep 17 00:00:00 2001 +Message-Id: <1f738998f8e1a6962ff73d192b2d578631792cdd.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:57:11 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 e221878ea..f245630ed 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 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 c54e986675b32bda66a071c2f8061c8260f5e0a5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:15:15 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit dd430bf5ecb40f9a89679c85868826475d71de54 ] 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 6440349fb..e3901f4e5 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 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 4dcb56fdb613d6d9e957726c09221c84042f63f4 Mon Sep 17 00:00:00 2001 +Message-Id: <4dcb56fdb613d6d9e957726c09221c84042f63f4.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Tiejun Chen Date: Mon, 30 Mar 2020 18:45:23 -0400 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 0c6b76c6a..930826f6e 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 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 d5e9cc85cf583e843367018c470c4eb5afcc2414 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Sun, 22 Mar 2020 00:00:28 +0100 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 72015b3da..4330fc093 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 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 a790345fb190c241de79172943a48546d9b795c2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Zhang Xiao Date: Tue, 17 Mar 2020 12:47:43 +0100 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 4137654a3..0b56b6721 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 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 e7610b6d4601c96dcc59dee0a8c14e26256b65e5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Rasmus Villemoes Date: Tue, 28 Apr 2020 16:40:26 +0200 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 799113b33..a8d49627a 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 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 e91db0b19074df285a6c68208c9ffc0e54d7978d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 16 Apr 2020 12:42:15 +0200 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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 f5adf2a9c..8b6580612 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 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 955ea4e3b93b3782e45aefb1cc45f3b808141f60 Mon Sep 17 00:00:00 2001 +Message-Id: <955ea4e3b93b3782e45aefb1cc45f3b808141f60.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Kevin Hao Date: Mon, 4 May 2020 11:34:07 +0800 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.142-rt63.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit 23a2c31b19e99beaf5107071b0f32a596202cdae ] @@ -49,7 +49,7 @@ Signed-off-by: Tom Zanussi 1 file changed, 3 deletions(-) diff --git a/mm/slub.c b/mm/slub.c -index af485aba93ec..9bf0c118cc16 100644 +index 362ec0e00f89..5ee7fbc62127 100644 --- a/mm/slub.c +++ b/mm/slub.c @@ -2368,9 +2368,6 @@ static void flush_all(struct kmem_cache *s) 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 dd404caa9..d200b6338 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 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 9e4127f120a46693ef293d65465523daab444e57 Mon Sep 17 00:00:00 2001 +Message-Id: <9e4127f120a46693ef293d65465523daab444e57.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> From: Tom Zanussi Date: Tue, 9 Jun 2020 11:04:08 -0500 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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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-signal-Prevent-double-free-of-user-struct.patch b/debian/patches-rt/0329-signal-Prevent-double-free-of-user-struct.patch index f22cec829..8f11e4507 100644 --- 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 @@ -1,11 +1,11 @@ -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 739f241c793a4258729c6ededd6ec4c02093ac7d Mon Sep 17 00:00:00 2001 +Message-Id: <739f241c793a4258729c6ededd6ec4c02093ac7d.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upsteam commit 9567db2ebe566a93485e1a27d8759969d0002d7a ] 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 index dafb7df86..78236b422 100644 --- 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 @@ -1,12 +1,12 @@ -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 dc7cecac1410bf03bfe28a8127c5e3720c3f389a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit e6da0edc24eecef2f6964d92fa9044e1821deace ] 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 index 1782cc915..259acd456 100644 --- 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 @@ -1,11 +1,11 @@ -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 4767910abe0a6ee1a470fe31c4390c57b83376f2 Mon Sep 17 00:00:00 2001 +Message-Id: <4767910abe0a6ee1a470fe31c4390c57b83376f2.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz [ Upstream commit 6554eac9ef2bd1c968886b31cc7266b49258a463 ] 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 index e22096c99..bf5350599 100644 --- 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 @@ -1,11 +1,11 @@ -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 f1c8cd78e517a1c544378207b8f54b9fbdfa8cc8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.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 +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.tar.xz A crash was seen in xfrm when running ltp's 'tcp4_ipsec06' stresser on v4.x based RT kernels. 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 deleted file mode 100644 index c014ca21a..000000000 --- a/debian/patches-rt/0333-Linux-4.19.142-rt63-REBASE.patch +++ /dev/null @@ -1,24 +0,0 @@ -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/0333-Linux-4.19.148-rt64-REBASE.patch b/debian/patches-rt/0333-Linux-4.19.148-rt64-REBASE.patch new file mode 100644 index 000000000..c757f0021 --- /dev/null +++ b/debian/patches-rt/0333-Linux-4.19.148-rt64-REBASE.patch @@ -0,0 +1,24 @@ +From 4a12f04d9fe7d2e1acabee082475d7ee02c5b18e Mon Sep 17 00:00:00 2001 +Message-Id: <4a12f04d9fe7d2e1acabee082475d7ee02c5b18e.1601675153.git.zanussi@kernel.org> +In-Reply-To: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +References: <5b5a156f9808b1acf1205606e03da117214549ea.1601675151.git.zanussi@kernel.org> +From: Tom Zanussi +Date: Fri, 2 Oct 2020 16:41:26 -0500 +Subject: [PATCH 333/333] Linux 4.19.148-rt64 REBASE +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.148-rt64.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..10474042df49 100644 +--- a/localversion-rt ++++ b/localversion-rt +@@ -1 +1 @@ +--rt16 ++-rt64 +-- +2.17.1 + diff --git a/debian/patches-rt/series b/debian/patches-rt/series index beb92e8c9..02ac50c65 100644 --- a/debian/patches-rt/series +++ b/debian/patches-rt/series @@ -330,4 +330,4 @@ 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 +0333-Linux-4.19.148-rt64-REBASE.patch