From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: stable-rt@vger.kernel.org
Subject: Re: Stable backports
Date: Thu, 27 Jul 2023 12:50:40 +0200 [thread overview]
Message-ID: <20230727105040.4V9DQ5pM@linutronix.de> (raw)
In-Reply-To: <20230620150329.6r4xxvHu@linutronix.de>
On 2023-06-20 17:03:29 [+0200], To stable-rt@vger.kernel.org wrote:
Hi,
> I've been looking over my queue and which patches vanishes (as in
> applied somewhere) and did not show up in the stable tree. Here is a
> list of some suggestions:
>
> - 7eb16f23b9a41 ("io-mapping: don't disable preempt on RT in io_mapping_map_atomic_wc().")
> - 286deb7ec03d9 ("locking/rwbase: Mitigate indefinite writer starvation")
> - 1c0908d8e4416 ("rtmutex: Add acquire semantics for rtmutex lock acquisition slow path")
> (is in v6.1 but not in v5.15)
> - b8a04a538ed47 ("revert: "softirq: Let ksoftirqd do its job"")
> - 38cdd83a47fb2 ("tracing/timer: Add missing hrtimer modes to decode_hrtimer_mode().")
No idea how far backporting got, I would like to extend the list:
- 40cd2835ced28 ("drm/i915: Do not disable preemption for resets")
- 7edeaf858cef4 ("locking/rtmutex: Fix task->pi_waiters integrity")
Could be routed via stable
- 053ba1b91e511 ("kernel/fork: beware of __put_task_struct calling context")
The following two are just for lockdep:
- 0cce06ba859a5 ("debugobjects,locking: Annotate debug_object_fill_pool() wait type violation")
- a5e446e728e89 ("sched: avoid false lockdep splat in put_task_struct()")
The following three are for mm backport from stable which broke RT and
was noticed during Luis' stable backport. This should be backported so
it is fixed and aligned with upstream:
- a3f6be6e53532 ("printk: Check only for migration in printk_deferred_*().")
- dc93c1f07d485 ("seqlock: Do the lockdep annotation before locking in do_write_seqcount_begin_nested()")
- 4d1139baae8bc ("mm/page_alloc: Use write_seqlock_irqsave() instead write_seqlock() + local_irq_save().")
And finally. Both upstream not sure if they get in via -stable, but I
doubt since they are RT-only and not tagged:
- ab5d47bd41b1d ("bpf: Remove in_atomic() from bpf_link_put().")
- 9d9e522010eb5 ("posix-timers: Prevent RT livelock in itimer_delete()")
- 8ce8849dd1e78 ("posix-timers: Ensure timer ID search-loop limit is valid")
Sebastian
prev parent reply other threads:[~2023-07-27 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 15:03 Stable backports Sebastian Andrzej Siewior
2023-06-27 19:14 ` Joseph Salisbury
2023-06-28 6:56 ` Sebastian Andrzej Siewior
2023-06-28 8:08 ` Steven Rostedt
2023-06-28 14:28 ` Joseph Salisbury
2023-07-27 10:50 ` Sebastian Andrzej Siewior [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230727105040.4V9DQ5pM@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=stable-rt@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).