CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@nabladev.com>
To: Ulrich Hecht <uli@fpond.eu>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"pavel@nabladev.com" <pavel@nabladev.com>,
	"nobuhiro.iwamatsu.x90@mail.toshiba"
	<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Re: Request for review for 4.19-st20, 4.19-cip136
Date: Thu, 10 Sep 2026 21:32:45 +0200	[thread overview]
Message-ID: <aqMF3bvKF4A-mzbV@duo.ucw.cz> (raw)
In-Reply-To: <588742173.259606.1788373971804@webmail.strato.de>

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

Hi!

> Here are the "manual" backports for the upcoming 4.19 kernel release. There's a total of 68; 40 by me, and 28 by LLM. (The latter are labeled with "Assisted-by: SLTR:qwen-3.8".)
> 
> 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
>

Reviewed-by: Pavel Machek <pavel@nabladev.com>

Most of the patches look good to me, some questions are below.

Thanks and sorry that it took so long.

Best regards,
								Pavel

a > 231854d20f22b KVM: nVMX: Hide shadow VMCS right after VMCLEAR
a > c4bc9e59cd758 perf/x86/amd/core: Always use the NMI latency mitigation
a > a0aef239f4722 i2c: core: fix adapter registration race
a just a API fix > 6cff48ecf1d69 net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink
a > c7b13e80811aa nfsd: release layout stid on setlease failure
a > d75140d1212a2 i2c: imx: fix locked bus on SMBus block-read of 0 (atomic)
a > e33cc57dadde8 selinux: avoid sk_socket dereference in selinux_sctp_bind_connect()
a > b8c1bbd016710 net/openvswitch: check Ethernet header length in key_extract()
a > f965a98a469c3 net: ipv6: fix dif and sdif mismatch in raw6_icmp_error
a original patch could use function reordering > 7bdb312c113d2 smb: client: restrict implied bcc[0] exemption to responses without data area
a > 8f223fbe6b2d4 batman-adv: retrieve ethhdr after potential skb realloc on RX

I guess I'm confused here. This one is not correct on its own, as it
creates non-balanced situation. Is the 1c72d53630aa3 fixing it up?
Where does 1c72d53630aa3 come from? Will it cause bisect problems?

!! > 1c72d53630aa3 NFS: Pin the 'struct nfs_server' during a FREE_STATEID call

This one does not have "upstream commit" annotation, and I could not
find where it comes from. I checked 6.12-cip version, and it looks
very different from this.

!! no upstream annotation > f1f7d30dcdfaa NFS: Decrement refcounts if allocating nfs_free_stateid_data fails



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

  parent reply	other threads:[~2026-09-10 19:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 18:32 Request for review for 4.19-st20, 4.19-cip136 Ulrich Hecht
2026-09-03  9:00 ` Pavel Machek
2026-09-03  9:18   ` Ulrich Hecht
2026-09-03 11:59 ` Pavel Machek
2026-09-10  8:09   ` [cip-dev] " Ulrich Hecht
2026-09-07 11:04 ` Pavel Machek
2026-09-10  8:09   ` [cip-dev] " Ulrich Hecht
2026-09-09 19:23 ` Pavel Machek
2026-09-10 19:32 ` Pavel Machek [this message]
2026-09-11 10:15   ` [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=aqMF3bvKF4A-mzbV@duo.ucw.cz \
    --to=pavel@nabladev.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --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