linux-kernel - [PATCH 0/2] Check for MSI 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20220609153843.1991-1-jvetter@kalrayinc.com>
Date:   Thu,  9 Jun 2022 17:38:41 +0200
From:   Julian Vetter <jvetter@...rayinc.com>
To:     gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
        ysionneau@...rayinc.com
Cc:     Julian Vetter <jvetter@...rayinc.com>
Subject: [PATCH 0/2] Check for MSI allocation

Our HW has a mailbox periph that supports up to 8192 MSIs, so the currently
supported 2048 is not enough. I believe there is no real reason to
contstrain the max platform MSIs to 2048, because the value is stored in
an irq_hw_number_t which is big enough to hold more MSIs. The value is
OR'ed with the device ID of which there is also a limited number.
The second patch contains a WARN() to warn the user if a device tries to
obtain more that MAX_DEV_MSIS, because this could lead to potentially
conflicting virtual interrupt numbers (as was the case for us) without
the Linux kernel telling us.

Julian Vetter (2):
  msi: The MSI framework only supports 2048 platform MSIs
  msi: Add sanity check if more than MAX_DEV_MSIS MSIs are requested

 drivers/base/platform-msi.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

-- 
2.17.1