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:   Tue, 29 May 2018 09:05:01 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Steffen Maier <maier@...ux.ibm.com>
Cc:     linux-kernel@...r.kernel.org,
        Bart Van Assche <bart.vanassche@....com>,
        stable@...r.kernel.org, Doug Gilbert <dgilbert@...erlog.com>,
        Hannes Reinecke <hare@...e.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        Sasha Levin <alexander.levin@...rosoft.com>
Subject: Re: [PATCH 4.14 199/496] scsi: core: return BLK_STS_OK for DID_OK in
 __scsi_error_from_host_byte()

On Mon, May 28, 2018 at 03:59:56PM +0200, Steffen Maier wrote:
> question:
> drop because of upstream's
> 
> cbe095e2b584 ("Revert "scsi: core: return BLK_STS_OK for DID_OK in
> __scsi_error_from_host_byte()"")
> Fixes: e39a97353e53 ("scsi: core: return BLK_STS_OK for DID_OK in
> __scsi_error_from_host_byte()")
> 
> as in stable-queue's
> 
> c40541008b93 ("drop a scsi patch from 4.14")
> 
> ?

Ugh, you are right, sorry about this, now dropping it again :)

Sasha, any way your scripts can detect that a patch was later reverted
so you don't add it to your patch series?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ