fixes panic on attach/detach due to free list corruption, also use
after usbd_free_xfer(), tested on i386
~~~
Index: uow.c
===
RCS file: /cvs/src/sys/dev/usb/uow.c,v
retrieving revision 1.33
diff -u -p -s -r1.33 uow.c
--- uow.c
> just saw that cat's *main* function does never return even though there is a
> return value,
> exit(3) is called instead.
> Is there any reason why or is it just historically, cause it's a bit
> confusing?
> If exit(3) is always called, than why not changing the return value to *void*?
>
> Oth
On Sun, Aug 30, 2015 at 12:10:03AM +0200, Fritjof Bornebusch wrote:
> If exit(3) is always called, than why not changing the return value to *void*?
Because ISO C says that in non-freestanding environment, main should
retutrn int.
Joerg
> From: Theo de Raadt
> Date: Sat, 29 Aug 2015 16:19:25 -0600
>
> * pool_allocator_multi_ni: A multi page allocator that is *not* safe
> for use in interrupts. Also less efficient than
> pool_allocator_single. It allocates kva from kernel_map, which is
> significantly more plentyful
Mark Kettenis wrote:
> This diff is purely mechanical. This means that it also changes some
> pool_allocator_nointr into pool_allocator_single where the intention
> was to signal that the pool would never be used in interrupt context.
> However, using pool_allocator_single in those cases isn't a b
* pool_allocator_multi_ni: A multi page allocator that is *not* safe
for use in interrupts. Also less efficient than
pool_allocator_single. It allocates kva from kernel_map, which is
significantly more plentyful.
We are the knights who say non-interruptable. Honestly, "ni" feels
a b
Hi,
just saw that cat's *main* function does never return even though there is a
return value,
exit(3) is called instead.
Is there any reason why or is it just historically, cause it's a bit confusing?
If exit(3) is always called, than why not changing the return value to *void*?
Other calls in
So whe have this "default" pool allocator called
"pool_allocator_nointr", which is perfectly safe to be used in
interrupt context. That always confuses the hell out of me. So here
is a diff that gives the allocators more sensible names. With this
change we have:
* pool_allocator_single: A singl
On 2015-08-29 06:05, Steven McDonald wrote:
I think chmod fits in the "cannot be tamed" category. tame(2) says of
chmod(2) and friends:
Setuid/setgid bits do not work, nor can the user or group be
changed on a file.
This breaks 'chmod u+s'.
I ran into this when building Xenocara.
Al
On Fri, Aug 28, 2015 at 07:53:23PM +0200, Alexander Bluhm wrote:
> On Fri, Aug 28, 2015 at 06:11:02PM +0200, Alexander Bluhm wrote:
> > The +host feature allows to select log messages from a specific
> > host. Normally syslogd does a reverse lookup on the sender's
> > address. If that fails or if
On 08/29/2015 01:13 PM, Alexandr Shadchin wrote:
On Fri, Aug 28, 2015 at 10:04:51PM +0200, Ulf Brosziewski wrote:
Some weeks ago a change was made in pms to support Synaptics touchpads
that don't provide W mode. I assume that only fairly old models are
concerned, and that the variant in the pat
The dwc2 driver uses too small FIFOs on Octeon. Because of this, the
USB controller can hammer the CPU with an immense flood of interrupts.
A rate of over 50,000 interrupts per second is not uncommon under
IO load.
The adjusted sizes below are from NetBSD. Those might not be the
optimum ones, but
On Sat, 29 Aug 2015 21:48:34 +1000
Steven McDonald wrote:
> Index: lib/libutil/opendev.c
> ===
> RCS file: /cvs/src/lib/libutil/opendev.c,v
> retrieving revision 1.15
> diff -u -p -r1.15 opendev.c
> --- lib/libutil/opendev.c 30 J
Same diff, corrected formatting. Sorry for the noise.
Index: lib/libutil/opendev.3
===
RCS file: /cvs/src/lib/libutil/opendev.3,v
retrieving revision 1.22
diff -u -p -r1.22 opendev.3
--- lib/libutil/opendev.3 15 Jan 2015 19:06:3
Same diff, corrected formatting. Sorry for the noise.
Index: lib/libutil/opendev.c
===
RCS file: /cvs/src/lib/libutil/opendev.c,v
retrieving revision 1.15
diff -u -p -r1.15 opendev.c
--- lib/libutil/opendev.c 30 Jun 2011 15:04:5
Sorry, my terminal seems to be mangling tabs into spaces. Here's a
properly copypasted diff:
Index: bin/chmod/chmod.c
===
RCS file: /cvs/src/bin/chmod/chmod.c,v
retrieving revision 1.34
diff -u -p -r1.34 chmod.c
--- bin/chmod/chmod.c
On Fri, Aug 28, 2015 at 10:04:51PM +0200, Ulf Brosziewski wrote:
>
> Some weeks ago a change was made in pms to support Synaptics touchpads
> that don't provide W mode. I assume that only fairly old models are
> concerned, and that the variant in the patch below is more accurate. It
> only fakes W
On 2015/08/29 13:25, Nathanael Rensen wrote:
> I use dhcpd(8) to boot some boxes with PXELINUX. The numbered options work
> but dhcpd.conf(5) is easier to maintain with names. These options are
> defined in RFC 5071.
I think this makes sense, any OKs? Ken?
It would also want an faq/current.html e
Hi Theo,
I think chmod fits in the "cannot be tamed" category. tame(2) says of
chmod(2) and friends:
Setuid/setgid bits do not work, nor can the user or group be
changed on a file.
This breaks 'chmod u+s'. It might be possible to tame only if it looks
like a mode is being set which is al
19 matches
Mail list logo
