Thread (11 messages) 11 messages, 5 authors, 2014-11-24

Re: UBIFS assert failed in ubifs_set_page_dirty at 1421

From: Dave Chinner <david@fromorbit.com>
Date: 2014-10-21 03:38:51
Also in: linux-fsdevel

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.
quoted
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>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help