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-st19, 4.19-cip135
Date: Fri, 31 Jul 2026 16:28:17 +0200 [thread overview]
Message-ID: <amyxAb4e3E7u7EzE@duo.ucw.cz> (raw)
In-Reply-To: <527172097.345263.1785165473174@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Hi!
>
> Here are the manual backports for the upcoming 4.19 kernel release. 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
a > 9f05da0b8dcfb Bluetooth: serialize accept_q access
I can see nothing wrong here, but ... this is quite complex and redoes
locking. I see quite a lot of bluetooth changes in stable, and we are
not really testing Bluetooth.
a > b106698c9084b netfilter: nf_queue: hold bridge skb->dev while queued
a > 50387c55b9106 mtd: spi-nor: sst: Fix write enable before AAI sequence
a > afa6edb63cc55 sched: Use u64 for bandwidth ratio calculations
> 43c19f228085a batman-adv: stop tp_meter sessions during mesh teardown
a > 1a36cfc71bae3 Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig
a > 8bc3105c22af8 net/sched: act_api: use RCU with deferred freeing for action lifecycle
a > 68d166edfbe56 thunderbolt: property: Reject u32 wrap in tb_property_entry_valid()
a > 44b20b4fce209 xfrm: esp: restore combined single-frag length gate
> 9118dc9ac0a49 batman-adv: tt: avoid empty VLAN responses
> e0f823e33114c batman-adv: tt: fix TOCTOU race for reported vlans
>
Best regards,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2026-07-31 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 15:17 Request for review for 4.19-st19, 4.19-cip135 Ulrich Hecht
2026-07-30 20:26 ` Pavel Machek
2026-07-31 14:28 ` Pavel Machek [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=amyxAb4e3E7u7EzE@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox