From: patchwork-bot+netdevbpf@kernel.org
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: paul.barker.ct@bp.renesas.com, niklas.soderlund@ragnatech.se,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, s.shtylyov@omp.ru,
thomas.petazzoni@bootlin.com,
niklas.soderlund+renesas@ragnatech.se,
claudiu.beznea.uj@bp.renesas.com, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] Fix missing rtnl lock in suspend path
Date: Thu, 30 Jan 2025 10:50:33 +0000 [thread overview]
Message-ID: <173823423301.921316.7275460470502894424.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250129-fix_missing_rtnl_lock_phy_disconnect-v3-0-24c4ba185a92@bootlin.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 29 Jan 2025 10:50:45 +0100 you wrote:
> Fix the suspend path by ensuring the rtnl lock is held where required.
> Calls to open, close and WOL operations must be performed under the
> rtnl lock to prevent conflicts with ongoing ndo operations.
>
> Discussion about this issue can be found here:
> https://lore.kernel.org/netdev/20250120141926.1290763-1-kory.maincent@bootlin.com/
>
> [...]
Here is the summary with links:
- [net,v3,1/2] net: ravb: Fix missing rtnl lock in suspend/resume path
https://git.kernel.org/netdev/net/c/2c2ebb2b4957
- [net,v3,2/2] net: sh_eth: Fix missing rtnl lock in suspend/resume path
https://git.kernel.org/netdev/net/c/b95102215a8d
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:[~2025-01-30 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 9:50 Kory Maincent
2025-01-29 9:50 ` [PATCH net v3 1/2] net: ravb: Fix missing rtnl lock in suspend/resume path Kory Maincent
2025-01-29 14:00 ` Niklas Söderlund
2025-01-29 9:50 ` [PATCH net v3 2/2] net: sh_eth: " Kory Maincent
2025-01-30 10:50 ` 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=173823423301.921316.7275460470502894424.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=niklas.soderlund@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=s.shtylyov@omp.ru \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®