[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5CE43DB5-8171-4C44-82AA-726E71D5C087@oracle.com>
Date: Wed, 22 Mar 2023 16:32:39 +0000
From: Chuck Lever III <chuck.lever@...cle.com>
To: Paolo Abeni <pabeni@...hat.com>
CC: Chuck Lever <cel@...nel.org>, Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>,
"kernel-tls-handshake@...ts.linux.dev"
<kernel-tls-handshake@...ts.linux.dev>,
John Haxby <john.haxby@...cle.com>
Subject: Re: [PATCH v7 1/2] net/handshake: Create a NETLINK service for
handling handshake requests
> On Mar 22, 2023, at 9:35 AM, Chuck Lever III <chuck.lever@...cle.com> wrote:
>
>> On Mar 22, 2023, at 5:03 AM, Paolo Abeni <pabeni@...hat.com> wrote:
>
>> plus explicitly triggering some errors path e.g.
>>
>> hn_pending_max+1 consecutive submit with no accept
>> handshake_cancel after handshake_complete
>> multiple handshake_complete on the same req
>> multiple handshake_cancel on the same req
>
> OK. I'm wondering if a user agent needs to be running
> for these, in which case, running Kunit in its stand-
> alone mode (ie, under UML) might not work at all.
>
> Just thinking out loud... Kunit after all might not be
> the right tool for this job.
Actually, maybe I can make handshake_genl_notify() a
no-op when running under Kunit. That should enable
tests to run without a user space handler agent.
--
Chuck Lever
Powered by blists - more mailing lists