linux-kernel - Re: [PATCH] loop: add management interface for on-demand device allocation

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Jul 2011 12:17:55 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Jens Axboe <jaxboe@...ionio.com>, Karel Zak <kzak@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] loop: add management interface for on-demand device
 allocation

Hello, Kay.

On Tue, Jul 26, 2011 at 01:50:30PM +0200, Kay Sievers wrote:
> From: Kay Sievers <kay.sievers@...y.org>
> Subject: loop: add management interface for on-demand device allocation
> 
> Loop devices today have a fixed pre-allocated number of usually 8.
> The number can only be changed at init time. To find a free device
> to use, /dev/loop%i needs to be scanned and all devices need to be
> opened.

It generally looks good to me but I really hope it were split into
multiple patches.  I think it's a bit too big and doing too many
different things.  Can you please split it up?

> +static int loop_lookup(struct loop_device **lo, int nr);
> +static int loop_add(struct loop_device **lo, int nr);

Also, can't these return loop_device * and ERR_PTR() value on errors?

Thanks.

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