[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m18x6sm6mk.fsf@ebiederm.dsl.xmission.com>
Date: Thu, 27 Sep 2007 10:10:27 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Daniel Lezcano <dlezcano@...ibm.com>
Cc: David Miller <davem@...emloft.net>,
Linux Containers <containers@...ts.osdl.org>,
netdev@...r.kernel.org, urs@...ogud.escape.de
Subject: Re: [PATCH 3/4] net ipv4: When possible test for IFF_LOOPBACK and not dev == loopback_dev
Daniel Lezcano <dlezcano@...ibm.com> writes:
> Eric W. Biederman wrote:
>> Now that multiple loopback devices are becoming possible it makes
>> the code a little cleaner and more maintainable to test if a deivice
>> is th a loopback device by testing dev->flags & IFF_LOOPBACK instead
>> of dev == loopback_dev.
>>
>> Signed-off-by: Eric W. Biederman <ebiederm@...ssion.com>
>
>
> Urs Thuermann posted the patch:
>
> [PATCH 5/7] CAN: Add virtual CAN netdevice driver
>
> This network driver set its flag to IFF_LOOPBACK for testing.
> Is it possible this can be a collision with your patch ?
I have brought it up on that thread. As best as I tell the CAN usage
of IFF_LOOPBACK will be a problem even without my patch. Assuming
something other then the CAN layer will see the CAN devices.
The CAN documentations IFF_LOOPBACK should be set on all CAN devices.
It seems that the people who want high performance predictable CAN
don't want this and the people who want something they can trace
easily want this.
It sounds to me like CAN routers don't exist.
Anyway hopefully that usage can be resolved as that code is reviewed,
and made ready to merge.
Eric
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists