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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 25 May 2020 08:52:34 +0200 From: Christoph Hellwig <hch@....de> To: "Theodore Y. Ts'o" <tytso@....edu> Cc: Al Viro <viro@...iv.linux.org.uk>, Christoph Hellwig <hch@....de>, linux-ext4@...r.kernel.org, jack@...e.cz, adilger@...ger.ca, riteshh@...ux.ibm.com, amir73il@...il.com, linux-fsdevel@...r.kernel.org, linux-unionfs@...r.kernel.org Subject: Re: fiemap cleanups v4 On Sun, May 24, 2020 at 03:17:13PM -0400, Theodore Y. Ts'o wrote: > > Hmmm... I can do an immutable shared branch, no problem. What would > > you prefer for a branchpoint for that one? > > I thought we had already agreed to run these patches through the ext4 > git tree, since most of the changes affect the ext4 tree (and there > aren't any other iomap fiemap changes pending as far as I know). > > The v3 versions of these patches have been part of the ext4 dev tree > since May 19th. Since the ext4 dev tree is rewinding, I can easily > update it fiemap-fixes patch to be on top of the first two patches > which Linus has already accepted, and then merge it into the ext4 dev > branch. I think we're all fine and set, unless Al really needs a shared branch. Based on what is in linux-next and out on the lists I don't see any real need, though.
Powered by blists - more mailing lists