linux-kernel - Re: [PATCH] firmware: arm_scmi: Fix xfers allocation on RX channel

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: <168173500399.1886197.2762979819765120755.b4-ty@arm.com>
Date:   Mon, 17 Apr 2023 13:43:51 +0100
From:   Sudeep Holla <sudeep.holla@....com>
To:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Cristian Marussi <cristian.marussi@....com>
Cc:     Sudeep Holla <sudeep.holla@....com>
Subject: Re: [PATCH] firmware: arm_scmi: Fix xfers allocation on RX channel

On Sun, 26 Mar 2023 21:34:49 +0100, Cristian Marussi wrote:
> Two distinct pools of xfer descriptors are allocated at initialization
> time: one (TX) used to provide xfers to track commands and their replies
> (or delayed replies) and another (RX) to pick xfers from to be used for
> processing notifications.
> 
> Such pools, though, are allocated globally to be used by the whole SCMI
> instance, they are not allocated per-channel and as such the allocation of
> notifications xfers cannot be simply skipped if no RX channel was found for
> the Base protocol common channel, because there could be defined more
> optional per-protocol dedicated channels that instead support RX channels.
> 
> [...]

Applied to sudeep.holla/linux (for-next/scmi/fixes), thanks!

[1/1] firmware: arm_scmi: Fix xfers allocation on RX channel
	https://git.kernel.org/sudeep.holla/c/b2ccba9e8cdc
--
Regards,
Sudeep