From: "Nicholas A. Bellinger" <nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>
To: Bart Van Assche <bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
target-devel
<target-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: SRPt oops with 4.5-rc3-ish
Date: Sat, 27 Feb 2016 20:47:08 -0800 [thread overview]
Message-ID: <1456634828.19657.84.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <56D274F8.9070804-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
On Sat, 2016-02-27 at 20:18 -0800, Bart Van Assche wrote:
> On 02/27/16 19:37, Nicholas A. Bellinger wrote:
> > This is a fairly recent srpt shutdown regression, right..?
>
> Hi Nic,
>
> My patch series to make TMR handling synchronous fixes what Doug
> reported. If you want I can rebase and repost that patch series.
>
There aren't even any TMRs being processed, so I don't see how that has
anything to do with it.
>From the logs, this OOPsen is related to some manner of recent srpt
configfs se_node_acl + se_session active I/O shutdown regression.
So short of sitting down and reproducing myself on v4.5-rc code,
commit 59fae4de's removal of ib_create_cq() + ib_comp_handler callback
usage look like a good place to start the investigation.
It would be useful to first find out what changes introduced this
regression, and how far back Doug is able to reproduce.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-28 4:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 16:09 SRPt oops with 4.5-rc3-ish Doug Ledford
2016-02-28 3:37 ` Nicholas A. Bellinger
[not found] ` <1456630639.19657.47.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2016-02-28 4:18 ` Bart Van Assche
[not found] ` <56D274F8.9070804-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-02-28 4:47 ` Nicholas A. Bellinger [this message]
2016-02-28 4:49 ` Bart Van Assche
2016-02-28 5:00 ` Nicholas A. Bellinger
2016-03-03 15:24 ` Doug Ledford
2016-02-28 8:26 ` Nicholas A. Bellinger
2016-02-28 16:14 ` Bart Van Assche
[not found] ` <56D31CC9.7000609-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-02-28 20:43 ` Nicholas A. Bellinger
2016-02-29 0:37 ` Bart Van Assche
[not found] ` <56D392D4.2000105-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-02-29 6:05 ` Christoph Hellwig
2016-03-01 6:49 ` Nicholas A. Bellinger
2016-03-01 7:16 ` Christoph Hellwig
[not found] ` <1456647963.19657.135.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2016-04-11 20:08 ` Doug Ledford
[not found] ` <56C0A6C3.3010903-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-02-16 1:42 ` Bart Van Assche
2016-02-29 9:11 ` Christoph Hellwig
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=1456634828.19657.84.camel@haakon3.risingtidesystems.com \
--to=nab-izhhd5pylfbp7fqvkimdcq@public.gmane.org \
--cc=bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=target-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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