Linux CAN drivers development
 help / color / mirror / Atom feed
From: laurent vaudoit <laurent.vaudoit@gmail.com>
To: linux-can@vger.kernel.org
Subject: Raw can socket close and disabling filters
Date: Fri, 22 Apr 2016 11:39:20 +0000 (UTC)	[thread overview]
Message-ID: <loom.20160422T133332-34@post.gmane.org> (raw)

Hi all,
i'm using a 3.10 kernel with rtpatch applied, with raw can features.
Running some debug in the release function, i've seen something weird (for 
me).

In the function, we get the socket informations
and then we unregister the notifier.

After this, we test if the socket is bound and which is the ifindex.

But when the unregister function is called, there is a call to the notifier 
with the event NETDEV_UNREGISTER, who leads to clear the socket inforamtions 
like bound and ifindex.

So in the release function we can never enter in the code specific to a 
device.

Is there something i've missed?

Thanks in advance for your answer.
Regards
Laurent


             reply	other threads:[~2016-04-22 11:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 11:39 laurent vaudoit [this message]
2016-04-23 13:33 ` Raw can socket close and disabling filters Oliver Hartkopp
2016-04-25  7:19   ` laurent vaudoit
2016-04-25  7:54     ` Oliver Hartkopp
2016-04-25  7:57       ` laurent vaudoit

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=loom.20160422T133332-34@post.gmane.org \
    --to=laurent.vaudoit@gmail.com \
    --cc=linux-can@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