Linux block layer
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Dennis Zhou <dennis@kernel.org>
Subject: Re: block: percpu ref (blkg_release) <= 0 (0) after switching to atomic
Date: Wed, 19 Dec 2018 11:27:39 +0800	[thread overview]
Message-ID: <20181219032738.GB4451@ming.t460p> (raw)
In-Reply-To: <20181219032520.GA4451@ming.t460p>

On Wed, Dec 19, 2018 at 11:25:21AM +0800, Ming Lei wrote:
> Hi Jens and Dennis,
> 
> The following warning can be triggered on for-4.21/block when running
> xfstests generic/475(xfs), and it is introduced by recent Dennis's patches.
> 
> test disk: virtio-blk
> scratch: nvme-pci disk

oops, the test disk is virtio-scsi, and seems it isn't easy to trigger
on virtio-blk.


Thanks,
Ming

  reply	other threads:[~2018-12-19  3:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19  3:25 block: percpu ref (blkg_release) <= 0 (0) after switching to atomic Ming Lei
2018-12-19  3:27 ` Ming Lei [this message]
2018-12-19  4:32   ` Jens Axboe

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=20181219032738.GB4451@ming.t460p \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dennis@kernel.org \
    --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