On Dec 29, 2012, at 10:56 PM, Christos Zoulas chris...@netbsd.org wrote:
Always call brelse() on error. Otherwise a possible error from bread() will
cause the buffer to stay lock and we end up blocking forever in
VOP_CLOSE-spec_close-vinvalbuf-bbysy since the buffer is marked busy
but there
On Sun, 30 Dec 2012 09:45:05 +
Michael Lorenz macal...@netbsd.org wrote:
Module Name: src
Committed By: macallan
Date: Sun Dec 30 09:45:05 UTC 2012
Modified Files:
src/sys/dev/pci: radeonfb.c radeonfbreg.h
Log Message:
Add support for R3xx.
Whi
EFATFINGERS, fixed
3. Always send ICMP_MINLEN packets; this is what everyone else does. Makes
ping -s n where n 8 work.
Shouldn't that be an error? Otherwise people will think that something
is happening when it isn't.
pgpsqNepA4SMC.pgp
Description: PGP signature
On Dec 30, 10:21am, hann...@eis.cs.tu-bs.de (J. Hannken-Illjes) wrote:
-- Subject: Re: CVS commit: src/sys/kern
| Thanks. Just applied the same to breadn().
Heh, I missed that!
Thanks,
christos
On Dec 30, 7:53am, g...@ir.bbn.com (Greg Troxel) wrote:
-- Subject: Re: CVS commit: src/sbin/ping
| 3. Always send ICMP_MINLEN packets; this is what everyone else does. Makes
| ping -s n where n 8 work.
|
| Shouldn't that be an error? Otherwise people will think that something
| is
On Sun, 30 Dec 2012 10:50:07 -0500
chris...@zoulas.com (Christos Zoulas) wrote:
netbsd-old
PING localhost (127.0.0.1): 1 data bytes
[no response]
Not that old, though; it has worked in the past:
box2$ uname -r
5.1_STABLE
box2$ ping -c 1 -s 1 localhost
PING localhost (127.0.0.1):
In article 20121230173516.ab058f88b94567154810b...@pandora.be,
dieter roelants dieter.net...@pandora.be wrote:
On Sun, 30 Dec 2012 10:50:07 -0500
chris...@zoulas.com (Christos Zoulas) wrote:
netbsd-old
PING localhost (127.0.0.1): 1 data bytes
[no response]
Not that old, though; it has worked
On Sun, Dec 30, 2012 at 05:36:00PM +, David A. Holland wrote:
Module Name: src
Committed By: dholland
Date: Sun Dec 30 17:36:00 UTC 2012
Modified Files:
src/lib/libutil: efun.c
Log Message:
If malloc, calloc, or realloc returns NULL when a size of 0 was
requested,
On Sun, Dec 30, 2012 at 08:16:59PM +, David Laight wrote:
Module Name: src
Committed By: dsl
Date: Sun Dec 30 20:16:59 UTC 2012
Modified Files:
src/external/gpl3/gcc/dist/gcc/config/i386: i386.c
Log Message:
No need to check both TARGET_64BIT and
On Mon, Dec 31, 2012 at 02:59:13AM +0100, Joerg Sonnenberger wrote:
Modified Files:
src/lib/libutil: efun.c
Log Message:
If malloc, calloc, or realloc returns NULL when a size of 0 was
requested, which is allowed by pertinent standards, honor it instead
of bombing.
On Mon, 31 Dec 2012, Joerg Sonnenberger wrote:
Log Message:
If malloc, calloc, or realloc returns NULL when a size of 0 was
requested, which is allowed by pertinent standards, honor it instead
of bombing.
Do not do this for calloc(x, y) where x != 0 y != 0 but x*y == 0;
in that case bomb.
11 matches
Mail list logo
