[linux] 07/07: [rt] Update to 4.9.76-rt61
debian-kernel at lists.debian.org
debian-kernel at lists.debian.org
Mon Feb 19 12:35:19 UTC 2018
This is an automated email from the git hooks/post-receive script.
corsac pushed a commit to branch stretch
in repository linux.
commit cefaad933560d75e844918b807460f779333df55
Author: Yves-Alexis Perez <corsac at corsac.net>
Date: Sun Feb 18 22:09:37 2018 +0100
[rt] Update to 4.9.76-rt61
---
debian/changelog | 2 +-
.../all/rt/0001-timer-make-the-base-lock-raw.patch | 35 +++++++++---------
...dle-statically-initialized-PER_CPU-locks-.patch | 5 ++-
...-compilation-error-for-CONFIG_MODULES-and.patch | 5 ++-
.../0004-lockdep-Fix-per-cpu-static-objects.patch | 7 ++--
...eanup-variable-names-for-futex_top_waiter.patch | 7 ++--
...-Use-smp_store_release-in-mark_wake_futex.patch | 5 ++-
...7-futex-Remove-rt_mutex_deadlock_account_.patch | 7 ++--
...mutex-Provide-futex-specific-rt_mutex-API.patch | 9 +++--
.../all/rt/0009-futex-Change-locking-rules.patch | 9 +++--
.../all/rt/0010-futex-Cleanup-refcounting.patch | 7 ++--
...ework-inconsistent-rt_mutex-futex_q-state.patch | 5 ++-
...rt_mutex_futex_unlock-out-from-under-hb-l.patch | 19 +++++-----
...x-rt_mutex-Introduce-rt_mutex_init_waiter.patch | 5 ++-
...tex-Restructure-rt_mutex_finish_proxy_loc.patch | 5 ++-
...k-futex_lock_pi-to-use-rt_mutex_-_proxy_l.patch | 7 ++--
.../0016-futex-Futex_unlock_pi-determinism.patch | 7 ++--
...-hb-lock-before-enqueueing-on-the-rtmutex.patch | 11 +++---
...x-Deboost-before-waking-up-the-top-waiter.patch | 5 ++-
...ex-deadline-Fix-a-PI-crash-for-deadline-t.patch | 9 +++--
...ine-rtmutex-Dont-miss-the-dl_runtime-dl_p.patch | 5 ++-
.../features/all/rt/0021-rtmutex-Clean-up.patch | 5 ++-
...2-sched-rtmutex-Refactor-rt_mutex_setprio.patch | 9 +++--
...hed-tracing-Update-trace_sched_pi_setprio.patch | 5 ++-
...0024-rtmutex-Fix-PI-chain-order-integrity.patch | 5 ++-
.../0025-rtmutex-Fix-more-prio-comparisons.patch | 5 ++-
...g-preempt-count-leak-in-rt_mutex_futex_un.patch | 5 ++-
.../0027-futex-Avoid-freeing-an-active-timer.patch | 7 ++--
...mall-and-harmless-looking-inconsistencies.patch | 5 ++-
...rify-mark_wake_futex-memory-barrier-usage.patch | 5 ++-
.../rt/0030-MAINTAINERS-Add-FUTEX-SUBSYSTEM.patch | 5 ++-
...-rt_mutex-Fix-rt_mutex_cleanup_proxy_lock.patch | 5 ++-
...t91-do-not-disable-enable-clocks-in-a-row.patch | 5 ++-
...e-clear_tasks_mm_cpumask-call-to-__cpu_di.patch | 5 ++-
...ex-Handle-non-enqueued-waiters-gracefully.patch | 5 ++-
.../all/rt/0035-fs-dcache-include-wait.h.patch | 5 ++-
...36-rbtree-include-rcu.h-because-we-use-it.patch | 5 ++-
.../0037-fs-dcache-init-in_lookup_hashtable.patch | 5 ++-
...don-t-disable-preempt-around-this_cpu_ptr.patch | 7 ++--
...don-t-disable-preemption-while-accessing-.patch | 11 +++---
...t-rid-of-warning-acpi_ioapic_lock-defined.patch | 7 ++--
...0041-rxrpc-remove-unused-static-variables.patch | 5 ++-
...rcu-update-make-RCU_EXPEDITE_BOOT-default.patch | 5 ++-
...cpu-rwsem-use-swait-for-the-wating-writer.patch | 5 ++-
...44-pinctrl-qcom-Use-raw-spinlock-variants.patch | 5 ++-
.../0045-x86-mm-cpa-avoid-wbinvd-for-PREEMPT.patch | 9 +++--
...NFSv4-replace-seqcount_t-with-a-seqlock_t.patch | 9 +++--
...47-sparc64-use-generic-rwsem-spinlocks-rt.patch | 5 ++-
...-kernel-SRCU-provide-a-static-initializer.patch | 5 ++-
...-block-Shorten-interrupt-disabled-regions.patch | 7 ++--
.../0050-timekeeping-Split-jiffies-seqlock.patch | 9 +++--
...count-for-preempt-off-in-preempt_schedule.patch | 5 ++-
.../0052-signal-Revert-ptrace-preempt-magic.patch | 9 +++--
.../rt/0053-arm-Convert-arm-boot_lock-to-raw.patch | 5 ++-
...arm-kprobe-replace-patch_lock-to-raw-lock.patch | 5 ++-
...low-rt-tasks-to-cache-one-sigqueue-struct.patch | 27 +++++++-------
...ers-random-Reduce-preempt-disabled-region.patch | 5 ++-
...T-Remove-irq-handler-when-clock-event-is-.patch | 5 ++-
...-drivers-timer-atmel-pit-fix-double-free_.patch | 5 ++-
...-TCLIB-Allow-higher-clock-rates-for-clock.patch | 5 ++-
...ers-net-Use-disable_irq_nosync-in-8139too.patch | 5 ++-
.../0062-suspend-Prevent-might-sleep-splats.patch | 5 ++-
.../rt/0063-net-flip-lock-dep-thingy.patch.patch | 5 ++-
...064-net-sched-Use-msleep-instead-of-yield.patch | 5 ++-
...Do-not-unmask-io_apic-when-interrupt-is-i.patch | 5 ++-
.../rt/0066-latencyhist-disable-jump-labels.patch | 5 ++-
.../rt/0067-tracing-Add-latency-histograms.patch | 5 ++-
...68-latency_hist-Update-sched_wakeup-probe.patch | 5 ++-
...cy-hist-Consider-new-argument-when-probin.patch | 7 ++--
...cuidle-version-for-preemptoff_hist-trace-.patch | 5 ++-
.../rt/0071-printk-Add-a-printk-kill-switch.patch | 5 ++-
...force_early_printk-boot-param-to-help-wit.patch | 5 ++-
...-rt-Provide-PREEMPT_RT_BASE-config-switch.patch | 5 ++-
...able-config-options-which-are-not-RT-comp.patch | 5 ++-
.../all/rt/0075-kconfig-Add-PREEMPT_RT_FULL.patch | 7 ++--
...UG_ON-WARN_ON-variants-dependend-on-RT-RT.patch | 5 ++-
...u-amd-Use-WARN_ON_NORT-in-__attach_device.patch | 7 ++--
...rt-local_irq_-variants-depending-on-RT-RT.patch | 5 ++-
...preempt-Provide-preempt_-_-no-rt-variants.patch | 5 ++-
.../0080-Intrduce-migrate_disable-cpu_light.patch | 5 ++-
...round-migrate_disable-enable-in-different.patch | 9 +++--
.../all/rt/0082-rt-Add-local-irq-locks.patch | 5 ++-
.../all/rt/0083-locallock-add-local_lock_on.patch | 5 ++-
...disable-interrupts-in-ide-code-for-preemp.patch | 11 +++---
...-Do-not-disable-interrupts-for-PREEMPT-RT.patch | 7 ++--
...Mellanox-IB-driver-patch-use-_nort-primit.patch | 5 ++-
...ort-Do-not-disable-interrupts-on-PREEMPT_.patch | 5 ++-
...-disable-interrupts-on-RT-in-kernel-users.patch | 5 ++-
.../0089-usb-Use-_nort-in-giveback-function.patch | 5 ++-
...-mm-scatterlist-Do-not-disable-irqs-on-RT.patch | 5 ++-
...et-Do-not-protect-workingset_shadow_nodes.patch | 7 ++--
...-signal-Make-__lock_task_sighand-RT-aware.patch | 11 +++---
...ignal-x86-Delay-calling-signals-in-atomic.patch | 11 +++---
...x86-signal-delay-calling-signals-on-32bit.patch | 5 ++-
.../rt/0095-net-wireless-Use-WARN_ON_NORT.patch | 5 ++-
...ffer_head-Replace-bh_uptodate_lock-for-rt.patch | 5 ++-
...-Make-state-lock-and-journal-head-lock-rt.patch | 5 ++-
...98-list_bl-Make-list-head-locking-RT-safe.patch | 5 ++-
.../0099-list_bl-fixup-bogus-lockdep-warning.patch | 5 ++-
.../all/rt/0100-genirq-Disable-irqpoll-on-rt.patch | 5 ++-
.../0101-genirq-Force-interrupt-thread-on-RT.patch | 5 ++-
...102-drivers-net-vortex-fix-locking-issues.patch | 5 ++-
...3-mm-page_alloc-rt-friendly-per-cpu-pages.patch | 5 ++-
...m-page_alloc-Reduce-lock-sections-further.patch | 5 ++-
.../rt/0105-mm-swap-Convert-to-percpu-locked.patch | 7 ++--
...106-mm-perform-lru_add_drain_all-remotely.patch | 5 ++-
...rotect-per-cpu-variables-with-preempt-dis.patch | 7 ++--
...ize-split-page-table-locks-for-vector-pag.patch | 5 ++-
.../0109-mm-bounce-Use-local_irq_save_nort.patch | 5 ++-
.../all/rt/0110-mm-Allow-only-slub-on-RT.patch | 5 ++-
.../all/rt/0111-mm-Enable-SLUB-for-RT.patch | 19 +++++-----
.../rt/0112-slub-Enable-irqs-for-__GFP_WAIT.patch | 5 ++-
.../rt/0113-slub-Disable-SLUB_CPU_PARTIAL.patch | 5 ++-
...oc-Use-local_lock_on-instead-of-plain-spi.patch | 5 ++-
...ol-Don-t-call-schedule_work_on-in-preempt.patch | 5 ++-
...ol-Replace-local_irq_disable-with-local-l.patch | 5 ++-
...ol-mem_cgroup_migrate-replace-another-loc.patch | 5 ++-
...dev-don-t-disable-IRQs-in-wb_congested_pu.patch | 5 ++-
...smalloc-copy-with-get_cpu_var-and-locking.patch | 7 ++--
.../all/rt/0120-radix-tree-use-local-locks.patch | 5 ++-
...get_random_bytes-for-RT_FULL-in-init_oops.patch | 5 ++-
.../0122-timers-Prepare-for-full-preemption.patch | 21 ++++++-----
...delay-waking-softirqs-from-the-jiffy-tick.patch | 9 +++--
.../rt/0125-hrtimer-enfore-64byte-alignment.patch | 5 ++-
...-deadline-dl_task_timer-has-to-be-irqsafe.patch | 10 ++++--
.../all/rt/0128-timer-fd-Prevent-live-lock.patch | 5 ++-
...-broadcast-Make-broadcast-hrtimer-irqsafe.patch | 5 ++-
...rtimer-check-properly-for-a-running-timer.patch | 5 ++-
...osix-timers-Thread-posix-cpu-timers-on-rt.patch | 9 +++--
...132-sched-Move-task_struct-cleanup-to-RCU.patch | 11 +++---
...t-the-number-of-task-migrations-per-batch.patch | 5 ++-
.../rt/0134-sched-Move-mmdrop-to-RCU-on-RT.patch | 9 +++--
...d-move-stack-kprobe-clean-up-to-__put_tas.patch | 11 +++---
...aved_state-for-tasks-blocked-on-sleeping-.patch | 5 ++-
...nt-task-state-corruption-by-spurious-lock.patch | 5 ++-
.../all/rt/0138-sched-Remove-TASK_ALL.patch | 5 ++-
...t-account-rcu_preempt_depth-on-RT-in-migh.patch | 5 ++-
...RT-softirq-semantics-into-account-in-cond.patch | 5 ++-
...e-the-proper-LOCK_OFFSET-for-cond_resched.patch | 5 ++-
.../rt/0142-sched-Disable-TTWU_QUEUE-on-RT.patch | 8 +++--
...sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch | 5 ++-
...Return-success-when-only-changing-the-sav.patch | 5 ++-
...ueue-Only-wake-up-idle-workers-if-not-blo.patch | 5 ++-
...ne-convert-stop_machine_run-to-PREEMPT_RT.patch | 7 ++--
.../rt/0147-stop_machine-Use-raw-spinlocks.patch | 9 +++--
.../0148-hotplug-Lightweight-get-online-cpus.patch | 7 ++--
...149-hotplug-sync_unplug-No-n-in-task-name.patch | 7 ++--
...read-hotplug_pcp-on-pin_current_cpu-retry.patch | 7 ++--
...igrate-disabled-counter-to-tracing-output.patch | 7 ++--
...152-hotplug-Use-migrate-disable-on-unplug.patch | 9 +++--
.../all/rt/0153-lockdep-Make-it-RT-aware.patch | 5 ++-
...0154-locking-Disable-spin-on-owner-for-RT.patch | 5 ++-
...vent-tasklets-from-going-into-infinite-sp.patch | 5 ++-
...ck-preemption-after-reenabling-interrupts.patch | 23 ++++++------
...157-softirq-Disable-softirq-stacks-for-RT.patch | 11 +++---
.../all/rt/0158-softirq-Split-softirq-locks.patch | 19 +++++-----
.../0159-kernel-softirq-unlock-with-irqs-on.patch | 5 ++-
...ate_disable-do-fastpath-in-atomic-irqs-of.patch | 5 ++-
...w-disabling-of-softirq-processing-in-irq-.patch | 5 ++-
...irq-split-timer-softirqs-out-of-ksoftirqd.patch | 5 ++-
...-softirq-wake-the-timer-softirq-if-needed.patch | 5 ++-
.../rt/0166-rtmutex-trylock-is-okay-on-RT.patch | 5 ++-
.../0167-gpu-don-t-check-for-the-lock-owner.patch | 5 ++-
...68-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch | 7 ++--
...dle-the-various-new-futex-race-conditions.patch | 7 ++--
...-bug-on-when-a-requeued-RT-task-times-out.patch | 5 ++-
...e-lock-unlock-symetry-versus-pi_lock-and-.patch | 5 ++-
.../all/rt/0172-pid.h-include-atomic.h.patch | 5 ++-
...0173-arm-include-definition-for-cpumask_t.patch | 5 ++-
...ktorture-Do-NOT-include-rwlock.h-directly.patch | 5 ++-
.../0175-rtmutex-Add-rtmutex_lock_killable.patch | 5 ++-
.../rt/0176-rtmutex-Make-lock_killable-work.patch | 5 ++-
...0177-spinlock-Split-the-lock-types-header.patch | 5 ++-
.../all/rt/0178-rtmutex-Avoid-include-hell.patch | 5 ++-
.../0179-rbtree-don-t-include-the-rcu-header.patch | 5 ++-
...-Add-the-preempt-rt-lock-replacement-APIs.patch | 9 +++--
...ex_disable-on-DEBUG-configs-and-the-GPL-s.patch | 5 ++-
...king-use-an-exclusive-wait_q-for-sleepers.patch | 9 +++--
.../rt/0183-rtmutex-Add-RT-aware-ww-locks.patch | 5 ++-
.../0184-rtmutex-Provide-rt_mutex_lock_state.patch | 5 ++-
.../rt/0185-rtmutex-Provide-locked-slowpath.patch | 5 ++-
...tex-rtmutex-Cure-RT-double-blocking-issue.patch | 5 ++-
...7-rwsem-rt-Lift-single-reader-restriction.patch | 5 ++-
...8-ptrace-fix-ptrace-vs-tasklist_lock-race.patch | 7 ++--
.../all/rt/0189-rcu-Frob-softirq-test.patch | 5 ++-
.../0190-rcu-Merge-RCU-bh-into-RCU-preempt.patch | 5 ++-
...cu-Make-ksoftirqd-do-RCU-quiescent-states.patch | 5 ++-
..._bh_qs-Disable-irq-while-calling-rcu_pree.patch | 5 ++-
...tty-serial-omap-Make-the-locking-RT-aware.patch | 5 ++-
...-serial-pl011-Make-the-locking-work-on-RT.patch | 5 ++-
...-rt-Improve-the-serial-console-PASS_LIMIT.patch | 5 ++-
...l-8250-don-t-take-the-trylock-during-oops.patch | 5 ++-
.../all/rt/0197-wait.h-include-atomic.h.patch | 5 ++-
...rk-simple-Simple-work-queue-implemenation.patch | 5 ++-
.../0199-completion-Use-simple-wait-queues.patch | 9 +++--
.../all/rt/0200-fs-aio-simple-simple-work.patch | 5 ++-
...ot-invoke-the-affinity-callback-via-a-wor.patch | 7 ++--
...-Move-schedule_work-call-to-helper-thread.patch | 5 ++-
...cpu-rwsem-Remove-preempt_disable-variants.patch | 13 ++++---
.../all/rt/0204-fs-namespace-preemption-fix.patch | 5 ++-
...activate_mm-by-preempt_-disable-enable-_r.patch | 5 ++-
...ock-Turn-off-warning-which-is-bogus-on-RT.patch | 7 ++--
...0207-fs-ntfs-disable-interrupt-only-on-RT.patch | 5 ++-
...bd2-pull-your-plug-when-waiting-for-space.patch | 5 ++-
.../rt/0209-x86-Convert-mce-timer-to-hrtimer.patch | 7 ++--
...0-x86-mce-use-swait-queue-for-mce-wakeups.patch | 5 ++-
...86-stackprotector-Avoid-random-pool-on-rt.patch | 5 ++-
...212-x86-Use-generic-rwsem_spinlocks-on-rt.patch | 7 ++--
.../rt/0213-x86-UV-raw_spinlock-conversion.patch | 9 +++--
...4-thermal-Defer-thermal-wakups-to-threads.patch | 7 ++--
...-fs-epoll-Do-not-disable-preemption-on-RT.patch | 5 ++-
...Another-preempt-disable-region-which-suck.patch | 5 ++-
.../all/rt/0217-block-mq-use-cpu_light.patch | 9 +++--
...18-block-mq-do-not-invoke-preempt_disable.patch | 7 ++--
...-block-mq-don-t-complete-requests-via-IPI.patch | 9 +++--
...raid5-Make-raid5_percpu-handling-RT-aware.patch | 15 ++++----
.../all/rt/0221-rt-Introduce-cpu_chill.patch | 5 ++-
...l-Add-a-UNINTERRUPTIBLE-hrtimer_nanosleep.patch | 9 +++--
.../all/rt/0223-block-blk-mq-Use-swait.patch | 9 +++--
.../0224-block-Use-cpu_chill-for-retry-loops.patch | 7 ++--
...-fs-dcache-Use-cpu_chill-in-trylock-loops.patch | 11 +++---
...26-net-Use-cpu_chill-instead-of-cpu_relax.patch | 7 ++--
...ache-use-swait_queue-instead-of-waitqueue.patch | 7 ++--
...d-Distangle-worker-accounting-from-rqlock.patch | 9 +++--
...al-lock-instead-of-preempt-enable-disable.patch | 5 ++-
.../all/rt/0233-percpu_ida-Use-local-locks.patch | 5 ++-
.../all/rt/0234-debugobjects-Make-RT-aware.patch | 5 ++-
...ump-label-disable-if-stop_machine-is-used.patch | 5 ++-
.../rt/0236-seqlock-Prevent-rt-starvation.patch | 5 ++-
...ake-svc_xprt_do_enqueue-use-get_cpu_light.patch | 9 +++--
.../rt/0238-net-Use-skbufhead-with-raw-lock.patch | 21 ++++++-----
...cpuhotplug-Drain-input_pkt_queue-lockless.patch | 9 +++--
...xmit_recursion-to-per-task-variable-on-RT.patch | 13 ++++---
...-a-way-to-delegate-processing-a-softirq-t.patch | 9 +++--
...ays-take-qdisc-s-busylock-in-__dev_xmit_s.patch | 9 +++--
...-net-Qdisc-use-a-seqlock-instead-seqcount.patch | 5 ++-
...k-the-missing-serialization-in-ip_send_un.patch | 7 ++--
.../rt/0245-net-add-a-lock-around-icmp_sk.patch | 7 ++--
...napi_schedule_irqoff-disable-interrupts-o.patch | 11 +++---
.../features/all/rt/0247-net-sysrq-via-icmp.patch | 11 +++---
...qwork-push-most-work-into-softirq-context.patch | 41 ++++++++++++----------
...irqwork-Move-irq-safe-work-to-irq-context.patch | 11 +++---
...-snd_pcm_stream_lock-irqs_disabled-splats.patch | 5 ++-
.../all/rt/0251-printk-Make-rt-aware.patch | 7 ++--
...tk-Don-t-try-to-print-from-IRQ-NMI-region.patch | 5 ++-
...53-printk-Drop-the-logbuf_lock-more-often.patch | 5 ++-
.../rt/0254-powerpc-Use-generic-rwsem-on-RT.patch | 5 ++-
...-Disable-in-kernel-MPIC-emulation-for-PRE.patch | 5 ++-
...-device-init.c-adapt-to-completions-using.patch | 5 ++-
...-at91-tclib-Default-to-tclib-timer-for-RT.patch | 5 ++-
.../rt/0258-arm-unwind-use-a-raw_spin_lock.patch | 5 ++-
...irq-in-translation-section-permission-fau.patch | 5 ++-
...pdate-irq_set_irqchip_state-documentation.patch | 5 ++-
...64-downgrade-preempt_disable-d-region-to-.patch | 5 ++-
.../rt/0262-arm64-xen-Make-XEN-depend-on-RT.patch | 5 ++-
.../0263-kgdb-serial-Short-term-workaround.patch | 9 +++--
.../0264-sysfs-Add-sys-kernel-realtime-entry.patch | 5 ++-
.../rt/0265-powerpc-Disable-highmem-on-RT.patch | 5 ++-
.../all/rt/0266-mips-Disable-highmem-on-RT.patch | 5 ++-
.../all/rt/0267-mm-rt-kmap_atomic-scheduling.patch | 5 ++-
...0268-mm-rt-Fix-generic-kmap_atomic-for-RT.patch | 5 ++-
...-x86-highmem-Add-a-already-used-pte-check.patch | 5 ++-
.../rt/0270-arm-highmem-Flush-tlb-on-unmap.patch | 5 ++-
.../all/rt/0271-arm-Enable-highmem-for-rt.patch | 5 ++-
.../rt/0272-ipc-sem-Rework-semaphore-wakeups.patch | 7 ++--
.../rt/0273-x86-kvm-Require-const-tsc-for-RT.patch | 9 +++--
...lapic-mark-LAPIC-timer-handler-as-irqsafe.patch | 5 ++-
.../all/rt/0275-scsi-fcoe-Make-RT-aware.patch | 7 ++--
...i-dont-t-disable-interrupts-in-qc_issue-h.patch | 5 ++-
...86-crypto-Reduce-preempt-disabled-regions.patch | 5 ++-
...educe-preempt-disabled-regions-more-algos.patch | 9 +++--
.../features/all/rt/0279-dm-Make-rt-aware.patch | 5 ++-
...vert-acpi_gbl_hardware-lock-back-to-a-raw.patch | 5 ++-
...sk-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch | 7 ++--
.../all/rt/0282-random-Make-it-work-on-rt.patch | 5 ++-
...3-random-avoid-preempt_disable-ed-section.patch | 5 ++-
...ke-hotplug.lock-a-sleeping-spinlock-on-RT.patch | 9 +++--
...285-cpu-rt-Rework-cpu-down-for-PREEMPT_RT.patch | 7 ++--
...g-Document-why-PREEMPT_RT-uses-a-spinlock.patch | 7 ++--
...fix-cpu-down-problem-if-kthread-s-cpu-is-.patch | 7 ++--
...plug-restore-original-cpu-mask-oncpu-down.patch | 9 +++--
.../0289-cpu_down-move-migrate_enable-back.patch | 9 +++--
...-set_cpus_allowed_ptr-in-sync_unplug_thre.patch | 7 ++--
...cking-Reenable-migration-accross-schedule.patch | 7 ++--
...x-Use-local_irq_save_nort-in-qla2x00_poll.patch | 5 ++-
...t-Remove-preemption-disabling-in-netif_rx.patch | 11 +++---
...nother-local_irq_disable-kmalloc-headache.patch | 7 ++--
...otect-users-of-napi_alloc_cache-against-r.patch | 7 ++--
...er-Serialize-xt_write_recseq-sections-on-.patch | 7 ++--
...-net-Add-a-mutex-around-devnet_rename_seq.patch | 15 ++++----
...pto-Convert-crypto-notifier-chain-to-SRCU.patch | 5 ++-
...ftest-Only-do-hardirq-context-test-for-ra.patch | 5 ++-
...ftest-fix-warnings-due-to-missing-PREEMPT.patch | 5 ++-
...wevent-hrtimer-run-in-irq-instead-of-soft.patch | 5 ++-
...-mark-perf_cpu_context-s-timer-as-irqsafe.patch | 5 ++-
.../rt/0303-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch | 5 ++-
...Eliminate-softirq-processing-from-rcutree.patch | 5 ++-
.../rt/0305-rcu-make-RCU_BOOST-default-on-RT.patch | 5 ++-
...e-rcu_normal_after_boot-by-default-for-RT.patch | 5 ++-
...307-sched-Add-support-for-lazy-preemption.patch | 11 +++---
.../0308-ftrace-Fix-trace-header-alignment.patch | 7 ++--
.../0310-arm-Add-support-for-lazy-preemption.patch | 13 ++++---
...1-powerpc-Add-support-for-lazy-preemption.patch | 17 +++++----
.../0312-arch-arm64-Add-lazy-preempt-support.patch | 9 +++--
...te-disable-handle-updated-task-mask-mg-di.patch | 5 ++-
...14-leds-trigger-disable-CPU-trigger-on-RT.patch | 5 ++-
.../rt/0315-mmci-Remove-bogus-local_irq_save.patch | 5 ++-
...req-drop-K8-s-driver-from-beeing-selected.patch | 5 ++-
...n_proc-Protect-send_msg-with-a-local-lock.patch | 5 ++-
...ck-zram-Replace-bit-spinlocks-with-rtmute.patch | 11 +++---
...m-Don-t-disable-preemption-in-zcomp_strea.patch | 7 ++--
...5-drop-trace_i915_gem_ring_dispatch-on-rt.patch | 5 ++-
...warning-from-i915-when-running-on-PREEMPT.patch | 5 ++-
...i915-Use-preempt_disable-enable_rt-where-.patch | 5 ++-
...e-local_lock-unlock_irq-in-intel_pipe_upd.patch | 5 ++-
...24-cgroups-use-simple-wait-in-css_release.patch | 5 ++-
...Prevent-scheduling-while-atomic-in-cgroup.patch | 5 ++-
...t-Convert-callback_lock-to-raw_spinlock_t.patch | 5 ++-
...-call-to-schedule_delayed_work-to-helper-.patch | 5 ++-
.../features/all/rt/0328-md-disable-bcache.patch | 5 ++-
...29-workqueue-Prevent-deadlock-stall-on-RT.patch | 13 ++++---
.../rt/0330-Add-localversion-for-RT-release.patch | 5 ++-
...m-fix-zcomp_stream_get-smp_processor_id-u.patch | 5 ++-
...isable-preemption-on-i_dir_seq-s-write-si.patch | 9 +++--
.../0333-tpm_tis-fix-stall-after-iowrite-s.patch | 5 ++-
...two-more-BH_Uptodate_Lock-related-bitspin.patch | 5 ++-
...mutex-fix-deadlock-in-device-mapper-block.patch | 5 ++-
.../0336-md-raid5-do-not-disable-interrupts.patch | 9 +++--
...ontrol-Prevent-scheduling-while-atomic-in.patch | 5 ++-
...bd2-pull-your-plug-when-waiting-for-space.patch | 5 ++-
.../rt/0339-rtmutex-Fix-lock-stealing-logic.patch | 5 ++-
...m-replace-raw_notifier-to-atomic_notifier.patch | 5 ++-
...ace-raw_notifier-with-atomic_notifier-fix.patch | 5 ++-
...rtimer-migrate-deferred-timer-on-CPU-down.patch | 5 ++-
...ake-the-tcp_sk_lock-lock-with-BH-disabled.patch | 7 ++--
...mer-don-t-wakeup-a-process-while-holding-.patch | 9 +++--
...mer-hotplug-don-t-wake-ktimersoftd-while-.patch | 5 ++-
...void-recursive-locking-in-hci_send_to_cha.patch | 5 ++-
...se-raw_cpu_ptr-instead-of-get_cpu_ptr-for.patch | 7 ++--
...-rt-locking-allow-recursive-local_trylock.patch | 5 ++-
...ng-rtmutex-don-t-drop-the-wait_lock-twice.patch | 5 ++-
.../all/rt/0350-net-use-trylock-in-icmp_sk.patch | 7 ++--
.../all/rt/0351-Linux-4.9.68-rt60-REBASE.patch | 16 ---------
.../all/rt/0351-Linux-4.9.76-rt61-REBASE.patch | 19 ++++++++++
debian/patches/series-rt | 2 +-
345 files changed, 1685 insertions(+), 657 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 84efe34..bf1e8ae 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -81,7 +81,7 @@ linux (4.9.82-1) UNRELEASED; urgency=medium
* [x86] linux-headers: Depend on updated linux-compiler-gcc-6-x86 for
retpoline support.
* [x86] Add versioned build-dependency on gcc-6 for retpoline support.
- * [rt] Refresh patchset against 4.9.82.
+ * [rt] Update to 4.9.76-rt61 except patches refreshed locally since 4.9.76.
* [rt] Add gpg key for Julia Cartwright (0x0A120DD923EEDD5F) to upstream
keyring
diff --git a/debian/patches/features/all/rt/0001-timer-make-the-base-lock-raw.patch b/debian/patches/features/all/rt/0001-timer-make-the-base-lock-raw.patch
index 538e1ac..a251a9a 100644
--- a/debian/patches/features/all/rt/0001-timer-make-the-base-lock-raw.patch
+++ b/debian/patches/features/all/rt/0001-timer-make-the-base-lock-raw.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 13 Jul 2016 18:22:23 +0200
Subject: [PATCH 001/351] timer: make the base lock raw
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=729899e04162021cad7ce71ab460abdf612bd827
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b847b92f4588d56db2472d5d85bc2e2d30403e11
The part where the base lock is held got more predictable / shorter after the
timer rework. One reason is the lack of re-cascading.
@@ -13,7 +13,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
-index 7d670362891a..0e9cb65c533c 100644
+index e872f7f05e8a..f61ccaf457ae 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -193,7 +193,7 @@ EXPORT_SYMBOL(jiffies_64);
@@ -25,7 +25,7 @@ index 7d670362891a..0e9cb65c533c 100644
struct timer_list *running_timer;
unsigned long clk;
unsigned long next_expiry;
-@@ -955,10 +955,10 @@ static struct timer_base *lock_timer_base(struct timer_list *timer,
+@@ -953,10 +953,10 @@ static struct timer_base *lock_timer_base(struct timer_list *timer,
if (!(tf & TIMER_MIGRATING)) {
base = get_timer_base(tf);
@@ -38,7 +38,7 @@ index 7d670362891a..0e9cb65c533c 100644
}
cpu_relax();
}
-@@ -1037,9 +1037,9 @@ __mod_timer(struct timer_list *timer, unsigned long expires, bool pending_only)
+@@ -1033,9 +1033,9 @@ __mod_timer(struct timer_list *timer, unsigned long expires, bool pending_only)
/* See the comment in lock_timer_base() */
timer->flags |= TIMER_MIGRATING;
@@ -50,7 +50,7 @@ index 7d670362891a..0e9cb65c533c 100644
WRITE_ONCE(timer->flags,
(timer->flags & ~TIMER_BASEMASK) | base->cpu);
forward_timer_base(base);
-@@ -1062,7 +1062,7 @@ __mod_timer(struct timer_list *timer, unsigned long expires, bool pending_only)
+@@ -1060,7 +1060,7 @@ __mod_timer(struct timer_list *timer, unsigned long expires, bool pending_only)
}
out_unlock:
@@ -59,7 +59,7 @@ index 7d670362891a..0e9cb65c533c 100644
return ret;
}
-@@ -1156,9 +1156,9 @@ void add_timer_on(struct timer_list *timer, int cpu)
+@@ -1154,9 +1154,9 @@ void add_timer_on(struct timer_list *timer, int cpu)
if (base != new_base) {
timer->flags |= TIMER_MIGRATING;
@@ -71,7 +71,7 @@ index 7d670362891a..0e9cb65c533c 100644
WRITE_ONCE(timer->flags,
(timer->flags & ~TIMER_BASEMASK) | cpu);
}
-@@ -1166,7 +1166,7 @@ void add_timer_on(struct timer_list *timer, int cpu)
+@@ -1164,7 +1164,7 @@ void add_timer_on(struct timer_list *timer, int cpu)
debug_activate(timer, timer->expires);
internal_add_timer(base, timer);
@@ -80,7 +80,7 @@ index 7d670362891a..0e9cb65c533c 100644
}
EXPORT_SYMBOL_GPL(add_timer_on);
-@@ -1193,7 +1193,7 @@ int del_timer(struct timer_list *timer)
+@@ -1191,7 +1191,7 @@ int del_timer(struct timer_list *timer)
if (timer_pending(timer)) {
base = lock_timer_base(timer, &flags);
ret = detach_if_pending(timer, base, true);
@@ -89,7 +89,7 @@ index 7d670362891a..0e9cb65c533c 100644
}
return ret;
-@@ -1221,7 +1221,7 @@ int try_to_del_timer_sync(struct timer_list *timer)
+@@ -1219,7 +1219,7 @@ int try_to_del_timer_sync(struct timer_list *timer)
timer_stats_timer_clear_start_info(timer);
ret = detach_if_pending(timer, base, true);
}
@@ -98,7 +98,7 @@ index 7d670362891a..0e9cb65c533c 100644
return ret;
}
-@@ -1353,13 +1353,13 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head)
+@@ -1351,13 +1351,13 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head)
data = timer->data;
if (timer->flags & TIMER_IRQSAFE) {
@@ -116,7 +116,7 @@ index 7d670362891a..0e9cb65c533c 100644
}
}
}
-@@ -1528,7 +1528,7 @@ u64 get_next_timer_interrupt(unsigned long basej, u64 basem)
+@@ -1526,7 +1526,7 @@ u64 get_next_timer_interrupt(unsigned long basej, u64 basem)
if (cpu_is_offline(smp_processor_id()))
return expires;
@@ -125,7 +125,7 @@ index 7d670362891a..0e9cb65c533c 100644
nextevt = __next_timer_interrupt(base);
is_max_delta = (nextevt == base->clk + NEXT_TIMER_MAX_DELTA);
base->next_expiry = nextevt;
-@@ -1562,7 +1562,7 @@ u64 get_next_timer_interrupt(unsigned long basej, u64 basem)
+@@ -1560,7 +1560,7 @@ u64 get_next_timer_interrupt(unsigned long basej, u64 basem)
base->is_idle = true;
}
}
@@ -134,7 +134,7 @@ index 7d670362891a..0e9cb65c533c 100644
return cmp_next_hrtimer_event(basem, expires);
}
-@@ -1649,7 +1649,7 @@ static inline void __run_timers(struct timer_base *base)
+@@ -1647,7 +1647,7 @@ static inline void __run_timers(struct timer_base *base)
if (!time_after_eq(jiffies, base->clk))
return;
@@ -143,7 +143,7 @@ index 7d670362891a..0e9cb65c533c 100644
while (time_after_eq(jiffies, base->clk)) {
-@@ -1660,7 +1660,7 @@ static inline void __run_timers(struct timer_base *base)
+@@ -1658,7 +1658,7 @@ static inline void __run_timers(struct timer_base *base)
expire_timers(base, heads + levels);
}
base->running_timer = NULL;
@@ -152,7 +152,7 @@ index 7d670362891a..0e9cb65c533c 100644
}
/*
-@@ -1868,16 +1868,16 @@ int timers_dead_cpu(unsigned int cpu)
+@@ -1881,16 +1881,16 @@ int timers_dead_cpu(unsigned int cpu)
* The caller is globally serialized and nobody else
* takes two locks at once, deadlock is not possible.
*/
@@ -173,7 +173,7 @@ index 7d670362891a..0e9cb65c533c 100644
put_cpu_ptr(&timer_bases);
}
return 0;
-@@ -1893,7 +1893,7 @@ static void __init init_timer_cpu(int cpu)
+@@ -1906,7 +1906,7 @@ static void __init init_timer_cpu(int cpu)
for (i = 0; i < NR_BASES; i++) {
base = per_cpu_ptr(&timer_bases[i], cpu);
base->cpu = cpu;
@@ -182,3 +182,6 @@ index 7d670362891a..0e9cb65c533c 100644
base->clk = jiffies;
}
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0002-lockdep-Handle-statically-initialized-PER_CPU-locks-.patch b/debian/patches/features/all/rt/0002-lockdep-Handle-statically-initialized-PER_CPU-locks-.patch
index a5506e3..8cdced0 100644
--- a/debian/patches/features/all/rt/0002-lockdep-Handle-statically-initialized-PER_CPU-locks-.patch
+++ b/debian/patches/features/all/rt/0002-lockdep-Handle-statically-initialized-PER_CPU-locks-.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 17 Feb 2017 19:44:39 +0100
Subject: [PATCH 002/351] lockdep: Handle statically initialized PER_CPU locks
proper
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=90d2ef5de7ac852039f6619fc8c0f841d3c6d280
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a7f8460e57b57e670938611374b0fc11f195c555
If a PER_CPU struct which contains a spin_lock is statically initialized
via:
@@ -276,3 +276,6 @@ index f014cebbf405..90349153b49d 100644
/**
* per_cpu_ptr_to_phys - convert translated percpu address to physical address
* @addr: the address to be converted to physical address
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0003-lockdep-Fix-compilation-error-for-CONFIG_MODULES-and.patch b/debian/patches/features/all/rt/0003-lockdep-Fix-compilation-error-for-CONFIG_MODULES-and.patch
index 7e0d14f..ac4e5bd 100644
--- a/debian/patches/features/all/rt/0003-lockdep-Fix-compilation-error-for-CONFIG_MODULES-and.patch
+++ b/debian/patches/features/all/rt/0003-lockdep-Fix-compilation-error-for-CONFIG_MODULES-and.patch
@@ -2,7 +2,7 @@ From: Dan Murphy <dmurphy at ti.com>
Date: Fri, 24 Feb 2017 08:41:49 -0600
Subject: [PATCH 003/351] lockdep: Fix compilation error for !CONFIG_MODULES
and !CONFIG_SMP
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=04290ef7aa427a278b49b5872ac959e7a9b5126b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ebf0b8f1db6ce6336c9c72ed71cea79a6f2ddbb7
When CONFIG_MODULES is not set then it fails to compile in lockdep:
@@ -58,3 +58,6 @@ index 289616d8ccfd..3483a3743b44 100644
#endif /* CONFIG_SMP */
#define MODINFO_ATTR(field) \
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0004-lockdep-Fix-per-cpu-static-objects.patch b/debian/patches/features/all/rt/0004-lockdep-Fix-per-cpu-static-objects.patch
index 60f7f6d..533c109 100644
--- a/debian/patches/features/all/rt/0004-lockdep-Fix-per-cpu-static-objects.patch
+++ b/debian/patches/features/all/rt/0004-lockdep-Fix-per-cpu-static-objects.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Mon, 20 Mar 2017 12:26:55 +0100
Subject: [PATCH 004/351] lockdep: Fix per-cpu static objects
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=490cf29da27b6166beab375d86beb70f0be43afa
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9e7bd782b3f6cd7a65764b135ba9d60b4c76dfb5
Since commit 383776fa7527 ("locking/lockdep: Handle statically initialized
PER_CPU locks properly") we try to collapse per-cpu locks into a single
@@ -72,7 +72,7 @@ index 8e0cb7a0f836..68123c1fe549 100644
/*
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index 26a4f74bff83..164b86a8b4e2 100644
+index 802eb3361a0a..dac06acbae9d 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -1242,6 +1242,8 @@ core_initcall(cpu_hotplug_pm_sync_init);
@@ -130,3 +130,6 @@ index 90349153b49d..4e739fcf91bf 100644
return true;
}
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0005-futex-Cleanup-variable-names-for-futex_top_waiter.patch b/debian/patches/features/all/rt/0005-futex-Cleanup-variable-names-for-futex_top_waiter.patch
index 4221f05..bd0a9b3 100644
--- a/debian/patches/features/all/rt/0005-futex-Cleanup-variable-names-for-futex_top_waiter.patch
+++ b/debian/patches/features/all/rt/0005-futex-Cleanup-variable-names-for-futex_top_waiter.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:48 +0100
Subject: [PATCH 005/351] futex: Cleanup variable names for futex_top_waiter()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e508a6de022c6e24f364e2a0b6f4f8143408994e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a84178938824443e360c9139868f6e562f59edfc
Upstream commit 499f5aca2cdd5e958b27e2655e7e7f82524f46b1
@@ -105,7 +105,7 @@ index 88bad86180ac..bc48b369f3fe 100644
int ret;
retry:
-@@ -2656,9 +2656,9 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
+@@ -2656,9 +2656,9 @@ retry:
* all and we at least want to know if user space fiddled
* with the futex value instead of blindly unlocking.
*/
@@ -118,3 +118,6 @@ index 88bad86180ac..bc48b369f3fe 100644
/*
* In case of success wake_futex_pi dropped the hash
* bucket lock.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0006-futex-Use-smp_store_release-in-mark_wake_futex.patch b/debian/patches/features/all/rt/0006-futex-Use-smp_store_release-in-mark_wake_futex.patch
index e2a966c..01207f5 100644
--- a/debian/patches/features/all/rt/0006-futex-Use-smp_store_release-in-mark_wake_futex.patch
+++ b/debian/patches/features/all/rt/0006-futex-Use-smp_store_release-in-mark_wake_futex.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:49 +0100
Subject: [PATCH 006/351] futex: Use smp_store_release() in mark_wake_futex()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a941bea864a5898af72decaedca96d54217657ad
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=62a20b3595f9eb9e7f645df9286a9ef5eddd9131
Upstream commit 1b367ece0d7e696cab1c8501bab282cc6a538b3f
@@ -39,3 +39,6 @@ index bc48b369f3fe..5729150be0bd 100644
}
static int wake_futex_pi(u32 __user *uaddr, u32 uval, struct futex_q *top_waiter,
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0007-futex-Remove-rt_mutex_deadlock_account_.patch b/debian/patches/features/all/rt/0007-futex-Remove-rt_mutex_deadlock_account_.patch
index f7e6f9c..781512f 100644
--- a/debian/patches/features/all/rt/0007-futex-Remove-rt_mutex_deadlock_account_.patch
+++ b/debian/patches/features/all/rt/0007-futex-Remove-rt_mutex_deadlock_account_.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:50 +0100
Subject: [PATCH 007/351] futex: Remove rt_mutex_deadlock_account_*()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=965d53c03e073e5696d2cf1d8d601210b81e48cb
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=da31318d9ab1041c9ce2852ba684b06817c1ba89
Upstream commit fffa954fb528963c2fb7b0c0084eb77e2be7ab52
@@ -61,7 +61,7 @@ diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index 2c49d76f96c3..1c57ff103a5b 100644
--- a/kernel/locking/rtmutex.c
+++ b/kernel/locking/rtmutex.c
-@@ -936,8 +936,6 @@ static int try_to_take_rt_mutex(struct rt_mutex *lock, struct task_struct *task,
+@@ -936,8 +936,6 @@ takeit:
*/
rt_mutex_set_owner(lock, task);
@@ -191,3 +191,6 @@ index c4060584c407..6607802efa8b 100644
#define debug_rt_mutex_init_waiter(w) do { } while (0)
#define debug_rt_mutex_free_waiter(w) do { } while (0)
#define debug_rt_mutex_lock(l) do { } while (0)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0008-futex-rt_mutex-Provide-futex-specific-rt_mutex-API.patch b/debian/patches/features/all/rt/0008-futex-rt_mutex-Provide-futex-specific-rt_mutex-API.patch
index c6c2aff..0a19393 100644
--- a/debian/patches/features/all/rt/0008-futex-rt_mutex-Provide-futex-specific-rt_mutex-API.patch
+++ b/debian/patches/features/all/rt/0008-futex-rt_mutex-Provide-futex-specific-rt_mutex-API.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:51 +0100
Subject: [PATCH 008/351] futex,rt_mutex: Provide futex specific rt_mutex API
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=58f809c8566f4803eb0bb3e83a47340b1bfb92b5
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9664bf5786b3b8fcee37fb0ef1399bb74d214e62
Upstream commit 5293c2efda37775346885c7e924d4ef7018ea60b
@@ -87,7 +87,7 @@ index 5729150be0bd..cf07ae476b76 100644
locked = 1;
goto out;
}
-@@ -2567,7 +2565,7 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
+@@ -2567,7 +2565,7 @@ retry_private:
if (!trylock) {
ret = rt_mutex_timed_futex_lock(&q.pi_state->pi_mutex, to);
} else {
@@ -96,7 +96,7 @@ index 5729150be0bd..cf07ae476b76 100644
/* Fixup the trylock return value: */
ret = ret ? 0 : -EWOULDBLOCK;
}
-@@ -2590,7 +2588,7 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
+@@ -2590,7 +2588,7 @@ retry_private:
* it and return the fault to userspace.
*/
if (ret && (rt_mutex_owner(&q.pi_state->pi_mutex) == current))
@@ -225,3 +225,6 @@ index e317e1cbb3eb..2441c2d2e6f3 100644
extern void rt_mutex_adjust_prio(struct task_struct *task);
#ifdef CONFIG_DEBUG_RT_MUTEXES
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0009-futex-Change-locking-rules.patch b/debian/patches/features/all/rt/0009-futex-Change-locking-rules.patch
index 4c36e38..67cfd70 100644
--- a/debian/patches/features/all/rt/0009-futex-Change-locking-rules.patch
+++ b/debian/patches/features/all/rt/0009-futex-Change-locking-rules.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:52 +0100
Subject: [PATCH 009/351] futex: Change locking rules
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3df179d9d97ca3616702e8ba3ebf97d5b5c2e8fa
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=27d36f21a268964814c3780f878797d1f52fef51
Upstream commit 734009e96d1983ad739e5b656e03430b3660c913
@@ -254,7 +254,7 @@ index cf07ae476b76..2d2267efc3cc 100644
if (ret) {
raw_spin_unlock_irq(&pi_state->pi_mutex.wait_lock);
return ret;
-@@ -1822,7 +1906,7 @@ static int futex_requeue(u32 __user *uaddr1, unsigned int flags,
+@@ -1822,7 +1906,7 @@ retry_private:
* If that call succeeds then we have pi_state and an
* initial refcount on it.
*/
@@ -294,7 +294,7 @@ index cf07ae476b76..2d2267efc3cc 100644
*/
retry:
if (get_futex_value_locked(&uval, uaddr))
-@@ -2165,47 +2251,60 @@ static int fixup_pi_state_owner(u32 __user *uaddr, struct futex_q *q,
+@@ -2165,47 +2251,60 @@ retry:
* itself.
*/
if (pi_state->owner != NULL) {
@@ -370,3 +370,6 @@ index cf07ae476b76..2d2267efc3cc 100644
}
static long futex_wait_restart(struct restart_block *restart);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0010-futex-Cleanup-refcounting.patch b/debian/patches/features/all/rt/0010-futex-Cleanup-refcounting.patch
index c7bb7a3..3b400bd 100644
--- a/debian/patches/features/all/rt/0010-futex-Cleanup-refcounting.patch
+++ b/debian/patches/features/all/rt/0010-futex-Cleanup-refcounting.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:53 +0100
Subject: [PATCH 010/351] futex: Cleanup refcounting
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=848aba0a4dfb1dae94bf67c41374a58700c1194a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1b910ebd1754af99e179636c0f1c5ce5e8cc1401
Upstream commit bf92cf3a5100f5a0d5f9834787b130159397cb22
@@ -67,7 +67,7 @@ index 2d2267efc3cc..b970b95f0508 100644
raw_spin_unlock_irq(&pi_state->pi_mutex.wait_lock);
*ps = pi_state;
return 0;
-@@ -1989,7 +1994,7 @@ static int futex_requeue(u32 __user *uaddr1, unsigned int flags,
+@@ -1989,7 +1994,7 @@ retry_private:
* refcount on the pi_state and store the pointer in
* the futex_q object of the waiter.
*/
@@ -76,3 +76,6 @@ index 2d2267efc3cc..b970b95f0508 100644
this->pi_state = pi_state;
ret = rt_mutex_start_proxy_lock(&pi_state->pi_mutex,
this->rt_waiter,
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0011-futex-Rework-inconsistent-rt_mutex-futex_q-state.patch b/debian/patches/features/all/rt/0011-futex-Rework-inconsistent-rt_mutex-futex_q-state.patch
index ee5ce43..4bf4f7f 100644
--- a/debian/patches/features/all/rt/0011-futex-Rework-inconsistent-rt_mutex-futex_q-state.patch
+++ b/debian/patches/features/all/rt/0011-futex-Rework-inconsistent-rt_mutex-futex_q-state.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:54 +0100
Subject: [PATCH 011/351] futex: Rework inconsistent rt_mutex/futex_q state
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c6ab217e45a3a33d61bfabeae7b5b3c68fe13a6d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=95a5f543b2e7385428db77014165b4c1fdb52656
Upstream commit 73d786bd043ebc855f349c81ea805f6b11cbf2aa
@@ -141,3 +141,6 @@ index b970b95f0508..81439b91133b 100644
out:
return ret ? ret : locked;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0012-futex-Pull-rt_mutex_futex_unlock-out-from-under-hb-l.patch b/debian/patches/features/all/rt/0012-futex-Pull-rt_mutex_futex_unlock-out-from-under-hb-l.patch
index ba3fc22..cd7aeaa 100644
--- a/debian/patches/features/all/rt/0012-futex-Pull-rt_mutex_futex_unlock-out-from-under-hb-l.patch
+++ b/debian/patches/features/all/rt/0012-futex-Pull-rt_mutex_futex_unlock-out-from-under-hb-l.patch
@@ -2,7 +2,7 @@ From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:55 +0100
Subject: [PATCH 012/351] futex: Pull rt_mutex_futex_unlock() out from under
hb->lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2a548f7db3e1af99e54405e42fe0e056b6006e81
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2128fbc9dc8cc940dc5af625ec8cd4577a1228b5
Upstream commit 16ffa12d742534d4ff73e8b3a4e81c1de39196f0
@@ -188,7 +188,7 @@ index 81439b91133b..f23864847549 100644
* We have to replace the newowner TID in the user space variable.
* This must be atomic as we have to preserve the owner died bit here.
*
-@@ -2248,7 +2246,7 @@ static int fixup_pi_state_owner(u32 __user *uaddr, struct futex_q *q,
+@@ -2248,7 +2246,7 @@ retry:
if (get_futex_value_locked(&uval, uaddr))
goto handle_fault;
@@ -216,7 +216,7 @@ index 81439b91133b..f23864847549 100644
struct futex_hash_bucket *hb;
struct futex_q q = futex_q_init;
int res, ret;
-@@ -2669,12 +2672,19 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
+@@ -2669,12 +2672,19 @@ retry_private:
* If fixup_owner() faulted and was unable to handle the fault, unlock
* it and return the fault to userspace.
*/
@@ -238,7 +238,7 @@ index 81439b91133b..f23864847549 100644
goto out_put_key;
out_unlock_put_key:
-@@ -2737,10 +2747,36 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
+@@ -2737,10 +2747,36 @@ retry:
*/
top_waiter = futex_top_waiter(hb, &key);
if (top_waiter) {
@@ -278,7 +278,7 @@ index 81439b91133b..f23864847549 100644
*/
if (!ret)
goto out_putkey;
-@@ -2755,7 +2791,6 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
+@@ -2755,7 +2791,6 @@ retry:
* setting the FUTEX_WAITERS bit. Try again.
*/
if (ret == -EAGAIN) {
@@ -286,7 +286,7 @@ index 81439b91133b..f23864847549 100644
put_futex_key(&key);
goto retry;
}
-@@ -2763,7 +2798,7 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
+@@ -2763,7 +2798,7 @@ retry:
* wake_futex_pi has detected invalid state. Tell user
* space.
*/
@@ -295,7 +295,7 @@ index 81439b91133b..f23864847549 100644
}
/*
-@@ -2773,8 +2808,10 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
+@@ -2773,8 +2808,10 @@ retry:
* preserve the WAITERS bit not the OWNER_DIED one. We are the
* owner.
*/
@@ -307,7 +307,7 @@ index 81439b91133b..f23864847549 100644
/*
* If uval has changed, let user space handle it.
-@@ -2788,7 +2825,6 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
+@@ -2788,7 +2825,6 @@ out_putkey:
return ret;
pi_faulted:
@@ -359,3 +359,6 @@ index 81439b91133b..f23864847549 100644
if (ret == -EINTR) {
/*
* We've already been requeued, but cannot restart by calling
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0013-futex-rt_mutex-Introduce-rt_mutex_init_waiter.patch b/debian/patches/features/all/rt/0013-futex-rt_mutex-Introduce-rt_mutex_init_waiter.patch
index c87f435..ddb8071 100644
--- a/debian/patches/features/all/rt/0013-futex-rt_mutex-Introduce-rt_mutex_init_waiter.patch
+++ b/debian/patches/features/all/rt/0013-futex-rt_mutex-Introduce-rt_mutex_init_waiter.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:56 +0100
Subject: [PATCH 013/351] futex,rt_mutex: Introduce rt_mutex_init_waiter()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=359f7baeccfb977e3493e858fa908388f2e0d3b8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2638717b61f3ee6a66b1a8eb182f89036024da2e
Upstream commit 50809358dd7199aa7ce232f6877dd09ec30ef374
@@ -84,3 +84,6 @@ index 2441c2d2e6f3..d16de23680a9 100644
extern int rt_mutex_start_proxy_lock(struct rt_mutex *lock,
struct rt_mutex_waiter *waiter,
struct task_struct *task);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0014-futex-rt_mutex-Restructure-rt_mutex_finish_proxy_loc.patch b/debian/patches/features/all/rt/0014-futex-rt_mutex-Restructure-rt_mutex_finish_proxy_loc.patch
index f450000..ef1c0f6 100644
--- a/debian/patches/features/all/rt/0014-futex-rt_mutex-Restructure-rt_mutex_finish_proxy_loc.patch
+++ b/debian/patches/features/all/rt/0014-futex-rt_mutex-Restructure-rt_mutex_finish_proxy_loc.patch
@@ -2,7 +2,7 @@ From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:57 +0100
Subject: [PATCH 014/351] futex,rt_mutex: Restructure
rt_mutex_finish_proxy_lock()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9dfc9cb667a3980b26c81b1430dff934004d50df
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e9695784910ea84ea42a074b89acdaad81da4a1b
Upstream commit 38d589f2fd08f1296aea3ce62bebd185125c6d81
@@ -164,3 +164,6 @@ index d16de23680a9..fedd5abe0b52 100644
extern int rt_mutex_timed_futex_lock(struct rt_mutex *l, struct hrtimer_sleeper *to);
extern int rt_mutex_futex_trylock(struct rt_mutex *l);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0015-futex-Rework-futex_lock_pi-to-use-rt_mutex_-_proxy_l.patch b/debian/patches/features/all/rt/0015-futex-Rework-futex_lock_pi-to-use-rt_mutex_-_proxy_l.patch
index 2adcd3f..a2659c7 100644
--- a/debian/patches/features/all/rt/0015-futex-Rework-futex_lock_pi-to-use-rt_mutex_-_proxy_l.patch
+++ b/debian/patches/features/all/rt/0015-futex-Rework-futex_lock_pi-to-use-rt_mutex_-_proxy_l.patch
@@ -2,7 +2,7 @@ From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:58 +0100
Subject: [PATCH 015/351] futex: Rework futex_lock_pi() to use
rt_mutex_*_proxy_lock()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ac8a0cba48179217dabe9af5d7fc8075850d8a8f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=90a45078102926c03ae09b6f91d03579e5269576
Upstream commit cfafcd117da0216520568c195cb2f6cd1980c4bb
@@ -148,7 +148,7 @@ index b72be871ac27..bff0a7e0cec5 100644
struct futex_hash_bucket *hb;
struct futex_q q = futex_q_init;
int res, ret;
-@@ -2638,24 +2644,51 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
+@@ -2638,24 +2644,51 @@ retry_private:
}
}
@@ -271,3 +271,6 @@ index fedd5abe0b52..4fe3f32da3c5 100644
extern int rt_mutex_futex_trylock(struct rt_mutex *l);
extern void rt_mutex_futex_unlock(struct rt_mutex *lock);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0016-futex-Futex_unlock_pi-determinism.patch b/debian/patches/features/all/rt/0016-futex-Futex_unlock_pi-determinism.patch
index 8ef9666..05d57c7 100644
--- a/debian/patches/features/all/rt/0016-futex-Futex_unlock_pi-determinism.patch
+++ b/debian/patches/features/all/rt/0016-futex-Futex_unlock_pi-determinism.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:35:59 +0100
Subject: [PATCH 016/351] futex: Futex_unlock_pi() determinism
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e3c041714046eb0a7c5d94f96494f005f7e624a5
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fd72c867d3785a7108ab03348ca8f3571619e9ed
Upstream commit bebe5b514345f09be2c15e414d076b02ecb9cce8
@@ -56,7 +56,7 @@ index bff0a7e0cec5..3d1be05af5ec 100644
*
* When this happens, give up our locks and try again, giving
* the futex_lock_pi() instance time to complete, either by
-@@ -2793,15 +2788,18 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
+@@ -2793,15 +2788,18 @@ retry:
if (pi_state->owner != current)
goto out_unlock;
@@ -81,3 +81,6 @@ index bff0a7e0cec5..3d1be05af5ec 100644
spin_unlock(&hb->lock);
ret = wake_futex_pi(uaddr, uval, pi_state);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0017-futex-Drop-hb-lock-before-enqueueing-on-the-rtmutex.patch b/debian/patches/features/all/rt/0017-futex-Drop-hb-lock-before-enqueueing-on-the-rtmutex.patch
index 7d78487..3526d19 100644
--- a/debian/patches/features/all/rt/0017-futex-Drop-hb-lock-before-enqueueing-on-the-rtmutex.patch
+++ b/debian/patches/features/all/rt/0017-futex-Drop-hb-lock-before-enqueueing-on-the-rtmutex.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 22 Mar 2017 11:36:00 +0100
Subject: [PATCH 017/351] futex: Drop hb->lock before enqueueing on the rtmutex
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2a24fa4cf065d2d794ac1049c66f164ae1c3924a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c74962bd11419fc8c525d92e20b4d36bf45f0532
Upstream commit 56222b212e8edb1cf51f5dd73ff645809b082b40
@@ -57,7 +57,7 @@ diff --git a/kernel/futex.c b/kernel/futex.c
index 3d1be05af5ec..cdd205aa929e 100644
--- a/kernel/futex.c
+++ b/kernel/futex.c
-@@ -2653,20 +2653,33 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
+@@ -2653,20 +2653,33 @@ retry_private:
goto no_block;
}
@@ -96,7 +96,7 @@ index 3d1be05af5ec..cdd205aa929e 100644
if (unlikely(to))
hrtimer_start_expires(&to->timer, HRTIMER_MODE_ABS);
-@@ -2679,6 +2692,9 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
+@@ -2679,6 +2692,9 @@ retry_private:
* first acquire the hb->lock before removing the lock from the
* rt_mutex waitqueue, such that we can keep the hb and rt_mutex
* wait lists consistent.
@@ -106,7 +106,7 @@ index 3d1be05af5ec..cdd205aa929e 100644
*/
if (ret && !rt_mutex_cleanup_proxy_lock(&q.pi_state->pi_mutex, &rt_waiter))
ret = 0;
-@@ -2790,10 +2806,6 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
+@@ -2790,10 +2806,6 @@ retry:
get_pi_state(pi_state);
/*
@@ -209,3 +209,6 @@ index 4fe3f32da3c5..25ccf716b936 100644
extern int rt_mutex_start_proxy_lock(struct rt_mutex *lock,
struct rt_mutex_waiter *waiter,
struct task_struct *task);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0018-rtmutex-Deboost-before-waking-up-the-top-waiter.patch b/debian/patches/features/all/rt/0018-rtmutex-Deboost-before-waking-up-the-top-waiter.patch
index 73cd96f..d0ba1f8 100644
--- a/debian/patches/features/all/rt/0018-rtmutex-Deboost-before-waking-up-the-top-waiter.patch
+++ b/debian/patches/features/all/rt/0018-rtmutex-Deboost-before-waking-up-the-top-waiter.patch
@@ -1,7 +1,7 @@
From: Xunlei Pang <xlpang at redhat.com>
Date: Thu, 23 Mar 2017 15:56:07 +0100
Subject: [PATCH 018/351] rtmutex: Deboost before waking up the top waiter
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=28e4510d075d7679424d76de6ec3283ee12f25fc
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2a79ff765732e66f751ef9c823db9a8ae78e2cc4
Upstream commit 2a1c6029940675abb2217b590512dbf691867ec4
@@ -184,3 +184,6 @@ index 25ccf716b936..6f073579b00b 100644
#ifdef CONFIG_DEBUG_RT_MUTEXES
# include "rtmutex-debug.h"
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0019-sched-rtmutex-deadline-Fix-a-PI-crash-for-deadline-t.patch b/debian/patches/features/all/rt/0019-sched-rtmutex-deadline-Fix-a-PI-crash-for-deadline-t.patch
index 4c1d868..4190268 100644
--- a/debian/patches/features/all/rt/0019-sched-rtmutex-deadline-Fix-a-PI-crash-for-deadline-t.patch
+++ b/debian/patches/features/all/rt/0019-sched-rtmutex-deadline-Fix-a-PI-crash-for-deadline-t.patch
@@ -2,7 +2,7 @@ From: Xunlei Pang <xlpang at redhat.com>
Date: Thu, 23 Mar 2017 15:56:08 +0100
Subject: [PATCH 019/351] sched/rtmutex/deadline: Fix a PI crash for deadline
tasks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=369438603d6dbc48af5b7ca3f4c2dfbee504a1d3
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bee79fb04ce5fa9a9fd9fcadde0957d48a259037
Upstream commit e96a7705e7d3fef96aec9b590c63b2f6f7d2ba22
@@ -98,10 +98,10 @@ index a30b172df6e1..60d0c4740b9f 100644
extern void rt_mutex_adjust_pi(struct task_struct *p);
static inline bool tsk_is_pi_blocked(struct task_struct *tsk)
diff --git a/kernel/fork.c b/kernel/fork.c
-index 9321b1ad3335..a5c663116a70 100644
+index 70e10cb49be0..40f4dbff7762 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
-@@ -1426,6 +1426,7 @@ static void rt_mutex_init_task(struct task_struct *p)
+@@ -1432,6 +1432,7 @@ static void rt_mutex_init_task(struct task_struct *p)
#ifdef CONFIG_RT_MUTEXES
p->pi_waiters = RB_ROOT;
p->pi_waiters_leftmost = NULL;
@@ -180,3 +180,6 @@ index e5066955cc3a..7c4614c54a26 100644
trace_sched_pi_setprio(p, prio);
oldprio = p->prio;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0020-sched-deadline-rtmutex-Dont-miss-the-dl_runtime-dl_p.patch b/debian/patches/features/all/rt/0020-sched-deadline-rtmutex-Dont-miss-the-dl_runtime-dl_p.patch
index e8bc594..891bbdd 100644
--- a/debian/patches/features/all/rt/0020-sched-deadline-rtmutex-Dont-miss-the-dl_runtime-dl_p.patch
+++ b/debian/patches/features/all/rt/0020-sched-deadline-rtmutex-Dont-miss-the-dl_runtime-dl_p.patch
@@ -2,7 +2,7 @@ From: Xunlei Pang <xlpang at redhat.com>
Date: Thu, 23 Mar 2017 15:56:09 +0100
Subject: [PATCH 020/351] sched/deadline/rtmutex: Dont miss the
dl_runtime/dl_period update
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e9685e687154039e67013ac2b502e80c7b1fa0de
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c7845ab4290a67128e3647dab25e3e7712134663
Upstream commit 85e2d4f992868ad78dc8bb2c077b652fcfb3661a
@@ -54,3 +54,6 @@ index 3c4e5bff1d9a..f0dc1f6cf22b 100644
if (!detect_deadlock)
goto out_unlock_pi;
else
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0021-rtmutex-Clean-up.patch b/debian/patches/features/all/rt/0021-rtmutex-Clean-up.patch
index 2f10eec..236e6fe 100644
--- a/debian/patches/features/all/rt/0021-rtmutex-Clean-up.patch
+++ b/debian/patches/features/all/rt/0021-rtmutex-Clean-up.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Thu, 23 Mar 2017 15:56:10 +0100
Subject: [PATCH 021/351] rtmutex: Clean up
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2df320e234dfe5c5dd465e568a02d1350eb982b2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=406db12e2231ecb3b7be665531809453759406ce
Upstream commit aa2bfe55366552cb7e93e8709d66e698d79ccc47
@@ -151,3 +151,6 @@ index 6f073579b00b..d1c07126e890 100644
#ifdef CONFIG_DEBUG_RT_MUTEXES
# include "rtmutex-debug.h"
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0022-sched-rtmutex-Refactor-rt_mutex_setprio.patch b/debian/patches/features/all/rt/0022-sched-rtmutex-Refactor-rt_mutex_setprio.patch
index f113504..24a17be 100644
--- a/debian/patches/features/all/rt/0022-sched-rtmutex-Refactor-rt_mutex_setprio.patch
+++ b/debian/patches/features/all/rt/0022-sched-rtmutex-Refactor-rt_mutex_setprio.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Thu, 23 Mar 2017 15:56:11 +0100
Subject: [PATCH 022/351] sched/rtmutex: Refactor rt_mutex_setprio()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3ff82e8189c758a01961537730b076c9c1a64aa4
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=04b2bcf16e442a8c2137eb8b79a19fb45f1d9a96
Upstream commit acd58620e415aee4a43a808d7d2fd87259ee0001
@@ -363,7 +363,7 @@ index 7c4614c54a26..3d2bcd9d4c88 100644
if (!dl_prio(p->normal_prio) ||
(pi_task && dl_entity_preempt(&pi_task->dl, &p->dl))) {
p->dl.dl_boosted = 1;
-@@ -3732,6 +3768,11 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
+@@ -3732,6 +3768,11 @@ out_unlock:
balance_callback(rq);
preempt_enable();
}
@@ -388,7 +388,7 @@ index 7c4614c54a26..3d2bcd9d4c88 100644
if (dl_prio(p->prio))
p->sched_class = &dl_sched_class;
-@@ -4266,7 +4306,7 @@ static int __sched_setscheduler(struct task_struct *p,
+@@ -4266,7 +4306,7 @@ change:
* the runqueue. This will be done when the task deboost
* itself.
*/
@@ -397,3 +397,6 @@ index 7c4614c54a26..3d2bcd9d4c88 100644
if (new_effective_prio == oldprio)
queue_flags &= ~DEQUEUE_MOVE;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0023-sched-tracing-Update-trace_sched_pi_setprio.patch b/debian/patches/features/all/rt/0023-sched-tracing-Update-trace_sched_pi_setprio.patch
index f00f1fb..89d5330 100644
--- a/debian/patches/features/all/rt/0023-sched-tracing-Update-trace_sched_pi_setprio.patch
+++ b/debian/patches/features/all/rt/0023-sched-tracing-Update-trace_sched_pi_setprio.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Thu, 23 Mar 2017 15:56:12 +0100
Subject: [PATCH 023/351] sched,tracing: Update trace_sched_pi_setprio()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=67be1dae30921f1e62a92d6c32b44079ea1816ba
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0409996f9b3ca972a7131c8bb18dc931641cd7b7
Upstream commit b91473ff6e979c0028f02f90e40c844959c736d8
@@ -111,3 +111,6 @@ index 3d2bcd9d4c88..3564d9d41495 100644
oldprio = p->prio;
if (oldprio == prio)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0024-rtmutex-Fix-PI-chain-order-integrity.patch b/debian/patches/features/all/rt/0024-rtmutex-Fix-PI-chain-order-integrity.patch
index 98c0673..2195f82 100644
--- a/debian/patches/features/all/rt/0024-rtmutex-Fix-PI-chain-order-integrity.patch
+++ b/debian/patches/features/all/rt/0024-rtmutex-Fix-PI-chain-order-integrity.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Thu, 23 Mar 2017 15:56:13 +0100
Subject: [PATCH 024/351] rtmutex: Fix PI chain order integrity
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8770059f31de05c53bfe90167719f2dd8d59f32b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a68d6cfa54c881595fa6c51074f87edfef0b5a77
Upstream commit e0aad5b44ff5d28ac1d6ae70cdf84ca228e889dc
@@ -124,3 +124,6 @@ index d1c07126e890..722e3cf38acf 100644
};
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0025-rtmutex-Fix-more-prio-comparisons.patch b/debian/patches/features/all/rt/0025-rtmutex-Fix-more-prio-comparisons.patch
index 4ee0e22..446f67b 100644
--- a/debian/patches/features/all/rt/0025-rtmutex-Fix-more-prio-comparisons.patch
+++ b/debian/patches/features/all/rt/0025-rtmutex-Fix-more-prio-comparisons.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Thu, 23 Mar 2017 15:56:14 +0100
Subject: [PATCH 025/351] rtmutex: Fix more prio comparisons
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=84c387d8aeb4b28ccb9cb722c100af29b9664924
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9359453641c70925c7d6c35d3a09f081e2f170c9
Upstream commit 19830e55247cddb3f46f1bf60b8e245593491bea
@@ -102,3 +102,6 @@ index e275b8148db9..a8202c772907 100644
raw_spin_unlock_irqrestore(&task->pi_lock, flags);
return;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0026-rtmutex-Plug-preempt-count-leak-in-rt_mutex_futex_un.patch b/debian/patches/features/all/rt/0026-rtmutex-Plug-preempt-count-leak-in-rt_mutex_futex_un.patch
index 4830f34..d157882 100644
--- a/debian/patches/features/all/rt/0026-rtmutex-Plug-preempt-count-leak-in-rt_mutex_futex_un.patch
+++ b/debian/patches/features/all/rt/0026-rtmutex-Plug-preempt-count-leak-in-rt_mutex_futex_un.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <efault at gmx.de>
Date: Wed, 5 Apr 2017 10:08:27 +0200
Subject: [PATCH 026/351] rtmutex: Plug preempt count leak in
rt_mutex_futex_unlock()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=beba9a5fa91b3ff3a9850f6e868ee7c5899eaeba
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8b286a6311190b64d0dc77bfd7bf3e09b7ce9607
Upstream commit def34eaae5ce04b324e48e1bfac873091d945213
@@ -43,3 +43,6 @@ index a8202c772907..ed2755befa35 100644
return true; /* call postunlock() */
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0027-futex-Avoid-freeing-an-active-timer.patch b/debian/patches/features/all/rt/0027-futex-Avoid-freeing-an-active-timer.patch
index 17264c9..9cdfc05 100644
--- a/debian/patches/features/all/rt/0027-futex-Avoid-freeing-an-active-timer.patch
+++ b/debian/patches/features/all/rt/0027-futex-Avoid-freeing-an-active-timer.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 10 Apr 2017 18:03:36 +0200
Subject: [PATCH 027/351] futex: Avoid freeing an active timer
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0c3e8a46724a7f0f23f4c52713ca509a4fc4c2b0
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=82bd1cda28c182eff0a12b3d5a6ad1dbcc60e908
Upstream commit 97181f9bd57405b879403763284537e27d46963d
@@ -41,7 +41,7 @@ diff --git a/kernel/futex.c b/kernel/futex.c
index 3c5173f520c6..51455f2fb072 100644
--- a/kernel/futex.c
+++ b/kernel/futex.c
-@@ -2735,8 +2735,10 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
+@@ -2735,8 +2735,10 @@ out_unlock_put_key:
out_put_key:
put_futex_key(&q.key);
out:
@@ -53,3 +53,6 @@ index 3c5173f520c6..51455f2fb072 100644
return ret != -EINTR ? ret : -ERESTARTNOINTR;
uaddr_faulted:
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0028-futex-Fix-small-and-harmless-looking-inconsistencies.patch b/debian/patches/features/all/rt/0028-futex-Fix-small-and-harmless-looking-inconsistencies.patch
index 42c48fc..7bbcaf6 100644
--- a/debian/patches/features/all/rt/0028-futex-Fix-small-and-harmless-looking-inconsistencies.patch
+++ b/debian/patches/features/all/rt/0028-futex-Fix-small-and-harmless-looking-inconsistencies.patch
@@ -2,7 +2,7 @@ From: Peter Zijlstra <peterz at infradead.org>
Date: Fri, 7 Apr 2017 09:04:07 +0200
Subject: [PATCH 028/351] futex: Fix small (and harmless looking)
inconsistencies
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=baac99b199c4118aad1e551106d453dcb14130d3
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=300c767926b3049b4bd79beb27295fa2b04f1def
Upstream commit 94ffac5d847cfd790bb37b7cef1cad803743985e
@@ -58,3 +58,6 @@ index 51455f2fb072..216a6427670d 100644
postunlock = __rt_mutex_futex_unlock(&pi_state->pi_mutex, &wake_q);
out_unlock:
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0029-futex-Clarify-mark_wake_futex-memory-barrier-usage.patch b/debian/patches/features/all/rt/0029-futex-Clarify-mark_wake_futex-memory-barrier-usage.patch
index 844ebb2..c672de9 100644
--- a/debian/patches/features/all/rt/0029-futex-Clarify-mark_wake_futex-memory-barrier-usage.patch
+++ b/debian/patches/features/all/rt/0029-futex-Clarify-mark_wake_futex-memory-barrier-usage.patch
@@ -1,7 +1,7 @@
From: "Darren Hart (VMware)" <dvhart at infradead.org>
Date: Fri, 14 Apr 2017 15:31:38 -0700
Subject: [PATCH 029/351] futex: Clarify mark_wake_futex memory barrier usage
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d6c37ef7b89b99e1f6e72c8537fc4f0f8cfbee4f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=979be2141f8ddd303c40ee8c3a6b2de2dd7ce46f
Upstream commit 38fcd06e9b7f6855db1f3ebac5e18b8fdb467ffd
@@ -38,3 +38,6 @@ index 216a6427670d..c1d2034800aa 100644
*/
smp_store_release(&q->lock_ptr, NULL);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0030-MAINTAINERS-Add-FUTEX-SUBSYSTEM.patch b/debian/patches/features/all/rt/0030-MAINTAINERS-Add-FUTEX-SUBSYSTEM.patch
index 5082cca..bb8ab8b 100644
--- a/debian/patches/features/all/rt/0030-MAINTAINERS-Add-FUTEX-SUBSYSTEM.patch
+++ b/debian/patches/features/all/rt/0030-MAINTAINERS-Add-FUTEX-SUBSYSTEM.patch
@@ -1,7 +1,7 @@
From: "Darren Hart (VMware)" <dvhart at infradead.org>
Date: Fri, 14 Apr 2017 15:46:08 -0700
Subject: [PATCH 030/351] MAINTAINERS: Add FUTEX SUBSYSTEM
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3aeda864925cc002b1febd1d1064a78c73fadeb1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f554ca15fbedcb09bd3da2e2971c29bcc69e618e
Upstream commit 59cd42c29618c45cd3c56da43402b14f611888dd
@@ -50,3 +50,6 @@ index 63cefa62324c..be0ea1e5c4cc 100644
FUTURE DOMAIN TMC-16x0 SCSI DRIVER (16-bit)
M: Rik Faith <faith at cs.unc.edu>
L: linux-scsi at vger.kernel.org
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0031-futex-rt_mutex-Fix-rt_mutex_cleanup_proxy_lock.patch b/debian/patches/features/all/rt/0031-futex-rt_mutex-Fix-rt_mutex_cleanup_proxy_lock.patch
index d326360..a6c1bf4 100644
--- a/debian/patches/features/all/rt/0031-futex-rt_mutex-Fix-rt_mutex_cleanup_proxy_lock.patch
+++ b/debian/patches/features/all/rt/0031-futex-rt_mutex-Fix-rt_mutex_cleanup_proxy_lock.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Mon, 22 May 2017 13:04:50 -0700
Subject: [PATCH 031/351] futex,rt_mutex: Fix rt_mutex_cleanup_proxy_lock()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f87410719a641ad0542e9a763367d699e65f0ea1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5e4dcd1f4d999f804d692d3e814ff4342fc135c0
Markus reported that the glibc/nptl/tst-robustpi8 test was failing after
commit:
@@ -127,3 +127,6 @@ index ed2755befa35..4b2126de44bb 100644
/*
* try_to_take_rt_mutex() sets the waiter bit unconditionally. We might
* have to fix that up.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0032-arm-at91-do-not-disable-enable-clocks-in-a-row.patch b/debian/patches/features/all/rt/0032-arm-at91-do-not-disable-enable-clocks-in-a-row.patch
index d577e4e..02d3086 100644
--- a/debian/patches/features/all/rt/0032-arm-at91-do-not-disable-enable-clocks-in-a-row.patch
+++ b/debian/patches/features/all/rt/0032-arm-at91-do-not-disable-enable-clocks-in-a-row.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 9 Mar 2016 10:51:06 +0100
Subject: [PATCH 032/351] arm: at91: do not disable/enable clocks in a row
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0a6405300a8c2842ce6ce11a5f6ccd70bbe63971
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e5546f9eaf78830699f4db63754d0b31496825bc
Currently the driver will disable the clock and enable it one line later
if it is switching from periodic mode into one shot.
@@ -92,3 +92,6 @@ index 4da2af9694a2..ed1ae4445e8d 100644
.set_state_periodic = tc_set_periodic,
.set_state_oneshot = tc_set_oneshot,
},
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0033-ARM-smp-Move-clear_tasks_mm_cpumask-call-to-__cpu_di.patch b/debian/patches/features/all/rt/0033-ARM-smp-Move-clear_tasks_mm_cpumask-call-to-__cpu_di.patch
index fa2943d..2c8bf76 100644
--- a/debian/patches/features/all/rt/0033-ARM-smp-Move-clear_tasks_mm_cpumask-call-to-__cpu_di.patch
+++ b/debian/patches/features/all/rt/0033-ARM-smp-Move-clear_tasks_mm_cpumask-call-to-__cpu_di.patch
@@ -2,7 +2,7 @@ From: Grygorii Strashko <grygorii.strashko at ti.com>
Date: Fri, 11 Sep 2015 21:21:23 +0300
Subject: [PATCH 033/351] ARM: smp: Move clear_tasks_mm_cpumask() call to
__cpu_die()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6ed07eee05411303964f1520227324d192a81f6f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=68a5ba063f97e571ed6cf49b92b12bcf23cef1a7
When running with the RT-kernel (4.1.5-rt5) on TI OMAP dra7-evm and trying
to do Suspend to RAM, the following backtrace occurs:
@@ -88,3 +88,6 @@ index 7dd14e8395e6..4cd7e3d98035 100644
pr_notice("CPU%u: shutdown\n", cpu);
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0034-rtmutex-Handle-non-enqueued-waiters-gracefully.patch b/debian/patches/features/all/rt/0034-rtmutex-Handle-non-enqueued-waiters-gracefully.patch
index 7f52de0..8af9244 100644
--- a/debian/patches/features/all/rt/0034-rtmutex-Handle-non-enqueued-waiters-gracefully.patch
+++ b/debian/patches/features/all/rt/0034-rtmutex-Handle-non-enqueued-waiters-gracefully.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 6 Nov 2015 18:51:03 +0100
Subject: [PATCH 034/351] rtmutex: Handle non enqueued waiters gracefully
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3d00b0372ac47d78e8b4d8269a0e5de6bf66b857
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4d770fa6f6d7d937b3e1ddaa3ea96665e99778cc
Yimin debugged that in case of a PI wakeup in progress when
rt_mutex_start_proxy_lock() calls task_blocks_on_rt_mutex() the latter
@@ -32,3 +32,6 @@ index 4b2126de44bb..5138805ee66c 100644
remove_waiter(lock, waiter);
debug_rt_mutex_print_deadlock(waiter);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0035-fs-dcache-include-wait.h.patch b/debian/patches/features/all/rt/0035-fs-dcache-include-wait.h.patch
index 114b90f..5379ffc 100644
--- a/debian/patches/features/all/rt/0035-fs-dcache-include-wait.h.patch
+++ b/debian/patches/features/all/rt/0035-fs-dcache-include-wait.h.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 14 Sep 2016 11:55:23 +0200
Subject: [PATCH 035/351] fs/dcache: include wait.h
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=37fd69dff5c92937d063acda3f22b1a9a1124091
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4734bc1c07b42aa34903200bbfe3206429931b44
Since commit d9171b934526 ("parallel lookups machinery, part 4 (and
last)") dcache.h is using but does not include wait.h. It works as long
@@ -24,3 +24,6 @@ index ff295e166b2c..8b10a30f5087 100644
struct path;
struct vfsmount;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0036-rbtree-include-rcu.h-because-we-use-it.patch b/debian/patches/features/all/rt/0036-rbtree-include-rcu.h-because-we-use-it.patch
index f259d0a..7afffc7 100644
--- a/debian/patches/features/all/rt/0036-rbtree-include-rcu.h-because-we-use-it.patch
+++ b/debian/patches/features/all/rt/0036-rbtree-include-rcu.h-because-we-use-it.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 14 Sep 2016 11:52:17 +0200
Subject: [PATCH 036/351] rbtree: include rcu.h because we use it
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=826b7dee269c5a66531442a5c92a0bc791c7811f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8257303e1421ae2e813738b792537d683cb0760d
Since commit c1adf20052d8 ("Introduce rb_replace_node_rcu()")
rbtree_augmented.h uses RCU related data structures but does not include
@@ -25,3 +25,6 @@ index d076183e49be..36bfb4dd57ae 100644
/*
* Please note - only struct rb_augment_callbacks and the prototypes for
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0037-fs-dcache-init-in_lookup_hashtable.patch b/debian/patches/features/all/rt/0037-fs-dcache-init-in_lookup_hashtable.patch
index c960371..ca6611b 100644
--- a/debian/patches/features/all/rt/0037-fs-dcache-init-in_lookup_hashtable.patch
+++ b/debian/patches/features/all/rt/0037-fs-dcache-init-in_lookup_hashtable.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 14 Sep 2016 17:57:03 +0200
Subject: [PATCH 037/351] fs/dcache: init in_lookup_hashtable
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1e4ae2502cf7681822e1965edb6f9b17dea7ffb3
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=62c00acc26e01bb4c28f5d5c2fe3031e908a0260
in_lookup_hashtable was introduced in commit 94bdd655caba ("parallel
lookups machinery, part 3") and never initialized but since it is in
@@ -28,3 +28,6 @@ index 67957f5b325c..10f848262852 100644
dcache_init_early();
inode_init_early();
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0038-iommu-iova-don-t-disable-preempt-around-this_cpu_ptr.patch b/debian/patches/features/all/rt/0038-iommu-iova-don-t-disable-preempt-around-this_cpu_ptr.patch
index 2c072d4..0f9a3b1 100644
--- a/debian/patches/features/all/rt/0038-iommu-iova-don-t-disable-preempt-around-this_cpu_ptr.patch
+++ b/debian/patches/features/all/rt/0038-iommu-iova-don-t-disable-preempt-around-this_cpu_ptr.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 15 Sep 2016 16:58:19 +0200
Subject: [PATCH 038/351] iommu/iova: don't disable preempt around
this_cpu_ptr()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2505300446589b3ec3a440ca82ee26ecf980e2eb
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c158b77fa43676c17836d6abaab1130975997e82
Commit 583248e6620a ("iommu/iova: Disable preemption around use of
this_cpu_ptr()") disables preemption while accessing a per-CPU variable.
@@ -38,7 +38,7 @@ index e23001bfcfee..359d5d169ec0 100644
static bool iova_rcache_insert(struct iova_domain *iovad,
unsigned long pfn,
-@@ -420,10 +421,8 @@ alloc_iova_fast(struct iova_domain *iovad, unsigned long size,
+@@ -420,10 +421,8 @@ retry:
/* Try replenishing IOVAs by flushing rcache. */
flushed_rcache = true;
@@ -83,3 +83,6 @@ index e23001bfcfee..359d5d169ec0 100644
return iova_pfn;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0039-iommu-vt-d-don-t-disable-preemption-while-accessing-.patch b/debian/patches/features/all/rt/0039-iommu-vt-d-don-t-disable-preemption-while-accessing-.patch
index d757300..7cd0471 100644
--- a/debian/patches/features/all/rt/0039-iommu-vt-d-don-t-disable-preemption-while-accessing-.patch
+++ b/debian/patches/features/all/rt/0039-iommu-vt-d-don-t-disable-preemption-while-accessing-.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 15 Sep 2016 17:16:44 +0200
Subject: [PATCH 039/351] iommu/vt-d: don't disable preemption while accessing
deferred_flush()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=90a456774613a5941fd409c3329508a642321c4d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4e7b2629c3b386ba48c98bd663fd26bb9ef39739
get_cpu() disables preemption and returns the current CPU number. The
CPU number is later only used once while retrieving the address of the
@@ -26,7 +26,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
-index 002f8a421efa..980f41f1a194 100644
+index 88bbc8ccc5e3..8a1a8432a6bd 100644
--- a/drivers/iommu/intel-iommu.c
+++ b/drivers/iommu/intel-iommu.c
@@ -479,7 +479,7 @@ struct deferred_flush_data {
@@ -38,7 +38,7 @@ index 002f8a421efa..980f41f1a194 100644
/* bitmap for indexing intel_iommus */
static int g_num_of_iommus;
-@@ -3719,10 +3719,8 @@ static void add_unmap(struct dmar_domain *dom, unsigned long iova_pfn,
+@@ -3721,10 +3721,8 @@ static void add_unmap(struct dmar_domain *dom, unsigned long iova_pfn,
struct intel_iommu *iommu;
struct deferred_flush_entry *entry;
struct deferred_flush_data *flush_data;
@@ -50,7 +50,7 @@ index 002f8a421efa..980f41f1a194 100644
/* Flush all CPUs' entries to avoid deferring too much. If
* this becomes a bottleneck, can just flush us, and rely on
-@@ -3755,8 +3753,6 @@ static void add_unmap(struct dmar_domain *dom, unsigned long iova_pfn,
+@@ -3757,8 +3755,6 @@ static void add_unmap(struct dmar_domain *dom, unsigned long iova_pfn,
}
flush_data->size++;
spin_unlock_irqrestore(&flush_data->lock, flags);
@@ -59,3 +59,6 @@ index 002f8a421efa..980f41f1a194 100644
}
static void intel_unmap(struct device *dev, dma_addr_t dev_addr, size_t size)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0040-x86-apic-get-rid-of-warning-acpi_ioapic_lock-defined.patch b/debian/patches/features/all/rt/0040-x86-apic-get-rid-of-warning-acpi_ioapic_lock-defined.patch
index c671970..1ed3729 100644
--- a/debian/patches/features/all/rt/0040-x86-apic-get-rid-of-warning-acpi_ioapic_lock-defined.patch
+++ b/debian/patches/features/all/rt/0040-x86-apic-get-rid-of-warning-acpi_ioapic_lock-defined.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 21 Oct 2016 10:29:11 +0200
Subject: [PATCH 040/351] x86/apic: get rid of "warning: 'acpi_ioapic_lock'
defined but not used"
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3886e1cbe1a6cd2dfe31681a9bc925586854f284
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=53e2084a0dcca2d30f9de291d6804d9f1b9788d1
kbuild test robot reported this against the -RT tree:
@@ -31,7 +31,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 2 insertions(+)
diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
-index b89bef95f63b..c3c1ad2fce5c 100644
+index 11cc600f4df0..8cbfc51ce339 100644
--- a/arch/x86/kernel/acpi/boot.c
+++ b/arch/x86/kernel/acpi/boot.c
@@ -87,7 +87,9 @@ static u64 acpi_lapic_addr __initdata = APIC_DEFAULT_PHYS_BASE;
@@ -44,3 +44,6 @@ index b89bef95f63b..c3c1ad2fce5c 100644
/* --------------------------------------------------------------------------
Boot-time Configuration
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0041-rxrpc-remove-unused-static-variables.patch b/debian/patches/features/all/rt/0041-rxrpc-remove-unused-static-variables.patch
index bac12fe..fc3230d 100644
--- a/debian/patches/features/all/rt/0041-rxrpc-remove-unused-static-variables.patch
+++ b/debian/patches/features/all/rt/0041-rxrpc-remove-unused-static-variables.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 21 Oct 2016 10:54:50 +0200
Subject: [PATCH 041/351] rxrpc: remove unused static variables
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2ffdfebe719f38dc1982db4cdb550406bf05f512
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6a7bc4b838283bbaefa5cc616f195762232c5e69
The rxrpc_security_methods and rxrpc_security_sem user has been removed
in 648af7fca159 ("rxrpc: Absorb the rxkad security module"). This was
@@ -27,3 +27,6 @@ index 7d921e56e715..13df56a738e5 100644
static const struct rxrpc_security *rxrpc_security_types[] = {
[RXRPC_SECURITY_NONE] = &rxrpc_no_security,
#ifdef CONFIG_RXKAD
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0042-rcu-update-make-RCU_EXPEDITE_BOOT-default.patch b/debian/patches/features/all/rt/0042-rcu-update-make-RCU_EXPEDITE_BOOT-default.patch
index 70f0721..5652208 100644
--- a/debian/patches/features/all/rt/0042-rcu-update-make-RCU_EXPEDITE_BOOT-default.patch
+++ b/debian/patches/features/all/rt/0042-rcu-update-make-RCU_EXPEDITE_BOOT-default.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 2 Nov 2016 16:45:58 +0100
Subject: [PATCH 042/351] rcu: update: make RCU_EXPEDITE_BOOT default
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f03d9b6a71a20c71edac387b0b973a0123c244e2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b73d47ac45f5e0525a489dd4733cccae0a5966ea
RCU_EXPEDITE_BOOT should speed up the boot process by enforcing
synchronize_rcu_expedited() instead of synchronize_rcu() during the boot
@@ -63,3 +63,6 @@ index 4f6db7e6a117..019b4708c9fa 100644
if (rcu_normal_after_boot)
WRITE_ONCE(rcu_normal, 1);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0043-locking-percpu-rwsem-use-swait-for-the-wating-writer.patch b/debian/patches/features/all/rt/0043-locking-percpu-rwsem-use-swait-for-the-wating-writer.patch
index 0b36cd9..67ad81b 100644
--- a/debian/patches/features/all/rt/0043-locking-percpu-rwsem-use-swait-for-the-wating-writer.patch
+++ b/debian/patches/features/all/rt/0043-locking-percpu-rwsem-use-swait-for-the-wating-writer.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 21 Nov 2016 19:26:15 +0100
Subject: [PATCH 043/351] locking/percpu-rwsem: use swait for the wating writer
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fc9e4b77ab0e1244be8dedc215634177c25d9e20
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6f4aae66aff75092d01fe28114c79db36ab1fb79
Use struct swait_queue_head instead of wait_queue_head_t for the waiting
writer. The swait implementation is smaller and lightweight compared to
@@ -75,3 +75,6 @@ index ce182599cf2e..2ad3a1e8344c 100644
}
EXPORT_SYMBOL_GPL(percpu_down_write);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0044-pinctrl-qcom-Use-raw-spinlock-variants.patch b/debian/patches/features/all/rt/0044-pinctrl-qcom-Use-raw-spinlock-variants.patch
index aa56343..4be17d0 100644
--- a/debian/patches/features/all/rt/0044-pinctrl-qcom-Use-raw-spinlock-variants.patch
+++ b/debian/patches/features/all/rt/0044-pinctrl-qcom-Use-raw-spinlock-variants.patch
@@ -1,7 +1,7 @@
From: Julia Cartwright <julia at ni.com>
Date: Fri, 20 Jan 2017 10:13:47 -0600
Subject: [PATCH 044/351] pinctrl: qcom: Use raw spinlock variants
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ed099dca885712f15644b23011876d9d852e3ee0
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1799298aca96cf668ded62171b393e6a29a9bae3
The MSM pinctrl driver currently implements an irq_chip for handling
GPIO interrupts; due to how irq_chip handling is done, it's necessary
@@ -253,3 +253,6 @@ index bedce3453dd3..faf038978650 100644
res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
pctrl->regs = devm_ioremap_resource(&pdev->dev, res);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0045-x86-mm-cpa-avoid-wbinvd-for-PREEMPT.patch b/debian/patches/features/all/rt/0045-x86-mm-cpa-avoid-wbinvd-for-PREEMPT.patch
index 25e1aa1..4ec814b 100644
--- a/debian/patches/features/all/rt/0045-x86-mm-cpa-avoid-wbinvd-for-PREEMPT.patch
+++ b/debian/patches/features/all/rt/0045-x86-mm-cpa-avoid-wbinvd-for-PREEMPT.patch
@@ -1,7 +1,7 @@
From: John Ogness <john.ogness at linutronix.de>
Date: Mon, 30 Jan 2017 09:41:21 +0100
Subject: [PATCH 045/351] x86/mm/cpa: avoid wbinvd() for PREEMPT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=96f3c0ac4e63ab47e624f91efbd1e527139d9bf5
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0289f698008f6297ef3777f285b710fef107e957
Although wbinvd() is faster than flushing many individual pages, it
blocks the memory bus for "long" periods of time (>100us), thus
@@ -20,10 +20,10 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 8 insertions(+)
diff --git a/arch/x86/mm/pageattr.c b/arch/x86/mm/pageattr.c
-index e3353c97d086..01664968555c 100644
+index 73dcb0e18c1b..c1085c7ee212 100644
--- a/arch/x86/mm/pageattr.c
+++ b/arch/x86/mm/pageattr.c
-@@ -214,7 +214,15 @@ static void cpa_flush_array(unsigned long *start, int numpages, int cache,
+@@ -215,7 +215,15 @@ static void cpa_flush_array(unsigned long *start, int numpages, int cache,
int in_flags, struct page **pages)
{
unsigned int i, level;
@@ -39,3 +39,6 @@ index e3353c97d086..01664968555c 100644
BUG_ON(irqs_disabled());
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0046-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch b/debian/patches/features/all/rt/0046-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch
index c737e4e..cae9ec9 100644
--- a/debian/patches/features/all/rt/0046-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch
+++ b/debian/patches/features/all/rt/0046-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 28 Oct 2016 23:05:11 +0200
Subject: [PATCH 046/351] NFSv4: replace seqcount_t with a seqlock_t
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5e3b43218398de95a9bc822cd041679daceedcce
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=870b86f52ee5c71d5cdf7e0dd141957c6d6dd4db
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
@@ -29,7 +29,7 @@ diff --git a/fs/nfs/delegation.c b/fs/nfs/delegation.c
index dff600ae0d74..d726d2e09353 100644
--- a/fs/nfs/delegation.c
+++ b/fs/nfs/delegation.c
-@@ -150,11 +150,11 @@ static int nfs_delegation_claim_opens(struct inode *inode,
+@@ -150,11 +150,11 @@ again:
sp = state->owner;
/* Block nfs4_proc_unlck */
mutex_lock(&sp->so_delegreturn_mutex);
@@ -105,7 +105,7 @@ index 71deeae6eefd..4be6999299dc 100644
restart:
list_for_each_entry(state, &sp->so_states, open_states) {
if (!test_and_clear_bit(ops->state_flag_bit, &state->flags))
-@@ -1568,14 +1572,20 @@ static int nfs4_reclaim_open_state(struct nfs4_state_owner *sp, const struct nfs
+@@ -1568,14 +1572,20 @@ restart:
spin_lock(&sp->so_lock);
goto restart;
}
@@ -130,3 +130,6 @@ index 71deeae6eefd..4be6999299dc 100644
return status;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0047-sparc64-use-generic-rwsem-spinlocks-rt.patch b/debian/patches/features/all/rt/0047-sparc64-use-generic-rwsem-spinlocks-rt.patch
index 0532c52..d6acd33 100644
--- a/debian/patches/features/all/rt/0047-sparc64-use-generic-rwsem-spinlocks-rt.patch
+++ b/debian/patches/features/all/rt/0047-sparc64-use-generic-rwsem-spinlocks-rt.patch
@@ -1,7 +1,7 @@
From: Allen Pais <allen.pais at oracle.com>
Date: Fri, 13 Dec 2013 09:44:41 +0530
Subject: [PATCH 047/351] sparc64: use generic rwsem spinlocks rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7fc5062dfa375522032ac4c0fa667b1957e02fda
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=113f9cc55951556f2311604781e330a5afa3e56d
Signed-off-by: Allen Pais <allen.pais at oracle.com>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
@@ -28,3 +28,6 @@ index 8b4152f3a764..c5cca159692a 100644
config GENERIC_HWEIGHT
bool
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0048-kernel-SRCU-provide-a-static-initializer.patch b/debian/patches/features/all/rt/0048-kernel-SRCU-provide-a-static-initializer.patch
index db88c5b..ebae0a4 100644
--- a/debian/patches/features/all/rt/0048-kernel-SRCU-provide-a-static-initializer.patch
+++ b/debian/patches/features/all/rt/0048-kernel-SRCU-provide-a-static-initializer.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Tue, 19 Mar 2013 14:44:30 +0100
Subject: [PATCH 048/351] kernel/SRCU: provide a static initializer
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1459d6a2d49fb3742b9bcc17261b899eccfbc3d1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a88b54f30ed26340e2e7fea679d71dcbb82cdbe1
There are macros for static initializer for the three out of four
possible notifier types, that are:
@@ -127,3 +127,6 @@ index dc8eb63c6568..e793d3a257da 100644
#define DEFINE_SRCU(name) __DEFINE_SRCU(name, /* not static */)
#define DEFINE_STATIC_SRCU(name) __DEFINE_SRCU(name, static)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0049-block-Shorten-interrupt-disabled-regions.patch b/debian/patches/features/all/rt/0049-block-Shorten-interrupt-disabled-regions.patch
index 5d990e0..783a396 100644
--- a/debian/patches/features/all/rt/0049-block-Shorten-interrupt-disabled-regions.patch
+++ b/debian/patches/features/all/rt/0049-block-Shorten-interrupt-disabled-regions.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 22 Jun 2011 19:47:02 +0200
Subject: [PATCH 049/351] block: Shorten interrupt disabled regions
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1de9473b395f25e52edf59678c19663be43cab6d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=29b4565fb84ef35d044645d4d9ec1fd0cdaab4a1
Moving the blk_sched_flush_plug() call out of the interrupt/preempt
disabled region in the scheduler allows us to replace
@@ -47,7 +47,7 @@ Link: http://lkml.kernel.org/r/20110622174919.025446432@linutronix.de
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/block/blk-core.c b/block/blk-core.c
-index b1c76aa73492..6ca17282da87 100644
+index 23daf40be371..d24e2e651775 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -3202,7 +3202,7 @@ static void queue_unplugged(struct request_queue *q, unsigned int depth,
@@ -97,3 +97,6 @@ index b1c76aa73492..6ca17282da87 100644
}
void blk_finish_plug(struct blk_plug *plug)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0050-timekeeping-Split-jiffies-seqlock.patch b/debian/patches/features/all/rt/0050-timekeeping-Split-jiffies-seqlock.patch
index 560bd29..93c2058 100644
--- a/debian/patches/features/all/rt/0050-timekeeping-Split-jiffies-seqlock.patch
+++ b/debian/patches/features/all/rt/0050-timekeeping-Split-jiffies-seqlock.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 14 Feb 2013 22:36:59 +0100
Subject: [PATCH 050/351] timekeeping: Split jiffies seqlock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5d9f75e05968432957536e96baa0f772e72275e5
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2be4fad0c4b85fb583c111d4127e6269afc95906
Replace jiffies_lock seqlock with a simple seqcounter and a rawlock so
it can be taken in atomic context on RT.
@@ -76,7 +76,7 @@ index 4fcd99e12aa0..5a47f2e98faf 100644
clockevents_switch_state(dev, CLOCK_EVT_STATE_ONESHOT);
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
-index 3bcb61b52f6c..10cb224cb9d4 100644
+index dae1a45be504..184ad05416ca 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -62,7 +62,8 @@ static void tick_do_update_jiffies64(ktime_t now)
@@ -121,7 +121,7 @@ index 3bcb61b52f6c..10cb224cb9d4 100644
return period;
}
-@@ -673,10 +678,10 @@ static ktime_t tick_nohz_stop_sched_tick(struct tick_sched *ts,
+@@ -678,10 +683,10 @@ static ktime_t tick_nohz_stop_sched_tick(struct tick_sched *ts,
/* Read jiffies and the time when jiffies were updated last */
do {
@@ -165,3 +165,6 @@ index 704f595ce83f..763a3e5121ff 100644
#define CS_NAME_LEN 32
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0051-tracing-Account-for-preempt-off-in-preempt_schedule.patch b/debian/patches/features/all/rt/0051-tracing-Account-for-preempt-off-in-preempt_schedule.patch
index bb4c3b5..7740ce7 100644
--- a/debian/patches/features/all/rt/0051-tracing-Account-for-preempt-off-in-preempt_schedule.patch
+++ b/debian/patches/features/all/rt/0051-tracing-Account-for-preempt-off-in-preempt_schedule.patch
@@ -2,7 +2,7 @@ From: Steven Rostedt <rostedt at goodmis.org>
Date: Thu, 29 Sep 2011 12:24:30 -0500
Subject: [PATCH 051/351] tracing: Account for preempt off in
preempt_schedule()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fd5e2d81ba167b783b55116e3fecb6761ed5189a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3f4a2d6fd00249efcd12ababd6e50be22bd163a7
The preempt_schedule() uses the preempt_disable_notrace() version
because it can cause infinite recursion by the function tracer as
@@ -48,3 +48,6 @@ index 3564d9d41495..1127df1b3463 100644
exception_exit(prev_ctx);
preempt_latency_stop(1);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0052-signal-Revert-ptrace-preempt-magic.patch b/debian/patches/features/all/rt/0052-signal-Revert-ptrace-preempt-magic.patch
index 6c9f263..a924325 100644
--- a/debian/patches/features/all/rt/0052-signal-Revert-ptrace-preempt-magic.patch
+++ b/debian/patches/features/all/rt/0052-signal-Revert-ptrace-preempt-magic.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 21 Sep 2011 19:57:12 +0200
Subject: [PATCH 052/351] signal: Revert ptrace preempt magic
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=82522e9d2bbf34b06951a79e6a7970629f1060d9
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a8db285f83052452342b3a0fe801a9a93f8d5572
Upstream commit '53da1d9456fe7f8 fix ptrace slowness' is nothing more
than a bandaid around the ptrace design trainwreck. It's not a
@@ -13,10 +13,10 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 8 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
-index e48668c3c972..4d58564ac7e3 100644
+index 7ebe236a5364..bdb44e325d94 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
-@@ -1854,15 +1854,7 @@ static void ptrace_stop(int exit_code, int why, int clear_code, siginfo_t *info)
+@@ -1856,15 +1856,7 @@ static void ptrace_stop(int exit_code, int why, int clear_code, siginfo_t *info)
if (gstop_done && ptrace_reparented(current))
do_notify_parent_cldstop(current, false, why);
@@ -32,3 +32,6 @@ index e48668c3c972..4d58564ac7e3 100644
freezable_schedule();
} else {
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0053-arm-Convert-arm-boot_lock-to-raw.patch b/debian/patches/features/all/rt/0053-arm-Convert-arm-boot_lock-to-raw.patch
index f90beb1..3ae1ae9 100644
--- a/debian/patches/features/all/rt/0053-arm-Convert-arm-boot_lock-to-raw.patch
+++ b/debian/patches/features/all/rt/0053-arm-Convert-arm-boot_lock-to-raw.patch
@@ -1,7 +1,7 @@
From: Frank Rowand <frank.rowand at am.sony.com>
Date: Mon, 19 Sep 2011 14:51:14 -0700
Subject: [PATCH 053/351] arm: Convert arm boot_lock to raw
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7d1db4e07b30edf58e9c2d286a70442520247d67
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d4fc2b62c5e6f1959fff86ae7f0e4ddd07571465
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.
@@ -422,3 +422,6 @@ index c2366510187a..6b60f582b738 100644
return pen_release != -1 ? -ENOSYS : 0;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0054-arm-kprobe-replace-patch_lock-to-raw-lock.patch b/debian/patches/features/all/rt/0054-arm-kprobe-replace-patch_lock-to-raw-lock.patch
index ebb86ad..6e78027 100644
--- a/debian/patches/features/all/rt/0054-arm-kprobe-replace-patch_lock-to-raw-lock.patch
+++ b/debian/patches/features/all/rt/0054-arm-kprobe-replace-patch_lock-to-raw-lock.patch
@@ -1,7 +1,7 @@
From: Yang Shi <yang.shi at linaro.org>
Date: Thu, 10 Nov 2016 16:17:55 -0800
Subject: [PATCH 054/351] arm: kprobe: replace patch_lock to raw lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=07ac21427cac8d41caa735da3cc4b75f6ec4d911
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e4c8939f64b41422001976f6a8c8d19311e6927f
When running kprobe on -rt kernel, the below bug is caught:
@@ -70,3 +70,6 @@ index 69bda1a5707e..1f665acaa6a9 100644
else
__release(&patch_lock);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0056-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch b/debian/patches/features/all/rt/0056-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch
index cbd74c2..d947783 100644
--- a/debian/patches/features/all/rt/0056-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch
+++ b/debian/patches/features/all/rt/0056-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 3 Jul 2009 08:44:56 -0500
Subject: [PATCH 056/351] signals: Allow rt tasks to cache one sigqueue struct
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=388213f48f691826b2cf39500500f2194112e117
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1b86bef6bf610f509bd0d9ef1917fefea3da50fc
To avoid allocation allow rt tasks to cache one sigqueue struct in
task struct.
@@ -53,10 +53,10 @@ index 3076f3089919..fb2ebcf3ca7c 100644
spin_unlock(&sighand->siglock);
diff --git a/kernel/fork.c b/kernel/fork.c
-index a5c663116a70..c508b761e494 100644
+index 40f4dbff7762..fca238739495 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
-@@ -1562,6 +1562,7 @@ static __latent_entropy struct task_struct *copy_process(
+@@ -1568,6 +1568,7 @@ static __latent_entropy struct task_struct *copy_process(
spin_lock_init(&p->alloc_lock);
init_sigpending(&p->pending);
@@ -65,7 +65,7 @@ index a5c663116a70..c508b761e494 100644
p->utime = p->stime = p->gtime = 0;
p->utimescaled = p->stimescaled = 0;
diff --git a/kernel/signal.c b/kernel/signal.c
-index 4d58564ac7e3..739615d8d5ae 100644
+index bdb44e325d94..64e8df5e3f39 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -14,6 +14,7 @@
@@ -76,7 +76,7 @@ index 4d58564ac7e3..739615d8d5ae 100644
#include <linux/fs.h>
#include <linux/tty.h>
#include <linux/binfmts.h>
-@@ -352,13 +353,30 @@ static bool task_participate_group_stop(struct task_struct *task)
+@@ -354,13 +355,30 @@ static bool task_participate_group_stop(struct task_struct *task)
return false;
}
@@ -108,7 +108,7 @@ index 4d58564ac7e3..739615d8d5ae 100644
{
struct sigqueue *q = NULL;
struct user_struct *user;
-@@ -375,7 +393,10 @@ __sigqueue_alloc(int sig, struct task_struct *t, gfp_t flags, int override_rlimi
+@@ -377,7 +395,10 @@ __sigqueue_alloc(int sig, struct task_struct *t, gfp_t flags, int override_rlimi
if (override_rlimit ||
atomic_read(&user->sigpending) <=
task_rlimit(t, RLIMIT_SIGPENDING)) {
@@ -120,7 +120,7 @@ index 4d58564ac7e3..739615d8d5ae 100644
} else {
print_dropped_signal(sig);
}
-@@ -392,6 +413,13 @@ __sigqueue_alloc(int sig, struct task_struct *t, gfp_t flags, int override_rlimi
+@@ -394,6 +415,13 @@ __sigqueue_alloc(int sig, struct task_struct *t, gfp_t flags, int override_rlimi
return q;
}
@@ -134,7 +134,7 @@ index 4d58564ac7e3..739615d8d5ae 100644
static void __sigqueue_free(struct sigqueue *q)
{
if (q->flags & SIGQUEUE_PREALLOC)
-@@ -401,6 +429,21 @@ static void __sigqueue_free(struct sigqueue *q)
+@@ -403,6 +431,21 @@ static void __sigqueue_free(struct sigqueue *q)
kmem_cache_free(sigqueue_cachep, q);
}
@@ -156,7 +156,7 @@ index 4d58564ac7e3..739615d8d5ae 100644
void flush_sigqueue(struct sigpending *queue)
{
struct sigqueue *q;
-@@ -413,6 +456,21 @@ void flush_sigqueue(struct sigpending *queue)
+@@ -415,6 +458,21 @@ void flush_sigqueue(struct sigpending *queue)
}
}
@@ -178,7 +178,7 @@ index 4d58564ac7e3..739615d8d5ae 100644
/*
* Flush all pending signals for this kthread.
*/
-@@ -532,7 +590,7 @@ static void collect_signal(int sig, struct sigpending *list, siginfo_t *info,
+@@ -534,7 +592,7 @@ still_pending:
(info->si_code == SI_TIMER) &&
(info->si_sys_private);
@@ -187,7 +187,7 @@ index 4d58564ac7e3..739615d8d5ae 100644
} else {
/*
* Ok, it wasn't in the queue. This must be
-@@ -568,6 +626,8 @@ int dequeue_signal(struct task_struct *tsk, sigset_t *mask, siginfo_t *info)
+@@ -570,6 +628,8 @@ int dequeue_signal(struct task_struct *tsk, sigset_t *mask, siginfo_t *info)
bool resched_timer = false;
int signr;
@@ -196,7 +196,7 @@ index 4d58564ac7e3..739615d8d5ae 100644
/* We only dequeue private signals from ourselves, we don't let
* signalfd steal them
*/
-@@ -1493,7 +1553,8 @@ EXPORT_SYMBOL(kill_pid);
+@@ -1495,7 +1555,8 @@ EXPORT_SYMBOL(kill_pid);
*/
struct sigqueue *sigqueue_alloc(void)
{
@@ -206,3 +206,6 @@ index 4d58564ac7e3..739615d8d5ae 100644
if (q)
q->flags |= SIGQUEUE_PREALLOC;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0057-drivers-random-Reduce-preempt-disabled-region.patch b/debian/patches/features/all/rt/0057-drivers-random-Reduce-preempt-disabled-region.patch
index aa0d1e3..fb5b193 100644
--- a/debian/patches/features/all/rt/0057-drivers-random-Reduce-preempt-disabled-region.patch
+++ b/debian/patches/features/all/rt/0057-drivers-random-Reduce-preempt-disabled-region.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:29:30 -0500
Subject: [PATCH 057/351] drivers: random: Reduce preempt disabled region
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9e1a191ad328b7bbe03477327ef51ea5dde63a47
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1779f1f49b6b1b541bc99da1eefd91dabcb07c12
No need to keep preemption disabled across the whole function.
@@ -32,3 +32,6 @@ index 08d1dd58c0d2..f17bc435eee1 100644
}
void add_input_randomness(unsigned int type, unsigned int code,
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0058-ARM-AT91-PIT-Remove-irq-handler-when-clock-event-is-.patch b/debian/patches/features/all/rt/0058-ARM-AT91-PIT-Remove-irq-handler-when-clock-event-is-.patch
index 6d6d3a2..30eeee1 100644
--- a/debian/patches/features/all/rt/0058-ARM-AT91-PIT-Remove-irq-handler-when-clock-event-is-.patch
+++ b/debian/patches/features/all/rt/0058-ARM-AT91-PIT-Remove-irq-handler-when-clock-event-is-.patch
@@ -5,7 +5,7 @@ Subject: [PATCH 058/351] ARM: AT91: PIT: Remove irq handler when clock event
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=991068b0e5a09a9091c7560b17d87996dc326580
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=91c7e0a4932ec96fe08f1e04976c38f3366504d4
Setup and remove the interrupt handler in clock event mode selection.
This avoids calling the (shared) interrupt handler when the device is
@@ -151,3 +151,6 @@ index e90ab5b63a90..9e124087c55f 100644
sclk = of_clk_get(node, 0);
if (IS_ERR(sclk)) {
pr_err("Unable to get slow clock\n");
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0059-clockevents-drivers-timer-atmel-pit-fix-double-free_.patch b/debian/patches/features/all/rt/0059-clockevents-drivers-timer-atmel-pit-fix-double-free_.patch
index b3d56c2..67d4980 100644
--- a/debian/patches/features/all/rt/0059-clockevents-drivers-timer-atmel-pit-fix-double-free_.patch
+++ b/debian/patches/features/all/rt/0059-clockevents-drivers-timer-atmel-pit-fix-double-free_.patch
@@ -2,7 +2,7 @@ From: Alexandre Belloni <alexandre.belloni at free-electrons.com>
Date: Thu, 17 Mar 2016 21:09:43 +0100
Subject: [PATCH 059/351] clockevents/drivers/timer-atmel-pit: fix double
free_irq
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1e00aa18cb34c894b9fe6044cb336eb2d53420d2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=008f8dc1a5acad4f64f14b27eeda64df61294670
clockevents_exchange_device() changes the state from detached to shutdown
and so at that point the IRQ has not yet been requested.
@@ -47,3 +47,6 @@ index 2c66bb3e595b..93288849b2bd 100644
/* update clocksource counter */
data->cnt += data->cycle * PIT_PICNT(pit_read(data->base, AT91_PIT_PIVR));
pit_write(data->base, AT91_PIT_MR,
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0060-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch b/debian/patches/features/all/rt/0060-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch
index c0d1dbd..8571244 100644
--- a/debian/patches/features/all/rt/0060-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch
+++ b/debian/patches/features/all/rt/0060-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch
@@ -5,7 +5,7 @@ Subject: [PATCH 060/351] clocksource: TCLIB: Allow higher clock rates for
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6e30432541321eb935687a583cc5d1d5c286cbe1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0a95e26e365d2dae6ab79c4d81a990b946f6bba5
As default the TCLIB uses the 32KiHz base clock rate for clock events.
Add a compile time selection to allow higher clock resulution.
@@ -164,3 +164,6 @@ index 64971baf11fa..9a6d60d57ec5 100644
config DUMMY_IRQ
tristate "Dummy IRQ handler"
default n
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0061-drivers-net-Use-disable_irq_nosync-in-8139too.patch b/debian/patches/features/all/rt/0061-drivers-net-Use-disable_irq_nosync-in-8139too.patch
index c94cb58..de6c1bd 100644
--- a/debian/patches/features/all/rt/0061-drivers-net-Use-disable_irq_nosync-in-8139too.patch
+++ b/debian/patches/features/all/rt/0061-drivers-net-Use-disable_irq_nosync-in-8139too.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:29:24 -0500
Subject: [PATCH 061/351] drivers/net: Use disable_irq_nosync() in 8139too
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=418c4480e46866f88575da9a8d41c5872c3a56a7
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bd690fdc251357c2a328d3a50758d68f17cfee1e
Use disable_irq_nosync() instead of disable_irq() as this might be
called in atomic context with netpoll.
@@ -25,3 +25,6 @@ index da4c2d8a4173..1420dfb56bac 100644
rtl8139_interrupt(irq, dev);
enable_irq(irq);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0062-suspend-Prevent-might-sleep-splats.patch b/debian/patches/features/all/rt/0062-suspend-Prevent-might-sleep-splats.patch
index 0b9db7a..b99ebc0 100644
--- a/debian/patches/features/all/rt/0062-suspend-Prevent-might-sleep-splats.patch
+++ b/debian/patches/features/all/rt/0062-suspend-Prevent-might-sleep-splats.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 15 Jul 2010 10:29:00 +0200
Subject: [PATCH 062/351] suspend: Prevent might sleep splats
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bf76b25a4327c9b26be80b3e8c4537863fd18419
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ddc7a48749f16afebfd953183991f443bb76b1ea
timekeeping suspend/resume calls read_persistant_clock() which takes
rtc_lock. That results in might sleep warnings because at that point
@@ -110,3 +110,6 @@ index 6ccb08f57fcb..40f8332ec170 100644
arch_suspend_enable_irqs();
BUG_ON(irqs_disabled());
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0063-net-flip-lock-dep-thingy.patch.patch b/debian/patches/features/all/rt/0063-net-flip-lock-dep-thingy.patch.patch
index c5053b9..1867941 100644
--- a/debian/patches/features/all/rt/0063-net-flip-lock-dep-thingy.patch.patch
+++ b/debian/patches/features/all/rt/0063-net-flip-lock-dep-thingy.patch.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 28 Jun 2011 10:59:58 +0200
Subject: [PATCH 063/351] net-flip-lock-dep-thingy.patch
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2cbe390fe34a5e1d9c2250e78bcf9e47cf448127
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f88d306efb7829a4907cce34a2f24dcdafbe408a
=======================================================
[ INFO: possible circular locking dependency detected ]
@@ -112,3 +112,6 @@ index e3b60460dc9c..8d15848c3a22 100644
}
EXPORT_SYMBOL(lock_sock_nested);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0064-net-sched-Use-msleep-instead-of-yield.patch b/debian/patches/features/all/rt/0064-net-sched-Use-msleep-instead-of-yield.patch
index 5c67dbc..545fb9f 100644
--- a/debian/patches/features/all/rt/0064-net-sched-Use-msleep-instead-of-yield.patch
+++ b/debian/patches/features/all/rt/0064-net-sched-Use-msleep-instead-of-yield.patch
@@ -1,7 +1,7 @@
From: Marc Kleine-Budde <mkl at pengutronix.de>
Date: Wed, 5 Mar 2014 00:49:47 +0100
Subject: [PATCH 064/351] net: sched: Use msleep() instead of yield()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=68115907f14e74848bd167b2cab60b1a56cb7bf8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b1de6360036856cbff29a9eb912bd30c807efe68
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
@@ -58,3 +58,6 @@ index 9016c8baf2aa..3a5fe6255c10 100644
}
void dev_deactivate(struct net_device *dev)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0065-x86-ioapic-Do-not-unmask-io_apic-when-interrupt-is-i.patch b/debian/patches/features/all/rt/0065-x86-ioapic-Do-not-unmask-io_apic-when-interrupt-is-i.patch
index 94a8c24..dd195a0 100644
--- a/debian/patches/features/all/rt/0065-x86-ioapic-Do-not-unmask-io_apic-when-interrupt-is-i.patch
+++ b/debian/patches/features/all/rt/0065-x86-ioapic-Do-not-unmask-io_apic-when-interrupt-is-i.patch
@@ -2,7 +2,7 @@ From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:29:27 -0500
Subject: [PATCH 065/351] x86/ioapic: Do not unmask io_apic when interrupt is
in progress
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c3ddf4bb3e1af0ec2528f0f46703c6eeee4766e6
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=996342e5c3772185f5546785243b5360d96068f4
With threaded interrupts we might see an interrupt in progress on
migration. Do not unmask it when this is the case.
@@ -27,3 +27,6 @@ index cf89928dbd46..18b5ec2a71df 100644
mask_ioapic_irq(data);
return true;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0066-latencyhist-disable-jump-labels.patch b/debian/patches/features/all/rt/0066-latencyhist-disable-jump-labels.patch
index 2a05669..e98fca2 100644
--- a/debian/patches/features/all/rt/0066-latencyhist-disable-jump-labels.patch
+++ b/debian/patches/features/all/rt/0066-latencyhist-disable-jump-labels.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 4 Feb 2016 14:08:06 +0100
Subject: [PATCH 066/351] latencyhist: disable jump-labels
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0a5eba0a9fb981e0f647364103c904aed8a88196
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=75b2eb2528e032a2f07a73f0f1d68ebf2be36959
Atleast on X86 we die a recursive death
@@ -62,3 +62,6 @@ index 659bdd079277..daac7dc4591c 100644
help
This option enables a transparent branch optimization that
makes certain almost-always-true or almost-always-false branch
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0067-tracing-Add-latency-histograms.patch b/debian/patches/features/all/rt/0067-tracing-Add-latency-histograms.patch
index 74bf928..b42cb96 100644
--- a/debian/patches/features/all/rt/0067-tracing-Add-latency-histograms.patch
+++ b/debian/patches/features/all/rt/0067-tracing-Add-latency-histograms.patch
@@ -1,7 +1,7 @@
From: Carsten Emde <C.Emde at osadl.org>
Date: Tue, 19 Jul 2011 14:03:41 +0100
Subject: [PATCH 067/351] tracing: Add latency histograms
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e9c168233d00b655d17d7760da31720066ee3182
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=83f165715f6675e8e46ecc867e192bee333d06fa
This patch provides a recording mechanism to store data of potential
sources of system latencies. The recordings separately determine the
@@ -1843,3 +1843,6 @@ index 03cdff84d026..0b5947ea46ef 100644
if (preempt_trace() && !irq_trace())
start_critical_timing(a0, a1);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0068-latency_hist-Update-sched_wakeup-probe.patch b/debian/patches/features/all/rt/0068-latency_hist-Update-sched_wakeup-probe.patch
index b503d61..cb0767c 100644
--- a/debian/patches/features/all/rt/0068-latency_hist-Update-sched_wakeup-probe.patch
+++ b/debian/patches/features/all/rt/0068-latency_hist-Update-sched_wakeup-probe.patch
@@ -1,7 +1,7 @@
From: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Date: Sun, 25 Oct 2015 18:06:05 -0400
Subject: [PATCH 068/351] latency_hist: Update sched_wakeup probe
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ae3de88378490def3998be9f3405217e93e156d9
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a8483aff96336626781af8cb7063370e592ca30e
"sched: Introduce the 'trace_sched_waking' tracepoint" introduces a
prototype change for the sched_wakeup probe: the "success" argument is
@@ -41,3 +41,6 @@ index 66a69eb5329c..b6c1d14b71c4 100644
{
unsigned long flags;
struct task_struct *curr = current;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0069-trace-latency-hist-Consider-new-argument-when-probin.patch b/debian/patches/features/all/rt/0069-trace-latency-hist-Consider-new-argument-when-probin.patch
index d642f94..e3880e9 100644
--- a/debian/patches/features/all/rt/0069-trace-latency-hist-Consider-new-argument-when-probin.patch
+++ b/debian/patches/features/all/rt/0069-trace-latency-hist-Consider-new-argument-when-probin.patch
@@ -2,7 +2,7 @@ From: Carsten Emde <C.Emde at osadl.org>
Date: Tue, 5 Jan 2016 10:21:59 +0100
Subject: [PATCH 069/351] trace/latency-hist: Consider new argument when
probing the sched_switch tracer
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=12b95063aae837307578d057db5062834a0c4160
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=30dfacf855885a275da7376bf54ed8870599f1e3
The sched_switch tracer has got a new argument. Fix the latency tracer
accordingly.
@@ -29,7 +29,7 @@ index b6c1d14b71c4..7f6ee70dea41 100644
static notrace void probe_sched_migrate_task(void *,
struct task_struct *task, int cpu);
static struct enable_data wakeup_latency_enabled_data = {
-@@ -907,7 +907,7 @@ static notrace void probe_wakeup_latency_hist_start(void *v,
+@@ -907,7 +907,7 @@ out:
}
static notrace void probe_wakeup_latency_hist_stop(void *v,
@@ -38,3 +38,6 @@ index b6c1d14b71c4..7f6ee70dea41 100644
{
unsigned long flags;
int cpu = task_cpu(next);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0070-trace-Use-rcuidle-version-for-preemptoff_hist-trace-.patch b/debian/patches/features/all/rt/0070-trace-Use-rcuidle-version-for-preemptoff_hist-trace-.patch
index a32e5bd..e060859 100644
--- a/debian/patches/features/all/rt/0070-trace-Use-rcuidle-version-for-preemptoff_hist-trace-.patch
+++ b/debian/patches/features/all/rt/0070-trace-Use-rcuidle-version-for-preemptoff_hist-trace-.patch
@@ -2,7 +2,7 @@ From: Yang Shi <yang.shi at windriver.com>
Date: Tue, 23 Feb 2016 13:23:23 -0800
Subject: [PATCH 070/351] trace: Use rcuidle version for preemptoff_hist trace
point
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=832a6a567b9f28ec0b6bce686efd173b54a67d71
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5b474f6b9506cee4bf7233c7487459b094e9d1e8
When running -rt kernel with both PREEMPT_OFF_HIST and LOCKDEP enabled,
the below error is reported:
@@ -89,3 +89,6 @@ index 0b5947ea46ef..940bd10b4406 100644
}
#else /* !CONFIG_PROVE_LOCKING */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0071-printk-Add-a-printk-kill-switch.patch b/debian/patches/features/all/rt/0071-printk-Add-a-printk-kill-switch.patch
index 50d9c13..5b21e7b 100644
--- a/debian/patches/features/all/rt/0071-printk-Add-a-printk-kill-switch.patch
+++ b/debian/patches/features/all/rt/0071-printk-Add-a-printk-kill-switch.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 22 Jul 2011 17:58:40 +0200
Subject: [PATCH 071/351] printk: Add a printk kill switch
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bb42b8132781f916ba3765c0dd984834b1be214b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6a796709a41df816d3c9f3b96bb71b8717d179a2
Add a prinkt-kill-switch. This is used from (NMI) watchdog to ensure that
it does not dead-lock with the early printk code.
@@ -167,3 +167,6 @@ index 12b8dd640786..4c90d2ee7433 100644
if (hardlockup_panic)
nmi_panic(regs, "Hard LOCKUP");
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0072-printk-Add-force_early_printk-boot-param-to-help-wit.patch b/debian/patches/features/all/rt/0072-printk-Add-force_early_printk-boot-param-to-help-wit.patch
index 2104a1d..be9f095 100644
--- a/debian/patches/features/all/rt/0072-printk-Add-force_early_printk-boot-param-to-help-wit.patch
+++ b/debian/patches/features/all/rt/0072-printk-Add-force_early_printk-boot-param-to-help-wit.patch
@@ -2,7 +2,7 @@ From: Peter Zijlstra <peterz at infradead.org>
Date: Fri, 2 Sep 2011 14:41:29 +0200
Subject: [PATCH 072/351] printk: Add "force_early_printk" boot param to help
with debugging
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f532e7fdf5b0482cf667c733b89c2e04d399b2db
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2852a151b0ac4e227855e6999f697b55e8a07eb9
Gives me an option to screw printk and actually see what the machine
says.
@@ -33,3 +33,6 @@ index 9d9e1f7e4240..35fb8be3e811 100644
void printk_kill(void)
{
printk_killswitch = true;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0073-rt-Provide-PREEMPT_RT_BASE-config-switch.patch b/debian/patches/features/all/rt/0073-rt-Provide-PREEMPT_RT_BASE-config-switch.patch
index 96fe16d..2480872 100644
--- a/debian/patches/features/all/rt/0073-rt-Provide-PREEMPT_RT_BASE-config-switch.patch
+++ b/debian/patches/features/all/rt/0073-rt-Provide-PREEMPT_RT_BASE-config-switch.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 17 Jun 2011 12:39:57 +0200
Subject: [PATCH 073/351] rt: Provide PREEMPT_RT_BASE config switch
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=136764a6b0c06ea52406b3b403e48e0726f849e8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=89946acaa00962a141912c73b97a7690d1b81119
Introduce PREEMPT_RT_BASE which enables parts of
PREEMPT_RT_FULL. Forces interrupt threading and enables some of the RT
@@ -54,3 +54,6 @@ index 3f9c97419f02..c669134982ec 100644
endchoice
config PREEMPT_COUNT
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0074-kconfig-Disable-config-options-which-are-not-RT-comp.patch b/debian/patches/features/all/rt/0074-kconfig-Disable-config-options-which-are-not-RT-comp.patch
index 82f002c..6a212d3 100644
--- a/debian/patches/features/all/rt/0074-kconfig-Disable-config-options-which-are-not-RT-comp.patch
+++ b/debian/patches/features/all/rt/0074-kconfig-Disable-config-options-which-are-not-RT-comp.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 24 Jul 2011 12:11:43 +0200
Subject: [PATCH 074/351] kconfig: Disable config options which are not RT
compatible
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=acc440ddad06b17641ee57c3a349b1b497c28a10
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=40183b7960bad5990906c94f7c5bdfdb031793b5
Disable stuff which is known to have issues on RT
@@ -37,3 +37,6 @@ index 86e3e0e74d20..77e5862a1ed2 100644
select COMPACTION
select RADIX_TREE_MULTIORDER
help
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0075-kconfig-Add-PREEMPT_RT_FULL.patch b/debian/patches/features/all/rt/0075-kconfig-Add-PREEMPT_RT_FULL.patch
index a43cba9..1f8d3f9 100644
--- a/debian/patches/features/all/rt/0075-kconfig-Add-PREEMPT_RT_FULL.patch
+++ b/debian/patches/features/all/rt/0075-kconfig-Add-PREEMPT_RT_FULL.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 29 Jun 2011 14:58:57 +0200
Subject: [PATCH 075/351] kconfig: Add PREEMPT_RT_FULL
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=75c3fcfc93316550772dec76cd1c66ed69a48082
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e6699f0856c0f18936b0bcd4faac92d25660fa20
Introduce the final symbol for PREEMPT_RT_FULL.
@@ -16,7 +16,7 @@ diff --git a/init/Makefile b/init/Makefile
index c4fb45525d08..821190dfaa75 100644
--- a/init/Makefile
+++ b/init/Makefile
-@@ -35,4 +35,4 @@ $(obj)/version.o: include/generated/compile.h
+@@ -35,4 +35,4 @@ silent_chk_compile.h = :
include/generated/compile.h: FORCE
@$($(quiet)chk_compile.h)
$(Q)$(CONFIG_SHELL) $(srctree)/scripts/mkcompile_h $@ \
@@ -63,3 +63,6 @@ index 6fdc97ef6023..523e0420d7f0 100755
UTS_VERSION="$UTS_VERSION $CONFIG_FLAGS $TIMESTAMP"
# Truncate to maximum length
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0076-bug-BUG_ON-WARN_ON-variants-dependend-on-RT-RT.patch b/debian/patches/features/all/rt/0076-bug-BUG_ON-WARN_ON-variants-dependend-on-RT-RT.patch
index b38619a..8fe933f 100644
--- a/debian/patches/features/all/rt/0076-bug-BUG_ON-WARN_ON-variants-dependend-on-RT-RT.patch
+++ b/debian/patches/features/all/rt/0076-bug-BUG_ON-WARN_ON-variants-dependend-on-RT-RT.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:29:58 -0500
Subject: [PATCH 076/351] bug: BUG_ON/WARN_ON variants dependend on RT/!RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7b17e83e1bdcd7c425d3d778454b874daf361329
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ab44b650392a75e3dcbec963e42f8cf1b58fae7a
Introduce RT/NON-RT WARN/BUG statements to avoid ifdefs in the code.
@@ -36,3 +36,6 @@ index 6f96247226a4..fa53a21263c2 100644
#endif /* __ASSEMBLY__ */
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0077-iommu-amd-Use-WARN_ON_NORT-in-__attach_device.patch b/debian/patches/features/all/rt/0077-iommu-amd-Use-WARN_ON_NORT-in-__attach_device.patch
index 38b916b..77a068c 100644
--- a/debian/patches/features/all/rt/0077-iommu-amd-Use-WARN_ON_NORT-in-__attach_device.patch
+++ b/debian/patches/features/all/rt/0077-iommu-amd-Use-WARN_ON_NORT-in-__attach_device.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 27 Feb 2016 10:22:23 +0100
Subject: [PATCH 077/351] iommu/amd: Use WARN_ON_NORT in __attach_device()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=54a3b493d78e1057cfbe5d4d9a6efcfb1671de99
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0d0508549da88cf2501cb126b352fc7933402ca6
RT does not disable interrupts here, but the protection is still
correct. Fixup the WARN_ON so it won't yell on RT.
@@ -16,7 +16,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
-index 1a0b110f12c0..a88595b21111 100644
+index 0c910a863581..75ee9538f169 100644
--- a/drivers/iommu/amd_iommu.c
+++ b/drivers/iommu/amd_iommu.c
@@ -1923,10 +1923,10 @@ static int __attach_device(struct iommu_dev_data *dev_data,
@@ -47,3 +47,6 @@ index 1a0b110f12c0..a88595b21111 100644
if (WARN_ON(!dev_data->domain))
return;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0078-rt-local_irq_-variants-depending-on-RT-RT.patch b/debian/patches/features/all/rt/0078-rt-local_irq_-variants-depending-on-RT-RT.patch
index 9e77132..75ec8e7 100644
--- a/debian/patches/features/all/rt/0078-rt-local_irq_-variants-depending-on-RT-RT.patch
+++ b/debian/patches/features/all/rt/0078-rt-local_irq_-variants-depending-on-RT-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 21 Jul 2009 22:34:14 +0200
Subject: [PATCH 078/351] rt: local_irq_* variants depending on RT/!RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f35dd408f32933f8e5d4474f60e15768203e3a65
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4a01d7c065ed5048553372028892ac491ec0eca6
Add local_irq_*_(no)rt variant which are mainly used to break
interrupt disabled sections on PREEMPT_RT or to explicitely disable
@@ -54,3 +54,6 @@ index 5dd1272d1ab2..f8f27cc5546f 100644
+#endif
+
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0079-preempt-Provide-preempt_-_-no-rt-variants.patch b/debian/patches/features/all/rt/0079-preempt-Provide-preempt_-_-no-rt-variants.patch
index c6eca0f..b6ff198 100644
--- a/debian/patches/features/all/rt/0079-preempt-Provide-preempt_-_-no-rt-variants.patch
+++ b/debian/patches/features/all/rt/0079-preempt-Provide-preempt_-_-no-rt-variants.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 24 Jul 2009 12:38:56 +0200
Subject: [PATCH 079/351] preempt: Provide preempt_*_(no)rt variants
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=67c1f4cc5dc33d4e541749b65c67080c545afd97
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=355da1e759d151f57651c377d8e6c3fbdee24c0f
RT needs a few preempt_disable/enable points which are not necessary
otherwise. Implement variants to avoid #ifdeffery.
@@ -47,3 +47,6 @@ index 7eeceac52dea..26e0eaa16492 100644
#ifdef CONFIG_PREEMPT_NOTIFIERS
struct preempt_notifier;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0080-Intrduce-migrate_disable-cpu_light.patch b/debian/patches/features/all/rt/0080-Intrduce-migrate_disable-cpu_light.patch
index 075955b..d08112b 100644
--- a/debian/patches/features/all/rt/0080-Intrduce-migrate_disable-cpu_light.patch
+++ b/debian/patches/features/all/rt/0080-Intrduce-migrate_disable-cpu_light.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 17 Jun 2011 15:42:38 +0200
Subject: [PATCH 080/351] Intrduce migrate_disable() + cpu_light()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d5fbfdf1fe816d093bdfa864b3d0cf298c1d167a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=87c55d018a3d7363ee05842f9b5f0fe5c721956b
Introduce migrate_disable(). The task can't be pushed to another CPU but can
be preempted.
@@ -293,3 +293,6 @@ index 1afec32de6f2..11fa431046a8 100644
print_symbol("caller is %s\n", (long)__builtin_return_address(0));
dump_stack();
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0081-futex-workaround-migrate_disable-enable-in-different.patch b/debian/patches/features/all/rt/0081-futex-workaround-migrate_disable-enable-in-different.patch
index fe6b084..dced1da 100644
--- a/debian/patches/features/all/rt/0081-futex-workaround-migrate_disable-enable-in-different.patch
+++ b/debian/patches/features/all/rt/0081-futex-workaround-migrate_disable-enable-in-different.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 8 Mar 2017 14:23:35 +0100
Subject: [PATCH 081/351] futex: workaround migrate_disable/enable in different
context
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9d97e28743fc9103c38fb0433ed9bce69954b0cd
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8365747b9d7498a94e4003ab9e673b55189ef735
migrate_disable()/migrate_enable() takes a different path in atomic() vs
!atomic() context. These little hacks ensure that we don't underflow / overflow
@@ -19,7 +19,7 @@ diff --git a/kernel/futex.c b/kernel/futex.c
index c1d2034800aa..1ec1a9910beb 100644
--- a/kernel/futex.c
+++ b/kernel/futex.c
-@@ -2670,9 +2670,18 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
+@@ -2670,9 +2670,18 @@ retry_private:
* lock handoff sequence.
*/
raw_spin_lock_irq(&q.pi_state->pi_mutex.wait_lock);
@@ -38,7 +38,7 @@ index c1d2034800aa..1ec1a9910beb 100644
if (ret) {
if (ret == 1)
-@@ -2816,10 +2825,21 @@ static int futex_unlock_pi(u32 __user *uaddr, unsigned int flags)
+@@ -2816,10 +2825,21 @@ retry:
* observed.
*/
raw_spin_lock_irq(&pi_state->pi_mutex.wait_lock);
@@ -60,3 +60,6 @@ index c1d2034800aa..1ec1a9910beb 100644
put_pi_state(pi_state);
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0082-rt-Add-local-irq-locks.patch b/debian/patches/features/all/rt/0082-rt-Add-local-irq-locks.patch
index 5cc55f4..b64e42a 100644
--- a/debian/patches/features/all/rt/0082-rt-Add-local-irq-locks.patch
+++ b/debian/patches/features/all/rt/0082-rt-Add-local-irq-locks.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 20 Jun 2011 09:03:47 +0200
Subject: [PATCH 082/351] rt: Add local irq locks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d4ae0c4e496540dd51576cbb9f2c1e1089b0ff76
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b1c3d3099f108bb77174aa12087a88db335a5ed2
Introduce locallock. For !RT this maps to preempt_disable()/
local_irq_disable() so there is not much that changes. For RT this will
@@ -330,3 +330,6 @@ index 491b3f5a5f8a..b988bf40ad3e 100644
/* minimum unit size, also is the maximum supported allocation size */
#define PCPU_MIN_UNIT_SIZE PFN_ALIGN(32 << 10)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0083-locallock-add-local_lock_on.patch b/debian/patches/features/all/rt/0083-locallock-add-local_lock_on.patch
index db2a6f3..5540edd 100644
--- a/debian/patches/features/all/rt/0083-locallock-add-local_lock_on.patch
+++ b/debian/patches/features/all/rt/0083-locallock-add-local_lock_on.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 27 May 2016 15:11:51 +0200
Subject: [PATCH 083/351] locallock: add local_lock_on()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7fb19106d14de5132a4599c80cde80784c1c2c18
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=234ba30f5b734dd5cf632b420179e460a41f9ea0
Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
---
@@ -32,3 +32,6 @@ index 218e5a4db343..96f22c568998 100644
static inline void __local_lock_irq(struct local_irq_lock *lv)
{
spin_lock_irqsave(&lv->lock, lv->flags);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0084-ata-Do-not-disable-interrupts-in-ide-code-for-preemp.patch b/debian/patches/features/all/rt/0084-ata-Do-not-disable-interrupts-in-ide-code-for-preemp.patch
index 9cb0d42..d0b2151 100644
--- a/debian/patches/features/all/rt/0084-ata-Do-not-disable-interrupts-in-ide-code-for-preemp.patch
+++ b/debian/patches/features/all/rt/0084-ata-Do-not-disable-interrupts-in-ide-code-for-preemp.patch
@@ -2,7 +2,7 @@ From: Steven Rostedt <srostedt at redhat.com>
Date: Fri, 3 Jul 2009 08:44:29 -0500
Subject: [PATCH 084/351] ata: Do not disable interrupts in ide code for
preempt-rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=783300bb506dac22bdbfab1637069c905c21092e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7a8541c8f9c862bd666c00e7b2aeb652c50bd027
Use the local_irq_*_nort variants.
@@ -14,7 +14,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c
-index 051b6158d1b7..7ad293bef6ed 100644
+index 8d22acdf90f0..64fbad747da9 100644
--- a/drivers/ata/libata-sff.c
+++ b/drivers/ata/libata-sff.c
@@ -678,9 +678,9 @@ unsigned int ata_sff_data_xfer_noirq(struct ata_device *dev, unsigned char *buf,
@@ -47,7 +47,7 @@ index 051b6158d1b7..7ad293bef6ed 100644
} else {
buf = page_address(page);
ap->ops->sff_data_xfer(qc->dev, buf + offset, qc->sect_size,
-@@ -864,7 +864,7 @@ static int __atapi_pio_bytes(struct ata_queued_cmd *qc, unsigned int bytes)
+@@ -864,7 +864,7 @@ next_sg:
unsigned long flags;
/* FIXME: use bounce buffer */
@@ -56,7 +56,7 @@ index 051b6158d1b7..7ad293bef6ed 100644
buf = kmap_atomic(page);
/* do the actual data transfer */
-@@ -872,7 +872,7 @@ static int __atapi_pio_bytes(struct ata_queued_cmd *qc, unsigned int bytes)
+@@ -872,7 +872,7 @@ next_sg:
count, rw);
kunmap_atomic(buf);
@@ -65,3 +65,6 @@ index 051b6158d1b7..7ad293bef6ed 100644
} else {
buf = page_address(page);
consumed = ap->ops->sff_data_xfer(dev, buf + offset,
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0085-ide-Do-not-disable-interrupts-for-PREEMPT-RT.patch b/debian/patches/features/all/rt/0085-ide-Do-not-disable-interrupts-for-PREEMPT-RT.patch
index 3d454ec..3eb086d 100644
--- a/debian/patches/features/all/rt/0085-ide-Do-not-disable-interrupts-for-PREEMPT-RT.patch
+++ b/debian/patches/features/all/rt/0085-ide-Do-not-disable-interrupts-for-PREEMPT-RT.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:30:16 -0500
Subject: [PATCH 085/351] ide: Do not disable interrupts for PREEMPT-RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3ea21ba2e2894d22963a029e3b5ad77b311b3063
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3b2970a20a69d3ee2411c6fb310234e412eb0a17
Use the local_irq_*_nort variants.
@@ -30,7 +30,7 @@ index 36f76e28a0bf..394f142f90c7 100644
if (m5229_revision < 0xC2) {
/*
-@@ -325,7 +325,7 @@ static int init_chipset_ali15x3(struct pci_dev *dev)
+@@ -325,7 +325,7 @@ out:
}
pci_dev_put(north);
pci_dev_put(isa_dev);
@@ -181,3 +181,6 @@ index a716693417a3..be0568c722d6 100644
ide_set_handler(drive, &task_pio_intr, WAIT_WORSTCASE);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0086-infiniband-Mellanox-IB-driver-patch-use-_nort-primit.patch b/debian/patches/features/all/rt/0086-infiniband-Mellanox-IB-driver-patch-use-_nort-primit.patch
index deb7dba..1dab36b 100644
--- a/debian/patches/features/all/rt/0086-infiniband-Mellanox-IB-driver-patch-use-_nort-primit.patch
+++ b/debian/patches/features/all/rt/0086-infiniband-Mellanox-IB-driver-patch-use-_nort-primit.patch
@@ -2,7 +2,7 @@ From: Sven-Thorsten Dietrich <sdietrich at novell.com>
Date: Fri, 3 Jul 2009 08:30:35 -0500
Subject: [PATCH 086/351] infiniband: Mellanox IB driver patch use _nort()
primitives
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=47d0b4af8a5292ca23ee32855a2030d07dda4ebe
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7486d7fe4a1d008b6a70208e3aa5266cfd181c51
Fixes in_atomic stack-dump, when Mellanox module is loaded into the RT
Kernel.
@@ -41,3 +41,6 @@ index fddff403d5d2..cca1bb4fbfe3 100644
/*
* make sure the in-flight joins have finished before we attempt
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0087-input-gameport-Do-not-disable-interrupts-on-PREEMPT_.patch b/debian/patches/features/all/rt/0087-input-gameport-Do-not-disable-interrupts-on-PREEMPT_.patch
index 3916f47..a710845 100644
--- a/debian/patches/features/all/rt/0087-input-gameport-Do-not-disable-interrupts-on-PREEMPT_.patch
+++ b/debian/patches/features/all/rt/0087-input-gameport-Do-not-disable-interrupts-on-PREEMPT_.patch
@@ -2,7 +2,7 @@ From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:30:16 -0500
Subject: [PATCH 087/351] input: gameport: Do not disable interrupts on
PREEMPT_RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b6a6d5428517edaa56f52b05720d900bed50524e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f7c6bf01da741d17b7ad43145671d6095048f2c6
Use the _nort() primitives.
@@ -61,3 +61,6 @@ index 4a2a9e370be7..e970d9afd179 100644
udelay(i * 10);
if (t2 - t1 < tx) tx = t2 - t1;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0088-core-Do-not-disable-interrupts-on-RT-in-kernel-users.patch b/debian/patches/features/all/rt/0088-core-Do-not-disable-interrupts-on-RT-in-kernel-users.patch
index 2a99a85..557a06b 100644
--- a/debian/patches/features/all/rt/0088-core-Do-not-disable-interrupts-on-RT-in-kernel-users.patch
+++ b/debian/patches/features/all/rt/0088-core-Do-not-disable-interrupts-on-RT-in-kernel-users.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 21 Jul 2009 23:06:05 +0200
Subject: [PATCH 088/351] core: Do not disable interrupts on RT in
kernel/users.c
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6cdd61495f3fbbe55e7fdecb828048e86b20f33c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=309692ca0f11ef28b85fbf8d0b431e7ae04b5715
Use the local_irq_*_nort variants to reduce latencies in RT. The code
is serialized by the locks. No need to disable interrupts.
@@ -30,3 +30,6 @@ index b069ccbfb0b0..1a2e88e98b5e 100644
}
struct user_struct *alloc_uid(kuid_t uid)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0089-usb-Use-_nort-in-giveback-function.patch b/debian/patches/features/all/rt/0089-usb-Use-_nort-in-giveback-function.patch
index 32c3763..1072126 100644
--- a/debian/patches/features/all/rt/0089-usb-Use-_nort-in-giveback-function.patch
+++ b/debian/patches/features/all/rt/0089-usb-Use-_nort-in-giveback-function.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 8 Nov 2013 17:34:54 +0100
Subject: [PATCH 089/351] usb: Use _nort in giveback function
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bd0fe588371fa58fa0eb9839af53488e121d0c0c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=358e5b3b642748d9f13c664f5be3cd7a3837f09f
Since commit 94dfd7ed ("USB: HCD: support giveback of URB in tasklet
context") I see
@@ -58,3 +58,6 @@ index fcc7aa248ce7..fb2c38d875f9 100644
usb_anchor_resume_wakeups(anchor);
atomic_dec(&urb->use_count);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0090-mm-scatterlist-Do-not-disable-irqs-on-RT.patch b/debian/patches/features/all/rt/0090-mm-scatterlist-Do-not-disable-irqs-on-RT.patch
index 49a68a1..943d8e8 100644
--- a/debian/patches/features/all/rt/0090-mm-scatterlist-Do-not-disable-irqs-on-RT.patch
+++ b/debian/patches/features/all/rt/0090-mm-scatterlist-Do-not-disable-irqs-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 3 Jul 2009 08:44:34 -0500
Subject: [PATCH 090/351] mm/scatterlist: Do not disable irqs on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7023840c8d6b360a05a9e3705ec459b0c69215e7
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e23265aca526bf9e72b80ae6c543f57e51146239
The local_irq_save() is not only used to get things done "fast" but
also to ensure that in case of SG_MITER_ATOMIC we are in "atomic"
@@ -44,3 +44,6 @@ index 004fc70fc56a..ccc46992a517 100644
return offset;
}
EXPORT_SYMBOL(sg_copy_buffer);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0091-mm-workingset-Do-not-protect-workingset_shadow_nodes.patch b/debian/patches/features/all/rt/0091-mm-workingset-Do-not-protect-workingset_shadow_nodes.patch
index b9b924d..0a0ba31 100644
--- a/debian/patches/features/all/rt/0091-mm-workingset-Do-not-protect-workingset_shadow_nodes.patch
+++ b/debian/patches/features/all/rt/0091-mm-workingset-Do-not-protect-workingset_shadow_nodes.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 29 Jan 2015 17:19:44 +0100
Subject: [PATCH 091/351] mm/workingset: Do not protect workingset_shadow_nodes
with irq off
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1e542fbd29e6be6ce8c78793a2472fe24174cb0e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e01dc61368f759609b2cda8aedc66bdf47085eaa
workingset_shadow_nodes is protected by local_irq_disable(). Some users
use spin_lock_irq().
@@ -94,7 +94,7 @@ diff --git a/mm/workingset.c b/mm/workingset.c
index 4c4f05655e6e..b97b1e87b54c 100644
--- a/mm/workingset.c
+++ b/mm/workingset.c
-@@ -334,7 +334,8 @@ void workingset_activation(struct page *page)
+@@ -334,7 +334,8 @@ out:
* point where they would still be useful.
*/
@@ -161,3 +161,6 @@ index 4c4f05655e6e..b97b1e87b54c 100644
err:
return ret;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0092-signal-Make-__lock_task_sighand-RT-aware.patch b/debian/patches/features/all/rt/0092-signal-Make-__lock_task_sighand-RT-aware.patch
index cebac6d..ff063f6 100644
--- a/debian/patches/features/all/rt/0092-signal-Make-__lock_task_sighand-RT-aware.patch
+++ b/debian/patches/features/all/rt/0092-signal-Make-__lock_task_sighand-RT-aware.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 22 Jul 2011 08:07:08 +0200
Subject: [PATCH 092/351] signal: Make __lock_task_sighand() RT aware
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=99fa9ac3e90ac5049fb761f2a34f0d56e5c1c664
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=633fe15be6997ab799c7bf0e0d6127955fd95fe6
local_irq_save() + spin_lock(&sighand->siglock) does not work on
-RT. Use the nort variants.
@@ -12,10 +12,10 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
-index 739615d8d5ae..be9753809dc7 100644
+index 64e8df5e3f39..8c4d357f484f 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
-@@ -1284,12 +1284,12 @@ struct sighand_struct *__lock_task_sighand(struct task_struct *tsk,
+@@ -1286,12 +1286,12 @@ struct sighand_struct *__lock_task_sighand(struct task_struct *tsk,
* Disable interrupts early to avoid deadlocks.
* See rcu_read_unlock() comment header for details.
*/
@@ -30,7 +30,7 @@ index 739615d8d5ae..be9753809dc7 100644
break;
}
/*
-@@ -1310,7 +1310,7 @@ struct sighand_struct *__lock_task_sighand(struct task_struct *tsk,
+@@ -1312,7 +1312,7 @@ struct sighand_struct *__lock_task_sighand(struct task_struct *tsk,
}
spin_unlock(&sighand->siglock);
rcu_read_unlock();
@@ -39,3 +39,6 @@ index 739615d8d5ae..be9753809dc7 100644
}
return sighand;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0093-signal-x86-Delay-calling-signals-in-atomic.patch b/debian/patches/features/all/rt/0093-signal-x86-Delay-calling-signals-in-atomic.patch
index a9508f5..8bb2b83 100644
--- a/debian/patches/features/all/rt/0093-signal-x86-Delay-calling-signals-in-atomic.patch
+++ b/debian/patches/features/all/rt/0093-signal-x86-Delay-calling-signals-in-atomic.patch
@@ -1,7 +1,7 @@
From: Oleg Nesterov <oleg at redhat.com>
Date: Tue, 14 Jul 2015 14:26:34 +0200
Subject: [PATCH 093/351] signal/x86: Delay calling signals in atomic
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=adce01ee88f6f51a2d835765cb4d7ac7f70d022f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=052dbbc75fe7b6ccd197db6dd6070bd80623db16
On x86_64 we must disable preemption before we enable interrupts
for stack faults, int3 and debugging, because the current task is using
@@ -94,10 +94,10 @@ index bfe832b3fc9f..040ae135ecb0 100644
unsigned long sas_ss_sp;
size_t sas_ss_size;
diff --git a/kernel/signal.c b/kernel/signal.c
-index be9753809dc7..99918dcd836f 100644
+index 8c4d357f484f..4d094ae3a625 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
-@@ -1224,8 +1224,8 @@ int do_send_sig_info(int sig, struct siginfo *info, struct task_struct *p,
+@@ -1226,8 +1226,8 @@ int do_send_sig_info(int sig, struct siginfo *info, struct task_struct *p,
* We don't want to have recursive SIGSEGV's etc, for example,
* that is why we also clear SIGNAL_UNKILLABLE.
*/
@@ -108,7 +108,7 @@ index be9753809dc7..99918dcd836f 100644
{
unsigned long int flags;
int ret, blocked, ignored;
-@@ -1250,6 +1250,39 @@ force_sig_info(int sig, struct siginfo *info, struct task_struct *t)
+@@ -1252,6 +1252,39 @@ force_sig_info(int sig, struct siginfo *info, struct task_struct *t)
return ret;
}
@@ -148,3 +148,6 @@ index be9753809dc7..99918dcd836f 100644
/*
* Nuke all other threads in the group.
*/
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0094-x86-signal-delay-calling-signals-on-32bit.patch b/debian/patches/features/all/rt/0094-x86-signal-delay-calling-signals-on-32bit.patch
index 51411a0..567f370 100644
--- a/debian/patches/features/all/rt/0094-x86-signal-delay-calling-signals-on-32bit.patch
+++ b/debian/patches/features/all/rt/0094-x86-signal-delay-calling-signals-on-32bit.patch
@@ -1,7 +1,7 @@
From: Yang Shi <yang.shi at linaro.org>
Date: Thu, 10 Dec 2015 10:58:51 -0800
Subject: [PATCH 094/351] x86/signal: delay calling signals on 32bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=92b348ab58b893166bee6f03651c6a23395a7260
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ddb43450a8092f61197c6ff6d1f4eaa97a65e3dc
When running some ptrace single step tests on x86-32 machine, the below problem
is triggered:
@@ -43,3 +43,6 @@ index c370fba8c38b..d1328789b759 100644
#define ARCH_RT_DELAYS_SIGNAL_SEND
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0095-net-wireless-Use-WARN_ON_NORT.patch b/debian/patches/features/all/rt/0095-net-wireless-Use-WARN_ON_NORT.patch
index 34114d7..2df4fb6 100644
--- a/debian/patches/features/all/rt/0095-net-wireless-Use-WARN_ON_NORT.patch
+++ b/debian/patches/features/all/rt/0095-net-wireless-Use-WARN_ON_NORT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 21 Jul 2011 21:05:33 +0200
Subject: [PATCH 095/351] net/wireless: Use WARN_ON_NORT()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ea2ea9ed0fda5d0892b8d0fc44f8cd1d0099d9e0
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=37b7cce0342bb209c461ee464b10a378ac25498a
The softirq counter is meaningless on RT, so the check triggers a
false positive.
@@ -24,3 +24,6 @@ index 439e597fd374..ca0daeaff370 100644
if (WARN_ON(status->band >= NUM_NL80211_BANDS))
goto drop;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0096-buffer_head-Replace-bh_uptodate_lock-for-rt.patch b/debian/patches/features/all/rt/0096-buffer_head-Replace-bh_uptodate_lock-for-rt.patch
index 7f5c9ff..b8dce5d 100644
--- a/debian/patches/features/all/rt/0096-buffer_head-Replace-bh_uptodate_lock-for-rt.patch
+++ b/debian/patches/features/all/rt/0096-buffer_head-Replace-bh_uptodate_lock-for-rt.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 18 Mar 2011 09:18:52 +0100
Subject: [PATCH 096/351] buffer_head: Replace bh_uptodate_lock for -rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4be10b502cc41eeeabe4d2b52273fe10cafaef8c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5e57b3d7311b144cd11101f50f032c1bfb4adce5
Wrap the bit_spin_lock calls into a separate inline and add the RT
replacements with a real spinlock.
@@ -166,3 +166,6 @@ index 4431ea2c8802..87c4ed37ee77 100644
/*
* macro tricks to expand the set_buffer_foo(), clear_buffer_foo()
* and buffer_foo() functions.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0097-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch b/debian/patches/features/all/rt/0097-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch
index 203387b..4b296b4 100644
--- a/debian/patches/features/all/rt/0097-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch
+++ b/debian/patches/features/all/rt/0097-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 18 Mar 2011 10:11:25 +0100
Subject: [PATCH 097/351] fs: jbd/jbd2: Make state lock and journal head lock
rt safe
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=343cafc95761b4ed3490ab1a4d9657cea3541e5f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4424d2b599a4e94a39a2b493163f99d5ffdd7038
bit_spin_locks break under RT.
@@ -104,3 +104,6 @@ index dfaa1f4dcb0c..d57dd06544a1 100644
}
#define J_ASSERT(assert) BUG_ON(!(assert))
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0098-list_bl-Make-list-head-locking-RT-safe.patch b/debian/patches/features/all/rt/0098-list_bl-Make-list-head-locking-RT-safe.patch
index 36fbcf9..426162b 100644
--- a/debian/patches/features/all/rt/0098-list_bl-Make-list-head-locking-RT-safe.patch
+++ b/debian/patches/features/all/rt/0098-list_bl-Make-list-head-locking-RT-safe.patch
@@ -1,7 +1,7 @@
From: Paul Gortmaker <paul.gortmaker at windriver.com>
Date: Fri, 21 Jun 2013 15:07:25 -0400
Subject: [PATCH 098/351] list_bl: Make list head locking RT safe
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7c9dcf1deaf8bbc254be286d30c11c3835c6411b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ceb8ea18648808562dfa7859c1d378b9176ccce1
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
@@ -115,3 +115,6 @@ index cb483305e1f5..d3af0990f01a 100644
}
static inline bool hlist_bl_is_locked(struct hlist_bl_head *b)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0099-list_bl-fixup-bogus-lockdep-warning.patch b/debian/patches/features/all/rt/0099-list_bl-fixup-bogus-lockdep-warning.patch
index 4e65d20..1c61035 100644
--- a/debian/patches/features/all/rt/0099-list_bl-fixup-bogus-lockdep-warning.patch
+++ b/debian/patches/features/all/rt/0099-list_bl-fixup-bogus-lockdep-warning.patch
@@ -1,7 +1,7 @@
From: Josh Cartwright <joshc at ni.com>
Date: Thu, 31 Mar 2016 00:04:25 -0500
Subject: [PATCH 099/351] list_bl: fixup bogus lockdep warning
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d7a5551333822f3138fc742402f735c5dd9cca97
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=85ed2eb3a75af8d2d212a84628cd0fc595d07867
At first glance, the use of 'static inline' seems appropriate for
INIT_HLIST_BL_HEAD().
@@ -98,3 +98,6 @@ index d3af0990f01a..4e5062316bb6 100644
static inline void INIT_HLIST_BL_NODE(struct hlist_bl_node *h)
{
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0100-genirq-Disable-irqpoll-on-rt.patch b/debian/patches/features/all/rt/0100-genirq-Disable-irqpoll-on-rt.patch
index f6bde48..847a16f 100644
--- a/debian/patches/features/all/rt/0100-genirq-Disable-irqpoll-on-rt.patch
+++ b/debian/patches/features/all/rt/0100-genirq-Disable-irqpoll-on-rt.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:29:57 -0500
Subject: [PATCH 100/351] genirq: Disable irqpoll on -rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=457d9cc09aba1fb19f9ee0b9ca2373a3b3433e6d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8dc1ec6286c5511950334bcdeb08b4256d0d790a
Creates long latencies for no value
@@ -37,3 +37,6 @@ index 5707f97a3e6a..73f38dc7a7fb 100644
irqfixup = 2;
printk(KERN_WARNING "Misrouted IRQ fixup and polling support "
"enabled\n");
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0101-genirq-Force-interrupt-thread-on-RT.patch b/debian/patches/features/all/rt/0101-genirq-Force-interrupt-thread-on-RT.patch
index 75b4f49..75b2a49 100644
--- a/debian/patches/features/all/rt/0101-genirq-Force-interrupt-thread-on-RT.patch
+++ b/debian/patches/features/all/rt/0101-genirq-Force-interrupt-thread-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 3 Apr 2011 11:57:29 +0200
Subject: [PATCH 101/351] genirq: Force interrupt thread on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=da9e3cd9428c84cba6c6896b026b789cb1c9ae65
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2387484b471470769ba70d403ba7d40eb56bb68a
Force threaded_irqs and optimize the code (force_irqthreads) in regard
to this.
@@ -51,3 +51,6 @@ index ea41820ab12e..bc1bfce421fd 100644
#endif
static void __synchronize_hardirq(struct irq_desc *desc)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0102-drivers-net-vortex-fix-locking-issues.patch b/debian/patches/features/all/rt/0102-drivers-net-vortex-fix-locking-issues.patch
index fab6fe6..42d56bc 100644
--- a/debian/patches/features/all/rt/0102-drivers-net-vortex-fix-locking-issues.patch
+++ b/debian/patches/features/all/rt/0102-drivers-net-vortex-fix-locking-issues.patch
@@ -1,7 +1,7 @@
From: Steven Rostedt <rostedt at goodmis.org>
Date: Fri, 3 Jul 2009 08:30:00 -0500
Subject: [PATCH 102/351] drivers/net: vortex fix locking issues
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=09ae2be6e4f2d047549beb8256d9725367038bc6
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fe72ecba91c1b6c5a6d5560bf9ea6c97aad65f68
Argh, cut and paste wasn't enough...
@@ -52,3 +52,6 @@ index 9133e7926da5..63afb921ed40 100644
}
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0103-mm-page_alloc-rt-friendly-per-cpu-pages.patch b/debian/patches/features/all/rt/0103-mm-page_alloc-rt-friendly-per-cpu-pages.patch
index 141e820..7b42487 100644
--- a/debian/patches/features/all/rt/0103-mm-page_alloc-rt-friendly-per-cpu-pages.patch
+++ b/debian/patches/features/all/rt/0103-mm-page_alloc-rt-friendly-per-cpu-pages.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:29:37 -0500
Subject: [PATCH 103/351] mm: page_alloc: rt-friendly per-cpu pages
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9711549a49c512d15e47fb0a499185f4b554b6c1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=62d99d0f7d0d7afa8b8d9e013c9cad02c71b28ab
rt-friendly per-cpu pages: convert the irqs-off per-cpu locking
method into a preemptible, explicit-per-cpu-locks method.
@@ -204,3 +204,6 @@ index fbc38888252b..cb3569830c46 100644
}
#ifdef CONFIG_MEMORY_HOTREMOVE
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0104-mm-page_alloc-Reduce-lock-sections-further.patch b/debian/patches/features/all/rt/0104-mm-page_alloc-Reduce-lock-sections-further.patch
index 6cce1d2..dff5f7e 100644
--- a/debian/patches/features/all/rt/0104-mm-page_alloc-Reduce-lock-sections-further.patch
+++ b/debian/patches/features/all/rt/0104-mm-page_alloc-Reduce-lock-sections-further.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Fri, 3 Jul 2009 08:44:37 -0500
Subject: [PATCH 104/351] mm: page_alloc: Reduce lock sections further
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fb8cd4d3a9bcf616fc4ec295e796e4cd02025ac1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9871f1411b67298cf05630cab4e8081b50df9fed
Split out the pages which are to be freed into a separate list and
call free_pages_bulk() outside of the percpu page allocator locks.
@@ -205,3 +205,6 @@ index cb3569830c46..f06a57ee00b4 100644
}
out:
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0105-mm-swap-Convert-to-percpu-locked.patch b/debian/patches/features/all/rt/0105-mm-swap-Convert-to-percpu-locked.patch
index 53c6abe..27b81b3 100644
--- a/debian/patches/features/all/rt/0105-mm-swap-Convert-to-percpu-locked.patch
+++ b/debian/patches/features/all/rt/0105-mm-swap-Convert-to-percpu-locked.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:29:51 -0500
Subject: [PATCH 105/351] mm/swap: Convert to percpu locked
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=626121de914af008728eead6090a63c87e951e8b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a0f74584591df2bd7416681bd5da8151ee8f98e3
Replace global locks (get_cpu + local_irq_save) with "local_locks()".
Currently there is one of for "rotate" and one for "swap".
@@ -31,7 +31,7 @@ diff --git a/mm/compaction.c b/mm/compaction.c
index 70e6bec46dc2..6678ed58b7c6 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
-@@ -1593,10 +1593,12 @@ static enum compact_result compact_zone(struct zone *zone, struct compact_contro
+@@ -1593,10 +1593,12 @@ check_drain:
block_start_pfn(cc->migrate_pfn, cc->order);
if (cc->last_migrated_pfn < current_block_start) {
@@ -196,3 +196,6 @@ index 4dcf852e1e6d..93840ec3cc62 100644
}
static void lru_add_drain_per_cpu(struct work_struct *dummy)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0106-mm-perform-lru_add_drain_all-remotely.patch b/debian/patches/features/all/rt/0106-mm-perform-lru_add_drain_all-remotely.patch
index 3049aa8..4603c16 100644
--- a/debian/patches/features/all/rt/0106-mm-perform-lru_add_drain_all-remotely.patch
+++ b/debian/patches/features/all/rt/0106-mm-perform-lru_add_drain_all-remotely.patch
@@ -1,7 +1,7 @@
From: Luiz Capitulino <lcapitulino at redhat.com>
Date: Fri, 27 May 2016 15:03:28 +0200
Subject: [PATCH 106/351] mm: perform lru_add_drain_all() remotely
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=45b613f8e695ba4b6ad8f71f0513efca16b93e1a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=56951d73b76017c05bf42238bed3b20f1e8356ea
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
@@ -111,3 +111,6 @@ index 93840ec3cc62..69c3a5b24060 100644
put_online_cpus();
mutex_unlock(&lock);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0107-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch b/debian/patches/features/all/rt/0107-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch
index 724884c..f012499 100644
--- a/debian/patches/features/all/rt/0107-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch
+++ b/debian/patches/features/all/rt/0107-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch
@@ -2,7 +2,7 @@ From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:30:13 -0500
Subject: [PATCH 107/351] mm/vmstat: Protect per cpu variables with preempt
disable on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9980328d216e909e6a4c99273e60faf308421446
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c2db32eb6954a77d17db8aab61c9e3cfe3bf8fde
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
@@ -40,7 +40,7 @@ index 613771909b6e..e28c5a43229d 100644
static inline void count_vm_events(enum vm_event_item item, long delta)
diff --git a/mm/vmstat.c b/mm/vmstat.c
-index 604f26a4f696..312006d2db50 100644
+index 6a088df04b29..abda95be88b4 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -245,6 +245,7 @@ void __mod_zone_page_state(struct zone *zone, enum zone_stat_item item,
@@ -139,3 +139,6 @@ index 604f26a4f696..312006d2db50 100644
}
void __dec_zone_page_state(struct page *page, enum zone_stat_item item)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0108-ARM-Initialize-split-page-table-locks-for-vector-pag.patch b/debian/patches/features/all/rt/0108-ARM-Initialize-split-page-table-locks-for-vector-pag.patch
index 65fec04..476985c 100644
--- a/debian/patches/features/all/rt/0108-ARM-Initialize-split-page-table-locks-for-vector-pag.patch
+++ b/debian/patches/features/all/rt/0108-ARM-Initialize-split-page-table-locks-for-vector-pag.patch
@@ -2,7 +2,7 @@ From: Frank Rowand <frank.rowand at am.sony.com>
Date: Sat, 1 Oct 2011 18:58:13 -0700
Subject: [PATCH 108/351] ARM: Initialize split page table locks for vector
page
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1915af65520726915411741e0338e1a25fbbeb8e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5735be7834260a72427fb35988529dd0eefac78a
Without this patch, ARM can not use SPLIT_PTLOCK_CPUS if
PREEMPT_RT_FULL=y because vectors_user_mapping() creates a
@@ -70,3 +70,6 @@ index 91d2d5b01414..750550098b59 100644
#ifdef CONFIG_KUSER_HELPERS
/*
* The vectors page is always readable from user space for the
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0109-mm-bounce-Use-local_irq_save_nort.patch b/debian/patches/features/all/rt/0109-mm-bounce-Use-local_irq_save_nort.patch
index 794d565..18c9b2e 100644
--- a/debian/patches/features/all/rt/0109-mm-bounce-Use-local_irq_save_nort.patch
+++ b/debian/patches/features/all/rt/0109-mm-bounce-Use-local_irq_save_nort.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 9 Jan 2013 10:33:09 +0100
Subject: [PATCH 109/351] mm: bounce: Use local_irq_save_nort
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=369b69704b7a049906eb769b052c31e9d590130e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=848a997c762753b6d982f56ea2be184fdc79864c
kmap_atomic() is preemptible on RT.
@@ -28,3 +28,6 @@ index 1cb5dd3a5da1..2f1ec8a67cbe 100644
}
#else /* CONFIG_HIGHMEM */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0110-mm-Allow-only-slub-on-RT.patch b/debian/patches/features/all/rt/0110-mm-Allow-only-slub-on-RT.patch
index 3fde560..887ba64 100644
--- a/debian/patches/features/all/rt/0110-mm-Allow-only-slub-on-RT.patch
+++ b/debian/patches/features/all/rt/0110-mm-Allow-only-slub-on-RT.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:44:03 -0500
Subject: [PATCH 110/351] mm: Allow only slub on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a8fb76cbd0c4aadd2c9a06c34887678c14102ba7
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7915a0268fc5fda0d37b3c8aa22c749e33a9ae46
Disable SLAB and SLOB on -RT. Only SLUB is adopted to -RT needs.
@@ -31,3 +31,6 @@ index ea73e8a9e89e..f3fe8040ff0f 100644
help
SLOB replaces the stock allocator with a drastically simpler
allocator. SLOB is generally more space efficient but
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0111-mm-Enable-SLUB-for-RT.patch b/debian/patches/features/all/rt/0111-mm-Enable-SLUB-for-RT.patch
index d88cc94..1e1fee7 100644
--- a/debian/patches/features/all/rt/0111-mm-Enable-SLUB-for-RT.patch
+++ b/debian/patches/features/all/rt/0111-mm-Enable-SLUB-for-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 25 Oct 2012 10:32:35 +0100
Subject: [PATCH 111/351] mm: Enable SLUB for RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b75f3e580f017fcb96b486709e8de11a8261a51f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2063da132ac29def6e7ea1df8ab99fdc05b6c90d
Make SLUB RT aware by converting locks to raw and using free lists to
move the freeing out of the lock held region.
@@ -41,7 +41,7 @@ index edc79ca3c6d5..bc7a5d448150 100644
slab_lock(page);
if (s->flags & SLAB_CONSISTENCY_CHECKS) {
-@@ -1179,7 +1179,7 @@ static noinline int free_debug_processing(
+@@ -1179,7 +1179,7 @@ out:
bulk_cnt, cnt);
slab_unlock(page);
@@ -135,7 +135,7 @@ index edc79ca3c6d5..bc7a5d448150 100644
return object;
}
-@@ -2076,7 +2106,7 @@ static void deactivate_slab(struct kmem_cache *s, struct page *page,
+@@ -2076,7 +2106,7 @@ redo:
* that acquire_slab() will see a slab page that
* is frozen
*/
@@ -144,7 +144,7 @@ index edc79ca3c6d5..bc7a5d448150 100644
}
} else {
m = M_FULL;
-@@ -2087,7 +2117,7 @@ static void deactivate_slab(struct kmem_cache *s, struct page *page,
+@@ -2087,7 +2117,7 @@ redo:
* slabs from diagnostic functions will not see
* any frozen slabs.
*/
@@ -153,7 +153,7 @@ index edc79ca3c6d5..bc7a5d448150 100644
}
}
-@@ -2122,7 +2152,7 @@ static void deactivate_slab(struct kmem_cache *s, struct page *page,
+@@ -2122,7 +2152,7 @@ redo:
goto redo;
if (lock)
@@ -254,7 +254,7 @@ index edc79ca3c6d5..bc7a5d448150 100644
void *freelist;
struct page *page;
-@@ -2561,6 +2615,13 @@ static void *___slab_alloc(struct kmem_cache *s, gfp_t gfpflags, int node,
+@@ -2561,6 +2615,13 @@ load_freelist:
VM_BUG_ON(!c->page->frozen);
c->freelist = get_freepointer(s, freelist);
c->tid = next_tid(c->tid);
@@ -268,7 +268,7 @@ index edc79ca3c6d5..bc7a5d448150 100644
return freelist;
new_slab:
-@@ -2592,7 +2653,7 @@ static void *___slab_alloc(struct kmem_cache *s, gfp_t gfpflags, int node,
+@@ -2592,7 +2653,7 @@ new_slab:
deactivate_slab(s, page, get_freepointer(s, freelist));
c->page = NULL;
c->freelist = NULL;
@@ -323,7 +323,7 @@ index edc79ca3c6d5..bc7a5d448150 100644
return;
slab_empty:
-@@ -2891,7 +2954,7 @@ static void __slab_free(struct kmem_cache *s, struct page *page,
+@@ -2891,7 +2954,7 @@ slab_empty:
remove_full(s, n, page);
}
@@ -467,3 +467,6 @@ index edc79ca3c6d5..bc7a5d448150 100644
}
for (i = 0; i < t.count; i++) {
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0112-slub-Enable-irqs-for-__GFP_WAIT.patch b/debian/patches/features/all/rt/0112-slub-Enable-irqs-for-__GFP_WAIT.patch
index 3f25f0c..d957c0b 100644
--- a/debian/patches/features/all/rt/0112-slub-Enable-irqs-for-__GFP_WAIT.patch
+++ b/debian/patches/features/all/rt/0112-slub-Enable-irqs-for-__GFP_WAIT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 9 Jan 2013 12:08:15 +0100
Subject: [PATCH 112/351] slub: Enable irqs for __GFP_WAIT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=87bf853eab5133b71980d9978e01ff8529a173ba
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=55c0ca72bd0d168db4bd38d2be036f284e35d5bb
SYSTEM_RUNNING might be too late for enabling interrupts. Allocations
with GFP_WAIT can happen before that. So use this as an indicator.
@@ -48,3 +48,6 @@ index bc7a5d448150..67eb368b9314 100644
local_irq_disable();
if (!page)
return NULL;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0113-slub-Disable-SLUB_CPU_PARTIAL.patch b/debian/patches/features/all/rt/0113-slub-Disable-SLUB_CPU_PARTIAL.patch
index 3247ede..935aa04 100644
--- a/debian/patches/features/all/rt/0113-slub-Disable-SLUB_CPU_PARTIAL.patch
+++ b/debian/patches/features/all/rt/0113-slub-Disable-SLUB_CPU_PARTIAL.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 15 Apr 2015 19:00:47 +0200
Subject: [PATCH 113/351] slub: Disable SLUB_CPU_PARTIAL
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=57c1051f0b9d2263921f794bad21607f9e6c53dd
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1640c2821d654f1a44de25d714dc42bf6fae4942
|BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:915
|in_atomic(): 1, irqs_disabled(): 0, pid: 87, name: rcuop/7
@@ -48,3 +48,6 @@ index f3fe8040ff0f..333d2b269208 100644
bool "SLUB per cpu partial cache"
help
Per cpu partial caches accellerate objects allocation and freeing
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0114-mm-page_alloc-Use-local_lock_on-instead-of-plain-spi.patch b/debian/patches/features/all/rt/0114-mm-page_alloc-Use-local_lock_on-instead-of-plain-spi.patch
index 1dd07a5..a9787b3 100644
--- a/debian/patches/features/all/rt/0114-mm-page_alloc-Use-local_lock_on-instead-of-plain-spi.patch
+++ b/debian/patches/features/all/rt/0114-mm-page_alloc-Use-local_lock_on-instead-of-plain-spi.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 27 Sep 2012 11:11:46 +0200
Subject: [PATCH 114/351] mm: page_alloc: Use local_lock_on() instead of plain
spinlock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a3b9a8e2735dddbcb015c537cb784fcec314c16d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=cfa50eb1af28a313b7dbfafc12b0bc6c4db46261
The plain spinlock while sufficient does not update the local_lock
internals. Use a proper local_lock function instead to ease debugging.
@@ -28,3 +28,6 @@ index 0e3df89b76a5..1cb08e1406ea 100644
#else
# define cpu_lock_irqsave(cpu, flags) local_irq_save(flags)
# define cpu_unlock_irqrestore(cpu, flags) local_irq_restore(flags)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0115-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch b/debian/patches/features/all/rt/0115-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch
index aa4e86f..d75ffeb 100644
--- a/debian/patches/features/all/rt/0115-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch
+++ b/debian/patches/features/all/rt/0115-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch
@@ -2,7 +2,7 @@ From: Yang Shi <yang.shi at windriver.com>
Date: Wed, 30 Oct 2013 11:48:33 -0700
Subject: [PATCH 115/351] mm/memcontrol: Don't call schedule_work_on in
preemption disabled context
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=158715cfabde690f20ba8a669c1687e440d890d8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bd4e959f8ddbc11ec9a7bd50b50da7336b41e64f
The following trace is triggered when running ltp oom test cases:
@@ -69,3 +69,6 @@ index 2a800c4a39bd..ae85112b058c 100644
put_online_cpus();
mutex_unlock(&percpu_charge_mutex);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0116-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch b/debian/patches/features/all/rt/0116-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch
index 9658c20..8309614 100644
--- a/debian/patches/features/all/rt/0116-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch
+++ b/debian/patches/features/all/rt/0116-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 28 Jan 2015 17:14:16 +0100
Subject: [PATCH 116/351] mm/memcontrol: Replace local_irq_disable with local
locks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=75c42e195f15eebc3a3fa8693badc5c9ab025736
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8e1ed54ac63af8e8f16569d2ceef22e402f52c0a
There are a few local_irq_disable() which then take sleeping locks. This
patch converts them local locks.
@@ -103,3 +103,6 @@ index ae85112b058c..e5391afdfce3 100644
}
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0117-mm-memcontrol-mem_cgroup_migrate-replace-another-loc.patch b/debian/patches/features/all/rt/0117-mm-memcontrol-mem_cgroup_migrate-replace-another-loc.patch
index 20c7f0f..df8ab37 100644
--- a/debian/patches/features/all/rt/0117-mm-memcontrol-mem_cgroup_migrate-replace-another-loc.patch
+++ b/debian/patches/features/all/rt/0117-mm-memcontrol-mem_cgroup_migrate-replace-another-loc.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Sun, 5 Jun 2016 08:11:13 +0200
Subject: [PATCH 117/351] mm/memcontrol: mem_cgroup_migrate() - replace another
local_irq_disable() w. local_lock_irq()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f02b41a976e71faae52732ff3ccb4c7998275020
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8490f9710e8c347befbdbec03530a648cb9ddb58
v4.6 grew a local_irq_disable() in mm/memcontrol.c::mem_cgroup_migrate().
Convert it to use the existing local lock (event_lock) like the others.
@@ -30,3 +30,6 @@ index e5391afdfce3..c04403033aec 100644
}
DEFINE_STATIC_KEY_FALSE(memcg_sockets_enabled_key);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0118-mm-backing-dev-don-t-disable-IRQs-in-wb_congested_pu.patch b/debian/patches/features/all/rt/0118-mm-backing-dev-don-t-disable-IRQs-in-wb_congested_pu.patch
index 4245723..0cc5026 100644
--- a/debian/patches/features/all/rt/0118-mm-backing-dev-don-t-disable-IRQs-in-wb_congested_pu.patch
+++ b/debian/patches/features/all/rt/0118-mm-backing-dev-don-t-disable-IRQs-in-wb_congested_pu.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 5 Feb 2016 12:17:14 +0100
Subject: [PATCH 118/351] mm: backing-dev: don't disable IRQs in
wb_congested_put()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a17d84e073aa0299b5120c970377e0e9307d54c6
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1db9186b764fcb9d118fd92dcbb9a25132b2f9df
it triggers:
|BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:930
@@ -43,3 +43,6 @@ index 6ff2d7744223..b5a91dd53b5f 100644
return;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0119-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch b/debian/patches/features/all/rt/0119-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch
index 0f75ab6..1bd7258 100644
--- a/debian/patches/features/all/rt/0119-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch
+++ b/debian/patches/features/all/rt/0119-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch
@@ -1,7 +1,7 @@
From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Tue, 22 Mar 2016 11:16:09 +0100
Subject: [PATCH 119/351] mm/zsmalloc: copy with get_cpu_var() and locking
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7798e86bcba233f398def8640963ff6c51d63db4
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bce5cb98ee4ef4d69b62de9d7cd4ee2b6633642a
get_cpu_var() disables preemption and triggers a might_sleep() splat later.
This is replaced with get_locked_var().
@@ -17,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 74 insertions(+), 6 deletions(-)
diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
-index 1689bb58e0d1..e52a8cb6aa5a 100644
+index d3548c48369f..8894f0749d8d 100644
--- a/mm/zsmalloc.c
+++ b/mm/zsmalloc.c
@@ -53,6 +53,7 @@
@@ -197,3 +197,6 @@ index 1689bb58e0d1..e52a8cb6aa5a 100644
migrate_read_unlock(zspage);
unpin_tag(handle);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0120-radix-tree-use-local-locks.patch b/debian/patches/features/all/rt/0120-radix-tree-use-local-locks.patch
index 580bc8e..bb8628c 100644
--- a/debian/patches/features/all/rt/0120-radix-tree-use-local-locks.patch
+++ b/debian/patches/features/all/rt/0120-radix-tree-use-local-locks.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 25 Jan 2017 16:34:27 +0100
Subject: [PATCH 120/351] radix-tree: use local locks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=517b419dffa4cfa8c5582aeb4b8fc1326919742f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=06ca1a3df1e13ee377ceb9210f58be7bb1157477
The preload functionality uses per-CPU variables and preempt-disable to
ensure that it does not switch CPUs during its usage. This patch adds
@@ -127,3 +127,6 @@ index 8e6d552c40dd..741da5a77fd5 100644
/*
* The maximum index which can be stored in a radix tree
*/
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0121-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch b/debian/patches/features/all/rt/0121-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch
index f187389..3366550 100644
--- a/debian/patches/features/all/rt/0121-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch
+++ b/debian/patches/features/all/rt/0121-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 14 Jul 2015 14:26:34 +0200
Subject: [PATCH 121/351] panic: skip get_random_bytes for RT_FULL in
init_oops_id
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=24c72cccdf2073d49707d9ee7157e6a2611f53a1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a6b62d00b747c2e605e97759744725db62be67e7
Disable on -RT. If this is invoked from irq-context we will have problems
to acquire the sleeping lock.
@@ -28,3 +28,6 @@ index dbec387099b1..b67a4803ff2b 100644
oops_id++;
return 0;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0122-timers-Prepare-for-full-preemption.patch b/debian/patches/features/all/rt/0122-timers-Prepare-for-full-preemption.patch
index 9b6b6bf..a941d74 100644
--- a/debian/patches/features/all/rt/0122-timers-Prepare-for-full-preemption.patch
+++ b/debian/patches/features/all/rt/0122-timers-Prepare-for-full-preemption.patch
@@ -1,7 +1,7 @@
From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:29:34 -0500
Subject: [PATCH 122/351] timers: Prepare for full preemption
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=58e8faf5b24512964f01f7792831e9f596c489f0
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=40f847c09e9cdd2b3a8b6ccad002322c40aa25bf
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
@@ -16,7 +16,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
3 files changed, 48 insertions(+), 7 deletions(-)
diff --git a/include/linux/timer.h b/include/linux/timer.h
-index 51d601f192d4..83cea629efe1 100644
+index ec86e4e55ea3..8e5b680d1275 100644
--- a/include/linux/timer.h
+++ b/include/linux/timer.h
@@ -241,7 +241,7 @@ extern void add_timer(struct timer_list *timer);
@@ -59,7 +59,7 @@ index fe82f403abe4..46adabdde922 100644
}
/*
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
-index 0e9cb65c533c..b1d2919903cf 100644
+index f61ccaf457ae..fbfd67e6d4b6 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -195,6 +195,9 @@ EXPORT_SYMBOL(jiffies_64);
@@ -72,7 +72,7 @@ index 0e9cb65c533c..b1d2919903cf 100644
unsigned long clk;
unsigned long next_expiry;
unsigned int cpu;
-@@ -1170,6 +1173,33 @@ void add_timer_on(struct timer_list *timer, int cpu)
+@@ -1168,6 +1171,33 @@ void add_timer_on(struct timer_list *timer, int cpu)
}
EXPORT_SYMBOL_GPL(add_timer_on);
@@ -106,7 +106,7 @@ index 0e9cb65c533c..b1d2919903cf 100644
/**
* del_timer - deactive a timer.
* @timer: the timer to be deactivated
-@@ -1227,7 +1257,7 @@ int try_to_del_timer_sync(struct timer_list *timer)
+@@ -1225,7 +1255,7 @@ int try_to_del_timer_sync(struct timer_list *timer)
}
EXPORT_SYMBOL(try_to_del_timer_sync);
@@ -115,7 +115,7 @@ index 0e9cb65c533c..b1d2919903cf 100644
/**
* del_timer_sync - deactivate a timer and wait for the handler to finish.
* @timer: the timer to be deactivated
-@@ -1287,7 +1317,7 @@ int del_timer_sync(struct timer_list *timer)
+@@ -1285,7 +1315,7 @@ int del_timer_sync(struct timer_list *timer)
int ret = try_to_del_timer_sync(timer);
if (ret >= 0)
return ret;
@@ -124,7 +124,7 @@ index 0e9cb65c533c..b1d2919903cf 100644
}
}
EXPORT_SYMBOL(del_timer_sync);
-@@ -1352,13 +1382,16 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head)
+@@ -1350,13 +1380,16 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head)
fn = timer->function;
data = timer->data;
@@ -142,7 +142,7 @@ index 0e9cb65c533c..b1d2919903cf 100644
raw_spin_lock_irq(&base->lock);
}
}
-@@ -1659,8 +1692,8 @@ static inline void __run_timers(struct timer_base *base)
+@@ -1657,8 +1690,8 @@ static inline void __run_timers(struct timer_base *base)
while (levels--)
expire_timers(base, heads + levels);
}
@@ -152,7 +152,7 @@ index 0e9cb65c533c..b1d2919903cf 100644
}
/*
-@@ -1895,6 +1928,9 @@ static void __init init_timer_cpu(int cpu)
+@@ -1908,6 +1941,9 @@ static void __init init_timer_cpu(int cpu)
base->cpu = cpu;
raw_spin_lock_init(&base->lock);
base->clk = jiffies;
@@ -162,3 +162,6 @@ index 0e9cb65c533c..b1d2919903cf 100644
}
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0123-timer-delay-waking-softirqs-from-the-jiffy-tick.patch b/debian/patches/features/all/rt/0123-timer-delay-waking-softirqs-from-the-jiffy-tick.patch
index 8622213..bc69951 100644
--- a/debian/patches/features/all/rt/0123-timer-delay-waking-softirqs-from-the-jiffy-tick.patch
+++ b/debian/patches/features/all/rt/0123-timer-delay-waking-softirqs-from-the-jiffy-tick.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Fri, 21 Aug 2009 11:56:45 +0200
Subject: [PATCH 123/351] timer: delay waking softirqs from the jiffy tick
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2e93096c172bb0fb38d935a8d43f0eca8e258a12
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=634ce3aa74efeee590e63ab2ec594e276b271f52
People were complaining about broken balancing with the recent -rt
series.
@@ -57,10 +57,10 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
-index b1d2919903cf..d8e1c2c5397c 100644
+index fbfd67e6d4b6..cdb291bf5ec1 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
-@@ -1660,13 +1660,13 @@ void update_process_times(int user_tick)
+@@ -1658,13 +1658,13 @@ void update_process_times(int user_tick)
/* Note: this timer irq context must be accounted for as well. */
account_process_tick(p, user_tick);
@@ -75,3 +75,6 @@ index b1d2919903cf..d8e1c2c5397c 100644
run_posix_cpu_timers(p);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0125-hrtimer-enfore-64byte-alignment.patch b/debian/patches/features/all/rt/0125-hrtimer-enfore-64byte-alignment.patch
index 34f4367..6c3c3f5 100644
--- a/debian/patches/features/all/rt/0125-hrtimer-enfore-64byte-alignment.patch
+++ b/debian/patches/features/all/rt/0125-hrtimer-enfore-64byte-alignment.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 23 Dec 2015 20:57:41 +0100
Subject: [PATCH 125/351] hrtimer: enfore 64byte alignment
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0ee9a53037772577493da2ab5229410df6b258b5
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e5db6aef704a43dff79dcfba30fd2e6601c23b4a
The patch "hrtimer: Fixup hrtimer callback changes for preempt-rt" adds
a list_head expired to struct hrtimer_clock_base and with it we run into
@@ -28,3 +28,6 @@ index b71f4b720a03..b7c2d54af68e 100644
/**
* struct hrtimer_clock_base - the timer base for a specific clock
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0127-sched-deadline-dl_task_timer-has-to-be-irqsafe.patch b/debian/patches/features/all/rt/0127-sched-deadline-dl_task_timer-has-to-be-irqsafe.patch
index e8b05e7..216f6a4 100644
--- a/debian/patches/features/all/rt/0127-sched-deadline-dl_task_timer-has-to-be-irqsafe.patch
+++ b/debian/patches/features/all/rt/0127-sched-deadline-dl_task_timer-has-to-be-irqsafe.patch
@@ -1,8 +1,7 @@
-From faea6ad3f29e5328706c402375fa5ccc1652994a Mon Sep 17 00:00:00 2001
From: Juri Lelli <juri.lelli at gmail.com>
Date: Tue, 13 May 2014 15:30:20 +0200
Subject: [PATCH 127/351] sched/deadline: dl_task_timer has to be irqsafe
-Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.9/older/patches-4.9.68-rt60.tar.xz
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=479b0ead94358f504f08e5bfd1ea46b229e0f239
As for rt_period_timer, dl_task_timer has to be irqsafe.
@@ -12,9 +11,11 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
kernel/sched/deadline.c | 1 +
1 file changed, 1 insertion(+)
+diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
+index df5c32a0c6ed..c77fd444dc3c 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
-@@ -693,6 +693,7 @@ void init_dl_task_timer(struct sched_dl_
+@@ -693,6 +693,7 @@ void init_dl_task_timer(struct sched_dl_entity *dl_se)
hrtimer_init(timer, CLOCK_MONOTONIC, HRTIMER_MODE_REL);
timer->function = dl_task_timer;
@@ -22,3 +23,6 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
}
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0128-timer-fd-Prevent-live-lock.patch b/debian/patches/features/all/rt/0128-timer-fd-Prevent-live-lock.patch
index 888d4c8..2b3884b 100644
--- a/debian/patches/features/all/rt/0128-timer-fd-Prevent-live-lock.patch
+++ b/debian/patches/features/all/rt/0128-timer-fd-Prevent-live-lock.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 25 Jan 2012 11:08:40 +0100
Subject: [PATCH 128/351] timer-fd: Prevent live lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=09cbaac7b189e3cbd77bdbc58ca7ba4e08843dc1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9918500bfd353e4e332e7159f70c61f254d4caa0
If hrtimer_try_to_cancel() requires a retry, then depending on the
priority setting te retry loop might prevent timer callback completion
@@ -30,3 +30,6 @@ index ab8dd1538381..5580853f57dd 100644
}
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0129-tick-broadcast-Make-broadcast-hrtimer-irqsafe.patch b/debian/patches/features/all/rt/0129-tick-broadcast-Make-broadcast-hrtimer-irqsafe.patch
index 49a5ff4..03207a4 100644
--- a/debian/patches/features/all/rt/0129-tick-broadcast-Make-broadcast-hrtimer-irqsafe.patch
+++ b/debian/patches/features/all/rt/0129-tick-broadcast-Make-broadcast-hrtimer-irqsafe.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 27 Feb 2016 10:47:10 +0100
Subject: [PATCH 129/351] tick/broadcast: Make broadcast hrtimer irqsafe
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0157f3118949c6c387a7d822011439db3b1fab69
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1d4d366e8426d42cc8d3e9978f7023be19028b07
Otherwise we end up with the following:
@@ -58,3 +58,6 @@ index 690b797f522e..fe8ba1619879 100644
+ bctimer.irqsafe = true;
clockevents_register_device(&ce_broadcast_hrtimer);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0130-timer-hrtimer-check-properly-for-a-running-timer.patch b/debian/patches/features/all/rt/0130-timer-hrtimer-check-properly-for-a-running-timer.patch
index 1c2fad0..94cbf35 100644
--- a/debian/patches/features/all/rt/0130-timer-hrtimer-check-properly-for-a-running-timer.patch
+++ b/debian/patches/features/all/rt/0130-timer-hrtimer-check-properly-for-a-running-timer.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 1 Mar 2017 16:30:49 +0100
Subject: [PATCH 130/351] timer/hrtimer: check properly for a running timer
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1c819369269ad7eecbd43c23d68ca421ce2d380d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f29d4235e787a89951fe9614a47ade8b34f6ed15
hrtimer_callback_running() checks only whether a timmer is running on a
CPU in hardirq-context. This is okay for !RT. For RT environment we move
@@ -34,3 +34,6 @@ index 65d0671f20b4..a34e10b55cde 100644
}
/* Forward a hrtimer so it expires after now: */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0131-posix-timers-Thread-posix-cpu-timers-on-rt.patch b/debian/patches/features/all/rt/0131-posix-timers-Thread-posix-cpu-timers-on-rt.patch
index bf20d73..7a5fb01 100644
--- a/debian/patches/features/all/rt/0131-posix-timers-Thread-posix-cpu-timers-on-rt.patch
+++ b/debian/patches/features/all/rt/0131-posix-timers-Thread-posix-cpu-timers-on-rt.patch
@@ -1,7 +1,7 @@
From: John Stultz <johnstul at us.ibm.com>
Date: Fri, 3 Jul 2009 08:29:58 -0500
Subject: [PATCH 131/351] posix-timers: Thread posix-cpu-timers on -rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=87a99aaca3bf8ea426b049f38ba8451115b4691b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=445d2175788f295bf923f8bae167ffc09f1e74b1
posix-cpu-timer code takes non -rt safe locks in hard irq
context. Move it to a thread.
@@ -57,10 +57,10 @@ index 040ae135ecb0..b6be669490e4 100644
/* process credentials */
const struct cred __rcu *ptracer_cred; /* Tracer's credentials at attach */
diff --git a/kernel/fork.c b/kernel/fork.c
-index c508b761e494..bc418dcfcda1 100644
+index fca238739495..2572a2547f3e 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
-@@ -1436,6 +1436,9 @@ static void rt_mutex_init_task(struct task_struct *p)
+@@ -1442,6 +1442,9 @@ static void rt_mutex_init_task(struct task_struct *p)
*/
static void posix_cpu_timers_init(struct task_struct *tsk)
{
@@ -307,3 +307,6 @@ index 39008d78927a..633f4eaca9e7 100644
/*
* Set one of the process-wide special case CPU timers or RLIMIT_CPU.
* The tsk->sighand->siglock must be held by the caller.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0132-sched-Move-task_struct-cleanup-to-RCU.patch b/debian/patches/features/all/rt/0132-sched-Move-task_struct-cleanup-to-RCU.patch
index d038f74..1ba0542 100644
--- a/debian/patches/features/all/rt/0132-sched-Move-task_struct-cleanup-to-RCU.patch
+++ b/debian/patches/features/all/rt/0132-sched-Move-task_struct-cleanup-to-RCU.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 31 May 2011 16:59:16 +0200
Subject: [PATCH 132/351] sched: Move task_struct cleanup to RCU
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=398c7aa901a1cc203163a2e03557120cb9987cb3
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=211d7d106577d939aa490fdbd9547cdea83a4d36
__put_task_struct() does quite some expensive work. We don't want to
burden random tasks with that.
@@ -51,10 +51,10 @@ index b6be669490e4..a1363ac435ce 100644
struct task_struct *task_rcu_dereference(struct task_struct **ptask);
struct task_struct *try_get_task_struct(struct task_struct **ptask);
diff --git a/kernel/fork.c b/kernel/fork.c
-index bc418dcfcda1..a9f95368ca66 100644
+index 2572a2547f3e..08a834f25b82 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
-@@ -376,7 +376,9 @@ static inline void put_signal_struct(struct signal_struct *sig)
+@@ -378,7 +378,9 @@ static inline void put_signal_struct(struct signal_struct *sig)
if (atomic_dec_and_test(&sig->sigcnt))
free_signal_struct(sig);
}
@@ -65,7 +65,7 @@ index bc418dcfcda1..a9f95368ca66 100644
void __put_task_struct(struct task_struct *tsk)
{
WARN_ON(!tsk->exit_state);
-@@ -393,7 +395,18 @@ void __put_task_struct(struct task_struct *tsk)
+@@ -395,7 +397,18 @@ void __put_task_struct(struct task_struct *tsk)
if (!profile_handoff_task(tsk))
free_task(tsk);
}
@@ -84,3 +84,6 @@ index bc418dcfcda1..a9f95368ca66 100644
void __init __weak arch_task_cache_init(void) { }
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0133-sched-Limit-the-number-of-task-migrations-per-batch.patch b/debian/patches/features/all/rt/0133-sched-Limit-the-number-of-task-migrations-per-batch.patch
index 091d1ab..c1e9325 100644
--- a/debian/patches/features/all/rt/0133-sched-Limit-the-number-of-task-migrations-per-batch.patch
+++ b/debian/patches/features/all/rt/0133-sched-Limit-the-number-of-task-migrations-per-batch.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 6 Jun 2011 12:12:51 +0200
Subject: [PATCH 133/351] sched: Limit the number of task migrations per batch
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7d0e18261572b79f5410bb3fcdc6579674f11c82
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f8eb2be63f75f9b7b4090ddae4792a8b1fa883ab
Put an upper limit on the number of tasks which are migrated per batch
to avoid large latencies.
@@ -27,3 +27,6 @@ index 7944079a4d71..b3515090f4fe 100644
/*
* period over which we average the RT time consumption, measured
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0134-sched-Move-mmdrop-to-RCU-on-RT.patch b/debian/patches/features/all/rt/0134-sched-Move-mmdrop-to-RCU-on-RT.patch
index d2fb8b2..43359e8 100644
--- a/debian/patches/features/all/rt/0134-sched-Move-mmdrop-to-RCU-on-RT.patch
+++ b/debian/patches/features/all/rt/0134-sched-Move-mmdrop-to-RCU-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 6 Jun 2011 12:20:33 +0200
Subject: [PATCH 134/351] sched: Move mmdrop to RCU on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0cb39bea677cad4b1e453add734eb9fda56a4669
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=87f8c415569dcfe9cb98074c69d3ef723a25c837
Takes sleeping locks and calls into the memory allocator, so nothing
we want to do in task switch and oder atomic contexts.
@@ -59,10 +59,10 @@ index a1363ac435ce..34c29a31f94b 100644
{
struct mm_struct *mm = container_of(work, struct mm_struct, async_put_work);
diff --git a/kernel/fork.c b/kernel/fork.c
-index a9f95368ca66..eac2a145ccb8 100644
+index 08a834f25b82..613a26994992 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
-@@ -874,6 +874,19 @@ void __mmdrop(struct mm_struct *mm)
+@@ -880,6 +880,19 @@ void __mmdrop(struct mm_struct *mm)
}
EXPORT_SYMBOL_GPL(__mmdrop);
@@ -134,3 +134,6 @@ index b3515090f4fe..a49d6550d483 100644
return 0;
}
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0135-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch b/debian/patches/features/all/rt/0135-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch
index fbb0b40..c113adb 100644
--- a/debian/patches/features/all/rt/0135-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch
+++ b/debian/patches/features/all/rt/0135-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 21 Nov 2016 19:31:08 +0100
Subject: [PATCH 135/351] kernel/sched: move stack + kprobe clean up to
__put_task_struct()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=11bd4ba93c99d025822d30eeb30938770e23e4f1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e1ede5aeb9189edb708ee5ad29f9591bd6fe436f
There is no need to free the stack before the task struct. This also
comes handy on -RT because we can't free memory in preempt disabled
@@ -16,10 +16,10 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
2 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/kernel/fork.c b/kernel/fork.c
-index eac2a145ccb8..11fa53573d26 100644
+index 613a26994992..5bcb777b6913 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
-@@ -76,6 +76,7 @@
+@@ -77,6 +77,7 @@
#include <linux/compiler.h>
#include <linux/sysctl.h>
#include <linux/kcov.h>
@@ -27,7 +27,7 @@ index eac2a145ccb8..11fa53573d26 100644
#include <asm/pgtable.h>
#include <asm/pgalloc.h>
-@@ -385,6 +386,15 @@ void __put_task_struct(struct task_struct *tsk)
+@@ -387,6 +388,15 @@ void __put_task_struct(struct task_struct *tsk)
WARN_ON(atomic_read(&tsk->usage));
WARN_ON(tsk == current);
@@ -63,3 +63,6 @@ index a49d6550d483..c330f971d6db 100644
put_task_struct(prev);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0136-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch b/debian/patches/features/all/rt/0136-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch
index 44a8054..d077d91 100644
--- a/debian/patches/features/all/rt/0136-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch
+++ b/debian/patches/features/all/rt/0136-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 25 Jun 2011 09:21:04 +0200
Subject: [PATCH 136/351] sched: Add saved_state for tasks blocked on sleeping
locks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ebf6df019a8d4889eb2c07e7cd7e6d3739652b28
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=89749d46a961a5ae02f6e66a09c29272c97c5675
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
@@ -99,3 +99,6 @@ index cff985feb6e7..5dc95852c984 100644
/*
* To aid in avoiding the subversion of "niceness" due to uneven distribution
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0137-sched-Prevent-task-state-corruption-by-spurious-lock.patch b/debian/patches/features/all/rt/0137-sched-Prevent-task-state-corruption-by-spurious-lock.patch
index 275e71f..4e3a42a 100644
--- a/debian/patches/features/all/rt/0137-sched-Prevent-task-state-corruption-by-spurious-lock.patch
+++ b/debian/patches/features/all/rt/0137-sched-Prevent-task-state-corruption-by-spurious-lock.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 6 Jun 2017 14:20:37 +0200
Subject: [PATCH 137/351] sched: Prevent task state corruption by spurious lock
wakeup
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=658d8741e55b6e8c3c9975be4b5e11a22728d976
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f619544f1a6ec65ce703e650f62ae82db9a360a8
Mathias and others reported GDB failures on RT.
@@ -79,3 +79,6 @@ index 109e6fbaf970..7769837b3926 100644
}
int wake_up_state(struct task_struct *p, unsigned int state)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0138-sched-Remove-TASK_ALL.patch b/debian/patches/features/all/rt/0138-sched-Remove-TASK_ALL.patch
index 79148ca..12b4640 100644
--- a/debian/patches/features/all/rt/0138-sched-Remove-TASK_ALL.patch
+++ b/debian/patches/features/all/rt/0138-sched-Remove-TASK_ALL.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 7 Jun 2017 10:12:45 +0200
Subject: [PATCH 138/351] sched: Remove TASK_ALL
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=cf1173b3a32909b0af486c36a7475898d42afa2a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4f8aff38de5d23a7b3b2f291455dd7c1fe37602b
It's unused:
@@ -30,3 +30,6 @@ index aa26cea7618f..7deb4bff4e06 100644
/* get_task_state() */
#define TASK_REPORT (TASK_RUNNING | TASK_INTERRUPTIBLE | \
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0139-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch b/debian/patches/features/all/rt/0139-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch
index a678349..9dcf780 100644
--- a/debian/patches/features/all/rt/0139-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch
+++ b/debian/patches/features/all/rt/0139-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 7 Jun 2011 09:19:06 +0200
Subject: [PATCH 139/351] sched: Do not account rcu_preempt_depth on RT in
might_sleep()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f1c0df98cd4f4b366a9a07df12ea01de3f976d32
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ee56a76b24dc7648b13f4e9165f77f44d8c56b81
RT changes the rcu_preempt_depth semantics, so we cannot check for it
in might_sleep().
@@ -51,3 +51,6 @@ index 7769837b3926..91d3f785d764 100644
return (nested == preempt_offset);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0140-sched-Take-RT-softirq-semantics-into-account-in-cond.patch b/debian/patches/features/all/rt/0140-sched-Take-RT-softirq-semantics-into-account-in-cond.patch
index 6c9f689..a52ec1f 100644
--- a/debian/patches/features/all/rt/0140-sched-Take-RT-softirq-semantics-into-account-in-cond.patch
+++ b/debian/patches/features/all/rt/0140-sched-Take-RT-softirq-semantics-into-account-in-cond.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 14 Jul 2011 09:56:44 +0200
Subject: [PATCH 140/351] sched: Take RT softirq semantics into account in
cond_resched()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3b58221ada1e9ec17cb357a20edbc7016bb8187c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d90d18ca9c6c80c0d348e1d9d88b6c3f168fd6a5
The softirq semantics work different on -RT. There is no SOFTIRQ_MASK in
the preemption counter which leads to the BUG_ON() statement in
@@ -56,3 +56,6 @@ index 91d3f785d764..ced1266c7ef7 100644
/**
* yield - yield the current processor to other threads.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0141-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch b/debian/patches/features/all/rt/0141-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch
index 6ced4cc..374624a 100644
--- a/debian/patches/features/all/rt/0141-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch
+++ b/debian/patches/features/all/rt/0141-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 17 Jul 2011 22:51:33 +0200
Subject: [PATCH 141/351] sched: Use the proper LOCK_OFFSET for cond_resched()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9b9e93d75f16574e5fc1b9259dfc0c5dd99d250d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e04b37b1010453bee30340e24bb5f1d2ec6ecf9d
RT does not increment preempt count when a 'sleeping' spinlock is
locked. Update PREEMPT_LOCK_OFFSET for that case.
@@ -27,3 +27,6 @@ index 64f1488df183..f17045be9fbf 100644
/*
* The preempt_count offset needed for things like:
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0142-sched-Disable-TTWU_QUEUE-on-RT.patch b/debian/patches/features/all/rt/0142-sched-Disable-TTWU_QUEUE-on-RT.patch
index f2b927e..42cf98d 100644
--- a/debian/patches/features/all/rt/0142-sched-Disable-TTWU_QUEUE-on-RT.patch
+++ b/debian/patches/features/all/rt/0142-sched-Disable-TTWU_QUEUE-on-RT.patch
@@ -1,8 +1,7 @@
-From d828c07c3abb7528cd1e50c549dd79b89184ea93 Mon Sep 17 00:00:00 2001
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 13 Sep 2011 16:42:35 +0200
Subject: [PATCH 142/351] sched: Disable TTWU_QUEUE on RT
-Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.9/older/patches-4.9.68-rt60.tar.xz
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=94fb6eca39d3d7cea515939b9a5e23ac9faa5228
The queued remote wakeup mechanism can introduce rather large
latencies if the number of migrated tasks is high. Disable it for RT.
@@ -12,6 +11,8 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
kernel/sched/features.h | 5 +++++
1 file changed, 5 insertions(+)
+diff --git a/kernel/sched/features.h b/kernel/sched/features.h
+index 1b3c8189b286..852cfc5bb77b 100644
--- a/kernel/sched/features.h
+++ b/kernel/sched/features.h
@@ -45,11 +45,16 @@ SCHED_FEAT(LB_BIAS, true)
@@ -31,3 +32,6 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
/*
* When doing wakeups, attempt to limit superfluous scans of the LLC domain.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0143-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch b/debian/patches/features/all/rt/0143-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch
index 0ea3aaf..3662318 100644
--- a/debian/patches/features/all/rt/0143-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch
+++ b/debian/patches/features/all/rt/0143-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 18 Jul 2011 17:03:52 +0200
Subject: [PATCH 143/351] sched: Disable CONFIG_RT_GROUP_SCHED on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7df0f49b4d4b6f407913aa97ff93db807d95bdb9
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6c924354545f48721334322784796e9e772cb633
Carsten reported problems when running:
@@ -29,3 +29,6 @@ index 333d2b269208..1762f2521ebc 100644
default n
help
This feature lets you explicitly allocate real CPU bandwidth
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0144-sched-ttwu-Return-success-when-only-changing-the-sav.patch b/debian/patches/features/all/rt/0144-sched-ttwu-Return-success-when-only-changing-the-sav.patch
index 6d9266b..3ccf791 100644
--- a/debian/patches/features/all/rt/0144-sched-ttwu-Return-success-when-only-changing-the-sav.patch
+++ b/debian/patches/features/all/rt/0144-sched-ttwu-Return-success-when-only-changing-the-sav.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 13 Dec 2011 21:42:19 +0100
Subject: [PATCH 144/351] sched: ttwu: Return success when only changing the
saved_state value
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9362fbc0be233c4a42fec759440431694e18bcb9
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=faa61fb49272cfb8e93ebd4804e88611a5ff75df
When a task blocks on a rt lock, it saves the current state in
p->saved_state, so a lock related wake up will not destroy the
@@ -35,3 +35,6 @@ index ced1266c7ef7..7451d4e3d92f 100644
}
goto out;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0145-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch b/debian/patches/features/all/rt/0145-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch
index 9251dd3..e7a8688 100644
--- a/debian/patches/features/all/rt/0145-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch
+++ b/debian/patches/features/all/rt/0145-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch
@@ -2,7 +2,7 @@ From: Steven Rostedt <rostedt at goodmis.org>
Date: Mon, 18 Mar 2013 15:12:49 -0400
Subject: [PATCH 145/351] sched/workqueue: Only wake up idle workers if not
blocked on sleeping spin lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3409c4cdfe60fb58ee3a7dc9a686ca73d1dc34fd
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=faa945788918d0aeadd195969ceceefcc309d132
In -rt, most spin_locks() turn into mutexes. One of these spin_lock
conversions is performed on the workqueue gcwq->lock. When the idle
@@ -39,3 +39,6 @@ index 7451d4e3d92f..e506ecc2f962 100644
struct task_struct *to_wakeup;
to_wakeup = wq_worker_sleeping(prev);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0146-stop_machine-convert-stop_machine_run-to-PREEMPT_RT.patch b/debian/patches/features/all/rt/0146-stop_machine-convert-stop_machine_run-to-PREEMPT_RT.patch
index 4c86edf..4b3d532 100644
--- a/debian/patches/features/all/rt/0146-stop_machine-convert-stop_machine_run-to-PREEMPT_RT.patch
+++ b/debian/patches/features/all/rt/0146-stop_machine-convert-stop_machine_run-to-PREEMPT_RT.patch
@@ -2,7 +2,7 @@ From: Ingo Molnar <mingo at elte.hu>
Date: Fri, 3 Jul 2009 08:30:27 -0500
Subject: [PATCH 146/351] stop_machine: convert stop_machine_run() to
PREEMPT_RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=070c022891528b1d372df4a8fec0d1697dc39a72
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b3669c804d4c03313c09bc469edf05768b591a73
Instead of playing with non-preemption, introduce explicit
startup serialization. This is more robust and cleaner as
@@ -19,7 +19,7 @@ diff --git a/kernel/stop_machine.c b/kernel/stop_machine.c
index ec9ab2f01489..56d142c31c6e 100644
--- a/kernel/stop_machine.c
+++ b/kernel/stop_machine.c
-@@ -475,6 +475,16 @@ static void cpu_stopper_thread(unsigned int cpu)
+@@ -475,6 +475,16 @@ repeat:
struct cpu_stop_done *done = work->done;
int ret;
@@ -36,3 +36,6 @@ index ec9ab2f01489..56d142c31c6e 100644
/* cpu stop callbacks must not sleep, make in_atomic() == T */
preempt_count_inc();
ret = fn(arg);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0147-stop_machine-Use-raw-spinlocks.patch b/debian/patches/features/all/rt/0147-stop_machine-Use-raw-spinlocks.patch
index 849cf0c..da908dd 100644
--- a/debian/patches/features/all/rt/0147-stop_machine-Use-raw-spinlocks.patch
+++ b/debian/patches/features/all/rt/0147-stop_machine-Use-raw-spinlocks.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 29 Jun 2011 11:01:51 +0200
Subject: [PATCH 147/351] stop_machine: Use raw spinlocks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f05d650bc2b5462a7035cb23f80e89b3daba9d7e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0d0f119725304cedcc89a2c577345794a75a7101
Use raw-locks in stomp_machine() to allow locking in irq-off regions.
@@ -51,7 +51,7 @@ index 56d142c31c6e..8b89dbedeaff 100644
err = -ENOENT;
if (!stopper1->enabled || !stopper2->enabled)
-@@ -255,8 +255,8 @@ static int cpu_stop_queue_two_works(int cpu1, struct cpu_stop_work *work1,
+@@ -255,8 +255,8 @@ retry:
__cpu_stop_queue_work(stopper1, work1);
__cpu_stop_queue_work(stopper2, work2);
unlock:
@@ -90,7 +90,7 @@ index 56d142c31c6e..8b89dbedeaff 100644
if (work) {
cpu_stop_fn_t fn = work->fn;
-@@ -475,15 +475,7 @@ static void cpu_stopper_thread(unsigned int cpu)
+@@ -475,15 +475,7 @@ repeat:
struct cpu_stop_done *done = work->done;
int ret;
@@ -116,3 +116,6 @@ index 56d142c31c6e..8b89dbedeaff 100644
INIT_LIST_HEAD(&stopper->works);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0148-hotplug-Lightweight-get-online-cpus.patch b/debian/patches/features/all/rt/0148-hotplug-Lightweight-get-online-cpus.patch
index 2547915..958ed1e 100644
--- a/debian/patches/features/all/rt/0148-hotplug-Lightweight-get-online-cpus.patch
+++ b/debian/patches/features/all/rt/0148-hotplug-Lightweight-get-online-cpus.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 15 Jun 2011 12:36:06 +0200
Subject: [PATCH 148/351] hotplug: Lightweight get online cpus
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ffdf8c8221b954d0a23233c03c0661eef425cc75
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=02ae35952fc21dc5fe58fb990b5cba72285ffdb5
get_online_cpus() is a heavy weight function which involves a global
mutex. migrate_disable() wants a simpler construct which prevents only
@@ -50,7 +50,7 @@ index dcfcdd563f69..5e52d28c20c1 100644
#define __hotcpu_notifier(fn, pri) do { (void)(fn); } while (0)
/* These aren't inline functions due to a GCC bug. */
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index 164b86a8b4e2..759dd49b28f6 100644
+index dac06acbae9d..c320c7464472 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -239,6 +239,100 @@ static struct {
@@ -200,3 +200,6 @@ index 164b86a8b4e2..759dd49b28f6 100644
cpu_hotplug_done();
/* This post dead nonsense must die */
if (!ret && hasdied)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0149-hotplug-sync_unplug-No-n-in-task-name.patch b/debian/patches/features/all/rt/0149-hotplug-sync_unplug-No-n-in-task-name.patch
index 64be3aa..9702fcd 100644
--- a/debian/patches/features/all/rt/0149-hotplug-sync_unplug-No-n-in-task-name.patch
+++ b/debian/patches/features/all/rt/0149-hotplug-sync_unplug-No-n-in-task-name.patch
@@ -1,7 +1,7 @@
From: Yong Zhang <yong.zhang0 at gmail.com>
Date: Sun, 16 Oct 2011 18:56:43 +0800
Subject: [PATCH 149/351] hotplug: sync_unplug: No "\n" in task name
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6493cded1d79a620e6268536736dfd62cf034b62
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4c6b9f996e2ba5e0559b9cf679718828958e8cf0
Otherwise the output will look a little odd.
@@ -13,7 +13,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index 759dd49b28f6..a5e711089d0a 100644
+index c320c7464472..129861b6ec00 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -318,7 +318,7 @@ static int cpu_unplug_begin(unsigned int cpu)
@@ -25,3 +25,6 @@ index 759dd49b28f6..a5e711089d0a 100644
if (IS_ERR(tsk))
return (PTR_ERR(tsk));
kthread_bind(tsk, cpu);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0150-hotplug-Reread-hotplug_pcp-on-pin_current_cpu-retry.patch b/debian/patches/features/all/rt/0150-hotplug-Reread-hotplug_pcp-on-pin_current_cpu-retry.patch
index 7ae239c..4564a3b 100644
--- a/debian/patches/features/all/rt/0150-hotplug-Reread-hotplug_pcp-on-pin_current_cpu-retry.patch
+++ b/debian/patches/features/all/rt/0150-hotplug-Reread-hotplug_pcp-on-pin_current_cpu-retry.patch
@@ -2,7 +2,7 @@ From: Yong Zhang <yong.zhang0 at gmail.com>
Date: Thu, 28 Jul 2011 11:16:00 +0800
Subject: [PATCH 150/351] hotplug: Reread hotplug_pcp on pin_current_cpu()
retry
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=eeeb91e6975f99b0b071aefabc1be67d01cfefd9
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=dd4601518e58ab1ff942179476e06440e30db9fe
When retry happens, it's likely that the task has been migrated to
another cpu (except unplug failed), but it still derefernces the
@@ -20,7 +20,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index a5e711089d0a..41d6cf1215c7 100644
+index 129861b6ec00..40e5c3af35d3 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -257,9 +257,11 @@ static DEFINE_PER_CPU(struct hotplug_pcp, hotplug_pcp);
@@ -36,3 +36,6 @@ index a5e711089d0a..41d6cf1215c7 100644
if (!hp->unplug || hp->refcount || preempt_count() > 1 ||
hp->unplug == current) {
hp->refcount++;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0151-trace-Add-migrate-disabled-counter-to-tracing-output.patch b/debian/patches/features/all/rt/0151-trace-Add-migrate-disabled-counter-to-tracing-output.patch
index 045c5eb..1815832 100644
--- a/debian/patches/features/all/rt/0151-trace-Add-migrate-disabled-counter-to-tracing-output.patch
+++ b/debian/patches/features/all/rt/0151-trace-Add-migrate-disabled-counter-to-tracing-output.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 17 Jul 2011 21:56:42 +0200
Subject: [PATCH 151/351] trace: Add migrate-disabled counter to tracing output
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=705dc0dece3c0e636f8eaa1e1a1707ca92e62e4d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4b1fcde90088f0133e0853e276df7dd49ba6e582
Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
---
@@ -25,7 +25,7 @@ index ba57266d9e80..4f8bb9c8eed8 100644
#define TRACE_EVENT_TYPE_MAX \
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
-index c1e50cc0d7b0..2b7caaae94a2 100644
+index 15b02645ce8b..038f9b758913 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1909,6 +1909,8 @@ tracing_generic_entry_update(struct trace_entry *entry, unsigned long flags,
@@ -80,3 +80,6 @@ index 3fc20422c166..badf130635f1 100644
return !trace_seq_has_overflowed(s);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0152-hotplug-Use-migrate-disable-on-unplug.patch b/debian/patches/features/all/rt/0152-hotplug-Use-migrate-disable-on-unplug.patch
index 52c0c86..ea3b3a4 100644
--- a/debian/patches/features/all/rt/0152-hotplug-Use-migrate-disable-on-unplug.patch
+++ b/debian/patches/features/all/rt/0152-hotplug-Use-migrate-disable-on-unplug.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 17 Jul 2011 19:35:29 +0200
Subject: [PATCH 152/351] hotplug: Use migrate disable on unplug
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=12843abad53a10e287c30dd8484239dae3aa56e3
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=97cf60c4289437df6310e6b2cfb091233bf431c3
Migration needs to be disabled accross the unplug handling to make
sure that the unplug thread is off the unplugged cpu.
@@ -12,7 +12,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index 41d6cf1215c7..4b8f59bee8d9 100644
+index 40e5c3af35d3..7c28baf1a9d6 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -1001,14 +1001,13 @@ static int __ref _cpu_down(unsigned int cpu, int tasks_frozen,
@@ -32,7 +32,7 @@ index 41d6cf1215c7..4b8f59bee8d9 100644
cpu_hotplug_begin();
ret = cpu_unplug_begin(cpu);
-@@ -1057,6 +1056,7 @@ static int __ref _cpu_down(unsigned int cpu, int tasks_frozen,
+@@ -1057,6 +1056,7 @@ out:
cpu_unplug_done(cpu);
out_cancel:
cpu_hotplug_done();
@@ -40,3 +40,6 @@ index 41d6cf1215c7..4b8f59bee8d9 100644
/* This post dead nonsense must die */
if (!ret && hasdied)
cpu_notify_nofail(CPU_POST_DEAD, cpu);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0153-lockdep-Make-it-RT-aware.patch b/debian/patches/features/all/rt/0153-lockdep-Make-it-RT-aware.patch
index 725a54c..5f1d96b 100644
--- a/debian/patches/features/all/rt/0153-lockdep-Make-it-RT-aware.patch
+++ b/debian/patches/features/all/rt/0153-lockdep-Make-it-RT-aware.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 17 Jul 2011 18:51:23 +0200
Subject: [PATCH 153/351] lockdep: Make it RT aware
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a7893de1f67bdaa79d7925d798ae8e5489a39e8b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2e0f463469a0f73e75adb200388a14010111c47c
teach lockdep that we don't really do softirqs on -RT.
@@ -61,3 +61,6 @@ index 43f06eda837a..79f8e00e802e 100644
if (!debug_locks)
print_irqtrace_events(current);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0154-locking-Disable-spin-on-owner-for-RT.patch b/debian/patches/features/all/rt/0154-locking-Disable-spin-on-owner-for-RT.patch
index bc55017..3678d79 100644
--- a/debian/patches/features/all/rt/0154-locking-Disable-spin-on-owner-for-RT.patch
+++ b/debian/patches/features/all/rt/0154-locking-Disable-spin-on-owner-for-RT.patch
@@ -4,7 +4,7 @@ Subject: [PATCH 154/351] locking: Disable spin on owner for RT
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2b09cc96af1c7a085bd7a25485a9afda87dfcffd
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7bcfa0eb5edc3a14a845a443d34ad088d6e0fcb5
Drop spin on owner for mutex / rwsem. We are most likely not using it
but…
@@ -32,3 +32,6 @@ index ebdb0043203a..b9e6aa7e5aa6 100644
config LOCK_SPIN_ON_OWNER
def_bool y
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0155-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch b/debian/patches/features/all/rt/0155-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch
index 05bbc50..773c19f 100644
--- a/debian/patches/features/all/rt/0155-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch
+++ b/debian/patches/features/all/rt/0155-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch
@@ -2,7 +2,7 @@ From: Ingo Molnar <mingo at elte.hu>
Date: Tue, 29 Nov 2011 20:18:22 -0500
Subject: [PATCH 155/351] tasklet: Prevent tasklets from going into infinite
spin in RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fb173301a3894851776fb2a84749d5bc5d48440e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=93a4bebb65f1fda7710e27f8d8794f64ea8dabfb
When CONFIG_PREEMPT_RT_FULL is enabled, tasklets run as threads,
and spinlocks turn are mutexes. But this can cause issues with
@@ -394,3 +394,6 @@ index 744fa611cae0..8669000c2aa3 100644
static int ksoftirqd_should_run(unsigned int cpu)
{
return local_softirq_pending();
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0156-softirq-Check-preemption-after-reenabling-interrupts.patch b/debian/patches/features/all/rt/0156-softirq-Check-preemption-after-reenabling-interrupts.patch
index 701e3ef..94e6f20 100644
--- a/debian/patches/features/all/rt/0156-softirq-Check-preemption-after-reenabling-interrupts.patch
+++ b/debian/patches/features/all/rt/0156-softirq-Check-preemption-after-reenabling-interrupts.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 13 Nov 2011 17:17:09 +0100
Subject: [PATCH 156/351] softirq: Check preemption after reenabling interrupts
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=71f27909ecca9a96baa626477b0e5b8d4fcef21d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3dab639adc2fed7cce10b9f41ac47764b5c8745c
raise_softirq_irqoff() disables interrupts and wakes the softirq
daemon, but after reenabling interrupts there is no preemption check,
@@ -40,7 +40,7 @@ index 06cf9807f49a..c40342643ca0 100644
return 0;
}
-@@ -141,6 +143,7 @@ void __blk_complete_request(struct request *req)
+@@ -141,6 +143,7 @@ do_local:
goto do_local;
local_irq_restore(flags);
@@ -116,10 +116,10 @@ index 1d6565e81030..b23a79761df7 100644
return 0;
}
diff --git a/net/core/dev.c b/net/core/dev.c
-index c37891828e4e..a275a8c147e7 100644
+index 09007a71c8dd..88bc38b1eecc 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
-@@ -2286,6 +2286,7 @@ static void __netif_reschedule(struct Qdisc *q)
+@@ -2287,6 +2287,7 @@ static void __netif_reschedule(struct Qdisc *q)
sd->output_queue_tailp = &q->next_sched;
raise_softirq_irqoff(NET_TX_SOFTIRQ);
local_irq_restore(flags);
@@ -127,7 +127,7 @@ index c37891828e4e..a275a8c147e7 100644
}
void __netif_schedule(struct Qdisc *q)
-@@ -2370,6 +2371,7 @@ void __dev_kfree_skb_irq(struct sk_buff *skb, enum skb_free_reason reason)
+@@ -2371,6 +2372,7 @@ void __dev_kfree_skb_irq(struct sk_buff *skb, enum skb_free_reason reason)
__this_cpu_write(softnet_data.completion_queue, skb);
raise_softirq_irqoff(NET_TX_SOFTIRQ);
local_irq_restore(flags);
@@ -135,7 +135,7 @@ index c37891828e4e..a275a8c147e7 100644
}
EXPORT_SYMBOL(__dev_kfree_skb_irq);
-@@ -3796,6 +3798,7 @@ static int enqueue_to_backlog(struct sk_buff *skb, int cpu,
+@@ -3797,6 +3799,7 @@ drop:
rps_unlock(sd);
local_irq_restore(flags);
@@ -143,7 +143,7 @@ index c37891828e4e..a275a8c147e7 100644
atomic_long_inc(&skb->dev->rx_dropped);
kfree_skb(skb);
-@@ -4852,6 +4855,7 @@ static void net_rps_action_and_irq_enable(struct softnet_data *sd)
+@@ -4853,6 +4856,7 @@ static void net_rps_action_and_irq_enable(struct softnet_data *sd)
sd->rps_ipi_list = NULL;
local_irq_enable();
@@ -151,7 +151,7 @@ index c37891828e4e..a275a8c147e7 100644
/* Send pending IPI's to kick RPS processing on remote cpus. */
while (remsd) {
-@@ -4865,6 +4869,7 @@ static void net_rps_action_and_irq_enable(struct softnet_data *sd)
+@@ -4866,6 +4870,7 @@ static void net_rps_action_and_irq_enable(struct softnet_data *sd)
} else
#endif
local_irq_enable();
@@ -159,7 +159,7 @@ index c37891828e4e..a275a8c147e7 100644
}
static bool sd_has_rps_ipi_waiting(struct softnet_data *sd)
-@@ -4942,6 +4947,7 @@ void __napi_schedule(struct napi_struct *n)
+@@ -4943,6 +4948,7 @@ void __napi_schedule(struct napi_struct *n)
local_irq_save(flags);
____napi_schedule(this_cpu_ptr(&softnet_data), n);
local_irq_restore(flags);
@@ -167,7 +167,7 @@ index c37891828e4e..a275a8c147e7 100644
}
EXPORT_SYMBOL(__napi_schedule);
-@@ -8044,6 +8050,7 @@ static int dev_cpu_callback(struct notifier_block *nfb,
+@@ -8045,6 +8051,7 @@ static int dev_cpu_callback(struct notifier_block *nfb,
raise_softirq_irqoff(NET_TX_SOFTIRQ);
local_irq_enable();
@@ -175,3 +175,6 @@ index c37891828e4e..a275a8c147e7 100644
/* Process offline CPU's input_pkt_queue */
while ((skb = __skb_dequeue(&oldsd->process_queue))) {
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0157-softirq-Disable-softirq-stacks-for-RT.patch b/debian/patches/features/all/rt/0157-softirq-Disable-softirq-stacks-for-RT.patch
index 88f84dc..f331104 100644
--- a/debian/patches/features/all/rt/0157-softirq-Disable-softirq-stacks-for-RT.patch
+++ b/debian/patches/features/all/rt/0157-softirq-Disable-softirq-stacks-for-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 18 Jul 2011 13:59:17 +0200
Subject: [PATCH 157/351] softirq: Disable softirq stacks for RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=488bd5e47b67312958029e01ea267d7c733887a8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9eec17ae19d578dec415cb169547e30726de55fc
Disable extra stacks for softirqs. We want to preempt softirqs and
having them on special IRQ-stack does not make this easier.
@@ -119,10 +119,10 @@ index 5cbf03c14981..6067d9379e5b 100644
#ifdef CONFIG_HOTPLUG_CPU
void fixup_irqs(void)
diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S
-index e7b0e7ff4c58..38dedcf62e01 100644
+index af4e58132d91..d573f0603a32 100644
--- a/arch/x86/entry/entry_64.S
+++ b/arch/x86/entry/entry_64.S
-@@ -894,6 +894,7 @@ EXPORT_SYMBOL(native_load_gs_index)
+@@ -925,6 +925,7 @@ bad_gs:
jmp 2b
.previous
@@ -130,7 +130,7 @@ index e7b0e7ff4c58..38dedcf62e01 100644
/* Call softirq on interrupt stack. Interrupts are off. */
ENTRY(do_softirq_own_stack)
pushq %rbp
-@@ -906,6 +907,7 @@ ENTRY(do_softirq_own_stack)
+@@ -937,6 +938,7 @@ ENTRY(do_softirq_own_stack)
decl PER_CPU_VAR(irq_count)
ret
END(do_softirq_own_stack)
@@ -171,3 +171,6 @@ index 5819d557f5fd..c2bcbd41e0ad 100644
void do_softirq_own_stack(void);
#else
static inline void do_softirq_own_stack(void)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0158-softirq-Split-softirq-locks.patch b/debian/patches/features/all/rt/0158-softirq-Split-softirq-locks.patch
index e97dda1..d659824 100644
--- a/debian/patches/features/all/rt/0158-softirq-Split-softirq-locks.patch
+++ b/debian/patches/features/all/rt/0158-softirq-Split-softirq-locks.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 4 Oct 2012 14:20:47 +0100
Subject: [PATCH 158/351] softirq: Split softirq locks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0b7bf6e470ff75f2c425b4b3a33ff62828aef37d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c6f73b05df89c4225e74483e11b76975b27f3ab5
The 3.x RT series removed the split softirq implementation in favour
of pushing softirq processing into the context of the thread which
@@ -199,10 +199,10 @@ index 4ffeb8ce1795..9aa9fef1d48d 100644
#define PF_EXITPIDONE 0x00000008 /* pi exit done on shut down */
#define PF_VCPU 0x00000010 /* I'm a virtual CPU */
diff --git a/init/main.c b/init/main.c
-index 25bac88bc66e..a4a61e7d2248 100644
+index 99f026565608..48ffaaad8ac9 100644
--- a/init/main.c
+++ b/init/main.c
-@@ -506,6 +506,7 @@ asmlinkage __visible void __init start_kernel(void)
+@@ -508,6 +508,7 @@ asmlinkage __visible void __init start_kernel(void)
setup_command_line(command_line);
setup_nr_cpu_ids();
setup_per_cpu_areas();
@@ -408,7 +408,7 @@ index 8669000c2aa3..ec9b3611f886 100644
/*
* Mask out PF_MEMALLOC s current task context is borrowed for the
-@@ -266,36 +419,7 @@ asmlinkage __visible void __softirq_entry __do_softirq(void)
+@@ -266,36 +419,7 @@ restart:
/* Reset the pending bitmask before enabling irqs */
set_softirq_pending(0);
@@ -810,10 +810,10 @@ index 8669000c2aa3..ec9b3611f886 100644
.thread_fn = run_ksoftirqd,
.thread_comm = "ksoftirqd/%u",
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
-index 14eaf34cbbc9..4367249e0dde 100644
+index 89191db4861a..4c185caffcce 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
-@@ -882,14 +882,7 @@ static bool can_stop_idle_tick(int cpu, struct tick_sched *ts)
+@@ -897,14 +897,7 @@ static bool can_stop_idle_tick(int cpu, struct tick_sched *ts)
return false;
if (unlikely(local_softirq_pending() && cpu_online(cpu))) {
@@ -830,10 +830,10 @@ index 14eaf34cbbc9..4367249e0dde 100644
}
diff --git a/net/core/dev.c b/net/core/dev.c
-index a275a8c147e7..885db5d6613c 100644
+index 88bc38b1eecc..01cde21ebf9a 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
-@@ -3867,11 +3867,9 @@ int netif_rx_ni(struct sk_buff *skb)
+@@ -3868,11 +3868,9 @@ int netif_rx_ni(struct sk_buff *skb)
trace_netif_rx_ni_entry(skb);
@@ -847,3 +847,6 @@ index a275a8c147e7..885db5d6613c 100644
return err;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0159-kernel-softirq-unlock-with-irqs-on.patch b/debian/patches/features/all/rt/0159-kernel-softirq-unlock-with-irqs-on.patch
index a107ec1..d5b3347 100644
--- a/debian/patches/features/all/rt/0159-kernel-softirq-unlock-with-irqs-on.patch
+++ b/debian/patches/features/all/rt/0159-kernel-softirq-unlock-with-irqs-on.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Tue, 9 Feb 2016 18:17:18 +0100
Subject: [PATCH 159/351] kernel: softirq: unlock with irqs on
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=95910c306744de0224a4e9775323e1b12133fcd3
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=998b01eaff914708fb3d17885478019c1f35b71c
We unlock the lock while the interrupts are off. This isn't a problem
now but will get because the migrate_disable() + enable are not
@@ -28,3 +28,6 @@ index ec9b3611f886..285a75bd7496 100644
}
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0160-kernel-migrate_disable-do-fastpath-in-atomic-irqs-of.patch b/debian/patches/features/all/rt/0160-kernel-migrate_disable-do-fastpath-in-atomic-irqs-of.patch
index 608447d..5988424 100644
--- a/debian/patches/features/all/rt/0160-kernel-migrate_disable-do-fastpath-in-atomic-irqs-of.patch
+++ b/debian/patches/features/all/rt/0160-kernel-migrate_disable-do-fastpath-in-atomic-irqs-of.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Tue, 9 Feb 2016 18:18:01 +0100
Subject: [PATCH 160/351] kernel: migrate_disable() do fastpath in atomic &
irqs-off
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=848e45dca6af0cfd8823d909bb03a4e4028200ec
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1097bc35502855e923364872984f78c1c75bdfc1
With interrupts off it makes no sense to do the long path since we can't
leave the CPU anyway. Also we might end up in a recursion with lockdep.
@@ -34,3 +34,6 @@ index e506ecc2f962..dcc12e735b50 100644
#ifdef CONFIG_SCHED_DEBUG
p->migrate_disable_atomic--;
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0161-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch b/debian/patches/features/all/rt/0161-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch
index 9b978a0..9b9c15c 100644
--- a/debian/patches/features/all/rt/0161-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch
+++ b/debian/patches/features/all/rt/0161-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 31 Jan 2012 13:01:27 +0100
Subject: [PATCH 161/351] genirq: Allow disabling of softirq processing in irq
thread context
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1808ce8675d75f887da43df457e3dc790e87bc29
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=afcf4b4c78e21ccff8f6ac893f1a18f20b3dba5b
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
@@ -155,3 +155,6 @@ index 285a75bd7496..a7f83bca653d 100644
int in_serving_softirq(void)
{
return current->flags & PF_IN_SOFTIRQ;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0162-softirq-split-timer-softirqs-out-of-ksoftirqd.patch b/debian/patches/features/all/rt/0162-softirq-split-timer-softirqs-out-of-ksoftirqd.patch
index cb61905..342bbb5 100644
--- a/debian/patches/features/all/rt/0162-softirq-split-timer-softirqs-out-of-ksoftirqd.patch
+++ b/debian/patches/features/all/rt/0162-softirq-split-timer-softirqs-out-of-ksoftirqd.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 20 Jan 2016 16:34:17 +0100
Subject: [PATCH 162/351] softirq: split timer softirqs out of ksoftirqd
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0cd872e5bb54fe1cca8f755333576f12ff29a4e2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=aecd06aed80b1cdc40804e278c745287be7383ff
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
@@ -209,3 +209,6 @@ index a7f83bca653d..a481db1a6774 100644
return 0;
}
early_initcall(spawn_ksoftirqd);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0163-softirq-wake-the-timer-softirq-if-needed.patch b/debian/patches/features/all/rt/0163-softirq-wake-the-timer-softirq-if-needed.patch
index 1464caa..7f2feeb 100644
--- a/debian/patches/features/all/rt/0163-softirq-wake-the-timer-softirq-if-needed.patch
+++ b/debian/patches/features/all/rt/0163-softirq-wake-the-timer-softirq-if-needed.patch
@@ -1,7 +1,7 @@
From: Mike Galbraith <efault at gmx.de>
Date: Fri, 20 Jan 2017 18:10:20 +0100
Subject: [PATCH 163/351] softirq: wake the timer softirq if needed
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=dc5521725df8d41de07395cd1a95221821063b75
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=39fa6f2f903526d894d98a090f2fa7d63b01ff49
The irq-exit path only checks the "normal"-softirq thread if it is
running and ignores the state of the "timer"-softirq thread. It is possible
@@ -72,3 +72,6 @@ index a481db1a6774..af2fd81cb9a5 100644
local_irq_save(flags);
if (__this_cpu_read(ksoftirqd) &&
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0166-rtmutex-trylock-is-okay-on-RT.patch b/debian/patches/features/all/rt/0166-rtmutex-trylock-is-okay-on-RT.patch
index 59c2d09..6cd8f51 100644
--- a/debian/patches/features/all/rt/0166-rtmutex-trylock-is-okay-on-RT.patch
+++ b/debian/patches/features/all/rt/0166-rtmutex-trylock-is-okay-on-RT.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 2 Dec 2015 11:34:07 +0100
Subject: [PATCH 166/351] rtmutex: trylock is okay on -RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8acbeef83c33340e870ac10706c57daa099a7231
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a11e247f93392773a99dcf5cf306c21079ff9d15
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
@@ -28,3 +28,6 @@ index 5138805ee66c..4b6fdcd827f5 100644
return 0;
return rt_mutex_fasttrylock(lock, rt_mutex_slowtrylock);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0167-gpu-don-t-check-for-the-lock-owner.patch b/debian/patches/features/all/rt/0167-gpu-don-t-check-for-the-lock-owner.patch
index efeb8a4..3965d28 100644
--- a/debian/patches/features/all/rt/0167-gpu-don-t-check-for-the-lock-owner.patch
+++ b/debian/patches/features/all/rt/0167-gpu-don-t-check-for-the-lock-owner.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Tue, 14 Jul 2015 14:26:34 +0200
Subject: [PATCH 167/351] gpu: don't check for the lock owner.
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=30dbafd3e222f0319e38081e63b32872a9e9051c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3bd6020b4f2aa9effb83a3aa5585f7878308633e
Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
---
@@ -35,3 +35,6 @@ index 192b2d3a79cb..d5372a207326 100644
return mutex->owner == task;
#else
/* Since UP may be pre-empted, we cannot assume that we own the lock */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0168-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch b/debian/patches/features/all/rt/0168-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch
index c6dc244..ddd8e78 100644
--- a/debian/patches/features/all/rt/0168-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch
+++ b/debian/patches/features/all/rt/0168-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 15 Sep 2016 10:51:27 +0200
Subject: [PATCH 168/351] fs/nfs: turn rmdir_sem into a semaphore
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7653ba0a36c73c6d9996c4ed69516e30fcb66fe4
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=aebb0cfd3602e4fc4a89f7ce54f71fca8b103ed9
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
@@ -21,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
4 files changed, 43 insertions(+), 4 deletions(-)
diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
-index 65566d5fcf39..c1cc9707bbb3 100644
+index 1e5321d1ed22..24c0a094d61e 100644
--- a/fs/nfs/dir.c
+++ b/fs/nfs/dir.c
@@ -1807,7 +1807,11 @@ int nfs_rmdir(struct inode *dir, struct dentry *dentry)
@@ -145,3 +145,6 @@ index 810124b33327..d54ca43d571f 100644
#if IS_ENABLED(CONFIG_NFS_V4)
struct nfs4_cached_acl *nfs4_acl;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0169-rtmutex-Handle-the-various-new-futex-race-conditions.patch b/debian/patches/features/all/rt/0169-rtmutex-Handle-the-various-new-futex-race-conditions.patch
index 1526c25..3f92afb 100644
--- a/debian/patches/features/all/rt/0169-rtmutex-Handle-the-various-new-futex-race-conditions.patch
+++ b/debian/patches/features/all/rt/0169-rtmutex-Handle-the-various-new-futex-race-conditions.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 10 Jun 2011 11:04:15 +0200
Subject: [PATCH 169/351] rtmutex: Handle the various new futex race conditions
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=352fa01858ed2713c52d175786df4be1b9bed12e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7ccdf7863b1dc0b57ee451611ab698cc8923160c
RT opens a few new interesting race conditions in the rtmutex/futex
combo due to futex hash bucket lock being a 'sleeping' spinlock and
@@ -18,7 +18,7 @@ diff --git a/kernel/futex.c b/kernel/futex.c
index 1ec1a9910beb..a9400070c61c 100644
--- a/kernel/futex.c
+++ b/kernel/futex.c
-@@ -2012,6 +2012,16 @@ static int futex_requeue(u32 __user *uaddr1, unsigned int flags,
+@@ -2012,6 +2012,16 @@ retry_private:
requeue_pi_wake_futex(this, &key2, hb2);
drop_count++;
continue;
@@ -250,3 +250,6 @@ index 722e3cf38acf..be1c0171f647 100644
extern struct task_struct *rt_mutex_next_owner(struct rt_mutex *lock);
extern void rt_mutex_init_proxy_locked(struct rt_mutex *lock,
struct task_struct *proxy_owner);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0170-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch b/debian/patches/features/all/rt/0170-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch
index fb093e5..b64b0f8 100644
--- a/debian/patches/features/all/rt/0170-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch
+++ b/debian/patches/features/all/rt/0170-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch
@@ -1,7 +1,7 @@
From: Steven Rostedt <rostedt at goodmis.org>
Date: Tue, 14 Jul 2015 14:26:34 +0200
Subject: [PATCH 170/351] futex: Fix bug on when a requeued RT task times out
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9e6e77bdae60cc2fb191c84b21440bc071db39cc
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a2ff17824be85a45123d9139c74d0b3b9048c677
Requeue with timeout causes a bug with PREEMPT_RT_FULL.
@@ -116,3 +116,6 @@ index be1c0171f647..0bb2a07c0566 100644
extern struct task_struct *rt_mutex_next_owner(struct rt_mutex *lock);
extern void rt_mutex_init_proxy_locked(struct rt_mutex *lock,
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0171-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch b/debian/patches/features/all/rt/0171-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch
index f82d89f..3d3b411 100644
--- a/debian/patches/features/all/rt/0171-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch
+++ b/debian/patches/features/all/rt/0171-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 1 Mar 2013 11:17:42 +0100
Subject: [PATCH 171/351] futex: Ensure lock/unlock symetry versus pi_lock and
hash bucket lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f5b6e36be5099d6afd23e12e72e04546e4f8aee7
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=77655b0d8142f3c7be6e949def4c4a28c9b1d448
In exit_pi_state_list() we have the following locking construct:
@@ -44,3 +44,6 @@ index a9400070c61c..b6c06e5886e5 100644
continue;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0172-pid.h-include-atomic.h.patch b/debian/patches/features/all/rt/0172-pid.h-include-atomic.h.patch
index 1386669..350bd49 100644
--- a/debian/patches/features/all/rt/0172-pid.h-include-atomic.h.patch
+++ b/debian/patches/features/all/rt/0172-pid.h-include-atomic.h.patch
@@ -1,7 +1,7 @@
From: Grygorii Strashko <Grygorii.Strashko at linaro.org>
Date: Tue, 21 Jul 2015 19:43:56 +0300
Subject: [PATCH 172/351] pid.h: include atomic.h
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c3377df0108d1fb221f910593b5316b8c8e2bcfc
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7ec111c1816db9c055255f169dacc92d8b2af704
This patch fixes build error:
CC kernel/pid_namespace.o
@@ -37,3 +37,6 @@ index 97b745ddece5..01a5460a0c85 100644
enum pid_type
{
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0173-arm-include-definition-for-cpumask_t.patch b/debian/patches/features/all/rt/0173-arm-include-definition-for-cpumask_t.patch
index d935d41..c6ea4e3 100644
--- a/debian/patches/features/all/rt/0173-arm-include-definition-for-cpumask_t.patch
+++ b/debian/patches/features/all/rt/0173-arm-include-definition-for-cpumask_t.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 22 Dec 2016 17:28:33 +0100
Subject: [PATCH 173/351] arm: include definition for cpumask_t
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f997597409411715b196354fb81bb2c69bba688c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=98bfd3c19d235060d8e6d856e6075bcad232a0f4
This definition gets pulled in by other files. With the (later) split of
RCU and spinlock.h it won't compile anymore.
@@ -25,3 +25,6 @@ index e53638c8ed8a..6095a1649865 100644
struct irqaction;
struct pt_regs;
extern void migrate_irqs(void);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0174-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch b/debian/patches/features/all/rt/0174-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch
index 6f80a96..6a7e85a 100644
--- a/debian/patches/features/all/rt/0174-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch
+++ b/debian/patches/features/all/rt/0174-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch
@@ -2,7 +2,7 @@ From: "Wolfgang M. Reimer" <linuxball at gmail.com>
Date: Tue, 21 Jul 2015 16:20:07 +0200
Subject: [PATCH 174/351] locking: locktorture: Do NOT include rwlock.h
directly
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=47b0667bfe0691c821e0990db366cb60a1d67434
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=adaee0bd1a6edb0ac7f57bc965eb0f39a2616d47
Including rwlock.h directly will cause kernel builds to fail
if CONFIG_PREEMPT_RT_FULL is defined. The correct header file
@@ -28,3 +28,6 @@ index d3de04b12f8c..0f49abeae337 100644
#include <linux/mutex.h>
#include <linux/rwsem.h>
#include <linux/smp.h>
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0175-rtmutex-Add-rtmutex_lock_killable.patch b/debian/patches/features/all/rt/0175-rtmutex-Add-rtmutex_lock_killable.patch
index f6dbaec..a0b03f0 100644
--- a/debian/patches/features/all/rt/0175-rtmutex-Add-rtmutex_lock_killable.patch
+++ b/debian/patches/features/all/rt/0175-rtmutex-Add-rtmutex_lock_killable.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 9 Jun 2011 11:43:52 +0200
Subject: [PATCH 175/351] rtmutex: Add rtmutex_lock_killable()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2428322fb6ebbc9ac697d8583898dd894a67bb48
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6d94fb66f2132e67afbdf6d54d824d7cd29f60b9
Add "killable" type to rtmutex. We need this since rtmutex are used as
"normal" mutexes which do use this type.
@@ -54,3 +54,6 @@ index eb38fc5f3d49..d2eb3db18563 100644
/**
* rt_mutex_timed_lock - lock a rt_mutex interruptible
* the timeout structure is provided
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0176-rtmutex-Make-lock_killable-work.patch b/debian/patches/features/all/rt/0176-rtmutex-Make-lock_killable-work.patch
index ed74ef0..d836909 100644
--- a/debian/patches/features/all/rt/0176-rtmutex-Make-lock_killable-work.patch
+++ b/debian/patches/features/all/rt/0176-rtmutex-Make-lock_killable-work.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 1 Apr 2017 12:50:59 +0200
Subject: [PATCH 176/351] rtmutex: Make lock_killable work
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=432d0238e258f9e32ef9cfec374d3f1f64a67afe
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=94ea9e3f2d2fc6d3b886f0639102fa923516a7c3
Locking an rt mutex killable does not work because signal handling is
restricted to TASK_INTERRUPTIBLE.
@@ -45,3 +45,6 @@ index d2eb3db18563..9d664eee062f 100644
}
raw_spin_unlock_irq(&lock->wait_lock);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0177-spinlock-Split-the-lock-types-header.patch b/debian/patches/features/all/rt/0177-spinlock-Split-the-lock-types-header.patch
index 6fc8085..bce21c9 100644
--- a/debian/patches/features/all/rt/0177-spinlock-Split-the-lock-types-header.patch
+++ b/debian/patches/features/all/rt/0177-spinlock-Split-the-lock-types-header.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 29 Jun 2011 19:34:01 +0200
Subject: [PATCH 177/351] spinlock: Split the lock types header
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9a9c429294bf50e8e5575033209ace534e11393c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fb758930d0c8b8b845fedf1d0b1cde5c5d5f8846
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
@@ -219,3 +219,6 @@ index 000000000000..edffc4d53fc9
+#define DEFINE_RAW_SPINLOCK(x) raw_spinlock_t x = __RAW_SPIN_LOCK_UNLOCKED(x)
+
+#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0178-rtmutex-Avoid-include-hell.patch b/debian/patches/features/all/rt/0178-rtmutex-Avoid-include-hell.patch
index f820b41..50bb473 100644
--- a/debian/patches/features/all/rt/0178-rtmutex-Avoid-include-hell.patch
+++ b/debian/patches/features/all/rt/0178-rtmutex-Avoid-include-hell.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 29 Jun 2011 20:06:39 +0200
Subject: [PATCH 178/351] rtmutex: Avoid include hell
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=85e8078ff5076a830eefa3ba2c37fd189c184d58
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a19cd4ae5a10bd3545e89c664cdcf0e6f50cd369
Include only the required raw types. This avoids pulling in the
complete spinlock header which in turn requires rtmutex.h at some point.
@@ -24,3 +24,6 @@ index 51dc12e3860c..2ed41c408043 100644
extern int max_lock_depth; /* for sysctl */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0179-rbtree-don-t-include-the-rcu-header.patch b/debian/patches/features/all/rt/0179-rbtree-don-t-include-the-rcu-header.patch
index bd63053..0b9361b 100644
--- a/debian/patches/features/all/rt/0179-rbtree-don-t-include-the-rcu-header.patch
+++ b/debian/patches/features/all/rt/0179-rbtree-don-t-include-the-rcu-header.patch
@@ -4,7 +4,7 @@ Subject: [PATCH 179/351] rbtree: don't include the rcu header
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=840207ac18135ed09fe1d0bef03f1a02ebcfba7e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=43704e5b1afb4fcb1157c00a2797aabd80791fe0
The RCU header pulls in spinlock.h and fails due not yet defined types:
@@ -169,3 +169,6 @@ index 00dc4a9474c0..a5b130e22c33 100644
/**
* rcu_access_pointer() - fetch RCU pointer with no dereferencing
* @p: The pointer to read
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0180-rt-Add-the-preempt-rt-lock-replacement-APIs.patch b/debian/patches/features/all/rt/0180-rt-Add-the-preempt-rt-lock-replacement-APIs.patch
index c698a49..1bfe33b 100644
--- a/debian/patches/features/all/rt/0180-rt-Add-the-preempt-rt-lock-replacement-APIs.patch
+++ b/debian/patches/features/all/rt/0180-rt-Add-the-preempt-rt-lock-replacement-APIs.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 26 Jul 2009 19:39:56 +0200
Subject: [PATCH 180/351] rt: Add the preempt-rt lock replacement APIs
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0d9677beb5cdec54cb9b48723485ed1193c17d10
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=cc1a1eac39001cfd85d534228f4c1ac6807d4181
Map spinlocks, rwlocks, rw_semaphores and semaphores to the rt_mutex
based locking functions for preempt-rt.
@@ -985,7 +985,7 @@ index b6c06e5886e5..2e074d63e8fa 100644
return ret;
}
-@@ -2667,7 +2668,7 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
+@@ -2667,7 +2668,7 @@ retry_private:
goto no_block;
}
@@ -1700,7 +1700,7 @@ index 9d664eee062f..b99ddf374df1 100644
/*
* The current top waiter stays enqueued. We
* don't have to change anything in the lock
-@@ -936,6 +974,339 @@ static int try_to_take_rt_mutex(struct rt_mutex *lock, struct task_struct *task,
+@@ -936,6 +974,339 @@ takeit:
return 1;
}
@@ -2379,3 +2379,6 @@ index dcc12e735b50..ea1c44f014b8 100644
put_task_struct(task);
}
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0181-rt-Drop-mutex_disable-on-DEBUG-configs-and-the-GPL-s.patch b/debian/patches/features/all/rt/0181-rt-Drop-mutex_disable-on-DEBUG-configs-and-the-GPL-s.patch
index 61eb4bd..5791e1b 100644
--- a/debian/patches/features/all/rt/0181-rt-Drop-mutex_disable-on-DEBUG-configs-and-the-GPL-s.patch
+++ b/debian/patches/features/all/rt/0181-rt-Drop-mutex_disable-on-DEBUG-configs-and-the-GPL-s.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 10 Feb 2017 18:21:04 +0100
Subject: [PATCH 181/351] rt: Drop mutex_disable() on !DEBUG configs and the
GPL suffix from export symbol
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0c8bdeccb2087245f3fdda1f4365f11b2587d573
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a1e4dad96bb4a5eb2acc611ba012ce5f98c1261d
Alex Goins reported that mutex_destroy() on RT will force a GPL only symbol
which won't link and therefore fail on a non-GPL kernel module.
@@ -34,3 +34,6 @@ index c38a44b14da5..e0284edec655 100644
#ifdef CONFIG_DEBUG_LOCK_ALLOC
# define mutex_lock_nested(l, s) _mutex_lock_nested(l, s)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0182-kernel-locking-use-an-exclusive-wait_q-for-sleepers.patch b/debian/patches/features/all/rt/0182-kernel-locking-use-an-exclusive-wait_q-for-sleepers.patch
index 2a41ed7..31aefdd 100644
--- a/debian/patches/features/all/rt/0182-kernel-locking-use-an-exclusive-wait_q-for-sleepers.patch
+++ b/debian/patches/features/all/rt/0182-kernel-locking-use-an-exclusive-wait_q-for-sleepers.patch
@@ -4,7 +4,7 @@ Subject: [PATCH 182/351] kernel/locking: use an exclusive wait_q for sleepers
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b4b54803cec1806371a6dc409b6b2b3550efc1ed
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e7b5667852b30a0d208f9b209f49114e14f8b156
If a task is queued as a sleeper for a wakeup and never goes to
schedule() (because it just obtained the lock) then it will receive a
@@ -78,10 +78,10 @@ index 0fc34f29f28c..7cc3ab932a7e 100644
#ifdef CONFIG_RT_MUTEXES
/* PI waiters blocked on a rt_mutex held by this task */
diff --git a/kernel/fork.c b/kernel/fork.c
-index 11fa53573d26..276acd8acf0a 100644
+index 5bcb777b6913..2529725eefa2 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
-@@ -558,6 +558,7 @@ static struct task_struct *dup_task_struct(struct task_struct *orig, int node)
+@@ -564,6 +564,7 @@ static struct task_struct *dup_task_struct(struct task_struct *orig, int node)
tsk->splice_pipe = NULL;
tsk->task_frag.page = NULL;
tsk->wake_q.next = NULL;
@@ -144,3 +144,6 @@ index ea1c44f014b8..7adb41e4b0f6 100644
/*
* wake_up_process() implies a wmb() to pair with the queueing
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0183-rtmutex-Add-RT-aware-ww-locks.patch b/debian/patches/features/all/rt/0183-rtmutex-Add-RT-aware-ww-locks.patch
index 75b748e..7bd8f18 100644
--- a/debian/patches/features/all/rt/0183-rtmutex-Add-RT-aware-ww-locks.patch
+++ b/debian/patches/features/all/rt/0183-rtmutex-Add-RT-aware-ww-locks.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc>
Date: Mon, 28 Oct 2013 09:36:37 +0100
Subject: [PATCH 183/351] rtmutex: Add RT aware ww locks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=41f6261e920c6bf80f1fb71362656fbcead21919
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=100961d9e029ba71c7d66cb27653047a4ae61690
lockdep says:
| --------------------------------------------------------------------------
@@ -412,3 +412,6 @@ index c1a3b9f099de..c3756e59fcc5 100644
-EXPORT_SYMBOL_GPL(ww_mutex_unlock);
+EXPORT_SYMBOL(ww_mutex_unlock);
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0184-rtmutex-Provide-rt_mutex_lock_state.patch b/debian/patches/features/all/rt/0184-rtmutex-Provide-rt_mutex_lock_state.patch
index 962051b..137cf73 100644
--- a/debian/patches/features/all/rt/0184-rtmutex-Provide-rt_mutex_lock_state.patch
+++ b/debian/patches/features/all/rt/0184-rtmutex-Provide-rt_mutex_lock_state.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 1 Apr 2017 12:51:00 +0200
Subject: [PATCH 184/351] rtmutex: Provide rt_mutex_lock_state()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f57fba35e2b5cd07df585f6dc132416881d4962a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5e53d2ae49c99fe262d145dde45298558ed33e27
Allow rtmutex to be locked with arbitrary states. Preparatory patch for the
rt rwsem rework.
@@ -115,3 +115,6 @@ index c3756e59fcc5..9076a7470159 100644
/**
* rt_mutex_timed_lock - lock a rt_mutex interruptible
* the timeout structure is provided
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0185-rtmutex-Provide-locked-slowpath.patch b/debian/patches/features/all/rt/0185-rtmutex-Provide-locked-slowpath.patch
index cc23834..a2e41a0 100644
--- a/debian/patches/features/all/rt/0185-rtmutex-Provide-locked-slowpath.patch
+++ b/debian/patches/features/all/rt/0185-rtmutex-Provide-locked-slowpath.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 1 Apr 2017 12:51:01 +0200
Subject: [PATCH 185/351] rtmutex: Provide locked slowpath
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b66010b0048ec5feb14dab5eb5d46c8c42a7e16e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f0c293aa74c1a0c57e2cb8ca6c07d999b7bfb8db
The new rt rwsem implementation needs rtmutex::wait_lock to protect struct
rw_semaphore. Dropping the lock and reaquiring it for locking the rtmutex
@@ -152,3 +152,6 @@ index 32ae70f25c08..64d89d780059 100644
#ifdef CONFIG_DEBUG_RT_MUTEXES
# include "rtmutex-debug.h"
#else
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0186-futex-rtmutex-Cure-RT-double-blocking-issue.patch b/debian/patches/features/all/rt/0186-futex-rtmutex-Cure-RT-double-blocking-issue.patch
index 4835687..0b1f016 100644
--- a/debian/patches/features/all/rt/0186-futex-rtmutex-Cure-RT-double-blocking-issue.patch
+++ b/debian/patches/features/all/rt/0186-futex-rtmutex-Cure-RT-double-blocking-issue.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 9 May 2017 17:11:10 +0200
Subject: [PATCH 186/351] futex/rtmutex: Cure RT double blocking issue
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bcba9aa81d398adcfbddfe1bcbe0300e5b8cb14f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0b8df5af982529af57185fea278363de34e718c5
RT has a problem when the wait on a futex/rtmutex got interrupted by a
timeout or a signal. task->pi_blocked_on is still set when returning from
@@ -61,3 +61,6 @@ index 43f1394aa12d..6e52bce66a26 100644
raw_spin_unlock_irq(&lock->wait_lock);
return ret;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0187-rwsem-rt-Lift-single-reader-restriction.patch b/debian/patches/features/all/rt/0187-rwsem-rt-Lift-single-reader-restriction.patch
index 1b58e0f..64f2bca 100644
--- a/debian/patches/features/all/rt/0187-rwsem-rt-Lift-single-reader-restriction.patch
+++ b/debian/patches/features/all/rt/0187-rwsem-rt-Lift-single-reader-restriction.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 1 Apr 2017 12:51:02 +0200
Subject: [PATCH 187/351] rwsem/rt: Lift single reader restriction
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7940550a681c32bfcccd78519d8a2053a0ea0141
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=66e31d15b1470796cadf35fc48a3aaad92b2366c
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
@@ -750,3 +750,6 @@ index 000000000000..4a708ffcded6
+ /* Release it and account current as reader */
+ __up_write_unlock(sem, WRITER_BIAS - 1, flags);
+}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0188-ptrace-fix-ptrace-vs-tasklist_lock-race.patch b/debian/patches/features/all/rt/0188-ptrace-fix-ptrace-vs-tasklist_lock-race.patch
index 181b11b..776e411 100644
--- a/debian/patches/features/all/rt/0188-ptrace-fix-ptrace-vs-tasklist_lock-race.patch
+++ b/debian/patches/features/all/rt/0188-ptrace-fix-ptrace-vs-tasklist_lock-race.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 29 Aug 2013 18:21:04 +0200
Subject: [PATCH 188/351] ptrace: fix ptrace vs tasklist_lock race
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a891976b84ef23a40b1114b410e005972543cacb
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f66aa0016aeaa5c68d8b80c2851e0b0b7d7e5785
As explained by Alexander Fyodorov <halcy at yandex.ru>:
@@ -120,7 +120,7 @@ diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 7adb41e4b0f6..da02e71c58e8 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
-@@ -1396,6 +1396,18 @@ int migrate_swap(struct task_struct *cur, struct task_struct *p)
+@@ -1396,6 +1396,18 @@ out:
return ret;
}
@@ -158,3 +158,6 @@ index 7adb41e4b0f6..da02e71c58e8 100644
ncsw = p->nvcsw | LONG_MIN; /* sets MSB */
task_rq_unlock(rq, p, &rf);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0189-rcu-Frob-softirq-test.patch b/debian/patches/features/all/rt/0189-rcu-Frob-softirq-test.patch
index 7026cf6..77b3af4 100644
--- a/debian/patches/features/all/rt/0189-rcu-Frob-softirq-test.patch
+++ b/debian/patches/features/all/rt/0189-rcu-Frob-softirq-test.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <a.p.zijlstra at chello.nl>
Date: Sat, 13 Aug 2011 00:23:17 +0200
Subject: [PATCH 189/351] rcu: Frob softirq test
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d5ef8c27aaf0213b7f8a1a7302d8071339c75cd4
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d8ac24429ae77d9a9442b1d1d2e3857fcb0d1029
With RT_FULL we get the below wreckage:
@@ -167,3 +167,6 @@ index e3944c4b072d..a95d623a84b9 100644
lockdep_rcu_suspicious(__FILE__, __LINE__,
"rcu_read_unlock() from irq or softirq with blocking in critical section!!!\n");
pr_alert("->rcu_read_unlock_special: %#x (b: %d, enq: %d nq: %d)\n",
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0190-rcu-Merge-RCU-bh-into-RCU-preempt.patch b/debian/patches/features/all/rt/0190-rcu-Merge-RCU-bh-into-RCU-preempt.patch
index 37602a1..6d5f04a 100644
--- a/debian/patches/features/all/rt/0190-rcu-Merge-RCU-bh-into-RCU-preempt.patch
+++ b/debian/patches/features/all/rt/0190-rcu-Merge-RCU-bh-into-RCU-preempt.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 5 Oct 2011 11:59:38 -0700
Subject: [PATCH 190/351] rcu: Merge RCU-bh into RCU-preempt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8c81040786dfee676b435f9cc77effa805453001
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2f8b78ab10a8d1118590de7937a6209dee9f7f61
The Linux kernel has long RCU-bh read-side critical sections that
intolerably increase scheduling latency under mainline's RCU-bh rules,
@@ -375,3 +375,6 @@ index 019b4708c9fa..949714f485ee 100644
#endif /* #ifdef CONFIG_DEBUG_LOCK_ALLOC */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0191-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch b/debian/patches/features/all/rt/0191-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch
index 1d15944..58d4e71 100644
--- a/debian/patches/features/all/rt/0191-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch
+++ b/debian/patches/features/all/rt/0191-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch
@@ -1,7 +1,7 @@
From: "Paul E. McKenney" <paulmck at linux.vnet.ibm.com>
Date: Wed, 5 Oct 2011 11:45:18 -0700
Subject: [PATCH 191/351] rcu: Make ksoftirqd do RCU quiescent states
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bb4b37e7d1720443ae8484b67784be0058be42e5
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=253e0ba2b1a0dc881236d590ddbae55e11ebb623
Implementing RCU-bh in terms of RCU-preempt makes the system vulnerable
to network-based denial-of-service attacks. This patch therefore
@@ -112,3 +112,6 @@ index a95d623a84b9..a375276227a8 100644
/*
* Prepare a CPU for idle from an RCU perspective. The first major task
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0192-rcutree-rcu_bh_qs-Disable-irq-while-calling-rcu_pree.patch b/debian/patches/features/all/rt/0192-rcutree-rcu_bh_qs-Disable-irq-while-calling-rcu_pree.patch
index c890d51..5233262 100644
--- a/debian/patches/features/all/rt/0192-rcutree-rcu_bh_qs-Disable-irq-while-calling-rcu_pree.patch
+++ b/debian/patches/features/all/rt/0192-rcutree-rcu_bh_qs-Disable-irq-while-calling-rcu_pree.patch
@@ -2,7 +2,7 @@ From: Tiejun Chen <tiejun.chen at windriver.com>
Date: Wed, 18 Dec 2013 17:51:49 +0800
Subject: [PATCH 192/351] rcutree/rcu_bh_qs: Disable irq while calling
rcu_preempt_qs()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=05db6a8cb6304233eb3f2a60f6fc99f90bc115f7
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9cf30eabea4c09bfe374db00c93431a34776b067
Any callers to the function rcu_preempt_qs() must disable irqs in
order to protect the assignment to ->rcu_read_unlock_special. In
@@ -50,3 +50,6 @@ index b33efec45353..dc5638f86744 100644
}
#else
void rcu_bh_qs(void)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0193-tty-serial-omap-Make-the-locking-RT-aware.patch b/debian/patches/features/all/rt/0193-tty-serial-omap-Make-the-locking-RT-aware.patch
index 630e9ae..497d947 100644
--- a/debian/patches/features/all/rt/0193-tty-serial-omap-Make-the-locking-RT-aware.patch
+++ b/debian/patches/features/all/rt/0193-tty-serial-omap-Make-the-locking-RT-aware.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 28 Jul 2011 13:32:57 +0200
Subject: [PATCH 193/351] tty/serial/omap: Make the locking RT aware
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6831c42db052ea23e3e9bbfe1010c08cd245d622
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c285cc8af1c583818c0f4a08fc9676ee6612bfe4
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
@@ -43,3 +43,6 @@ index 472ba3c813c1..e654cb421fb7 100644
}
static int __init
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0194-tty-serial-pl011-Make-the-locking-work-on-RT.patch b/debian/patches/features/all/rt/0194-tty-serial-pl011-Make-the-locking-work-on-RT.patch
index c902929..7846fbe 100644
--- a/debian/patches/features/all/rt/0194-tty-serial-pl011-Make-the-locking-work-on-RT.patch
+++ b/debian/patches/features/all/rt/0194-tty-serial-pl011-Make-the-locking-work-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 8 Jan 2013 21:36:51 +0100
Subject: [PATCH 194/351] tty/serial/pl011: Make the locking work on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8e14a8061e9ba40b0bdb5f4be05b3848e5d84c2b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=63116759a6a4a09ec1e3ef1e26bbfc7a8d503437
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.
@@ -48,3 +48,6 @@ index e2c33b9528d8..53af53c43e8c 100644
clk_disable(uap->clk);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0195-rt-Improve-the-serial-console-PASS_LIMIT.patch b/debian/patches/features/all/rt/0195-rt-Improve-the-serial-console-PASS_LIMIT.patch
index b129409..8d90573 100644
--- a/debian/patches/features/all/rt/0195-rt-Improve-the-serial-console-PASS_LIMIT.patch
+++ b/debian/patches/features/all/rt/0195-rt-Improve-the-serial-console-PASS_LIMIT.patch
@@ -4,7 +4,7 @@ Subject: [PATCH 195/351] rt: Improve the serial console PASS_LIMIT
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=305c878b6fade44a35656ea5059d7c20643085a8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c889573a586b3419d7167e0069eda1354b70fd2f
Beyond the warning:
@@ -41,3 +41,6 @@ index e8819aa20415..dd7f9bf45d6c 100644
#include <asm/serial.h>
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0196-tty-serial-8250-don-t-take-the-trylock-during-oops.patch b/debian/patches/features/all/rt/0196-tty-serial-8250-don-t-take-the-trylock-during-oops.patch
index deb1e87..a0ce6aa 100644
--- a/debian/patches/features/all/rt/0196-tty-serial-8250-don-t-take-the-trylock-during-oops.patch
+++ b/debian/patches/features/all/rt/0196-tty-serial-8250-don-t-take-the-trylock-during-oops.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 11 Apr 2016 16:55:02 +0200
Subject: [PATCH 196/351] tty: serial: 8250: don't take the trylock during oops
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7fe85278972fe09701a6dd91772ddc9dd0ad6366
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=89c4d972e77ca3cd5c258d3a6193dd83e010c076
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
@@ -29,3 +29,6 @@ index f6e4373a8850..004931f34d04 100644
else
spin_lock_irqsave(&port->lock, flags);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0197-wait.h-include-atomic.h.patch b/debian/patches/features/all/rt/0197-wait.h-include-atomic.h.patch
index 7e15b20..a1ed6b8 100644
--- a/debian/patches/features/all/rt/0197-wait.h-include-atomic.h.patch
+++ b/debian/patches/features/all/rt/0197-wait.h-include-atomic.h.patch
@@ -4,7 +4,7 @@ Subject: [PATCH 197/351] wait.h: include atomic.h
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ebde33cfd1182abcf5c296fc4f5e470475cc35cb
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fea63f2dfb8c6d7edc9240449ba9fd70d9b1ff6e
| CC init/main.o
|In file included from include/linux/mmzone.h:9:0,
@@ -36,3 +36,6 @@ index 2408e8d5c05c..db50d6609195 100644
typedef struct __wait_queue wait_queue_t;
typedef int (*wait_queue_func_t)(wait_queue_t *wait, unsigned mode, int flags, void *key);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0198-work-simple-Simple-work-queue-implemenation.patch b/debian/patches/features/all/rt/0198-work-simple-Simple-work-queue-implemenation.patch
index b5b3064..6b62925 100644
--- a/debian/patches/features/all/rt/0198-work-simple-Simple-work-queue-implemenation.patch
+++ b/debian/patches/features/all/rt/0198-work-simple-Simple-work-queue-implemenation.patch
@@ -1,7 +1,7 @@
From: Daniel Wagner <daniel.wagner at bmw-carit.de>
Date: Fri, 11 Jul 2014 15:26:11 +0200
Subject: [PATCH 198/351] work-simple: Simple work queue implemenation
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7f8d32488f522317e756b32ffe574419e4dbd463
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5ea41ef38bdc0d01afe3b08dca20643c20992ed5
Provides a framework for enqueuing callbacks from irq context
PREEMPT_RT_FULL safe. The callbacks are executed in kthread context.
@@ -240,3 +240,6 @@ index 000000000000..1950f40ca725
+ mutex_unlock(&worker_mutex);
+}
+EXPORT_SYMBOL_GPL(swork_put);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0199-completion-Use-simple-wait-queues.patch b/debian/patches/features/all/rt/0199-completion-Use-simple-wait-queues.patch
index 22b0a25..68387ca 100644
--- a/debian/patches/features/all/rt/0199-completion-Use-simple-wait-queues.patch
+++ b/debian/patches/features/all/rt/0199-completion-Use-simple-wait-queues.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 11 Jan 2013 11:23:51 +0100
Subject: [PATCH 199/351] completion: Use simple wait queues
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=439088f209b2b5919065a6c444a5596999d88acd
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=869f15816077e674b9c65767a33343cdd903d168
Completions have no long lasting callbacks and therefor do not need
the complex waitqueue variant. Use simple waitqueues which reduces the
@@ -37,7 +37,7 @@ index bca6935a94db..d7a35ee34d03 100644
}
break;
diff --git a/drivers/usb/gadget/function/f_fs.c b/drivers/usb/gadget/function/f_fs.c
-index 4fce83266926..5e902a89d8e6 100644
+index 7b107e43b1c4..f1e8534a1748 100644
--- a/drivers/usb/gadget/function/f_fs.c
+++ b/drivers/usb/gadget/function/f_fs.c
@@ -1593,7 +1593,7 @@ static void ffs_data_put(struct ffs_data *ffs)
@@ -50,7 +50,7 @@ index 4fce83266926..5e902a89d8e6 100644
kfree(ffs);
}
diff --git a/drivers/usb/gadget/legacy/inode.c b/drivers/usb/gadget/legacy/inode.c
-index f69dbd4bcd18..3b7638322f9f 100644
+index b8534d3f8bb0..8fcaf02e21b0 100644
--- a/drivers/usb/gadget/legacy/inode.c
+++ b/drivers/usb/gadget/legacy/inode.c
@@ -347,7 +347,7 @@ ep_io (struct ep_data *epdata, void *buf, unsigned len)
@@ -370,3 +370,6 @@ index 82f0dff90030..e2e224c59c0a 100644
void swake_up(struct swait_queue_head *q)
{
unsigned long flags;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0200-fs-aio-simple-simple-work.patch b/debian/patches/features/all/rt/0200-fs-aio-simple-simple-work.patch
index 3819547..30cc632 100644
--- a/debian/patches/features/all/rt/0200-fs-aio-simple-simple-work.patch
+++ b/debian/patches/features/all/rt/0200-fs-aio-simple-simple-work.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 16 Feb 2015 18:49:10 +0100
Subject: [PATCH 200/351] fs/aio: simple simple work
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2cf79576d15f6fe4746fac3ef3bac8b39594b37d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=eac7d06bbb8aca64fff7f8ed5a166ffa4504e40b
|BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:768
|in_atomic(): 1, irqs_disabled(): 0, pid: 26, name: rcuos/2
@@ -107,3 +107,6 @@ index 0fcb49ad67d4..211ebc21e4db 100644
static int ioctx_add_table(struct kioctx *ctx, struct mm_struct *mm)
{
unsigned i, new_nr;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0201-genirq-Do-not-invoke-the-affinity-callback-via-a-wor.patch b/debian/patches/features/all/rt/0201-genirq-Do-not-invoke-the-affinity-callback-via-a-wor.patch
index 1661688..33123df 100644
--- a/debian/patches/features/all/rt/0201-genirq-Do-not-invoke-the-affinity-callback-via-a-wor.patch
+++ b/debian/patches/features/all/rt/0201-genirq-Do-not-invoke-the-affinity-callback-via-a-wor.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 21 Aug 2013 17:48:46 +0200
Subject: [PATCH 201/351] genirq: Do not invoke the affinity callback via a
workqueue on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2e148d5859ff5d5acd7f444bb4b2ba029cbded92
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2b2d780da0d611b2eff54d8a20f5e682add6758e
Joe Korty reported, that __irq_set_affinity_locked() schedules a
workqueue while holding a rawlock which results in a might_sleep()
@@ -93,7 +93,7 @@ index 562df8dc14be..5f14e0d7c0c7 100644
struct irq_desc *desc = irq_to_desc(notify->irq);
cpumask_var_t cpumask;
unsigned long flags;
-@@ -298,6 +301,35 @@ static void irq_affinity_notify(struct work_struct *work)
+@@ -298,6 +301,35 @@ out:
kref_put(¬ify->kref, notify->release);
}
@@ -142,3 +142,6 @@ index 562df8dc14be..5f14e0d7c0c7 100644
}
raw_spin_lock_irqsave(&desc->lock, flags);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0202-hrtimer-Move-schedule_work-call-to-helper-thread.patch b/debian/patches/features/all/rt/0202-hrtimer-Move-schedule_work-call-to-helper-thread.patch
index e829406..bd17dc3 100644
--- a/debian/patches/features/all/rt/0202-hrtimer-Move-schedule_work-call-to-helper-thread.patch
+++ b/debian/patches/features/all/rt/0202-hrtimer-Move-schedule_work-call-to-helper-thread.patch
@@ -1,7 +1,7 @@
From: Yang Shi <yang.shi at windriver.com>
Date: Mon, 16 Sep 2013 14:09:19 -0700
Subject: [PATCH 202/351] hrtimer: Move schedule_work call to helper thread
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3faa57c11f1d08ed370e5ca73e7ccc8381f98987
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6ea2ef8334ed97251a3e60459ab75275149e090e
When run ltp leapsec_timer test, the following call trace is caught:
@@ -92,3 +92,6 @@ index 0ac7cd65a163..4bd08d62151d 100644
#else
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0203-locking-percpu-rwsem-Remove-preempt_disable-variants.patch b/debian/patches/features/all/rt/0203-locking-percpu-rwsem-Remove-preempt_disable-variants.patch
index 8324ee7..a5267db 100644
--- a/debian/patches/features/all/rt/0203-locking-percpu-rwsem-Remove-preempt_disable-variants.patch
+++ b/debian/patches/features/all/rt/0203-locking-percpu-rwsem-Remove-preempt_disable-variants.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 23 Nov 2016 16:29:32 +0100
Subject: [PATCH 203/351] locking/percpu-rwsem: Remove preempt_disable variants
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3cd88a296ed3973a3f2d2d82e34bbba6ddd013da
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2381562be08f61925fe295f141f273c74f4320fd
Effective revert commit:
@@ -29,7 +29,7 @@ index 22c5b4aa4961..269c6a44449a 100644
spin_lock(&ctx->flc_lock);
if (request->fl_flags & FL_ACCESS)
goto find_conflict;
-@@ -976,7 +976,7 @@ static int flock_lock_inode(struct inode *inode, struct file_lock *request)
+@@ -976,7 +976,7 @@ find_conflict:
out:
spin_unlock(&ctx->flc_lock);
@@ -65,7 +65,7 @@ index 22c5b4aa4961..269c6a44449a 100644
spin_lock(&ctx->flc_lock);
time_out_leases(inode, &dispose);
-@@ -1512,13 +1512,13 @@ int __break_lease(struct inode *inode, unsigned int mode, unsigned int type)
+@@ -1512,13 +1512,13 @@ restart:
locks_insert_block(fl, new_fl);
trace_break_lease_block(inode, new_fl);
spin_unlock(&ctx->flc_lock);
@@ -81,7 +81,7 @@ index 22c5b4aa4961..269c6a44449a 100644
spin_lock(&ctx->flc_lock);
trace_break_lease_unblock(inode, new_fl);
locks_delete_block(new_fl);
-@@ -1535,7 +1535,7 @@ int __break_lease(struct inode *inode, unsigned int mode, unsigned int type)
+@@ -1535,7 +1535,7 @@ restart:
}
out:
spin_unlock(&ctx->flc_lock);
@@ -117,7 +117,7 @@ index 22c5b4aa4961..269c6a44449a 100644
spin_lock(&ctx->flc_lock);
time_out_leases(inode, &dispose);
error = check_conflicting_open(dentry, arg, lease->fl_flags);
-@@ -1765,7 +1765,7 @@ generic_add_lease(struct file *filp, long arg, struct file_lock **flp, void **pr
+@@ -1765,7 +1765,7 @@ out_setup:
lease->fl_lmops->lm_setup(lease, priv);
out:
spin_unlock(&ctx->flc_lock);
@@ -220,3 +220,6 @@ index 82d54a4b9988..ea940f451606 100644
extern void percpu_down_write(struct percpu_rw_semaphore *);
extern void percpu_up_write(struct percpu_rw_semaphore *);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0204-fs-namespace-preemption-fix.patch b/debian/patches/features/all/rt/0204-fs-namespace-preemption-fix.patch
index 27a84d9..15c699d 100644
--- a/debian/patches/features/all/rt/0204-fs-namespace-preemption-fix.patch
+++ b/debian/patches/features/all/rt/0204-fs-namespace-preemption-fix.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 19 Jul 2009 08:44:27 -0500
Subject: [PATCH 204/351] fs: namespace preemption fix
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7d6de0d7098fe1f886968f180a667543ab0b9f29
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=da3da7414a5c976fe409963d3c185c55327e310b
On RT we cannot loop with preemption disabled here as
mnt_make_readonly() might have been preempted. We can safely enable
@@ -30,3 +30,6 @@ index d7360f9897b4..295b02091d1f 100644
/*
* After the slowpath clears MNT_WRITE_HOLD, mnt_is_readonly will
* be set to match its requirements. So we must not load that until
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0205-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch b/debian/patches/features/all/rt/0205-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch
index 2027e5d..1ebdf82 100644
--- a/debian/patches/features/all/rt/0205-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch
+++ b/debian/patches/features/all/rt/0205-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch
@@ -2,7 +2,7 @@ From: Yong Zhang <yong.zhang0 at gmail.com>
Date: Tue, 15 May 2012 13:53:56 +0800
Subject: [PATCH 205/351] mm: Protect activate_mm() by
preempt_[disable&enable]_rt()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e8bfe7ea326d36b8c5a8121fe6b617cfc9c00b6d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=095b26f0406e10065661986f4eebc324abeeac78
User preempt_*_rt instead of local_irq_*_rt or otherwise there will be
warning on ARM like below:
@@ -75,3 +75,6 @@ index 6f4d27c5bb32..5cd25c745a8f 100644
task_unlock(tsk);
#ifdef finish_arch_post_lock_switch
finish_arch_post_lock_switch();
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0206-block-Turn-off-warning-which-is-bogus-on-RT.patch b/debian/patches/features/all/rt/0206-block-Turn-off-warning-which-is-bogus-on-RT.patch
index 084c2dc..c30f476 100644
--- a/debian/patches/features/all/rt/0206-block-Turn-off-warning-which-is-bogus-on-RT.patch
+++ b/debian/patches/features/all/rt/0206-block-Turn-off-warning-which-is-bogus-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 14 Jun 2011 17:05:09 +0200
Subject: [PATCH 206/351] block: Turn off warning which is bogus on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0cfcd5218dd65049b69bd53aaafa4fef28a01d65
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0baea4b0ec11c97642a11853d82eb91b514407ac
On -RT the context is always with IRQs enabled. Ignore this warning on -RT.
@@ -11,7 +11,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/blk-core.c b/block/blk-core.c
-index 6ca17282da87..9d70e3d27f74 100644
+index d24e2e651775..ed5a0e92c718 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -233,7 +233,7 @@ EXPORT_SYMBOL(blk_start_queue_async);
@@ -23,3 +23,6 @@ index 6ca17282da87..9d70e3d27f74 100644
queue_flag_clear(QUEUE_FLAG_STOPPED, q);
__blk_run_queue(q);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0207-fs-ntfs-disable-interrupt-only-on-RT.patch b/debian/patches/features/all/rt/0207-fs-ntfs-disable-interrupt-only-on-RT.patch
index 025a6a7..449abe1 100644
--- a/debian/patches/features/all/rt/0207-fs-ntfs-disable-interrupt-only-on-RT.patch
+++ b/debian/patches/features/all/rt/0207-fs-ntfs-disable-interrupt-only-on-RT.patch
@@ -1,7 +1,7 @@
From: Mike Galbraith <efault at gmx.de>
Date: Fri, 3 Jul 2009 08:44:12 -0500
Subject: [PATCH 207/351] fs: ntfs: disable interrupt only on !RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=44355bff88c128e750c2005a2f3d6252e7b809fe
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1b9925bc457d940138739905c0450faf460def41
On Sat, 2007-10-27 at 11:44 +0200, Ingo Molnar wrote:
> * Nick Piggin <nickpiggin at yahoo.com.au> wrote:
@@ -75,3 +75,6 @@ index 8bb79f5fda59..e89da4fb14c2 100644
flush_dcache_page(page);
if (likely(page_uptodate && !PageError(page)))
SetPageUptodate(page);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0208-fs-jbd2-pull-your-plug-when-waiting-for-space.patch b/debian/patches/features/all/rt/0208-fs-jbd2-pull-your-plug-when-waiting-for-space.patch
index 12bebf8..7184655 100644
--- a/debian/patches/features/all/rt/0208-fs-jbd2-pull-your-plug-when-waiting-for-space.patch
+++ b/debian/patches/features/all/rt/0208-fs-jbd2-pull-your-plug-when-waiting-for-space.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 17 Feb 2014 17:30:03 +0100
Subject: [PATCH 208/351] fs: jbd2: pull your plug when waiting for space
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e88fa76dcd3daf908ca6be92231f2307d8d9d16d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b4a3553c21b74accb8205d1db7d5cebf931a7f10
Two cps in parallel managed to stall the the ext4 fs. It seems that
journal code is either waiting for locks or sleeping waiting for
@@ -32,3 +32,6 @@ index 684996c8a3a4..6e18a06aaabe 100644
mutex_lock(&journal->j_checkpoint_mutex);
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0209-x86-Convert-mce-timer-to-hrtimer.patch b/debian/patches/features/all/rt/0209-x86-Convert-mce-timer-to-hrtimer.patch
index ba045cd..e72f352 100644
--- a/debian/patches/features/all/rt/0209-x86-Convert-mce-timer-to-hrtimer.patch
+++ b/debian/patches/features/all/rt/0209-x86-Convert-mce-timer-to-hrtimer.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 13 Dec 2010 16:33:39 +0100
Subject: [PATCH 209/351] x86: Convert mce timer to hrtimer
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b4856cb2ca459dfa88471705147165586bc673bb
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fc5d2333fd0812f6d63c6da1f9f26ed89afb0999
mce_timer is started in atomic contexts of cpu bringup. This results
in might_sleep() warnings on RT. Convert mce_timer to a hrtimer to
@@ -94,7 +94,7 @@ index 8ca5f8ad008e..d9fab6408357 100644
}
/*
-@@ -1371,7 +1358,7 @@ static void mce_timer_fn(unsigned long data)
+@@ -1371,7 +1358,7 @@ done:
*/
void mce_timer_kick(unsigned long interval)
{
@@ -180,3 +180,6 @@ index 8ca5f8ad008e..d9fab6408357 100644
break;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0210-x86-mce-use-swait-queue-for-mce-wakeups.patch b/debian/patches/features/all/rt/0210-x86-mce-use-swait-queue-for-mce-wakeups.patch
index c10cfc1..3f6c45f 100644
--- a/debian/patches/features/all/rt/0210-x86-mce-use-swait-queue-for-mce-wakeups.patch
+++ b/debian/patches/features/all/rt/0210-x86-mce-use-swait-queue-for-mce-wakeups.patch
@@ -1,7 +1,7 @@
From: Steven Rostedt <rostedt at goodmis.org>
Date: Fri, 27 Feb 2015 15:20:37 +0100
Subject: [PATCH 210/351] x86/mce: use swait queue for mce wakeups
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=599e2c48e126db7663f3e045f64436cdbadf4f00
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1ae6e2788dc52260432420cf7bfba41014bbbb35
We had a customer report a lockup on a 3.0-rt kernel that had the
following backtrace:
@@ -160,3 +160,6 @@ index d9fab6408357..edcbd18b3189 100644
if (!zalloc_cpumask_var(&mce_device_initialized, GFP_KERNEL)) {
err = -ENOMEM;
goto err_out;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0211-x86-stackprotector-Avoid-random-pool-on-rt.patch b/debian/patches/features/all/rt/0211-x86-stackprotector-Avoid-random-pool-on-rt.patch
index 4b6c90c..31609e2 100644
--- a/debian/patches/features/all/rt/0211-x86-stackprotector-Avoid-random-pool-on-rt.patch
+++ b/debian/patches/features/all/rt/0211-x86-stackprotector-Avoid-random-pool-on-rt.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 16 Dec 2010 14:25:18 +0100
Subject: [PATCH 211/351] x86: stackprotector: Avoid random pool on rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=79d9eb5be9d1be9f30b1849abe0d69b492a45b63
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8a45ec3560f0a52a3875928ea8723e68c65aaf00
CPU bringup calls into the random pool to initialize the stack
canary. During boot that works nicely even on RT as the might sleep
@@ -46,3 +46,6 @@ index 58505f01962f..02fa39652cd6 100644
tsc = rdtsc();
canary += tsc + (tsc << 32UL);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0212-x86-Use-generic-rwsem_spinlocks-on-rt.patch b/debian/patches/features/all/rt/0212-x86-Use-generic-rwsem_spinlocks-on-rt.patch
index ec9aa2e..945b21c 100644
--- a/debian/patches/features/all/rt/0212-x86-Use-generic-rwsem_spinlocks-on-rt.patch
+++ b/debian/patches/features/all/rt/0212-x86-Use-generic-rwsem_spinlocks-on-rt.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 26 Jul 2009 02:21:32 +0200
Subject: [PATCH 212/351] x86: Use generic rwsem_spinlocks on -rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8c9a625db9ea233fc1c756ae27f12f0356e677f2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fe40d30e84a0a09272e6afc3cb95e3b0d696f388
Simplifies the separation of anon_rw_semaphores and rw_semaphores for
-rt.
@@ -12,7 +12,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
-index b9c546a305a4..88c67b3a25a4 100644
+index da8156fd3d58..b7a8745c8083 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -232,8 +232,11 @@ config ARCH_MAY_HAVE_PC_FDC
@@ -28,3 +28,6 @@ index b9c546a305a4..88c67b3a25a4 100644
config GENERIC_CALIBRATE_DELAY
def_bool y
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0213-x86-UV-raw_spinlock-conversion.patch b/debian/patches/features/all/rt/0213-x86-UV-raw_spinlock-conversion.patch
index c4b437d..0eb72eb 100644
--- a/debian/patches/features/all/rt/0213-x86-UV-raw_spinlock-conversion.patch
+++ b/debian/patches/features/all/rt/0213-x86-UV-raw_spinlock-conversion.patch
@@ -1,7 +1,7 @@
From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Sun, 2 Nov 2014 08:31:37 +0100
Subject: [PATCH 213/351] x86: UV: raw_spinlock conversion
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c7a7c75f834180f08f88d4310facc6bca4e3286d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=43163e21a5e4328d1b217db98174dfe351ac8f6a
Shrug. Lots of hobbyists have a beast in their basement, right?
@@ -52,7 +52,7 @@ index 57ab86d94d64..35d25e27180f 100644
}
diff --git a/arch/x86/platform/uv/tlb_uv.c b/arch/x86/platform/uv/tlb_uv.c
-index 9e42842e924a..5398f97172f9 100644
+index 0f0175186f1b..39b5d5b2627d 100644
--- a/arch/x86/platform/uv/tlb_uv.c
+++ b/arch/x86/platform/uv/tlb_uv.c
@@ -748,9 +748,9 @@ static void destination_plugged(struct bau_desc *bau_desc,
@@ -128,7 +128,7 @@ index 9e42842e924a..5398f97172f9 100644
return -1;
}
-@@ -1940,9 +1940,9 @@ static void __init init_per_cpu_tunables(void)
+@@ -1939,9 +1939,9 @@ static void __init init_per_cpu_tunables(void)
bcp->cong_reps = congested_reps;
bcp->disabled_period = sec_2_cycles(disabled_period);
bcp->giveup_limit = giveup_limit;
@@ -225,3 +225,6 @@ index b333fc45f9ec..8b85916e6986 100644
}
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0214-thermal-Defer-thermal-wakups-to-threads.patch b/debian/patches/features/all/rt/0214-thermal-Defer-thermal-wakups-to-threads.patch
index e463bc8..7d9c20c 100644
--- a/debian/patches/features/all/rt/0214-thermal-Defer-thermal-wakups-to-threads.patch
+++ b/debian/patches/features/all/rt/0214-thermal-Defer-thermal-wakups-to-threads.patch
@@ -1,7 +1,7 @@
From: Daniel Wagner <wagi at monom.org>
Date: Tue, 17 Feb 2015 09:37:44 +0100
Subject: [PATCH 214/351] thermal: Defer thermal wakups to threads
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8890b285e7bbe0399acc9769b3747d5f40721510
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=cb01363f3e7f68880927b0d8c7a4c3965824a2e8
On RT the spin lock in pkg_temp_thermal_platfrom_thermal_notify will
call schedule while we run in irq context.
@@ -116,7 +116,7 @@ index 95f4c1bcdb4c..0be934799bff 100644
spin_lock_init(&pkg_work_lock);
platform_thermal_package_notify =
pkg_temp_thermal_platform_thermal_notify;
-@@ -609,7 +652,7 @@ static int __init pkg_temp_thermal_init(void)
+@@ -609,7 +652,7 @@ err_ret:
kfree(pkg_work_scheduled);
platform_thermal_package_notify = NULL;
platform_thermal_package_rate_control = NULL;
@@ -133,3 +133,6 @@ index 95f4c1bcdb4c..0be934799bff 100644
for_each_online_cpu(i)
cancel_delayed_work_sync(
&per_cpu(pkg_temp_thermal_threshold_work, i));
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0215-fs-epoll-Do-not-disable-preemption-on-RT.patch b/debian/patches/features/all/rt/0215-fs-epoll-Do-not-disable-preemption-on-RT.patch
index d685ac0..c8349db 100644
--- a/debian/patches/features/all/rt/0215-fs-epoll-Do-not-disable-preemption-on-RT.patch
+++ b/debian/patches/features/all/rt/0215-fs-epoll-Do-not-disable-preemption-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 8 Jul 2011 16:35:35 +0200
Subject: [PATCH 215/351] fs/epoll: Do not disable preemption on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=86c983ae33d605addc6a030fc87a51d2c44e7a58
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=63e07b7b6f9292416d0c250ba389abef3bc510eb
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
@@ -31,3 +31,6 @@ index 3cbc30413add..41a94f552aab 100644
}
static void ep_remove_wait_queue(struct eppoll_entry *pwq)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0216-mm-vmalloc-Another-preempt-disable-region-which-suck.patch b/debian/patches/features/all/rt/0216-mm-vmalloc-Another-preempt-disable-region-which-suck.patch
index 1ea0e26..0c74a61 100644
--- a/debian/patches/features/all/rt/0216-mm-vmalloc-Another-preempt-disable-region-which-suck.patch
+++ b/debian/patches/features/all/rt/0216-mm-vmalloc-Another-preempt-disable-region-which-suck.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 12 Jul 2011 11:39:36 +0200
Subject: [PATCH 216/351] mm/vmalloc: Another preempt disable region which
sucks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6a34fa4868e9a19a6cda4ffb2cefe7c8d1afd238
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=449c95f465093b808c257bd3fd92ad44479db85f
Avoid the preempt disable version of get_cpu_var(). The inner-lock should
provide enough serialisation.
@@ -67,3 +67,6 @@ index 195de42bea1f..b46cb686fde7 100644
rcu_read_unlock();
/* Allocate new block if nothing was found */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0217-block-mq-use-cpu_light.patch b/debian/patches/features/all/rt/0217-block-mq-use-cpu_light.patch
index fe8e6af..ab0fd2d 100644
--- a/debian/patches/features/all/rt/0217-block-mq-use-cpu_light.patch
+++ b/debian/patches/features/all/rt/0217-block-mq-use-cpu_light.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 9 Apr 2014 10:37:23 +0200
Subject: [PATCH 217/351] block: mq: use cpu_light()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4995cf457c8a65fcabe167bd8e76a4fa981adcb1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=612beef9b644d2b3c74d4cb045860c5e02c5dfe0
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().
@@ -12,10 +12,10 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/blk-mq.h b/block/blk-mq.h
-index e5d25249028c..1e846b842eab 100644
+index c55bcf67b956..c26a84d44cc4 100644
--- a/block/blk-mq.h
+++ b/block/blk-mq.h
-@@ -72,12 +72,12 @@ static inline struct blk_mq_ctx *__blk_mq_get_ctx(struct request_queue *q,
+@@ -73,12 +73,12 @@ static inline struct blk_mq_ctx *__blk_mq_get_ctx(struct request_queue *q,
*/
static inline struct blk_mq_ctx *blk_mq_get_ctx(struct request_queue *q)
{
@@ -30,3 +30,6 @@ index e5d25249028c..1e846b842eab 100644
}
struct blk_mq_alloc_data {
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0218-block-mq-do-not-invoke-preempt_disable.patch b/debian/patches/features/all/rt/0218-block-mq-do-not-invoke-preempt_disable.patch
index fba59cc..3f84d08 100644
--- a/debian/patches/features/all/rt/0218-block-mq-do-not-invoke-preempt_disable.patch
+++ b/debian/patches/features/all/rt/0218-block-mq-do-not-invoke-preempt_disable.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Tue, 14 Jul 2015 14:26:34 +0200
Subject: [PATCH 218/351] block/mq: do not invoke preempt_disable()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e93f2bf68d6b3a43c534c1cff63c369f9a36897f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9e79e29df9866e11cb88363099a9729dc6c93307
preempt_disable() and get_cpu() don't play well together with the sleeping
locks it tries to allocate later.
@@ -13,7 +13,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/block/blk-mq.c b/block/blk-mq.c
-index 7b597ec4e9c5..1be09013d7ff 100644
+index 10f8f94b7f20..e8671fcf2a68 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -363,7 +363,7 @@ static void blk_mq_ipi_complete_request(struct request *rq)
@@ -52,3 +52,6 @@ index 7b597ec4e9c5..1be09013d7ff 100644
}
kblockd_schedule_work_on(blk_mq_hctx_next_cpu(hctx), &hctx->run_work);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0219-block-mq-don-t-complete-requests-via-IPI.patch b/debian/patches/features/all/rt/0219-block-mq-don-t-complete-requests-via-IPI.patch
index af46598..54b0f55 100644
--- a/debian/patches/features/all/rt/0219-block-mq-don-t-complete-requests-via-IPI.patch
+++ b/debian/patches/features/all/rt/0219-block-mq-don-t-complete-requests-via-IPI.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 29 Jan 2015 15:10:08 +0100
Subject: [PATCH 219/351] block/mq: don't complete requests via IPI
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c964c3696f88eec45bf4cb6655fbe0583cff81a2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f723d2bd5fd9d1e66cdd861a221604518dc8188e
The IPI runs in hardirq context and there are sleeping locks. This patch
moves the completion into a workqueue.
@@ -15,7 +15,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
4 files changed, 25 insertions(+), 1 deletion(-)
diff --git a/block/blk-core.c b/block/blk-core.c
-index 9d70e3d27f74..1ff9fbcbe320 100644
+index ed5a0e92c718..a36124682875 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -125,6 +125,9 @@ void blk_rq_init(struct request_queue *q, struct request *rq)
@@ -29,7 +29,7 @@ index 9d70e3d27f74..1ff9fbcbe320 100644
rq->q = q;
rq->__sector = (sector_t) -1;
diff --git a/block/blk-mq.c b/block/blk-mq.c
-index 1be09013d7ff..c7bc5e66330d 100644
+index e8671fcf2a68..e26bbdff3735 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -177,6 +177,9 @@ static void blk_mq_rq_ctx_init(struct request_queue *q, struct blk_mq_ctx *ctx,
@@ -109,3 +109,6 @@ index f6a816129856..3b519c3a498e 100644
u64 fifo_time;
};
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0220-md-raid5-Make-raid5_percpu-handling-RT-aware.patch b/debian/patches/features/all/rt/0220-md-raid5-Make-raid5_percpu-handling-RT-aware.patch
index 2f12a20..8451ab9 100644
--- a/debian/patches/features/all/rt/0220-md-raid5-Make-raid5_percpu-handling-RT-aware.patch
+++ b/debian/patches/features/all/rt/0220-md-raid5-Make-raid5_percpu-handling-RT-aware.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 6 Apr 2010 16:51:31 +0200
Subject: [PATCH 220/351] md: raid5: Make raid5_percpu handling RT aware
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=807eefa6420c86fab6734776b6447a4e38d9a0d7
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f11b4f9ce39bc486cf6f007d51bccb484a788839
__raid_run_ops() disables preemption with get_cpu() around the access
to the raid5_percpu variables. That causes scheduling while atomic
@@ -19,10 +19,10 @@ Tested-by: Udo van den Heuvel <udovdh at xs4all.nl>
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
-index 7aea0221530c..4d8cfce1de86 100644
+index 475a7a1bcfe0..710bb5d009a8 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
-@@ -1934,8 +1934,9 @@ static void raid_run_ops(struct stripe_head *sh, unsigned long ops_request)
+@@ -1937,8 +1937,9 @@ static void raid_run_ops(struct stripe_head *sh, unsigned long ops_request)
struct raid5_percpu *percpu;
unsigned long cpu;
@@ -33,7 +33,7 @@ index 7aea0221530c..4d8cfce1de86 100644
if (test_bit(STRIPE_OP_BIOFILL, &ops_request)) {
ops_run_biofill(sh);
overlap_clear++;
-@@ -1991,7 +1992,8 @@ static void raid_run_ops(struct stripe_head *sh, unsigned long ops_request)
+@@ -1994,7 +1995,8 @@ static void raid_run_ops(struct stripe_head *sh, unsigned long ops_request)
if (test_and_clear_bit(R5_Overlap, &dev->flags))
wake_up(&sh->raid_conf->wait_for_overlap);
}
@@ -43,7 +43,7 @@ index 7aea0221530c..4d8cfce1de86 100644
}
static struct stripe_head *alloc_stripe(struct kmem_cache *sc, gfp_t gfp,
-@@ -6407,6 +6409,7 @@ static int raid456_cpu_up_prepare(unsigned int cpu, struct hlist_node *node)
+@@ -6410,6 +6412,7 @@ static int raid456_cpu_up_prepare(unsigned int cpu, struct hlist_node *node)
__func__, cpu);
return -ENOMEM;
}
@@ -51,7 +51,7 @@ index 7aea0221530c..4d8cfce1de86 100644
return 0;
}
-@@ -6417,7 +6420,6 @@ static int raid5_alloc_percpu(struct r5conf *conf)
+@@ -6420,7 +6423,6 @@ static int raid5_alloc_percpu(struct r5conf *conf)
conf->percpu = alloc_percpu(struct raid5_percpu);
if (!conf->percpu)
return -ENOMEM;
@@ -71,3 +71,6 @@ index 57ec49f0839e..0739604990b7 100644
struct page *spare_page; /* Used when checking P/Q in raid6 */
struct flex_array *scribble; /* space for constructing buffer
* lists and performing address
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0221-rt-Introduce-cpu_chill.patch b/debian/patches/features/all/rt/0221-rt-Introduce-cpu_chill.patch
index f7d2360..9294b0d 100644
--- a/debian/patches/features/all/rt/0221-rt-Introduce-cpu_chill.patch
+++ b/debian/patches/features/all/rt/0221-rt-Introduce-cpu_chill.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 7 Mar 2012 20:51:03 +0100
Subject: [PATCH 221/351] rt: Introduce cpu_chill()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8a90e2f63a0d3634549561fbe5a68766b7f0dc61
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=54d4cf381c2f94bb088c104d770e72a0460b28bd
Retry loops on RT might loop forever when the modifying side was
preempted. Add cpu_chill() to replace cpu_relax(). cpu_chill()
@@ -131,3 +131,6 @@ index 4bd08d62151d..73b62329b722 100644
/*
* Functions related to boot-time initialization:
*/
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0222-cpu_chill-Add-a-UNINTERRUPTIBLE-hrtimer_nanosleep.patch b/debian/patches/features/all/rt/0222-cpu_chill-Add-a-UNINTERRUPTIBLE-hrtimer_nanosleep.patch
index 86f86fd..60435f9 100644
--- a/debian/patches/features/all/rt/0222-cpu_chill-Add-a-UNINTERRUPTIBLE-hrtimer_nanosleep.patch
+++ b/debian/patches/features/all/rt/0222-cpu_chill-Add-a-UNINTERRUPTIBLE-hrtimer_nanosleep.patch
@@ -1,7 +1,7 @@
From: Steven Rostedt <rostedt at goodmis.org>
Date: Tue, 4 Mar 2014 12:28:32 -0500
Subject: [PATCH 222/351] cpu_chill: Add a UNINTERRUPTIBLE hrtimer_nanosleep
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b1da223b42215b141707dd955d839a0dadd99019
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=978af46238db61018ec1ad2e6a8a11f8d6212952
We hit another bug that was caused by switching cpu_chill() from
msleep() to hrtimer_nanosleep().
@@ -62,7 +62,7 @@ index 73b62329b722..0797bd6eadb4 100644
goto out;
rmtp = restart->nanosleep.rmtp;
-@@ -1723,8 +1725,10 @@ long __sched hrtimer_nanosleep_restart(struct restart_block *restart)
+@@ -1723,8 +1725,10 @@ out:
return ret;
}
@@ -84,7 +84,7 @@ index 73b62329b722..0797bd6eadb4 100644
goto out;
/* Absolute timers do not update the rmtp value and restart: */
-@@ -1764,6 +1768,12 @@ long hrtimer_nanosleep(struct timespec *rqtp, struct timespec __user *rmtp,
+@@ -1764,6 +1768,12 @@ out:
return ret;
}
@@ -107,3 +107,6 @@ index 73b62329b722..0797bd6eadb4 100644
if (!freeze_flag)
current->flags &= ~PF_NOFREEZE;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0223-block-blk-mq-Use-swait.patch b/debian/patches/features/all/rt/0223-block-blk-mq-Use-swait.patch
index d723dc2..d6f4e93 100644
--- a/debian/patches/features/all/rt/0223-block-blk-mq-Use-swait.patch
+++ b/debian/patches/features/all/rt/0223-block-blk-mq-Use-swait.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 13 Feb 2015 11:01:26 +0100
Subject: [PATCH 223/351] block: blk-mq: Use swait
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4015dace9fb83207d95049fcdbbf01fa008a61ef
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=dae952cdaff7dc43087149d7671f04e9978efc21
| 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
@@ -45,7 +45,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/block/blk-core.c b/block/blk-core.c
-index 1ff9fbcbe320..5808a85a7974 100644
+index a36124682875..e8341f78f119 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -663,7 +663,7 @@ int blk_queue_enter(struct request_queue *q, bool nowait)
@@ -76,7 +76,7 @@ index 1ff9fbcbe320..5808a85a7974 100644
/*
* Init percpu_ref in atomic mode so that it's faster to shutdown.
diff --git a/block/blk-mq.c b/block/blk-mq.c
-index c7bc5e66330d..48c9652a701c 100644
+index e26bbdff3735..82500641f37b 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -72,7 +72,7 @@ EXPORT_SYMBOL_GPL(blk_mq_freeze_queue_start);
@@ -119,3 +119,6 @@ index 3b519c3a498e..ec7a4676f8a8 100644
struct percpu_ref q_usage_counter;
struct list_head all_q_node;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0224-block-Use-cpu_chill-for-retry-loops.patch b/debian/patches/features/all/rt/0224-block-Use-cpu_chill-for-retry-loops.patch
index 2fe1c6a..a205891 100644
--- a/debian/patches/features/all/rt/0224-block-Use-cpu_chill-for-retry-loops.patch
+++ b/debian/patches/features/all/rt/0224-block-Use-cpu_chill-for-retry-loops.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 20 Dec 2012 18:28:26 +0100
Subject: [PATCH 224/351] block: Use cpu_chill() for retry loops
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d0adc2ca37964a2e5b5573c2f4f1730027afd9a6
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=78f5268662ed145d9eab8b2f0b508e5a16e84518
Retry loops on RT might loop forever when the modifying side was
preempted. Steven also observed a live lock when there was a
@@ -36,7 +36,7 @@ index 381cb50a673c..dc8785233d94 100644
spin_lock_irqsave_nested(&ioc->lock, flags, 1);
}
}
-@@ -187,7 +188,7 @@ void put_io_context_active(struct io_context *ioc)
+@@ -187,7 +188,7 @@ retry:
spin_unlock(icq->q->queue_lock);
} else {
spin_unlock_irqrestore(&ioc->lock, flags);
@@ -45,3 +45,6 @@ index 381cb50a673c..dc8785233d94 100644
goto retry;
}
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0225-fs-dcache-Use-cpu_chill-in-trylock-loops.patch b/debian/patches/features/all/rt/0225-fs-dcache-Use-cpu_chill-in-trylock-loops.patch
index 5ecfff1..704a1bd 100644
--- a/debian/patches/features/all/rt/0225-fs-dcache-Use-cpu_chill-in-trylock-loops.patch
+++ b/debian/patches/features/all/rt/0225-fs-dcache-Use-cpu_chill-in-trylock-loops.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 7 Mar 2012 21:00:34 +0100
Subject: [PATCH 225/351] fs: dcache: Use cpu_chill() in trylock loops
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4ef996a87817b5c15ec6e9cf4ec9e3ad608d4587
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e48dafadb556e118cb5039dc3b42fed66a934819
Retry loops on RT might loop forever when the modifying side was
preempted. Use cpu_chill() instead of cpu_relax() to let the system
@@ -31,7 +31,7 @@ diff --git a/fs/autofs4/expire.c b/fs/autofs4/expire.c
index d8e6d421c27f..2e689ab1306b 100644
--- a/fs/autofs4/expire.c
+++ b/fs/autofs4/expire.c
-@@ -148,7 +148,7 @@ static struct dentry *get_next_positive_dentry(struct dentry *prev,
+@@ -148,7 +148,7 @@ again:
parent = p->d_parent;
if (!spin_trylock(&parent->d_lock)) {
spin_unlock(&p->d_lock);
@@ -61,7 +61,7 @@ index 10f848262852..112ef2773fe3 100644
if (unlikely(!dentry))
return;
-@@ -815,9 +818,18 @@ void dput(struct dentry *dentry)
+@@ -815,9 +818,18 @@ repeat:
return;
kill_it:
@@ -83,7 +83,7 @@ index 10f848262852..112ef2773fe3 100644
goto repeat;
}
}
-@@ -2352,7 +2364,7 @@ void d_delete(struct dentry * dentry)
+@@ -2352,7 +2364,7 @@ again:
if (dentry->d_lockref.count == 1) {
if (!spin_trylock(&inode->i_lock)) {
spin_unlock(&dentry->d_lock);
@@ -113,3 +113,6 @@ index 295b02091d1f..da188c6966a3 100644
preempt_disable();
}
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0226-net-Use-cpu_chill-instead-of-cpu_relax.patch b/debian/patches/features/all/rt/0226-net-Use-cpu_chill-instead-of-cpu_relax.patch
index a80bd5a..aacb9bd 100644
--- a/debian/patches/features/all/rt/0226-net-Use-cpu_chill-instead-of-cpu_relax.patch
+++ b/debian/patches/features/all/rt/0226-net-Use-cpu_chill-instead-of-cpu_relax.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 7 Mar 2012 21:10:04 +0100
Subject: [PATCH 226/351] net: Use cpu_chill() instead of cpu_relax()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5f3ff8158446f154b0cf0e302f07db92ef0db443
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=aab0e3bfd1e6a680f8c5c91948e9075dcaa2a25c
Retry loops on RT might loop forever when the modifying side was
preempted. Use cpu_chill() instead of cpu_relax() to let the system
@@ -14,7 +14,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c
-index e7f6657269e0..f635b773d28f 100644
+index 267db0d603bc..00994de54d57 100644
--- a/net/packet/af_packet.c
+++ b/net/packet/af_packet.c
@@ -63,6 +63,7 @@
@@ -64,3 +64,6 @@ index 977f69886c00..f3e7a36b0396 100644
}
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0227-fs-dcache-use-swait_queue-instead-of-waitqueue.patch b/debian/patches/features/all/rt/0227-fs-dcache-use-swait_queue-instead-of-waitqueue.patch
index 3da9dde..a2492c9 100644
--- a/debian/patches/features/all/rt/0227-fs-dcache-use-swait_queue-instead-of-waitqueue.patch
+++ b/debian/patches/features/all/rt/0227-fs-dcache-use-swait_queue-instead-of-waitqueue.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 14 Sep 2016 14:35:49 +0200
Subject: [PATCH 227/351] fs/dcache: use swait_queue instead of waitqueue
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=db8a4c70e86b558691babe8b6afdce311ccf840c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=24c7fe99a845f6453c0effe78f40bf51af529ead
__d_lookup_done() invokes wake_up_all() while holding a hlist_bl_lock()
which disables preemption. As a workaround convert it to swait.
@@ -119,7 +119,7 @@ index e7d125c23aa6..072a2f724437 100644
if (unlikely(IS_DEADDIR(dir_inode)))
return -ENOENT;
diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
-index c1cc9707bbb3..5f08183dddcd 100644
+index 24c0a094d61e..2510f2be8557 100644
--- a/fs/nfs/dir.c
+++ b/fs/nfs/dir.c
@@ -485,7 +485,7 @@ static
@@ -235,3 +235,6 @@ index e2e224c59c0a..ef027ff3250a 100644
raw_spin_lock_irq(&q->lock);
list_splice_init(&q->task_list, &tmp);
while (!list_empty(&tmp)) {
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0231-sched-Distangle-worker-accounting-from-rqlock.patch b/debian/patches/features/all/rt/0231-sched-Distangle-worker-accounting-from-rqlock.patch
index fbd030c..d1955af 100644
--- a/debian/patches/features/all/rt/0231-sched-Distangle-worker-accounting-from-rqlock.patch
+++ b/debian/patches/features/all/rt/0231-sched-Distangle-worker-accounting-from-rqlock.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 22 Jun 2011 19:47:03 +0200
Subject: [PATCH 231/351] sched: Distangle worker accounting from rqlock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=35cca0b9744eedfa527ca8814429dfe375eb898d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b4dc9dc2358796a570687c5430d5e8373d514a83
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
@@ -44,7 +44,7 @@ index 13cf7061ee36..63f536082449 100644
}
/*
-@@ -2163,53 +2159,6 @@ try_to_wake_up(struct task_struct *p, unsigned int state, int wake_flags)
+@@ -2163,53 +2159,6 @@ out:
return success;
}
@@ -157,7 +157,7 @@ index 13cf7061ee36..63f536082449 100644
EXPORT_SYMBOL(schedule);
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
-index 707f56db71c8..4bb9113bd1f9 100644
+index 4b4b49654445..618ce6bae95a 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -842,43 +842,32 @@ static void wake_up_worker(struct worker_pool *pool)
@@ -273,3 +273,6 @@ index 29fa81f0f51a..42d1e3974554 100644
+void wq_worker_sleeping(struct task_struct *task);
#endif /* _KERNEL_WORKQUEUE_INTERNAL_H */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0232-idr-Use-local-lock-instead-of-preempt-enable-disable.patch b/debian/patches/features/all/rt/0232-idr-Use-local-lock-instead-of-preempt-enable-disable.patch
index ea85e8e..53f0de6 100644
--- a/debian/patches/features/all/rt/0232-idr-Use-local-lock-instead-of-preempt-enable-disable.patch
+++ b/debian/patches/features/all/rt/0232-idr-Use-local-lock-instead-of-preempt-enable-disable.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 14 Jul 2015 14:26:34 +0200
Subject: [PATCH 232/351] idr: Use local lock instead of preempt enable/disable
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=df3234134973c51c30568cc369d2f3cebfc1094f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=51c9294253f9fb87a5a3d324c20f1c31d172ac00
We need to protect the per cpu variable and prevent migration.
@@ -126,3 +126,6 @@ index 6098336df267..9decbe914595 100644
if (!new)
break;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0233-percpu_ida-Use-local-locks.patch b/debian/patches/features/all/rt/0233-percpu_ida-Use-local-locks.patch
index 2ee4835..bb36744 100644
--- a/debian/patches/features/all/rt/0233-percpu_ida-Use-local-locks.patch
+++ b/debian/patches/features/all/rt/0233-percpu_ida-Use-local-locks.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 9 Apr 2014 11:58:17 +0200
Subject: [PATCH 233/351] percpu_ida: Use local locks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7eba5c7003680060bc596111c50de483d8ef8802
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e573f3d9e464f64a61238cb326829a4bffb4e41a
the local_irq_save() + spin_lock() does not work that well on -RT
@@ -102,3 +102,6 @@ index 6d40944960de..822a2c027e72 100644
return err;
}
EXPORT_SYMBOL_GPL(percpu_ida_for_each_free);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0234-debugobjects-Make-RT-aware.patch b/debian/patches/features/all/rt/0234-debugobjects-Make-RT-aware.patch
index 82bdd02..46358ad 100644
--- a/debian/patches/features/all/rt/0234-debugobjects-Make-RT-aware.patch
+++ b/debian/patches/features/all/rt/0234-debugobjects-Make-RT-aware.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 17 Jul 2011 21:41:35 +0200
Subject: [PATCH 234/351] debugobjects: Make RT aware
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=58b185bd6e77d2b3550d06b8cee894cbce9618c8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6f430c3dcf1664fa711cf6fb231201f34ff78d96
Avoid filling the pool / allocating memory with irqs off().
@@ -26,3 +26,6 @@ index 056052dc8e91..d8494e126de8 100644
db = get_bucket((unsigned long) addr);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0235-jump-label-disable-if-stop_machine-is-used.patch b/debian/patches/features/all/rt/0235-jump-label-disable-if-stop_machine-is-used.patch
index eefc428..ba1f926 100644
--- a/debian/patches/features/all/rt/0235-jump-label-disable-if-stop_machine-is-used.patch
+++ b/debian/patches/features/all/rt/0235-jump-label-disable-if-stop_machine-is-used.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 8 Jul 2015 17:14:48 +0200
Subject: [PATCH 235/351] jump-label: disable if stop_machine() is used
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f30dc44d998ceb1ccfc20b6c06ec23c97238480c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a8d462494ebeeed0538899226f615522c8fc3305
Some architectures are using stop_machine() while switching the opcode which
leads to latency spikes.
@@ -36,3 +36,6 @@ index b5d529fdffab..1703d4162857 100644
select HAVE_ARCH_KGDB if !CPU_ENDIAN_BE32 && MMU
select HAVE_ARCH_MMAP_RND_BITS if MMU
select HAVE_ARCH_SECCOMP_FILTER if (AEABI && !OABI_COMPAT)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0236-seqlock-Prevent-rt-starvation.patch b/debian/patches/features/all/rt/0236-seqlock-Prevent-rt-starvation.patch
index 49931bb..c2347ea 100644
--- a/debian/patches/features/all/rt/0236-seqlock-Prevent-rt-starvation.patch
+++ b/debian/patches/features/all/rt/0236-seqlock-Prevent-rt-starvation.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 22 Feb 2012 12:03:30 +0100
Subject: [PATCH 236/351] seqlock: Prevent rt starvation
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f8226c2aa283913281efd23706d51ef787b1c9a1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b087019fb48b4e859060cae456e9ee2ee842b15c
If a low prio writer gets preempted while holding the seqlock write
locked, a high prio reader spins forever on RT.
@@ -193,3 +193,6 @@ index 8b683841e574..bf656008f6e7 100644
const struct net_device *dev)
{
unsigned int seq;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0237-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch b/debian/patches/features/all/rt/0237-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch
index 7940514..0206e5c 100644
--- a/debian/patches/features/all/rt/0237-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch
+++ b/debian/patches/features/all/rt/0237-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Wed, 18 Feb 2015 16:05:28 +0100
Subject: [PATCH 237/351] sunrpc: Make svc_xprt_do_enqueue() use
get_cpu_light()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a3036feb3aac2cc8c4a207adcdcb15b8053fdb86
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0be5d32740a97c9862e99ed2e659cac04c669051
|BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:915
|in_atomic(): 1, irqs_disabled(): 0, pid: 3194, name: rpc.nfsd
@@ -46,7 +46,7 @@ index 9c9db55a0c1e..e6583b018a72 100644
pool = svc_pool_for_cpu(xprt->xpt_server, cpu);
atomic_long_inc(&pool->sp_stats.packets);
-@@ -432,7 +432,7 @@ void svc_xprt_do_enqueue(struct svc_xprt *xprt)
+@@ -432,7 +432,7 @@ redo_search:
atomic_long_inc(&pool->sp_stats.threads_woken);
wake_up_process(rqstp->rq_task);
@@ -55,7 +55,7 @@ index 9c9db55a0c1e..e6583b018a72 100644
goto out;
}
rcu_read_unlock();
-@@ -453,7 +453,7 @@ void svc_xprt_do_enqueue(struct svc_xprt *xprt)
+@@ -453,7 +453,7 @@ redo_search:
goto redo_search;
}
rqstp = NULL;
@@ -64,3 +64,6 @@ index 9c9db55a0c1e..e6583b018a72 100644
out:
trace_svc_xprt_do_enqueue(xprt, rqstp);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0238-net-Use-skbufhead-with-raw-lock.patch b/debian/patches/features/all/rt/0238-net-Use-skbufhead-with-raw-lock.patch
index 7f053fd..e79b6a6 100644
--- a/debian/patches/features/all/rt/0238-net-Use-skbufhead-with-raw-lock.patch
+++ b/debian/patches/features/all/rt/0238-net-Use-skbufhead-with-raw-lock.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 12 Jul 2011 15:38:34 +0200
Subject: [PATCH 238/351] net: Use skbufhead with raw lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=dec2aeb787791e57345571a64c65130d02050638
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8788c51d1cce4450ba46bd4c9e67fddfe77be3bd
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
@@ -52,7 +52,7 @@ index 601dfa849d30..dca387a8fa6b 100644
struct lock_class_key *class)
{
diff --git a/net/core/dev.c b/net/core/dev.c
-index 885db5d6613c..f39b2a53b716 100644
+index 01cde21ebf9a..9ff83f117a6b 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -211,14 +211,14 @@ static inline struct hlist_head *dev_index_hash(struct net *net, int ifindex)
@@ -72,7 +72,7 @@ index 885db5d6613c..f39b2a53b716 100644
#endif
}
-@@ -4348,7 +4348,7 @@ static void flush_backlog(struct work_struct *work)
+@@ -4349,7 +4349,7 @@ static void flush_backlog(struct work_struct *work)
skb_queue_walk_safe(&sd->input_pkt_queue, skb, tmp) {
if (skb->dev->reg_state == NETREG_UNREGISTERING) {
__skb_unlink(skb, &sd->input_pkt_queue);
@@ -81,7 +81,7 @@ index 885db5d6613c..f39b2a53b716 100644
input_queue_head_incr(sd);
}
}
-@@ -4358,11 +4358,14 @@ static void flush_backlog(struct work_struct *work)
+@@ -4359,11 +4359,14 @@ static void flush_backlog(struct work_struct *work)
skb_queue_walk_safe(&sd->process_queue, skb, tmp) {
if (skb->dev->reg_state == NETREG_UNREGISTERING) {
__skb_unlink(skb, &sd->process_queue);
@@ -97,7 +97,7 @@ index 885db5d6613c..f39b2a53b716 100644
}
static void flush_all_backlogs(void)
-@@ -4897,7 +4900,9 @@ static int process_backlog(struct napi_struct *napi, int quota)
+@@ -4898,7 +4901,9 @@ static int process_backlog(struct napi_struct *napi, int quota)
while (again) {
struct sk_buff *skb;
@@ -107,7 +107,7 @@ index 885db5d6613c..f39b2a53b716 100644
rcu_read_lock();
__netif_receive_skb(skb);
rcu_read_unlock();
-@@ -4905,9 +4910,9 @@ static int process_backlog(struct napi_struct *napi, int quota)
+@@ -4906,9 +4911,9 @@ static int process_backlog(struct napi_struct *napi, int quota)
if (++work >= quota)
return work;
@@ -118,7 +118,7 @@ index 885db5d6613c..f39b2a53b716 100644
rps_lock(sd);
if (skb_queue_empty(&sd->input_pkt_queue)) {
/*
-@@ -5249,13 +5254,21 @@ static __latent_entropy void net_rx_action(struct softirq_action *h)
+@@ -5250,13 +5255,21 @@ static __latent_entropy void net_rx_action(struct softirq_action *h)
struct softnet_data *sd = this_cpu_ptr(&softnet_data);
unsigned long time_limit = jiffies + 2;
int budget = netdev_budget;
@@ -140,7 +140,7 @@ index 885db5d6613c..f39b2a53b716 100644
for (;;) {
struct napi_struct *n;
-@@ -8059,6 +8072,9 @@ static int dev_cpu_callback(struct notifier_block *nfb,
+@@ -8060,6 +8073,9 @@ static int dev_cpu_callback(struct notifier_block *nfb,
netif_rx_ni(skb);
input_queue_head_incr(oldsd);
}
@@ -150,7 +150,7 @@ index 885db5d6613c..f39b2a53b716 100644
return NOTIFY_OK;
}
-@@ -8363,8 +8379,9 @@ static int __init net_dev_init(void)
+@@ -8364,8 +8380,9 @@ static int __init net_dev_init(void)
INIT_WORK(flush, flush_backlog);
@@ -162,3 +162,6 @@ index 885db5d6613c..f39b2a53b716 100644
INIT_LIST_HEAD(&sd->poll_list);
sd->output_queue_tailp = &sd->output_queue;
#ifdef CONFIG_RPS
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0239-net-core-cpuhotplug-Drain-input_pkt_queue-lockless.patch b/debian/patches/features/all/rt/0239-net-core-cpuhotplug-Drain-input_pkt_queue-lockless.patch
index 829077f..aac63e4 100644
--- a/debian/patches/features/all/rt/0239-net-core-cpuhotplug-Drain-input_pkt_queue-lockless.patch
+++ b/debian/patches/features/all/rt/0239-net-core-cpuhotplug-Drain-input_pkt_queue-lockless.patch
@@ -1,7 +1,7 @@
From: Grygorii Strashko <grygorii.strashko at ti.com>
Date: Fri, 9 Oct 2015 09:25:49 -0500
Subject: [PATCH 239/351] net/core/cpuhotplug: Drain input_pkt_queue lockless
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2324fe928ce5f25976add3a4498fdfea01ef2288
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fdae29d570c9095ea729054c587bf42084e3883e
I can constantly see below error report with 4.1 RT-kernel on TI ARM dra7-evm
if I'm trying to unplug cpu1:
@@ -35,10 +35,10 @@ Cc: stable-rt at vger.kernel.org
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/core/dev.c b/net/core/dev.c
-index f39b2a53b716..1460f176cea7 100644
+index 9ff83f117a6b..cdabeb2a2024 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
-@@ -8068,7 +8068,7 @@ static int dev_cpu_callback(struct notifier_block *nfb,
+@@ -8069,7 +8069,7 @@ static int dev_cpu_callback(struct notifier_block *nfb,
netif_rx_ni(skb);
input_queue_head_incr(oldsd);
}
@@ -47,3 +47,6 @@ index f39b2a53b716..1460f176cea7 100644
netif_rx_ni(skb);
input_queue_head_incr(oldsd);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0240-net-move-xmit_recursion-to-per-task-variable-on-RT.patch b/debian/patches/features/all/rt/0240-net-move-xmit_recursion-to-per-task-variable-on-RT.patch
index 39fbf52..46b7d54 100644
--- a/debian/patches/features/all/rt/0240-net-move-xmit_recursion-to-per-task-variable-on-RT.patch
+++ b/debian/patches/features/all/rt/0240-net-move-xmit_recursion-to-per-task-variable-on-RT.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 13 Jan 2016 15:55:02 +0100
Subject: [PATCH 240/351] net: move xmit_recursion to per-task variable on -RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e41836398451629b5f23a1d29f9d963ef312bd94
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=90aaaffd3a478e67386aa23013c9416e40912822
A softirq on -RT can be preempted. That means one task is in
__dev_queue_xmit(), gets preempted and another task may enter
@@ -96,10 +96,10 @@ index a1331f77fad3..bdf040606769 100644
int pagefault_disabled;
#ifdef CONFIG_MMU
diff --git a/net/core/dev.c b/net/core/dev.c
-index 1460f176cea7..77fea52924b3 100644
+index cdabeb2a2024..2617fcce0555 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
-@@ -3176,8 +3176,10 @@ static void skb_update_prio(struct sk_buff *skb)
+@@ -3177,8 +3177,10 @@ static void skb_update_prio(struct sk_buff *skb)
#define skb_update_prio(skb)
#endif
@@ -110,7 +110,7 @@ index 1460f176cea7..77fea52924b3 100644
/**
* dev_loopback_xmit - loop back @skb
-@@ -3411,8 +3413,7 @@ static int __dev_queue_xmit(struct sk_buff *skb, void *accel_priv)
+@@ -3412,8 +3414,7 @@ static int __dev_queue_xmit(struct sk_buff *skb, void *accel_priv)
int cpu = smp_processor_id(); /* ok because BHs are off */
if (txq->xmit_lock_owner != cpu) {
@@ -120,7 +120,7 @@ index 1460f176cea7..77fea52924b3 100644
goto recursion_alert;
skb = validate_xmit_skb(skb, dev);
-@@ -3422,9 +3423,9 @@ static int __dev_queue_xmit(struct sk_buff *skb, void *accel_priv)
+@@ -3423,9 +3424,9 @@ static int __dev_queue_xmit(struct sk_buff *skb, void *accel_priv)
HARD_TX_LOCK(dev, txq, cpu);
if (!netif_xmit_stopped(txq)) {
@@ -157,3 +157,6 @@ index 4eb4ce0aeef4..4f09d6a57217 100644
return ret;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0241-net-provide-a-way-to-delegate-processing-a-softirq-t.patch b/debian/patches/features/all/rt/0241-net-provide-a-way-to-delegate-processing-a-softirq-t.patch
index 45633fb..5dde612 100644
--- a/debian/patches/features/all/rt/0241-net-provide-a-way-to-delegate-processing-a-softirq-t.patch
+++ b/debian/patches/features/all/rt/0241-net-provide-a-way-to-delegate-processing-a-softirq-t.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 20 Jan 2016 15:39:05 +0100
Subject: [PATCH 241/351] net: provide a way to delegate processing a softirq
to ksoftirqd
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=be9a38cda60166b27964a0eae3d3eb5a679d7020
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f50f6ba7d8126faea4c7a5369ef8adc9d3e9611c
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
@@ -71,10 +71,10 @@ index af2fd81cb9a5..819bd7cf5ad0 100644
* This function must run with irqs disabled!
*/
diff --git a/net/core/dev.c b/net/core/dev.c
-index 77fea52924b3..729daa8052fd 100644
+index 2617fcce0555..476381189495 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
-@@ -5300,7 +5300,7 @@ static __latent_entropy void net_rx_action(struct softirq_action *h)
+@@ -5301,7 +5301,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))
@@ -83,3 +83,6 @@ index 77fea52924b3..729daa8052fd 100644
net_rps_action_and_irq_enable(sd);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0242-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch b/debian/patches/features/all/rt/0242-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch
index 262ac4d..f3dcea5 100644
--- a/debian/patches/features/all/rt/0242-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch
+++ b/debian/patches/features/all/rt/0242-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 30 Mar 2016 13:36:29 +0200
Subject: [PATCH 242/351] net: dev: always take qdisc's busylock in
__dev_xmit_skb()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3ca58f3ce24a831ef2c413ea14b9a79e8f7bafee
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1b0074b088c08c29594c87ab2d72fc1897cc0bf7
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
@@ -21,10 +21,10 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 4 insertions(+)
diff --git a/net/core/dev.c b/net/core/dev.c
-index 729daa8052fd..e88c621a7c39 100644
+index 476381189495..ef55906b0263 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
-@@ -3113,7 +3113,11 @@ static inline int __dev_xmit_skb(struct sk_buff *skb, struct Qdisc *q,
+@@ -3114,7 +3114,11 @@ static inline int __dev_xmit_skb(struct sk_buff *skb, struct Qdisc *q,
* This permits qdisc->running owner to get the lock more
* often and dequeue packets faster.
*/
@@ -36,3 +36,6 @@ index 729daa8052fd..e88c621a7c39 100644
if (unlikely(contended))
spin_lock(&q->busylock);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0243-net-Qdisc-use-a-seqlock-instead-seqcount.patch b/debian/patches/features/all/rt/0243-net-Qdisc-use-a-seqlock-instead-seqcount.patch
index 4486423..66efa85 100644
--- a/debian/patches/features/all/rt/0243-net-Qdisc-use-a-seqlock-instead-seqcount.patch
+++ b/debian/patches/features/all/rt/0243-net-Qdisc-use-a-seqlock-instead-seqcount.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 14 Sep 2016 17:36:35 +0200
Subject: [PATCH 243/351] net/Qdisc: use a seqlock instead seqcount
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d110ec6f66b72a0b9668b48374e568dbc68a5b0e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=69bdde639951e9b2a69a2abdb9b7245cada0160f
The seqcount disables preemption on -RT while it is held which can't
remove. Also we don't want the reader to spin for ages if the writer is
@@ -289,3 +289,6 @@ index 3a5fe6255c10..d925f0e63679 100644
sch->ops = ops;
sch->enqueue = ops->enqueue;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0244-net-add-back-the-missing-serialization-in-ip_send_un.patch b/debian/patches/features/all/rt/0244-net-add-back-the-missing-serialization-in-ip_send_un.patch
index 7f78976..fa6a4e8 100644
--- a/debian/patches/features/all/rt/0244-net-add-back-the-missing-serialization-in-ip_send_un.patch
+++ b/debian/patches/features/all/rt/0244-net-add-back-the-missing-serialization-in-ip_send_un.patch
@@ -5,7 +5,7 @@ Subject: [PATCH 244/351] net: add back the missing serialization in
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=82f113114bc888f6a3d64377540a09cf06fe4a01
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=dc5ca2f1ec3d25c9c5be0f59e32ef6bf30a0132a
Some time ago Sami Pietikäinen reported a crash on -RT in
ip_send_unicast_reply() which was later fixed by Nicholas Mc Guire
@@ -42,7 +42,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 7 insertions(+)
diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
-index d577ec07a0d8..3336e1534bc5 100644
+index b3960738464e..67ca3fe56ac1 100644
--- a/net/ipv4/tcp_ipv4.c
+++ b/net/ipv4/tcp_ipv4.c
@@ -62,6 +62,7 @@
@@ -94,3 +94,6 @@ index d577ec07a0d8..3336e1534bc5 100644
}
static void tcp_v4_timewait_ack(struct sock *sk, struct sk_buff *skb)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0245-net-add-a-lock-around-icmp_sk.patch b/debian/patches/features/all/rt/0245-net-add-a-lock-around-icmp_sk.patch
index de35c11..d4b77ea 100644
--- a/debian/patches/features/all/rt/0245-net-add-a-lock-around-icmp_sk.patch
+++ b/debian/patches/features/all/rt/0245-net-add-a-lock-around-icmp_sk.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 31 Aug 2016 17:54:09 +0200
Subject: [PATCH 245/351] net: add a lock around icmp_sk()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a30d01fec27b3bc07052666aa0fdf998844ef4d2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e11ab45470488d56062cdc1a850d4e7aeeb2c0c0
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
@@ -14,7 +14,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 8 insertions(+)
diff --git a/net/ipv4/icmp.c b/net/ipv4/icmp.c
-index 48734ee6293f..dc915cc96981 100644
+index 31f17f0bbd1c..31ddd8067d4a 100644
--- a/net/ipv4/icmp.c
+++ b/net/ipv4/icmp.c
@@ -77,6 +77,7 @@
@@ -73,3 +73,6 @@ index 48734ee6293f..dc915cc96981 100644
}
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0246-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch b/debian/patches/features/all/rt/0246-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch
index e754a93..2de2a4a 100644
--- a/debian/patches/features/all/rt/0246-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch
+++ b/debian/patches/features/all/rt/0246-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch
@@ -2,7 +2,7 @@ From: Steven Rostedt <rostedt at goodmis.org>
Date: Tue, 6 Dec 2016 17:50:30 -0500
Subject: [PATCH 246/351] net: Have __napi_schedule_irqoff() disable interrupts
on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=952f3cf307422176232f461a4132ff57474b30aa
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8adebf29a8b9a62aceebf306460f36f0289e008b
A customer hit a crash where the napi sd->poll_list became corrupted.
The customer had the bnx2x driver, which does a
@@ -52,10 +52,10 @@ index dcad41b4e3b3..85fc72b8a92b 100644
static inline bool napi_disable_pending(struct napi_struct *n)
{
diff --git a/net/core/dev.c b/net/core/dev.c
-index e88c621a7c39..d9e0da1032fd 100644
+index ef55906b0263..661ec4bccdb9 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
-@@ -4959,6 +4959,7 @@ void __napi_schedule(struct napi_struct *n)
+@@ -4960,6 +4960,7 @@ void __napi_schedule(struct napi_struct *n)
}
EXPORT_SYMBOL(__napi_schedule);
@@ -63,7 +63,7 @@ index e88c621a7c39..d9e0da1032fd 100644
/**
* __napi_schedule_irqoff - schedule for receive
* @n: entry to schedule
-@@ -4970,6 +4971,7 @@ void __napi_schedule_irqoff(struct napi_struct *n)
+@@ -4971,6 +4972,7 @@ void __napi_schedule_irqoff(struct napi_struct *n)
____napi_schedule(this_cpu_ptr(&softnet_data), n);
}
EXPORT_SYMBOL(__napi_schedule_irqoff);
@@ -71,3 +71,6 @@ index e88c621a7c39..d9e0da1032fd 100644
void __napi_complete(struct napi_struct *n)
{
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0247-net-sysrq-via-icmp.patch b/debian/patches/features/all/rt/0247-net-sysrq-via-icmp.patch
index adf629b..c567b3b 100644
--- a/debian/patches/features/all/rt/0247-net-sysrq-via-icmp.patch
+++ b/debian/patches/features/all/rt/0247-net-sysrq-via-icmp.patch
@@ -1,7 +1,7 @@
From: Carsten Emde <C.Emde at osadl.org>
Date: Tue, 19 Jul 2011 13:51:17 +0100
Subject: [PATCH 247/351] net: sysrq via icmp
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2cdf564a4b3d6d45d0d4c0310fbbc127163c6aea
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d7f4add00463b584964717ef390bc5183ea9b1a6
There are (probably rare) situations when a system crashed and the system
console becomes unresponsive but the network icmp layer still is alive.
@@ -55,7 +55,7 @@ index 7adf4386ac8f..d3fd5c357268 100644
int sysctl_icmp_ratelimit;
int sysctl_icmp_ratemask;
diff --git a/net/ipv4/icmp.c b/net/ipv4/icmp.c
-index dc915cc96981..e6864ff11352 100644
+index 31ddd8067d4a..9a5f3fef53bb 100644
--- a/net/ipv4/icmp.c
+++ b/net/ipv4/icmp.c
@@ -69,6 +69,7 @@
@@ -66,7 +66,7 @@ index dc915cc96981..e6864ff11352 100644
#include <linux/socket.h>
#include <linux/in.h>
#include <linux/inet.h>
-@@ -898,6 +899,30 @@ static bool icmp_redirect(struct sk_buff *skb)
+@@ -907,6 +908,30 @@ static bool icmp_redirect(struct sk_buff *skb)
return true;
}
@@ -97,7 +97,7 @@ index dc915cc96981..e6864ff11352 100644
/*
* Handle ICMP_ECHO ("ping") requests.
*
-@@ -925,6 +950,11 @@ static bool icmp_echo(struct sk_buff *skb)
+@@ -934,6 +959,11 @@ static bool icmp_echo(struct sk_buff *skb)
icmp_param.data_len = skb->len;
icmp_param.head_len = sizeof(struct icmphdr);
icmp_reply(&icmp_param, skb);
@@ -127,3 +127,6 @@ index 566cfc50f7cf..4b8551d78a3b 100644
{
.procname = "icmp_ignore_bogus_error_responses",
.data = &init_net.ipv4.sysctl_icmp_ignore_bogus_error_responses,
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0248-irqwork-push-most-work-into-softirq-context.patch b/debian/patches/features/all/rt/0248-irqwork-push-most-work-into-softirq-context.patch
index caf5bdc..387e912 100644
--- a/debian/patches/features/all/rt/0248-irqwork-push-most-work-into-softirq-context.patch
+++ b/debian/patches/features/all/rt/0248-irqwork-push-most-work-into-softirq-context.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Tue, 23 Jun 2015 15:32:51 +0200
-Subject: [PATCH 248/337] irqwork: push most work into softirq context
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=89020e73eaac64e9b206c0183d5077a51927be7c
+Subject: [PATCH 248/351] irqwork: push most work into softirq context
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9efd8f0964c1f409fc3b896bf8b8d5af088e4281
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.
@@ -22,7 +22,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
---
include/linux/irq_work.h | 1 +
kernel/irq_work.c | 47 ++++++++++++++++++++++++++++++++++-------------
- kernel/sched/rt.c | 1 +
+ kernel/sched/core.c | 1 +
kernel/time/tick-sched.c | 1 +
kernel/time/timer.c | 6 +++++-
5 files changed, 42 insertions(+), 14 deletions(-)
@@ -146,20 +146,20 @@ index bcf107ce0854..0ddaf1e66d8c 100644
}
EXPORT_SYMBOL_GPL(irq_work_run);
-diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
-index f5a1132f9014..b0691f4e7d49 100644
---- a/kernel/sched/rt.c
-+++ b/kernel/sched/rt.c
-@@ -102,6 +102,7 @@ void init_rt_rq(struct rt_rq *rt_rq)
- rt_rq->rt_nr_migratory = 0;
- rt_rq->overloaded = 0;
- plist_head_init(&rt_rq->pushable_tasks);
-+ rt_rq->push_work.flags |= IRQ_WORK_HARD_IRQ;
- #endif /* CONFIG_SMP */
- /* We start is dequeued state, because no RT tasks are queued */
- rt_rq->rt_queued = 0;
+diff --git a/kernel/sched/core.c b/kernel/sched/core.c
+index 63f536082449..ca7927521f2f 100644
+--- a/kernel/sched/core.c
++++ b/kernel/sched/core.c
+@@ -6030,6 +6030,7 @@ static int init_rootdomain(struct root_domain *rd)
+ rd->rto_cpu = -1;
+ raw_spin_lock_init(&rd->rto_lock);
+ init_irq_work(&rd->rto_push_work, rto_push_irq_work_func);
++ rd->rto_push_work.flags |= IRQ_WORK_HARD_IRQ;
+ #endif
+
+ init_dl_bw(&rd->dl_bw);
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
-index 4367249e0dde..66d85482a96e 100644
+index 4c185caffcce..c573b1a848b6 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -220,6 +220,7 @@ static void nohz_full_kick_func(struct irq_work *work)
@@ -171,10 +171,10 @@ index 4367249e0dde..66d85482a96e 100644
/*
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
-index d8e1c2c5397c..fad6d60bf4e0 100644
+index cdb291bf5ec1..4cdec3d24423 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
-@@ -1663,7 +1663,7 @@ void update_process_times(int user_tick)
+@@ -1661,7 +1661,7 @@ void update_process_times(int user_tick)
scheduler_tick();
run_local_timers();
rcu_check_callbacks(user_tick);
@@ -183,7 +183,7 @@ index d8e1c2c5397c..fad6d60bf4e0 100644
if (in_irq())
irq_work_tick();
#endif
-@@ -1716,6 +1716,10 @@ static __latent_entropy void run_timer_softirq(struct softirq_action *h)
+@@ -1714,6 +1714,10 @@ static __latent_entropy void run_timer_softirq(struct softirq_action *h)
*/
base->must_forward_clk = false;
@@ -194,3 +194,6 @@ index d8e1c2c5397c..fad6d60bf4e0 100644
__run_timers(base);
if (IS_ENABLED(CONFIG_NO_HZ_COMMON))
__run_timers(this_cpu_ptr(&timer_bases[BASE_DEF]));
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0249-irqwork-Move-irq-safe-work-to-irq-context.patch b/debian/patches/features/all/rt/0249-irqwork-Move-irq-safe-work-to-irq-context.patch
index f85d53d..e24bb2a 100644
--- a/debian/patches/features/all/rt/0249-irqwork-Move-irq-safe-work-to-irq-context.patch
+++ b/debian/patches/features/all/rt/0249-irqwork-Move-irq-safe-work-to-irq-context.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 15 Nov 2015 18:40:17 +0100
Subject: [PATCH 249/351] irqwork: Move irq safe work to irq context
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=54d53ca594ebe06ea7e2ef5f7d109a1c2da7339e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=847d68e970fc0fe74c45965780912ef6eb7d11a5
On architectures where arch_irq_work_has_interrupt() returns false, we
end up running the irq safe work from the softirq context. That
@@ -59,10 +59,10 @@ index 0ddaf1e66d8c..2899ba0d23d1 100644
/*
* Synchronize against the irq_work @entry, ensures the entry is not
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
-index fad6d60bf4e0..31703677505f 100644
+index 4cdec3d24423..8e75e7442aaa 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
-@@ -1663,7 +1663,7 @@ void update_process_times(int user_tick)
+@@ -1661,7 +1661,7 @@ void update_process_times(int user_tick)
scheduler_tick();
run_local_timers();
rcu_check_callbacks(user_tick);
@@ -71,7 +71,7 @@ index fad6d60bf4e0..31703677505f 100644
if (in_irq())
irq_work_tick();
#endif
-@@ -1716,9 +1716,7 @@ static __latent_entropy void run_timer_softirq(struct softirq_action *h)
+@@ -1714,9 +1714,7 @@ static __latent_entropy void run_timer_softirq(struct softirq_action *h)
*/
base->must_forward_clk = false;
@@ -82,3 +82,6 @@ index fad6d60bf4e0..31703677505f 100644
__run_timers(base);
if (IS_ENABLED(CONFIG_NO_HZ_COMMON))
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0250-snd-pcm-fix-snd_pcm_stream_lock-irqs_disabled-splats.patch b/debian/patches/features/all/rt/0250-snd-pcm-fix-snd_pcm_stream_lock-irqs_disabled-splats.patch
index 37ce1a5..d096ea0 100644
--- a/debian/patches/features/all/rt/0250-snd-pcm-fix-snd_pcm_stream_lock-irqs_disabled-splats.patch
+++ b/debian/patches/features/all/rt/0250-snd-pcm-fix-snd_pcm_stream_lock-irqs_disabled-splats.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Wed, 18 Feb 2015 15:09:23 +0100
Subject: [PATCH 250/351] snd/pcm: fix snd_pcm_stream_lock*() irqs_disabled()
splats
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d7460301bdeb52befcfe28cd99be02d373fc90a8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=81bb79656476f068b7b24504b1355a99c3023a0b
Locking functions previously using read_lock_irq()/read_lock_irqsave() were
changed to local_irq_disable/save(), leading to gripes. Use nort variants.
@@ -71,3 +71,6 @@ index 9d33c1e85c79..3d307bda86f9 100644
}
EXPORT_SYMBOL_GPL(snd_pcm_stream_unlock_irqrestore);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0251-printk-Make-rt-aware.patch b/debian/patches/features/all/rt/0251-printk-Make-rt-aware.patch
index 44f0b89..b5448ba 100644
--- a/debian/patches/features/all/rt/0251-printk-Make-rt-aware.patch
+++ b/debian/patches/features/all/rt/0251-printk-Make-rt-aware.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 19 Sep 2012 14:50:37 +0200
Subject: [PATCH 251/351] printk: Make rt aware
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ceb5c20d0c1c56beff1ea388e15b12406ef2f9d6
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5b229fecc157b0b16348edeae05400295b9d5914
Drop the lock before calling the console driver and do not disable
interrupts while printing to a serial console.
@@ -73,7 +73,7 @@ index 35fb8be3e811..b0fd37e9ebac 100644
return;
out:
raw_spin_unlock_irqrestore(&logbuf_lock, flags);
-@@ -2477,13 +2494,17 @@ void console_unlock(void)
+@@ -2477,13 +2494,17 @@ skip:
console_idx = log_next(console_idx);
console_seq++;
console_prev = msg->flags;
@@ -92,3 +92,6 @@ index 35fb8be3e811..b0fd37e9ebac 100644
if (do_cond_resched)
cond_resched();
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0252-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch b/debian/patches/features/all/rt/0252-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch
index 18c2a6d..f09598a 100644
--- a/debian/patches/features/all/rt/0252-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch
+++ b/debian/patches/features/all/rt/0252-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 19 May 2016 17:45:27 +0200
Subject: [PATCH 252/351] kernel/printk: Don't try to print from IRQ/NMI region
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0d852df32bf5b05afa405fc67b60f937df52ab32
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b4618dd0e7d119f4f2f8386e57799b2b87678a62
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
@@ -42,3 +42,6 @@ index b0fd37e9ebac..a5d6b6cd9ac0 100644
/*
* console_unblank can no longer be called in interrupt context unless
* oops_in_progress is set to 1..
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0253-printk-Drop-the-logbuf_lock-more-often.patch b/debian/patches/features/all/rt/0253-printk-Drop-the-logbuf_lock-more-often.patch
index c967ff1..afadde5 100644
--- a/debian/patches/features/all/rt/0253-printk-Drop-the-logbuf_lock-more-often.patch
+++ b/debian/patches/features/all/rt/0253-printk-Drop-the-logbuf_lock-more-often.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 21 Mar 2013 19:01:05 +0100
Subject: [PATCH 253/351] printk: Drop the logbuf_lock more often
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=cf809c12378d4a22a1a6be07ae050e7b63674017
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c41409443a01bf519dfcf63ec48144b34ec3d528
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.
@@ -76,3 +76,6 @@ index a5d6b6cd9ac0..cf15bdb6855b 100644
raw_spin_unlock_irq(&logbuf_lock);
kfree(text);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0254-powerpc-Use-generic-rwsem-on-RT.patch b/debian/patches/features/all/rt/0254-powerpc-Use-generic-rwsem-on-RT.patch
index a568374..bbff5ae 100644
--- a/debian/patches/features/all/rt/0254-powerpc-Use-generic-rwsem-on-RT.patch
+++ b/debian/patches/features/all/rt/0254-powerpc-Use-generic-rwsem-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 14 Jul 2015 14:26:34 +0200
Subject: [PATCH 254/351] powerpc: Use generic rwsem on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b9f478e50eda0b85cd4fed3524d1d228c4ecc0d2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a834c8abbf0a57437119250c86411b23f8ca0317
Use generic code which uses rtmutex
@@ -27,3 +27,6 @@ index 6eda5abbd719..1aca48ecabe5 100644
config GENERIC_LOCKBREAK
bool
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0255-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch b/debian/patches/features/all/rt/0255-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch
index 3ef7934..8ac9451 100644
--- a/debian/patches/features/all/rt/0255-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch
+++ b/debian/patches/features/all/rt/0255-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch
@@ -2,7 +2,7 @@ From: Bogdan Purcareata <bogdan.purcareata at freescale.com>
Date: Fri, 24 Apr 2015 15:53:13 +0000
Subject: [PATCH 255/351] powerpc/kvm: Disable in-kernel MPIC emulation for
PREEMPT_RT_FULL
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0c07b0aafb1e0d1a0756adb0d4f7d8b1732c4781
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2a4a2a342fdfe4efc71f651948d8324b8b9378a1
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
@@ -39,3 +39,6 @@ index 029be26b5a17..9528089ea142 100644
select HAVE_KVM_IRQCHIP
select HAVE_KVM_IRQFD
select HAVE_KVM_IRQ_ROUTING
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0256-powerpc-ps3-device-init.c-adapt-to-completions-using.patch b/debian/patches/features/all/rt/0256-powerpc-ps3-device-init.c-adapt-to-completions-using.patch
index 8cd4088..0cf4997 100644
--- a/debian/patches/features/all/rt/0256-powerpc-ps3-device-init.c-adapt-to-completions-using.patch
+++ b/debian/patches/features/all/rt/0256-powerpc-ps3-device-init.c-adapt-to-completions-using.patch
@@ -2,7 +2,7 @@ From: Paul Gortmaker <paul.gortmaker at windriver.com>
Date: Sun, 31 May 2015 14:44:42 -0400
Subject: [PATCH 256/351] powerpc: ps3/device-init.c - adapt to completions
using swait vs wait
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=95acfb07ed845bb2bd07740b68327becf3483d78
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=54f66f9cae7ea33a1f1e2cd0e2bb9fbe6ea86e98
To fix:
@@ -33,3 +33,6 @@ index e48462447ff0..2670cee66064 100644
dev->done.done || kthread_should_stop());
if (kthread_should_stop())
res = -EINTR;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0257-ARM-at91-tclib-Default-to-tclib-timer-for-RT.patch b/debian/patches/features/all/rt/0257-ARM-at91-tclib-Default-to-tclib-timer-for-RT.patch
index f14324e..7dcdb06 100644
--- a/debian/patches/features/all/rt/0257-ARM-at91-tclib-Default-to-tclib-timer-for-RT.patch
+++ b/debian/patches/features/all/rt/0257-ARM-at91-tclib-Default-to-tclib-timer-for-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 1 May 2010 18:29:35 +0200
Subject: [PATCH 257/351] ARM: at91: tclib: Default to tclib timer for RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6f77315a976ca1687bf08dc39c99a62f8ed1e1a4
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8011c7e279ad9fbe4ef37f0928a34effbb94bfdf
RT is not too happy about the shared timer interrupt in AT91
devices. Default to tclib timer for RT.
@@ -32,3 +32,6 @@ index 9a6d60d57ec5..215e91e36198 100644
help
Select this to use 32 KiHz base clock rate as TC block clock
source for clock events.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0258-arm-unwind-use-a-raw_spin_lock.patch b/debian/patches/features/all/rt/0258-arm-unwind-use-a-raw_spin_lock.patch
index 499a1d7..c24a753 100644
--- a/debian/patches/features/all/rt/0258-arm-unwind-use-a-raw_spin_lock.patch
+++ b/debian/patches/features/all/rt/0258-arm-unwind-use-a-raw_spin_lock.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 20 Sep 2013 14:31:54 +0200
Subject: [PATCH 258/351] arm/unwind: use a raw_spin_lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a00e398eec5e2c3af7bc4cb3270220082d7e8dc1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0d5be589db87d90c4c11818da731971d7a527fe2
Mostly unwind is done with irqs enabled however SLUB may call it with
irqs disabled while creating a new SLUB cache.
@@ -84,3 +84,6 @@ index 0bee233fef9a..314cfb232a63 100644
kfree(tab);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0259-ARM-enable-irq-in-translation-section-permission-fau.patch b/debian/patches/features/all/rt/0259-ARM-enable-irq-in-translation-section-permission-fau.patch
index 74f168e..277a37d 100644
--- a/debian/patches/features/all/rt/0259-ARM-enable-irq-in-translation-section-permission-fau.patch
+++ b/debian/patches/features/all/rt/0259-ARM-enable-irq-in-translation-section-permission-fau.patch
@@ -5,7 +5,7 @@ Subject: [PATCH 259/351] ARM: enable irq in translation/section permission
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5a686eecd3f7db127e1a7a2f3aeedcb5542873e5
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=785fbb8d805c0d1f57abd5b2726221ea83b2faec
Probably happens on all ARM, with
CONFIG_PREEMPT_RT_FULL
@@ -90,3 +90,6 @@ index f7861dc83182..ce47dfe25fb0 100644
do_bad_area(addr, fsr, regs);
return 0;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0260-genirq-update-irq_set_irqchip_state-documentation.patch b/debian/patches/features/all/rt/0260-genirq-update-irq_set_irqchip_state-documentation.patch
index 62ba03b..6e81ae5 100644
--- a/debian/patches/features/all/rt/0260-genirq-update-irq_set_irqchip_state-documentation.patch
+++ b/debian/patches/features/all/rt/0260-genirq-update-irq_set_irqchip_state-documentation.patch
@@ -1,7 +1,7 @@
From: Josh Cartwright <joshc at ni.com>
Date: Thu, 11 Feb 2016 11:54:00 -0600
Subject: [PATCH 260/351] genirq: update irq_set_irqchip_state documentation
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3a39034661e1222aee4e9fdfc36aec315b4f7eab
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e89345e53e4b0c1e1820239a8fa856d9c60a3789
On -rt kernels, the use of migrate_disable()/migrate_enable() is
sufficient to guarantee a task isn't moved to another CPU. Update the
@@ -26,3 +26,6 @@ index 5f14e0d7c0c7..6b075cc0603a 100644
* interrupt controller has per-cpu registers.
*/
int irq_set_irqchip_state(unsigned int irq, enum irqchip_irq_state which,
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0261-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch b/debian/patches/features/all/rt/0261-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch
index 7c96dfb..99ee2c5 100644
--- a/debian/patches/features/all/rt/0261-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch
+++ b/debian/patches/features/all/rt/0261-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch
@@ -2,7 +2,7 @@ From: Josh Cartwright <joshc at ni.com>
Date: Thu, 11 Feb 2016 11:54:01 -0600
Subject: [PATCH 261/351] KVM: arm/arm64: downgrade preempt_disable()d region
to migrate_disable()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=838ee9c1a410b7649938d7c003765b44a91f1bd1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7dea203e3b11d3c86359e2670e34a80965db5ec6
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
@@ -53,3 +53,6 @@ index 19b5f5c1c0ff..82aa639e6737 100644
ret = handle_exit(vcpu, run, ret);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0262-arm64-xen-Make-XEN-depend-on-RT.patch b/debian/patches/features/all/rt/0262-arm64-xen-Make-XEN-depend-on-RT.patch
index 3eb121e..256af6e 100644
--- a/debian/patches/features/all/rt/0262-arm64-xen-Make-XEN-depend-on-RT.patch
+++ b/debian/patches/features/all/rt/0262-arm64-xen-Make-XEN-depend-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 12 Oct 2015 11:18:40 +0200
Subject: [PATCH 262/351] arm64/xen: Make XEN depend on !RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f7c258226225fe38b5d57b815357eca34d00a5b0
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9ddb13530453433138b31b2b921f68ffbe8d8711
It's not ready and probably never will be, unless xen folks have a
look at it.
@@ -24,3 +24,6 @@ index cf57a7799a0f..9984f654c000 100644
select SWIOTLB_XEN
select PARAVIRT
help
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0263-kgdb-serial-Short-term-workaround.patch b/debian/patches/features/all/rt/0263-kgdb-serial-Short-term-workaround.patch
index a333921..a7fdd34 100644
--- a/debian/patches/features/all/rt/0263-kgdb-serial-Short-term-workaround.patch
+++ b/debian/patches/features/all/rt/0263-kgdb-serial-Short-term-workaround.patch
@@ -1,7 +1,7 @@
From: Jason Wessel <jason.wessel at windriver.com>
Date: Thu, 28 Jul 2011 12:42:23 -0500
Subject: [PATCH 263/351] kgdb/serial: Short term workaround
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=531001893ab2f04ff397be186712c9a67b019c73
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=af0e0ec9a6bf509c2aa25aed76780d2147301294
On 07/27/2011 04:37 PM, Thomas Gleixner wrote:
> - KGDB (not yet disabled) is reportedly unusable on -rt right now due
@@ -65,7 +65,7 @@ index 410decacff8f..0861bebfc188 100644
static inline int kdb_register(char *cmd, kdb_func_t func, char *usage,
char *help, short minlen) { return 0; }
diff --git a/kernel/debug/kdb/kdb_io.c b/kernel/debug/kdb/kdb_io.c
-index fc1ef736253c..83c666537a7a 100644
+index 77777d918676..3203e9dee9f8 100644
--- a/kernel/debug/kdb/kdb_io.c
+++ b/kernel/debug/kdb/kdb_io.c
@@ -554,7 +554,6 @@ int vkdb_printf(enum kdb_msgsrc src, const char *fmt, va_list ap)
@@ -85,7 +85,7 @@ index fc1ef736253c..83c666537a7a 100644
/* Serialize kdb_printf if multiple cpus try to write at once.
* But if any cpu goes recursive in kdb, just print the output,
-@@ -855,7 +852,6 @@ int vkdb_printf(enum kdb_msgsrc src, const char *fmt, va_list ap)
+@@ -855,7 +852,6 @@ kdb_print_out:
} else {
__release(kdb_printf_lock);
}
@@ -105,3 +105,6 @@ index fc1ef736253c..83c666537a7a 100644
return r;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0264-sysfs-Add-sys-kernel-realtime-entry.patch b/debian/patches/features/all/rt/0264-sysfs-Add-sys-kernel-realtime-entry.patch
index 1f288ea..1841e0b 100644
--- a/debian/patches/features/all/rt/0264-sysfs-Add-sys-kernel-realtime-entry.patch
+++ b/debian/patches/features/all/rt/0264-sysfs-Add-sys-kernel-realtime-entry.patch
@@ -1,7 +1,7 @@
From: Clark Williams <williams at redhat.com>
Date: Sat, 30 Jul 2011 21:55:53 -0500
Subject: [PATCH 264/351] sysfs: Add /sys/kernel/realtime entry
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ffc3696f920ba50fb6fa2f1760d65bb8a8aa8079
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d97f372eeba9076faa80412e5555f1d6dfe086a3
Add a /sys/kernel entry to indicate that the kernel is a
realtime kernel.
@@ -48,3 +48,6 @@ index ee1bc1bb8feb..ddef07958840 100644
#endif
NULL
};
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0265-powerpc-Disable-highmem-on-RT.patch b/debian/patches/features/all/rt/0265-powerpc-Disable-highmem-on-RT.patch
index 2689010..670983a 100644
--- a/debian/patches/features/all/rt/0265-powerpc-Disable-highmem-on-RT.patch
+++ b/debian/patches/features/all/rt/0265-powerpc-Disable-highmem-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 18 Jul 2011 17:08:34 +0200
Subject: [PATCH 265/351] powerpc: Disable highmem on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=13812c4fd8e40dc39a452662e504967c42fe6696
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=86d87c110aabd76b21ab538d944fec7bbf9841e8
The current highmem handling on -RT is not compatible and needs fixups.
@@ -23,3 +23,6 @@ index 1aca48ecabe5..cdf9c16c1284 100644
source kernel/Kconfig.hz
source kernel/Kconfig.preempt
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0266-mips-Disable-highmem-on-RT.patch b/debian/patches/features/all/rt/0266-mips-Disable-highmem-on-RT.patch
index 68eb432..a63546d 100644
--- a/debian/patches/features/all/rt/0266-mips-Disable-highmem-on-RT.patch
+++ b/debian/patches/features/all/rt/0266-mips-Disable-highmem-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 18 Jul 2011 17:10:12 +0200
Subject: [PATCH 266/351] mips: Disable highmem on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e017443689ed8a4edef900e5e894c21d24f0bd7c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e83a790b8fe82b8b56fc9445836fd00e0460a410
The current highmem handling on -RT is not compatible and needs fixups.
@@ -23,3 +23,6 @@ index 5e844f68e847..dc613cc10f54 100644
config CPU_SUPPORTS_HIGHMEM
bool
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0267-mm-rt-kmap_atomic-scheduling.patch b/debian/patches/features/all/rt/0267-mm-rt-kmap_atomic-scheduling.patch
index 34a515f..832367c 100644
--- a/debian/patches/features/all/rt/0267-mm-rt-kmap_atomic-scheduling.patch
+++ b/debian/patches/features/all/rt/0267-mm-rt-kmap_atomic-scheduling.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Thu, 28 Jul 2011 10:43:51 +0200
Subject: [PATCH 267/351] mm, rt: kmap_atomic scheduling
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e1b604ac98e9b40d7d17c9464601943e88f91899
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=44b5393e6cad3cade1fdeb94491a9fbf4c91ec58
In fact, with migrate_disable() existing one could play games with
kmap_atomic. You could save/restore the kmap_atomic slots on context
@@ -301,3 +301,6 @@ index 50b4ca6787f0..77518a3b35a1 100644
unsigned int nr_free_highpages (void)
{
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0268-mm-rt-Fix-generic-kmap_atomic-for-RT.patch b/debian/patches/features/all/rt/0268-mm-rt-Fix-generic-kmap_atomic-for-RT.patch
index d75881b..bc630cf 100644
--- a/debian/patches/features/all/rt/0268-mm-rt-Fix-generic-kmap_atomic-for-RT.patch
+++ b/debian/patches/features/all/rt/0268-mm-rt-Fix-generic-kmap_atomic-for-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 19 Sep 2015 10:15:00 +0200
Subject: [PATCH 268/351] mm: rt: Fix generic kmap_atomic for RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=30afbf6049972651a5edce171c8018f73c76a45b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=58ee9ebf3544905c9571a50f53ed6e63f7aa1203
The update to 4.1 brought in the mainline variant of the pagefault
disable distangling from preempt count. That introduced a
@@ -41,3 +41,6 @@ index 1a8a811ae882..04ec5c35c2d5 100644
}
#define kmap_atomic_pfn(pfn) kmap_atomic(pfn_to_page(pfn))
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0269-x86-highmem-Add-a-already-used-pte-check.patch b/debian/patches/features/all/rt/0269-x86-highmem-Add-a-already-used-pte-check.patch
index 7421b25..165454b 100644
--- a/debian/patches/features/all/rt/0269-x86-highmem-Add-a-already-used-pte-check.patch
+++ b/debian/patches/features/all/rt/0269-x86-highmem-Add-a-already-used-pte-check.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 11 Mar 2013 17:09:55 +0100
Subject: [PATCH 269/351] x86/highmem: Add a "already used pte" check
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=09e62707cdfd52eab3538466864a410d5bd9f599
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b6881a7f79f26361fe890529c57582135ea580ef
This is a copy from kmap_atomic_prot().
@@ -23,3 +23,6 @@ index 2620fb55ece1..585f6829653b 100644
#ifdef CONFIG_PREEMPT_RT_FULL
current->kmap_pte[type] = pte;
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0270-arm-highmem-Flush-tlb-on-unmap.patch b/debian/patches/features/all/rt/0270-arm-highmem-Flush-tlb-on-unmap.patch
index 3f3d9a6..d79d9d4 100644
--- a/debian/patches/features/all/rt/0270-arm-highmem-Flush-tlb-on-unmap.patch
+++ b/debian/patches/features/all/rt/0270-arm-highmem-Flush-tlb-on-unmap.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 11 Mar 2013 21:37:27 +0100
Subject: [PATCH 270/351] arm/highmem: Flush tlb on unmap
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f59a84bc219601047001a30f16c5667c8ef311a6
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=04d2391e17c0a179d10dc0d41778984dd226156d
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
@@ -28,3 +28,6 @@ index d02f8187b1cc..eb4b225d28c9 100644
kmap_atomic_idx_pop();
} else if (vaddr >= PKMAP_ADDR(0) && vaddr < PKMAP_ADDR(LAST_PKMAP)) {
/* this address was obtained through kmap_high_get() */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0271-arm-Enable-highmem-for-rt.patch b/debian/patches/features/all/rt/0271-arm-Enable-highmem-for-rt.patch
index 637684f..7f29a5a 100644
--- a/debian/patches/features/all/rt/0271-arm-Enable-highmem-for-rt.patch
+++ b/debian/patches/features/all/rt/0271-arm-Enable-highmem-for-rt.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 13 Feb 2013 11:03:11 +0100
Subject: [PATCH 271/351] arm: Enable highmem for rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=25f18f6a787e457f12f9ac48fbd26f6fa608ba35
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e3c90bfe193d23fbf05f6d2de413fd69cea19323
fixup highmem for ARM.
@@ -178,3 +178,6 @@ index 04ec5c35c2d5..a117a33ef72c 100644
#include <asm/cacheflush.h>
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0272-ipc-sem-Rework-semaphore-wakeups.patch b/debian/patches/features/all/rt/0272-ipc-sem-Rework-semaphore-wakeups.patch
index 1f24e61..b8a634d 100644
--- a/debian/patches/features/all/rt/0272-ipc-sem-Rework-semaphore-wakeups.patch
+++ b/debian/patches/features/all/rt/0272-ipc-sem-Rework-semaphore-wakeups.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Wed, 14 Sep 2011 11:57:04 +0200
Subject: [PATCH 272/351] ipc/sem: Rework semaphore wakeups
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=98e4276949bb2494165c839db10e5f2d1c49c385
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=16831aaa7c9e8c1f7945bb8db0560115e2e2408b
Current sysv sems have a weird ass wakeup scheme that involves keeping
preemption disabled over a potential O(n^2) loop and busy waiting on
@@ -32,7 +32,7 @@ diff --git a/ipc/sem.c b/ipc/sem.c
index 10b94bc59d4a..b8360eaacc7a 100644
--- a/ipc/sem.c
+++ b/ipc/sem.c
-@@ -712,6 +712,13 @@ static int perform_atomic_semop(struct sem_array *sma, struct sem_queue *q)
+@@ -712,6 +712,13 @@ undo:
static void wake_up_sem_queue_prepare(struct list_head *pt,
struct sem_queue *q, int error)
{
@@ -70,3 +70,6 @@ index 10b94bc59d4a..b8360eaacc7a 100644
}
static void unlink_queue(struct sem_array *sma, struct sem_queue *q)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0273-x86-kvm-Require-const-tsc-for-RT.patch b/debian/patches/features/all/rt/0273-x86-kvm-Require-const-tsc-for-RT.patch
index b0c813a..7159483 100644
--- a/debian/patches/features/all/rt/0273-x86-kvm-Require-const-tsc-for-RT.patch
+++ b/debian/patches/features/all/rt/0273-x86-kvm-Require-const-tsc-for-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 6 Nov 2011 12:26:18 +0100
Subject: [PATCH 273/351] x86: kvm Require const tsc for RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e7591296fdc69a7a673b9e8bb80a1a6f0e3a58c9
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c7632563606becc176d6b4b016bfb87888d1c9f5
Non constant TSC is a nightmare on bare metal already, but with
virtualization it becomes a complete disaster because the workarounds
@@ -14,10 +14,10 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 7 insertions(+)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
-index 02d45296a97c..4963bd51d20b 100644
+index 73304b1a03cc..2a0fae2ef089 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
-@@ -5966,6 +5966,13 @@ int kvm_arch_init(void *opaque)
+@@ -5967,6 +5967,13 @@ int kvm_arch_init(void *opaque)
goto out;
}
@@ -31,3 +31,6 @@ index 02d45296a97c..4963bd51d20b 100644
r = kvm_mmu_module_init();
if (r)
goto out_free_percpu;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0274-KVM-lapic-mark-LAPIC-timer-handler-as-irqsafe.patch b/debian/patches/features/all/rt/0274-KVM-lapic-mark-LAPIC-timer-handler-as-irqsafe.patch
index d8b8838..4cd663a 100644
--- a/debian/patches/features/all/rt/0274-KVM-lapic-mark-LAPIC-timer-handler-as-irqsafe.patch
+++ b/debian/patches/features/all/rt/0274-KVM-lapic-mark-LAPIC-timer-handler-as-irqsafe.patch
@@ -1,7 +1,7 @@
From: Marcelo Tosatti <mtosatti at redhat.com>
Date: Wed, 8 Apr 2015 20:33:25 -0300
Subject: [PATCH 274/351] KVM: lapic: mark LAPIC timer handler as irqsafe
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=cae1efe1d20f8dbcb21cfd8248d2c77b92a2c525
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=30c73399111caf3f35bcfce7301af46f8559feb0
Since lapic timer handler only wakes up a simple waitqueue,
it can be executed from hardirq context.
@@ -26,3 +26,6 @@ index b24b3c6d686e..02a062b0de5d 100644
/*
* APIC is created enabled. This will prevent kvm_lapic_set_base from
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0275-scsi-fcoe-Make-RT-aware.patch b/debian/patches/features/all/rt/0275-scsi-fcoe-Make-RT-aware.patch
index 76b12c0..ad23863 100644
--- a/debian/patches/features/all/rt/0275-scsi-fcoe-Make-RT-aware.patch
+++ b/debian/patches/features/all/rt/0275-scsi-fcoe-Make-RT-aware.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sat, 12 Nov 2011 14:00:48 +0100
Subject: [PATCH 275/351] scsi/fcoe: Make RT aware.
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f81588c6ec0d9371860da68432f15416a2b77e1a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bf4f2748cb7f77936ecfc2b232e464d96630989e
Do not disable preemption while taking sleeping locks. All user look safe
for migrate_diable() only.
@@ -17,7 +17,7 @@ diff --git a/drivers/scsi/fcoe/fcoe.c b/drivers/scsi/fcoe/fcoe.c
index 9bd41a35a78a..8e2d436c2e3f 100644
--- a/drivers/scsi/fcoe/fcoe.c
+++ b/drivers/scsi/fcoe/fcoe.c
-@@ -1455,11 +1455,11 @@ static int fcoe_rcv(struct sk_buff *skb, struct net_device *netdev,
+@@ -1455,11 +1455,11 @@ err2:
static int fcoe_alloc_paged_crc_eof(struct sk_buff *skb, int tlen)
{
struct fcoe_percpu_s *fps;
@@ -110,3 +110,6 @@ index 16ca31ad5ec0..c3987347e762 100644
/* peek cache of free slot */
if (pool->left != FC_XID_UNKNOWN) {
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0276-sas-ata-isci-dont-t-disable-interrupts-in-qc_issue-h.patch b/debian/patches/features/all/rt/0276-sas-ata-isci-dont-t-disable-interrupts-in-qc_issue-h.patch
index bc90d71..8591af7 100644
--- a/debian/patches/features/all/rt/0276-sas-ata-isci-dont-t-disable-interrupts-in-qc_issue-h.patch
+++ b/debian/patches/features/all/rt/0276-sas-ata-isci-dont-t-disable-interrupts-in-qc_issue-h.patch
@@ -2,7 +2,7 @@ From: Paul Gortmaker <paul.gortmaker at windriver.com>
Date: Sat, 14 Feb 2015 11:01:16 -0500
Subject: [PATCH 276/351] sas-ata/isci: dont't disable interrupts in qc_issue
handler
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=22fb44122d1e189d823f45a43dd1478b838dcc95
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=29e94019e176eb99819f9888065d3211751899d7
On 3.14-rt we see the following trace on Canoe Pass for
SCSI_ISCI "Intel(R) C600 Series Chipset SAS Controller"
@@ -80,3 +80,6 @@ index 87f5e694dbed..23c0a50fb6aa 100644
return ret;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0277-x86-crypto-Reduce-preempt-disabled-regions.patch b/debian/patches/features/all/rt/0277-x86-crypto-Reduce-preempt-disabled-regions.patch
index 761b40f..28c763e 100644
--- a/debian/patches/features/all/rt/0277-x86-crypto-Reduce-preempt-disabled-regions.patch
+++ b/debian/patches/features/all/rt/0277-x86-crypto-Reduce-preempt-disabled-regions.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Mon, 14 Nov 2011 18:19:27 +0100
Subject: [PATCH 277/351] x86: crypto: Reduce preempt disabled regions
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7777d7b57bd2079813b77e8fe8cb21bf94816b29
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f769c2a6b78c7762e889b490a8f6a78ecb528a25
Restrict the preempt disabled regions to the actual floating point
operations and enable preemption for the administrative actions.
@@ -113,3 +113,6 @@ index aa8b0672f87a..2429414bfc71 100644
return err;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0278-crypto-Reduce-preempt-disabled-regions-more-algos.patch b/debian/patches/features/all/rt/0278-crypto-Reduce-preempt-disabled-regions-more-algos.patch
index 1b054c7..da13e96 100644
--- a/debian/patches/features/all/rt/0278-crypto-Reduce-preempt-disabled-regions-more-algos.patch
+++ b/debian/patches/features/all/rt/0278-crypto-Reduce-preempt-disabled-regions-more-algos.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 21 Feb 2014 17:24:04 +0100
Subject: [PATCH 278/351] crypto: Reduce preempt disabled regions, more algos
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4b609ad53307543be5a0bdd2642bbcb221034cc2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=82dabbf203e4a2ae3b0de37d016e8a1cf32ca6a5
Don Estabrook reported
| kernel: WARNING: CPU: 2 PID: 858 at kernel/sched/core.c:2428 migrate_disable+0xed/0x100()
@@ -76,7 +76,7 @@ index 8648158f3916..d7699130ee36 100644
return err;
}
-@@ -227,7 +226,7 @@ static unsigned int __cbc_decrypt(struct blkcipher_desc *desc,
+@@ -227,7 +226,7 @@ done:
static int cbc_decrypt(struct blkcipher_desc *desc, struct scatterlist *dst,
struct scatterlist *src, unsigned int nbytes)
{
@@ -100,7 +100,7 @@ index 8648158f3916..d7699130ee36 100644
return err;
}
-@@ -311,7 +309,7 @@ static unsigned int __ctr_crypt(struct blkcipher_desc *desc,
+@@ -311,7 +309,7 @@ done:
static int ctr_crypt(struct blkcipher_desc *desc, struct scatterlist *dst,
struct scatterlist *src, unsigned int nbytes)
{
@@ -244,3 +244,6 @@ index 6a85598931b5..3a506ce7ed93 100644
return err;
}
EXPORT_SYMBOL_GPL(glue_xts_crypt_128bit);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0279-dm-Make-rt-aware.patch b/debian/patches/features/all/rt/0279-dm-Make-rt-aware.patch
index c609b12..058e0e1 100644
--- a/debian/patches/features/all/rt/0279-dm-Make-rt-aware.patch
+++ b/debian/patches/features/all/rt/0279-dm-Make-rt-aware.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 14 Nov 2011 23:06:09 +0100
Subject: [PATCH 279/351] dm: Make rt aware
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3df8ba175e799faf63caf668dfbde9c24c6ca594
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8787a298df0d3036cc7e75ba1be93e88ef0a1a2c
Use the BUG_ON_NORT variant for the irq_disabled() checks. RT has
interrupts legitimately enabled here as we cant deadlock against the
@@ -27,3 +27,6 @@ index ba7c4c685db3..834ec328f217 100644
}
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0280-acpi-rt-Convert-acpi_gbl_hardware-lock-back-to-a-raw.patch b/debian/patches/features/all/rt/0280-acpi-rt-Convert-acpi_gbl_hardware-lock-back-to-a-raw.patch
index e62a19c..6a8a604 100644
--- a/debian/patches/features/all/rt/0280-acpi-rt-Convert-acpi_gbl_hardware-lock-back-to-a-raw.patch
+++ b/debian/patches/features/all/rt/0280-acpi-rt-Convert-acpi_gbl_hardware-lock-back-to-a-raw.patch
@@ -2,7 +2,7 @@ From: Steven Rostedt <rostedt at goodmis.org>
Date: Wed, 13 Feb 2013 09:26:05 -0500
Subject: [PATCH 280/351] acpi/rt: Convert acpi_gbl_hardware lock back to a
raw_spinlock_t
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7ddd5fbf666830c1138c3ff6529a77711b51e513
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=cbb033da5c8716cf1f8e6d3d110330105de7762f
We hit the following bug with 3.6-rt:
@@ -183,3 +183,6 @@ index e861a24f06f2..b5c97d3059c7 100644
/*
* OSL interfaces used by debugger/disassembler
*/
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0281-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch b/debian/patches/features/all/rt/0281-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch
index c8b12d1..226d309 100644
--- a/debian/patches/features/all/rt/0281-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch
+++ b/debian/patches/features/all/rt/0281-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 14 Dec 2011 01:03:49 +0100
Subject: [PATCH 281/351] cpumask: Disable CONFIG_CPUMASK_OFFSTACK for RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4527e2562a35d86da4d2839fdb9e1b6c26549e13
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=683c6146696fe672f0ee01f28f8cfb61124b21ff
There are "valid" GFP_ATOMIC allocations such as
@@ -46,7 +46,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
-index 88c67b3a25a4..ab7c90867543 100644
+index b7a8745c8083..507bcea14207 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -900,7 +900,7 @@ config IOMMU_HELPER
@@ -70,3 +70,6 @@ index 260a80e313b9..b06becb3f477 100644
help
Use dynamic allocation for cpumask_var_t, instead of putting
them on the stack. This is a bit more expensive, but avoids
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0282-random-Make-it-work-on-rt.patch b/debian/patches/features/all/rt/0282-random-Make-it-work-on-rt.patch
index 7d6b15a..a811f86 100644
--- a/debian/patches/features/all/rt/0282-random-Make-it-work-on-rt.patch
+++ b/debian/patches/features/all/rt/0282-random-Make-it-work-on-rt.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Tue, 21 Aug 2012 20:38:50 +0200
Subject: [PATCH 282/351] random: Make it work on rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f44e63d2da7b2e20dcb55db02a2a4328f5f303dc
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e168364bb77edb889b39b3ee8a832e599c758507
Delegate the random insertion to the forced threaded interrupt
handler. Store the return IP of the hard interrupt handler in the irq
@@ -142,3 +142,6 @@ index 6b075cc0603a..5994867526f3 100644
wake_threads_waitq(desc);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0283-random-avoid-preempt_disable-ed-section.patch b/debian/patches/features/all/rt/0283-random-avoid-preempt_disable-ed-section.patch
index 4dc7b4f..73526e9 100644
--- a/debian/patches/features/all/rt/0283-random-avoid-preempt_disable-ed-section.patch
+++ b/debian/patches/features/all/rt/0283-random-avoid-preempt_disable-ed-section.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 12 May 2017 15:46:17 +0200
Subject: [PATCH 283/351] random: avoid preempt_disable()ed section
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fd62e45d7b2893263f27ca403644145260f66bd6
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d3343c0c5a67d8786cef21d841f0d48f8e8365c1
extract_crng() will use sleeping locks while in a preempt_disable()
section due to get_cpu_var().
@@ -74,3 +74,6 @@ index ec886dda1b21..25ee319dc8e3 100644
return ret;
}
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0284-cpu-Make-hotplug.lock-a-sleeping-spinlock-on-RT.patch b/debian/patches/features/all/rt/0284-cpu-Make-hotplug.lock-a-sleeping-spinlock-on-RT.patch
index 08b55d9..e792621 100644
--- a/debian/patches/features/all/rt/0284-cpu-Make-hotplug.lock-a-sleeping-spinlock-on-RT.patch
+++ b/debian/patches/features/all/rt/0284-cpu-Make-hotplug.lock-a-sleeping-spinlock-on-RT.patch
@@ -1,7 +1,7 @@
From: Steven Rostedt <rostedt at goodmis.org>
Date: Fri, 2 Mar 2012 10:36:57 -0500
Subject: [PATCH 284/351] cpu: Make hotplug.lock a "sleeping" spinlock on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8b76bdb82d3a63dad44933efa392550c31b16b59
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f48fa279d7ecb444429c7265e567a113f61b6ea7
Tasks can block on hotplug.lock in pin_current_cpu(), but their state
might be != RUNNING. So the mutex wakeup will set the state
@@ -24,7 +24,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 25 insertions(+), 7 deletions(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index 4b8f59bee8d9..9bb0d333bfc7 100644
+index 7c28baf1a9d6..238f11eb99ae 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -210,10 +210,16 @@ static int cpu_hotplug_disabled;
@@ -69,7 +69,7 @@ index 4b8f59bee8d9..9bb0d333bfc7 100644
/* Lockdep annotations for get/put_online_cpus() and cpu_hotplug_begin/end() */
#define cpuhp_lock_acquire_read() lock_map_acquire_read(&cpu_hotplug.dep_map)
#define cpuhp_lock_acquire_tryread() \
-@@ -268,8 +286,8 @@ void pin_current_cpu(void)
+@@ -268,8 +286,8 @@ retry:
return;
}
preempt_enable();
@@ -115,3 +115,6 @@ index 4b8f59bee8d9..9bb0d333bfc7 100644
cpuhp_lock_release();
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0285-cpu-rt-Rework-cpu-down-for-PREEMPT_RT.patch b/debian/patches/features/all/rt/0285-cpu-rt-Rework-cpu-down-for-PREEMPT_RT.patch
index a1713d8..1f7c90e 100644
--- a/debian/patches/features/all/rt/0285-cpu-rt-Rework-cpu-down-for-PREEMPT_RT.patch
+++ b/debian/patches/features/all/rt/0285-cpu-rt-Rework-cpu-down-for-PREEMPT_RT.patch
@@ -1,7 +1,7 @@
From: Steven Rostedt <srostedt at redhat.com>
Date: Mon, 16 Jul 2012 08:07:43 +0000
Subject: [PATCH 285/351] cpu/rt: Rework cpu down for PREEMPT_RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7e84328fe8e6bc6d33668ab9a1abfd6ee050c9ed
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3c9d5469540588bbba3240e21ebad0cd71cf4324
Bringing a CPU down is a pain with the PREEMPT_RT kernel because
tasks can be preempted in many more places than in non-RT. In
@@ -80,7 +80,7 @@ index f49f4970ce30..9bb98e2bc6d0 100644
#ifdef CONFIG_NO_HZ_COMMON
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index 9bb0d333bfc7..acac23803b36 100644
+index 238f11eb99ae..763512dfe168 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -210,16 +210,10 @@ static int cpu_hotplug_disabled;
@@ -529,3 +529,6 @@ index ca7927521f2f..0cbc7654192a 100644
/*
* Change a given task's CPU affinity. Migrate the thread to a
* proper CPU and schedule it away if the CPU it's executing on
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0286-cpu-hotplug-Document-why-PREEMPT_RT-uses-a-spinlock.patch b/debian/patches/features/all/rt/0286-cpu-hotplug-Document-why-PREEMPT_RT-uses-a-spinlock.patch
index 34159d8..2d0b113 100644
--- a/debian/patches/features/all/rt/0286-cpu-hotplug-Document-why-PREEMPT_RT-uses-a-spinlock.patch
+++ b/debian/patches/features/all/rt/0286-cpu-hotplug-Document-why-PREEMPT_RT-uses-a-spinlock.patch
@@ -1,7 +1,7 @@
From: Steven Rostedt <rostedt at goodmis.org>
Date: Thu, 5 Dec 2013 09:16:52 -0500
Subject: [PATCH 286/351] cpu hotplug: Document why PREEMPT_RT uses a spinlock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c369b45060503082bc6dbfbca35b28aed1eb8760
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=84d6282cc8498fd9fe22ed7043450c4706e32fac
The patch:
@@ -38,7 +38,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 8 insertions(+)
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index acac23803b36..82a409cf8c8a 100644
+index 763512dfe168..39d45e15db37 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -260,6 +260,14 @@ struct hotplug_pcp {
@@ -56,3 +56,6 @@ index acac23803b36..82a409cf8c8a 100644
spinlock_t lock;
#else
struct mutex mutex;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0287-kernel-cpu-fix-cpu-down-problem-if-kthread-s-cpu-is-.patch b/debian/patches/features/all/rt/0287-kernel-cpu-fix-cpu-down-problem-if-kthread-s-cpu-is-.patch
index 11d4e1f..1fec07a 100644
--- a/debian/patches/features/all/rt/0287-kernel-cpu-fix-cpu-down-problem-if-kthread-s-cpu-is-.patch
+++ b/debian/patches/features/all/rt/0287-kernel-cpu-fix-cpu-down-problem-if-kthread-s-cpu-is-.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 7 Jun 2013 22:37:06 +0200
Subject: [PATCH 287/351] kernel/cpu: fix cpu down problem if kthread's cpu is
going down
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=70b57c11672144bdc000a6a7596f317bdeaa9291
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6a73bc9c7e2a3b2feaeaaf5ffd5d177d07031670
If kthread is pinned to CPUx and CPUx is going down then we get into
trouble:
@@ -27,7 +27,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index 82a409cf8c8a..d4a29d33e52b 100644
+index 39d45e15db37..42e0d25e2a0c 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -259,6 +259,7 @@ struct hotplug_pcp {
@@ -87,3 +87,6 @@ index 82a409cf8c8a..d4a29d33e52b 100644
/* Park the smpboot threads */
kthread_park(per_cpu_ptr(&cpuhp_state, cpu)->thread);
smpboot_park_threads(cpu);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0288-kernel-hotplug-restore-original-cpu-mask-oncpu-down.patch b/debian/patches/features/all/rt/0288-kernel-hotplug-restore-original-cpu-mask-oncpu-down.patch
index 86da583..2de63db 100644
--- a/debian/patches/features/all/rt/0288-kernel-hotplug-restore-original-cpu-mask-oncpu-down.patch
+++ b/debian/patches/features/all/rt/0288-kernel-hotplug-restore-original-cpu-mask-oncpu-down.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 14 Jun 2013 17:16:35 +0200
Subject: [PATCH 288/351] kernel/hotplug: restore original cpu mask oncpu/down
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c6dc7df03df93744ccdf84c80c17486a7cfbc43c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f2b33955bd328bbb1f854e7ee5b78dd4a7b82f19
If a task which is allowed to run only on CPU X puts CPU Y down then it
will be allowed on all CPUs but the on CPU Y after it comes back from
@@ -15,7 +15,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index d4a29d33e52b..bdf5331e9afd 100644
+index 42e0d25e2a0c..38f834b63ccf 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -1179,6 +1179,7 @@ static int __ref _cpu_down(unsigned int cpu, int tasks_frozen,
@@ -49,7 +49,7 @@ index d4a29d33e52b..bdf5331e9afd 100644
}
cpu_hotplug_begin();
-@@ -1251,6 +1259,9 @@ static int __ref _cpu_down(unsigned int cpu, int tasks_frozen,
+@@ -1251,6 +1259,9 @@ out_cancel:
/* This post dead nonsense must die */
if (!ret && hasdied)
cpu_notify_nofail(CPU_POST_DEAD, cpu);
@@ -59,3 +59,6 @@ index d4a29d33e52b..bdf5331e9afd 100644
return ret;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0289-cpu_down-move-migrate_enable-back.patch b/debian/patches/features/all/rt/0289-cpu_down-move-migrate_enable-back.patch
index 1c5d5ab..6ef71f0 100644
--- a/debian/patches/features/all/rt/0289-cpu_down-move-migrate_enable-back.patch
+++ b/debian/patches/features/all/rt/0289-cpu_down-move-migrate_enable-back.patch
@@ -1,7 +1,7 @@
From: Tiejun Chen <tiejun.chen at windriver.com>
Date: Thu, 7 Nov 2013 10:06:07 +0800
Subject: [PATCH 289/351] cpu_down: move migrate_enable() back
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bbe0284060e7f564e9613b2d5edf47231364d56f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fa4e2c118abe239387aad3d0a06939cb49146f09
Commit 08c1ab68, "hotplug-use-migrate-disable.patch", intends to
use migrate_enable()/migrate_disable() to replace that combination
@@ -34,7 +34,7 @@ Signed-off-by: Tiejun Chen <tiejun.chen at windriver.com>
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index bdf5331e9afd..60774d291e3a 100644
+index 38f834b63ccf..174029461534 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -1208,6 +1208,7 @@ static int __ref _cpu_down(unsigned int cpu, int tasks_frozen,
@@ -45,7 +45,7 @@ index bdf5331e9afd..60774d291e3a 100644
cpu_hotplug_begin();
ret = cpu_unplug_begin(cpu);
if (ret) {
-@@ -1255,7 +1256,6 @@ static int __ref _cpu_down(unsigned int cpu, int tasks_frozen,
+@@ -1255,7 +1256,6 @@ out:
cpu_unplug_done(cpu);
out_cancel:
cpu_hotplug_done();
@@ -53,3 +53,6 @@ index bdf5331e9afd..60774d291e3a 100644
/* This post dead nonsense must die */
if (!ret && hasdied)
cpu_notify_nofail(CPU_POST_DEAD, cpu);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0290-hotplug-Use-set_cpus_allowed_ptr-in-sync_unplug_thre.patch b/debian/patches/features/all/rt/0290-hotplug-Use-set_cpus_allowed_ptr-in-sync_unplug_thre.patch
index 26c833b..02ed324 100644
--- a/debian/patches/features/all/rt/0290-hotplug-Use-set_cpus_allowed_ptr-in-sync_unplug_thre.patch
+++ b/debian/patches/features/all/rt/0290-hotplug-Use-set_cpus_allowed_ptr-in-sync_unplug_thre.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Tue, 24 Mar 2015 08:14:49 +0100
Subject: [PATCH 290/351] hotplug: Use set_cpus_allowed_ptr() in
sync_unplug_thread()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a774888bd016e57202db0372489986571d5b8b9d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e49c96468f541884a4ba2b54596f212f13e55b05
do_set_cpus_allowed() is not safe vs ->sched_class change.
@@ -36,7 +36,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
-index 60774d291e3a..010db3c943cd 100644
+index 174029461534..c6a4cf8ba645 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -418,7 +418,7 @@ static int sync_unplug_thread(void *data)
@@ -48,3 +48,6 @@ index 60774d291e3a..010db3c943cd 100644
migrate_me();
return 0;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0291-rt-locking-Reenable-migration-accross-schedule.patch b/debian/patches/features/all/rt/0291-rt-locking-Reenable-migration-accross-schedule.patch
index 2d26645..bff30a6 100644
--- a/debian/patches/features/all/rt/0291-rt-locking-Reenable-migration-accross-schedule.patch
+++ b/debian/patches/features/all/rt/0291-rt-locking-Reenable-migration-accross-schedule.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Mon, 8 Feb 2016 16:15:28 +0100
Subject: [PATCH 291/351] rt/locking: Reenable migration accross schedule
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7b00e0a9a809dbc2062c7dc7d2bd43e50243782b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c1eade0214f020acd609f2bf375b9cef7512872a
We currently disable migration across lock acquisition. That includes the part
where we block on the lock and schedule out. We cannot disable migration after
@@ -21,7 +21,7 @@ diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index 6e52bce66a26..78a6c4a223c1 100644
--- a/kernel/locking/rtmutex.c
+++ b/kernel/locking/rtmutex.c
-@@ -980,14 +980,19 @@ static int __try_to_take_rt_mutex(struct rt_mutex *lock,
+@@ -980,14 +980,19 @@ takeit:
* preemptible spin_lock functions:
*/
static inline void rt_spin_lock_fastlock(struct rt_mutex *lock,
@@ -112,3 +112,6 @@ index 6e52bce66a26..78a6c4a223c1 100644
}
EXPORT_SYMBOL(rt_spin_lock_nested);
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0292-scsi-qla2xxx-Use-local_irq_save_nort-in-qla2x00_poll.patch b/debian/patches/features/all/rt/0292-scsi-qla2xxx-Use-local_irq_save_nort-in-qla2x00_poll.patch
index cbfa5a3..bbc6aee 100644
--- a/debian/patches/features/all/rt/0292-scsi-qla2xxx-Use-local_irq_save_nort-in-qla2x00_poll.patch
+++ b/debian/patches/features/all/rt/0292-scsi-qla2xxx-Use-local_irq_save_nort-in-qla2x00_poll.patch
@@ -2,7 +2,7 @@ From: John Kacur <jkacur at redhat.com>
Date: Fri, 27 Apr 2012 12:48:46 +0200
Subject: [PATCH 292/351] scsi: qla2xxx: Use local_irq_save_nort() in
qla2x00_poll
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=74c7bcf76b9fc859076a39712f85a2c35c8a198f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=04aee504bdd4fd2a5df58d6af38f5682af0a51c7
RT triggers the following:
@@ -49,3 +49,6 @@ index edc48f3b8230..ee5c6f9dfb6f 100644
}
static inline uint8_t *
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0293-net-Remove-preemption-disabling-in-netif_rx.patch b/debian/patches/features/all/rt/0293-net-Remove-preemption-disabling-in-netif_rx.patch
index 8e93a80..b627310 100644
--- a/debian/patches/features/all/rt/0293-net-Remove-preemption-disabling-in-netif_rx.patch
+++ b/debian/patches/features/all/rt/0293-net-Remove-preemption-disabling-in-netif_rx.patch
@@ -1,7 +1,7 @@
From: Priyanka Jain <Priyanka.Jain at freescale.com>
Date: Thu, 17 May 2012 09:35:11 +0530
Subject: [PATCH 293/351] net: Remove preemption disabling in netif_rx()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=76a945030c2aa1b1a147dde8c637c5e204082240
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=35569b09c2b93f647d6c08f08edfb5c63d05cacf
1)enqueue_to_backlog() (called from netif_rx) should be
bind to a particluar CPU. This can be achieved by
@@ -35,10 +35,10 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/net/core/dev.c b/net/core/dev.c
-index d9e0da1032fd..63fcf5930077 100644
+index 661ec4bccdb9..059d956a4cde 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
-@@ -3822,7 +3822,7 @@ static int netif_rx_internal(struct sk_buff *skb)
+@@ -3823,7 +3823,7 @@ static int netif_rx_internal(struct sk_buff *skb)
struct rps_dev_flow voidflow, *rflow = &voidflow;
int cpu;
@@ -47,7 +47,7 @@ index d9e0da1032fd..63fcf5930077 100644
rcu_read_lock();
cpu = get_rps_cpu(skb->dev, skb, &rflow);
-@@ -3832,13 +3832,13 @@ static int netif_rx_internal(struct sk_buff *skb)
+@@ -3833,13 +3833,13 @@ static int netif_rx_internal(struct sk_buff *skb)
ret = enqueue_to_backlog(skb, cpu, &rflow->last_qtail);
rcu_read_unlock();
@@ -64,3 +64,6 @@ index d9e0da1032fd..63fcf5930077 100644
}
return ret;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0294-net-Another-local_irq_disable-kmalloc-headache.patch b/debian/patches/features/all/rt/0294-net-Another-local_irq_disable-kmalloc-headache.patch
index c6418c7..44efb27 100644
--- a/debian/patches/features/all/rt/0294-net-Another-local_irq_disable-kmalloc-headache.patch
+++ b/debian/patches/features/all/rt/0294-net-Another-local_irq_disable-kmalloc-headache.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 26 Sep 2012 16:21:08 +0200
Subject: [PATCH 294/351] net: Another local_irq_disable/kmalloc headache
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b09e398e61647cd4eb17d40fda51df2eb8e0593b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c1c7e6bef533c0706526916cc90d210b55883e6a
Replace it by a local lock. Though that's pretty inefficient :(
@@ -11,7 +11,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/net/core/skbuff.c b/net/core/skbuff.c
-index aec5605944d3..ba5d24bd9343 100644
+index a64515583bc1..b97ba2671638 100644
--- a/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -64,6 +64,7 @@
@@ -59,3 +59,6 @@ index aec5605944d3..ba5d24bd9343 100644
if (unlikely(!data))
return NULL;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0295-net-core-protect-users-of-napi_alloc_cache-against-r.patch b/debian/patches/features/all/rt/0295-net-core-protect-users-of-napi_alloc_cache-against-r.patch
index 586ff1c..3448c01 100644
--- a/debian/patches/features/all/rt/0295-net-core-protect-users-of-napi_alloc_cache-against-r.patch
+++ b/debian/patches/features/all/rt/0295-net-core-protect-users-of-napi_alloc_cache-against-r.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 15 Jan 2016 16:33:34 +0100
Subject: [PATCH 295/351] net/core: protect users of napi_alloc_cache against
reentrance
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c7ff1d45e4cae90938762c7ba67a28b9858eb8a4
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1bff1dce7a422790bb2c253545cf576a8d29810f
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
@@ -17,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/net/core/skbuff.c b/net/core/skbuff.c
-index ba5d24bd9343..d4cb8bfdb83c 100644
+index b97ba2671638..fec448d29f42 100644
--- a/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -362,6 +362,7 @@ struct napi_alloc_cache {
@@ -113,3 +113,6 @@ index ba5d24bd9343..d4cb8bfdb83c 100644
}
void __kfree_skb_defer(struct sk_buff *skb)
{
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0296-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch b/debian/patches/features/all/rt/0296-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch
index 7180f1c..0ca5ed5 100644
--- a/debian/patches/features/all/rt/0296-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch
+++ b/debian/patches/features/all/rt/0296-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch
@@ -2,7 +2,7 @@ From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 28 Oct 2012 11:18:08 +0100
Subject: [PATCH 296/351] net: netfilter: Serialize xt_write_recseq sections on
RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d4242ddc87ff26b3be11b15f9861ed107c53b69a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8df5a185fc0603a4325a2e6b64228dbf8dbf1797
The netfilter code relies only on the implicit semantics of
local_bh_disable() for serializing wt_write_recseq sections. RT breaks
@@ -55,7 +55,7 @@ index 2ad1a2b289b5..b4d10155af54 100644
/*
diff --git a/net/netfilter/core.c b/net/netfilter/core.c
-index 004af030ef1a..b64f751bda45 100644
+index d869ea50623e..5cafa87b030b 100644
--- a/net/netfilter/core.c
+++ b/net/netfilter/core.c
@@ -22,12 +22,18 @@
@@ -77,3 +77,6 @@ index 004af030ef1a..b64f751bda45 100644
static DEFINE_MUTEX(afinfo_mutex);
const struct nf_afinfo __rcu *nf_afinfo[NFPROTO_NUMPROTO] __read_mostly;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0297-net-Add-a-mutex-around-devnet_rename_seq.patch b/debian/patches/features/all/rt/0297-net-Add-a-mutex-around-devnet_rename_seq.patch
index 51e366e..73975a9 100644
--- a/debian/patches/features/all/rt/0297-net-Add-a-mutex-around-devnet_rename_seq.patch
+++ b/debian/patches/features/all/rt/0297-net-Add-a-mutex-around-devnet_rename_seq.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Wed, 20 Mar 2013 18:06:20 +0100
Subject: [PATCH 297/351] net: Add a mutex around devnet_rename_seq
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2ea4d8baee01167754071f787eaf00ac1cd38efc
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=649c760019983e37bc35ce10934d9e2f54d1209e
On RT write_seqcount_begin() disables preemption and device_rename()
allocates memory with GFP_KERNEL and grabs later the sysfs_mutex
@@ -21,7 +21,7 @@ Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
1 file changed, 20 insertions(+), 14 deletions(-)
diff --git a/net/core/dev.c b/net/core/dev.c
-index 63fcf5930077..3235360cd9a4 100644
+index 059d956a4cde..6cb279747408 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -190,6 +190,7 @@ static unsigned int napi_gen_id = NR_CPUS;
@@ -32,7 +32,7 @@ index 63fcf5930077..3235360cd9a4 100644
static inline void dev_base_seq_inc(struct net *net)
{
-@@ -888,7 +889,8 @@ int netdev_get_name(struct net *net, char *name, int ifindex)
+@@ -888,7 +889,8 @@ retry:
strcpy(name, dev->name);
rcu_read_unlock();
if (read_seqcount_retry(&devnet_rename_seq, seq)) {
@@ -69,7 +69,7 @@ index 63fcf5930077..3235360cd9a4 100644
if (oldname[0] && !strchr(oldname, '%'))
netdev_info(dev, "renamed from %s\n", oldname);
-@@ -1183,11 +1182,12 @@ int dev_change_name(struct net_device *dev, const char *newname)
+@@ -1183,11 +1182,12 @@ rollback:
if (ret) {
memcpy(dev->name, oldname, IFNAMSIZ);
dev->name_assign_type = old_assign_type;
@@ -85,7 +85,7 @@ index 63fcf5930077..3235360cd9a4 100644
netdev_adjacent_rename_links(dev, oldname);
-@@ -1208,7 +1208,8 @@ int dev_change_name(struct net_device *dev, const char *newname)
+@@ -1208,7 +1208,8 @@ rollback:
/* err >= 0 after dev_alloc_name() or stores the first errno */
if (err >= 0) {
err = ret;
@@ -95,7 +95,7 @@ index 63fcf5930077..3235360cd9a4 100644
memcpy(dev->name, oldname, IFNAMSIZ);
memcpy(oldname, newname, IFNAMSIZ);
dev->name_assign_type = old_assign_type;
-@@ -1221,6 +1222,11 @@ int dev_change_name(struct net_device *dev, const char *newname)
+@@ -1221,6 +1222,11 @@ rollback:
}
return err;
@@ -107,3 +107,6 @@ index 63fcf5930077..3235360cd9a4 100644
}
/**
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0298-crypto-Convert-crypto-notifier-chain-to-SRCU.patch b/debian/patches/features/all/rt/0298-crypto-Convert-crypto-notifier-chain-to-SRCU.patch
index 20b639a..84c9b11 100644
--- a/debian/patches/features/all/rt/0298-crypto-Convert-crypto-notifier-chain-to-SRCU.patch
+++ b/debian/patches/features/all/rt/0298-crypto-Convert-crypto-notifier-chain-to-SRCU.patch
@@ -1,7 +1,7 @@
From: Peter Zijlstra <peterz at infradead.org>
Date: Fri, 5 Oct 2012 09:03:24 +0100
Subject: [PATCH 298/351] crypto: Convert crypto notifier chain to SRCU
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=4636c57e58170846b7fd4f2972818f791f7e2134
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=906b2ed4933946027e3740438df7fcbd81c6ecef
The crypto notifier deadlocks on RT. Though this can be a real deadlock
on mainline as well due to fifo fair rwsems.
@@ -187,3 +187,6 @@ index 7eefcdb00227..0ecc7f5a2f40 100644
}
#endif /* _CRYPTO_INTERNAL_H */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0299-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch b/debian/patches/features/all/rt/0299-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch
index 783761e..ada31dc 100644
--- a/debian/patches/features/all/rt/0299-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch
+++ b/debian/patches/features/all/rt/0299-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch
@@ -2,7 +2,7 @@ From: Yong Zhang <yong.zhang at windriver.com>
Date: Mon, 16 Apr 2012 15:01:56 +0800
Subject: [PATCH 299/351] lockdep: selftest: Only do hardirq context test for
raw spinlock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=36a92dc20f553bd819a67f740c948c22f4f8b9a4
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b9a601e3829839d7c02b3d69e18fa2c62c971782
On -rt there is no softirq context any more and rwlock is sleepable,
disable softirq context test and rwlock+irq test.
@@ -56,3 +56,6 @@ index f3a217ea0388..c17fc0bd0aa3 100644
ww_tests();
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0300-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch b/debian/patches/features/all/rt/0300-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch
index 550de30..69c157c 100644
--- a/debian/patches/features/all/rt/0300-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch
+++ b/debian/patches/features/all/rt/0300-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch
@@ -2,7 +2,7 @@ From: Josh Cartwright <josh.cartwright at ni.com>
Date: Wed, 28 Jan 2015 13:08:45 -0600
Subject: [PATCH 300/351] lockdep: selftest: fix warnings due to missing
PREEMPT_RT conditionals
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=571900ac9608b1e04fa6240b62d018b4c493540e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b351c161584da286b859dbf973e07e851f0b044b
"lockdep: Selftest: Only do hardirq context test for raw spinlock"
disabled the execution of certain tests with PREEMPT_RT_FULL, but did
@@ -143,3 +143,6 @@ index c17fc0bd0aa3..4611b156ef79 100644
/*
* read-lock / write-lock recursion that is unsafe.
*/
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0301-perf-Make-swevent-hrtimer-run-in-irq-instead-of-soft.patch b/debian/patches/features/all/rt/0301-perf-Make-swevent-hrtimer-run-in-irq-instead-of-soft.patch
index c97c3ee..cef1c3a 100644
--- a/debian/patches/features/all/rt/0301-perf-Make-swevent-hrtimer-run-in-irq-instead-of-soft.patch
+++ b/debian/patches/features/all/rt/0301-perf-Make-swevent-hrtimer-run-in-irq-instead-of-soft.patch
@@ -2,7 +2,7 @@ From: Yong Zhang <yong.zhang at windriver.com>
Date: Wed, 11 Jul 2012 22:05:21 +0000
Subject: [PATCH 301/351] perf: Make swevent hrtimer run in irq instead of
softirq
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=37a9181f8cf7890b3948ae37c8cf7cd1eb82e9ea
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8f582018653d9b26d0339513359cfb310634de04
Otherwise we get a deadlock like below:
@@ -69,3 +69,6 @@ index 13b9784427b0..7e8e200fb441 100644
/*
* Since hrtimers have a fixed rate, we can do a static freq->period
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0302-kernel-perf-mark-perf_cpu_context-s-timer-as-irqsafe.patch b/debian/patches/features/all/rt/0302-kernel-perf-mark-perf_cpu_context-s-timer-as-irqsafe.patch
index 76da859..7084dc0 100644
--- a/debian/patches/features/all/rt/0302-kernel-perf-mark-perf_cpu_context-s-timer-as-irqsafe.patch
+++ b/debian/patches/features/all/rt/0302-kernel-perf-mark-perf_cpu_context-s-timer-as-irqsafe.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 4 Feb 2016 16:38:10 +0100
Subject: [PATCH 302/351] kernel/perf: mark perf_cpu_context's timer as irqsafe
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=90f34d60d1bda3b0d7dbbf4180a4ab7fab9ba3e1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=06466060d8344ad5b52330ec6bb9a965a2f50ee5
Otherwise we get a WARN_ON() backtrace and some events are reported as
"not counted".
@@ -25,3 +25,6 @@ index 7e8e200fb441..f74fbfe5465c 100644
}
static int perf_mux_hrtimer_restart(struct perf_cpu_context *cpuctx)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0303-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch b/debian/patches/features/all/rt/0303-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch
index daa5a49..b58bce2 100644
--- a/debian/patches/features/all/rt/0303-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch
+++ b/debian/patches/features/all/rt/0303-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Sun, 28 Oct 2012 13:26:09 +0000
Subject: [PATCH 303/351] rcu: Disable RCU_FAST_NO_HZ on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8895357589ca33b0df111d1e499037861216bb9e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fba717cfe268f738ee8ee0d31fef344b1fb6c647
This uses a timer_list timer from the irq disabled guts of the idle
code. Disable it for now to prevent wreckage.
@@ -24,3 +24,6 @@ index 1762f2521ebc..4811bfaa905c 100644
default n
help
This option permits CPUs to enter dynticks-idle state even if
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0304-rcu-Eliminate-softirq-processing-from-rcutree.patch b/debian/patches/features/all/rt/0304-rcu-Eliminate-softirq-processing-from-rcutree.patch
index 3952dbe..b0b88d4 100644
--- a/debian/patches/features/all/rt/0304-rcu-Eliminate-softirq-processing-from-rcutree.patch
+++ b/debian/patches/features/all/rt/0304-rcu-Eliminate-softirq-processing-from-rcutree.patch
@@ -1,7 +1,7 @@
From: "Paul E. McKenney" <paulmck at linux.vnet.ibm.com>
Date: Mon, 4 Nov 2013 13:21:10 -0800
Subject: [PATCH 304/351] rcu: Eliminate softirq processing from rcutree
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9fee96270f06a19be19f642b8e4ce0a87fca4030
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3d879fe4f2329026a3b5ea60f03936c6e0224dc8
Running RCU out of softirq is a problem for some workloads that would
like to manage RCU core processing independently of other softirq work,
@@ -439,3 +439,6 @@ index a375276227a8..be12d1aac840 100644
static bool rcu_is_callbacks_kthread(void)
{
return false;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0305-rcu-make-RCU_BOOST-default-on-RT.patch b/debian/patches/features/all/rt/0305-rcu-make-RCU_BOOST-default-on-RT.patch
index 8c6c543..597eae2 100644
--- a/debian/patches/features/all/rt/0305-rcu-make-RCU_BOOST-default-on-RT.patch
+++ b/debian/patches/features/all/rt/0305-rcu-make-RCU_BOOST-default-on-RT.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 21 Mar 2014 20:19:05 +0100
Subject: [PATCH 305/351] rcu: make RCU_BOOST default on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7732cf7e3178229e93d2530f8ff4e30eeaf370a2
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=dce2cf05ecbdbeefc865df36d6e4207a2502a880
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
@@ -35,3 +35,6 @@ index 4811bfaa905c..2ce33a32e65d 100644
help
This option boosts the priority of preempted RCU readers that
block the current preemptible RCU grace period for too long.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0306-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch b/debian/patches/features/all/rt/0306-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch
index f69f84e..1e37b07 100644
--- a/debian/patches/features/all/rt/0306-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch
+++ b/debian/patches/features/all/rt/0306-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch
@@ -1,7 +1,7 @@
From: Julia Cartwright <julia at ni.com>
Date: Wed, 12 Oct 2016 11:21:14 -0500
Subject: [PATCH 306/351] rcu: enable rcu_normal_after_boot by default for RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=436aebe7d675e3a234e2a961a92f8772a0126725
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c73197671291b99e17a0b7d5f7c4f53db7580f25
The forcing of an expedited grace period is an expensive and very
RT-application unfriendly operation, as it forcibly preempts all running
@@ -30,3 +30,6 @@ index 949714f485ee..ee02e1e1b3e5 100644
module_param(rcu_normal_after_boot, int, 0);
#endif /* #ifndef CONFIG_TINY_RCU */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0307-sched-Add-support-for-lazy-preemption.patch b/debian/patches/features/all/rt/0307-sched-Add-support-for-lazy-preemption.patch
index 7a8ce18..7f20450 100644
--- a/debian/patches/features/all/rt/0307-sched-Add-support-for-lazy-preemption.patch
+++ b/debian/patches/features/all/rt/0307-sched-Add-support-for-lazy-preemption.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 26 Oct 2012 18:50:54 +0100
Subject: [PATCH 307/351] sched: Add support for lazy preemption
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2c5d2d126e0f30f647697b91068e7f113ae47960
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=70684857fa6c605cb4170b716c4a865b9824efb3
It has become an obsession to mitigate the determinism vs. throughput
loss of RT. Looking at the mainline semantics of preemption points
@@ -368,7 +368,7 @@ index 0cbc7654192a..f29c4f961104 100644
* The idle tasks have their own, simple scheduling class:
*/
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
-index 7a68c631d5b5..f9189909640b 100644
+index 3d862f5b0331..c6db32c0c557 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -3518,7 +3518,7 @@ check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr)
@@ -444,7 +444,7 @@ index 7a68c631d5b5..f9189909640b 100644
check_preempt_curr(rq, p, 0);
}
diff --git a/kernel/sched/features.h b/kernel/sched/features.h
-index 11258a0feae7..6d28fcd08872 100644
+index 852cfc5bb77b..36086f74e011 100644
--- a/kernel/sched/features.h
+++ b/kernel/sched/features.h
@@ -47,6 +47,9 @@ SCHED_FEAT(NONTASK_CAPACITY, true)
@@ -478,7 +478,7 @@ index 5dc95852c984..280c7d5a7657 100644
extern void init_rt_bandwidth(struct rt_bandwidth *rt_b, u64 period, u64 runtime);
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
-index 2b7caaae94a2..b9cf63aba3f9 100644
+index 038f9b758913..d7c01658f877 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1897,6 +1897,7 @@ tracing_generic_entry_update(struct trace_entry *entry, unsigned long flags,
@@ -611,3 +611,6 @@ index badf130635f1..65a6dde71a7d 100644
if (entry->migrate_disable)
trace_seq_printf(s, "%x", entry->migrate_disable);
else
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0308-ftrace-Fix-trace-header-alignment.patch b/debian/patches/features/all/rt/0308-ftrace-Fix-trace-header-alignment.patch
index 01523ea..76f3223 100644
--- a/debian/patches/features/all/rt/0308-ftrace-Fix-trace-header-alignment.patch
+++ b/debian/patches/features/all/rt/0308-ftrace-Fix-trace-header-alignment.patch
@@ -1,7 +1,7 @@
From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Sun, 16 Oct 2016 05:08:30 +0200
Subject: [PATCH 308/351] ftrace: Fix trace header alignment
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=198898d0b36d33c37ddeb095f6cd4e652a685a60
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=255b20357219600c936267e6e76adb99fbdd3d17
Line up helper arrows to the right column.
@@ -14,7 +14,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
-index b9cf63aba3f9..035e61604455 100644
+index d7c01658f877..00d9ebcf42e2 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -2902,17 +2902,17 @@ get_total_entries(struct trace_buffer *buf,
@@ -63,3 +63,6 @@ index b9cf63aba3f9..035e61604455 100644
}
void
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0310-arm-Add-support-for-lazy-preemption.patch b/debian/patches/features/all/rt/0310-arm-Add-support-for-lazy-preemption.patch
index d6bf748..c14a289 100644
--- a/debian/patches/features/all/rt/0310-arm-Add-support-for-lazy-preemption.patch
+++ b/debian/patches/features/all/rt/0310-arm-Add-support-for-lazy-preemption.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 31 Oct 2012 12:04:11 +0100
Subject: [PATCH 310/351] arm: Add support for lazy preemption
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b8ff2d525cbd016c6398530c8418aa689d75cf53
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f1525c3e455016b38cc009bea13b8e6ac346e814
Implement the arm pieces for lazy preempt.
@@ -83,7 +83,7 @@ diff --git a/arch/arm/kernel/entry-armv.S b/arch/arm/kernel/entry-armv.S
index 9f157e7c51e7..468e224d76aa 100644
--- a/arch/arm/kernel/entry-armv.S
+++ b/arch/arm/kernel/entry-armv.S
-@@ -220,11 +220,18 @@ ENDPROC(__dabt_svc)
+@@ -220,11 +220,18 @@ __irq_svc:
#ifdef CONFIG_PREEMPT
ldr r8, [tsk, #TI_PREEMPT] @ get preempt count
@@ -104,7 +104,7 @@ index 9f157e7c51e7..468e224d76aa 100644
#endif
svc_exit r5, irq = 1 @ return from exception
-@@ -239,8 +246,14 @@ ENDPROC(__irq_svc)
+@@ -239,8 +246,14 @@ svc_preempt:
1: bl preempt_schedule_irq @ irq en/disable is done inside
ldr r0, [tsk, #TI_FLAGS] @ get new tasks TI_FLAGS
tst r0, #_TIF_NEED_RESCHED
@@ -124,7 +124,7 @@ diff --git a/arch/arm/kernel/entry-common.S b/arch/arm/kernel/entry-common.S
index 10c3283d6c19..8872937862cc 100644
--- a/arch/arm/kernel/entry-common.S
+++ b/arch/arm/kernel/entry-common.S
-@@ -36,7 +36,9 @@
+@@ -36,7 +36,9 @@ ret_fast_syscall:
UNWIND(.cantunwind )
disable_irq_notrace @ disable interrupts
ldr r1, [tsk, #TI_FLAGS] @ re-check for syscall tracing
@@ -135,7 +135,7 @@ index 10c3283d6c19..8872937862cc 100644
bne fast_work_pending
/* perform architecture specific actions before user return */
-@@ -62,8 +64,11 @@ ENDPROC(ret_fast_syscall)
+@@ -62,8 +64,11 @@ ret_fast_syscall:
str r0, [sp, #S_R0 + S_OFF]! @ save returned r0
disable_irq_notrace @ disable interrupts
ldr r1, [tsk, #TI_FLAGS] @ re-check for syscall tracing
@@ -162,3 +162,6 @@ index 7b8f2141427b..96541e00b74a 100644
schedule();
} else {
if (unlikely(!user_mode(regs)))
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0311-powerpc-Add-support-for-lazy-preemption.patch b/debian/patches/features/all/rt/0311-powerpc-Add-support-for-lazy-preemption.patch
index 42fc66c..df2ffb4 100644
--- a/debian/patches/features/all/rt/0311-powerpc-Add-support-for-lazy-preemption.patch
+++ b/debian/patches/features/all/rt/0311-powerpc-Add-support-for-lazy-preemption.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Thu, 1 Nov 2012 10:14:11 +0100
Subject: [PATCH 311/351] powerpc: Add support for lazy preemption
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8ce92e7ac88988f59f2a8f300ab2235805d16f21
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f6af764099f79c3afb9d1f2c41714c489121f0f6
Implement the powerpc pieces for lazy preempt.
@@ -92,7 +92,7 @@ diff --git a/arch/powerpc/kernel/entry_32.S b/arch/powerpc/kernel/entry_32.S
index 3841d749a430..6dbaeff192b9 100644
--- a/arch/powerpc/kernel/entry_32.S
+++ b/arch/powerpc/kernel/entry_32.S
-@@ -835,7 +835,14 @@ user_exc_return: /* r10 contains MSR_KERNEL here */
+@@ -835,7 +835,14 @@ resume_kernel:
cmpwi 0,r0,0 /* if non-zero, just restore regs and return */
bne restore
andi. r8,r8,_TIF_NEED_RESCHED
@@ -107,7 +107,7 @@ index 3841d749a430..6dbaeff192b9 100644
lwz r3,_MSR(r1)
andi. r0,r3,MSR_EE /* interrupts off? */
beq restore /* don't schedule if so */
-@@ -846,11 +853,11 @@ user_exc_return: /* r10 contains MSR_KERNEL here */
+@@ -846,11 +853,11 @@ resume_kernel:
*/
bl trace_hardirqs_off
#endif
@@ -122,7 +122,7 @@ index 3841d749a430..6dbaeff192b9 100644
#ifdef CONFIG_TRACE_IRQFLAGS
/* And now, to properly rebalance the above, we tell lockdep they
* are being turned back on, which will happen when we return
-@@ -1171,7 +1178,7 @@ END_FTR_SECTION_IFSET(CPU_FTR_NEED_PAIRED_STWCX)
+@@ -1171,7 +1178,7 @@ global_dbcr0:
#endif /* !(CONFIG_4xx || CONFIG_BOOKE) */
do_work: /* r10 contains MSR_KERNEL here */
@@ -131,7 +131,7 @@ index 3841d749a430..6dbaeff192b9 100644
beq do_user_signal
do_resched: /* r10 contains MSR_KERNEL here */
-@@ -1192,7 +1199,7 @@ do_resched: /* r10 contains MSR_KERNEL here */
+@@ -1192,7 +1199,7 @@ recheck:
MTMSRD(r10) /* disable interrupts */
CURRENT_THREAD_INFO(r9, r1)
lwz r9,TI_FLAGS(r9)
@@ -153,7 +153,7 @@ index caa659671599..891080c4a41e 100644
beq 2f
bl restore_interrupts
SCHEDULE_USER
-@@ -718,10 +718,18 @@ _GLOBAL(ret_from_except_lite)
+@@ -718,10 +718,18 @@ resume_kernel:
#ifdef CONFIG_PREEMPT
/* Check if we need to preempt */
@@ -173,7 +173,7 @@ index caa659671599..891080c4a41e 100644
cmpwi cr1,r8,0
ld r0,SOFTE(r1)
cmpdi r0,0
-@@ -738,7 +746,7 @@ _GLOBAL(ret_from_except_lite)
+@@ -738,7 +746,7 @@ resume_kernel:
/* Re-test flags and eventually loop */
CURRENT_THREAD_INFO(r9, r1)
ld r4,TI_FLAGS(r9)
@@ -182,3 +182,6 @@ index caa659671599..891080c4a41e 100644
bne 1b
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0312-arch-arm64-Add-lazy-preempt-support.patch b/debian/patches/features/all/rt/0312-arch-arm64-Add-lazy-preempt-support.patch
index b499b26..a1e3dbb 100644
--- a/debian/patches/features/all/rt/0312-arch-arm64-Add-lazy-preempt-support.patch
+++ b/debian/patches/features/all/rt/0312-arch-arm64-Add-lazy-preempt-support.patch
@@ -1,7 +1,7 @@
From: Anders Roxell <anders.roxell at linaro.org>
Date: Thu, 14 May 2015 17:52:17 +0200
Subject: [PATCH 312/351] arch/arm64: Add lazy preempt support
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6ec4b293ac451ca722e586b76f9d30ea7cdf09a1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b62f9f211a57bab9f2f1d1d969fe8ba291c91325
arm64 is missing support for PREEMPT_RT. The main feature which is
lacking is support for lazy preemption. The arch-specific entry code,
@@ -86,7 +86,7 @@ diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
index b4c7db434654..433d846f4f51 100644
--- a/arch/arm64/kernel/entry.S
+++ b/arch/arm64/kernel/entry.S
-@@ -430,11 +430,16 @@ ENDPROC(el1_sync)
+@@ -430,11 +430,16 @@ el1_irq:
#ifdef CONFIG_PREEMPT
ldr w24, [tsk, #TI_PREEMPT] // get preempt count
@@ -106,7 +106,7 @@ index b4c7db434654..433d846f4f51 100644
#endif
#ifdef CONFIG_TRACE_IRQFLAGS
bl trace_hardirqs_on
-@@ -448,6 +453,7 @@ ENDPROC(el1_irq)
+@@ -448,6 +453,7 @@ el1_preempt:
1: bl preempt_schedule_irq // irq en/disable is done inside
ldr x0, [tsk, #TI_FLAGS] // get new tasks TI_FLAGS
tbnz x0, #TIF_NEED_RESCHED, 1b // needs rescheduling?
@@ -127,3 +127,6 @@ index 404dd67080b9..639dc6d12e72 100644
schedule();
} else {
local_irq_enable();
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0313-sched-migrate-disable-handle-updated-task-mask-mg-di.patch b/debian/patches/features/all/rt/0313-sched-migrate-disable-handle-updated-task-mask-mg-di.patch
index f414066..c268d31 100644
--- a/debian/patches/features/all/rt/0313-sched-migrate-disable-handle-updated-task-mask-mg-di.patch
+++ b/debian/patches/features/all/rt/0313-sched-migrate-disable-handle-updated-task-mask-mg-di.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 19 Jun 2017 09:55:47 +0200
Subject: [PATCH 313/351] sched/migrate disable: handle updated task-mask
mg-dis section
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=14a5e6b25964132c71db01033b3ffafaff21570b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=0c05aacc2ebbcc9dd3bee25dc486c1411d0d4b27
If task's cpumask changes while in the task is in a migrate_disable()
section then we don't react on it after a migrate_enable(). It matters
@@ -123,3 +123,6 @@ index f29c4f961104..5ebcf53bcf3d 100644
unpin_current_cpu();
preempt_enable();
preempt_lazy_enable();
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0314-leds-trigger-disable-CPU-trigger-on-RT.patch b/debian/patches/features/all/rt/0314-leds-trigger-disable-CPU-trigger-on-RT.patch
index 6c12d1d..f9da27a 100644
--- a/debian/patches/features/all/rt/0314-leds-trigger-disable-CPU-trigger-on-RT.patch
+++ b/debian/patches/features/all/rt/0314-leds-trigger-disable-CPU-trigger-on-RT.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 23 Jan 2014 14:45:59 +0100
Subject: [PATCH 314/351] leds: trigger: disable CPU trigger on -RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a8d759127f947af0c00900717240e2ba2264661b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=76c2d58c1495cb5e7658be76861707d9c54e0ed6
as it triggers:
|CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.8-rt10 #141
@@ -36,3 +36,6 @@ index 3f9ddb9fafa7..09da5b6b44a1 100644
help
This allows LEDs to be controlled by active CPUs. This shows
the active CPUs across an array of LEDs so you can see which
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0315-mmci-Remove-bogus-local_irq_save.patch b/debian/patches/features/all/rt/0315-mmci-Remove-bogus-local_irq_save.patch
index 67ed816..4498bf4 100644
--- a/debian/patches/features/all/rt/0315-mmci-Remove-bogus-local_irq_save.patch
+++ b/debian/patches/features/all/rt/0315-mmci-Remove-bogus-local_irq_save.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Wed, 9 Jan 2013 12:11:12 +0100
Subject: [PATCH 315/351] mmci: Remove bogus local_irq_save()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=02a70dc0f9118eee331b58cd05163ebd4c889e13
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=027f376f0b30586ea90c9718fc9a3c09520bdbaf
On !RT interrupt runs with interrupts disabled. On RT it's in a
thread, so no need to disable interrupts at all.
@@ -40,3 +40,6 @@ index df990bb8c873..1a162709a85e 100644
/*
* If we have less than the fifo 'half-full' threshold to transfer,
* trigger a PIO interrupt as soon as any data is available.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0316-cpufreq-drop-K8-s-driver-from-beeing-selected.patch b/debian/patches/features/all/rt/0316-cpufreq-drop-K8-s-driver-from-beeing-selected.patch
index 86d846c..a69246b 100644
--- a/debian/patches/features/all/rt/0316-cpufreq-drop-K8-s-driver-from-beeing-selected.patch
+++ b/debian/patches/features/all/rt/0316-cpufreq-drop-K8-s-driver-from-beeing-selected.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 9 Apr 2015 15:23:01 +0200
Subject: [PATCH 316/351] cpufreq: drop K8's driver from beeing selected
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f9200334d1976edc4edd04b948aaa96c76f06308
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5f4b5f0ad639d0229a2729374340af867407d83c
Ralf posted a picture of a backtrace from
@@ -33,3 +33,6 @@ index adbd1de1cea5..1fac5074f2cf 100644
help
This adds the CPUFreq driver for K8/early Opteron/Athlon64 processors.
Support for K10 and newer processors is now in acpi-cpufreq.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0317-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch b/debian/patches/features/all/rt/0317-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch
index c8b139b..07f5167 100644
--- a/debian/patches/features/all/rt/0317-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch
+++ b/debian/patches/features/all/rt/0317-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Sun, 16 Oct 2016 05:11:54 +0200
Subject: [PATCH 317/351] connector/cn_proc: Protect send_msg() with a local
lock on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e57e7544cf7b025afa86e6075bff43f585f2f868
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=52c0ab186058ba4c6b4b0ecf9253a6ebe5a5f3df
|BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:931
|in_atomic(): 1, irqs_disabled(): 0, pid: 31807, name: sleep
@@ -68,3 +68,6 @@ index a782ce87715c..19d265948526 100644
}
void proc_fork_connector(struct task_struct *task)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0318-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch b/debian/patches/features/all/rt/0318-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch
index c1622e3..ecdb419 100644
--- a/debian/patches/features/all/rt/0318-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch
+++ b/debian/patches/features/all/rt/0318-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Thu, 31 Mar 2016 04:08:28 +0200
Subject: [PATCH 318/351] drivers/block/zram: Replace bit spinlocks with
rtmutex for -rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=507cbeeef86ab05ca72369d5bbda8e8b8d68e0d0
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7350eb986f8fe252f549ffdca187625a19d1ca96
They're nondeterministic, and lead to ___might_sleep() splats in -rt.
OTOH, they're a lot less wasteful than an rtmutex per page.
@@ -15,7 +15,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
2 files changed, 57 insertions(+), 14 deletions(-)
diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
-index c9914d653968..553954c4ffd0 100644
+index b7c0b69a02f5..22009186b3df 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -528,6 +528,8 @@ static struct zram_meta *zram_meta_alloc(char *pool_name, u64 disksize)
@@ -69,7 +69,7 @@ index c9914d653968..553954c4ffd0 100644
if (is_partial_io(bvec))
/* Use a temporary buffer to decompress the page */
-@@ -700,10 +702,10 @@ static int zram_bvec_write(struct zram *zram, struct bio_vec *bvec, u32 index,
+@@ -700,10 +702,10 @@ compress_again:
if (user_mem)
kunmap_atomic(user_mem);
/* Free memory associated with this sector now. */
@@ -82,7 +82,7 @@ index c9914d653968..553954c4ffd0 100644
atomic64_inc(&zram->stats.zero_pages);
ret = 0;
-@@ -794,12 +796,12 @@ static int zram_bvec_write(struct zram *zram, struct bio_vec *bvec, u32 index,
+@@ -794,12 +796,12 @@ compress_again:
* Free memory associated with this sector
* before overwriting unused sectors.
*/
@@ -178,3 +178,6 @@ index 74fcf10da374..fd4020c99b9e 100644
+#endif /* CONFIG_PREEMPT_RT_BASE */
+
#endif
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0319-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch b/debian/patches/features/all/rt/0319-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch
index d88292a..e2cb05a 100644
--- a/debian/patches/features/all/rt/0319-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch
+++ b/debian/patches/features/all/rt/0319-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Thu, 20 Oct 2016 11:15:22 +0200
Subject: [PATCH 319/351] drivers/zram: Don't disable preemption in
zcomp_stream_get/put()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=62a4340558f78756267ca9182939f1423dec2fb0
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=419fe7dc006767e3be9e00494fbebd2f6bbb5dad
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
@@ -66,7 +66,7 @@ index 478cac2ed465..f7a6efdc3285 100644
/* dynamic per-device compression frontend */
diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
-index 553954c4ffd0..2038d138f286 100644
+index 22009186b3df..47d033b8a966 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -577,6 +577,7 @@ static int zram_decompress_page(struct zram *zram, char *mem, u32 index)
@@ -96,3 +96,6 @@ index 553954c4ffd0..2038d138f286 100644
zram_unlock_table(&meta->table[index]);
/* Should NEVER happen. Return bio error if it does. */
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0320-drm-i915-drop-trace_i915_gem_ring_dispatch-on-rt.patch b/debian/patches/features/all/rt/0320-drm-i915-drop-trace_i915_gem_ring_dispatch-on-rt.patch
index b8e4d83..2533419 100644
--- a/debian/patches/features/all/rt/0320-drm-i915-drop-trace_i915_gem_ring_dispatch-on-rt.patch
+++ b/debian/patches/features/all/rt/0320-drm-i915-drop-trace_i915_gem_ring_dispatch-on-rt.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 25 Apr 2013 18:12:52 +0200
Subject: [PATCH 320/351] drm/i915: drop trace_i915_gem_ring_dispatch on rt
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8b2e58eefcb7fcdcaec8784d337b0f16bd8d09f4
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=be516ee5933e851efaa452b4b0d60fcd5fa43a67
This tracepoint is responsible for:
@@ -59,3 +59,6 @@ index 2117f172d7a2..96c15501b0c8 100644
i915_gem_execbuffer_move_to_active(vmas, params->request);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0321-i915-bogus-warning-from-i915-when-running-on-PREEMPT.patch b/debian/patches/features/all/rt/0321-i915-bogus-warning-from-i915-when-running-on-PREEMPT.patch
index b60e4c5..c0dd47c 100644
--- a/debian/patches/features/all/rt/0321-i915-bogus-warning-from-i915-when-running-on-PREEMPT.patch
+++ b/debian/patches/features/all/rt/0321-i915-bogus-warning-from-i915-when-running-on-PREEMPT.patch
@@ -2,7 +2,7 @@ From: Clark Williams <williams at redhat.com>
Date: Tue, 26 May 2015 10:43:43 -0500
Subject: [PATCH 321/351] i915: bogus warning from i915 when running on
PREEMPT_RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3586546287ee8cb1dc3ce800801b4fd28c8568f6
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7af22022d5c62c4ffca621f9d6b47e73889d77a0
The i915 driver has a 'WARN_ON(!in_interrupt())' in the display
handler, which whines constanly on the RT kernel (since the interrupt
@@ -31,3 +31,6 @@ index ce32303b3013..c0a53bf2e952 100644
if (crtc == NULL)
return;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0322-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch b/debian/patches/features/all/rt/0322-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch
index c814670..5425973 100644
--- a/debian/patches/features/all/rt/0322-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch
+++ b/debian/patches/features/all/rt/0322-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Sat, 27 Feb 2016 08:09:11 +0100
Subject: [PATCH 322/351] drm,radeon,i915: Use preempt_disable/enable_rt()
where recommended
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=34471fd99c235a53994099d8c7bd31ab93563809
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=195163c9fa406e44133574a84ee83683169dcfbd
DRM folks identified the spots, so use them.
@@ -55,3 +55,6 @@ index cdb8cb568c15..b6d7fd964cbc 100644
/* Decode into vertical and horizontal scanout position. */
*vpos = position & 0x1fff;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0323-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch b/debian/patches/features/all/rt/0323-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch
index 8da478d..9fdbf97 100644
--- a/debian/patches/features/all/rt/0323-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch
+++ b/debian/patches/features/all/rt/0323-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Sat, 27 Feb 2016 09:01:42 +0100
Subject: [PATCH 323/351] drm,i915: Use local_lock/unlock_irq() in
intel_pipe_update_start/end()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c4c7dae41db444bdcc8b5640fa34959ce624926c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=309ef074390494f64b1f2a8b01b63f90889f419d
[ 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
@@ -113,3 +113,6 @@ index 64f4e2e18594..aebf1e9eabcb 100644
if (crtc->debug.start_vbl_count &&
crtc->debug.start_vbl_count != end_vbl_count) {
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0324-cgroups-use-simple-wait-in-css_release.patch b/debian/patches/features/all/rt/0324-cgroups-use-simple-wait-in-css_release.patch
index 1af8aae..facef33 100644
--- a/debian/patches/features/all/rt/0324-cgroups-use-simple-wait-in-css_release.patch
+++ b/debian/patches/features/all/rt/0324-cgroups-use-simple-wait-in-css_release.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 13 Feb 2015 15:52:24 +0100
Subject: [PATCH 324/351] cgroups: use simple wait in css_release()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b33a2df01d133458ee4ec982365ae44684f8f615
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5dc4b51f10301471528b6ed80c5b6a67b42225b1
To avoid:
|BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914
@@ -89,3 +89,6 @@ index 4c233437ee1a..6c3c9f298f22 100644
/*
* Used to destroy pidlists and separate to serve as flush domain.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0325-memcontrol-Prevent-scheduling-while-atomic-in-cgroup.patch b/debian/patches/features/all/rt/0325-memcontrol-Prevent-scheduling-while-atomic-in-cgroup.patch
index a857395..a45d218 100644
--- a/debian/patches/features/all/rt/0325-memcontrol-Prevent-scheduling-while-atomic-in-cgroup.patch
+++ b/debian/patches/features/all/rt/0325-memcontrol-Prevent-scheduling-while-atomic-in-cgroup.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <umgwanakikbuti at gmail.com>
Date: Sat, 21 Jun 2014 10:09:48 +0200
Subject: [PATCH 325/351] memcontrol: Prevent scheduling while atomic in cgroup
code
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=8eb6172be3a753b8f055d02f201e77383dda3c7d
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d2d84fda3684649c86d4c78327b686614f818588
mm, memcg: make refill_stock() use get_cpu_light()
@@ -106,3 +106,6 @@ index c04403033aec..12b94909ba7b 100644
}
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0326-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch b/debian/patches/features/all/rt/0326-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch
index 0519d2a..692f763 100644
--- a/debian/patches/features/all/rt/0326-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch
+++ b/debian/patches/features/all/rt/0326-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch
@@ -1,7 +1,7 @@
From: Mike Galbraith <efault at gmx.de>
Date: Sun, 8 Jan 2017 09:32:25 +0100
Subject: [PATCH 326/351] cpuset: Convert callback_lock to raw_spinlock_t
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=fb16993886c091ebb046017f619792529bb517ce
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b4e9ef48ff0a2876b306df849130782397fe599a
The two commits below add up to a cpuset might_sleep() splat for RT:
@@ -287,3 +287,6 @@ index 511b1dd8ff09..1dd63833ecdc 100644
return allowed;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0327-rt-ntp-Move-call-to-schedule_delayed_work-to-helper-.patch b/debian/patches/features/all/rt/0327-rt-ntp-Move-call-to-schedule_delayed_work-to-helper-.patch
index dc9fc70..2ba3056 100644
--- a/debian/patches/features/all/rt/0327-rt-ntp-Move-call-to-schedule_delayed_work-to-helper-.patch
+++ b/debian/patches/features/all/rt/0327-rt-ntp-Move-call-to-schedule_delayed_work-to-helper-.patch
@@ -2,7 +2,7 @@ From: Steven Rostedt <rostedt at goodmis.org>
Date: Wed, 26 Jun 2013 15:28:11 -0400
Subject: [PATCH 327/351] rt,ntp: Move call to schedule_delayed_work() to
helper thread
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=00b2577fb82e975388956f5682262fa3f505b224
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=dcaedb3b02fdede71bdcf1c48c92fb62d08c0f3a
The ntp code for notify_cmos_timer() is called from a hard interrupt
context. schedule_delayed_work() under PREEMPT_RT_FULL calls spinlocks
@@ -74,3 +74,6 @@ index 6df8927c58a5..05b7391bf9bd 100644
#else
void ntp_notify_cmos_timer(void) { }
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0328-md-disable-bcache.patch b/debian/patches/features/all/rt/0328-md-disable-bcache.patch
index 8646dc5..8e59d89 100644
--- a/debian/patches/features/all/rt/0328-md-disable-bcache.patch
+++ b/debian/patches/features/all/rt/0328-md-disable-bcache.patch
@@ -4,7 +4,7 @@ Subject: [PATCH 328/351] md: disable bcache
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3476cfc22712f8a55bce8fdb6cfac13795fc4193
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=9adc4bd07cddb951f47595a0c79b8a7bae5f9ca5
It uses anon semaphores
|drivers/md/bcache/request.c: In function ‘cached_dev_write_complete’:
@@ -35,3 +35,6 @@ index 4d200883c505..98b64ed5cb81 100644
---help---
Allows a block device to be used as cache for other devices; uses
a btree for indexing and the layout is optimized for SSDs.
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0329-workqueue-Prevent-deadlock-stall-on-RT.patch b/debian/patches/features/all/rt/0329-workqueue-Prevent-deadlock-stall-on-RT.patch
index 52db8f1..fa12c2f 100644
--- a/debian/patches/features/all/rt/0329-workqueue-Prevent-deadlock-stall-on-RT.patch
+++ b/debian/patches/features/all/rt/0329-workqueue-Prevent-deadlock-stall-on-RT.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 27 Jun 2014 16:24:52 +0200
Subject: [PATCH 329/351] workqueue: Prevent deadlock/stall on RT
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=45d0394b436c76c5e592eb0b8e85e77d870ad413
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2ee1eb724e95a3d8748b244ac2816de63b2d5ad0
Austin reported a XFS deadlock/stall on RT where scheduled work gets
never exececuted and tasks are waiting for each other for ever.
@@ -68,7 +68,7 @@ index 5ebcf53bcf3d..ed1ebcc2ff3d 100644
* If we are going to sleep and we have plugged IO queued,
* make sure to submit it to avoid deadlocks.
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
-index 4bb9113bd1f9..beee8ad4b9ea 100644
+index 618ce6bae95a..7eed129f114a 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -124,6 +124,11 @@ enum {
@@ -172,7 +172,7 @@ index 4bb9113bd1f9..beee8ad4b9ea 100644
}
/**
-@@ -1632,7 +1660,9 @@ static void worker_enter_idle(struct worker *worker)
+@@ -1633,7 +1661,9 @@ static void worker_enter_idle(struct worker *worker)
worker->last_active = jiffies;
/* idle_list is LIFO */
@@ -182,7 +182,7 @@ index 4bb9113bd1f9..beee8ad4b9ea 100644
if (too_many_workers(pool) && !timer_pending(&pool->idle_timer))
mod_timer(&pool->idle_timer, jiffies + IDLE_WORKER_TIMEOUT);
-@@ -1665,7 +1695,9 @@ static void worker_leave_idle(struct worker *worker)
+@@ -1666,7 +1696,9 @@ static void worker_leave_idle(struct worker *worker)
return;
worker_clr_flags(worker, WORKER_IDLE);
pool->nr_idle--;
@@ -192,7 +192,7 @@ index 4bb9113bd1f9..beee8ad4b9ea 100644
}
static struct worker *alloc_worker(int node)
-@@ -1831,7 +1863,9 @@ static void destroy_worker(struct worker *worker)
+@@ -1832,7 +1864,9 @@ static void destroy_worker(struct worker *worker)
pool->nr_workers--;
pool->nr_idle--;
@@ -202,3 +202,6 @@ index 4bb9113bd1f9..beee8ad4b9ea 100644
worker->flags |= WORKER_DIE;
wake_up_process(worker->task);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0330-Add-localversion-for-RT-release.patch b/debian/patches/features/all/rt/0330-Add-localversion-for-RT-release.patch
index 8510a47..4985f59 100644
--- a/debian/patches/features/all/rt/0330-Add-localversion-for-RT-release.patch
+++ b/debian/patches/features/all/rt/0330-Add-localversion-for-RT-release.patch
@@ -1,7 +1,7 @@
From: Thomas Gleixner <tglx at linutronix.de>
Date: Fri, 8 Jul 2011 20:25:16 +0200
Subject: [PATCH 330/351] Add localversion for -RT release
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=711d4a1e6e0c43fb0ff7d87eb74e425d3360331c
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=05151ea768875473f673a7763fae6e940deddea7
Signed-off-by: Thomas Gleixner <tglx at linutronix.de>
---
@@ -16,3 +16,6 @@ index 000000000000..9a218ca23053
+++ b/localversion-rt
@@ -0,0 +1 @@
+-rt23
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0331-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch b/debian/patches/features/all/rt/0331-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch
index e4965e8..8fae882 100644
--- a/debian/patches/features/all/rt/0331-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch
+++ b/debian/patches/features/all/rt/0331-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <efault at gmx.de>
Date: Wed, 23 Aug 2017 11:57:29 +0200
Subject: [PATCH 331/351] drivers/zram: fix zcomp_stream_get()
smp_processor_id() use in preemptible code
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6b1993403f14d13ada9ed46a903e4b22fbdc79c8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3546a4f36b53972abef0a5ead7d521188146ca12
Use get_local_ptr() instead this_cpu_ptr() to avoid a warning regarding
smp_processor_id() in preemptible code.
@@ -39,3 +39,6 @@ index fa8329ad79fd..8c93ee150ee8 100644
}
int zcomp_compress(struct zcomp_strm *zstrm,
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0332-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch b/debian/patches/features/all/rt/0332-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch
index 3838322..9a6f014 100644
--- a/debian/patches/features/all/rt/0332-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch
+++ b/debian/patches/features/all/rt/0332-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 20 Oct 2017 11:29:53 +0200
Subject: [PATCH 332/351] fs/dcache: disable preemption on i_dir_seq's write
side
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=24f0a4011408dc71877405d8963009b53bbb212f
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c4ca4a1117ebbd37d952fa2b315bc37f7fe0d568
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
@@ -60,7 +60,7 @@ index 37948da28742..f0719b2f1be5 100644
r_seq = read_seqbegin(&rename_lock);
dentry = __d_lookup_rcu(parent, name, &d_seq);
if (unlikely(dentry)) {
-@@ -2477,7 +2479,7 @@ struct dentry *d_alloc_parallel(struct dentry *parent,
+@@ -2477,7 +2479,7 @@ retry:
goto retry;
}
hlist_bl_lock(b);
@@ -95,7 +95,7 @@ index 9588780ad43e..9b37abd354c9 100644
struct dentry *res;
struct list_head *p;
bool skipped;
-@@ -122,8 +122,9 @@ static struct dentry *next_positive(struct dentry *parent,
+@@ -122,8 +122,9 @@ retry:
static void move_cursor(struct dentry *cursor, struct list_head *after)
{
struct dentry *parent = cursor->d_parent;
@@ -127,3 +127,6 @@ index d705ae084edd..ab1946f4a729 100644
};
__u32 i_generation;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0333-tpm_tis-fix-stall-after-iowrite-s.patch b/debian/patches/features/all/rt/0333-tpm_tis-fix-stall-after-iowrite-s.patch
index a6848cc..772758e 100644
--- a/debian/patches/features/all/rt/0333-tpm_tis-fix-stall-after-iowrite-s.patch
+++ b/debian/patches/features/all/rt/0333-tpm_tis-fix-stall-after-iowrite-s.patch
@@ -1,7 +1,7 @@
From: Haris Okanovic <haris.okanovic at ni.com>
Date: Tue, 15 Aug 2017 15:13:08 -0500
Subject: [PATCH 333/351] tpm_tis: fix stall after iowrite*()s
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=d2d77febce57f03e360002a856fe0dc79d68de8b
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ace69013f4b272bb71131c1dc3b08e7b6b1d456a
ioread8() operations to TPM MMIO addresses can stall the cpu when
immediately following a sequence of iowrite*()'s to the same region.
@@ -79,3 +79,6 @@ index 8022bea27fed..247330efd310 100644
return 0;
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0334-fs-convert-two-more-BH_Uptodate_Lock-related-bitspin.patch b/debian/patches/features/all/rt/0334-fs-convert-two-more-BH_Uptodate_Lock-related-bitspin.patch
index 2634c1c..23d7c58 100644
--- a/debian/patches/features/all/rt/0334-fs-convert-two-more-BH_Uptodate_Lock-related-bitspin.patch
+++ b/debian/patches/features/all/rt/0334-fs-convert-two-more-BH_Uptodate_Lock-related-bitspin.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 6 Nov 2017 18:45:30 +0100
Subject: [PATCH 334/351] fs: convert two more BH_Uptodate_Lock related
bitspinlocks
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ac709fc6486bc43e186c1ed4d3a110107df67be8
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1b6799bde24449b33a8c300f73c7cc69cb60e2f4
We convert all BH_Uptodate_Lock based bit-spinlocks to use
bh_uptodate_lock_irqsave() instead. Those two were introduced after the
@@ -64,3 +64,6 @@ index d31cd1ebd8e9..5ea3f933a52a 100644
if (!busy)
end_page_writeback(bvec->bv_page);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0335-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch b/debian/patches/features/all/rt/0335-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch
index 15d5fa5..84048f5 100644
--- a/debian/patches/features/all/rt/0335-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch
+++ b/debian/patches/features/all/rt/0335-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch
@@ -2,7 +2,7 @@ From: Mikulas Patocka <mpatocka at redhat.com>
Date: Mon, 13 Nov 2017 12:56:53 -0500
Subject: [PATCH 335/351] locking/rt-mutex: fix deadlock in device mapper /
block-IO
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=41515a02fd26d60a8b7297a5b86f06e406b97029
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=2cb85395c899be113d17a205057372fb0c2246ae
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
@@ -76,3 +76,6 @@ index 78a6c4a223c1..b73cd7c87551 100644
return slowfn(lock, state, timeout, chwalk, ww_ctx);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0336-md-raid5-do-not-disable-interrupts.patch b/debian/patches/features/all/rt/0336-md-raid5-do-not-disable-interrupts.patch
index 0769eec..6bddf10 100644
--- a/debian/patches/features/all/rt/0336-md-raid5-do-not-disable-interrupts.patch
+++ b/debian/patches/features/all/rt/0336-md-raid5-do-not-disable-interrupts.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 17 Nov 2017 16:21:00 +0100
Subject: [PATCH 336/351] md/raid5: do not disable interrupts
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=141b9c572138632b2912374ea22592de87578491
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f5dcddfeaf286d0e114585418ad2ff260c4fb688
|BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:974
|in_atomic(): 0, irqs_disabled(): 1, pid: 2992, name: lvm
@@ -35,7 +35,7 @@ Signed-off-by: Steven Rostedt (VMware) <rostedt at goodmis.org>
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
-index 4d8cfce1de86..4dde911925dc 100644
+index 710bb5d009a8..8d2c9d70042e 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -429,7 +429,7 @@ void raid5_release_stripe(struct stripe_head *sh)
@@ -47,7 +47,7 @@ index 4d8cfce1de86..4dde911925dc 100644
/* we are ok here if STRIPE_ON_RELEASE_LIST is set or not */
if (atomic_dec_and_lock(&sh->count, &conf->device_lock)) {
INIT_LIST_HEAD(&list);
-@@ -438,7 +438,7 @@ void raid5_release_stripe(struct stripe_head *sh)
+@@ -438,7 +438,7 @@ slow_path:
spin_unlock(&conf->device_lock);
release_inactive_stripe_list(conf, &list, hash);
}
@@ -56,3 +56,6 @@ index 4d8cfce1de86..4dde911925dc 100644
}
static inline void remove_hash(struct stripe_head *sh)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0337-Revert-memcontrol-Prevent-scheduling-while-atomic-in.patch b/debian/patches/features/all/rt/0337-Revert-memcontrol-Prevent-scheduling-while-atomic-in.patch
index 51b6a20..d8119a8 100644
--- a/debian/patches/features/all/rt/0337-Revert-memcontrol-Prevent-scheduling-while-atomic-in.patch
+++ b/debian/patches/features/all/rt/0337-Revert-memcontrol-Prevent-scheduling-while-atomic-in.patch
@@ -2,7 +2,7 @@ From: "Steven Rostedt (VMware)" <rostedt at goodmis.org>
Date: Wed, 22 Nov 2017 07:31:19 -0500
Subject: [PATCH 337/351] Revert "memcontrol: Prevent scheduling while atomic
in cgroup code"
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=73151b7028efd3386509eb3bd89a0403125600d9
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=79d0aa9d9c466e78c3c607afc40802d68dea9003
The commit "memcontrol: Prevent scheduling while atomic in cgroup code"
fixed this issue:
@@ -101,3 +101,6 @@ index 12b94909ba7b..c04403033aec 100644
}
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0338-Revert-fs-jbd2-pull-your-plug-when-waiting-for-space.patch b/debian/patches/features/all/rt/0338-Revert-fs-jbd2-pull-your-plug-when-waiting-for-space.patch
index 9421756..b0825a5 100644
--- a/debian/patches/features/all/rt/0338-Revert-fs-jbd2-pull-your-plug-when-waiting-for-space.patch
+++ b/debian/patches/features/all/rt/0338-Revert-fs-jbd2-pull-your-plug-when-waiting-for-space.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 23 Nov 2017 17:51:51 +0100
Subject: [PATCH 338/351] Revert "fs: jbd2: pull your plug when waiting for
space"
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=ad24d535a852a1b83f587910dab3190d243bc302
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=84efce6b9d2163c49080f24ed3f9a90d5822cb18
This reverts commit "fs: jbd2: pull your plug when waiting for space".
This was a duct-tape fix which shouldn't be needed since commit
@@ -28,3 +28,6 @@ index 6e18a06aaabe..684996c8a3a4 100644
mutex_lock(&journal->j_checkpoint_mutex);
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0339-rtmutex-Fix-lock-stealing-logic.patch b/debian/patches/features/all/rt/0339-rtmutex-Fix-lock-stealing-logic.patch
index 5794bac..6380f07 100644
--- a/debian/patches/features/all/rt/0339-rtmutex-Fix-lock-stealing-logic.patch
+++ b/debian/patches/features/all/rt/0339-rtmutex-Fix-lock-stealing-logic.patch
@@ -1,7 +1,7 @@
From: Mike Galbraith <efault at gmx.de>
Date: Fri, 23 Jun 2017 09:37:14 +0200
Subject: [PATCH 339/351] rtmutex: Fix lock stealing logic
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=12662cc688be0b0b946d35c7a938a8c58ef27164
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=39d455a996ec0570ebf925921b7bafed1701e293
1. When trying to acquire an rtmutex, we first try to grab it without
queueing the waiter, and explicitly check for that initial attempt
@@ -160,3 +160,6 @@ index b73cd7c87551..5dbf6789383b 100644
return 0;
/*
* The current top waiter stays enqueued. We
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0340-cpu_pm-replace-raw_notifier-to-atomic_notifier.patch b/debian/patches/features/all/rt/0340-cpu_pm-replace-raw_notifier-to-atomic_notifier.patch
index c6ef89f..e266484 100644
--- a/debian/patches/features/all/rt/0340-cpu_pm-replace-raw_notifier-to-atomic_notifier.patch
+++ b/debian/patches/features/all/rt/0340-cpu_pm-replace-raw_notifier-to-atomic_notifier.patch
@@ -1,7 +1,7 @@
From: Alex Shi <alex.shi at linaro.org>
Date: Thu, 6 Jul 2017 16:47:46 +0800
Subject: [PATCH 340/351] cpu_pm: replace raw_notifier to atomic_notifier
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=740d4bdfc19b445ebb43c20e0f0f8b56b5639bd1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=e5356b2b7929191763b14ad89241c8e355330187
This patch replace a rwlock and raw notifier by atomic notifier which
protected by spin_lock and rcu.
@@ -173,3 +173,6 @@ index 009cc9a17d95..10f4640f991e 100644
}
EXPORT_SYMBOL_GPL(cpu_cluster_pm_exit);
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0341-PM-CPU-replace-raw_notifier-with-atomic_notifier-fix.patch b/debian/patches/features/all/rt/0341-PM-CPU-replace-raw_notifier-with-atomic_notifier-fix.patch
index ef60a01..fc558c7 100644
--- a/debian/patches/features/all/rt/0341-PM-CPU-replace-raw_notifier-with-atomic_notifier-fix.patch
+++ b/debian/patches/features/all/rt/0341-PM-CPU-replace-raw_notifier-with-atomic_notifier-fix.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 17 Aug 2017 11:38:51 +0200
Subject: [PATCH 341/351] PM / CPU: replace raw_notifier with atomic_notifier
(fixup)
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=68fb318c153c57bd80c317505c2c2e2edf9a8e6a
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=af89f1069b81ad789d3fd7eb857b384895bfe802
The original patch changed betwen its posting and what finally went into
Rafael's tree so here is the delta.
@@ -32,3 +32,6 @@ index 10f4640f991e..67b02e138a47 100644
return notifier_to_errno(ret);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0342-kernel-hrtimer-migrate-deferred-timer-on-CPU-down.patch b/debian/patches/features/all/rt/0342-kernel-hrtimer-migrate-deferred-timer-on-CPU-down.patch
index 464927c..15adcf5 100644
--- a/debian/patches/features/all/rt/0342-kernel-hrtimer-migrate-deferred-timer-on-CPU-down.patch
+++ b/debian/patches/features/all/rt/0342-kernel-hrtimer-migrate-deferred-timer-on-CPU-down.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Fri, 18 Aug 2017 10:09:09 +0200
Subject: [PATCH 342/351] kernel/hrtimer: migrate deferred timer on CPU down
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=eaeac8064f7f2f7ff47daa59818393fd628897ad
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c68b48ed0f09f3f51b5a2f30663c02aa38b43717
hrtimers, which were deferred to the softirq context, and expire between
softirq shutdown and hrtimer migration are dangling around. If the CPU
@@ -33,3 +33,6 @@ index 0797bd6eadb4..39e4435b8451 100644
}
int hrtimers_dead_cpu(unsigned int scpu)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0343-net-take-the-tcp_sk_lock-lock-with-BH-disabled.patch b/debian/patches/features/all/rt/0343-net-take-the-tcp_sk_lock-lock-with-BH-disabled.patch
index eb8a083..5621e7a 100644
--- a/debian/patches/features/all/rt/0343-net-take-the-tcp_sk_lock-lock-with-BH-disabled.patch
+++ b/debian/patches/features/all/rt/0343-net-take-the-tcp_sk_lock-lock-with-BH-disabled.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Mon, 21 Aug 2017 15:09:13 +0200
Subject: [PATCH 343/351] net: take the tcp_sk_lock lock with BH disabled
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=46dbe03ccfbabdcebca5110f09d79732c4afbafe
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=3631d9dc11775725bf7ddd9709bef2a4632e6649
Lockdep may complain about an unsafe locking scenario:
| CPU0 CPU1
@@ -26,7 +26,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
-index 3336e1534bc5..3b7298459c87 100644
+index 67ca3fe56ac1..17699390a324 100644
--- a/net/ipv4/tcp_ipv4.c
+++ b/net/ipv4/tcp_ipv4.c
@@ -698,8 +698,8 @@ static void tcp_v4_send_reset(const struct sock *sk, struct sk_buff *skb)
@@ -68,3 +68,6 @@ index 3336e1534bc5..3b7298459c87 100644
}
static void tcp_v4_timewait_ack(struct sock *sk, struct sk_buff *skb)
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0344-kernel-hrtimer-don-t-wakeup-a-process-while-holding-.patch b/debian/patches/features/all/rt/0344-kernel-hrtimer-don-t-wakeup-a-process-while-holding-.patch
index 8c4d1cc..fbf2f43 100644
--- a/debian/patches/features/all/rt/0344-kernel-hrtimer-don-t-wakeup-a-process-while-holding-.patch
+++ b/debian/patches/features/all/rt/0344-kernel-hrtimer-don-t-wakeup-a-process-while-holding-.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 31 Aug 2017 18:19:06 +0200
Subject: [PATCH 344/351] kernel/hrtimer: don't wakeup a process while holding
the hrtimer base lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=7e5f72d0e04e6fe5d62b487a1af2c8cd624ab4c1
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=05d872fd76420ff4cbb3766a660a21503b6410cd
We must not wake any process (and thus acquire the pi->lock) while
holding the hrtimer's base lock. This does not happen usually because
@@ -48,7 +48,7 @@ index 39e4435b8451..8a20ef6919d9 100644
BUG_ON(!cpu_base->hres_active);
cpu_base->nr_events++;
-@@ -1523,7 +1523,7 @@ void hrtimer_interrupt(struct clock_event_device *dev)
+@@ -1523,7 +1523,7 @@ retry:
*/
cpu_base->expires_next.tv64 = KTIME_MAX;
@@ -57,7 +57,7 @@ index 39e4435b8451..8a20ef6919d9 100644
/* Reevaluate the clock bases for the next expiry */
expires_next = __hrtimer_get_next_event(cpu_base);
-@@ -1534,6 +1534,8 @@ void hrtimer_interrupt(struct clock_event_device *dev)
+@@ -1534,6 +1534,8 @@ retry:
cpu_base->expires_next = expires_next;
cpu_base->in_hrtirq = 0;
raw_spin_unlock(&cpu_base->lock);
@@ -86,3 +86,6 @@ index 39e4435b8451..8a20ef6919d9 100644
}
/*
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0345-kernel-hrtimer-hotplug-don-t-wake-ktimersoftd-while-.patch b/debian/patches/features/all/rt/0345-kernel-hrtimer-hotplug-don-t-wake-ktimersoftd-while-.patch
index b589ea5..85388fc 100644
--- a/debian/patches/features/all/rt/0345-kernel-hrtimer-hotplug-don-t-wake-ktimersoftd-while-.patch
+++ b/debian/patches/features/all/rt/0345-kernel-hrtimer-hotplug-don-t-wake-ktimersoftd-while-.patch
@@ -2,7 +2,7 @@ From: Mike Galbraith <efault at gmx.de>
Date: Sun, 3 Sep 2017 04:48:10 +0200
Subject: [PATCH 345/351] kernel/hrtimer/hotplug: don't wake ktimersoftd while
holding the hrtimer base lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c3b9b9115bc663cb42da1aa73174c2bcd49ba6fe
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=59663020ab5afba6078313eaef85454b4e7a3c8b
kernel/hrtimer: don't wakeup a process while holding the hrtimer base lock
missed a path, namely hrtimers_dead_cpu() -> migrate_hrtimer_list(). Defer
@@ -69,3 +69,6 @@ index 8a20ef6919d9..369203af6406 100644
/* Check, if we got expired work to do */
__hrtimer_peek_ahead_timers();
local_irq_enable();
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0346-Bluetooth-avoid-recursive-locking-in-hci_send_to_cha.patch b/debian/patches/features/all/rt/0346-Bluetooth-avoid-recursive-locking-in-hci_send_to_cha.patch
index fe949af..d773717 100644
--- a/debian/patches/features/all/rt/0346-Bluetooth-avoid-recursive-locking-in-hci_send_to_cha.patch
+++ b/debian/patches/features/all/rt/0346-Bluetooth-avoid-recursive-locking-in-hci_send_to_cha.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 21 Sep 2017 15:35:57 +0200
Subject: [PATCH 346/351] Bluetooth: avoid recursive locking in
hci_send_to_channel()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=394ea479da613334f923cf77689dc2c8798bfd15
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=b6be9c0bac29876e8b74e06caff20ab6144e6e49
Mart reported a deadlock in -RT in the call path:
hci_send_monitor_ctrl_event() -> hci_send_to_channel()
@@ -71,3 +71,6 @@ index c88a6007e643..5de85b55a821 100644
kfree_skb(skb);
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0347-iommu-amd-Use-raw_cpu_ptr-instead-of-get_cpu_ptr-for.patch b/debian/patches/features/all/rt/0347-iommu-amd-Use-raw_cpu_ptr-instead-of-get_cpu_ptr-for.patch
index d15b4dd..b118990 100644
--- a/debian/patches/features/all/rt/0347-iommu-amd-Use-raw_cpu_ptr-instead-of-get_cpu_ptr-for.patch
+++ b/debian/patches/features/all/rt/0347-iommu-amd-Use-raw_cpu_ptr-instead-of-get_cpu_ptr-for.patch
@@ -2,7 +2,7 @@ From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Tue, 5 Sep 2017 14:11:41 +0200
Subject: [PATCH 347/351] iommu/amd: Use raw_cpu_ptr() instead of get_cpu_ptr()
for ->flush_queue
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=5c78c5029a560bf213fd9a79c3753d8ca942007e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=cafc98963ab110ba8d353503ffd6d1891230ab5b
get_cpu_ptr() disabled preemption and returns the ->flush_queue object
of the current CPU. raw_cpu_ptr() does the same except that it not
@@ -23,7 +23,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
-index a88595b21111..ff5c2424eb9e 100644
+index 75ee9538f169..3408e5dd1b93 100644
--- a/drivers/iommu/amd_iommu.c
+++ b/drivers/iommu/amd_iommu.c
@@ -2283,7 +2283,7 @@ static void queue_add(struct dma_ops_domain *dma_dom,
@@ -44,3 +44,6 @@ index a88595b21111..ff5c2424eb9e 100644
}
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0348-rt-locking-allow-recursive-local_trylock.patch b/debian/patches/features/all/rt/0348-rt-locking-allow-recursive-local_trylock.patch
index 477f452..19ab97f 100644
--- a/debian/patches/features/all/rt/0348-rt-locking-allow-recursive-local_trylock.patch
+++ b/debian/patches/features/all/rt/0348-rt-locking-allow-recursive-local_trylock.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 21 Sep 2017 14:39:56 +0200
Subject: [PATCH 348/351] rt/locking: allow recursive local_trylock()
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=c8232f40d938e7a1d8c202da9d1c32ae0c7b3799
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=f84b0b29610e85618e3af944cadc7aef9ddb5348
required for following networking patch which does recursive try-lock.
While at it, add the !RT version of it because it did not yet exist.
@@ -39,3 +39,6 @@ index 845c77f1a5ca..280f884a05a3 100644
#define local_lock(lvar) preempt_disable()
#define local_unlock(lvar) preempt_enable()
#define local_lock_irq(lvar) local_irq_disable()
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0349-locking-rtmutex-don-t-drop-the-wait_lock-twice.patch b/debian/patches/features/all/rt/0349-locking-rtmutex-don-t-drop-the-wait_lock-twice.patch
index 7750669..7cf1c79 100644
--- a/debian/patches/features/all/rt/0349-locking-rtmutex-don-t-drop-the-wait_lock-twice.patch
+++ b/debian/patches/features/all/rt/0349-locking-rtmutex-don-t-drop-the-wait_lock-twice.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 7 Sep 2017 12:38:47 +0200
Subject: [PATCH 349/351] locking/rtmutex: don't drop the wait_lock twice
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=a17b3d864d451e221b388dce10e18f2d836e6e26
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=29f14304b47fde8760b419886ca1ff8faf6d8ace
Since the futex rework, __rt_mutex_start_proxy_lock() does no longer
acquire the wait_lock so it must not drop it. Otherwise the lock is not
@@ -30,3 +30,6 @@ index 5dbf6789383b..3a8b5d44aaf8 100644
return -EAGAIN;
}
task->pi_blocked_on = PI_REQUEUE_INPROGRESS;
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0350-net-use-trylock-in-icmp_sk.patch b/debian/patches/features/all/rt/0350-net-use-trylock-in-icmp_sk.patch
index e56668e..45ae6de 100644
--- a/debian/patches/features/all/rt/0350-net-use-trylock-in-icmp_sk.patch
+++ b/debian/patches/features/all/rt/0350-net-use-trylock-in-icmp_sk.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
Date: Thu, 21 Sep 2017 14:42:04 +0200
Subject: [PATCH 350/351] net: use trylock in icmp_sk
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=bb87744dd4e5973af951f4cadc9b06883c8f8a0e
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=13d326161ba07de9deb8bcffbfe8f53929f0b53a
The locking path can be recursive (same as for sk->sk_lock.slock) and
therefore we need a trylock version for the locallock, too.
@@ -14,7 +14,7 @@ Signed-off-by: Steven Rostedt (VMware) <rostedt at goodmis.org>
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/net/ipv4/icmp.c b/net/ipv4/icmp.c
-index e6864ff11352..330224ef4174 100644
+index 9a5f3fef53bb..c9525356823c 100644
--- a/net/ipv4/icmp.c
+++ b/net/ipv4/icmp.c
@@ -219,7 +219,11 @@ static inline struct sock *icmp_xmit_lock(struct net *net)
@@ -30,3 +30,6 @@ index e6864ff11352..330224ef4174 100644
sk = icmp_sk(net);
if (unlikely(!spin_trylock(&sk->sk_lock.slock))) {
+--
+2.16.1
+
diff --git a/debian/patches/features/all/rt/0351-Linux-4.9.68-rt60-REBASE.patch b/debian/patches/features/all/rt/0351-Linux-4.9.68-rt60-REBASE.patch
deleted file mode 100644
index 6bdb673..0000000
--- a/debian/patches/features/all/rt/0351-Linux-4.9.68-rt60-REBASE.patch
+++ /dev/null
@@ -1,16 +0,0 @@
-From: "Steven Rostedt (VMware)" <rostedt at goodmis.org>
-Date: Thu, 30 Nov 2017 19:12:26 -0500
-Subject: [PATCH 351/351] Linux 4.9.68-rt60 REBASE
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=1ae113e318f6532b9d16c6e2f5417f37ce5fc6fb
-
----
- localversion-rt | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/localversion-rt b/localversion-rt
-index 9a218ca23053..66fa05e70f29 100644
---- a/localversion-rt
-+++ b/localversion-rt
-@@ -1 +1 @@
---rt23
-+-rt60
diff --git a/debian/patches/features/all/rt/0351-Linux-4.9.76-rt61-REBASE.patch b/debian/patches/features/all/rt/0351-Linux-4.9.76-rt61-REBASE.patch
new file mode 100644
index 0000000..a43079d
--- /dev/null
+++ b/debian/patches/features/all/rt/0351-Linux-4.9.76-rt61-REBASE.patch
@@ -0,0 +1,19 @@
+From: Julia Cartwright <julia at ni.com>
+Date: Mon, 15 Jan 2018 13:10:48 -0600
+Subject: [PATCH 351/351] Linux 4.9.76-rt61 REBASE
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=6f503aeecec8e5041a4dc1e17ad483b449855814
+
+---
+ localversion-rt | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/localversion-rt b/localversion-rt
+index 9a218ca23053..9b7de9345ef4 100644
+--- a/localversion-rt
++++ b/localversion-rt
+@@ -1 +1 @@
+--rt23
++-rt61
+--
+2.16.1
+
diff --git a/debian/patches/series-rt b/debian/patches/series-rt
index 145db90..b09f335 100644
--- a/debian/patches/series-rt
+++ b/debian/patches/series-rt
@@ -348,4 +348,4 @@ features/all/rt/0347-iommu-amd-Use-raw_cpu_ptr-instead-of-get_cpu_ptr-for.patch
features/all/rt/0348-rt-locking-allow-recursive-local_trylock.patch
features/all/rt/0349-locking-rtmutex-don-t-drop-the-wait_lock-twice.patch
features/all/rt/0350-net-use-trylock-in-icmp_sk.patch
-features/all/rt/0351-Linux-4.9.68-rt60-REBASE.patch
+features/all/rt/0351-Linux-4.9.76-rt61-REBASE.patch
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/kernel/linux.git
More information about the Kernel-svn-changes
mailing list