From: Gianluca Anzolin <gianluca@sottospazio.it>
To: Mathias Hasselmann <mathias.hasselmann@kdab.com>
Cc: Dean Jenkins <Dean_Jenkins@mentor.com>, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Fix tty refcounting in rfcomm/tty.c
Date: Wed, 10 Jul 2013 13:24:46 +0200 [thread overview]
Message-ID: <20130710112446.GA9592@debian.seek.priv> (raw)
In-Reply-To: <1373445561.4594.21.camel@smarty>
On Wed, Jul 10, 2013 at 10:39:21AM +0200, Mathias Hasselmann wrote:
> > Is this failure easy to reproduce ?
>
> Just setup a RFCOMM tty and then violently break the link, by killing
> the rfcomm tool, by plugging the bt adapter, by turning off one
> peer, ... As soon as timeouts occur on the still running side you'll get
> the panic. Almost 100% reproducible.
Hi,
yes indeed that's the easiest way to reproduce the issue. I was wondering
why so few people hit these bugs since they're so easy to trigger.
Did you have a chance to test the two patches I sent?
Ciao,
Gianluca
>
> Ciao,
> Mathias
> --
> Mathias Hasselmann | mathias.hasselmann@kdab.com | Software Engineer
> KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
> Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090
> KDAB - Qt Experts - Platform-independent software solutions
>
>
next prev parent reply other threads:[~2013-07-10 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 17:05 [PATCH 1/2] Fix tty refcounting in rfcomm/tty.c Gianluca Anzolin
2013-07-10 8:17 ` Dean Jenkins
2013-07-10 8:39 ` Mathias Hasselmann
2013-07-10 11:24 ` Gianluca Anzolin [this message]
2013-07-10 9:37 ` Gianluca Anzolin
2013-07-10 10:43 ` Gianluca Anzolin
2013-07-10 15:46 ` Gustavo Padovan
2013-07-10 16:24 ` Gianluca Anzolin
2013-07-10 16:55 ` Gustavo Padovan
2013-07-10 17:01 ` Gianluca Anzolin
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=20130710112446.GA9592@debian.seek.priv \
--to=gianluca@sottospazio.it \
--cc=Dean_Jenkins@mentor.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mathias.hasselmann@kdab.com \
/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).