From: patchwork-bot+netdevbpf@kernel.org
To: Kumar@ci.codeaurora.org, M Chetan <m.chetan.kumar@linux.intel.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
johannes@sipsolutions.net, ryazanov.s.a@gmail.com,
loic.poulain@linaro.org, linuxwwan@intel.com,
m.chetan.kumar@intel.com, edumazet@google.com, pabeni@redhat.com,
simon.horman@corigine.com, sam@samwein.com
Subject: Re: [PATCH v3 net] net: wwan: iosm: fix NULL pointer dereference when removing device
Date: Wed, 17 May 2023 12:00:20 +0000 [thread overview]
Message-ID: <168432482018.30872.8605947380694334089.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <6d9e4d90ec89d8ac026e149381ca0c8243a11a19.1684250558.git.m.chetan.kumar@linux.intel.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 16 May 2023 21:09:46 +0530 you wrote:
> From: M Chetan Kumar <m.chetan.kumar@linux.intel.com>
>
> In suspend and resume cycle, the removal and rescan of device ends
> up in NULL pointer dereference.
>
> During driver initialization, if the ipc_imem_wwan_channel_init()
> fails to get the valid device capabilities it returns an error and
> further no resource (wwan struct) will be allocated. Now in this
> situation if driver removal procedure is initiated it would result
> in NULL pointer exception since unallocated wwan struct is dereferenced
> inside ipc_wwan_deinit().
>
> [...]
Here is the summary with links:
- [v3,net] net: wwan: iosm: fix NULL pointer dereference when removing device
https://git.kernel.org/netdev/net/c/60829145f1e2
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:[~2023-05-17 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 15:39 [PATCH v3 net] net: wwan: iosm: fix NULL pointer dereference when removing device m.chetan.kumar
2023-05-16 19:10 ` Simon Horman
2023-05-17 12:00 ` 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=168432482018.30872.8605947380694334089.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Kumar@ci.codeaurora.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=m.chetan.kumar@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryazanov.s.a@gmail.com \
--cc=sam@samwein.com \
--cc=simon.horman@corigine.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.