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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 21 Dec 2017 23:31:40 +0800 From: weiping zhang <zwp10758@...il.com> To: Bruno Wolff III <bruno@...ff.to> Cc: Laura Abbott <labbott@...hat.com>, Jan Kara <jack@...e.cz>, Jens Axboe <axboe@...nel.dk>, linux-mm@...ck.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, regressions@...mhuis.info, weiping zhang <zhangweiping@...ichuxing.com>, linux-block@...r.kernel.org Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register") 2017-12-21 23:18 GMT+08:00 Bruno Wolff III <bruno@...ff.to>: > On Thu, Dec 21, 2017 at 22:01:33 +0800, > weiping zhang <zwp10758@...il.com> wrote: >> >> Hi, >> how do you do bisect ?build all kernel commit one by one ? >> as you did before: >> https://bugzilla.redhat.com/show_bug.cgi?id=1520982 > > > I just did the one bisect using Linus' tree. After each build, I would do a > test boot and see if the boot was normal or if I got errors and an eventual > hang before boot. > > Since then I have used git revert to revert just the problem commit from > later kernels (such as v4.15-rc4) and when I do the system boots normally. > And when I don't do the revert or just use stock Fedora kernels the problem > occurs every time. does every time boot fail can trigger WANRING in device_add_disk ?
Powered by blists - more mailing lists