From: Ulrich Hecht <uli@fpond.eu>
To: "pavel@denx.de" <pavel@denx.de>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Request for reviews for 4.4-st39, 4.4-cip74, 4.4-cip74-rt43
Date: Thu, 30 Mar 2023 10:52:31 +0200 (CEST) [thread overview]
Message-ID: <1611211333.1066638.1680166351379@webmail.strato.com> (raw)
Hi!
Here are the manual backports for the upcoming 4.4-st39, 4.4-cip74 and 4.4-cip74-rt43 releases that should be reviewed, and that can currently be found in https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-st-rc
Trivial backports:
** m | d2d3052d9 6f8ecb o+ | gpio: vf610: connect GPIO label to dev name
** m | c075aa346 5d5aa2 o | ARM: dts: exynos: Use Exynos5420 compatible for the MIPI video phy
** m | 09fa241bc 4971c2 o+ | ima: Align ima_file_mmap() parameters with mmap_file LSM hook
** m | 38345d84e aa56b9 o | dm flakey: fix logic when corrupting a bio
** m | c214be981 709fca o | Bluetooth: hci_sock: purge socket queues in the destruct() callback
** m | 9acadaf26 a98fc2 | staging: rtl8192e: Remove function ..dm_check_ac_dc_power calling a script
** m | 1c4293ded fe413a | staging: rtl8192e: Remove call_usermodehelper starting RadioPower.sh
** m | 85f922f42 c22c3b o+ | net: phy: smsc: bail out in lan87xx_read_status if genphy_read_status fails
Not completely trivial backports, and/or stuff that touches important subsystems:
** m | 4e3b4b170 9a5571 o+ | f2fs: fix information leak in f2fs_move_inline_dirents()
** m | 5621f7a81 256fe4 o | udf: Do not update file length for failed writes to inline files
** m | 11790a4fa b06730 o+ | irqdomain: Fix association race
** m | 30b560087 3f883c o+ | irqdomain: Fix disassociation race
** m | b40d2fbf4 4d57a7 o+ | ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed
** m | 3df6f492f db4df8 o | tty: fix out-of-bounds access in tty_driver_lookup_tty()
** m | 438d62a68 c4c81d o | tty: serial: fsl_lpuart: disable the CTS when send break signal
I would also like an opinion or two on the importance of this patch:
** i | d5cf15857 e88b2c o+ | bpf: Fix 32 bit src register truncation on div/mod
I have chosen not to include it because it would require backporting quite a bit of infrastructure. According to the bug report at https://bugzilla.redhat.com/show_bug.cgi?id=1981954, the issue is not exploitable for out-of-bounds accesses on 4.4.
Thanks!
CU
Uli
next reply other threads:[~2023-03-30 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 8:52 Ulrich Hecht [this message]
2023-03-30 11:32 ` Request for reviews for 4.4-st39, 4.4-cip74, 4.4-cip74-rt43 Pavel Machek
2023-03-30 11:43 ` Ulrich Hecht
2023-03-31 15:55 ` Alexander Grund
2023-04-03 8:56 ` [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=1611211333.1066638.1680166351379@webmail.strato.com \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=pavel@denx.de \
/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