> Any reason to not replace the somewhat arbitary earlier test
> for this?
I chose to keep the condition simpler and the existing constraints intact for
minimal impact, but I would agree it's better to consolidate with the existing
check.
Your diff looks good to me, +1.
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 ar
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 the machine is running
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 the machine is running low on free memory and uses a lot
for cache.
kern.bufcachepercent is 90
After setting this to 20 the machine feels a lot mor
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 as
> 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
> such architecture
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 tin
> 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 longer valid
> > > since all our platfor
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 n
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 longer valid
> > since all our platforms are ELF. ddb(4) handle them just fine.
> >
> > Here's an example after sett
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
>
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
> > t
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
> > >>
> > >> The reason w
13 matches
Mail list logo