[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <FE0E7BFD-7BCC-49A8-BBB4-060D924D28A6@oracle.com>
Date: Mon, 25 Apr 2022 17:51:17 +0000
From: Chuck Lever III <chuck.lever@...cle.com>
To: Jakub Kicinski <kuba@...nel.org>, Hannes Reinecke <hare@...e.de>
CC: netdev <netdev@...r.kernel.org>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
CIFS <linux-cifs@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"ak@...pesta-tech.com" <ak@...pesta-tech.com>,
"borisp@...dia.com" <borisp@...dia.com>,
"simo@...hat.com" <simo@...hat.com>
Subject: Re: [PATCH RFC 2/5] tls: build proto after context has been
initialized
> On Apr 25, 2022, at 1:11 PM, Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Mon, 18 Apr 2022 12:49:36 -0400 Chuck Lever wrote:
>> From: Hannes Reinecke <hare@...e.de>
>>
>> We have to build the proto ops only after the context has been
>> initialized, as otherwise we might crash when I/O is ongoing
>> during initialisation.
>
> Can you say more about the crash you see? protos are not used until
> at least one socket calls update_sk_prot().
Hannes reported the crash and supplied the fix. I didn't have a
problem with this patch series without this patch. Hannes?
--
Chuck Lever
Powered by blists - more mailing lists