Commit d62c251f authored by Christoph Hellwig's avatar Christoph Hellwig Committed by Lachlan McIlroy

[XFS] use KM_MAYFAIL in xfs_mountfs

Use KM_MAYFAIL for the m_perag allocation, we can deal with the error
easily and blocking forever during mount is not a good idea either.

SGI-PV: 981498

SGI-Modid: xfs-linux-melb:xfs-kern:31837a
Signed-off-by: default avatarChristoph Hellwig <hch@infradead.org>
Signed-off-by: default avatarLachlan McIlroy <lachlan@sgi.com>
parent ff4f038c
...@@ -1052,8 +1052,10 @@ xfs_mountfs( ...@@ -1052,8 +1052,10 @@ xfs_mountfs(
* Allocate and initialize the per-ag data. * Allocate and initialize the per-ag data.
*/ */
init_rwsem(&mp->m_peraglock); init_rwsem(&mp->m_peraglock);
mp->m_perag = mp->m_perag = kmem_zalloc(sbp->sb_agcount * sizeof(xfs_perag_t),
kmem_zalloc(sbp->sb_agcount * sizeof(xfs_perag_t), KM_SLEEP); KM_MAYFAIL);
if (!mp->m_perag)
goto error1;
mp->m_maxagi = xfs_initialize_perag(mp, sbp->sb_agcount); mp->m_maxagi = xfs_initialize_perag(mp, sbp->sb_agcount);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment