[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2b3440abbb46c08be1160678b7c50efa5d246cf6.camel@oracle.com>
Date: Mon, 29 Jan 2024 21:03:34 +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 UPSTREAM 1/1] rds: Fix possible deadlock in
rds_message_put
On Fri, 2024-01-26 at 17:28 -0800, Jakub Kicinski wrote:
> On Fri, 26 Jan 2024 10:26:52 -0700
> allison.henderson@...cle.com wrote:
> > + if (to_drop) {
> > + rds_inc_put(to_drop);
> > +
> > rdsdebug("inc %p rs %p still %d dropped %d\n", inc, rs,
> > ret, drop);
> > return ret;
> > }
>
> This does not build..
Opps, apologies, I will re-check my build configs. Thank you!
Allison
Powered by blists - more mailing lists