netdev - Re: [PATCH] net: Fix the devmem sock opts and msgs for parisc

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 for Android: free password hash cracker in your pocket

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

Message-ID: <67dd8beeeff3_14b14029476@willemb.c.googlers.com.notmuch>
Date: Fri, 21 Mar 2025 11:55:26 -0400
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Pranjal Shrivastava <praan@...gle.com>, 
 "David S . Miller" <davem@...emloft.net>, 
 Eric Dumazet <edumazet@...gle.com>, 
 Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, 
 linux-parisc@...r.kernel.org, 
 Willem de Bruijn <willemb@...gle.com>, 
 Mina Almasry <almasrymina@...gle.com>, 
 Pranjal Shrivastava <praan@...gle.com>
Subject: Re: [PATCH] net: Fix the devmem sock opts and msgs for parisc

Pranjal Shrivastava wrote:
> The devmem socket options and socket control message definitions
> introduced in the TCP devmem series[1] incorrectly continued the socket
> definitions for arch/parisc.
> 
> The UAPI change seems safe as there are currently no drivers that
> declare support for devmem TCP RX via PP_FLAG_ALLOW_UNREADABLE_NETMEM.
> Hence, fixing this UAPI should be safe.
> 
> Fix the devmem socket options and socket control message definitions to
> reflect the series followed by arch/parisc.
> 
> [1]
> https://lore.kernel.org/lkml/20240910171458.219195-10-almasrymina@google.com/
> 
> Fixes: 8f0b3cc9a4c10 ("tcp: RX path for devmem TCP")
> Signed-off-by: Pranjal Shrivastava <praan@...gle.com>

This patch is already marked in patchwork as not applicable.

Because it is not correctly marked as [PATCH net]?

Patchwork interpreted it as not a local patch.

It affects parisc, but the patch referenced in Fixes also went in
through net-next. So I think this should go through net.