From: Sasha Levin <sasha.levin@oracle.com>
To: Chao Yu <yuchaochina@hotmail.com>, jaegeuk.kim@samsung.com
Cc: 'Dave Jones' <davej@redhat.com>,
'LKML' <linux-kernel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: f2fs: kernel BUG at fs/f2fs/segment.h:543
Date: Wed, 09 Apr 2014 11:57:36 -0400 [thread overview]
Message-ID: <53456DF0.5060605@oracle.com> (raw)
In-Reply-To: <COL402-EAS13359D6EB23C18DA0BBE9DAAB6A0@phx.gbl>
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 cmp %edx,-0x14(%ebp)
> segment.h:542 (discriminator 3)
> 2f38: 8d 44 02 ff lea -0x1(%edx,%eax,1),%eax
> segment.h:543 (discriminator 3)
> 2f3c: 0f 82 dc 01 00 00 jb 311e <f2fs_submit_page_mbio+0x22e>
> segment.h:544
> 2f42: 39 45 ec cmp %eax,-0x14(%ebp)
> 2f45: 0f 87 d1 01 00 00 ja 311c <f2fs_submit_page_mbio+0x22c>
verify_block_addr():
/home/sasha/linux-next/fs/f2fs/data.c:1079 (discriminator 3)
f710: 49 8b 45 38 mov 0x38(%r13),%rax
/home/sasha/linux-next/fs/f2fs/segment.h:540 (discriminator 3)
f714: 41 8b 8d d0 06 00 00 mov 0x6d0(%r13),%ecx
/home/sasha/linux-next/fs/f2fs/segment.h:541 (discriminator 3)
f71b: 44 8b 40 78 mov 0x78(%rax),%r8d
/home/sasha/linux-next/fs/f2fs/segment.h:540 (discriminator 3)
f71f: 8b 80 84 00 00 00 mov 0x84(%rax),%eax
f725: d3 e0 shl %cl,%eax
/home/sasha/linux-next/fs/f2fs/segment.h:543 (discriminator 3)
f727: 45 39 c6 cmp %r8d,%r14d
/home/sasha/linux-next/fs/f2fs/segment.h:542 (discriminator 3)
f72a: 45 8d 4c 00 ff lea -0x1(%r8,%rax,1),%r9d
/home/sasha/linux-next/fs/f2fs/segment.h:543 (discriminator 3)
f72f: 73 1f jae f750 <f2fs_submit_page_mbio+0xa0>
/home/sasha/linux-next/fs/f2fs/segment.h:544
f731: 49 8b 7d 00 mov 0x0(%r13),%rdi
f735: 44 89 f1 mov %r14d,%ecx
f738: 48 c7 c2 00 00 00 00 mov $0x0,%rdx
f73f: 48 c7 c6 00 00 00 00 mov $0x0,%rsi
f746: 31 c0 xor %eax,%eax
f748: e8 00 00 00 00 callq f74d <f2fs_submit_page_mbio+0x9d>
/home/sasha/linux-next/fs/f2fs/segment.h:547
f74d: 0f 0b ud2
f74f: 90 nop
/home/sasha/linux-next/fs/f2fs/segment.h:550
f750: 45 39 ce cmp %r9d,%r14d
f753: 76 0b jbe f760 <f2fs_submit_page_mbio+0xb0>
f755: 0f 0b ud2
f757: 66 0f 1f 84 00 00 00 nopw 0x0(%rax,%rax,1)
f75e: 00 00
Thanks,
Sasha
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sasha.levin@oracle.com>
To: Chao Yu <yuchaochina@hotmail.com>, jaegeuk.kim@samsung.com
Cc: "'Dave Jones'" <davej@redhat.com>,
"'LKML'" <linux-kernel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] f2fs: kernel BUG at fs/f2fs/segment.h:543
Date: Wed, 09 Apr 2014 11:57:36 -0400 [thread overview]
Message-ID: <53456DF0.5060605@oracle.com> (raw)
In-Reply-To: <COL402-EAS13359D6EB23C18DA0BBE9DAAB6A0@phx.gbl>
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 cmp %edx,-0x14(%ebp)
> segment.h:542 (discriminator 3)
> 2f38: 8d 44 02 ff lea -0x1(%edx,%eax,1),%eax
> segment.h:543 (discriminator 3)
> 2f3c: 0f 82 dc 01 00 00 jb 311e <f2fs_submit_page_mbio+0x22e>
> segment.h:544
> 2f42: 39 45 ec cmp %eax,-0x14(%ebp)
> 2f45: 0f 87 d1 01 00 00 ja 311c <f2fs_submit_page_mbio+0x22c>
verify_block_addr():
/home/sasha/linux-next/fs/f2fs/data.c:1079 (discriminator 3)
f710: 49 8b 45 38 mov 0x38(%r13),%rax
/home/sasha/linux-next/fs/f2fs/segment.h:540 (discriminator 3)
f714: 41 8b 8d d0 06 00 00 mov 0x6d0(%r13),%ecx
/home/sasha/linux-next/fs/f2fs/segment.h:541 (discriminator 3)
f71b: 44 8b 40 78 mov 0x78(%rax),%r8d
/home/sasha/linux-next/fs/f2fs/segment.h:540 (discriminator 3)
f71f: 8b 80 84 00 00 00 mov 0x84(%rax),%eax
f725: d3 e0 shl %cl,%eax
/home/sasha/linux-next/fs/f2fs/segment.h:543 (discriminator 3)
f727: 45 39 c6 cmp %r8d,%r14d
/home/sasha/linux-next/fs/f2fs/segment.h:542 (discriminator 3)
f72a: 45 8d 4c 00 ff lea -0x1(%r8,%rax,1),%r9d
/home/sasha/linux-next/fs/f2fs/segment.h:543 (discriminator 3)
f72f: 73 1f jae f750 <f2fs_submit_page_mbio+0xa0>
/home/sasha/linux-next/fs/f2fs/segment.h:544
f731: 49 8b 7d 00 mov 0x0(%r13),%rdi
f735: 44 89 f1 mov %r14d,%ecx
f738: 48 c7 c2 00 00 00 00 mov $0x0,%rdx
f73f: 48 c7 c6 00 00 00 00 mov $0x0,%rsi
f746: 31 c0 xor %eax,%eax
f748: e8 00 00 00 00 callq f74d <f2fs_submit_page_mbio+0x9d>
/home/sasha/linux-next/fs/f2fs/segment.h:547
f74d: 0f 0b ud2
f74f: 90 nop
/home/sasha/linux-next/fs/f2fs/segment.h:550
f750: 45 39 ce cmp %r9d,%r14d
f753: 76 0b jbe f760 <f2fs_submit_page_mbio+0xb0>
f755: 0f 0b ud2
f757: 66 0f 1f 84 00 00 00 nopw 0x0(%rax,%rax,1)
f75e: 00 00
Thanks,
Sasha
next prev parent reply other threads:[~2014-04-09 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 15:12 f2fs: kernel BUG at fs/f2fs/segment.h:543 Sasha Levin
2014-04-05 15:12 ` Sasha Levin
2014-04-07 1:20 ` Jaegeuk Kim
2014-04-07 1:20 ` Jaegeuk Kim
2014-04-07 1:55 ` Sasha Levin
2014-04-07 1:55 ` Sasha Levin
2014-04-07 3:40 ` Jaegeuk Kim
2014-04-07 3:40 ` Jaegeuk Kim
2014-04-09 15:51 ` Chao Yu
2014-04-09 15:51 ` [f2fs-dev] " Chao Yu
2014-04-09 15:57 ` Sasha Levin [this message]
2014-04-09 15:57 ` Sasha Levin
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=53456DF0.5060605@oracle.com \
--to=sasha.levin@oracle.com \
--cc=davej@redhat.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchaochina@hotmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.