All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bernard Metzler" <BMT@zurich.ibm.com>
To: "Bart Van Assche" <bvanassche@acm.org>
Cc: linux-rdma@vger.kernel.org, "Jason Gunthorpe" <jgg@nvidia.com>
Subject: Re: v5.15-rc1 issue with the soft-iWARP driver
Date: Thu, 16 Sep 2021 19:18:55 +0000	[thread overview]
Message-ID: <OF74B9ECF6.B2B7F2D4-ON00258752.00675A19-00258752.006A1A3D@ibm.com> (raw)
In-Reply-To: <ccb9ee03-4aaa-2288-3d2f-ce01f550a609@acm.org>

-----"Bart Van Assche" <bvanassche@acm.org> wrote: -----

>To: linux-rdma@vger.kernel.org, "Jason Gunthorpe" <jgg@nvidia.com>
>From: "Bart Van Assche" <bvanassche@acm.org>
>Date: 09/15/2021 06:54AM
>Subject: [EXTERNAL] v5.15-rc1 issue with the soft-iWARP driver
>
>Hi,
>
>If I run test srp/015 from the blktests suite then the following
>appears
>in the kernel log:
>
>==================================================================
>BUG: KASAN: null-ptr-deref in __list_del_entry_valid+0x4d/0xe0
>Read of size 8 at addr 0000000000000000 by task kworker/u16:3/161
>
>CPU: 5 PID: 161 Comm: kworker/u16:3 Not tainted 5.15.0-rc1-dbg+ #2
>Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
>rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014
>Workqueue: iw_cm_wq cm_work_handler [iw_cm]
>Call Trace:
>  show_stack+0x52/0x58
>  dump_stack_lvl+0x5b/0x82
>  kasan_report.cold+0x52/0x57
>  __asan_load8+0x69/0x90
>  __list_del_entry_valid+0x4d/0xe0
>  _cma_cancel_listens+0x49/0x230 [rdma_cm]
>  _destroy_id+0x4e/0x420 [rdma_cm]
>  destroy_id_handler_unlock+0xc4/0x200 [rdma_cm]
>  iw_conn_req_handler+0x335/0x370 [rdma_cm]
>  cm_conn_req_handler+0x546/0x7d0 [iw_cm]
>  cm_work_handler+0x419/0x480 [iw_cm]
>  process_one_work+0x59d/0xb00
>  worker_thread+0x8f/0x5c0
>  kthread+0x1fc/0x230
>  ret_from_fork+0x1f/0x30
>==================================================================
>
>I think this is a regression. This happened with commit a17a1faf5d3e
>("RDMA/cma: Fix listener leak in rdma_cma_listen_on_all() failure").
>
So far I could not reproduce it with that patch (tried to get better
understanding with siw debugging enabled). That doesn't mean much.

But I do see issues with rxe if running the complete srp set from
blktest, which seem to be unrelated. I'll send an extra message.

Many thanks,
Bernard.

      parent reply	other threads:[~2021-09-16 19:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15  4:54 v5.15-rc1 issue with the soft-iWARP driver Bart Van Assche
2021-09-15 14:34 ` Jason Gunthorpe
2021-09-16 19:18 ` Bernard Metzler [this message]

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=OF74B9ECF6.B2B7F2D4-ON00258752.00675A19-00258752.006A1A3D@ibm.com \
    --to=bmt@zurich.ibm.com \
    --cc=bvanassche@acm.org \
    --cc=jgg@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.