| To: | Matt Domsch <Matt_Domsch@xxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 2.6] dev.c: clear SIOCGIFHWADDR buffer if !dev->addr_len |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 30 Oct 2004 15:10:19 -0400 |
| Cc: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <20041030030936.GA25102@xxxxxxxxxxxxxxxxx> |
| Organization: | jamalopolous |
| References: | <20041030013700.GA21540@xxxxxxxxxxxxxxxxx> <E1CNiOT-0008GU-00@xxxxxxxxxxxxxxxxxxxxxxxx> <20041030030936.GA25102@xxxxxxxxxxxxxxxxx> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 2004-10-29 at 23:09, Matt Domsch wrote: > On Sat, Oct 30, 2004 at 11:51:01AM +1000, Herbert Xu wrote: > > > s/dev_addr/addr_len in the comments above, that's the field we care > > > about being non-zero. > > > > This still doesn't make sense. What if dev->addr_len is less than the > > size of the buffer? The caller has to know what the length is anyway. > > Ahh, indeed. net-snmp has hard-coded the number 6 or uses the > definition of IFHWADDRLEN (from include/linux/if.h, a copy of which is > in /usr/include/linux/if.h of course) in several places for this. fix the net-snmp code. The addr_len is dependent on the device type. 6 is good for ethernet but may not equate for others. Having said that i think we should somehow signal that info to user space. perhaps returning -EINVAL in the case the L2 address is 0? EINVAL will break a few apps and make them puke as opposed to silently returning something wrong. cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] WOL for sis900, Daniele Venzano |
|---|---|
| Next by Date: | Re: Asynchronous crypto layer., James Morris |
| Previous by Thread: | Re: [PATCH 2.6] dev.c: clear SIOCGIFHWADDR buffer if !dev->addr_len, Matt Domsch |
| Next by Thread: | Re: [PATCH 2.6] dev.c: clear SIOCGIFHWADDR buffer if !dev->addr_len, Matt Domsch |
| Indexes: | [Date] [Thread] [Top] [All Lists] |