Skip to contentSkip to conversation

block, iomap: disable iopoll for split bio

PATCH Superseded Jeffle Xu 2 participants 8 messages Oct 16, 2020

Subsystems (3)

v3 of 9 Superseded Latest is v9 →

lore
Share & tools
lore

Jeffle Xu

author
#0 lore raw

v3 cover block, iomap: disable iopoll for split bio

This patchset is to fix the potential hang occurred in sync polling.

Please refer the following link for background info and the v1 patch:
https://patchwork.kernel.org/project/linux-block/patch/[email protected]/

The first patch disables iopoll for split bio in block layer, which is suggested by Ming Lei.

The second patch disables iopoll when one dio need to be split into multiple bios.

changes since v2:
- tune the line length of patch 1
- fix the condition checking whether split needed in patch 2

changes since v1:
- adopt the fix suggested by Ming Lei, to disable iopoll for split bio directly
- disable iopoll in direct IO routine of blkdev fs and iomap

Jeffle Xu (2):
block: disable iopoll for split bio
block,iomap: disable iopoll when split needed

 block/blk-merge.c    | 14 ++++++++++++++
 fs/block_dev.c       |  7 +++++++
 fs/iomap/direct-io.c |  8 ++++++++
 3 files changed, 29 insertions(+)
Signature · 1 line
2.27.0
author
#1 lore raw

PATCH v3 1/2 block: disable iopoll for split bio

iopoll is initially for small size, latency sensitive IO. It doesn't work well for big IO, especially when it needs to be split to multiple bios. In this case, the returned cookie of __submit_bio_noacct_mq() is indeed the cookie of the last split bio. The completion of *this* last split bio done by iopoll doesn't mean the whole original bio has completed. Callers of iopoll still need to wait for completion of other split bios.

Besides bio splitting may cause more trouble for iopoll which isn't supposed to be used in case of big IO.

iopoll for split bio may cause potential race if CPU migration happens during bio submission. Since the returned cookie is that of the last split bio, polling on the corresponding hardware queue doesn't help complete other split bios, if these split bios are enqueued into different hardware queues. Since interrupts are disabled for polling queues, the completion of these other split bios depends on timeout mechanism, thus causing a potential hang.

iopoll for split bio may also cause hang for sync polling. Currently both the blkdev and iomap-based fs (ext4/xfs, etc) support sync polling in direct IO routine. These routines will submit bio without REQ_NOWAIT flag set, and then start sync polling in current process context. The process may hang in blk_mq_get_tag() if the submitted bio has to be split into multiple bios and can rapidly exhaust the queue depth. The process are waiting for the completion of the previously allocated requests, which should be reaped by the following polling, and thus causing a deadlock.

To avoid these subtle trouble described above, just disable iopoll for split bio.

---
 block/blk-merge.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
block/blk-merge.c +14 -0
index bcf5e4580603..924db7c428b4 100644
@@ -279,6 +279,20 @@ static struct bio *blk_bio_segment_split(struct request_queue *q,
 	return NULL;
 split:
 	*segs = nsegs;
+
+	/*
+	 * bio splitting may cause more trouble for iopoll which isn't supposed
+	 * to be used in case of big IO.
+	 * iopoll is initially for small size, latency sensitive IO. It doesn't
+	 * work well for big IO, especially when it needs to be split to multiple
+	 * bios. In this case, the returned cookie of __submit_bio_noacct_mq()
+	 * is indeed the cookie of the last split bio. The completion of *this*
+	 * last split bio done by iopoll doesn't mean the whole original bio has
+	 * completed. Callers of iopoll still need to wait for completion of
+	 * other split bios.
+	 */
+	bio->bi_opf &= ~REQ_HIPRI;
+
 	return bio_split(bio, sectors, GFP_NOIO, bs);
 }
 
Signature · 1 line
2.27.0
#2 lore raw

Re: [PATCH v3 1/2] block: disable iopoll for split bio

Quoted 52 lines · Jeffle Xu

iopoll is initially for small size, latency sensitive IO. It doesn't work well for big IO, especially when it needs to be split to multiple bios. In this case, the returned cookie of __submit_bio_noacct_mq() is indeed the cookie of the last split bio. The completion of *this* last split bio done by iopoll doesn't mean the whole original bio has completed. Callers of iopoll still need to wait for completion of other split bios.

Besides bio splitting may cause more trouble for iopoll which isn't supposed to be used in case of big IO.

iopoll for split bio may cause potential race if CPU migration happens during bio submission. Since the returned cookie is that of the last split bio, polling on the corresponding hardware queue doesn't help complete other split bios, if these split bios are enqueued into different hardware queues. Since interrupts are disabled for polling queues, the completion of these other split bios depends on timeout mechanism, thus causing a potential hang.

iopoll for split bio may also cause hang for sync polling. Currently both the blkdev and iomap-based fs (ext4/xfs, etc) support sync polling in direct IO routine. These routines will submit bio without REQ_NOWAIT flag set, and then start sync polling in current process context. The process may hang in blk_mq_get_tag() if the submitted bio has to be split into multiple bios and can rapidly exhaust the queue depth. The process are waiting for the completion of the previously allocated requests, which should be reaped by the following polling, and thus causing a deadlock.

To avoid these subtle trouble described above, just disable iopoll for split bio.

---
 block/blk-merge.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
block/blk-merge.c +6 -0
index bcf5e4580603..924db7c428b4 100644
@@ -279,6 +279,20 @@ static struct bio *blk_bio_segment_split(struct request_queue *q,
 	return NULL;
 split:
 	*segs = nsegs;
+
+	/*
+	 * bio splitting may cause more trouble for iopoll which isn't supposed
+	 * to be used in case of big IO.
+	 * iopoll is initially for small size, latency sensitive IO. It doesn't
+	 * work well for big IO, especially when it needs to be split to multiple

block/blk-merge.c static struct bio *blk_bio_segment_split(struct request_queue *q, · line 297

Quoted 10 lines
block/blk-merge.c +8 -0
+	 * bios. In this case, the returned cookie of __submit_bio_noacct_mq()
+	 * is indeed the cookie of the last split bio. The completion of *this*
+	 * last split bio done by iopoll doesn't mean the whole original bio has
+	 * completed. Callers of iopoll still need to wait for completion of
+	 * other split bios.
+	 */
+	bio->bi_opf &= ~REQ_HIPRI;
+
 	return bio_split(bio, sectors, GFP_NOIO, bs);
 }

The above change may not be enough, since caller of submit_bio() still can call into blk_poll() even though REQ_HIPRI is cleared for splitted bio, for avoiding this issue:

- Either we may add check in blk_poll() to only allow hctx with HCTX_TYPE_POLL to poll,
- or return BLK_QC_T_NONE from blk_mq_submit_bio() if REQ_HIPRI is cleared.

thanks,
Ming

author
#3 lore raw

PATCH v3 2/2 block,iomap: disable iopoll when split needed

In reply to Jeffle Xu

Both blkdev fs and iomap-based fs (ext4, xfs, etc.) currently support sync iopoll. One single bio can contain at most BIO_MAX_PAGES, i.e. 256 bio_vec. If the input iov_iter contains more than 256 segments, then one dio will be split into multiple bios, which may cause potential deadlock for sync iopoll.

When it comes to sync iopoll, the bio is submitted without REQ_NOWAIT flag set and the process may hang in blk_mq_get_tag() if the dio needs to be split into multiple bios and thus can rapidly exhausts the queue depth. The process has to wait for the completion of the previously allocated requests, which should be reaped by the following sync polling, and thus causing a deadlock.

In fact there's a subtle difference of handling of HIPRI IO between blkdev fs and iomap-based fs, when dio need to be split into multiple bios. blkdev fs will set REQ_HIPRI for only the last split bio, leaving the previous bios queued into normal hardware queues, and not causing the trouble described above. iomap-based fs will set REQ_HIPRI for all split bios, and thus may cause the potential deadlock decribed above.

Thus disable iopoll when one dio need to be split into multiple bios. Though blkdev fs may not suffer this issue, still it may not make much sense to iopoll for big IO, since iopoll is initially for small size, latency sensitive IO.

---
 fs/block_dev.c       | 7 +++++++
 fs/iomap/direct-io.c | 8 ++++++++
 2 files changed, 15 insertions(+)
fs/block_dev.c +7 -0
index 9e84b1928b94..1b56b39e35b5 100644
@@ -436,6 +436,13 @@ __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages)
 			break;
 		}
 
+		/*
+		 * The current dio need to be split into multiple bios here.
+		 * iopoll is initially for small size, latency sensitive IO,
+		 * and thus disable iopoll if split needed.
+		 */
+		iocb->ki_flags &= ~IOCB_HIPRI;
+
 		if (!dio->multi_bio) {
 			/*
 			 * AIO needs an extra reference to ensure the dio
fs/iomap/direct-io.c +8 -0
index c1aafb2ab990..46668cceefd2 100644
@@ -308,6 +308,14 @@ iomap_dio_bio_actor(struct inode *inode, loff_t pos, loff_t length,
 		copied += n;
 
 		nr_pages = iov_iter_npages(dio->submit.iter, BIO_MAX_PAGES);
+		/*
+		 * The current dio need to be split into multiple bios here.
+		 * iopoll is initially for small size, latency sensitive IO,
+		 * and thus disable iopoll if split needed.
+		 */
+		if (nr_pages)
+			dio->iocb->ki_flags &= ~IOCB_HIPRI;
+
 		iomap_dio_submit_bio(dio, iomap, bio, pos);
 		pos += n;
 	} while (nr_pages);
Signature · 1 line
2.27.0
#4 lore raw

Re: [PATCH v3 2/2] block,iomap: disable iopoll when split needed

Quoted 36 lines · Jeffle Xu

Both blkdev fs and iomap-based fs (ext4, xfs, etc.) currently support sync iopoll. One single bio can contain at most BIO_MAX_PAGES, i.e. 256 bio_vec. If the input iov_iter contains more than 256 segments, then one dio will be split into multiple bios, which may cause potential deadlock for sync iopoll.

When it comes to sync iopoll, the bio is submitted without REQ_NOWAIT flag set and the process may hang in blk_mq_get_tag() if the dio needs to be split into multiple bios and thus can rapidly exhausts the queue depth. The process has to wait for the completion of the previously allocated requests, which should be reaped by the following sync polling, and thus causing a deadlock.

In fact there's a subtle difference of handling of HIPRI IO between blkdev fs and iomap-based fs, when dio need to be split into multiple bios. blkdev fs will set REQ_HIPRI for only the last split bio, leaving the previous bios queued into normal hardware queues, and not causing the trouble described above. iomap-based fs will set REQ_HIPRI for all split bios, and thus may cause the potential deadlock decribed above.

Thus disable iopoll when one dio need to be split into multiple bios. Though blkdev fs may not suffer this issue, still it may not make much sense to iopoll for big IO, since iopoll is initially for small size, latency sensitive IO.

---
 fs/block_dev.c       | 7 +++++++
 fs/iomap/direct-io.c | 8 ++++++++
 2 files changed, 15 insertions(+)
fs/block_dev.c +0 -0
index 9e84b1928b94..1b56b39e35b5 100644

fs/block_dev.c __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages) · line 445

Quoted 10 lines
fs/block_dev.c +7 -0
@@ -436,6 +436,13 @@ __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages)
 			break;
 		}
 
+		/*
+		 * The current dio need to be split into multiple bios here.
+		 * iopoll is initially for small size, latency sensitive IO,
+		 * and thus disable iopoll if split needed.
+		 */
+		iocb->ki_flags &= ~IOCB_HIPRI;
+

Not sure if it is good to clear IOCB_HIPRI of iocb, since it is usually maintained by upper layer code(io_uring, aio, ...) and we shouldn't touch this flag here.

Quoted 8 lines
fs/block_dev.c +0 -0
 		if (!dio->multi_bio) {
 			/*
 			 * AIO needs an extra reference to ensure the dio
fs/iomap/direct-io.c +0 -0
index c1aafb2ab990..46668cceefd2 100644

fs/iomap/direct-io.c iomap_dio_bio_actor(struct inode *inode, loff_t pos, loff_t length, · line 317

Quoted 10 lines
fs/iomap/direct-io.c +7 -0
@@ -308,6 +308,14 @@ iomap_dio_bio_actor(struct inode *inode, loff_t pos, loff_t length,
 		copied += n;
 
 		nr_pages = iov_iter_npages(dio->submit.iter, BIO_MAX_PAGES);
+		/*
+		 * The current dio need to be split into multiple bios here.
+		 * iopoll is initially for small size, latency sensitive IO,
+		 * and thus disable iopoll if split needed.
+		 */
+		if (nr_pages)
+			dio->iocb->ki_flags &= ~IOCB_HIPRI;

Same concern as above.

Thanks,
Ming

author
#5 lore raw

Re: [PATCH v3 2/2] block,iomap: disable iopoll when split needed

Quoted 40 lines · Ming Lei
Quoted 39 lines · Jeffle Xu

Both blkdev fs and iomap-based fs (ext4, xfs, etc.) currently support sync iopoll. One single bio can contain at most BIO_MAX_PAGES, i.e. 256 bio_vec. If the input iov_iter contains more than 256 segments, then one dio will be split into multiple bios, which may cause potential deadlock for sync iopoll.

When it comes to sync iopoll, the bio is submitted without REQ_NOWAIT flag set and the process may hang in blk_mq_get_tag() if the dio needs to be split into multiple bios and thus can rapidly exhausts the queue depth. The process has to wait for the completion of the previously allocated requests, which should be reaped by the following sync polling, and thus causing a deadlock.

In fact there's a subtle difference of handling of HIPRI IO between blkdev fs and iomap-based fs, when dio need to be split into multiple bios. blkdev fs will set REQ_HIPRI for only the last split bio, leaving the previous bios queued into normal hardware queues, and not causing the trouble described above. iomap-based fs will set REQ_HIPRI for all split bios, and thus may cause the potential deadlock decribed above.

Thus disable iopoll when one dio need to be split into multiple bios. Though blkdev fs may not suffer this issue, still it may not make much sense to iopoll for big IO, since iopoll is initially for small size, latency sensitive IO.

---
  fs/block_dev.c       | 7 +++++++
  fs/iomap/direct-io.c | 8 ++++++++
  2 files changed, 15 insertions(+)
fs/block_dev.c +0 -0
index 9e84b1928b94..1b56b39e35b5 100644
@@ -436,6 +436,13 @@ __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages)
  			break;
  		}
 
Quoted 10 lines

fs/block_dev.c __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages) · line 445

Quoted 7 lines
fs/block_dev.c +7 -0
+		/*
+		 * The current dio need to be split into multiple bios here.
+		 * iopoll is initially for small size, latency sensitive IO,
+		 * and thus disable iopoll if split needed.
+		 */
+		iocb->ki_flags &= ~IOCB_HIPRI;
+

Not sure if it is good to clear IOCB_HIPRI of iocb, since it is usually maintained by upper layer code(io_uring, aio, ...) and we shouldn't touch this flag here.

If we queue bios into the DEFAULT hardware queue, but leaving the corresponding kiocb->ki_flags's

IOCB_HIPRI set (exactly what the first patch does), is this another inconsistency?

Please consider the following code snippet from __blkdev_direct_IO()

```
	for (;;) {
		set_current_state(TASK_UNINTERRUPTIBLE);
		if (!READ_ONCE(dio->waiter))
			break;

		if (!(iocb->ki_flags & IOCB_HIPRI) ||
		    !blk_poll(bdev_get_queue(bdev), qc, true))
			blk_io_schedule();
	}
```

The IOCB_HIPRI flag is still set in iocb->ki_flags, but the corresponding bios are queued into DEFAULT hardware queue since the first patch. blk_poll() is still called in this case.

Quoted 23 lines
Quoted 9 lines
fs/block_dev.c +0 -0
  		if (!dio->multi_bio) {
  			/*
  			 * AIO needs an extra reference to ensure the dio
fs/iomap/direct-io.c +0 -0
index c1aafb2ab990..46668cceefd2 100644

fs/iomap/direct-io.c iomap_dio_bio_actor(struct inode *inode, loff_t pos, loff_t length, · line 317

Quoted 10 lines
fs/iomap/direct-io.c +7 -0
@@ -308,6 +308,14 @@ iomap_dio_bio_actor(struct inode *inode, loff_t pos, loff_t length,
  		copied += n;
 
  		nr_pages = iov_iter_npages(dio->submit.iter, BIO_MAX_PAGES);
+		/*
+		 * The current dio need to be split into multiple bios here.
+		 * iopoll is initially for small size, latency sensitive IO,
+		 * and thus disable iopoll if split needed.
+		 */
+		if (nr_pages)
+			dio->iocb->ki_flags &= ~IOCB_HIPRI;

Same concern as above.

Thanks,
Ming

#6 lore raw

Re: [PATCH v3 2/2] block,iomap: disable iopoll when split needed

Quoted 52 lines · JeffleXu
Quoted 41 lines · Ming Lei
Quoted 40 lines · Jeffle Xu

Both blkdev fs and iomap-based fs (ext4, xfs, etc.) currently support sync iopoll. One single bio can contain at most BIO_MAX_PAGES, i.e. 256 bio_vec. If the input iov_iter contains more than 256 segments, then one dio will be split into multiple bios, which may cause potential deadlock for sync iopoll.

When it comes to sync iopoll, the bio is submitted without REQ_NOWAIT flag set and the process may hang in blk_mq_get_tag() if the dio needs to be split into multiple bios and thus can rapidly exhausts the queue depth. The process has to wait for the completion of the previously allocated requests, which should be reaped by the following sync polling, and thus causing a deadlock.

In fact there's a subtle difference of handling of HIPRI IO between blkdev fs and iomap-based fs, when dio need to be split into multiple bios. blkdev fs will set REQ_HIPRI for only the last split bio, leaving the previous bios queued into normal hardware queues, and not causing the trouble described above. iomap-based fs will set REQ_HIPRI for all split bios, and thus may cause the potential deadlock decribed above.

Thus disable iopoll when one dio need to be split into multiple bios. Though blkdev fs may not suffer this issue, still it may not make much sense to iopoll for big IO, since iopoll is initially for small size, latency sensitive IO.

---
  fs/block_dev.c       | 7 +++++++
  fs/iomap/direct-io.c | 8 ++++++++
  2 files changed, 15 insertions(+)
fs/block_dev.c +2 -0
index 9e84b1928b94..1b56b39e35b5 100644
@@ -436,6 +436,13 @@ __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages)
  			break;
  		}
+		/*
+		 * The current dio need to be split into multiple bios here.
Quoted 8 lines

fs/block_dev.c __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages) · line 445

Quoted 5 lines
fs/block_dev.c +5 -0
+		 * iopoll is initially for small size, latency sensitive IO,
+		 * and thus disable iopoll if split needed.
+		 */
+		iocb->ki_flags &= ~IOCB_HIPRI;
+

Not sure if it is good to clear IOCB_HIPRI of iocb, since it is usually maintained by upper layer code(io_uring, aio, ...) and we shouldn't touch this flag here.

Quoted 5 lines

If we queue bios into the DEFAULT hardware queue, but leaving the corresponding kiocb->ki_flags's

IOCB_HIPRI set (exactly what the first patch does), is this another inconsistency?

My question is that if it is good for this code to clear IOCB_HIPRI of iocb, given this is the 1st such usage. And does io_uring implementation expect the flag to be cleared by lower layer?

Quoted 15 lines

Please consider the following code snippet from __blkdev_direct_IO()

```
	for (;;) {
		set_current_state(TASK_UNINTERRUPTIBLE);
		if (!READ_ONCE(dio->waiter))
			break;

		if (!(iocb->ki_flags & IOCB_HIPRI) ||
		    !blk_poll(bdev_get_queue(bdev), qc, true))
			blk_io_schedule();
	}
```
Quoted 3 lines

The IOCB_HIPRI flag is still set in iocb->ki_flags, but the corresponding bios are queued into DEFAULT hardware queue since the first patch. blk_poll() is still called in this case.

It may be handled in the following way:

if (!((iocb->ki_flags & IOCB_HIPRI) && !dio->multi_bio) ||
!blk_poll(bdev_get_queue(bdev), qc, true))
blk_io_schedule();

BTW, even for single bio with IOCB_HIPRI, the single fs bio can still be splitted, and blk_poll() will be called too.

Thanks,
Ming

author
#7 lore raw

Re: [PATCH v3 2/2] block,iomap: disable iopoll when split needed

Quoted 51 lines · Ming Lei
Quoted 50 lines · JeffleXu
Quoted 49 lines · Ming Lei
Quoted 36 lines · Jeffle Xu

Both blkdev fs and iomap-based fs (ext4, xfs, etc.) currently support sync iopoll. One single bio can contain at most BIO_MAX_PAGES, i.e. 256 bio_vec. If the input iov_iter contains more than 256 segments, then one dio will be split into multiple bios, which may cause potential deadlock for sync iopoll.

When it comes to sync iopoll, the bio is submitted without REQ_NOWAIT flag set and the process may hang in blk_mq_get_tag() if the dio needs to be split into multiple bios and thus can rapidly exhausts the queue depth. The process has to wait for the completion of the previously allocated requests, which should be reaped by the following sync polling, and thus causing a deadlock.

In fact there's a subtle difference of handling of HIPRI IO between blkdev fs and iomap-based fs, when dio need to be split into multiple bios. blkdev fs will set REQ_HIPRI for only the last split bio, leaving the previous bios queued into normal hardware queues, and not causing the trouble described above. iomap-based fs will set REQ_HIPRI for all split bios, and thus may cause the potential deadlock decribed above.

Thus disable iopoll when one dio need to be split into multiple bios. Though blkdev fs may not suffer this issue, still it may not make much sense to iopoll for big IO, since iopoll is initially for small size, latency sensitive IO.

---
   fs/block_dev.c       | 7 +++++++
   fs/iomap/direct-io.c | 8 ++++++++
   2 files changed, 15 insertions(+)
fs/block_dev.c +0 -0
index 9e84b1928b94..1b56b39e35b5 100644

fs/block_dev.c __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages) · line 444

Quoted 9 lines
fs/block_dev.c +7 -0
@@ -436,6 +436,13 @@ __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages)
   			break;
   		}
+		/*
+		 * The current dio need to be split into multiple bios here.
+		 * iopoll is initially for small size, latency sensitive IO,
+		 * and thus disable iopoll if split needed.
+		 */
+		iocb->ki_flags &= ~IOCB_HIPRI;
+

Not sure if it is good to clear IOCB_HIPRI of iocb, since it is usually maintained by upper layer code(io_uring, aio, ...) and we shouldn't touch this flag here.

Quoted 8 lines
Quoted 5 lines

If we queue bios into the DEFAULT hardware queue, but leaving the corresponding kiocb->ki_flags's

IOCB_HIPRI set (exactly what the first patch does), is this another inconsistency?

My question is that if it is good for this code to clear IOCB_HIPRI of iocb, given this is the 1st such usage. And does io_uring implementation expect the flag to be cleared by lower layer?

I know your point. I will check code in io_uring later.

Quoted 18 lines
Quoted 15 lines

Please consider the following code snippet from __blkdev_direct_IO()

```
	for (;;) {
		set_current_state(TASK_UNINTERRUPTIBLE);
		if (!READ_ONCE(dio->waiter))
			break;

		if (!(iocb->ki_flags & IOCB_HIPRI) ||
		    !blk_poll(bdev_get_queue(bdev), qc, true))
			blk_io_schedule();
	}
```
Quoted 3 lines

The IOCB_HIPRI flag is still set in iocb->ki_flags, but the corresponding bios are queued into DEFAULT hardware queue since the first patch. blk_poll() is still called in this case.

Quoted 8 lines

It may be handled in the following way:

  		if (!((iocb->ki_flags & IOCB_HIPRI) && !dio->multi_bio) ||
  		    !blk_poll(bdev_get_queue(bdev), qc, true))
  				blk_io_schedule();

BTW, even for single bio with IOCB_HIPRI, the single fs bio can still be splitted, and blk_poll() will be called too.

Yes that's exactly I'm concerned and I've seen your comments in patch 1. Thanks.

Quoted 4 lines

Thanks,
Ming