On 04/09/2014 11:51 AM, Chao Yu wrote:
> Hi Levin,
>
> Could you share dump code info like following one which can be generated
> by 'objdump -Dl f2fs.ko > obj'.
> It may help us to get a clue for this problem.
>
> verify_block_addr()
> segment.h:543 (discriminator 3)
> 2f35: 39 55 ec
es;
> LKML;
> linux-f2fs-de...@lists.sourceforge.net
> Subject: [f2fs-dev] f2fs: kernel BUG at fs/f2fs/segment.h:543
>
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running the latest
> -next kernel I've stumbled on the following:
>
> [ 1789.220942
2014-04-06 (일), 21:55 -0400, Sasha Levin:
> On 04/06/2014 09:20 PM, Jaegeuk Kim wrote:
> > Hi,
> >
> > Thank you for the report.
> >
> > If possible, could you share fsck.f2fs or dump.f2fs on the corrupted
> > partition?
> >
> > Otherwise, how about this?
> > # fdisk /dev/sdx
> >> > p
>
> Hey J
On 04/06/2014 09:20 PM, Jaegeuk Kim wrote:
> Hi,
>
> Thank you for the report.
>
> If possible, could you share fsck.f2fs or dump.f2fs on the corrupted
> partition?
>
> Otherwise, how about this?
> # fdisk /dev/sdx
>> > p
Hey Jaegeuk,
Unfortunately it was a temporary filesystem inside the fuzz
Hi,
Thank you for the report.
If possible, could you share fsck.f2fs or dump.f2fs on the corrupted
partition?
Otherwise, how about this?
# fdisk /dev/sdx
> p
Thank you,
2014-04-05 (토), 11:12 -0400, Sasha Levin:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running the late
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest
-next kernel I've stumbled on the following:
[ 1789.220942] kernel BUG at fs/f2fs/segment.h:543!
[ 1789.220942] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[ 1789.220942] Dumping ftrace buffer:
[ 1789.220942]
6 matches
Mail list logo
