linux-kernel - Re: nvme, allocation failures, and aborted commands

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: <20170309230334.GE14329@localhost.localdomain>
Date:   Thu, 9 Mar 2017 18:03:34 -0500
From:   Keith Busch <keith.busch@...el.com>
To:     Thomas Fjellstrom <thomas@...llstrom.ca>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>,
        linux-nvme@...ts.infradead.org
Subject: Re: nvme, allocation failures, and aborted commands

On Thu, Mar 09, 2017 at 03:01:27PM -0700, Thomas Fjellstrom wrote:
> On Monday, March 6, 2017 5:46:33 PM MST Keith Busch wrote:
> > 
> >   echo 128 > /sys/block/nvme0n1/queue/max_hw_sectors_kb
> >   echo 128 > /sys/block/nvme0n1/queue/max_nr_requests
> > 
> 
> First off, theres no max_nr_requests, and echoing into max_hw_sectors_kb gets
> me a permission denied even as root no matter the value I tried.

What I meant to say was "max_sectors_kb" and "nr_request".