On Thu, 8 Feb 2024, Ulrich Hecht wrote:
On 02/05/2024 11:15 AM CET Michael Schmitz <schmitzmic@xxxxxxxxx>
wrote: On that note - Uli: would you prefer the entire backport
series, or only those you do not already have?
I'd prefer to only get what's missing.
Ulrich, I imagine that you would normally receive fixes via the
corresponding -stable trees. If Michael's series went into
stable/linux-4.19.y you could cherry-pick from there for your v4.4.y tree
and maybe avoid some merge conflicts that way. So perhaps we should ask
the -stable maintainers to backport first (?)
Al, I see that the following commits are missing from stable/linux-v6.1
and older trees, despite the word "fix" in the subject. Reading the merge
commit 1a8d05a726dc "Merge tag 'pull-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs" suggests to me
that these are old bugs...
bd75497a77cc m68k: fix livelock in uaccess
d835eb3a57de riscv: fix livelock in uaccess
0b92ed09cb9f hexagon: fix livelock in uaccess
15261678a8c2 parisc: fix livelock in uaccess
dce45493aff3 alpha: fix livelock in uaccess
79c54c97c773 sparc: fix livelock in uaccess
d088af1e221c ia64: fix livelock in uaccess
a1179ac743e8 microblaze: fix livelock in uaccess
e902e508c5b2 nios2: fix livelock in uaccess
caa82ae7ef52 openrisc: fix livelock in uaccess
In addition, stable/linux-v5.10 and the older trees lack the following
commit, despite the Fixes tag.
50e43a573344 m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal
