| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | [PATCH 0/9] fixes for memory allocator recursions into the filesystem |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sat, 18 Jul 2009 18:14:52 -0400 |
| Cc: | sage@xxxxxxxxxxxx |
| User-agent: | quilt/0.47-1 |
lockdep has recently start tracking if a lock is used in reclaim context and if so warns if we do allocations without the NOFS flag inside it. This patch series fixes the easy targers involving the i_lock by switching various allocations to the NOFS variant, or in case of the growfs code moving the allocation out of the lock. We still have some more issues that involve the iolock, but I think we can simply get rid of the iolock in the reclaim path, but I'll send that our for a separate discussion. Sage, this should fix the two reports you've sent a while ago. |
| Previous by Date: | [PATCH 7/9] xfs: switch to NOFS allocation under i_lock in xfs_attr_rmtval_set, Christoph Hellwig |
|---|---|
| Next by Date: | [PATCH 8/9] xfs: switch to NOFS allocation under i_lock in xfs_readlink_bmap, Christoph Hellwig |
| Previous by Thread: | does XFS support block sizes other than 512 bytes?, Linda A. Walsh |
| Next by Thread: | [PATCH 6/9] xfs: switch to NOFS allocation under i_lock in xfs_buf_associate_memory, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |