linux-kernel - Re: [PATCH] nvme-pci: fix prp list allocation

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CABwBYcazb-2E937U2HeNJXRAtLbyfGdMh3AJarmP9wasyS-qWw@mail.gmail.com>
Date:   Sat, 12 Feb 2022 15:16:24 -0700
From:   Matt Waltz <matthewwaltzis@...il.com>
To:     Keith Busch <kbusch@...nel.org>
Cc:     Jens Axboe <axboe@...com>, Christoph Hellwig <hch@....de>,
        Sagi Grimberg <sagi@...mberg.me>,
        linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvme-pci: fix prp list allocation

On Sat, Feb 12, 2022 at 2:03 PM Keith Busch <kbusch@...nel.org> wrote:
> That only applies to chaining list elements. It does not apply to the
> "PRP list pointer in a command". The driver allocates from the 256B dma
> pool only for the command's PRP list pointer, so we're fine.

Ah yes, I was confused by the PRP2 definition which says it can be a
"PRP list pointer",
now I feel extremely silly. Guess I'll need to look elsewhere for a
fix for this bug I am
encountering, thank you for the clarity!