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]
Date:   Fri, 10 Mar 2017 15:29:49 +0000
From:   KY Srinivasan <kys@...rosoft.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Ben Hutchings <ben@...adent.org.uk>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        Long Li <longli@...rosoft.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>
Subject: RE: [PATCH 4.4 34/91] scsi: storvsc: use tagged SRB requests if
 supported by the device



> -----Original Message-----
> From: Greg Kroah-Hartman [mailto:gregkh@...uxfoundation.org]
> Sent: Friday, March 10, 2017 7:22 AM
> To: Ben Hutchings <ben@...adent.org.uk>
> Cc: linux-kernel@...r.kernel.org; stable@...r.kernel.org; Long Li
> <longli@...rosoft.com>; KY Srinivasan <kys@...rosoft.com>; Martin K.
> Petersen <martin.petersen@...cle.com>
> Subject: Re: [PATCH 4.4 34/91] scsi: storvsc: use tagged SRB requests if
> supported by the device
> 
> On Fri, Mar 10, 2017 at 02:56:59PM +0000, Ben Hutchings wrote:
> > On Fri, 2017-03-10 at 10:08 +0100, Greg Kroah-Hartman wrote:
> > > 4.4-stable review patch.  If anyone has any objections, please let me
> know.
> > >
> > > ------------------
> > >
> > > From: Long Li <longli@...rosoft.com>
> > >
> > > commit 3cd6d3d9b1abab8dcdf0800224ce26daac24eea2 upstream.
> > >
> > > Properly set SRB flags when hosting device supports tagged queuing.
> > > This patch improves the performance on Fiber Channel disks.
> > [...]
> >
> > This looks more like a feature/optimisation than a bug fix.  Is this
> > really within the stable rules?
> 
> Making things work properly (i.e. i/o does not suck anymore), is ok for
> stable stuff.  KY, that's the case here, right?

If I recall correctly, this was needed for Fibre Channel SANs where without
this fix the performance was so bad to be almost unusable.

K. Y

> 
> thanks,
> 
> greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ