public inbox for cip-dev@lists.cip-project.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.4-st73, 4.4-cip108
Date: Thu, 26 Feb 2026 12:05:21 +0100	[thread overview]
Message-ID: <aaAo8TUKFDgI9j+f@duo.ucw.cz> (raw)
In-Reply-To: <440487134.6462.1771997574376@webmail.strato.de>

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

Hi!

> Here are 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
> 
a > dd2af1ff15baa macvlan: fix possible UAF in macvlan_forward_source()
a > 6e7f9685b9d35 wifi: wlcore: ensure skb headroom before skb_push
a > 1b847006e7141 sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT
a> bf3c650dfddf3 btrfs: fix deadlock in wait_current_trans() due to ignored transaction type
a> 9dbc25309be1c net/sched: sch_qfq: do not free existing class in qfq_change_class()
>

Thank you, these look good to me.

> Plus one fix for my convenience:
> 
> e0e89cfcf08df arm64: replace Sun/Solaris style flag on section directive

Pointer "mainline equivalent of this is XXX" would be nice here.

Thanks and best regards,
									Pavel

Author: Ulrich Hecht <uli@kernel.org>
Date:   Tue Feb 24 18:21:17 2026 +0800

    arm64: replace Sun/Solaris style flag on section directive
    
    Fixes compilation with recent GNU toolchains.
    
    Signed-off-by: Ulrich Hecht <uli@kernel.org>

diff --git a/arch/arm64/mm/proc.S b/arch/arm64/mm/proc.S
index 0b095b75abeb74..16b1b654d14020 100644
--- a/arch/arm64/mm/proc.S
+++ b/arch/arm64/mm/proc.S
@@ -152,7 +152,7 @@ alternative_else
 alternative_endif
 ENDPROC(cpu_do_switch_mm)
 
-       .section ".text.init", #alloc, #execinstr
+       .section ".text.init", "ax"
 
 /*
  *     __cpu_setup


-- 
In cooperation with Nabla.

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

  reply	other threads:[~2026-02-26 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  5:32 Request for review for 4.4-st73, 4.4-cip108 Ulrich Hecht
2026-02-26 11:05 ` Pavel Machek [this message]
2026-03-03  2:18   ` [cip-dev] " Ulrich Hecht
2026-02-27  6:50 ` nobuhiro.iwamatsu.x90

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=aaAo8TUKFDgI9j+f@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