From: "Luoshijie (Poincare Lab)" <luoshijie1@huawei.com>
To: David Miller <davem@davemloft.net>
Cc: <tgraf@suug.ch>, <dsahern@gmail.com>, <netdev@vger.kernel.org>,
<liuzhiqiang26@huawei.com>, <wangxiaogang3@huawei.com>,
<mingfangsen@huawei.com>, <zhoukang7@huawei.com>
Subject: Re: [PATCH v2 0/3] fix bugs when enable route_localnet
Date: Tue, 25 Jun 2019 09:50:27 +0800 [thread overview]
Message-ID: <4080e8ea-8e05-d0c7-8e4a-bab006bbb509@huawei.com> (raw)
In-Reply-To: <20190624.090325.163853495970223718.davem@davemloft.net>
On 2019/6/25 0:03, David Miller wrote:
> From: luoshijie <luoshijie1@huawei.com>
> Date: Tue, 18 Jun 2019 15:14:02 +0000
>
>> From: Shijie Luo <luoshijie1@huawei.com>
>>
>> When enable route_localnet, route of the 127/8 address is enabled.
>> But in some situations like arp_announce=2, ARP requests or reply
>> work abnormally.
>>
>> This patchset fix some bugs when enable route_localnet.
>>
>> Change History:
>> V2:
>> - Change a single patch to a patchset.
>> - Add bug fix for arp_ignore = 3.
>> - Add a couple of test for enabling route_localnet in selftests.
>
> Series applied to net-next, thanks.
>
Thanks a lot, and I'm truly grateful for advice and help of David Ahern.
prev parent reply other threads:[~2019-06-25 1:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 15:14 [PATCH v2 0/3] fix bugs when enable route_localnet luoshijie
2019-06-18 15:14 ` [PATCH v2 1/3] ipv4: fix inet_select_addr() " luoshijie
2019-06-18 15:14 ` [PATCH v2 2/3] ipv4: fix confirm_addr_indev() " luoshijie
2019-06-18 15:14 ` [PATCH v2 3/3] selftests: add route_localnet test script luoshijie
2019-06-22 8:41 ` [PATCH v2 0/3] fix bugs when enable route_localnet Zhiqiang Liu
2019-06-22 12:46 ` David Miller
2019-06-24 1:19 ` Zhiqiang Liu
2019-06-24 3:47 ` David Ahern
2019-06-24 16:03 ` David Miller
2019-06-25 1:25 ` Zhiqiang Liu
2019-06-25 1:50 ` Luoshijie (Poincare Lab) [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=4080e8ea-8e05-d0c7-8e4a-bab006bbb509@huawei.com \
--to=luoshijie1@huawei.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=liuzhiqiang26@huawei.com \
--cc=mingfangsen@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=wangxiaogang3@huawei.com \
--cc=zhoukang7@huawei.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).