From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
Matthew Wilcox <willy@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>, Theodore Ts'o <tytso@mit.edu>,
adilger.kernel@dilger.ca,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Jens Axboe <axboe@kernel.dk>, Eric Biggers <ebiggers@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg KH <gregkh@linuxfoundation.org>,
kemi.wang@intel.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: Regression in next with apps hanging with vm_fault_t
Date: Tue, 11 Sep 2018 08:05:03 +1000 [thread overview]
Message-ID: <20180911080503.62cb4699@canb.auug.org.au> (raw)
In-Reply-To: <CAFqt6zaRFW+bwVmWbMQ9ni9VJzsa1QMPRLFDCE6X0yQbvbPukw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
Hi all,
On Tue, 11 Sep 2018 00:17:45 +0530 Souptick Joarder <jrdr.linux@gmail.com> wrote:
>
> On Mon, Sep 10, 2018 at 11:51 PM Tony Lindgren <tony@atomide.com> wrote:
> >
> > 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.
OK, I have removed that commit (and the following fix patch) from
linux-next today (in case Andrew doesn't get around to it).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-09-10 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 18:21 Regression in next with apps hanging with vm_fault_t Tony Lindgren
2018-09-10 18:47 ` Souptick Joarder
2018-09-10 22:05 ` Stephen Rothwell [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=20180911080503.62cb4699@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=darrick.wong@oracle.com \
--cc=ebiggers@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jrdr.linux@gmail.com \
--cc=kemi.wang@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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