[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFqt6zaRFW+bwVmWbMQ9ni9VJzsa1QMPRLFDCE6X0yQbvbPukw@mail.gmail.com>
Date: Tue, 11 Sep 2018 00:17:45 +0530
From: Souptick Joarder <jrdr.linux@...il.com>
To: Tony Lindgren <tony@...mide.com>
Cc: Matthew Wilcox <willy@...radead.org>,
Al Viro <viro@...iv.linux.org.uk>,
"Theodore Ts'o" <tytso@....edu>, adilger.kernel@...ger.ca,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Jens Axboe <axboe@...nel.dk>,
Eric Biggers <ebiggers@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Greg KH <gregkh@...uxfoundation.org>, kemi.wang@...el.com,
Andrew Morton <akpm@...ux-foundation.org>,
sfr@...b.auug.org.au, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-omap@...r.kernel.org
Subject: Re: Regression in next with apps hanging with vm_fault_t
On Mon, Sep 10, 2018 at 11:51 PM Tony Lindgren <tony@...mide.com> wrote:
>
> Hi,
>
> I'm seeing a regression with Linux next with commit 7b6ec2ae877a
> ("fs: convert return type int to vm_fault_t") where apps can just
> hang.
>
> The reproducable test case I have is to remove a distro package
> and then add it back where adding the package back just hangs and
> the package file seems corrupted.
>
> This is with ext4 rootfs on MMC, NFSroot does not have this
> issue. Any ideas?
This is a bad commit and there is a plan to remove it from all the tree.
Not sure why it is still showing in linux-next tree.
Powered by blists - more mailing lists