On Tue, Feb 19, 2013 at 01:18:25PM -0500, Sasha Levin wrote:
> >> [ 169.930103] ---[ end trace 4d135f3def21b4bd ]---
> >>
> >> The code translates to the following in fs/pipe.c:alloc_pipe_info :
> >>
> >> pipe = kzalloc(sizeof(struct pipe_inode_info), GFP_KERNEL);
> >> if
On 02/19/2013 01:29 PM, Dave Jones wrote:
> On Tue, Feb 19, 2013 at 01:18:25PM -0500, Sasha Levin wrote:
>
> > >> [ 169.930103] ---[ end trace 4d135f3def21b4bd ]---
> > >>
> > >> The code translates to the following in fs/pipe.c:alloc_pipe_info :
> > >>
> > >> pipe =
On 02/18/2013 07:35 PM, Christoph Lameter wrote:
> Maybe the result of free pointer corruption due to writing to an object
> after free. Please run again with slub_debug specified on the commandline
> to get detailed reports on how this came about.
>
> On Sun, 17 Feb 2013, Sasha Levin wrote:
>
On 02/18/2013 07:35 PM, Christoph Lameter wrote:
Maybe the result of free pointer corruption due to writing to an object
after free. Please run again with slub_debug specified on the commandline
to get detailed reports on how this came about.
On Sun, 17 Feb 2013, Sasha Levin wrote:
Hi
On 02/19/2013 01:29 PM, Dave Jones wrote:
On Tue, Feb 19, 2013 at 01:18:25PM -0500, Sasha Levin wrote:
[ 169.930103] ---[ end trace 4d135f3def21b4bd ]---
The code translates to the following in fs/pipe.c:alloc_pipe_info :
pipe = kzalloc(sizeof(struct
On Tue, Feb 19, 2013 at 01:18:25PM -0500, Sasha Levin wrote:
[ 169.930103] ---[ end trace 4d135f3def21b4bd ]---
The code translates to the following in fs/pipe.c:alloc_pipe_info :
pipe = kzalloc(sizeof(struct pipe_inode_info), GFP_KERNEL);
if (pipe) {
Maybe the result of free pointer corruption due to writing to an object
after free. Please run again with slub_debug specified on the commandline
to get detailed reports on how this came about.
On Sun, 17 Feb 2013, Sasha Levin wrote:
> Hi all,
>
> I was fuzzing with trinity inside a KVM tools
Maybe the result of free pointer corruption due to writing to an object
after free. Please run again with slub_debug specified on the commandline
to get detailed reports on how this came about.
On Sun, 17 Feb 2013, Sasha Levin wrote:
Hi all,
I was fuzzing with trinity inside a KVM tools
Hi all,
I was fuzzing with trinity inside a KVM tools guest, running latest -next
kernel,
and hit the following bug:
[ 169.773688] BUG: unable to handle kernel NULL pointer dereference at
0001
[ 169.774976] IP: [] memset+0x1f/0xb0
[ 169.775989] PGD 93e02067 PUD ac1a2067 PMD 0
[
Hi all,
I was fuzzing with trinity inside a KVM tools guest, running latest -next
kernel,
and hit the following bug:
[ 169.773688] BUG: unable to handle kernel NULL pointer dereference at
0001
[ 169.774976] IP: [81a15c2f] memset+0x1f/0xb0
[ 169.775989] PGD 93e02067 PUD
10 matches
Mail list logo