From: "Jan Beulich" <JBeulich@novell.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [xen-4.0-testing test] 2045: regressions - FAIL
Date: Fri, 17 Sep 2010 15:09:49 +0100 [thread overview]
Message-ID: <4C9392CD02000078000176DC@vpn.id2.novell.com> (raw)
In-Reply-To: <1283267148.12544.9437.camel@zakaz.uk.xensource.com>
>>> On 31.08.10 at 17:05, Ian Campbell <Ian.Campbell@eu.citrix.com> wrote:
> On Tue, 2010-08-31 at 15:35 +0100, Ian Jackson wrote:
>>
>> > Even with the fix in place the gratuitous ARP behaviour is disabled
>> by
>> > default so you need to enable the net.ipv4.conf.<dev>.arp_notify
>> sysctl
>> > for any device you want to send the notifications. When I was
>> testing I
>> > did this by adding
>> > net.ipv4.conf.default.arp_notify = 1
>> > to /etc/sysctl.conf and that seemed to do the trick.
>>
>> I think this is a bug. I think the default should be for something to
>> send this gratuitous arp and the most logical answer in the PV or
>> PV-on-HVM case is the domU.
>
> This is the upstream default, not something we control directly from
> netfront etc.
Wouldn't it seem possible/reasonable to force this on from netfront
(via IN_DEV_CONF_SET()) at least until upstream possibly decides
to not let the ARP_NOTIFY sysctl control the sending of an ARP
explicitly requested through netif_notify_peers()?
The perhaps undesirable effect of this (as well as setting the sysctl
through /etc/sysctl.conf) is that it doesn't only control the ARP we
want sent, but also one when bringing the interface up or changing
its address, so I'd still favor moving the NETDEV_NOTIFY_PEERS
case past the "if (IN_DEV_ARP_NOTIFY(in_dev))" in inetdev_event().
Have you got any feedback from Linux folks on such a potential
change?
Jan
prev parent reply other threads:[~2010-09-17 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 14:21 [xen-4.0-testing test] 2045: regressions - FAIL xen.org
2010-08-25 15:40 ` Pasi Kärkkäinen
2010-08-25 18:25 ` Ian Jackson
2010-08-26 7:06 ` Ian Campbell
2010-08-31 14:35 ` Ian Jackson
2010-08-31 15:05 ` Ian Campbell
2010-08-31 15:10 ` Ian Jackson
2010-08-31 18:11 ` Ian Jackson
2010-08-31 18:49 ` Ian Campbell
2010-09-17 14:09 ` Jan Beulich [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=4C9392CD02000078000176DC@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).