linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evan Green <evgreen@chromium.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-block <linux-block@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>
Subject: Re: blkdev_get deadlock
Date: Mon, 6 May 2019 08:31:37 -0700	[thread overview]
Message-ID: <CAE=gft58X0o+_=J81F1F8F5_N58mK+Nqs1zrsmtPC8JDj_Z1LA@mail.gmail.com> (raw)
In-Reply-To: <ca507480-0b06-5e4d-ebe6-464302d3af92@acm.org>

On Fri, May 3, 2019 at 6:15 PM Bart Van Assche <bvanassche@acm.org> wrote:
>
> On 5/3/19 10:47 AM, Evan Green wrote:
> > Hey blockies,
>   ^^^^^^^^^^^^
>
> That's the weirdest greeting I have encountered so far on the
> linux-block mailing list.

Heh, achievement unlocked.

>
> > I'm seeing a hung task in the kernel, and I wanted to share it in case
> > it's a known issue. I'm still trying to wrap my head around the stacks
> > myself. This is our Chrome OS 4.19 kernel, which is admittedly not
> > 100% vanilla mainline master, but we try to keep it pretty close.
> >
> > I can reproduce this reliably within our chrome OS installer, where
> > it's trying to dd from my system disk (NVMe) to a loop device backed
> > by a removable UFS card (4kb sectors) in a USB dongle.
>
> Although this is not the only possible cause such hangs are often caused
> by a block driver or SCSI LLD not completing a request. A list of
> pending requests can be obtained e.g. by running the attached script.

Thanks for the script. I'll try a few different combinations of dd
involving the UFS card to see if I can at least remove the system disk
from the equation. Hopefully the system will still be responsive
enough to run the script if I keep it in the right place and maybe
pre-warm it up. I also might try an older kernel, since if it's a
misbehaving block device as you suggest then all kernel versions
should lock up.

>
> Bart.

      reply	other threads:[~2019-05-06 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 17:47 blkdev_get deadlock Evan Green
2019-05-04  1:15 ` Bart Van Assche
2019-05-06 15:31   ` Evan Green [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='CAE=gft58X0o+_=J81F1F8F5_N58mK+Nqs1zrsmtPC8JDj_Z1LA@mail.gmail.com' \
    --to=evgreen@chromium.org \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).