This is the first pass of mallocarray() in sys/dev. Please proofread.
Index: rd.c
===
RCS file: /cvs/src/sys/dev/rd.c,v
retrieving revision 1.7
diff -u -p -u -r1.7 rd.c
--- rd.c12 Jul 2014 18:48:51 - 1.7
+++ rd.c
We are sorry that the errata for these libssl security issues are not
up yet.
The majority of these issues are in our ssl library as well.
Most other operating system vendors have patches available, but that
is because they were (obviously) given a heads up to prepare them over
the last few
Small demonstration of the kinds of things we'll have to mop up for
weeks more.
From OpenSSL CHANGES file:
*) Introduce safe string copy and catenation functions
(BUF_strlcpy() and BUF_strlcat()).
[Ben Laurie (CHATS) and Richard Levitte]
That's from back in 2002.
These functions
I would like to thank the members of the community who deliver four
vax machines to the project.
Vax builds have started again!
Looking at ATI resume, I pushed Mark to explore using DVACT_WAKEUP instead,
because the code looks super hairy and might sleep...
The same applies to Intel.
Since there are many more people who rely on such machines, can we get
some test reports of this on all machines, for suspend/resume and
From time to time, there are people who say that strlcpy and strlcat
are stupid.
This is a little frustrating because we just want developers to have
an easier time writing/auditing string code to avoid overflows and
truncations, especially considering so many standard C APIs require
fixed length
libkvm already figures out the pagesize of the machine in _kvm_open(),
and then allows the machine-dependent _kvm_initvtop() to override it
if need be (thereby, handling sparc). Thus we can avoid the PAGE_SIZE,
PAGE_SHIFT, ... variables.
Seems to be working ... wonder if I missed some relevant
