From: valdis.kletnieks@vt.edu
To: Gustavo Padovan <gustavo@padovan.org>
Cc: linville@tuxdriver.com, davem@davemloft.net,
linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: notify userspace of security level change
Date: Mon, 14 May 2012 12:22:16 -0400 [thread overview]
Message-ID: <15456.1337012536@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 13 May 2012 03:20:07 -0300." <1336890007-10646-1-git-send-email-gustavo@padovan.org>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Sun, 13 May 2012 03:20:07 -0300, Gustavo Padovan said:
> It enables the userspace a security level change when the socket is
> already connected and create a way to notify the socket the result of the
> request. At the moment of the request the socket is made non writable, if
> the request fails the connections closes, otherwise the socket is made
> writable again, POLL_OUT is emmited.
What happens to in-flight data already written but not yet consumed? I'm
smelling a possible race condition with data sent under the old level but
read under the new level....
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2012-05-14 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 0:12 pull request: bluetooth 2012-05-04 Gustavo Padovan
2012-05-08 7:07 ` Gustavo Padovan
2012-05-11 20:16 ` Gustavo Padovan
2012-05-12 18:22 ` John W. Linville
2012-05-12 19:09 ` Gustavo Padovan
2012-05-12 19:11 ` [PATCH 1/2] Bluetooth: notify userspace of security level change Gustavo Padovan
2012-05-12 19:11 ` [PATCH 2/2] Bluetooth: mgmt: Fix device_connected sending order Gustavo Padovan
2012-05-13 6:20 ` [PATCH 1/2] Bluetooth: notify userspace of security level change Gustavo Padovan
2012-05-14 16:22 ` valdis.kletnieks [this message]
2012-05-13 6:22 ` Gustavo Padovan
2012-05-13 4:31 ` pull request: bluetooth 2012-05-04 Johan Hedberg
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=15456.1337012536@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=davem@davemloft.net \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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
all inboxes | Powered by JetHome®