From: Pavel Machek <pavel@suse.cz>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
gregkh@suse.de, marcel@holtmann.org,
linux-bluetooth@vger.kernel.org
Subject: Re: 2.6.26-rc1: warnings from sysfs, bluetooth related
Date: Thu, 15 May 2008 20:17:37 +0200 [thread overview]
Message-ID: <20080515181737.GC21623@elf.ucw.cz> (raw)
In-Reply-To: <a8e1da0805111905y49239cb7ja13f8e1c685bf6a9@mail.gmail.com>
Hi!
> > I'm getting these from rfcomm...
>
>
> Are you sure it's a regression?
No, I'm not sure it is an regression. I have not seen it in a while,
and I seen it on -rc1. It does not seem to be too repeatable.
> Dont know if it's same bug as BUG 10341. I just describe the problem
> in bug 10341:
>
> While a rfcomm device is opened more than once, the BUG 10341 can be triggered.
>
> rfcomm dev reference will be held for every rfcomm_tty_open, but release_dev
> will hangup the tty and release the dev number for free use without
> judge the dev->opened.
>
> rfcomm_dev_state_change and rfcomm_tty_hangup could del the rfcomm dev
> as well, the problem is similar as above.
>
> If the create_dev called before the last tty_close, sysfs will
> warning and create will fail.
>
> I have a patch which don't hold the dev reference in rfcomm_tty_open,
> but it need some review and test.
>
> please see:
> http://bugzilla.kernel.org/attachment.cgi?id=15746
>
> Marcel, do you have idea about this? or other solution?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-05-15 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 16:19 Pavel Machek
2008-05-12 2:05 ` Dave Young
2008-05-15 18:17 ` Pavel Machek [this message]
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=20080515181737.GC21623@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=gregkh@suse.de \
--cc=hidave.darkstar@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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®