| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20131214082059.GS31386@dastard> Date: Sat, 14 Dec 2013 19:20:59 +1100 From: Dave Chinner <david@...morbit.com> To: Dave Jones <davej@...hat.com>, Christoph Hellwig <hch@...radead.org>, Linux Kernel <linux-kernel@...r.kernel.org>, xfs@....sgi.com Subject: Re: XFS / writeback invoking soft lockup. On Fri, Dec 13, 2013 at 11:22:28AM -0500, Dave Jones wrote: > On Fri, Dec 13, 2013 at 03:16:39AM -0800, Christoph Hellwig wrote: > > On Fri, Dec 13, 2013 at 09:48:53PM +1100, Dave Chinner wrote: > > > All I can say is that there doesn't look to be any obvious signs > > > that this is a XFS or writeback problem fom the stack trace, and > > > without more information or a reproducable test case I'm not going > > > to be able to understand the cause. > > > > > > Is the problem reproducable, or is it just a one-off? > > > > If it's reproducable it would be good to enable the xfs_writepage > > tracepoint and get a trace-cmd log of it. > > I hit it pretty reliably last night. I'll make a note to look into it > on monday with that enabled. You might want to grab the writeback tracepoints as well. Note that you'll probably have to filter by device so you don't get noise from all the other block devices, too. Cheers, Dave. -- Dave Chinner david@...morbit.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists