Re: [PATCH RESEND] client: Clean up agent if bluetoothd exited without releasing it

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Johan,

On Monday 28 of April 2014 11:22:36 Johan Hedberg wrote:
> Hi Szymon,
> 
> On Fri, Apr 25, 2014, Szymon Janc wrote:
> > If bluetoothd exited without releasing agent (eg. due to crash) it was
> > not possible to register client as agent after daemon was restarted.
> > ---
> >  client/agent.c | 21 +++++++++++++++++++--
> >  1 file changed, 19 insertions(+), 2 deletions(-)
> 
> Since client/main.c is already doing tracking or org.bluez I think it
> might make more sense to do the agent clearing from there, maybe by
> adding an agent_clear function to agent.c and then calling it from
> disconnect_handler in main.c. Thoughts?

There is patch from Luiz that does exactly this and I'm fine with applying it
instead.

"[PATCH BlueZ 2/3] client: Fix not releasing agent if bluetoothd exit without
calling Release" from 26.11.2013.

-- 
Best regards, 
Szymon Janc
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux