linux-kernel - Re: [PATCH v3 2/2] iommu/tegra-smmu: Expend mutex protection range

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

Message-ID: <20200929060336.GB6564@infradead.org>
Date:   Tue, 29 Sep 2020 07:03:36 +0100
From:   Christoph Hellwig <hch@...radead.org>
To:     Nicolin Chen <nicoleotsuka@...il.com>
Cc:     thierry.reding@...il.com, joro@...tes.org,
        linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
        jonathanh@...dia.com, linux-tegra@...r.kernel.org, digetx@...il.com
Subject: Re: [PATCH v3 2/2] iommu/tegra-smmu: Expend mutex protection range

On Mon, Sep 28, 2020 at 09:52:47PM -0700, Nicolin Chen wrote:
> This is used to protect potential race condition at use_count.
> since probes of client drivers, calling attach_dev(), may run
> concurrently.

Shouldn't this read "expand" instead of "expend"?