From: Bart Van Assche <bvanassche@acm.org>
To: Bernard Metzler <bmt@zurich.ibm.com>, linux-rdma@vger.kernel.org
Subject: Re: siw trigger BUG: sleeping function called from invalid context at mm/slab.h:50
Date: Fri, 23 Aug 2019 16:41:37 -0700 [thread overview]
Message-ID: <03dfc9ef-c854-4821-7eaa-9f862bcc6d70@acm.org> (raw)
In-Reply-To: <6ed77231-800b-f629-5d15-14409f0777c7@acm.org>
On 8/23/19 4:02 PM, Bart Van Assche wrote:
> If I try to associate the ib_srpt driver with the siw driver the
> complaint shown below appears on the console.
According to gdb:
(gdb) list *(siw_create_listen+0x2f5)
0x6195 is in siw_create_listen (drivers/infiniband/sw/siw
/siw_cm.c:2011).
2006 bind_addr.sin6_port =
s_laddr->sin6_port;
2007 bind_addr.sin6_flowinfo = 0;
2008 bind_addr.sin6_addr = ifp->addr;
2009 bind_addr.sin6_scope_id = dev->ifindex;
2010
2011 rv = siw_listen_address(id, backlog,
2012 (struct sockaddr *)&bind_addr,
2013 AF_INET6);
2014 if (!rv)
2015 listeners++;
This is the code that causes trouble:
read_lock_bh(&in6_dev->lock);
list_for_each_entry(ifp, &in6_dev->addr_list, if_list) {
struct sockaddr_in6 bind_addr;
if (ipv6_addr_any(&s_laddr->sin6_addr) ||
ipv6_addr_equal(&s_laddr->sin6_addr, &ifp->addr)) {
bind_addr.sin6_family = AF_INET6;
bind_addr.sin6_port = s_laddr->sin6_port;
bind_addr.sin6_flowinfo = 0;
bind_addr.sin6_addr = ifp->addr;
bind_addr.sin6_scope_id = dev->ifindex;
rv = siw_listen_address(id, backlog,
(struct sockaddr *)&bind_addr,
AF_INET6);
if (!rv)
listeners++;
}
}
read_unlock_bh(&in6_dev->lock);
siw_listen_address() calls sock_create(). I don't think it is allowed to
call sock_create() from atomic context.
Thanks,
Bart.
next prev parent reply other threads:[~2019-08-23 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 23:02 siw trigger BUG: sleeping function called from invalid context at mm/slab.h:50 Bart Van Assche
2019-08-23 23:41 ` Bart Van Assche [this message]
2019-08-26 8:00 ` Bernard Metzler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03dfc9ef-c854-4821-7eaa-9f862bcc6d70@acm.org \
--to=bvanassche@acm.org \
--cc=bmt@zurich.ibm.com \
--cc=linux-rdma@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox