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: Wed, 20 Dec 2017 16:08:05 -0800 From: "tj@...nel.org" <tj@...nel.org> To: Bart Van Assche <Bart.VanAssche@....com> Cc: "axboe@...nel.dk" <axboe@...nel.dk>, "kernel-team@...com" <kernel-team@...com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "peterz@...radead.org" <peterz@...radead.org>, "osandov@...com" <osandov@...com>, "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>, "oleg@...hat.com" <oleg@...hat.com>, "hch@....de" <hch@....de> Subject: Re: [PATCHSET v2] blk-mq: reimplement timeout handling On Wed, Dec 20, 2017 at 11:41:02PM +0000, Bart Van Assche wrote: > On Tue, 2017-12-12 at 11:01 -0800, Tejun Heo wrote: > > Currently, blk-mq timeout path synchronizes against the usual > > issue/completion path using a complex scheme involving atomic > > bitflags, REQ_ATOM_*, memory barriers and subtle memory coherence > > rules. Unfortunatley, it contains quite a few holes. > > Hello Tejun, > > An attempt to run SCSI I/O with this patch series applied resulted in > the following: Can you please try the v3? There were a couple bugs that I missed while testing earlier versions. http://lkml.kernel.org/r/20171216120726.517153-1-tj@kernel.org Thanks. -- tejun
Powered by blists - more mailing lists