linux-kernel - Re: block: oopses on 4.13.*, 4.14.* and 4.15-rc2 (bisected)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20171218211931.1a447a9f@darkstar.example.org>
Date:   Mon, 18 Dec 2017 21:19:31 +0100
From:   Michele Ballabio <barra_cuda@...amail.com>
To:     Ming Lei <tom.leiming@...il.com>
Cc:     Jens Axboe <axboe@...nel.dk>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Christoph Hellwig <hch@....de>,
        linux-block <linux-block@...r.kernel.org>
Subject: Re: block: oopses on 4.13.*, 4.14.* and 4.15-rc2 (bisected)

On Mon, 18 Dec 2017 15:46:36 +0800
Ming Lei <tom.leiming@...il.com> wrote:

> On Sat, Dec 9, 2017 at 7:27 AM, Michele Ballabio
> <barra_cuda@...amail.com> wrote:
> > On Fri, 8 Dec 2017 13:08:37 -0700
> > Jens Axboe <axboe@...nel.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@...amail.com>