netdev - Re: [PATCH bpf-next v3 0/3] net/smc: Introduce smc_hs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251028121531.GA51645@j66a10360.sqa.eu95>
Date: Tue, 28 Oct 2025 20:15:31 +0800
From: "D. Wythe" <alibuda@...ux.alibaba.com    >
To: "D. Wythe" <alibuda@...ux.alibaba.com>, martin.lau@...ux.de,
	ast@...nel.org, andrii.nakryiko@...il.com
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
	martin.lau@...ux.dev, pabeni@...hat.com, song@...nel.org,
	sdf@...gle.com, haoluo@...gle.com, yhs@...com, edumazet@...gle.com,
	john.fastabend@...il.com, kpsingh@...nel.org, jolsa@...nel.org,
	mjambigi@...ux.ibm.com, wenjia@...ux.ibm.com, wintera@...ux.ibm.com,
	dust.li@...ux.alibaba.com, tonylu@...ux.alibaba.com,
	guwen@...ux.alibaba.com, bpf@...r.kernel.org, davem@...emloft.net,
	kuba@...nel.org, netdev@...r.kernel.org, sidraya@...ux.ibm.com,
	jaka@...ux.ibm.com
Subject: Re: [PATCH bpf-next v3 0/3] net/smc: Introduce smc_hs_ctrl

On Mon, Sep 29, 2025 at 02:33:57PM +0800, D. Wythe wrote:
> This patch aims to introduce BPF injection capabilities for SMC and
> includes a self-test to ensure code stability.
> 
> Since the SMC protocol isn't ideal for every situation, especially
> short-lived ones, most applications can't guarantee the absence of
> such scenarios. Consequently, applications may need specific strategies
> to decide whether to use SMC. For example, an application might limit SMC
> usage to certain IP addresses or ports.
> 
> To maintain the principle of transparent replacement, we want applications
> to remain unaffected even if they need specific SMC strategies. In other
> words, they should not require recompilation of their code.
> 
> Additionally, we need to ensure the scalability of strategy implementation.
> While using socket options or sysctl might be straightforward, it could
> complicate future expansions.
> 
> Fortunately, BPF addresses these concerns effectively. Users can write
> their own strategies in eBPF to determine whether to use SMC, and they can
> easily modify those strategies in the future.
> 
> This is a rework of the series from [1]. Changes since [1] are limited to
> the SMC parts:
> 
> 1. Rename smc_ops to smc_hs_ctrl and change interface name.
> 2. Squash SMC patches, removing standalone non-BPF hook capability.
> 3. Fix typos


Hi bpf folks,

I've noticed this patch has been pending for a while, and I wanted to
gently check in. Is there any specific concerns or feedback regarding
it from the BPF side? I'm keen to address any issues and move it
forward.

Also, I'd appreciate your guidance on whether this patch should be
targeted for net-next.

Thanks for your time and consideration.

Best regards,
D. Wythe