From: Michele Ballabio <barra_cuda@katamail.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: block: oopses on 4.13.*, 4.14.* and 4.15-rc2 (bisected)
Date: Mon, 18 Dec 2017 21:19:31 +0100 [thread overview]
Message-ID: <20171218211931.1a447a9f@darkstar.example.org> (raw)
In-Reply-To: <CACVXFVPYYGx8Q25kC+ugReK1wixOmjj2EUVY+Mr2x9Rh5prLrQ@mail.gmail.com>
On Mon, 18 Dec 2017 15:46:36 +0800
Ming Lei <tom.leiming@gmail.com> wrote:
> On Sat, Dec 9, 2017 at 7:27 AM, Michele Ballabio
> <barra_cuda@katamail.com> wrote:
> > On Fri, 8 Dec 2017 13:08:37 -0700
> > Jens Axboe <axboe@kernel.dk> wrote:
> >
> >> On 12/08/2017 08:38 AM, Michele Ballabio wrote:
> >> > Hi,
> >> > kernels 4.13.*, 4.14.* 4.15-rc2 crash on occasion,
> >> > especially on x86-32 systems. To trigger the problem, run as
> >> > root:
> >> >
> >> > while true
> >> > do
> >> > /sbin/udevadm trigger --type=subsystems --action=change
> >> > /sbin/udevadm trigger --type=devices --action=change
> >> > /sbin/udevadm settle --timeout=120
> >> > done
> >> >
> >> > (Thanks to Patrick Volkerding for the reproducer).
> >> >
> >> > Sometimes the kernel oopses immediately, sometimes a bit later
> >> > (less than five minutes).
> >> >
> >> > The bisection pointed to commit
> >> > caa4b02476e31fc7933d2138062f7f355d3cd8f7 (blk-map: call
> >> > blk_queue_bounce from blk_rq_append_bio). A revert fixes the
> >> > problem (tested on 4.13 and master).
> >>
> >> Thanks for your report - can you try the below patch? Totally
> >> untested...
> >
> > I applied the patch on master
> > (968edbd93c0cbb40ab48aca972392d377713a0c3), I tried two times to
> > boot the system but couldn't get to the shell. I found this in the
> > log:
>
> Hi Michele,
>
> Please test the patches I sent out and see if it fixes your issue. In
> my environment
> the two just works fine.
>
> https://marc.info/?l=linux-block&m=151358285916762&w=2
>
I can confirm these fixes the issue on my system (tested on top of
4.15-rc3), thanks!
Tested-by: Michele Ballabio <barra_cuda@katamail.com>
next prev parent reply other threads:[~2017-12-18 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 15:38 block: oopses on 4.13.*, 4.14.* and 4.15-rc2 (bisected) Michele Ballabio
2017-12-08 20:08 ` Jens Axboe
2017-12-08 23:27 ` Michele Ballabio
2017-12-18 7:46 ` Ming Lei
2017-12-18 20:19 ` Michele Ballabio [this message]
2017-12-08 23:54 ` Ming Lei
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=20171218211931.1a447a9f@darkstar.example.org \
--to=barra_cuda@katamail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.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.