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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c7a454f4-c471-49d5-ac35-5375a45a6610@intel.com>
Date: Tue, 21 Oct 2025 16:03:30 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Vinicius Costa Gomes <vinicius.gomes@...el.com>,
 Dave Jiang <dave.jiang@...el.com>, Vinod Koul <vkoul@...nel.org>,
 Fenghua Yu <fenghua.yu@...el.com>, Dan Williams <dan.j.williams@...el.com>
Cc: dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 01/10] dmaengine: idxd: Fix lockdep warnings when
 calling idxd_device_config()

On 8/21/25 15:59, Vinicius Costa Gomes wrote:
> Move the check for IDXD_FLAG_CONFIGURABLE and the locking to "inside"
> idxd_device_config(), as this is common to all callers, and the one
> that wasn't holding the lock was an error (that was causing the
> lockdep warning).

What is "the lockdep error"? I don't see any details about an error in
the changelog here or the cover letter?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ