linux-kernel - Re: linux-next: Tree for May 1 (devtmpfs)

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]

Message-ID: <20090501225616.GA18064@kroah.com>
Date:	Fri, 1 May 2009 15:56:16 -0700
From:	Greg KH <greg@...ah.com>
To:	Chris Wedgwood <cw@...f.org>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Kay Sievers <kay.sievers@...y.org>
Subject: Re: linux-next: Tree for May 1 (devtmpfs)

On Fri, May 01, 2009 at 09:55:52AM -0700, Chris Wedgwood wrote:
> On Fri, May 01, 2009 at 08:28:33AM -0700, Randy Dunlap wrote:
> 
> > drivers/base/devtmpfs.c:41: error: implicit declaration of function 'vfs_mkdir'
> > drivers/base/devtmpfs.c:46: error: dereferencing pointer to incomplete type
> 
> [...]
> 
> Why is devtmpfs in linux-next?  My read of the thread so far seems to
> indicate there is considerable uncertainty that this is necessary or
> desirable.

As we discussed on irc, I think you no longer object to this, and see
how it solves a real problem, and can probably help out your initramfs
tools.

So it should stay in -next for now, and see if any build/use problems
happen with it.  I've been running it all this week on my machines just
fine.

thanks,

greg k-h
--
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/