From: David Miller <davem@davemloft.net>
To: roy.qing.li@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: Set default hoplimit as zero.
Date: Wed, 24 Oct 2012 23:15:11 -0400 (EDT) [thread overview]
Message-ID: <20121024.231511.97424602338053960.davem@davemloft.net> (raw)
In-Reply-To: <1351058478-29252-1-git-send-email-roy.qing.li@gmail.com>
From: roy.qing.li@gmail.com
Date: Wed, 24 Oct 2012 14:01:18 +0800
> From: Li RongQing <roy.qing.li@gmail.com>
>
> Commit a02e4b7dae4551(Demark default hoplimit as zero) only changes the
> hoplimit checking condition and default value in ip6_dst_hoplimit, not
> zeros all hoplimit default value.
>
> Keep the zeroing ip6_template_metrics[RTAX_HOPLIMIT - 1] to force it as
> const, cause as a37e6e344910(net: force dst_default_metrics to const
> section)
>
> Signed-off-by: Li RongQing <roy.qing.li@gmail.com>
This bug has existed in various forms, thanks for fixing these
cases too. (f.e. see e965c05dabdabb85af0187952ccd75e43995c4b3)
Applied and queued up for -stable.
prev parent reply other threads:[~2012-10-25 3:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 6:01 [PATCH] ipv6: Set default hoplimit as zero roy.qing.li
2012-10-25 3:15 ` 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=20121024.231511.97424602338053960.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roy.qing.li@gmail.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).