linux-kernel - Re: [PATCH v5 1/1] wifi: mac80211: fortify the spinlock against deadlock by interrupt

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: <87r0qyjeiy.fsf@kernel.org>
Date:   Tue, 30 May 2023 13:32:21 +0300
From:   Kalle Valo <kvalo@...nel.org>
To:     Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>
Cc:     Johannes Berg <johannes@...solutions.net>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Leon Romanovsky <leonro@...dia.com>
Subject: Re: [PATCH v5 1/1] wifi: mac80211: fortify the spinlock against deadlock by interrupt

Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr> writes:

> On 5/17/23 23:34, Johannes Berg wrote:
>>>
>>> Fixes: 4444bc2116ae ("wifi: mac80211: Proper mark iTXQs for resumption")
>>> Link: https://lore.kernel.org/all/1f58a0d1-d2b9-d851-73c3-93fcc607501c@alu.unizg.hr/
>>> Reported-by: Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>
>>> Link: https://lore.kernel.org/all/cdc80531-f25f-6f9d-b15f-25e16130b53a@alu.unizg.hr/
>>> Signed-off-by: Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>
>>> Reviewed-by: Leon Romanovsky <leonro@...dia.com>
>>> ---
>>>
>>
>> You really should say what you changed, but anyway, it's too late - I
>> applied a previous version yesterday.
>
> Yes. Sorry, I was following Andy's advice to resend, at the wrong
> assumption that the system ate the patch after three weeks of
> inactivity. :-/

Yeah, unfortunately we maintainers are busy so sometimes it takes before
we can process patches. But you can check the patch status from
patchwork, link below. Also the wiki has more information how we use it.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches