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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 14 Nov 2008 09:40:45 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Zhaolei <zhaolei@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org, jeremy@...source.com
Subject: Re: [PATCH] Release old elevator on change elevator

On Fri, Nov 14 2008, Zhaolei wrote:
> We should release old elevator when change to use a new one.
> 
> Signed-off-by: Zhao Lei <zhaolei@...fujitsu.com>
> ---
>  drivers/block/xen-blkfront.c |    8 +++++++-
>  1 files changed, 7 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
> index b220c68..2d19f0c 100644
> --- a/drivers/block/xen-blkfront.c
> +++ b/drivers/block/xen-blkfront.c
> @@ -338,12 +338,18 @@ wait:
>  static int xlvbd_init_blk_queue(struct gendisk *gd, u16 sector_size)
>  {
>  	struct request_queue *rq;
> +	elevator_t *old_e;
>  
>  	rq = blk_init_queue(do_blkif_request, &blkif_io_lock);
>  	if (rq == NULL)
>  		return -1;
>  
> -	elevator_init(rq, "noop");
> +	old_e = rq->elevator;
> +	if (IS_ERR_VALUE(elevator_init(rq, "noop")))
> +		printk(KERN_WARNING
> +			"blkfront: Switch elevator failed, use default\n");
> +	else
> +		elevator_exit(old_e);
>  
>  	/* Hard sector size and max sectors impersonate the equiv. hardware. */
>  	blk_queue_hardsect_size(rq, sector_size);
> -- 
> 1.5.5.3

I thought we'd already switched that to the nonrot flag, but that is
merged up for 2.6.29. So this looks appropriate for 2.6.28, I'll queue
it up.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ