On Jun 16, 2017, at 1:53 PM, Darrick J. Wong <darrick.wong@xxxxxxxxxx> wrote: > > Hi all, > > So I /think/ the xfs_attr_inactive crashes that both of you have been > seeing are a result of XFS assuming that there aren't ever any mapping > holes in the extended attribute fork and crashing when it tries to > grab a buffer for the hole and fails to notice that holes don't have > buffers. This lightly tested patch gets rid of /that/ problem. > > So, if you're willing, can you try this out and see if the crashes go > away? Granted, this might only enable us to lurch on whatever's next... I can give this a try. Now that you have an idea of what caused the issue, is there some way to (easily or not) reproduce it, ideally in userspace? Part of the problem we're having is that we can't reproduce it on a test machine so are forced to wait for it to happen in the field under load, where it inconveniences users. David -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
