Request for review for 4.19-st8, 4.19-cip124

Request for review for 4.19-st8, 4.19-cip124

[Ulrich Hecht]

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
(At least that's what I assume; I'm no longer able to get past the bot protection...)

c50175dd232f1 f2fs: fix to do sanity check on ino and xnid
c5da7386ca038 squashfs: fix memory leak in squashfs_fill_super
8004a014004f3 pNFS: Handle RPC size limit for layoutcommits
73d1fa319709c wifi: iwlwifi: fw: Fix possible memory leak in iwl_fw_dbg_collect
a2cab05b5667d usb: core: usb_submit_urb: downgrade type check
ddc44ffdaa7d8 udf: Verify partition map count
68def4bf2c714 f2fs: fix to avoid panic in f2fs_evict_inode
a2f0f298a3bc6 usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm
0f86291316a33 f2fs: fix to avoid out-of-boundary access in dnode page

Thanks for having a look!

CU
Uli

Re: Request for review for 4.19-st8, 4.19-cip124

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1500 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
> (At least that's what I assume; I'm no longer able to get past the bot protection...)

I have seen it randomly fail on me, too. Could LF tone it down?

Patches look ok to me, ddc44ffdaa7d8 should probably return
-EFSCORRUPTED but I doubt anyone cares.

Best regards,
								Pavel

a just a robustness against fs corruption > c50175dd232f1 f2fs: fix to do sanity check on ino and xnid
a > c5da7386ca038 squashfs: fix memory leak in squashfs_fill_super
a critical section could be shorter > 8004a014004f3 pNFS: Handle RPC size limit for layoutcommits
a > 73d1fa319709c wifi: iwlwifi: fw: Fix possible memory leak in iwl_fw_dbg_collect
a just a printk tweak > a2cab05b5667d usb: core: usb_submit_urb: downgrade type check
a just a robustness against fs corruption, -EFSCORRUPTED? > ddc44ffdaa7d8 udf: Verify partition map count
a just a robustness against fs corruption > 68def4bf2c714 f2fs: fix to avoid panic in f2fs_evict_inode
a > a2f0f298a3bc6 usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm
a just a robustness against fs corruption > 0f86291316a33 f2fs: fix to avoid out-of-boundary access in dnode page
> 


-- 
In cooperation with DENX Software Engineering GmbH, HRB 165235 Munich,
Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

RE: Request for review for 4.19-st8, 4.19-cip124

[nobuhiro.iwamatsu.x90]

Hello,

> -----Original Message-----
> From: Ulrich Hecht <uli@fpond.eu>
> Sent: Wednesday, September 17, 2025 12:04 AM
> To: cip-dev@lists.cip-project.org; pavel@denx.de; iwamatsu nobuhiro(岩松 信
> 洋 □ＤＩＴＣ○ＣＰＴ) <nobuhiro.iwamatsu.x90@mail.toshiba>
> Subject: Request for review for 4.19-st8, 4.19-cip124
> 
> 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=linu
> x-4.19.y-st-rc
> (At least that's what I assume; I'm no longer able to get past the bot
> protection...)
> 
> c50175dd232f1 f2fs: fix to do sanity check on ino and xnid
> c5da7386ca038 squashfs: fix memory leak in squashfs_fill_super
> 8004a014004f3 pNFS: Handle RPC size limit for layoutcommits 73d1fa319709c
> wifi: iwlwifi: fw: Fix possible memory leak in iwl_fw_dbg_collect
> a2cab05b5667d usb: core: usb_submit_urb: downgrade type check
> ddc44ffdaa7d8 udf: Verify partition map count
> 68def4bf2c714 f2fs: fix to avoid panic in f2fs_evict_inode
> a2f0f298a3bc6 usb: hub: Fix flushing and scheduling of delayed work that
> tunes runtime pm
> 0f86291316a33 f2fs: fix to avoid out-of-boundary access in dnode page
> 
> Thanks for having a look!
> 

I have reviewed patches and build, there are no issues.

Reviewed-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>

Best regards,
  Nobuhiro