From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Mischke <survivor@uni-paderborn.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: read_RSSI and others not thread-safe?
Date: Fri, 08 Oct 2004 17:40:58 +0200 [thread overview]
Message-ID: <1097250057.4407.25.camel@pegasus> (raw)
In-Reply-To: <4166B45C.1000802@uni-paderborn.de>
Hi Stefan,
> if there is no pre-filtering then a process could open a socket to hci,
> set the event filter to "all events" and receive events which are
> results of other processes/sockets? Is this really true?
it is a raw socket and every process can get all events. It is not
possible to prevent this and actually the HCI itself is not designed for
something like this. However you must be root to get some special
events.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-10-08 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 12:41 [Bluez-devel] read_RSSI and others not thread-safe? Stefan Mischke
2004-10-08 14:48 ` [Bluez-devel] " Stefan Mischke
2004-10-08 15:29 ` Marcel Holtmann
2004-10-08 15:38 ` Stefan Mischke
2004-10-08 15:40 ` Marcel Holtmann [this message]
2004-10-08 16:02 ` Stefan Mischke
2004-10-08 16:06 ` Marcel Holtmann
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=1097250057.4407.25.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=survivor@uni-paderborn.de \
/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