From: hujianyang <hujianyang@huawei.com>
To: <dedekind1@gmail.com>
Cc: Caizhiyong <caizhiyong@hisilicon.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
Jijiagang <jijiagang@hisilicon.com>
Subject: Re: UBIFS assert failed in ubifs_set_page_dirty at 1421
Date: Wed, 22 Oct 2014 11:38:53 +0800 [thread overview]
Message-ID: <544726CD.90902@huawei.com> (raw)
In-Reply-To: <1413805935.7906.225.camel@sauron.fi.intel.com>
On 2014/10/20 19:52, Artem Bityutskiy wrote:
> On Thu, 2014-10-09 at 06:48 +0000, Jijiagang wrote:
>> Hi Artem and Adrian,
>>
>> We encountered a “UBIFS assert failed in ubifs_set_page_dirty at 1421
>> (pid 543)” problem when running MONKEY test in android platform.
>
> Hi, yes, this looks like a bug,
>
> could you please re-send this e-mail in plain test format, because the
> MTD mailing list traps HTML e-mails.
>
> Thanks!
>
Hi Artem,
My colleagues find me and complain about this problem in September. The
previous bug I fixed, commit 691a7c6f, didn't fix the problem they
tolerate now. It has a different dump stack.
I don't have enough board or enough understanding to recreate this failure.
Do you think it is related?
line 1160, func try_to_unmap_one() in mm/rmap.c
""
/* Move the dirty bit to the physical page now the pte is gone. */
if (pte_dirty(pteval))
set_page_dirty(page);
""
Is this pte_dirty() cause this error?
The recent patch you send, [PATCH] UBIFS: fix budget leak in error path,
seems not to fix this problem. They've tested this patch and find the
problem still exist.
Do you have any suggestions about this? I was busy these days so maybe
I could start to deal with this problem in November.
I should say, I don't know if it is a real problem caused by kernel. Maybe
this problem is caused by other changes outside kernel.
Any help is welcomed~!
Hu
next prev parent reply other threads:[~2014-10-22 3:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BE257DAADD2C0D439647A271332966573949EFEC@SZXEMA511-MBS.china.huawei.com>
2014-10-20 11:52 ` UBIFS assert failed in ubifs_set_page_dirty at 1421 Artem Bityutskiy
2014-10-20 11:55 ` Caizhiyong
2014-10-20 12:01 ` Caizhiyong
2014-10-20 13:11 ` Artem Bityutskiy
2014-10-20 13:11 ` Artem Bityutskiy
2014-10-20 13:11 ` Artem Bityutskiy
2014-10-21 2:30 ` Jijiagang
2014-10-21 2:30 ` Jijiagang
2014-10-21 3:38 ` Dave Chinner
2014-10-21 3:38 ` Dave Chinner
2014-10-21 3:38 ` Dave Chinner
2014-10-21 8:41 ` Jijiagang
2014-10-21 8:41 ` Jijiagang
2014-10-21 8:41 ` Jijiagang
2014-11-06 8:28 ` Jijiagang
2014-11-06 8:28 ` Jijiagang
2014-11-06 8:28 ` Jijiagang
2014-11-07 2:22 ` hujianyang
2014-11-07 2:22 ` hujianyang
2014-11-07 2:22 ` hujianyang
2014-11-20 12:30 ` Kirill A. Shutemov
2014-11-20 12:30 ` Kirill A. Shutemov
2014-11-24 2:59 ` Jijiagang
2014-11-24 2:59 ` Jijiagang
2014-11-24 2:59 ` Jijiagang
2014-11-24 9:10 ` Kirill A. Shutemov
2014-11-24 9:10 ` Kirill A. Shutemov
2014-11-24 10:20 ` Jijiagang
2014-11-24 10:20 ` Jijiagang
2014-11-24 10:20 ` Jijiagang
2014-11-24 13:27 ` Kirill A. Shutemov
2014-11-24 13:27 ` Kirill A. Shutemov
2014-10-22 3:38 ` hujianyang [this message]
2014-10-22 8:02 ` Artem Bityutskiy
2014-10-22 8:21 ` hujianyang
2014-10-22 9:30 ` 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=544726CD.90902@huawei.com \
--to=hujianyang@huawei.com \
--cc=adrian.hunter@intel.com \
--cc=caizhiyong@hisilicon.com \
--cc=dedekind1@gmail.com \
--cc=jijiagang@hisilicon.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 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.