linux-kernel - Re: [PATCH v2] nvme-pci: do not set the NUMA node of device if it has none

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] [day] [month] [year] [list]

Message-ID: <ZQCNn99783AbnQ5O@kbusch-mbp.dhcp.thefacebook.com>
Date:   Tue, 12 Sep 2023 09:11:11 -0700
From:   Keith Busch <kbusch@...nel.org>
To:     Pratyush Yadav <ptyadav@...zon.de>
Cc:     Jens Axboe <axboe@...nel.dk>, Christoph Hellwig <hch@....de>,
        Sagi Grimberg <sagi@...mberg.me>,
        linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] nvme-pci: do not set the NUMA node of device if it
 has none

On Tue, Sep 12, 2023 at 05:52:49PM +0200, Pratyush Yadav wrote:
> If a device has no NUMA node information associated with it, the driver
> puts the device in node first_memory_node (say node 0). Not having a
> NUMA node and being associated with node 0 are completely different
> things and it makes little sense to mix the two.

Applied for nvme-6.6. This overall makes sense, though I hope the patch
isn't just to work around xen's incompatibility with managed irqs :)