From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Jack Wang <xjtuwjp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Jack Morgenstein
<jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Moni Shoua <monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: Mlx4: BUG: unable to handle kernel at ffffffffa02be210
Date: Wed, 8 Jul 2015 16:49:52 +0300 [thread overview]
Message-ID: <559D2A80.4040909@mellanox.com> (raw)
In-Reply-To: <CAD+HZHVCMa97zEQ1SB=JXCKHOGgSO93BPyLha2PDrOOTsHTUCw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 7/8/2015 3:47 PM, Jack Wang wrote:
> static void mlx4_ib_cq_comp(struct mlx4_cq *cq)
> 47 {
> 48 struct ib_cq *ibcq = &to_mibcq(cq)->ibcq;
> 49 ibcq->comp_handler(ibcq, ibcq->cq_context);
> 50 }
>
> Looks like cq use-after-free? I have no idea where.
see if you have in the code base you're using (why not the stock 3.18.14
driver, BTW?) all the synchronize_irq
calls we have in the latest upstream driver:
drivers/net/ethernet/mellanox/mlx4/cq.c:371:
synchronize_irq(priv->eq_table.eq[MLX4_CQ_TO_EQ_VECTOR(cq->vector)].irq);
drivers/net/ethernet/mellanox/mlx4/cq.c:374:
synchronize_irq(priv->eq_table.eq[MLX4_EQ_ASYNC].irq);
drivers/net/ethernet/mellanox/mlx4/eq.c:1088: synchronize_irq(eq->irq);
--
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:[~2015-07-08 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 9:42 Mlx4: BUG: unable to handle kernel at ffffffffa02be210 Jack Wang
[not found] ` <CAD+HZHXi2bB59eWLYaGiXj5-b5w3V1NhwUJbSjx5NfdmhEaRhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-08 12:19 ` Or Gerlitz
[not found] ` <559D1562.2070309-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-07-08 12:47 ` Jack Wang
[not found] ` <CAD+HZHVCMa97zEQ1SB=JXCKHOGgSO93BPyLha2PDrOOTsHTUCw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-08 13:49 ` Or Gerlitz [this message]
[not found] ` <559D2A80.4040909-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-07-08 14:07 ` Jack Wang
[not found] ` <CAD+HZHWBn-KZCsskSGPKLtntj-LjDRodda9jngr+qcKSxLhkGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-08 18:22 ` Or Gerlitz
2015-07-09 11:14 ` Jack Wang
[not found] ` <CAD+HZHXcrejwu=dAhmL7vZ=tkAPswm2LiCgwK42kEe5XDvBvhQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-09 11:21 ` Or Gerlitz
[not found] ` <559E592D.5000201-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-07-09 13:35 ` Jack Wang
2015-07-09 13:57 ` Or Gerlitz
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=559D2A80.4040909@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=xjtuwjp-Re5JQEeQqe8AvxtiuMwx3w@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 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.