From: subashab@codeaurora.org
To: netdev@vger.kernel.org
Cc: eric.dumazet@gmail.com
Subject: [RFC] Handling device free after a packet is passed to the network stack
Date: Fri, 27 Mar 2015 19:57:34 -0000 [thread overview]
Message-ID: <f3c7672edb978d520f12d72cb41d1e4d.squirrel@www.codeaurora.org> (raw)
We have been coming across a couple of scenarios where the device is freed
and the corresponding packets which were already queued up the stack
encounter crashes when they find that contents of skb->dev are no longer
valid.
Specifically, we have observed an instance where a cpu hotplug occurs
along with the network driver module unloading. When the packets are being
queued up the stack using netif_rx_ni from dev_cpu_callback, get_rps_cpus
crashes as it encounters invalid data at skb->dev since it would have been
freed.
We would like to know if the kernel provides some mechanisms to safeguard
against such scenarios.
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
next reply other threads:[~2015-03-27 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 19:57 subashab [this message]
2015-03-28 2:49 ` [RFC] Handling device free after a packet is passed to the network stack Eric Dumazet
2015-03-30 14:19 ` Harout Hedeshian
2015-03-30 22:41 ` Eric Dumazet
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=f3c7672edb978d520f12d72cb41d1e4d.squirrel@www.codeaurora.org \
--to=subashab@codeaurora.org \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).