| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 5 Nov 2013 12:38:33 -0800 From: Olof Johansson <olof@...om.net> To: Chris Mason <chris.mason@...ionio.com> Cc: Jens Axboe <axboe@...nel.dk>, Tushar Behera <tushar.behera@...aro.org>, "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>, lkml <linux-kernel@...r.kernel.org> Subject: Re: Boot failure on Arndale with next-20131105 On Tue, Nov 5, 2013 at 12:33 PM, Chris Mason <chris.mason@...ionio.com> wrote: > Quoting Olof Johansson (2013-11-05 15:23:51) >> On Tue, Nov 5, 2013 at 11:33 AM, Jens Axboe <axboe@...nel.dk> wrote: > > [ horrible crashes fixed by removing my patch ] > >> > Very weird! What file system is being used? >> >> Most of my failures have happened on regular MMC cards with ext4 >> filesystems on them. >> >> Note that the panic happens during device probe / partition table >> scanning, not after mounting the filesystem. >> >> Giving your patch a go now across the board. I'm very concerned about >> the reports of bisectability, build failures and heaps of warnings >> though. Did the 0-day builder pick up any of those? :-/ >> > > Hmmm, is bcache in your config? Doesn't look that way -- no ARM defconfigs enable it (it's what I build and boot), and the option defaults to off and nothing selects it. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists