[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6c63549d6771bfb1ab410338b2dcea3e3fedb415.camel@oracle.com>
Date: Wed, 7 Feb 2024 17:23:53 +0000
From: Allison Henderson <allison.henderson@...cle.com>
To: "kuba@...nel.org" <kuba@...nel.org>
CC: "rds-devel@....oracle.com" <rds-devel@....oracle.com>,
Santosh Shilimkar
<santosh.shilimkar@...cle.com>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"davem@...emloft.net"
<davem@...emloft.net>
Subject: Re: [PATCH v2 1/1] net:rds: Fix possible deadlock in rds_message_put
On Tue, 2024-02-06 at 18:48 -0800, Jakub Kicinski wrote:
> On Wed, 31 Jan 2024 10:54:17 -0700
> allison.henderson@...cle.com wrote:
> > Fixes: possible deadlock in rds_message_put
>
> This is not a correct Fixes tag. Please look at git history
Sorry, the fixes tag identifies the offending commit? I think it's an
existing bug since the code was introduced. Which would be:
Fixes: bdbe6fbc6a2f (RDS: recv.c)
If that's not a useful tag, I can remove it too. The syzbot bisect
points to a virtio commit 1628c6877f37, but that doesn't look correct
to me. Let me know what you would prefer. Thank you!
Allison
Powered by blists - more mailing lists