| 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: Sun, 4 Nov 2007 14:26:21 +0100 From: Jens Axboe <jens.axboe@...cle.com> To: Stefan Richter <stefanr@...6.in-berlin.de> Cc: Torsten Kaiser <just.for.lkml@...glemail.com>, linux-kernel@...r.kernel.org, linux1394-devel@...ts.sourceforge.net Subject: Re: 2.6.24-rc1-54866f032307063776b4eff7eadb131d47f9f9b4 fails to boot: kernel BUG at include/linux/scatterlist.h:49! On Sun, Nov 04 2007, Stefan Richter wrote: > Jens Axboe wrote: > > Chained sg lists will only be feed to a scsi host controller that > > enables chaining in its host template. > > > > The fix looks fine though, it's just not a requirement or bug fix :-) > > Good, then the sbp2 and fw-sbp2 patches can wait for 2.6.25. > > Which criteria decide whether a SCSI low-level driver should enable > chained s/g lists? The SBP-2 protocol supports s/g lists with up to > 65535 entries. The sbp2 and fw-sbp2 driver limit this currently to SG_ALL. If the driver can benefit (or even requires) from more segments than you can typically allocate in one piece, then it should enable chaining. In general, all drivers must be transitioned to using the sg accessor helpers, so we can eventually kill the sg chaining enable parameter in the host template and just make it the default. The parameter is only there as a transition help. -- Jens Axboe - 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