From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
o.rempel@pengutronix.de,
syzbot+ee1cd780f69483a8616b@syzkaller.appspotmail.com,
hdanton@sina.com, stable@vger.kernel.org
Subject: Re: [PATCH net 1/2] can: j1939: prevent deadlock by moving j1939_sk_errqueue()
Date: Tue, 28 Mar 2023 02:50:18 +0000 [thread overview]
Message-ID: <167997181871.12698.12733102984157992409.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230327124807.1157134-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Mon, 27 Mar 2023 14:48:06 +0200 you wrote:
> From: Oleksij Rempel <o.rempel@pengutronix.de>
>
> This commit addresses a deadlock situation that can occur in certain
> scenarios, such as when running data TP/ETP transfer and subscribing to
> the error queue while receiving a net down event. The deadlock involves
> locks in the following order:
>
> [...]
Here is the summary with links:
- [net,1/2] can: j1939: prevent deadlock by moving j1939_sk_errqueue()
https://git.kernel.org/netdev/net/c/d1366b283d94
- [net,2/2] can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write
https://git.kernel.org/netdev/net/c/2b4c99f7d9a5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-28 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 12:48 [PATCH net 0/2] pull-request: can 2023-03-27 Marc Kleine-Budde
2023-03-27 12:48 ` [PATCH net 1/2] can: j1939: prevent deadlock by moving j1939_sk_errqueue() Marc Kleine-Budde
2023-03-28 2:50 ` patchwork-bot+netdevbpf [this message]
2023-03-27 12:48 ` [PATCH net 2/2] can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write Marc Kleine-Budde
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=167997181871.12698.12733102984157992409.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hdanton@sina.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=stable@vger.kernel.org \
--cc=syzbot+ee1cd780f69483a8616b@syzkaller.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.