summaryrefslogtreecommitdiff
path: root/fs/bio-integrity.c
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@infradead.org>2012-07-02 06:00:04 -0400
committerBen Myers <bpm@sgi.com>2012-07-13 13:09:39 -0500
commit40a9b7963df32e743c45d79a5f41445fe2476f15 (patch)
treef764ef81befb876a05dc3166e8dfce1e057acba1 /fs/bio-integrity.c
parentaa292847b9fc6e187547110de833a7d3131bbddf (diff)
downloadlinux-3.10-40a9b7963df32e743c45d79a5f41445fe2476f15.tar.gz
linux-3.10-40a9b7963df32e743c45d79a5f41445fe2476f15.tar.bz2
linux-3.10-40a9b7963df32e743c45d79a5f41445fe2476f15.zip
xfs: prevent recursion in xfs_buf_iorequest
If the b_iodone handler is run in calling context in xfs_buf_iorequest we can run into a recursion where xfs_buf_iodone_callbacks keeps calling back into xfs_buf_iorequest because an I/O error happened, which keeps calling back into xfs_buf_iorequest. This chain will usually not take long because the filesystem gets shut down because of log I/O errors, but even over a short time it can cause stack overflows if run on the same context. As a short term workaround make sure we always call the iodone handler in workqueue context. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Ben Myers <bpm@sgi.com>
Diffstat (limited to 'fs/bio-integrity.c')
0 files changed, 0 insertions, 0 deletions