[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+ajxhUaRg+XSuqQZN8rD96S820yMTWx2GpRVRb9Maz50g@mail.gmail.com>
Date: Thu, 6 Sep 2018 10:52:59 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: David Howells <dhowells@...hat.com>
Cc: syzbot <syzbot+762a577f56cfb1574647@...kaller.appspotmail.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Levin, Alexander" <alexander.levin@...izon.com>,
LKML <linux-kernel@...r.kernel.org>, linux@...inikbrodowski.net,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>,
nikolaus.voss@...wensteinmedical.de,
Stephen Rothwell <sfr@...b.auug.org.au>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: linux-next boot error (2)
On Thu, Sep 6, 2018 at 10:41 AM, David Howells <dhowells@...hat.com> wrote:
> Do we know what type of filesystem is on the root device?
ext4
The image is built with this script (you can find mkfs.ext4 there):
https://github.com/google/syzkaller/blob/master/tools/create-gce-image.sh
> Also, is there a way to tell if AppArmor denied something?
That I don't know. I guess it would have printed something.
This configuration worked before. And we don't see any errors on other trees.
A relatively recent addition was ext4 options "-O
^resize_inode,has_journal,ext_attr,extents,huge_file,flex_bg,dir_nlink,sparse_super".
But I think we already tested with them and that all worked.
Powered by blists - more mailing lists