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-st38/4.4-cip73
Date: Mon, 27 Feb 2023 11:00:30 +0100 (CET) [thread overview]
Message-ID: <1010789948.2703824.1677492030810@webmail.strato.com> (raw)
Hi!
Here are the manual backports for the upcoming 4.4-st38/4.4-cip73 release that should be reviewed, and 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 :
ff1d923b1cbd mm/swapfile: add cond_resched() in get_swap_pages()
c2242a203f81 fbcon: Check font dimension limits
0697f3908a1c ipv6: ensure sane device mtu in tunnels
6e1a18831ef9 net: ravb: Fix possible hang if RIS2_QFF1 happen
e15755dd0185 EDAC/device: Respect any driver-supplied workqueue polling value
1e5047422011 net: mlx5: eliminate anonymous module_init & module_exit
8f0e3e6f2ec8 amd-xgbe: TX Flow Ctrl Registers are h/w ver dependent
30a61de78f81 usb: gadget: f_ncm: fix potential NULL ptr deref in ncm_bitrate()
70ccdf253245 usb: core: hub: disable autosuspend for TI TUSB8041
9c336605666d USB: hub: Fix the broken detection of USB3 device in SMSC hub
57059c01a09d nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame()
93215b524bdf hvc/xen: lock console list traversal
7672af7c726f ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF
e6f2bae11168 net: sched: disallow noqueue for qdisc classes
e22ac280fe43 qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure
f38b21843014 nilfs2: fix underflow in second superblock position calculations
9a977a3c8fab mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps
f09f686242e2 SUNRPC: ensure the matching upcall is in-flight upon downcall
97494d49b7e0 NFSv4.x: Fail client initialisation if state manager thread can't run
That's more than I anticipated because a bunch of patches that seemed to apply cleanly had to be fixed up to actually make sense in 4.4. Nevertheless, most backports are minor adjustments to fit the 4.4 context.
The ones that need closer attention, IMO, are "ipv6: ensure sane device mtu in tunnels" and "nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame()". Additional notes can be found in https://gitlab.com/cip-project/cip-kernel/lts-commit-list/-/blob/master/v4.4.org . Thanks.
CU
Uli
next reply other threads:[~2023-02-27 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:00 Ulrich Hecht [this message]
2023-03-09 21:35 ` Request for reviews for 4.4-st38/4.4-cip73 Pavel Machek
2023-03-13 15:58 ` [cip-dev] " Ulrich Hecht
[not found] ` <174ADDD3EF16CBFE.27660@lists.cip-project.org>
2023-03-10 10:09 ` Pavel Machek
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=1010789948.2703824.1677492030810@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