public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* xfs readdir hang on for-next (3.15.0-rc1)
@ 2014-04-14 16:43 Brian Foster
  2014-04-14 19:08 ` Brian Foster
  0 siblings, 1 reply; 5+ messages in thread
From: Brian Foster @ 2014-04-14 16:43 UTC (permalink / raw)
  To: xfs

Hi all,

This is a heads up that I'm seeing a blatant readdir hang on the current
for-next with selinux enabled. To reproduce, I format a clean fs, mount
and attempt an ls.

The problem does not occur with selinux disabled, if I back out the
following commit:

40194ecc6d78 xfs: reinstate the ilock in xfs_readdir

... or if I remove the locking around xfs_attr_get(), so I suspect this
is another instance of a recursive deadlock. I'm getting no output
whatsoever in order to confirm this and it also leads to a complete
system lockup. It's also interesting that this hasn't been observed
until now, given the above commit was introduced in 3.14. So the above
commit doesn't appear to be the most recent change that triggers this.

I reproduced on the latest linus tree and do not reproduce on 3.14, so
I'm trying to do a bisect to find out what else might have changed to
trigger this.

Brian

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2014-04-14 22:06 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-14 16:43 xfs readdir hang on for-next (3.15.0-rc1) Brian Foster
2014-04-14 19:08 ` Brian Foster
2014-04-14 20:57   ` Peter Zijlstra
2014-04-14 21:47     ` Michael L. Semon
2014-04-14 22:06     ` Brian Foster

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox