public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Honggang LI <honli@redhat.com>, Eric Dumazet <eric.dumazet@gmail.com>
Cc: roland@kernel.org, sean.hefty@intel.com,
	hal.rosenstock@gmail.com, kaber@trash.net, davem@davemloft.net,
	alex.estrin@intel.com, dledford@redhat.com, edumazet@google.com,
	erezsh@mellanox.com, maheshb@google.com, jbenc@redhat.com,
	ebiederm@xmission.com, elfring@users.sourceforge.net,
	f.fainelli@gmail.com, linux@roeck-us.net, andrew@lunn.ch,
	sfeldma@gmail.com, alexander.h.duyck@intel.com,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH linux-next 1/4] infiniband/ipoib: fix possible NULL pointer dereference in ipoib_get_iflink
Date: Tue, 14 Apr 2015 17:49:55 +0200	[thread overview]
Message-ID: <552D3723.9050706@6wind.com> (raw)
In-Reply-To: <20150414154422.GB21856@honli.nay.redhat.com>

Le 14/04/2015 17:44, Honggang LI a écrit :
> On Tue, Apr 14, 2015 at 08:34:33AM -0700, Eric Dumazet wrote:
>> On Tue, 2015-04-14 at 23:20 +0800, Honggang Li wrote:
>>> Starting monitoring for VG vg_rdma01:   3 logical volume(s) in volume
>>> group "vg_rdma01" monitored
>>> [  OK  ]
>>
>>
>>> CR2: 0000000000000120
>>> ---[ end trace a8610f6e9640eb85 ]---
>>>
>>> Signed-off-by: Honggang Li <honli@redhat.com>
>>
>> When was this bug added ?
>>
>
> Sorry, I do not know. I ran into this bug today when I'm tracing a race
> condition issue related qib. In order to check upstream linux-next fix
> the race condition or not, I build linux-next-20150414 on two machines. Both
> machines panic at modprobe ib_ipoib. Do you means I need to report a
> bug? But I do not know report to who or where.

Here is the tag:
Fixes: 5aa7add8f14b ("infiniband/ipoib: implement ndo_get_iflink")


  reply	other threads:[~2015-04-14 15:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 15:20 [PATCH linux-next 0/4] fix possile NULL pointer dereference in ndo_get_iflink callback functions Honggang Li
2015-04-14 15:20 ` [PATCH linux-next 1/4] infiniband/ipoib: fix possible NULL pointer dereference in ipoib_get_iflink Honggang Li
2015-04-14 15:34   ` Eric Dumazet
2015-04-14 15:44     ` Honggang LI
2015-04-14 15:49       ` Nicolas Dichtel [this message]
2015-04-14 15:53         ` Honggang LI
2015-04-14 16:14           ` Eric Dumazet
2015-04-14 16:01         ` Yann Droneaud
2015-04-14 16:44           ` Nicolas Dichtel
2015-04-14 16:30   ` Erez Shitrit
2015-04-14 16:46     ` Nicolas Dichtel
2015-04-14 20:41     ` Jason Gunthorpe
2015-04-15  5:24       ` Or Gerlitz
2015-04-15  6:17       ` Erez Shitrit
2015-04-15 16:06         ` Jason Gunthorpe
2015-04-16 11:27           ` Erez Shitrit
2015-04-15  5:16     ` Honggang LI
2015-04-15  6:57       ` Honggang LI
2015-04-14 15:20 ` [PATCH linux-next 2/4] ipvlan: fix possible NULL pointer dereference in ipvlan_get_iflink Honggang Li
2015-04-14 15:20 ` [PATCH linux-next 3/4] macvlan: fix possible NULL pointer dereference in macvlan_dev_get_iflink Honggang Li
2015-04-14 15:26   ` Patrick McHardy
2015-04-14 15:32     ` Honggang LI
2015-04-14 15:35       ` Patrick McHardy
2015-04-14 17:47       ` David Miller
2015-04-14 15:35     ` Nicolas Dichtel
2015-04-14 15:37       ` Andrew Lunn
2015-04-14 15:46         ` Honggang LI
2015-04-14 15:20 ` [PATCH linux-next 4/4] net/dsa: fix possible NULL pointer dereference in dsa_slave_get_iflink Honggang Li
2015-04-14 15:55   ` Guenter Roeck
2015-04-14 16:26 ` [PATCH linux-next v2] infiniband/ipoib: fix possible NULL pointer dereference in ipoib_get_iflink Honggang Li
2015-04-14 16:26   ` [PATCH] " Honggang Li

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=552D3723.9050706@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=alex.estrin@intel.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=edumazet@google.com \
    --cc=elfring@users.sourceforge.net \
    --cc=erezsh@mellanox.com \
    --cc=eric.dumazet@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=honli@redhat.com \
    --cc=jbenc@redhat.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=maheshb@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=roland@kernel.org \
    --cc=sean.hefty@intel.com \
    --cc=sfeldma@gmail.com \
    /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