On Wed, 19 Dec 2012, Hugh Dickins wrote:
> On Wed, 19 Dec 2012, Petr Holasek wrote:
> > >
> > > For the moment, you're safer not to run KSM: configure it out or don't
> > > set it to run. Fixes to follow later, I'll try to remember to Cc you.
>
> Sadly I couldn't send out fixes yesterday,
On Wed, 19 Dec 2012, Petr Holasek wrote:
> On Tue, 18 Dec 2012, Hugh Dickins wrote:
> > On Tue, 18 Dec 2012, Sasha Levin wrote:
> >
> > > Hi all,
> > >
> > > While fuzzing with trinity inside a KVM tools guest, running latest
> > > linux-next kernel, I've
> > > stumbled on the following:
> > >
On Tue, 18 Dec 2012, Hugh Dickins wrote:
> On Tue, 18 Dec 2012, Sasha Levin wrote:
>
> > Hi all,
> >
> > While fuzzing with trinity inside a KVM tools guest, running latest
> > linux-next kernel, I've
> > stumbled on the following:
> >
> > [ 127.959264] BUG: unable to handle kernel NULL
On Tue, 18 Dec 2012, Hugh Dickins wrote:
> On Tue, 18 Dec 2012, Sasha Levin wrote:
>
> > Hi all,
> >
> > While fuzzing with trinity inside a KVM tools guest, running latest
> > linux-next kernel, I've
> > stumbled on the following:
> >
> > [ 127.959264] BUG: unable to handle kernel NULL
On Tue, 18 Dec 2012, Hugh Dickins wrote:
On Tue, 18 Dec 2012, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest, running latest
linux-next kernel, I've
stumbled on the following:
[ 127.959264] BUG: unable to handle kernel NULL pointer dereference
On Tue, 18 Dec 2012, Hugh Dickins wrote:
On Tue, 18 Dec 2012, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest, running latest
linux-next kernel, I've
stumbled on the following:
[ 127.959264] BUG: unable to handle kernel NULL pointer dereference
On Wed, 19 Dec 2012, Petr Holasek wrote:
On Tue, 18 Dec 2012, Hugh Dickins wrote:
On Tue, 18 Dec 2012, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest, running latest
linux-next kernel, I've
stumbled on the following:
[ 127.959264] BUG:
On Wed, 19 Dec 2012, Hugh Dickins wrote:
On Wed, 19 Dec 2012, Petr Holasek wrote:
For the moment, you're safer not to run KSM: configure it out or don't
set it to run. Fixes to follow later, I'll try to remember to Cc you.
Sadly I couldn't send out fixes yesterday, because my
On Tue, 18 Dec 2012, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest, running latest
> linux-next kernel, I've
> stumbled on the following:
>
> [ 127.959264] BUG: unable to handle kernel NULL pointer dereference at
> 0110
> [ 127.960379] IP:
Hi all,
While fuzzing with trinity inside a KVM tools guest, running latest linux-next
kernel, I've
stumbled on the following:
[ 127.959264] BUG: unable to handle kernel NULL pointer dereference at
0110
[ 127.960379] IP: [] __lock_acquire+0xb0/0xa90
[ 127.960379] PGD cc54067 PUD
Hi all,
While fuzzing with trinity inside a KVM tools guest, running latest linux-next
kernel, I've
stumbled on the following:
[ 127.959264] BUG: unable to handle kernel NULL pointer dereference at
0110
[ 127.960379] IP: [81185b60] __lock_acquire+0xb0/0xa90
[ 127.960379]
On Tue, 18 Dec 2012, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest, running latest
linux-next kernel, I've
stumbled on the following:
[ 127.959264] BUG: unable to handle kernel NULL pointer dereference at
0110
[ 127.960379] IP:
12 matches
Mail list logo