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, 7 May 2009 04:40:29 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Greg KH <greg@...ah.com>, Jan Blunck <jblunck@...e.de>
Subject: Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev tmpfs

On Thu, May 7, 2009 at 04:25, Arjan van de Ven <arjan@...radead.org> wrote:
> On Thu, 7 May 2009 04:08:33 +0200
> Kay Sievers <kay.sievers@...y.org> wrote:
>>
>> How will you solve the dynamic device numbers? They are a complete
>> reality today.
>
> not for storage though...

Oh sure:
  cat /sys/class/block/sd*/dev
  259:524288
  259:262144
  259:786432
  259:131072
  259:0
  259:393216
  259:655360

That's the box I write this from. It's experimental now but in the
upstream kernel. Distros want to support more than 15 partitions, so
that will happen sooner than later.

And you may talk to the wrong rtc device, if you use static nodes, and
so on. There are just too many things that can go wrong, and distros
that don't have a very limited set of hardware, can not take the risk
of a static /dev. They don't have this today, and will not go back to
it. That's why we are coming up with this.

> and for the rest udev is fast enough in
> practice....

Sure, but you still have the transition to the tmpfs /dev, and during
that you are very limited in what you can do, and this addresses
devtmpfs.

Thanks,
Kay
--
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