From: David Miller <davem@davemloft.net>
To: ja@ssi.bg
Cc: netdev@vger.kernel.org, shmulik.ladkani@gmail.com
Subject: Re: [PATCH net] ipv4: mask tos for input route
Date: Sun, 26 Feb 2017 11:05:11 -0500 (EST) [thread overview]
Message-ID: <20170226.110511.987468399452857466.davem@davemloft.net> (raw)
In-Reply-To: <1488122075-23952-1-git-send-email-ja@ssi.bg>
From: Julian Anastasov <ja@ssi.bg>
Date: Sun, 26 Feb 2017 17:14:35 +0200
> Restore the lost masking of TOS in input route code to
> allow ip rules to match it properly.
>
> Problem [1] noticed by Shmulik Ladkani <shmulik.ladkani@gmail.com>
>
> [1] http://marc.info/?t=137331755300040&r=1&w=2
>
> Fixes: 89aef8921bfb ("ipv4: Delete routing cache.")
> Signed-off-by: Julian Anastasov <ja@ssi.bg>
Our TOS handling in the routing code is certainly more subtle than it
needs to be.
Applied and queued up for -stable.
prev parent reply other threads:[~2017-02-26 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 15:14 [PATCH net] ipv4: mask tos for input route Julian Anastasov
2017-02-26 16:05 ` 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=20170226.110511.987468399452857466.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ja@ssi.bg \
--cc=netdev@vger.kernel.org \
--cc=shmulik.ladkani@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).