linux-kernel - Re: [GIT PULL] Squashfs pull request for 2.6.29

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: <4966B24E.1050700@lougher.demon.co.uk>
Date:	Fri, 09 Jan 2009 02:11:26 +0000
From:	Phillip Lougher <phillip@...gher.demon.co.uk>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Christoph Hellwig <hch@...radead.org>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [GIT PULL] Squashfs pull request for 2.6.29

Andrew Morton wrote:
> On Thu, 8 Jan 2009 11:50:29 -0500 Christoph Hellwig <hch@...radead.org> wrote:
> 
>> On Thu, Jan 08, 2009 at 04:48:51PM +0000, Phillip Lougher wrote:
>>> Please consider pulling my linux-next branch
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/pkl/squashfs-linus.git
>>>
>>> The patches have been posted to LKML and linux-fsdevel over the last
>>> couple of months and have been reviewed and changed as requested.
>>> Diffstat below.
>>>
>>> Squashfs is a compressed read-only filesystem. It compresses metadata
>>> and data, and uses up to 1 MiB block sizes for greater compression.
>> That seems pretty fast for something only posted this week and not
>> even in -next.
> 
> I discussed this with Phillip a bit, and it looks like we'll go for a
> 2.6.21 merge.  This gives a couple of months for testing and review in
> linux-next.
> 
> Of course, this assumes that someone will actually perform that testing
> and review.  Chances are that it'll just sit there, getting nothing more
> than compilation testing.

Yes please review!  If people feels it needs a couple more months in
linux-next with more in-depth review then I'll live with that.  I'll
fix anything more that comes up, because I'm desperate to get it
mainlined.  I've lived the last couple of years with constant
moaning from people that I've not mainlined it, and I took
the last six months off work to work on it full time to get
it into shape to mainline.

Hopefully now it's at least in sufficient shape to go into
Linux-next I can get another job, and get some income which
will be nice.

> 
> Apparently I reviewed the code a while back - that grey cell must have
> died.  Does anyone else intend to review the code in that timeframe? 
> If not, we might as well merge it now, if ever..
> 

I'll be very happy for a merge now, but of course it's not up to me :-(

Phillip

> 

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