[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b3c99664-a628-4d6b-8033-3d6e109e9a3e@yandex.ru>
Date: Wed, 14 Feb 2024 19:34:16 +0300
From: Dmitry Antipov <dmantipov@...dex.ru>
To: Wenjia Zhang <wenjia@...ux.ibm.com>, Ursula Braun <ubraun@...ux.ibm.com>
Cc: Karsten Graul <kgraul@...ux.ibm.com>, Jan Karcher <jaka@...ux.ibm.com>,
"David S . Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
lvc-project@...uxtesting.org
Subject: Re: [PATCH] net: smc: fix spurious error message from
__sock_release()
On 2/14/24 18:09, Wenjia Zhang wrote:
> - It looks reasonable to me. I'm curious how you got the warning. By using ULP, right?
This was tracked down from https://syzkaller.appspot.com/bug?extid=5f1acda7e06a2298fae6,
and unfortunately it doesn't fix an actual leak of 'struct fasync_struct' objects. I'm
suspecting an undefined behavior caused by the race condition somewhere around socket
impersonation tricks in 'smc_switch_to_fallback()', and it would be very helpful if an
original authors can take a look as well.
Dmitry
Powered by blists - more mailing lists