[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180906140744.GB5098@thunk.org>
Date: Thu, 6 Sep 2018 10:07:44 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: Souptick Joarder <jrdr.linux@...il.com>, Jan Kara <jack@...e.cz>,
syzbot+87a05ae4accd500f5242@...kaller.appspotmail.com,
ak@...ux.intel.com, Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Linux-MM <linux-mm@...ck.org>,
mgorman@...hsingularity.net, syzkaller-bugs@...glegroups.com,
tim.c.chen@...ux.intel.com, zwisler@...nel.org,
Matthew Wilcox <willy@...radead.org>
Subject: Re: linux-next test error
P.S. This is the second time the vm_fualt_t change has broken things.
The first time, when it went through the ext4 tree, I NACK'ed it after
a 60 seconds smoke test showed it was broken. This time it went
through the mm tree...
In the future, even for "trivial" changes, could you *please* run the
kvm-xfstests[1] or gce-xfstests[2][3]?
[1] https://github.com/tytso/xfstests-bld/blob/master/Documentation/kvm-quickstart.md
[2] https://github.com/tytso/xfstests-bld/blob/master/Documentation/gce-xfstests.md
[3] https:/thunk.org/gce-xfstests
Or if you're too lazy to run the smoke tests, please send it through
the ext4 tree so *I* can run the smoke tests.
- Ted
Powered by blists - more mailing lists