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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1494892845.2567.14.camel@sandisk.com>
Date:   Tue, 16 May 2017 00:00:46 +0000
From:   Bart Van Assche <Bart.VanAssche@...disk.com>
To:     "jejb@...ux.vnet.ibm.com" <jejb@...ux.vnet.ibm.com>,
        "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "longli@...rosoft.com" <longli@...rosoft.com>,
        "martin.petersen@...cle.com" <martin.petersen@...cle.com>
CC:     "sthemmin@...rosoft.com" <sthemmin@...rosoft.com>,
        "kys@...rosoft.com" <kys@...rosoft.com>
Subject: Re: [PATCH] scsi: zero per-cmd driver data for each MQ I/O

On Mon, 2017-05-15 at 23:32 +0000, Long Li wrote:
> Thanks for looking! Yes this is for chasing a bug. 
> 
> With the patch, we also zero the private data used by lower layer driver, in
> addition to the private data in scsi_cmnd.

Hello Long,

What bug did you encounter, with which combination of ULP (sd?) and LLD SCSI
driver(s) and for which request type (REQ_OP_*)? You will have to mention that
information in the patch description anyway if you want your patch to get
accepted.

If the bug that you encountered only occurs with a single LLD, would it be
possible to implement a fix by modifying the LLD instead of the SCSI core?

Thanks,

Bart.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ