Re: size bugs

2004-02-20 Thread Colin Percival
At 01:48 20/02/2004, Ted Unangst wrote: A few final bugs from Coverity. Most of these are off by one, the RF bug is malloc'ing the wrong type. One false alarm here -- the first netinet6 report, since the line of code in question is never executed with bytelen==16 -- but I've got patches for thre

Re: Size-independent byte order swapping functions.

2003-11-25 Thread Pawel Jakub Dawidek
On Mon, Nov 24, 2003 at 05:13:08PM -0800, David Schultz wrote: +> On Mon, Nov 24, 2003, Pawel Jakub Dawidek wrote: +> > If one is using strictly defined types as uint8_t, uint16_t, int32_t, etc. +> > those macros are helpful IMHO, because futher value size changes does not +> > affects code for byt

Re: Size-independent byte order swapping functions.

2003-11-25 Thread Mark Murray
David Schultz writes: > > I'm not sure if dedicated epanic() is the best way to implement out-of-rang > e > > errors prevention - the more handy solution should cause compile error. > > See CTASSERT. There is an extremely limited number of sizes that are possible here, even with weird/theoretical

Re: Size-independent byte order swapping functions.

2003-11-24 Thread David Schultz
On Mon, Nov 24, 2003, Pawel Jakub Dawidek wrote: > If one is using strictly defined types as uint8_t, uint16_t, int32_t, etc. > those macros are helpful IMHO, because futher value size changes does not > affects code for byte order managing. This also does not hit perfromance, > because this should

Re: size

2001-11-25 Thread Leo Bicknell
On Sun, Nov 25, 2001 at 11:07:58AM -0500, we'uns wrote: > Greetings. I got this email address out of the FreeBSD Newsletter, > issue#1. I'm not sure if you're the right guys to address such a > query to so if this seems out of place I apologize, but perhaps > you can direct it to the right folks.

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-10 Thread Graham Wheeler
Graham Wheeler wrote: > > David Malone wrote: > > > > If you read the paragraph below that code, it notes that the ifreq > > structures are of variable length. The spacing depends on the size > > of the returned info. > > That's true. In which case the cheops code is wrong, as it iterates > thro

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread Dennis
At 10:51 AM 01/09/2001, David Malone wrote: > > Marko - does Linux have getifaddrs()? I somehow doubt it... > >Linux should have getifaddrs() if it has support for IPv6 in >userland libraries. There is an implimentation of it at: > > http://www.linux-ipv6.org/cvsweb/libinet6/?cvsroot=usagi

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread Mike E. Matsnev
On Tue, Jan 09, 2001 at 03:39:22PM +0200, Graham Wheeler wrote: > David Malone wrote: > > > > If you read the paragraph below that code, it notes that the ifreq > > structures are of variable length. The spacing depends on the size > > of the returned info. > > That's true. In which case the che

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread David Malone
> Marko - does Linux have getifaddrs()? I somehow doubt it... Linux should have getifaddrs() if it has support for IPv6 in userland libraries. There is an implimentation of it at: http://www.linux-ipv6.org/cvsweb/libinet6/?cvsroot=usagi-libc David. To Unsubscribe: send mail to [EMAIL

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread David Malone
> Something that isn't clear to me - do you know (Mark for Linux, Dave or > someone else for FreeBSD) whether it is reasonable to assume the > ifr_name if the struct ifreq will be NUL terminated? I know that the > name in a struct sockaddr_dl is not necessarily so terminated, but for > the ifr_nam

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread Graham Wheeler
David Malone wrote: > > If you read the paragraph below that code, it notes that the ifreq > structures are of variable length. The spacing depends on the size > of the returned info. > > David. Something that isn't clear to me - do you know (Mark for Linux, Dave or someone else for Fre

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread Graham Wheeler
David Malone wrote: > > If you read the paragraph below that code, it notes that the ifreq > structures are of variable length. The spacing depends on the size > of the returned info. That's true. In which case the cheops code is wrong, as it iterates through the list by incrementing a pointer t

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread Graham Wheeler
David Malone wrote: > > On Tue, Jan 09, 2001 at 12:21:11PM +0200, Graham Wheeler wrote: > > > I am attempting to port the cheops network mapping/diagnostic program > > from Linux to FreeBSD (see www.marko.net/cheops). One of the first snags > > I have hit comes in using SIOCGIFCONF to queries th

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread David Malone
On Tue, Jan 09, 2001 at 12:30:44PM +0200, Graham Wheeler wrote: > Just a follow up on this: on Stevens vol 2 pg 117, code line 299, is the > implication that the returned buffer DOES hold an array of struct ifreq > elements. So this does seem to indicate that something may be broken on > FreeBSD.

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread David Malone
On Tue, Jan 09, 2001 at 12:21:11PM +0200, Graham Wheeler wrote: > I am attempting to port the cheops network mapping/diagnostic program > from Linux to FreeBSD (see www.marko.net/cheops). One of the first snags > I have hit comes in using SIOCGIFCONF to queries the network interface > names and a

Re: Size of struct ifreq/returned buffer of SIOCGIFCONF

2001-01-09 Thread Graham Wheeler
Just a follow up on this: on Stevens vol 2 pg 117, code line 299, is the implication that the returned buffer DOES hold an array of struct ifreq elements. So this does seem to indicate that something may be broken on FreeBSD. At the very least there is some ambiguity - is this an array of struct i

Re: Size limits for kld's?

2000-08-25 Thread Mike Smith
> Unfortunately, while the open and close functions I wrote are called > correctly, the ioctl function is never called. A call to ioctl(filehdl, > PLEX86_IOCTL, int) returns an error, and a perror("ioctl") prints > "ioctl: Bad Address." I know that the ioctl number is correct, and it > was defin

Re: Size of arp database.

1999-10-20 Thread Wiktor
On Tue, 19 Oct 1999, Ruslan Ermilov wrote: > This is because none of your ethernet interfaces matches `pc7'. > > 1/ What does `route -n -v get -host pc7' show? bash-2.02# route -n -v get -host pc7 u: inet 195.117.4.106; u: link ; RTM_GET: Report Metrics: len 128, pid: 0, seq 1 , errno 0, flags: l

Re: Size of arp database.

1999-10-19 Thread Ruslan Ermilov
On Tue, Oct 19, 1999 at 07:06:43PM +0200, Wiktor wrote: [...] > What i tested is: > root@wotan:~# arp -S pc7 00:00:E8:73:FF:FD pub > delete: can't locate pc7 > root@wotan:~# arp -a > router (195.117.4.97) at 0:a0:c5:21:14:8 > wotan.2slo.waw.pl (195.117.4.98) at 0:10:4b:36:6a:fd permanent > pc2 (19

Re: Size of arp database.

1999-10-19 Thread Wiktor
On Tue, 19 Oct 1999, Dan Nelson wrote: > In the last episode (Oct 19), Wiktor said: > > Is there any way to enlarge the arp database. I've got a feeling that > > it is limited to only 10 enteries... For me it's a bit to less. > > $ arp -a | wc -l > 256 > > Maybe you only have 10 machines on you

Re: Size of arp database.

1999-10-19 Thread Wiktor
On Tue, 19 Oct 1999, Dan Nelson wrote: > In the last episode (Oct 19), Wiktor said: > > Is there any way to enlarge the arp database. I've got a feeling that > > it is limited to only 10 enteries... For me it's a bit to less. > > $ arp -a | wc -l > 256 > > Maybe you only have 10 machines on you

Re: Size of arp database.

1999-10-19 Thread Dan Nelson
In the last episode (Oct 19), Wiktor said: > Is there any way to enlarge the arp database. I've got a feeling that > it is limited to only 10 enteries... For me it's a bit to less. $ arp -a | wc -l 256 Maybe you only have 10 machines on your network? -- Dan Nelson [EMAIL PROTEC