[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080515181737.GC21623@elf.ucw.cz>
Date: Thu, 15 May 2008 20:17:37 +0200
From: Pavel Machek <pavel@...e.cz>
To: Dave Young <hidave.darkstar@...il.com>
Cc: kernel list <linux-kernel@...r.kernel.org>, gregkh@...e.de,
marcel@...tmann.org, linux-bluetooth@...r.kernel.org
Subject: Re: 2.6.26-rc1: warnings from sysfs, bluetooth related
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists