aboutsummaryrefslogtreecommitdiff
path: root/block/blk-settings.c
diff options
context:
space:
mode:
authorGravatar Christoph Hellwig <hch@lst.de> 2024-03-13 19:16:23 -0700
committerGravatar Jens Axboe <axboe@kernel.dk> 2024-03-13 20:35:48 -0600
commitbf5e3a30f777b6e763f6a46c10e1250c20237e97 (patch)
tree766aa66fdfa4ef0856b664ef724ac6f84eab684d /block/blk-settings.c
parentRevert "block/mq-deadline: use correct way to throttling write requests" (diff)
downloadlinux-bf5e3a30f777b6e763f6a46c10e1250c20237e97.tar.gz
linux-bf5e3a30f777b6e763f6a46c10e1250c20237e97.tar.bz2
linux-bf5e3a30f777b6e763f6a46c10e1250c20237e97.zip
Revert "blk-lib: check for kill signal"
This reverts commit 8a08c5fd89b447a7de7eb293a7a274c46b932ba2. It turns out while this is a perfectly valid and long overdue thing to do for user initiated discards / zeroing from the ioctl handler, it actually breaks file system use of the discard helper by interrupting in places the file system doesn't expect, and by leaving the bio chain in a state that the file system callers of (at least) __blkdev_issue_discard do not expect. Revert the change for now, we'll redo it for the next merge window after refactoring the code to better split the file system vs ioctl callers and cleaning up a few other loose ends. Reported-by: Chandan Babu R <chandanbabu@kernel.org> Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Keith Busch <kbusch@kernel.org> Link: https://lore.kernel.org/r/20240314021623.1908895-1-hch@lst.de Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-settings.c')
0 files changed, 0 insertions, 0 deletions