netdev - Re: [PATCH net-next v3 1/9] tsnep: Use spin_lock

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: <cbffa3fd-b095-2c87-2a5a-dcbab553b0af@engleder-embedded.com>
Date:   Thu, 5 Jan 2023 20:48:55 +0100
From:   Gerhard Engleder <gerhard@...leder-embedded.com>
To:     Alexander Lobakin <alexandr.lobakin@...el.com>
Cc:     davem@...emloft.net, kuba@...nel.org, edumazet@...gle.com,
        pabeni@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3 1/9] tsnep: Use spin_lock_bh for TX

On 05.01.23 13:40, Alexander Lobakin wrote:
> From: Gerhard Engleder <gerhard@...leder-embedded.com>
> Date: Wed Jan 04 2023 20:41:24 GMT+0100
> 
>> TX processing is done only within process or BH context. Therefore,
>> _irqsafe variant is not necessary.
> 
> NAPI and .ndo_{start,xdp}_xmit are BH-only, where can the process
> context happen here?

I will remove the process context from the description.

Gerhard