linux-kernel - Re: [PATCH v1 0/1] aoe: possible interrupt unsafe locking scenario

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: <170611025731.2148128.9958144886915388505.b4-ty@kernel.dk>
Date: Wed, 24 Jan 2024 08:30:57 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Maksim Kiselev <bigunclemax@...il.com>
Cc: Justin Sanders <justin@...aid.com>, linux-block@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 0/1] aoe: possible interrupt unsafe locking scenario


On Wed, 24 Jan 2024 10:24:35 +0300, Maksim Kiselev wrote:
> I'm using an AoE device on board with D1 SoC (riscv arch).
> When I enabled CONFIG_PROVE_LOCKING option, I got the warning below.
> After some investigations, I made a not very elegant, but working solution.
> The patch sent with next message.
> 
> I would be glad to know what you think about this.
> 
> [...]

Applied, thanks!

[1/1] aoe: avoid potential deadlock at set_capacity
      commit: e169bd4fb2b36c4b2bee63c35c740c85daeb2e86

Best regards,
-- 
Jens Axboe