From: Pavel Machek <pavel@denx.de>
To: Ulrich Hecht <uli@fpond.eu>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: Request for review for 4.4-st65, 4.4-cip100
Date: Tue, 17 Jun 2025 11:27:05 +0200 [thread overview]
Message-ID: <aFE06VzaBSMttFH9@duo.ucw.cz> (raw)
In-Reply-To: <1652754680.135113.1750092922654@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
Hi!
> Here's the manual backports for the upcoming 4.4 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.4.y-st-rc
>
One patch is not complete, the rest look ok to me.
a > 8dab9bb642b2e net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too
> 6f43c571bf094 of/irq: Fix device node refcount leakages in
> of_irq_init()
4.4 has one more place to handle, AFAICT:
if (WARN(!match->data,
"of_irq_init: no init function for %s\n",
match->compatible)) {
kfree(desc);
continue;
}
(Being behind WARN(), it is probably not too important).
a > 7f406a4c1fd70 mm: add missing release barrier on PGDAT_RECLAIM_LOCKED unlock
a > d24045205aaa7 media: streamzap: prevent processing IR data on URB failure
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
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:[~2025-06-17 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 16:55 Request for review for 4.4-st65, 4.4-cip100 Ulrich Hecht
2025-06-17 7:15 ` nobuhiro1.iwamatsu
2025-06-17 9:27 ` Pavel Machek [this message]
2025-06-17 10:20 ` Indirect Target Selection (CVE-2024-28956) " Pavel Machek
2025-06-17 15:05 ` [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=aFE06VzaBSMttFH9@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--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