From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sun, 1 Sep 2013 17:55:25 +0100 From: Gustavo Padovan To: Pavel Machek Cc: marcel@holtmann.org, johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org, kernel list Subject: Re: 3.11-rc7: unpriviledged user crashes kernel using bluetooth Message-ID: <20130901165525.GK7440@joana> References: <20130831100127.GA6711@amd.pavel.ucw.cz> <20130831100933.GA7029@amd.pavel.ucw.cz> <20130831101451.GC7029@amd.pavel.ucw.cz> <20130831104238.GA7767@amd.pavel.ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20130831104238.GA7767@amd.pavel.ucw.cz> List-ID: Hi Pavel, 2013-08-31 Pavel Machek : > On Sat 2013-08-31 12:14:51, Pavel Machek wrote: > > On Sat 2013-08-31 12:09:33, Pavel Machek wrote: > > > Hi! > > > > > > > . Python sources for client/server are at > > > > > > > > http://tui.cvs.sourceforge.net/viewvc/tui/tui/liveview/ > > > > > > > > . My kernels like to warn about > > > System is debian stable with gnome2. > > > > And no, it is not fixed in 3.11-rc7. > > 2.6.32-5-686 from debian seems to work. Could you try linux-next? We recently pushed a rework of the RFCOMM tty handling, it should fix this. The work was too big to be pushed to 3.11 Gustavo