From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: jasowang@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, gregkh@suse.de, stable@kernel.org,
mst@redhat.com, akong@redhat.com
Subject: Re: Possible NULL dereference caused by -stable commit ef81bb40bf15f350fe865f31fa42f1082772a576
Date: Wed, 28 Sep 2011 13:12:42 -0400 (EDT) [thread overview]
Message-ID: <20110928.131242.1368255500458954764.davem@davemloft.net> (raw)
In-Reply-To: <1317211749.2941.6.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 28 Sep 2011 14:09:09 +0200
> All we need here is not the route but inet_peer, so that inet_getid()
> can be called on it.
It's not exactly that simple, you have to parse all hop-by-hop options
to get the correct "destination" address.
next prev parent reply other threads:[~2011-09-28 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 10:51 Possible NULL dereference caused by -stable commit ef81bb40bf15f350fe865f31fa42f1082772a576 Jason Wang
2011-09-28 12:09 ` Eric Dumazet
2011-09-28 17:12 ` David Miller [this message]
2011-09-28 18:32 ` 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=20110928.131242.1368255500458954764.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akong@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=gregkh@suse.de \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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).