public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Wang <jinpu.wang-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Sebastian Riemer
	<sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: Shlomo Pongratz <shlomop-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: BUG: unable to handle kernel paging request at 0000000000070a78 IPoIB
Date: Tue, 21 May 2013 17:19:54 +0200	[thread overview]
Message-ID: <519B909A.8010004@profitbricks.com> (raw)
In-Reply-To: <519B6DD6.4090502-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>

On 05/21/2013 02:51 PM, Sebastian Riemer wrote:
> On 17.05.2013 16:16, Jack Wang wrote:
>> unable to handle kernel paging request
> 
> Hi Jack,
> 
> this should be related to the list corruption in IPoIB as list_del()
> sets the LIST_POISON1 and LIST_POISON2 pointers.
> Referencing these results in page faults according to the documentation
> in the code.
> 
> Cheers,
> Sebastian
> 
This bug is easy triggered with below inject_bug with iperf -P 50 &&
switch ib mode in sync on both side.
-- a/drivers/infiniband/ulp/ipoib/ipoib_cm.c
+++ b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
@@ -1315,7 +1315,8 @@ static void ipoib_cm_tx_start(struct work_struct
*work)
 		netif_tx_lock_bh(dev);
 		spin_lock_irqsave(&priv->lock, flags);

-		if (ret) {
+		if (ret || priv->inject_bug) {
+			priv->inject_bug = 0;
 			neigh = p->neigh;
 			if (neigh) {
 				neigh->cm = NULL;

It turned into another panic after patch list_del to list_del_init, I'm
managing to get the back trace.
--
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

  parent reply	other threads:[~2013-05-21 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 14:16 BUG: unable to handle kernel paging request at 0000000000070a78 IPoIB Jack Wang
     [not found] ` <51963BC6.1050901-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-05-21 12:51   ` Sebastian Riemer
     [not found]     ` <519B6DD6.4090502-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-05-21 15:19       ` Jack Wang [this message]
     [not found]         ` <519B909A.8010004-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-05-23 15:38           ` Jack Wang
     [not found]             ` <519E37DE.1080504-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-05-23 17:41               ` Doug Ledford
     [not found]                 ` <519E54D9.1050506-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-05-23 18:53                   ` Jack Wang
     [not found]                     ` <519E65B5.1090909-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-05-23 18:55                       ` Doug Ledford

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=519B909A.8010004@profitbricks.com \
    --to=jinpu.wang-eikl63zcoxah+58jc4qpia@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
    --cc=shlomop-VPRAkNaXOzVWk0Htik3J/w@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