| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1287676486-19645-1-git-send-email-lczerner@redhat.com> Date: Thu, 21 Oct 2010 17:54:46 +0200 From: Lukas Czerner <lczerner@...hat.com> To: linux-ext4@...r.kernel.org Cc: tytso@....edu, sandeen@...hat.com, adilger@...ger.ca, axboe@...nel.dk, linux-kernel@...r.kernel.org, lczerner@...hat.com Subject: [PATCH] block: Make blkdev_issue_discard() interruptible Since the discard may take quite long time, especially with really big extents (like the whole device for example), it would be nice to give to users the opportunity to abort it. This is especially useful for mkfs, when user can not know in advance how long it will take. In conjunction with mke2fs patch "Inform user about ongoing discard" it gives the user all the comfort of being informed about discard and being able to abort the operation. Signed-off-by: Lukas Czerner <lczerner@...hat.com> --- block/blk-lib.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/block/blk-lib.c b/block/blk-lib.c index 1a320d2..db44671 100644 --- a/block/blk-lib.c +++ b/block/blk-lib.c @@ -91,6 +91,9 @@ int blkdev_issue_discard(struct block_device *bdev, sector_t sector, bio_get(bio); submit_bio(type, bio); + if (unlikely(fatal_signal_pending(current))) + ret = -ERESTARTSYS; + wait_for_completion(&wait); if (bio_flagged(bio, BIO_EOPNOTSUPP)) -- 1.7.2.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists