From: Alexey Dobriyan <adobriyan@gmail.com>
To: jslaby@suse.cz
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] NET: ipv6, fix potential null dereference
Date: Sun, 10 Jan 2010 12:35:29 +0200 [thread overview]
Message-ID: <20100110103528.GA4769@x200> (raw)
> Stanse found a potential null dereference
Nobody learns from Coverity, it seems. :^)
snmp6_unregister_dev() always called with valid idev.
next reply other threads:[~2010-01-10 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 10:35 Alexey Dobriyan [this message]
2010-01-10 10:38 ` [PATCH 1/1] NET: ipv6, fix potential null dereference Jiri Slaby
2010-01-10 10:47 ` Alexey Dobriyan
2010-01-10 11:05 ` Jiri Slaby
2010-01-10 11:37 ` Jiri Slaby
2010-01-10 10:43 ` [PATCH 1/1] NET: ipv6, remove unnecessary check Jiri Slaby
2010-01-10 21:28 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2010-01-10 9:06 [PATCH 1/1] NET: ipv6, fix potential null dereference Jiri Slaby
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=20100110103528.GA4769@x200 \
--to=adobriyan@gmail.com \
--cc=jslaby@suse.cz \
--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 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.