[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <71ec8c74-270e-41f6-b336-0198b16dd697@online.de>
Date: Tue, 13 Feb 2024 12:54:03 +0100
From: Max Schulze <max.schulze@...ine.de>
To: Paolo Abeni <pabeni@...hat.com>, gregkh@...uxfoundation.org
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, tdeseyn@...hat.com
Subject: Re: [PATCH v2 net] tcp: allow again tcp_disconnect() when threads are
waiting
Am 14.10.23 um 02:00 schrieb patchwork-bot+netdevbpf@...nel.org:
> Hello:
>
> This patch was applied to netdev/net.git (main)
> by Jakub Kicinski <kuba@...nel.org>:
>
> On Wed, 11 Oct 2023 09:20:55 +0200 you wrote:
>> As reported by Tom, .NET and applications build on top of it rely
>> on connect(AF_UNSPEC) to async cancel pending I/O operations on TCP
>> socket.
>>
>> The blamed commit below caused a regression, as such cancellation
>> can now fail.
>>
>> [...]
Hello authors, Gregkh,
it looks to me like the breaking commit
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/net/ipv4/tcp.c?h=linux-4.19.y&id=0377416ce1744c03584df3e9461d4b881356d608
was applied to stable, but not the fix?
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/net/ipv4/tcp.c?id=419ce133ab928ab5efd7b50b2ef36ddfd4eadbd2
Could you consider applying the fix for 4.19 also?
Powered by blists - more mailing lists