From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Jijiagang <jijiagang@hisilicon.com>
Cc: "dedekind1@gmail.com" <dedekind1@gmail.com>,
Caizhiyong <caizhiyong@hisilicon.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
Hujianyang <hujianyang@huawei.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Wanli \(welly\)" <welly.wan@hisilicon.com>
Subject: Re: UBIFS assert failed in ubifs_set_page_dirty at 1421
Date: Mon, 24 Nov 2014 15:27:55 +0200 [thread overview]
Message-ID: <20141124132755.GA3167@node.dhcp.inet.fi> (raw)
In-Reply-To: <BE257DAADD2C0D439647A27133296657394A75F1@SZXEMA511-MBS.china.huawei.com>
On Mon, Nov 24, 2014 at 10:20:59AM +0000, Jijiagang wrote:
> Hi Kirill,
> I test your patch, bus there's no dump_vma definition.
> The log is here, hope it will be helpful.
>
> page:817fd7e0 count:3 mapcount:1 mapping:a318bb8c index:0x4
> page flags: 0xa19(locked|uptodate|dirty|arch_1|private)
> pte_write: 1
> page:81441a80 count:3 mapcount:1 mapping:a318bb8c index:0x5
> page flags: 0x209(locked|uptodate|arch_1)
> pte_write: 1
Okay, pte is writable but page is not dirty and doesn't have private flag
set.
I looked through code and don't see how that could happen.
> UBIFS assert failed in ubifs_set_page_dirty at 1422 (pid 545)
> CPU: 2 PID: 545 Comm: kswapd0 Tainted: P O 3.10.0_s40 #19
Is it possible to reproduce the issue on current upstream without any
patches or third-party modules?
--
Kirill A. Shutemov
WARNING: multiple messages have this Message-ID (diff)
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Jijiagang <jijiagang@hisilicon.com>
Cc: Hujianyang <hujianyang@huawei.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>,
Caizhiyong <caizhiyong@hisilicon.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Wanli (welly)" <welly.wan@hisilicon.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>
Subject: Re: UBIFS assert failed in ubifs_set_page_dirty at 1421
Date: Mon, 24 Nov 2014 15:27:55 +0200 [thread overview]
Message-ID: <20141124132755.GA3167@node.dhcp.inet.fi> (raw)
In-Reply-To: <BE257DAADD2C0D439647A27133296657394A75F1@SZXEMA511-MBS.china.huawei.com>
On Mon, Nov 24, 2014 at 10:20:59AM +0000, Jijiagang wrote:
> Hi Kirill,
> I test your patch, bus there's no dump_vma definition.
> The log is here, hope it will be helpful.
>
> page:817fd7e0 count:3 mapcount:1 mapping:a318bb8c index:0x4
> page flags: 0xa19(locked|uptodate|dirty|arch_1|private)
> pte_write: 1
> page:81441a80 count:3 mapcount:1 mapping:a318bb8c index:0x5
> page flags: 0x209(locked|uptodate|arch_1)
> pte_write: 1
Okay, pte is writable but page is not dirty and doesn't have private flag
set.
I looked through code and don't see how that could happen.
> UBIFS assert failed in ubifs_set_page_dirty at 1422 (pid 545)
> CPU: 2 PID: 545 Comm: kswapd0 Tainted: P O 3.10.0_s40 #19
Is it possible to reproduce the issue on current upstream without any
patches or third-party modules?
--
Kirill A. Shutemov
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-11-24 13:28 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 [this message]
2014-11-24 13:27 ` Kirill A. Shutemov
2014-10-22 3:38 ` hujianyang
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=20141124132755.GA3167@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=adrian.hunter@intel.com \
--cc=caizhiyong@hisilicon.com \
--cc=dedekind1@gmail.com \
--cc=hujianyang@huawei.com \
--cc=jijiagang@hisilicon.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=welly.wan@hisilicon.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.