From: David Miller <davem@davemloft.net>
To: idosch@mellanox.com
Cc: netdev@vger.kernel.org, dsahern@gmail.com, mlxsw@mellanox.com,
wenxu@ucloud.cn
Subject: Re: [PATCH net-next] net: ipv4: Fix NULL pointer dereference in route lookup
Date: Sat, 02 Mar 2019 00:42:42 -0800 (PST) [thread overview]
Message-ID: <20190302.004242.1745996281205103666.davem@davemloft.net> (raw)
In-Reply-To: <20190301133810.8107-1-idosch@mellanox.com>
From: Ido Schimmel <idosch@mellanox.com>
Date: Fri, 1 Mar 2019 13:38:43 +0000
> When calculating the multipath hash for input routes the flow info is
> not available and therefore should not be used.
>
> Fixes: 24ba14406c5c ("route: Add multipath_hash in flowi_common to make user-define hash")
> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Applied.
prev parent reply other threads:[~2019-03-02 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 13:38 [PATCH net-next] net: ipv4: Fix NULL pointer dereference in route lookup Ido Schimmel
2019-03-01 14:36 ` wenxu
2019-03-01 18:32 ` Nikolay Aleksandrov
2019-03-02 8:42 ` 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=20190302.004242.1745996281205103666.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=wenxu@ucloud.cn \
/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).