netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: michael-dev@fami-braun.de, netdev@vger.kernel.org
Subject: Re: [PATCH] BUG: unable to handle kernel NULL pointer dereference at br_multicast_leave_group
Date: Mon, 15 Mar 2010 20:38:33 -0700 (PDT)	[thread overview]
Message-ID: <20100315.203833.165440357.davem@davemloft.net> (raw)
In-Reply-To: <20100316031005.GA17727@gondor.apana.org.au>

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Tue, 16 Mar 2010 11:10:05 +0800

> michael-dev@fami-braun.de wrote:
>> 
>> I'm currently using linux-next and have been running into an OOPs which
>> I think might be caused by a patch you submitted on 2010-02-27.
>> 
>> It's a linux-next kernel from 2010-03-12 on an x86 system and it
>> OOPs in the bridge module in br_mdp_ip_get (called by
>> br_multicast_leave_group) because the br->mdb is null.
> 
> Thanks, there's actually another spot (the query handler) where
> the same thing can happen.
> 
> Here's a patch to fix them both.
> 
> bridge: Move NULL mdb check into br_mdb_ip_get
> 
> Since all callers of br_mdb_ip_get need to check whether the
> hash table is NULL, this patch moves the check into the function.
> 
> This fixes the two callers (query/leave handler) that didn't
> check it.
> 
> Reported-by: Michael Braun <michael-dev@fami-braun.de>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

Applied, thanks Herbert.

      reply	other threads:[~2010-03-16  3:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14  2:28 [PATCH] BUG: unable to handle kernel NULL pointer dereference at br_multicast_leave_group michael-dev
2010-03-16  3:10 ` Herbert Xu
2010-03-16  3:38   ` David Miller [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=20100315.203833.165440357.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=michael-dev@fami-braun.de \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).