From: Pavel Machek <pavel@nabladev.com>
To: Ulrich Hecht <uli@fpond.eu>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@nabladev.com" <pavel@nabladev.com>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Re: Request for review for 4.19-st20, 4.19-cip136
Date: Wed, 9 Sep 2026 21:23:04 +0200 [thread overview]
Message-ID: <aqGyGN25fPID67KZ@duo.ucw.cz> (raw)
In-Reply-To: <588742173.259606.1788373971804@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
Hi!
> Here are the "manual" backports for the upcoming 4.19 kernel release. There's a total of 68; 40 by me, and 28 by LLM. (The latter are labeled with "Assisted-by: SLTR:qwen-3.8".)
>
> As always they can be found in https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-st-rc
>
The openvswitch patch is not easy to review, rest looks okay.
Thanks and best regards,
Pavel
a > e370b6e8d1a59 vhost: reset the vring metadata cache on vring reconfiguration
a this makes me a bit nervous > 7d8fc6d0208be futex: Prevent robust futex exit race some more
a > 3d3bcb5dd85d1 Input: evdev - fix information leak in evdev_pass_values()
a > a3e7176697ddd mm/huge_memory: unlock i_mmap_rwsem before releasing after-split folios
a > 96c6f93b3ff66 sctp: prevent peer transport count overflow
a > 39cf294824a31 net: bridge: stop fast-leave after deleting a port group
a > f0b272d10c9df mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk()
a > caba2e7b56939 ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump
! changing meaning of variable while keeping name is pretty anti-social > 5298659ef682c openvswitch: fix GSO userspace truncation underflow
a just a API fix > 031a2f99d475b vxlan: require CAP_NET_ADMIN in the device netns for changelink
a > e7383f6dbb6b9 can: bcm: defer rx_op deallocation to workqueue to fix thrtimer UAF
a quite different from upstream fix > bd5b04d67545f tipc: fix u16 MTU truncation in media and bearer MTU validation
a > fd119cc5d1ce0 net/sched: act_tunnel_key: Defer dst_release to RCU callback
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-09-09 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 18:32 Request for review for 4.19-st20, 4.19-cip136 Ulrich Hecht
2026-09-03 9:00 ` Pavel Machek
2026-09-03 9:18 ` Ulrich Hecht
2026-09-03 11:59 ` Pavel Machek
2026-09-10 8:09 ` [cip-dev] " Ulrich Hecht
2026-09-07 11:04 ` Pavel Machek
2026-09-10 8:09 ` [cip-dev] " Ulrich Hecht
2026-09-09 19:23 ` Pavel Machek [this message]
2026-09-10 19:32 ` Pavel Machek
2026-09-11 10:15 ` [cip-dev] " Ulrich Hecht
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=aqGyGN25fPID67KZ@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=uli@fpond.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.