From: Johan Hedberg <johan.hedberg@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/3] plugins/sixaxis: Fix cable pairing not working
Date: Wed, 8 Nov 2017 09:49:30 +0200 [thread overview]
Message-ID: <20171108074930.GA11778@x1c.lan> (raw)
In-Reply-To: <20171107182356.15683-1-hadess@hadess.net>
Hi Bastien,
On Tue, Nov 07, 2017, Bastien Nocera wrote:
> In 6c467e9, get_pairing_type() was modified to return a structure that's
> allocated on the stack. While not a problem for the direct callers,
> as the function is defined as "inline", function that expected to return
> this structure themselves would fail, as the stack would be trampled
> upon on function exit.
The devices array inside get_pairing() is declared as static, so I don't
see how this can be on the stack? Are these the structures you're
referring to? That said, it seems weird to have an inline function
declare a static variable, since then every single caller of the
function would cause another static variable to be allocated, right? It
seems to me that if the function is still desired to be inline then the
cable_pairing array should at least be moved into some c-file, so that
it only gets created once. Perhaps a better solution is however to stop
having get_pairing() as inline to begin with?
Johan
next prev parent reply other threads:[~2017-11-08 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 18:23 [PATCH 1/3] plugins/sixaxis: Fix cable pairing not working Bastien Nocera
2017-11-07 18:23 ` [PATCH 2/3] core/device: Add support for setting SDP record Bastien Nocera
2017-11-07 18:23 ` [PATCH 3/3] plugins/sixaxis: Provide DualShock 3 SDP record while adding new device Bastien Nocera
2017-11-08 11:29 ` Bastien Nocera
2017-11-08 7:49 ` Johan Hedberg [this message]
2017-11-08 11:06 ` [PATCH 1/3] plugins/sixaxis: Fix cable pairing not working Bastien Nocera
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=20171108074930.GA11778@x1c.lan \
--to=johan.hedberg@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@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).