All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "zhangxiaoxu (A)" <zhangxiaoxu5@huawei.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
	John Dorminy <jdorminy@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>,
	Heinz Mauelshagen <heinzm@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	dm-devel@redhat.com,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Alasdair G Kergon <agk@redhat.com>
Subject: Re: block: Fix a WRITE SAME BUG_ON
Date: Wed, 13 Feb 2019 21:31:16 -0500	[thread overview]
Message-ID: <yq1lg2jqex7.fsf@oracle.com> (raw)
In-Reply-To: <d693e299-3c7d-b3cb-e8c7-a1f94bba4697@huawei.com> (zhangxiaoxu's message of "Tue, 12 Feb 2019 11:11:29 +0800")


zhangxiaoxu,

> Any progress about the problme?
> Should we disable the write same when stack the different LBA disks?

Yes, please.

-- 
Martin K. Petersen	Oracle Linux Engineering

WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "zhangxiaoxu \(A\)" <zhangxiaoxu5@huawei.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Heinz Mauelshagen <heinzm@redhat.com>,
	John Dorminy <jdorminy@redhat.com>, <axboe@kernel.dk>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"Mike Snitzer" <snitzer@redhat.com>,
	<linux-block@vger.kernel.org>, <dm-devel@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>
Subject: Re: [dm-devel] block: Fix a WRITE SAME BUG_ON
Date: Wed, 13 Feb 2019 21:31:16 -0500	[thread overview]
Message-ID: <yq1lg2jqex7.fsf@oracle.com> (raw)
In-Reply-To: <d693e299-3c7d-b3cb-e8c7-a1f94bba4697@huawei.com> (zhangxiaoxu's message of "Tue, 12 Feb 2019 11:11:29 +0800")


zhangxiaoxu,

> Any progress about the problme?
> Should we disable the write same when stack the different LBA disks?

Yes, please.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2019-02-14  2:31 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25  2:11 [v2] block: Fix a WRITE SAME BUG_ON Zhang Xiaoxu
2019-01-26 11:17 ` John Dorminy
2019-01-26 11:17   ` [dm-devel] " John Dorminy
2019-01-28  5:48   ` zhangxiaoxu (A)
2019-01-28  5:48     ` [dm-devel] " zhangxiaoxu (A)
2019-01-28 22:14   ` Mike Snitzer
2019-01-28 22:14     ` Mike Snitzer
2019-01-29  4:54     ` Martin K. Petersen
2019-01-29  4:54       ` Martin K. Petersen
2019-01-29  8:52       ` Christoph Hellwig
2019-01-29  8:52         ` Christoph Hellwig
2019-01-30  6:50         ` zhangxiaoxu (A)
2019-01-30  6:50           ` zhangxiaoxu (A)
2019-01-30 14:08       ` John Dorminy
2019-01-30 14:08         ` John Dorminy
2019-01-31  0:58         ` zhangxiaoxu (A)
2019-01-31  0:58           ` zhangxiaoxu (A)
2019-01-31  2:23         ` Martin K. Petersen
2019-01-31  2:23           ` Martin K. Petersen
2019-01-31 10:39         ` Christoph Hellwig
2019-01-31 10:39           ` Christoph Hellwig
2019-01-31 19:41           ` John Dorminy
2019-01-31 19:41             ` John Dorminy
2019-02-01  7:35             ` Christoph Hellwig
2019-02-01  7:35               ` Christoph Hellwig
2019-02-01 14:09               ` John Dorminy
2019-02-01 14:09                 ` John Dorminy
2019-02-01 16:03                 ` Heinz Mauelshagen
2019-02-01 16:03                   ` [dm-devel] " Heinz Mauelshagen
2019-02-01 16:18                   ` Christoph Hellwig
2019-02-01 16:18                     ` [dm-devel] " Christoph Hellwig
2019-02-12  3:11                     ` zhangxiaoxu (A)
2019-02-12  3:11                       ` [dm-devel] " zhangxiaoxu (A)
2019-02-14  2:31                       ` Martin K. Petersen [this message]
2019-02-14  2:31                         ` Martin K. Petersen
2019-02-14  9:36                         ` zhangxiaoxu (A)
2019-02-14  9:36                           ` [dm-devel] " zhangxiaoxu (A)
2019-02-18 14:10                           ` zhangxiaoxu (A)
2019-02-18 14:10                             ` [dm-devel] " zhangxiaoxu (A)
2019-02-19 23:10                             ` Martin K. Petersen
2019-02-19 23:10                               ` [dm-devel] " Martin K. Petersen

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=yq1lg2jqex7.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=agk@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=heinzm@redhat.com \
    --cc=jdorminy@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=snitzer@redhat.com \
    --cc=zhangxiaoxu5@huawei.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.