Linux block layer
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@wdc.com>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Jan Kara <jack@suse.com>
Subject: Re: [PATCH v3 0/3] Fix races between blkcg code and request queue initialization and cleanup
Date: Wed, 21 Feb 2018 14:51:53 -0800	[thread overview]
Message-ID: <98646c21-9f4e-6014-1335-1f2d66bf9730@wdc.com> (raw)
In-Reply-To: <20180209184405.25835-1-bart.vanassche@wdc.com>

On 02/09/18 10:44, Bart Van Assche wrote:
> Recently Joseph Qi identified races between the block cgroup code and request
> queue initialization and cleanup. This patch series address these races. Please
> consider these patches for kernel v4.17.

Hello Joseph,

Can you add your Tested-by or Reviewed-by to the patches in this series?

Thanks,

Bart.

      parent reply	other threads:[~2018-02-21 22:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 18:44 [PATCH v3 0/3] Fix races between blkcg code and request queue initialization and cleanup Bart Van Assche
2018-02-09 18:44 ` [PATCH v3 1/3] block: Add a third argument to blk_alloc_queue_node() Bart Van Assche
2018-02-09 18:44 ` [PATCH v3 2/3] block: Fix a race between the cgroup code and request queue initialization Bart Van Assche
2018-02-09 18:44 ` [PATCH v3 3/3] block: Fix a race between request queue removal and the block cgroup controller Bart Van Assche
2018-02-22  2:25   ` Joseph Qi
2018-02-22  3:28     ` Ming Lei
2018-02-22 16:59     ` Bart Van Assche
2018-02-21 22:51 ` Bart Van Assche [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=98646c21-9f4e-6014-1335-1f2d66bf9730@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=jack@suse.com \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-block@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox