From: Alexandra Winter <wintera@linux.ibm.com>
To: Bryam Vargas <hexlabsecurity@proton.me>
Cc: Hidayath Khan <hidayath@linux.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thorsten Winkler <twinkler@linux.ibm.com>
Subject: Re: [RFC] net/iucv: af_iucv socket locking - accounting, and a staged plan
Date: Mon, 10 Aug 2026 09:47:12 +0200 [thread overview]
Message-ID: <6f82c1f5-06f5-431d-9b23-4e34c8572c8a@linux.ibm.com> (raw)
In-Reply-To: <20260809014911.752106-1-hexlabsecurity@proton.me>
On 09.08.26 03:49, Bryam Vargas wrote:
>> That would be great, we are also working on several small fixes. Let's get them out of the way.
> The connack patch is written: bh_lock_sock() in iucv_callback_connack(), the one
> site whose context is unambiguous, since connrej and shutdown run in the same
> tasklet and already take it. Fixes: eac3731bd04c - the function has held no lock
> since 2007. checkpatch --strict is quiet and it builds for s390x. Which tree do
> you want it against?
net, please.
next prev parent reply other threads:[~2026-08-10 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 22:29 [RFC] net/iucv: af_iucv socket locking - accounting, and a staged plan Bryam Vargas
2026-07-28 12:52 ` Alexandra Winter
2026-08-09 1:49 ` Bryam Vargas
2026-08-10 7:47 ` Alexandra Winter [this message]
2026-08-22 19:08 ` Hidayath Khan
2026-08-28 18:34 ` Bryam Vargas
2026-09-02 15:09 ` Hidayath Khan
2026-08-21 15:28 ` Hidayath Khan
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=6f82c1f5-06f5-431d-9b23-4e34c8572c8a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.