From: David Miller <davem@davemloft.net>
To: sasha.levin@oracle.com
Cc: linux-kernel@vger.kernel.org, ying.xue@windriver.com,
Tero.Aho@coriant.com, jon.maloy@ericsson.com,
allan.stephens@windriver.com, netdev@vger.kernel.org,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH] tipc: correctly handle releasing a not fully initialized sock
Date: Tue, 13 Jan 2015 17:25:23 -0500 (EST) [thread overview]
Message-ID: <20150113.172523.1612644763021758959.davem@davemloft.net> (raw)
In-Reply-To: <1421171201-25224-1-git-send-email-sasha.levin@oracle.com>
From: Sasha Levin <sasha.levin@oracle.com>
Date: Tue, 13 Jan 2015 12:46:41 -0500
> Commit "tipc: make tipc node table aware of net namespace" has added a
> dereference of sock->sk before making sure it's not NULL, which makes
> releasing a tipc socket NULL pointer dereference for sockets that are
> not fully initialized.
>
> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Good catch, applied, thanks.
prev parent reply other threads:[~2015-01-13 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 17:46 [PATCH] tipc: correctly handle releasing a not fully initialized sock Sasha Levin
2015-01-13 22:25 ` 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=20150113.172523.1612644763021758959.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Tero.Aho@coriant.com \
--cc=allan.stephens@windriver.com \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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).