From: Jason Gunthorpe <jgg@nvidia.com>
To: Bart Van Assche <bvanassche@acm.org>,
Leon Romanovsky <leonro@nvidia.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-rdma@vger.kernel.org
Subject: Re: v5.14-rc5: KASAN complains about use-after-free in __ib_process_cq()
Date: Mon, 23 Aug 2021 14:32:06 -0300 [thread overview]
Message-ID: <20210823173206.GQ1721383@nvidia.com> (raw)
In-Reply-To: <eac61295-05d2-98f2-eb32-280ffec8269f@acm.org>
On Mon, Aug 23, 2021 at 10:30:39AM -0700, Bart Van Assche wrote:
> Hi,
>
> If I run blktests against Jens' for-next branch (5026771bd46e ("Merge branch
> 'for-5.15/io_uring-late' into for-next")) then most SRP tests time out.
> Additionally, a KASAN use-after-free complaint is sometimes reported for
> __ib_process_cq(). With commit 4b5f4d3fb408 ("RDMA: Split the alloc_hw_stats()
> ops to port and device variants") however all SRP tests pass and no KASAN
> complaints are reported. There are no changes in the SRP drivers between these
> two commits. This makes me wonder whether a regression has been introduced in
> the RDMA core? I have not yet run a full bisect - this is something I am
> working on. Please note that I may be hitting multiple unrelated issues -
> there is no evidence so far that the SRP test timeouts are related to changes
> in the RDMA code. These could also be caused by changes in the block layer.
Maybe Leon's QP rework?
Jason
prev parent reply other threads:[~2021-08-23 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 17:30 v5.14-rc5: KASAN complains about use-after-free in __ib_process_cq() Bart Van Assche
2021-08-23 17:32 ` Jason Gunthorpe [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=20210823173206.GQ1721383@nvidia.com \
--to=jgg@nvidia.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=leonro@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.