From: patchwork-bot+netdevbpf@kernel•org
To: Sebastian Andrzej Siewior <bigeasy@linutronix•de>
Cc: netdev@vger•kernel.org, jwyatt@redhat•com, rajur@chelsio•com,
jlelli@redhat•com, williams@redhat•com, lgoncalv@redhat•com,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, tglx@linutronix•de
Subject: Re: [PATCH net] cxgb4: Properly lock TX queue for the selftest.
Date: Wed, 01 May 2024 01:40:31 +0000 [thread overview]
Message-ID: <171452763152.16260.2017250381831802167.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240429091147.YWAaal4v@linutronix.de>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Mon, 29 Apr 2024 11:11:47 +0200 you wrote:
> The selftest for the driver sends a dummy packet and checks if the
> packet will be received properly as it should be. The regular TX path
> and the selftest can use the same network queue so locking is required
> and was missing in the selftest path. This was addressed in the commit
> cited below.
> Unfortunately locking the TX queue requires BH to be disabled which is
> not the case in selftest path which is invoked in process context.
> Lockdep should be complaining about this.
>
> [...]
Here is the summary with links:
- [net] cxgb4: Properly lock TX queue for the selftest.
https://git.kernel.org/netdev/net/c/9067eccdd784
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-05-01 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 4:10 net: cxgb4: Call Trace reported with PREEMPT_RT: BUG: using smp_processor_id() in preemptible [00000000] code: ethtool/78718 John B. Wyatt IV
2024-04-23 15:03 ` Luis Claudio R. Goncalves
2024-04-29 9:11 ` [PATCH net] cxgb4: Properly lock TX queue for the selftest Sebastian Andrzej Siewior
2024-05-01 1:40 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171452763152.16260.2017250381831802167.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=bigeasy@linutronix$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jlelli@redhat$(echo .)com \
--cc=jwyatt@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=lgoncalv@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=rajur@chelsio$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=williams@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox