linux-ext4 - ext4 changes in linux-next

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-next>] [day] [month] [year] [list]

Message-Id: <20090107140436.46a17a3e.akpm@linux-foundation.org>
Date:	Wed, 7 Jan 2009 14:04:36 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org
Subject: ext4 changes in linux-next

Ted,

a pile of new ext4 stuff just turned up in linux-next.  This means that
I had to rework
filesystem-freeze-add-error-handling-of-write_super_lockfs-unlockfs.patch
a little bit, and that patch now has a dependency upon the newly-added
ext4 patches.

I assume those one-day-old changes are targetted at 2.6.20, so I'll
need to undo that fix when I send
filesystem-freeze-add-error-handling-of-write_super_lockfs-unlockfs.patch
(perhaps today) and this will then cause conflicts in ext4 and/pr
linux-next.

It's not a big problem in this case, but this is why we ask that new
work not be added into linux-next until 2.6.x-rc1 has been cut.

Ta.
--
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