From: Dave Jones <davej@redhat.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH v2] can: add missing socket check in can/raw release
Date: Wed, 20 Apr 2011 13:03:34 -0400 [thread overview]
Message-ID: <20110420170333.GD24930@redhat.com> (raw)
In-Reply-To: <4DAECA1B.5050300@hartkopp.net>
On Wed, Apr 20, 2011 at 01:57:15PM +0200, Oliver Hartkopp wrote:
> v2: added space after 'if' according code style.
>
> We can get here with a NULL socket argument passed from userspace,
> so we need to handle it accordingly.
>
> Thanks to Dave Jones pointing at this issue in net/can/bcm.c
>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
ACK. That was the first thing I hit this morning ;-)
Dave
next prev parent reply other threads:[~2011-04-20 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 11:57 [PATCH v2] can: add missing socket check in can/raw release Oliver Hartkopp
2011-04-20 17:03 ` Dave Jones [this message]
2011-04-20 19:22 ` 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=20110420170333.GD24930@redhat.com \
--to=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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).