| 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
| ||
|
Message-ID: <20091126081359.414c8216@notabene.brown> Date: Thu, 26 Nov 2009 08:13:59 +1100 From: Neil Brown <neilb@...e.de> To: Jiri Slaby <jirislaby@...il.com> Cc: James Bottomley <James.Bottomley@...e.de>, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, mm-commits@...r.kernel.org, linux-scsi@...r.kernel.org, Jens Axboe <Jens.Axboe@...cle.com> Subject: Re: BUG at scsi_lib.c:1108 [Was: mmotm 2009-11-24-16-47 uploaded] On Wed, 25 Nov 2009 21:22:57 +0100 Jiri Slaby <jirislaby@...il.com> wrote: > It doesn't make sense at all. How can empty merge cause a regression? > And md/for-next doesn't produce the BUG. I've hit that situation before. Two separate changes in separate branches conspire to cause a problem. md/for-next contains code to handle barriers properly for all levels, not just RAID1. It is possible I got this wrong in some way, and some new sanity check in a separate branch is firing, or it is possible some other bug in barrier handling has been added and now that MD sends barriers, it is being triggered. What I did to find the actual offending patches is to got to one of the heads just before the merge, and cherry-pick all the patches from the other branch, and then bisect that. NeilBrown -- 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