linux-kernel - Re: [GIT PATCH] driver core patches for 2.6.31-git

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:	Wed, 16 Sep 2009 08:45:33 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Greg KH <gregkh@...e.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] driver core patches for 2.6.31-git

On Tue, Sep 15, 2009 at 11:12:47AM -0700, Greg KH wrote:
> Here is the driver core patchset for the 2.6.31 merge window
> 
> It consists of a variety of different things:
> 	- devtmpfs.  This has been discussed a lot, is tiny,
> 	  self-contained, and has been acked by all of the major distros
> 	  as something they will use, and it has been used in the SuSE
> 	  kernels for quite some time now.

Grr, as Greg didn't Cc the actual patches to Linus here's the objection
again:

 - it mounts a filesystem into the init (aka global) namespace on mount
   for no good reason
 - it then manipulates it using the high-level VFS functions which it
   could just do on any filesystem if it really wanted

These lots of dicussions were basically people telling Greg that he
should come up wit ha real problem instead of just pushing it for it's
own sake.  Arjan And Eric have very well refuted the spped claim.

NACK from me from the VFS point of view - this is devfs 2.0, just worse
than the last version of devfs 1.  I would really really like to head
what the udev folks actually want instead of pushing in this crap.

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