[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180811.112225.71238093640629717.davem@davemloft.net>
Date: Sat, 11 Aug 2018 11:22:25 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: sowmini.varadhan@...cle.com
Cc: netdev@...r.kernel.org, rds-devel@....oracle.com,
santosh.shilimkar@...cle.com
Subject: Re: [PATCH net-next] rds: avoid lock hierarchy violation between
m_rs_lock and rs_recv_lock
From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
Date: Wed, 8 Aug 2018 13:57:13 -0700
> The following deadlock, reported by syzbot, can occur if CPU0 is in
> rds_send_remove_from_sock() while CPU1 is in rds_clear_recv_queue()
>
> CPU0 CPU1
> ---- ----
> lock(&(&rm->m_rs_lock)->rlock);
> lock(&rs->rs_recv_lock);
> lock(&(&rm->m_rs_lock)->rlock);
> lock(&rs->rs_recv_lock);
>
> The deadlock should be avoided by moving the messages from the
> rs_recv_queue into a tmp_list in rds_clear_recv_queue() under
> the rs_recv_lock, and then dropping the refcnt on the messages
> in the tmp_list (potentially resulting in rds_message_purge())
> after dropping the rs_recv_lock.
>
> The same lock hierarchy violation also exists in rds_still_queued()
> and should be avoided in a similar manner
>
> Signed-off-by: Sowmini Varadhan <sowmini.varadhan@...cle.com>
> Reported-by: syzbot+52140d69ac6dc6b927a9@...kaller.appspotmail.com
I'm putting this in deferred state for now.
Sowmini, once you and Santosh agree on what exactly to do, please
resubmit.
Thank you.
Powered by blists - more mailing lists