netdev - Re: [PATCH net-next] r8169: Use a raw_spinlock

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: 
 <168490021929.7545.5401674402592156945.git-patchwork-notify@kernel.org>
Date: Wed, 24 May 2023 03:50:19 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
 hkallweit1@...il.com, kuba@...nel.org, efault@....de, pabeni@...hat.com,
 tglx@...utronix.de, nic_swsd@...ltek.com
Subject: Re: [PATCH net-next] r8169: Use a raw_spinlock_t for the register locks.

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Mon, 22 May 2023 15:41:21 +0200 you wrote:
> The driver's interrupt service routine is requested with the
> IRQF_NO_THREAD if MSI is available. This means that the routine is
> invoked in hardirq context even on PREEMPT_RT. The routine itself is
> relatively short and schedules a worker, performs register access and
> schedules NAPI. On PREEMPT_RT, scheduling NAPI from hardirq results in
> waking ksoftirqd for further processing so using NAPI threads with this
> driver is highly recommended since it NULL routes the threaded-IRQ
> efforts.
> 
> [...]

Here is the summary with links:
  - [net-next] r8169: Use a raw_spinlock_t for the register locks.
    https://git.kernel.org/netdev/net/c/d6c36cbc5e53

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html