public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	george.mccollister@gmail.com, kuba@kernel.org,
	davem@davemloft.net, olteanv@gmail.com, f.fainelli@gmail.com,
	vivien.didelot@gmail.com, andrew@lunn.ch,
	UNGLinuxDriver@microchip.com, woojung.huh@microchip.com
Subject: Re: [PATCH v2 net] net: dsa: microchip: Added the condition for scheduling ksz_mib_read_work
Date: Tue, 12 Oct 2021 10:40:07 +0000	[thread overview]
Message-ID: <163403520747.25122.15656227462874718417.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211011154808.25820-1-arun.ramadoss@microchip.com>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 11 Oct 2021 21:18:08 +0530 you wrote:
> When the ksz module is installed and removed using rmmod, kernel crashes
> with null pointer dereferrence error. During rmmod, ksz_switch_remove
> function tries to cancel the mib_read_workqueue using
> cancel_delayed_work_sync routine and unregister switch from dsa.
> 
> During dsa_unregister_switch it calls ksz_mac_link_down, which in turn
> reschedules the workqueue since mib_interval is non-zero.
> Due to which queue executed after mib_interval and it tries to access
> dp->slave. But the slave is unregistered in the ksz_switch_remove
> function. Hence kernel crashes.
> 
> [...]

Here is the summary with links:
  - [v2,net] net: dsa: microchip: Added the condition for scheduling ksz_mib_read_work
    https://git.kernel.org/netdev/net/c/ef1100ef20f2

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



      reply	other threads:[~2021-10-12 10:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 15:48 [PATCH v2 net] net: dsa: microchip: Added the condition for scheduling ksz_mib_read_work Arun Ramadoss
2021-10-12 10: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=163403520747.25122.15656227462874718417.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=arun.ramadoss@microchip.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=george.mccollister@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=vivien.didelot@gmail.com \
    --cc=woojung.huh@microchip.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