linux-kernel - Re: [PATCH] dmaengine: idxd: Fix default allowed read buffers value in group

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: <Y+Xe4RTN72DTmJRL@matsya>
Date:   Fri, 10 Feb 2023 11:36:25 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Fenghua Yu <fenghua.yu@...el.com>
Cc:     Dave Jiang <dave.jiang@...el.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        dmaengine@...r.kernel.org, Ramesh Thomas <ramesh.thomas@...el.com>,
        Nikhil Rao <nikhil.rao@...el.com>
Subject: Re: [PATCH] dmaengine: idxd: Fix default allowed read buffers value
 in group

On 27-01-23, 11:28, Fenghua Yu wrote:
> Currently default read buffers that is allowed in a group is 0.
> grpcfg will be configured to max read buffers that IDXD can support if
> the group's allowed read buffers value is 0. But 0 is an invalid
> read buffers value and user may get confused when seeing the invalid
> initial value 0 through sysfs interface.
> 
> To show only valid allowed read buffers value and eliminate confusion,
> directly initialize the allowed read buffers to IDXD's max read buffers.
> User still can change the value through sysfs interface.

Applied, thanks

-- 
~Vinod