public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
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-st42, 4.4-cip77
Date: Sun, 9 Jul 2023 21:50:34 +0200	[thread overview]
Message-ID: <ZKsPiq6+/Zx1CLHr@duo.ucw.cz> (raw)
In-Reply-To: <721088923.1980911.1688547506942@webmail.strato.com>

[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]

Hi!

> Here are the manual backports for the upcoming 4.4-st42 and 4.4-cip77 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
> 
> trivial backports:
> 

a| 61256d2d6 None o+ | netfilter: nft_dynset: do not reject set updates with NFT_SET_EVAL

Usual marking is "Commit xxx upstream.", this one has [ xxx ].

a | 42ca9589c 138906 o  | USB: core: Add routines for endpoint checks in old drivers
a | 72197f21d b8c75e o  | media: dvb-core: Fix kernel WARNING for blocking operation in wait_event*()
a | 66e262ad9 280a8a o  | media: dvb-core: Fix use-after-free due to race condition at dvb_ca_en50221
a | 22fb46cc1 2474e0 o+ | tty: serial: fsl_lpuart: use UARTCTRL_TXINV to send break instead of UARTCTRL_SBK
a | 1a5353475 fb686c o  | btrfs: check return value of btrfs_commit_transaction in relocation
a | ff0e8ed8d 85f02d o  | btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()
a | 1ba0925b4 b6ebaa o  | xen/blkfront: Only check REQ_FUA for writes
a | 2b88ccb93 50d927 o  | ocfs2: fix use-after-free when unmounting read-only filesystem
a | 6f40a2503 7651e2  + | IB/isert: Fix possible list corruption in CMA handler
a | 5304616a6 48bfd0 .  | drm/exynos: fix race condition UAF in exynos_g2d_exec_ioctl

> slightly more interesting backports with non-trivial differences in context:

a | 4e0dbab57 None o+ | netfilter: nf_tables: do not allow SET_ID to refer to another table

Again, usual marking is "Commit xxx upstream.", this one has [ xxx
]. And.. no this is not trivial backport.

a | 6119cae79 5c34c0 F+ | power: supply: bq27xxx: Fix bq27xxx_battery_update() race condition
a | 3bd7816c9 efb6b5 o+ | usb: gadget: f_fs: Add unbind event before functionfs_unbind
a | 4bb5329c7 1e5c64 o+ | rfs: annotate lockless accesses to sk->sk_rxhash
a | b221b7189 409e87 o  | ceph: fix use-after-free bug for inodes when flushing capsnaps

So... all seems to be good.

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 --]

  reply	other threads:[~2023-07-09 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05  8:58 Request for reviews for 4.4-st42, 4.4-cip77 Ulrich Hecht
2023-07-09 19:50 ` Pavel Machek [this message]
2023-07-10 16:47   ` [cip-dev] " Ulrich Hecht
     [not found]   ` <17708F7C47443676.32062@lists.cip-project.org>
2023-08-01 15:24     ` Upstream hash format in commit messages; was: " 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=ZKsPiq6+/Zx1CLHr@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