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
| ||
|
Date: Wed, 1 Nov 2017 16:01:36 +0100 From: Christoph Hellwig <hch@....de> To: Dave Chinner <david@...morbit.com> Cc: Cong Wang <xiyou.wangcong@...il.com>, Dave Chinner <dchinner@...hat.com>, darrick.wong@...cle.com, linux-xfs@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, Christoph Hellwig <hch@....de>, Al Viro <viro@...iv.linux.org.uk> Subject: Re: xfs: list corruption in xfs_setup_inode() On Wed, Nov 01, 2017 at 04:07:01PM +1100, Dave Chinner wrote: > > We are trying to make kdump working, but even if kdump works > > we still can't turn on panic_on_warn since this is production > > machine. > > Hmmm. Ok, maybe you could leave a trace of the xfs_iget* trace > points running and check the log tail for unusual events around the > time of the next crash. e.g. xfs_iget_reclaim_fail events. That > might point us to a potential interaction we can look at more > closely. I'd also suggest slab poisoning as well, as that will > catch other lifecycle problems that could be causing list > corruptions such as use-after-free. KASAN has also been really useful for these kinds of issues.
Powered by blists - more mailing lists