linux-kernel - Re: [patch] brd: support barriers

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 15 Apr 2009 11:08:10 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Nick Piggin <npiggin@...e.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [patch] brd: support barriers

On Wed, Apr 15 2009, Nick Piggin wrote:
> Hi Jens,
> Do you have a tree I can send this though? Is this the right way to
> do what I want?

It'll let the barriers through, so I think it does what you want :-)
I can put it in the block tree.

> 
> --
> 
> brd is always ordered (not that it matters, as it is defined not to
> survive when the system goes down). So tell the block layer it is
> ordered, which might be of help with testing filesystems.
> 
> Signed-off-by: Nick Piggin <npiggin@...e.de>
> ---
>  drivers/block/brd.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> Index: linux-2.6/drivers/block/brd.c
> ===================================================================
> --- linux-2.6.orig/drivers/block/brd.c
> +++ linux-2.6/drivers/block/brd.c
> @@ -436,6 +436,7 @@ static struct brd_device *brd_alloc(int
>  	if (!brd->brd_queue)
>  		goto out_free_dev;
>  	blk_queue_make_request(brd->brd_queue, brd_make_request);
> +	blk_queue_ordered(brd->brd_queue, QUEUE_ORDERED_TAG, NULL);
>  	blk_queue_max_sectors(brd->brd_queue, 1024);
>  	blk_queue_bounce_limit(brd->brd_queue, BLK_BOUNCE_ANY);
>  

-- 
Jens Axboe

--
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/