[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160615213320.GA9527@sucs.org>
Date: Wed, 15 Jun 2016 22:33:21 +0100
From: Sitsofe Wheeler <sitsofe@...il.com>
To: Arvind Kumar <arvindkumar@...are.com>
Cc: Tom Yan <tom.ty89@...il.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Shaohua Li <shli@...nel.org>, Jens Axboe <axboe@...nel.dk>,
VMware PV-Drivers <pv-drivers@...are.com>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Petr Vandrovec <petr@...are.com>
Subject: Re: BLKZEROOUT not zeroing md dev on VMDK
On Wed, Jun 15, 2016 at 06:17:37PM +0000, Arvind Kumar wrote:
> It is possibly some race. We saw a WRITE SAME related issue in past
> for which Petr sent out a patch but looks like the patch didn't make
> it. :(
>
> https://groups.google.com/forum/#!topic/linux.kernel/1WGDSlyY0y0
Indeed - the investigation you folks did is linked to within the
upstream Bugzilla bug (see
https://bugzilla.kernel.org/show_bug.cgi?id=118581#c2 ). Hopefully this
issue will be resolved but there's still some debate over on
http://thread.gmane.org/gmane.linux.kernel/2236800 . The problem is that
it is causing real problems in stable kernels (data not being correctly
zero'd) today...
--
Sitsofe | http://sucs.org/~sits/
Powered by blists - more mailing lists