All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Jan Kara" <jack@suse.cz>, "Mika Penttilä" <mika.penttila@nextfour.com>
Cc: jack@suse.com, LKML <linux-kernel@vger.kernel.org>,
	Jeff Moyer <jmoyer@redhat.com>
Subject: Re: Fwd: 4.4-rc2 crash: block related
Date: Wed, 25 Nov 2015 09:30:39 -0700	[thread overview]
Message-ID: <5655E22F.6@kernel.dk> (raw)
In-Reply-To: <20151125083943.GJ25232@quack.suse.cz>

On 11/25/2015 01:39 AM, Jan Kara wrote:
> On Wed 25-11-15 08:27:56, Mika Penttilä wrote:
>> With recent block layer pull i see a 100% repeatable crash on boot while
>> mounting roots (ext4 partition on eMMC, with cfq io scheduler).
>
> Thanks for report! After some investigation I found out we allocate
> elevator specific data in __get_request() only for non-flush requests. And
> this is actually required since the flush machinery uses the space in
> struct request for something else. Doh. So my patch is just wrong and not
> easy to fix since at the time __get_request() is called we are not sure
> whether the flush machinery will be used in the end. Jens, please revert
> 1b2ff19e6a957b1ef0f365ad331b608af80e932e. Thanks!
>
> I'm somewhat surprised that you can reliably hit the race where flushing
> gets disabled for the device just while the request is in flight. But I
> guess during boot it makes some sense.

Yeah, that's impressive. I'll revert it and get it sent up before -rc3 
is cut.

-- 
Jens Axboe


      reply	other threads:[~2015-11-25 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25  6:04 4.4-rc2 crash: block related Mika Penttilä
     [not found] ` <565554EC.7050603@nextfour.com>
2015-11-25  8:39   ` Fwd: " Jan Kara
2015-11-25 16:30     ` Jens Axboe [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=5655E22F.6@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.penttila@nextfour.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.