[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180314213354.GH24557@oracle.com>
Date: Wed, 14 Mar 2018 17:33:54 -0400
From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: syzbot <syzbot+c68e51bb5e699d3f8d91@...kaller.appspotmail.com>,
davem@...emloft.net, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
rds-devel@....oracle.com, santosh.shilimkar@...cle.com,
syzkaller-bugs@...glegroups.com
Subject: Re: WARNING in __local_bh_enable_ip (2)
On (03/14/18 14:28), Eric Dumazet wrote:
>
>
> spin_lock_bh(&rds_tcp_conn_lock);/spin_unlock_bh(&rds_tcp_conn_lock); in
> rds_tcp_conn_free()
>
> is in conflict with the spin_lock_irqsave(&rds_conn_lock, flags);
> in __rds_conn_create()
yes I was going to look into this and fix it later.
> Hard to understand why RDS is messing with hard irqs really.
some of it comes from the rds_rdma history: some parts of
the common rds and rds_rdma module get called in various
driver contexts for infiniband.
--Sowmini
Powered by blists - more mailing lists