diff options
| author | Dave Chinner | 2012-10-05 03:06:58 +0200 |
|---|---|---|
| committer | Ben Myers | 2012-10-19 00:41:56 +0200 |
| commit | 2455881c0b52f87be539c4c7deab1afff4d8a560 (patch) | |
| tree | ef2ed6c1f0f10727c929838992d89d54bb821993 /fs/xfs/xfs_iomap.c | |
| parent | xfs: zero allocation_args on the kernel stack (diff) | |
| download | kernel-qcow2-linux-2455881c0b52f87be539c4c7deab1afff4d8a560.tar.gz kernel-qcow2-linux-2455881c0b52f87be539c4c7deab1afff4d8a560.tar.xz kernel-qcow2-linux-2455881c0b52f87be539c4c7deab1afff4d8a560.zip | |
xfs: introduce XFS_BMAPI_STACK_SWITCH
Certain allocation paths through xfs_bmapi_write() are in situations
where we have limited stack available. These are almost always in
the buffered IO writeback path when convertion delayed allocation
extents to real extents.
The current stack switch occurs for userdata allocations, which
means we also do stack switches for preallocation, direct IO and
unwritten extent conversion, even those these call chains have never
been implicated in a stack overrun.
Hence, let's target just the single stack overun offended for stack
switches. To do that, introduce a XFS_BMAPI_STACK_SWITCH flag that
the caller can pass xfs_bmapi_write() to indicate it should switch
stacks if it needs to do allocation.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Mark Tinguely <tinguely@sgi.com>
Signed-off-by: Ben Myers <bpm@sgi.com>
Diffstat (limited to 'fs/xfs/xfs_iomap.c')
| -rw-r--r-- | fs/xfs/xfs_iomap.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c index f858b903678e..a066cf1766ab 100644 --- a/fs/xfs/xfs_iomap.c +++ b/fs/xfs/xfs_iomap.c @@ -575,7 +575,9 @@ xfs_iomap_write_allocate( * pointer that the caller gave to us. */ error = xfs_bmapi_write(tp, ip, map_start_fsb, - count_fsb, 0, &first_block, 1, + count_fsb, + XFS_BMAPI_STACK_SWITCH, + &first_block, 1, imap, &nimaps, &free_list); if (error) goto trans_cancel; |