From: Alexandra Winter <wintera@linux.ibm.com>
To: Bryam Vargas <hexlabsecurity@proton.me>,
Thorsten Winkler <twinkler@linux.ibm.com>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S . Miller" <davem@davemloft.net>
Cc: Hidayath Khan <hidayath@linux.ibm.com>,
Simon Horman <horms@kernel.org>,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 1/2] net/iucv: drop HiperSockets frames from other network namespaces
Date: Mon, 24 Aug 2026 10:47:58 +0200 [thread overview]
Message-ID: <ac920c76-07db-43f4-ad95-da36073ca45a@linux.ibm.com> (raw)
In-Reply-To: <20260821114210.430509-1-hexlabsecurity@proton.me>
On 21.08.26 13:42, Bryam Vargas wrote:
> Alexandra,
>
>> I am wondering whether a check of
>> + if (iucv_sk(sk)->hs_dev != dev)
>> + continue;
>>
>> would cover a broader range of issues.
>
> It does, and I'd rather have yours than mine. It covers three things at
> once: the namespace case, since hs_dev can only come from the init_net scan
> in iucv_sock_bind(); the transport case the earlier patch went after, since
> classic sockets have hs_dev == NULL and drop out of the walk; and delivery
> to a socket bound to a different HiperSockets device.
>
> I went looking for the regression it could carry -- an accept-queue child
> left without hs_dev, which would break connection setup -- and it isn't
> there. The child inherits at af_iucv.c:1908.
>
> One thing it doesn't reach, and it's why I'm not dropping both: the check
> sits after EBCASC() has already rewritten the transport header in place at
> :2073-2076, and a SYN matching no socket still takes the !iucv branch at
> :1872-1877, which swaps the frame and hands it to dev_queue_xmit(). So it
> replaces 1/2 and stays complementary to 2/2.
>
> Send yours and I'll drop 1/2.
>
> Thanks,
> Bryam
>
Thank you very much Bryam, I fully agree.
I've sent R-b for 2/2, and propose to take it as it is.
See https://lore.kernel.org/netdev/20260821125501.3718748-1-wintera@linux.ibm.com/
for my proposal that should supersede 1/2.
Your review would be highly appreciated.
next prev parent reply other threads:[~2026-08-24 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 16:07 [PATCH net 0/2] net/iucv: give afiucv_hs_rcv() the preamble a packet_type handler needs Bryam Vargas via B4 Relay
2026-08-15 16:07 ` [PATCH net 1/2] net/iucv: drop HiperSockets frames from other network namespaces Bryam Vargas via B4 Relay
2026-08-19 15:06 ` Alexandra Winter
2026-08-21 11:42 ` Bryam Vargas
2026-08-24 8:47 ` Alexandra Winter [this message]
2026-08-15 16:07 ` [PATCH net 2/2] net/iucv: take a private, writable frame before rewriting it in place Bryam Vargas via B4 Relay
2026-08-18 11:55 ` Alexandra Winter
2026-08-21 11:42 ` Bryam Vargas
2026-08-21 14:55 ` Hidayath Khan
2026-08-24 8:33 ` Alexandra Winter
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=ac920c76-07db-43f4-ad95-da36073ca45a@linux.ibm.com \
--to=wintera@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hexlabsecurity@proton.me \
--cc=hidayath@linux.ibm.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=twinkler@linux.ibm.com \
/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
all inboxes | Powered by JetHome®