From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43862)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jcody@redhat.com>) id 1asTDS-00051Z-9C
	for qemu-devel@nongnu.org; Tue, 19 Apr 2016 06:49:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jcody@redhat.com>) id 1asTDO-0005cz-73
	for qemu-devel@nongnu.org; Tue, 19 Apr 2016 06:49:10 -0400
Received: from mx1.redhat.com ([209.132.183.28]:55020)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jcody@redhat.com>) id 1asTDO-0005cU-1e
	for qemu-devel@nongnu.org; Tue, 19 Apr 2016 06:49:06 -0400
Date: Tue, 19 Apr 2016 06:49:01 -0400
From: Jeff Cody <jcody@redhat.com>
Message-ID: <20160419104901.GB4841@localhost.localdomain>
References: <CAFEAcA9jNjeqFMa6KjkSuc_xGzs6BDF8A-A5_A_qpk9g798zPA@mail.gmail.com>
	<20160419091012.GA4498@noname.str.redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160419091012.GA4498@noname.str.redhat.com>
Subject: Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6
 release!
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, QEMU Developers <qemu-devel@nongnu.org>

On Tue, Apr 19, 2016 at 11:10:12AM +0200, Kevin Wolf wrote:
> Am 18.04.2016 um 13:22 hat Peter Maydell geschrieben:
> > Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> > the mailing list we seem to be in reasonable shape for the 2.6 release.
> > I would ideally like the 2.6rc3 tarball which we will make later this
> > week to be the final one before full release.
> > 
> > This is therefore the last call for any bugs that need to be fixed
> > for 2.6 or patches that must go in. If you have anything you think
> > should go into 2.6 please either add it to the "still unfixed in
> > master" part of the planning wiki page or follow up to this email to
> > describe it/link to the relevant patches/etc.
> 
> Jeff, I still don't see a v2 gluster patch to avoid data corruption
> after I/O errors. I think we agreed that we definitely need this in 2.6.
>

Yes, I'm working on a good test for the patch still.  I'll go ahead and send
the patch for any comments now, though, and hopefully can have the testing
done later today.