Re: midiplay: Fix out-of-bounds memory access

On Wed, Apr 27, 2016 at 07:49:50PM -0700, Geoff Hill wrote: > Fix possible reads past the end of the buffer. > > Found by random fuzz testing (zzuf). Without the fix the fuzzer crashes > in several seconds; with the patch, the fuzzer runs clean for hours. Any reason to not replace the somewhat

Re: machine slow with latest snapshot (bufcache related?) on sparc64

You should include dmesg or even report as proper bugreport. On Fri, Apr 29, 2016 at 10:51 PM, Markus Lude wrote: > Hello, > > with latest snapshot I've short hangs on my (good old) SUN Blade 100. > The desktop clocks often shows jumps for several seconds. > I noticed that

Re: Speedup sdhc(4)

On 4/28/16 2:30 PM, Mark Kettenis wrote: So here are just the bits that add DMA support. Since Theo likes this so much, I'd like to move forward with this. ok? Hi Mark, This diff seems to break things on my Lenovo Ideapad 100s. The 100s has an internal eMMC and a microSD card slot. As far

Re: sched_init_cpu() fix

> Date: Fri, 29 Apr 2016 13:59:50 +0200 > From: Martin Pieuchot > > 3 architectures make the scheduler aware of secondary CPUs before they > can really execute anything. This is bad because during the boot > process threads will be put on their run queues. That means that on

Re: Speedup sdhc(4)

On Thu, Apr 28, 2016 at 08:30:13PM +0200, Mark Kettenis wrote: > So here are just the bits that add DMA support. Since Theo likes this > so much, I'd like to move forward with this. > > ok? Go for it. Havent' tested it myself but looks good and is a very much needed enhancement. I found one

Re: static in ze kernel

> Date: Fri, 29 Apr 2016 13:41:00 +0200 > From: Martin Pieuchot > > On 28/04/16(Thu) 14:49, Mark Kettenis wrote: > > > Date: Thu, 28 Apr 2016 13:50:53 +0200 > > > From: Martin Pieuchot > > > > > > The reason why we do not use 'static' in the kernel is no

sched_init_cpu() fix

3 architectures make the scheduler aware of secondary CPUs before they can really execute anything. This is bad because during the boot process threads will be put on their run queues. That means that on such architecture we are only able to boot because the first CPU can steal threads from the

Re: tmux(1): dealing with broken wcwidth(3)

Hi Nic, Nicholas Marriott wrote on Fri, Apr 29, 2016 at 10:08:18AM +0100: > If this was just guaranteed nonprintable characters, there would be no > issue. But the problem is that some platforms are missing genuine UTF-8 > characters and since many terminals do not use wcwidth(), it means that >

Re: tmux(1): dealing with broken wcwidth(3)

On Thu, Apr 28, 2016 at 06:49:58PM +0200, Ingo Schwarze wrote: > Hi Nic, > > Nicholas Marriott wrote on Thu, Apr 28, 2016 at 01:11:44PM +0100: > > > tmux is not some sort of terminal firewall. Of course we try to avoid > > anything obviously stupid, but we also want stuff that works outside > >

Re: static in ze kernel

On Fri, Apr 29, 2016 at 08:54:51AM +0200, Otto Moerbeek wrote: > On Fri, Apr 29, 2016 at 04:43:56PM +1000, David Gwynne wrote: > > > > > > On 28 Apr 2016, at 22:49, Mark Kettenis wrote: > > > > > >> Date: Thu, 28 Apr 2016 13:50:53 +0200 > > >> From: Martin Pieuchot

Re: static in ze kernel

On Fri, Apr 29, 2016 at 04:43:56PM +1000, David Gwynne wrote: > > > On 28 Apr 2016, at 22:49, Mark Kettenis wrote: > > > >> Date: Thu, 28 Apr 2016 13:50:53 +0200 > >> From: Martin Pieuchot > >> > >> The reason why we do not use 'static' in the kernel

Re: static in ze kernel

On Fri, Apr 29, 2016 at 04:43:56PM +1000, David Gwynne wrote: > > > On 28 Apr 2016, at 22:49, Mark Kettenis wrote: > > > >> Date: Thu, 28 Apr 2016 13:50:53 +0200 > >> From: Martin Pieuchot > >> > >> The reason why we do not use 'static' in the

Re: multi-pool malloc wip diff

Hi, new diff in http://www.drijf.net/openbsd/malloc/ Should fix the issue Ted spotted and contains initial code to only set up multiple pools if threaded. This one is only lightly tested by me, but I wanted to post this before I'll be away for a semi-long weekend, I don't think this is ready

Re: static in ze kernel

> On 28 Apr 2016, at 22:49, Mark Kettenis wrote: > >> Date: Thu, 28 Apr 2016 13:50:53 +0200 >> From: Martin Pieuchot >> >> The reason why we do not use 'static' in the kernel is no longer valid >> since all our platforms are ELF. ddb(4) handle them