From: Tony Lindgren <tony@atomide.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>, Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <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 Kroah-Hartman <gregkh@linuxfoundation.org>,
Kemi Wang <kemi.wang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Regression in next with apps hanging with vm_fault_t
Date: Mon, 10 Sep 2018 11:21:43 -0700 [thread overview]
Message-ID: <20180910182143.GW5662@atomide.com> (raw)
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?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression in next with apps hanging with vm_fault_t
Date: Mon, 10 Sep 2018 11:21:43 -0700 [thread overview]
Message-ID: <20180910182143.GW5662@atomide.com> (raw)
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?
Regards,
Tony
next reply other threads:[~2018-09-10 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 18:21 Tony Lindgren [this message]
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 18:47 ` Souptick Joarder
2018-09-10 22:05 ` Stephen Rothwell
2018-09-10 22:05 ` Stephen Rothwell
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=20180910182143.GW5662@atomide.com \
--to=tony@atomide.com \
--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=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--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 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.