From: Tommi Rantala <tt.rantala@gmail.com>
To: linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>,
Changman Lee <cm224.lee@samsung.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
trinity@vger.kernel.org, Dave Jones <davej@redhat.com>
Subject: f2fs get_dnode_of_data oops
Date: Sun, 7 Sep 2014 22:14:02 +0300 [thread overview]
Message-ID: <CA+ydwtrB-rJB1fURO+CC1J-=VZ16g9Un47cMSMAZsTFPNg2s+g@mail.gmail.com> (raw)
Hello,
Hit this oops while fuzzing v3.17-rc3-176-g2b12164 with Trinity.
Tommi
BUG: unable to handle kernel paging request at ffff8804338717a8
IP: [<ffffffff81779039>] get_dnode_of_data+0x3a9/0x440
PGD 4594067 PUD 0
Oops: 0000 [#1] SMP DEBUG_PAGEALLOC
CPU: 0 PID: 4719 Comm: trinity-c3 Not tainted 3.17.0-rc3+ #33
Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
task: ffff880015630000 ti: ffff88000724c000 task.ti: ffff88000724c000
RIP: 0010:[<ffffffff81779039>] [<ffffffff81779039>]
get_dnode_of_data+0x3a9/0x440
RSP: 0018:ffff88000724fe08 EFLAGS: 00010246
RAX: ffff880033874000 RBX: 00000000000000f8 RCX: 00000000fffff590
RDX: ffff880033874168 RSI: ffff88000724fd98 RDI: ffff88000724fef0
RBP: ffff88000724feb8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: ffffffff83b33f90 R12: fffffffffffff590
R13: 0000000000000000 R14: ffffea0000ce1d00 R15: ffff8800209f8000
FS: 00007f2bd22dc700(0000) GS:ffff88003fa00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffff8804338717a8 CR3: 00000000346c0000 CR4: 00000000000006f0
DR0: 000000000185d000 DR1: 000000000185d000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 00000000000b0602
Stack:
ffff88000724fef0 ffff88000724fe30 ffff880036c18000 0000000000000004
ffff8800209f80f0 00000002fffff590 ffffffff81189f1d ffff8800fffff590
0000000000000246 ffffffff00000000 ffffffff81189ce0 ffffffff000000f8
Call Trace:
[<ffffffff81189f1d>] ? trace_hardirqs_on+0xd/0x10
[<ffffffff81189ce0>] ? mark_held_locks+0x90/0xa0
[<ffffffff81189e75>] ? trace_hardirqs_on_caller+0x185/0x220
[<ffffffff81763417>] f2fs_llseek+0xf7/0x420
[<ffffffff8127e4d5>] SyS_lseek+0x65/0xa0
[<ffffffff8259b229>] system_call_fastpath+0x16/0x1b
Code: ba 00 00 00 00 00 88 ff ff 48 c1 f8 06 48 c1 e0 0c 48 01 d0 8b
98 ec 0f 00 00 39 98 e8 0f 00 00 48 8d 90 68 01 00 00 48 0f 45 d0 <8b>
04 8a 89 47 24 31 c0 eb 75 41 bc e4 ff ff ff 4d 85 f6 74 19
RIP [<ffffffff81779039>] get_dnode_of_data+0x3a9/0x440
RSP <ffff88000724fe08>
CR2: ffff8804338717a8
---[ end trace bed7b35d1c48e9c3 ]---
next reply other threads:[~2014-09-07 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 19:14 Tommi Rantala [this message]
2014-09-07 19:20 ` f2fs get_dnode_of_data oops Tommi Rantala
2014-09-08 4:20 ` Jaegeuk Kim
2014-09-08 15:39 ` Tommi Rantala
2014-09-09 4:41 ` Jaegeuk Kim
2014-09-09 8:10 ` [f2fs-dev] " Chao Yu
2014-09-10 7:23 ` Jaegeuk Kim
2014-09-09 18:24 ` Tommi Rantala
2014-09-10 7:26 ` Jaegeuk Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+ydwtrB-rJB1fURO+CC1J-=VZ16g9Un47cMSMAZsTFPNg2s+g@mail.gmail.com' \
--to=tt.rantala@gmail.com \
--cc=cm224.lee@samsung.com \
--cc=davej@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trinity@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).