From: Pavel Machek <pavel@denx.de>
To: Ulrich Hecht <uli@fpond.eu>
Cc: "pavel@denx.de" <pavel@denx.de>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: Request for reviews for 4.4-st38/4.4-cip73
Date: Thu, 9 Mar 2023 22:35:08 +0100 [thread overview]
Message-ID: <ZApRDHkYvu2bOgZM@duo.ucw.cz> (raw)
In-Reply-To: <1010789948.2703824.1677492030810@webmail.strato.com>
[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]
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 :
>
I managed to review most of them.
These are ok:
a > ff1d923b1cbd mm/swapfile: add cond_resched() in get_swap_pages()
a > c2242a203f81 fbcon: Check font dimension limits
a > 0697f3908a1c ipv6: ensure sane device mtu in tunnels
a > 6e1a18831ef9 net: ravb: Fix possible hang if RIS2_QFF1 happen
a not a minimum fix> e15755dd0185 EDAC/device: Respect any driver-supplied workqueue polling value
a not really stable material > 1e5047422011 net: mlx5: eliminate anonymous module_init & module_exit
a not really stable material > 8f0e3e6f2ec8 amd-xgbe: TX Flow Ctrl Registers are h/w ver dependent
a cargo cult programming > 30a61de78f81 usb: gadget: f_ncm: fix potential NULL ptr deref in ncm_bitrate()
a not really worth the work > 70ccdf253245 usb: core: hub: disable autosuspend for TI TUSB8041
a > 9c336605666d USB: hub: Fix the broken detection of USB3 device in SMSC hub
a > 93215b524bdf hvc/xen: lock console list traversal
a > e22ac280fe43 qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure
a > f38b21843014 nilfs2: fix underflow in second superblock position calculations
a just an API tweak, do we have 1/ of the series? > 9a977a3c8fab mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps
a > f09f686242e2 SUNRPC: ensure the matching upcall is in-flight upon downcall
a > 97494d49b7e0 NFSv4.x: Fail client initialisation if state manager thread can't run
(comments there are really nothing you can do much, but I'd not bother
backporting 1e5047422011 and 8f0e3e6f2ec8).
I believe we should be taking this one. It is mostly theoretical bug,
backport is extensive and we really have no way of testing it:
! syscaller -> theoretical bug. This would really need testing. They
were deleting code from ack_complete. Lets... not? > 57059c01a09d nfc:
pn533: Wait for out_urb's completion in pn533_usb_send_frame()
I'd cite commit # being backported on the first one, and I'll need to
take second look at these:
! cite commit # of the patch being backported? > 7672af7c726f ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF
! NL_SET_ERR_MSG? > e6f2bae11168 net: sched: disallow noqueue for qdisc classes
>
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-03-09 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:00 Request for reviews for 4.4-st38/4.4-cip73 Ulrich Hecht
2023-03-09 21:35 ` Pavel Machek [this message]
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=ZApRDHkYvu2bOgZM@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--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;
as well as URLs for NNTP newsgroup(s).