<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>See "<span style="font-size: 12pt; font-family: Helvetica;">[vfs] WARNING: CPU: 3 PID: 2339 at mm/truncate.c:758 pagecache_isize_extended+0xdd/0x120()" sent earlier today.</span></div><div><p style="margin: 0px; font-size: 12px; font-family: Helvetica;"><span style="font-size: 12pt;"><br></span></p><p style="margin: 0px; font-size: 12px; font-family: Helvetica;"><span style="font-size: 12pt;">-Eric</span></p><p style="margin: 0px; font-size: 12px; font-family: Helvetica;"><span style="font-size: 12pt;"><br></span></p>On Oct 26, 2014, at 10:21 PM, "Michael L. Semon" <<a href="mailto:mlsemon35@gmail.com">mlsemon35@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hi!  I was having fantastic luck with v5/finobt XFS and kernel</span><br><span>3.18.0-rc1, so I decided to disable quota support and debug support</span><br><span>in XFS...</span><br><span></span><br><span>[    0.000000] Linux version 3.18.0-rc1+ (root@kyhorse) (gcc version 4.8.3 (GCC) ) #5 SMP Sun Oct 26 14:43:09 EDT 2014</span><br><span># i686 Pentium 4, BTW.</span><br><span>[    0.857655] SGI XFS with ACLs, security attributes, no debug enabled</span><br><span></span><br><span>Some other debug items were shut off as well.</span><br><span></span><br><span>Now, my logs are getting pelted with items that look like this (first trace,</span><br><span>on boot):</span><br><span></span><br><span>[   14.549583] XFS (sda1): Mounting V5 Filesystem</span><br><span>[   14.810908] XFS (sda1): Ending clean mount</span><br><span>[   14.826918] mount (155) used greatest stack depth: 6056 bytes left</span><br><span>[   15.139152] rc.S (64) used greatest stack depth: 5948 bytes left</span><br><span>[   29.443780] ------------[ cut here ]------------</span><br><span>[   29.443801] WARNING: CPU: 0 PID: 387 at mm/truncate.c:758 pagecache_isize_extended+0x124/0x129()</span><br><span>[   29.443809] CPU: 0 PID: 387 Comm: gtk-query-immod Not tainted 3.18.0-rc1+ #5</span><br><span>[   29.443813] Hardware name: Gateway                         E-2000                         /D845GRG                        , BIOS RG84510A.15A.0009.P03.020</span><br><span>[   29.443817]  00000000 00000000 ee1e9e20 c144939c 00000000 ee1e9e50 c1031b03 c154f66c</span><br><span>[   29.443828]  00000000 00000183 c1553739 000002f6 c1098458 c1098458 e849ed54 00000000</span><br><span>[   29.443838]  00001000 ee1e9e60 c1031bb8 00000009 00000000 ee1e9e98 c1098458 efd69100</span><br><span>[   29.443848] Call Trace:</span><br><span>[   29.443858]  [<c144939c>] dump_stack+0x41/0x52</span><br><span>[   29.443867]  [<c1031b03>] warn_slowpath_common+0x6f/0x86</span><br><span>[   29.443873]  [<c1098458>] ? pagecache_isize_extended+0x124/0x129</span><br><span>[   29.443878]  [<c1098458>] ? pagecache_isize_extended+0x124/0x129</span><br><span>[   29.443884]  [<c1031bb8>] warn_slowpath_null+0x1d/0x1f</span><br><span>[   29.443889]  [<c1098458>] pagecache_isize_extended+0x124/0x129</span><br><span>[   29.443895]  [<c1098494>] truncate_setsize+0x37/0x50</span><br><span>[   29.443902]  [<c117c534>] xfs_setattr_size+0x13d/0x3d6</span><br><span>[   29.443909]  [<c116a2ed>] ? __xfs_get_blocks+0x5ff/0x5ff</span><br><span>[   29.443916]  [<c1172c13>] xfs_file_fallocate+0x2fe/0x340</span><br><span>[   29.443922]  [<c1444ccc>] ? kmemleak_free+0x20/0x43</span><br><span>[   29.443931]  [<c10ba00d>] ? kmem_cache_free+0x76/0xc4</span><br><span>[   29.443938]  [<c10bd802>] do_fallocate+0x111/0x18a</span><br><span>[   29.443943]  [<c10bd8cb>] SyS_fallocate+0x50/0x70</span><br><span>[   29.443950]  [<c144f6ef>] syscall_call+0x7/0x7</span><br><span>[   29.443954] ---[ end trace 281f0f955c16f86c ]---</span><br><span></span><br><span>In an xfstests run, it seemed to start with generic/012 and hit a</span><br><span>great many tests after that.  The actual BUG_ON is somewhere in</span><br><span>mm/truncate.c, though...</span><br><span></span><br><span>        WARN_ON(!mutex_is_locked(&inode->i_mutex));</span><br><span></span><br><span>Is this an XFS issue at all?  Or is there some kind of extra</span><br><span>precaution that has to be taken on the XFS side?  Feel free to toss</span><br><span>me over to mm to ask, "What is this?"</span><br><span></span><br><span>Thanks!</span><br><span></span><br><span>Michael</span><br><span></span><br><span>_______________________________________________</span><br><span>xfs mailing list</span><br><span><a href="mailto:xfs@oss.sgi.com">xfs@oss.sgi.com</a></span><br><span><a href="http://oss.sgi.com/mailman/listinfo/xfs">http://oss.sgi.com/mailman/listinfo/xfs</a></span><br><span></span><br></div></blockquote></body></html>