linux-kernel - Re: [PATCH] Add commandline partitions for block devices v2

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:	Wed, 23 Jun 2010 10:23:38 +0200
From:	Ulf Hansson <ulf.hansson@...ricsson.com>
To:	"Andries E. Brouwer" <Andries.Brouwer@....nl>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linus WALLEIJ <linus.walleij@...ricsson.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jens Axboe <jens.axboe@...cle.com>
Subject: Re: [PATCH] Add commandline partitions for block devices v2

Andries E. Brouwer wrote:
> On Tue, Jun 22, 2010 Andrew Morton wrote:
>   
>> On Tue, 8 Jun 2010 Linus Walleij wrote:
>>
>>     
>>> From: Ulf Hansson <ulf.hansson@...ricsson.com>
>>>
>>> This adds an option to pass in block device partitions from the kernel
>>> cmdline.
>>>
>>> The rationale is that in embedded systems we sometimes have no standard
>>> partition table available: often due to the fact that raw binary data is
>>> read out from the first sectors of the device by ROM code in ASICs. We
>>> have for a long time supplied custom partition information to embedded
>>> flash memories through the MTDparts interface which has similar
>>> semantics, and with the advent of embedded MMC block devices this now
>>> comes to standard block devices.
>>>       
>
> There exist ioctls BLKPG_ADD_PARTITION and BLKPG_DEL_PARTITION that
> allow one to add or remove partitions at run time, without having
> a partition table, or without having a partition table in a format
> understood by the kernel. Things can be done in user space.
>
> In general there are many things one would like the kernel to do at
> init time, and it is a bad idea to do all of this from the kernel
> command line. So adding options like these should be done only
> if it would be really awkward to do the same from an initial
> ramdisk.
>
> Andries
>
>   
I see your point!

Although, in an embedded system it is not always convenient to use an 
initial ramdisk. Instead your init program will be found directy from 
your rootfs, which means the kernel must itself be able to setup the 
partitions.

Regards
Uffe

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