From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Guenter Roeck <linux@roeck-us.net>
Cc: David Howells <dhowells@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Widespread crashes in next-20180906
Date: Thu, 6 Sep 2018 10:04:13 -0400 [thread overview]
Message-ID: <20180906140413.GA5098@thunk.org> (raw)
In-Reply-To: <2e8e31f5-4db5-4907-2d09-f6444bc78ede@roeck-us.net>
On Thu, Sep 06, 2018 at 06:45:15AM -0700, Guenter Roeck wrote:
> Build results:
> total: 134 pass: 133 fail: 1
> Failed builds:
> sparc32:allmodconfig
> Qemu test results:
> total: 311 pass: 76 fail: 235
> Failed builds:
> <pretty much everything trying to boot from disk>
>
> Error message is always something like
>
> Filesystem requires source device
> VFS: Cannot open root device "hda" or unknown-block(3,0): error -2
>
> The only variance is the boot device. Logs in full glory are available
> at https://kerneltests.org/builders/, in the "next" column.
>
> I did not run bisect, but the recent filesystem changes are a definite suspect.
Yes, this is the vm_fault_t changes. See the other thread on LKML.
The guilty commit was: 83c0adddcc6e: fs: convert return type int to
vm_fault_t
This is the *second* time vm_fault_t patches have broken things. The
first time it went through the ext4 tree, and I NACK'ed it after
running a 60 second smoke test showed it was broken. The seocnd time
the problem was supposedly fixed, but it went through the mm tree, and
so I didn't have a chance regression test or stop it...
- Ted
next prev parent reply other threads:[~2018-09-06 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 13:45 Widespread crashes in next-20180906 Guenter Roeck
2018-09-06 14:04 ` Theodore Y. Ts'o [this message]
2018-09-06 14:13 ` Matt Hart
2018-09-06 15:23 ` Guenter Roeck
2018-09-06 19:14 ` Matt Hart
2018-09-06 19:43 ` Theodore Y. Ts'o
2018-09-07 14:49 ` Matt Hart
2018-09-06 15:41 ` Guenter Roeck
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=20180906140413.GA5098@thunk.org \
--to=tytso@mit.edu \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.