linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Dolev Raviv" <draviv@codeaurora.org>
To: "'hujianyang'" <hujianyang@huawei.com>,
	"'Artem Bityutskiy'" <dedekind1@gmail.com>
Cc: 'linux-mtd' <linux-mtd@lists.infradead.org>
Subject: RE: ubifs: assertion fails
Date: Thu, 29 May 2014 10:24:01 +0300	[thread overview]
Message-ID: <004001cf7b0e$f839a640$e8acf2c0$@codeaurora.org> (raw)
In-Reply-To: <538693AD.5070606@huawei.com>

Hi,
I still see this. I was blocked recently by other tasks. I guess I'll get to
it in the near future.
If you have an insight on this it will be very helpful.

Thanks,
Dolev
-- 
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation


-----Original Message-----
From: hujianyang [mailto:hujianyang@huawei.com] 
Sent: Thursday, May 29, 2014 4:56 AM
To: Dolev Raviv; Artem Bityutskiy
Cc: linux-mtd
Subject: Re: ubifs: assertion fails

Hi Dolev and Artem,

I hit the same assert failed in Kernel v3.10 shows like this:

[ 9641.164028] UBIFS assert failed in shrink_tnc at 131 (pid 13297)
[ 9641.234078] CPU: 1 PID: 13297 Comm: mmap.test Tainted: G           O
3.10.40 #1
[ 9641.234116] [<c0011a6c>] (unwind_backtrace+0x0/0x12c) from [<c000d0b0>]
(show_stack+0x20/0x24) [ 9641.234137] [<c000d0b0>] (show_stack+0x20/0x24)
from [<c0311134>] (dump_stack+0x20/0x28) [ 9641.234188] [<c0311134>]
(dump_stack+0x20/0x28) from [<bf22425c>] (shrink_tnc_trees+0x25c/0x350
[ubifs]) [ 9641.234265] [<bf22425c>] (shrink_tnc_trees+0x25c/0x350 [ubifs])
from [<bf2245ac>] (ubifs_shrinker+0x25c/0x310 [ubifs]) [ 9641.234307]
[<bf2245ac>] (ubifs_shrinker+0x25c/0x310 [ubifs]) from [<c00cdad8>]
(shrink_slab+0x1d4/0x2f8) [ 9641.234327] [<c00cdad8>]
(shrink_slab+0x1d4/0x2f8) from [<c00d03d0>]
(do_try_to_free_pages+0x300/0x544)
[ 9641.234344] [<c00d03d0>] (do_try_to_free_pages+0x300/0x544) from
[<c00d0a44>] (try_to_free_pages+0x2d0/0x398) [ 9641.234363] [<c00d0a44>]
(try_to_free_pages+0x2d0/0x398) from [<c00c6a60>]
(__alloc_pages_nodemask+0x494/0x7e8)
[ 9641.234382] [<c00c6a60>] (__alloc_pages_nodemask+0x494/0x7e8) from
[<c00f62d8>] (new_slab+0x78/0x238) [ 9641.234400] [<c00f62d8>]
(new_slab+0x78/0x238) from [<c031081c>]
(__slab_alloc.constprop.42+0x1a4/0x50c)
[ 9641.234419] [<c031081c>] (__slab_alloc.constprop.42+0x1a4/0x50c) from
[<c00f80e8>] (kmem_cache_alloc_trace+0x54/0x188)
[ 9641.234459] [<c00f80e8>] (kmem_cache_alloc_trace+0x54/0x188) from
[<bf227908>] (do_readpage+0x168/0x468 [ubifs]) [ 9641.234553] [<bf227908>]
(do_readpage+0x168/0x468 [ubifs]) from [<bf2296a0>]
(ubifs_readpage+0x424/0x464 [ubifs]) [ 9641.234606] [<bf2296a0>]
(ubifs_readpage+0x424/0x464 [ubifs]) from [<c00c17c0>]
(filemap_fault+0x304/0x418) [ 9641.234638] [<c00c17c0>]
(filemap_fault+0x304/0x418) from [<c00de694>] (__do_fault+0xd4/0x530) [
9641.234665] [<c00de694>] (__do_fault+0xd4/0x530) from [<c00e10c0>]
(handle_pte_fault+0x480/0xf54) [ 9641.234690] [<c00e10c0>]
(handle_pte_fault+0x480/0xf54) from [<c00e2bf8>]
(handle_mm_fault+0x140/0x184) [ 9641.234716] [<c00e2bf8>]
(handle_mm_fault+0x140/0x184) from [<c0316688>] (do_page_fault+0x150/0x3ac)
[ 9641.234737] [<c0316688>] (do_page_fault+0x150/0x3ac) from [<c000842c>]
(do_DataAbort+0x3c/0xa0) [ 9641.234759] [<c000842c>]
(do_DataAbort+0x3c/0xa0) from [<c0314e38>] (__dabt_usr+0x38/0x40)

Did you fix it in recent patches? If not, I will take some times on it.

I hit this when I was doing stress test, only once and no other failed
messages. I haven't do umount or rmmod until now so I don't know further
information about it.

Thanks!


Hu

  reply	other threads:[~2014-05-29  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  6:03 ubifs: assertion fails Dolev Raviv
2014-03-31 10:14 ` Artem Bityutskiy
2014-04-01  5:52   ` Tanya Brokhman
2014-04-07 11:43     ` Artem Bityutskiy
2014-04-27 12:12       ` Dolev Raviv
2014-05-29  1:55         ` hujianyang
2014-05-29  7:24           ` Dolev Raviv [this message]
2014-05-29  7:42           ` Artem Bityutskiy

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='004001cf7b0e$f839a640$e8acf2c0$@codeaurora.org' \
    --to=draviv@codeaurora.org \
    --cc=dedekind1@gmail.com \
    --cc=hujianyang@huawei.com \
    --cc=linux-mtd@lists.infradead.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 NNTP newsgroup(s).