[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170108164321.GA31687@lst.de>
Date: Sun, 8 Jan 2017 17:43:21 +0100
From: Christoph Hellwig <hch@....de>
To: Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc: Christoph Hellwig <hch@....de>, linux-xfs@...r.kernel.org,
Dave Chinner <david@...morbit.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Al Viro <viro@...IV.linux.org.uk>,
James Morris <jmorris@...ei.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Safford <david.safford@...com>
Subject: Re: xfs: commit 6552321831dc "xfs: remove i_iolock and use
i_rwsem in the VFS inode instead" change causes hang
On Sun, Jan 08, 2017 at 11:38:26AM -0500, Mimi Zohar wrote:
> We definitely need VFS help in resolving this regression. As a last
> resort, we could always update the default IMA builtin policy to exclude
> XFS.
No, you need to explicitly white list file system that are supported,
and most importantly actually tested using an automated tesuite.
Powered by blists - more mailing lists