Hi, The 1st patch handles bio error in dio_end_io() which is only used by btrfs. The 2nd patch uses bio_endio() to call .bi_end_io() in dio_end_io(). The 3rd patch avoids to call .bi_end_io recursively in complete path. xfstests(-g auto) is run over ext4, xfs and btrfs with this patchset and no regression is reported. With this patchset, lots of stack space can be saved in bio complete path. Even there was stack overflow report in bio complete path, see details in 3/3 commit log. V3: - no behaviour change - reorganize the function of unwind_bio_endio() and make it more clean V2: - introduce patch 1 & 2 - deal with running bio_endio() from process context, and makes generic/323 & generic/224 of xfstests happy on btrfs V1: - change to RFC - fix when unwind_bio_endio() is called recursively - run xfstest again: no regression found on ext4, but generic/323 and generic/224 cause kernel oops Ming Lei (3): fs: direct-io: handle error in dio_end_io() fs: direct-io: call .bi_end_io via bio_endio() bflock: avoid to call .bi_end_io() recursively block/bio.c | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++-- fs/direct-io.c | 8 +++----- 2 files changed, 56 insertions(+), 7 deletions(-) -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
