From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Arvind Kumar <arvindkumar@vmware.com>
Cc: Tom Yan <tom.ty89@gmail.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Shaohua Li <shli@kernel.org>, Jens Axboe <axboe@kernel.dk>,
VMware PV-Drivers <pv-drivers@vmware.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Petr Vandrovec <petr@vmware.com>
Subject: Re: BLKZEROOUT not zeroing md dev on VMDK
Date: Wed, 15 Jun 2016 22:33:21 +0100 [thread overview]
Message-ID: <20160615213320.GA9527@sucs.org> (raw)
In-Reply-To: <1466014718999.6976@vmware.com>
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/
prev parent reply other threads:[~2016-06-15 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 22:39 BLKZEROOUT not zeroing md dev on VMDK Sitsofe Wheeler
2016-05-27 4:18 ` Darrick J. Wong
2016-05-27 4:45 ` Sitsofe Wheeler
2016-05-27 9:30 ` Tom Yan
2016-06-01 5:04 ` Sitsofe Wheeler
2016-06-15 18:17 ` Arvind Kumar
2016-06-15 18:17 ` Arvind Kumar
2016-06-15 21:33 ` Sitsofe Wheeler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160615213320.GA9527@sucs.org \
--to=sitsofe@gmail.com \
--cc=arvindkumar@vmware.com \
--cc=axboe@kernel.dk \
--cc=darrick.wong@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=petr@vmware.com \
--cc=pv-drivers@vmware.com \
--cc=shli@kernel.org \
--cc=tom.ty89@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.