From: Dave Chinner <david@fromorbit.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Jijiagang <jijiagang@hisilicon.com>,
Caizhiyong <caizhiyong@hisilicon.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
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: Tue, 21 Oct 2014 14:38:47 +1100 [thread overview]
Message-ID: <20141021033847.GS17506@dastard> (raw)
In-Reply-To: <1413810719.7906.268.camel@sauron.fi.intel.com>
On Mon, Oct 20, 2014 at 04:11:59PM +0300, Artem Bityutskiy wrote:
> 3. There are exactly 2 places where UBIFS-backed pages may be marked as
> dirty:
>
> a) ubifs_write_end() [->wirte_end] - the file write path
> b) ubifs_page_mkwrite() [->page_mkwirte] - the file mmap() path
>
> 4. If anything calls 'ubifs_set_page_dirty()' directly (not through
> write_end()/mkwrite()), and the page was not dirty, UBIFS will complain
> with the assertion that you see.
>
> > CPU: 3 PID: 543 Comm: kswapd0 Tainted: P O 3.10.0_s40 #1
Kernel is tainted. Not worth wasting time on unless it can be
reproduced on an untainted kernel...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Caizhiyong <caizhiyong@hisilicon.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org, Jijiagang <jijiagang@hisilicon.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Wanli (welly)" <welly.wan@hisilicon.com>
Subject: Re: UBIFS assert failed in ubifs_set_page_dirty at 1421
Date: Tue, 21 Oct 2014 14:38:47 +1100 [thread overview]
Message-ID: <20141021033847.GS17506@dastard> (raw)
In-Reply-To: <1413810719.7906.268.camel@sauron.fi.intel.com>
On Mon, Oct 20, 2014 at 04:11:59PM +0300, Artem Bityutskiy wrote:
> 3. There are exactly 2 places where UBIFS-backed pages may be marked as
> dirty:
>
> a) ubifs_write_end() [->wirte_end] - the file write path
> b) ubifs_page_mkwrite() [->page_mkwirte] - the file mmap() path
>
> 4. If anything calls 'ubifs_set_page_dirty()' directly (not through
> write_end()/mkwrite()), and the page was not dirty, UBIFS will complain
> with the assertion that you see.
>
> > CPU: 3 PID: 543 Comm: kswapd0 Tainted: P O 3.10.0_s40 #1
Kernel is tainted. Not worth wasting time on unless it can be
reproduced on an untainted kernel...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Caizhiyong <caizhiyong@hisilicon.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org, Jijiagang <jijiagang@hisilicon.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Wanli (welly)" <welly.wan@hisilicon.com>
Subject: Re: UBIFS assert failed in ubifs_set_page_dirty at 1421
Date: Tue, 21 Oct 2014 14:38:47 +1100 [thread overview]
Message-ID: <20141021033847.GS17506@dastard> (raw)
In-Reply-To: <1413810719.7906.268.camel@sauron.fi.intel.com>
On Mon, Oct 20, 2014 at 04:11:59PM +0300, Artem Bityutskiy wrote:
> 3. There are exactly 2 places where UBIFS-backed pages may be marked as
> dirty:
>
> a) ubifs_write_end() [->wirte_end] - the file write path
> b) ubifs_page_mkwrite() [->page_mkwirte] - the file mmap() path
>
> 4. If anything calls 'ubifs_set_page_dirty()' directly (not through
> write_end()/mkwrite()), and the page was not dirty, UBIFS will complain
> with the assertion that you see.
>
> > CPU: 3 PID: 543 Comm: kswapd0 Tainted: P O 3.10.0_s40 #1
Kernel is tainted. Not worth wasting time on unless it can be
reproduced on an untainted kernel...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
--
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-10-21 3:41 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 [this message]
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
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=20141021033847.GS17506@dastard \
--to=david@fromorbit.com \
--cc=adrian.hunter@intel.com \
--cc=caizhiyong@hisilicon.com \
--cc=dedekind1@gmail.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.