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
| ||
|
Date: Thu, 08 Sep 2011 09:29:54 +0800 From: Shaohua Li <shaohua.li@...el.com> To: lkml <linux-kernel@...r.kernel.org> Cc: Jens Axboe <jaxboe@...ionio.com>, Tejun Heo <htejun@...il.com>, Vivek Goyal <vgoyal@...hat.com> Subject: [RFC]block: don't mark flush request as SOFTBARRIER I'm wondering why flush request should be marked as SOFTBARRIER. Current flush sequence guarantees the correctness of flush even the request is reordered by ioscheduler. Signed-off-by: Shaohua Li <shaohua.li@...el.com> diff --git a/block/elevator.c b/block/elevator.c index a3b64bc..e589b76 100644 --- a/block/elevator.c +++ b/block/elevator.c @@ -715,7 +715,6 @@ void __elv_add_request(struct request_queue *q, struct request *rq, int where) break; case ELEVATOR_INSERT_FLUSH: - rq->cmd_flags |= REQ_SOFTBARRIER; blk_insert_flush(rq); break; default: -- 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