• Rob N's avatar
    vdev_disk: ensure trim errors are returned immediately · e620d435
    Rob N authored
    After 06e25f9c
    
    , the discard issuing code was organised such that if
    requesting an async discard or secure erase failed before the IO was
    issued (that is, calling __blkdev_issue_discard() returned an error),
    the failed zio would never be executed, resulting in txg_sync hanging
    forever waiting for IO to finish.
    
    This commit fixes that by immediately executing a failed zio on error.
    To handle the successful synchronous op case, we fake an async op by,
    when not using an asynchronous submission method, queuing the successful
    result zio as part of the discard handler.
    
    Since it was hard to understand the differences between discard and
    secure erase, and sync and async, across different kernel versions, I've
    commented and reorganised the code a bit to try and make everything more
    contained and linear.
    
    Sponsored-by: Klara, Inc.
    Sponsored-by: Wasabi Technology, Inc.
    Reviewed-by: default avatarAmeer Hamza <ahamza@ixsystems.com>
    Reviewed-by: default avatarAlexander Motin <mav@FreeBSD.org>
    Reviewed-by: default avatarBrian Behlendorf <behlendorf1@llnl.gov>
    Signed-off-by: default avatarRob Norris <rob.norris@klarasystems.com>
    Closes #16070 
    e620d435
kernel-blkdev.m4 19.3 KB