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-st44 4.4-cip79
Date: Mon, 4 Sep 2023 11:43:57 +0200 (CEST) [thread overview]
Message-ID: <1583308606.3395319.1693820637255@webmail.strato.com> (raw)
Hi!
Here are the manual backports for the upcoming 4.4-st44 and 4.4-cip79 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
My apologies, this is a big one. Thankfully, most backports are of the trivial sort:
** m-| 9559a3e60 f9c998 o | x86/smp: Use dedicated cache-line for mwait_play_dead()
** m-| f175f567b f8ef12 .+ | ARM: orion5x: fix d2net gpio initialization
** m-| 4ee69c91c 6eef7a o+ | netfilter: conntrack: Avoid nf_ct_helper_hash uses after free
** m-| f66069f9d 247c3d o | ext4: fix wrong unit use in ext4_mb_clear_bb
** m-| b3e17e6e6 a82d62 o+ | Revert "8250: add support for ASIX devices with a FIFO bug"
** m-| f35bd94b4 af73f2 o | scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport()
** m-| 005961bd8 00eca1 o | scsi: qla2xxx: Pointer may be dereferenced
** m-| 11b8e27ed 55c3b9 o+ | can: bcm: Fix UAF in bcm_proc_show()
** m-| 8dc52c200 8ce884 f | posix-timers: Ensure timer ID search-loop limit is valid
** m-| 4793f9802 1aeb87 o+ | tcp: annotate data-races around tp->notsent_lowat
** m-| a276d17dc c55afc . | usb: ohci-at91: Fix the unhandle interrupt when resume
** m-| d3009700f c2a88e o+ | drm/client: Fix memory leak in drm_client_target_cloned
** m-| f0f874147 3044b1 o+ | net/sched: cls_u32: No longer copy tcf_result on update to avoid use-after-free
** m-| 005f68d6b 949ad6 o+ | tcp_metrics: annotate data-races around tm->tcpm_stamp
** m-| 38f1f09dc 8c4d04 o+ | tcp_metrics: annotate data-races around tm->tcpm_vals[]
** m-| e28208e21 404615 o | ext2: Drop fragment support
** m-| 368684d3b 048c79 o | ipv6: adjust ndisc_is_useropt() to also return true for PIO
** m-| 8fad4df94 8a9896 o+ | net/packet: annotate data-races around tp->status
** m-| 4eb1fca13 d6a95d | quota: fix warning in dqgrab()
These might need a closer look:
** mo| 70cc55f6c 1cba6c o+ | kexec: fix a memory leak in crash_shrink_memory()
** mo| 6fb4b3443 504a10 o | gfs2: Don't deref jdesc in evict
** mo| 5df411bb8 8cda3e o+ | dmaengine: pl330: Return DMA_PAUSED when transaction is paused
There is also "x86/msr-index: remove duplicate definition of MSR_AMD64_DE_CFG", a minor fixup for a warning introduced in the previous release.
Thanks for having a look.
CU
Uli
next reply other threads:[~2023-09-04 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 9:43 Ulrich Hecht [this message]
2023-09-04 10:42 ` Request for reviews for 4.4-st44 4.4-cip79 Pavel Machek
2023-09-04 11:43 ` Pavel Machek
2023-09-06 8:32 ` [cip-dev] " Ulrich Hecht
2023-09-11 8:27 ` 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=1583308606.3395319.1693820637255@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