From: David Miller <davem@davemloft.net>
To: synmyth@gmail.com
Cc: netdev@vger.kernel.org, mporter@kernel.crashing.org,
jj@chaosbits.net, cmdkhh@gmail.com
Subject: Re: [PATCH]rionet: fix NULL pointer dereference in rionet_remove
Date: Wed, 29 Jun 2011 05:57:59 -0700 (PDT) [thread overview]
Message-ID: <20110629.055759.1556521651128595877.davem@davemloft.net> (raw)
In-Reply-To: <4e098bf5.87f62a0a.4c71.571a@mx.google.com>
From: Yinglin Luan <synmyth@gmail.com>
Date: Sun, 26 Jun 2011 12:12:12 +0800
> Function rionet_remove initializes local variable 'ndev' to NULL
> and do nothing changes before the call to unregister_netdev(ndev),
> this could cause a NULL pointer dereference.
>
> Reported-by: Jesper Juhl <jj@chaosbits.net>
> Signed-off-by: Yinglin Luan <synmyth@gmail.com>
Applied.
next prev parent reply other threads:[~2011-06-29 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 4:12 [PATCH]rionet: fix NULL pointer dereference in rionet_remove Yinglin Luan
2011-06-29 12:57 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-18 15:27 Yinglin Luan
2011-06-20 5:44 ` David Miller
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=20110629.055759.1556521651128595877.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cmdkhh@gmail.com \
--cc=jj@chaosbits.net \
--cc=mporter@kernel.crashing.org \
--cc=netdev@vger.kernel.org \
--cc=synmyth@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;
as well as URLs for NNTP newsgroup(s).