public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Ulrich Hecht <uli@fpond.eu>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"pavel@denx.de" <pavel@denx.de>,
	"nobuhiro1.iwamatsu@toshiba.co.jp"
	<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Request for reviews for 4.4-st58, 4.4-cip93
Date: Mon, 18 Nov 2024 08:00:50 +0100 (CET)	[thread overview]
Message-ID: <1048687374.465216.1731913250080@webmail.strato.de> (raw)

Hi!

Here's the manual backports to review for the next 4.4 release which, as always, 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

810047a5a2d59 xhci: Fix Link TRB DMA in command ring stopped completion event
514f5ac9c1666 selinux: improve error checking in sel_write_load()
a2b280ab0ae0b nilfs2: fix kernel bug due to missing clearing of buffer delay flag
3bcf6988dfd1a drm/amd: Guard against bad data for ATIF ACPI method
86191495e89b8 RDMA/cxgb4: Fix RDMA_CM_EVENT_UNREACHABLE error for iWARP
3ab089df2d674 nilfs2: propagate directory read errors from nilfs_find_entry()
f39491c638d21 CDC-NCM: avoid overflow in sanity checking
56c693c3da940 net: ipv6: ensure we call ipv6_mc_down() at most once
0544747431c07 tcp: fix tcp_enter_recovery() to zero retrans_stamp when it's safe
2d384ff2d55e3 SUNRPC: Fix integer overflow in decode_rc_list()
2e666ea559b34 rtc: at91sam9: fix OF node leak in probe() error path
bec0bfe9b401f ext4: update orig_path in ext4_find_extent()
e6bc59e0c89e7 ext4: fix slab-use-after-free in ext4_split_extent_at()
e01afdabeaffc ext4: avoid ext4_error()'s caused by ENOMEM in the truncate path
1ac1d775e3a60 aoe: fix the potential use-after-free problem in more places
f164fee72b643 ocfs2: reserve space for inline xattr before attaching reflink tree
bfe7a9a5b48c4 ext4: fix i_data_sem unlock order in ext4_ind_migrate()
49dd4925f15ef ACPI: EC: Do not release locks during operation region accesses
19e2758d6c70e sctp: set sk_state back to CLOSED if autobind fails in sctp_listen_start
43c8bfae4c2a5 fs: Fix file_set_fowner LSM hook inconsistencies
58779420cf48b netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()
8b7c662950e81 ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()
66b2e36a28fce RDMA/cxgb4: Added NULL check for lookup_atid
32e5edc296e1a nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()
6832f76bf7d42 ext4: avoid OOB when system.data xattr changes underneath the filesystem
89278fdddd51e kthread: fix task state in kthread worker if being frozen
0994d75c1648c kthread: add kthread_work tracepoints
cad9f4314a05e drm/rockchip: vop: Allow 4096px width scaling
65dc79e557302 gpio: prevent potential speculation leaks in gpio_device_get_desc()

There's also a fix for a previous backport:

c4a2255b27149 nilfs2: fix incorrect use of nilfs_error()

Thank you for having a look.

CU
Uli


             reply	other threads:[~2024-11-18  7:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18  7:00 Ulrich Hecht [this message]
2024-11-19 19:48 ` Request for reviews for 4.4-st58, 4.4-cip93 Pavel Machek
2024-11-25  5:06 ` nobuhiro1.iwamatsu
2024-11-25  6:03   ` [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=1048687374.465216.1731913250080@webmail.strato.de \
    --to=uli@fpond.eu \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --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