On Fri, Jun 09, 2017 at 01:15:10PM -0400, David Miller wrote:
> From: Krister Johansen
> Date: Fri, 9 Jun 2017 10:13:10 -0700
>
> > On Fri, Jun 09, 2017 at 12:26:46PM -0400, David Miller wrote:
> >> From: Krister Johansen
> >> Date: Thu, 8 Jun 2017 13:12:14 -0700
> >>
> >> > The ipvlan code alr
From: Krister Johansen
Date: Fri, 9 Jun 2017 10:13:10 -0700
> On Fri, Jun 09, 2017 at 12:26:46PM -0400, David Miller wrote:
>> From: Krister Johansen
>> Date: Thu, 8 Jun 2017 13:12:14 -0700
>>
>> > The ipvlan code already knows how to detect when a duplicate address is
>> > about to be assigned
On Fri, Jun 09, 2017 at 12:26:46PM -0400, David Miller wrote:
> From: Krister Johansen
> Date: Thu, 8 Jun 2017 13:12:14 -0700
>
> > The ipvlan code already knows how to detect when a duplicate address is
> > about to be assigned to an ipvlan device. However, that failure is not
> > propogated ou
From: Krister Johansen
Date: Thu, 8 Jun 2017 13:12:14 -0700
> The ipvlan code already knows how to detect when a duplicate address is
> about to be assigned to an ipvlan device. However, that failure is not
> propogated outward and leads to a silent failure.
>
> Introduce a validation step at i
The ipvlan code already knows how to detect when a duplicate address is
about to be assigned to an ipvlan device. However, that failure is not
propogated outward and leads to a silent failure.
Introduce a validation step at ip address creation time and allow device
drivers to register to validate
