| 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
| ||
|
Message-ID: <20160208091644.GD27429@dastard> Date: Mon, 8 Feb 2016 20:16:44 +1100 From: Dave Chinner <david@...morbit.com> To: Christoph Hellwig <hch@....de> Cc: linux-fsdevel@...r.kernel.org, xfs@....sgi.com, linux-ext4@...r.kernel.org, ocfs2-devel@....oracle.com Subject: Re: [PATCH 2/3] xfs: don't use ioends for direct write completions On Mon, Feb 08, 2016 at 08:31:21AM +0100, Christoph Hellwig wrote: > On Mon, Feb 08, 2016 at 05:17:31PM +1100, Dave Chinner wrote: > > Right now this series is in a stable branch in the XFS tree: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git xfs-dio-fix-4.6 > > > > If you want to push it through some other tree, please let me know > > when/where it is committed so I can rebuild the XFS for-next branch > > appropriately from a stable commit/branch... > > That's how I think it should be handled. This would also allow the > ext4 and ocfs2 maintainers to depend on the stable branch to clean > up their direct I/O completion handling in this merge window if they > want to. I can't tell if you are saying what I've done is fine if the xfs-dio-fix-4.6 branch is stable (so others can pull it) or whether it should be in some other tree. Can you clarify, Christoph? Cheers, Dave. -- Dave Chinner david@...morbit.com -- 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