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: <20090104011747.GI4758@mit.edu>
Date:	Sat, 3 Jan 2009 20:17:47 -0500
From:	Theodore Tso <tytso@....edu>
To:	Frank Mayhar <fmayhar@...gle.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] Allow ext4 to run without a journal.

On Sat, Jan 03, 2009 at 12:19:00PM -0800, Frank Mayhar wrote:
> On Sat, 2009-01-03 at 10:52 -0500, Theodore Tso wrote:
> > I've modified your patch to reflect the comments I made two weeks ago.
> > Were there any other changes you have planned?  I'd like to get this
> > pushed to Linus soon....
> 
> My apologies, I have a new patch that has been tested quite a bit more
> (although I still wouldn't say quite thoroughly yet, but close), all I
> need to do is set it up correctly for you guys and send it to the list.
> Unfortunately other stuff (including the holidays) has gotten in the
> way.  Expect it on Monday or Tuesday.  Note that this version will have
> a handful of small but important bugs fixed, as well.
> 
> One question:  Shold I make the patch relative to the stable tree or to
> the latest bits?

At this point can you make your patch relative to whatever you used
last time (and remind me what it is)?  Or, can you give me a delta
between what you did last time and what you have now that has the
fixes?  The problem is that the patch touches so much of ext4 that
it's quite painful to maintain it in the ext4 patch queue --- it
either invalidates a large number of patches after the fact, or the
patch needs a huge amount of work to fix up patch conflicts if it is
applied afterwards --- and if it is placed in the middle of the patch
queue, both conditions apply.

So I will have to do a lot of fix ups either way.  So unless you're
willing to pull down the ext4 patch queue, at:

	git://repo.or.cz/ext4-patch-queue.git

... and worry about making it apply in place, it's probably easier for
you to give me delta's versus the last patch, and I'll integrate in
the changes by hand.

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ