lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 29 Jan 2017 09:39:39 +0200
From:   Sagi Grimberg <sagi@...mberg.me>
To:     Stevie Trujillo <stevie.trujillo@...il.com>,
        target-devel@...r.kernel.org, linux-rdma@...r.kernel.org,
        linux-kernel@...r.kernel.org, Doug Ledford <dledford@...hat.com>,
        Sean Hefty <sean.hefty@...el.com>,
        Hal Rosenstock <hal.rosenstock@...il.com>
Subject: Re: "isert: isert_setup_id: rdma_bind_addr() failed: -19" spam,
 followed by Recursive Fault on reboot


> Hello

Hey Steve,

> I'm trying (failing) to get iSER working. After rebooting with some settings
> saved in targetcli, I got an endless stream of messages like this:
>
> [  192.701299] isert: isert_setup_id: rdma_bind_addr() failed: -19
> [  192.702733] isert: isert_setup_id: rdma_bind_addr() failed: -19
> [  192.704021] isert: isert_setup_id: rdma_bind_addr() failed: -19
> [  192.705458] isert: isert_setup_id: rdma_bind_addr() failed: -19
> [  192.706979] isert: isert_setup_id: rdma_bind_addr() failed: -19

You get -ENODEV errors because you don't have an RDMA device.
This is probably due to the fact that the mlx5_ib (or mlx4_ib, depending
on your device) is not loaded.

Can you try loading mlx[4|5]_ib module before you enable iser on
a network portal?

I do see that mlx5 and mlx4 are requesting the mlx_ib module at probe
time, I wander how that didn't happen on your system..

I didn't see a endless loop of this error? can you share your
targetcli json?

> I tried deleting everything from targetcli, but the flood would not stop. The
> ib_isert module did not unload. When rebooting I got a "Recursive Fault"
> with a stacktrace inside configfs.
>
> I hope this is enough information to fix this bug. I assumed the stacktrace
> would be saved to the log so I didn't write it down, and I haven't been able to
> retrace all the wrong stuff I did trying to make iSER work.
>
> Linux Version: Linux 4.8.15-2~bpo8+2 (Debian 8 Backports)

Would it be possible to try with upstream kernel and report what you
are seeing?

Powered by blists - more mailing lists