[PATCH v2 0/3] jbd2: check return value of blkdev_issue_flush()

[guolingxing]

Check the return value of blkdev_issue_flush() in three JBD2 paths
where it was ignored, and abort the journal on failure. This prevents
journal tail updates or successful transaction completion from
proceeding without the required cache flush succeeding.

Changes since v1:
- 1/3: collected Reviewed-by from Jan Kara.
- 2/3: reuse the existing err variable instead of declaring a new
  one that shadows it, per review from Jan Kara.
- 3/3: use flush_err to avoid shadowing err, preserve any earlier
  commit-record error, and reuse the existing abort handling,
  as suggested by Jan Kara.

guolingxing (3):
  jbd2: check return value of blkdev_issue_flush() when checkpointing
  jbd2: check return value of blkdev_issue_flush() when committing
  jbd2: check return value of blkdev_issue_flush() for async commits

 fs/jbd2/checkpoint.c | 10 ++++++++--
 fs/jbd2/commit.c     | 13 ++++++++++---
 2 files changed, 18 insertions(+), 5 deletions(-)

-- 
2.34.1