From: David Miller <davem@davemloft.net>
To: pabeni@redhat.com
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, hannes@stressinduktion.org
Subject: Re: [PATCH net] net/route: enforce hoplimit max value
Date: Sat, 14 May 2016 15:34:55 -0400 (EDT) [thread overview]
Message-ID: <20160514.153455.805172777482220210.davem@davemloft.net> (raw)
In-Reply-To: <4a951826f558b10f62ce4338cb2620b6fc886ba5.1463154659.git.pabeni@redhat.com>
From: Paolo Abeni <pabeni@redhat.com>
Date: Fri, 13 May 2016 18:33:41 +0200
> Currently, when creating or updating a route, no check is performed
> in both ipv4 and ipv6 code to the hoplimit value.
>
> The caller can i.e. set hoplimit to 256, and when such route will
> be used, packets will be sent with hoplimit/ttl equal to 0.
>
> This commit adds checks for the RTAX_HOPLIMIT value, in both ipv4
> ipv6 route code, substituting any value greater than 255 with 255.
>
> This is consistent with what is currently done for ADVMSS and MTU
> in the ipv4 code.
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Applied, thanks for fixing this.
prev parent reply other threads:[~2016-05-14 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 16:33 [PATCH net] net/route: enforce hoplimit max value Paolo Abeni
2016-05-14 19:34 ` 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=20160514.153455.805172777482220210.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).