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:   Thu, 20 Apr 2017 12:29:25 -0400
From:   Keith Busch <keith.busch@...el.com>
To:     Sagi Grimberg <sagi@...mberg.me>
Cc:     Jens Axboe <axboe@...nel.dk>, Andy Lutomirski <luto@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Kai-Heng Feng <kai.heng.feng@...onical.com>,
        linux-nvme@...ts.infradead.org, Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v2 0/2] nvme APST quirk updates, take two

On Thu, Apr 20, 2017 at 07:15:15PM +0300, Sagi Grimberg wrote:
> 
> > > Hi Jens-
> > > 
> > > These are just the quirk updates, split out.  The patches are
> > > unchanged.
> > > 
> > > I think that, even if we want to apply a broader quirk for 4.11, we
> > > should still apply these so that we can cleanly revert the broader
> > > quirk later.  IOW, let's get the known regressions fixed before we
> > > get too excited about the unknown regressions.
> > 
> > This looks good to me, and 4.11 appropriate. I'll expedite this
> > through the block tree, if Keith/Sagi/Christoph agrees on this
> > being the right approach for 4.11.
> 
> I'm perfectly fine with this going to 4.11

All good with me as well.

Reviewed-by: Keith Busch <keith.busch@...el.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ